Blog Archive

Sunday, March 29, 2020

P/2020 F1 Leonard

In an interesting MPML message, Sam Deen who found precovery images of this comet has shown that P/2020 F1 Leonard had a close encounter with Saturn in May 1936.

The close approach has been confirmed by Denis Denisenko and also by Syuichi Nakano that mentioned it in CBET 4737 (see by Brian Skiff's note ).

Denis Denisenko has also shown that what was previously thought to be a galaxy known as SDSS J113712.61+064629.0 was in fact the same comet!

It seems that the close approach with Saturn occurred at less than 1 mln km distance, quoting his words "coming to the point where Titan should be probably taken into account".

Due to this possibility, I am not sure if the below simulation can be reliable because even if all planets (including Uranus and  ... well ... also former planet Pluto) were taken into account, I did not add Titan.

As suggested by Denis Denisenko, Titan should probably be taken into account because according to the simulation results shown below, the close encounter with Saturn could have occurred at a distance much much lower than 1 mln km... I really wonder if what shown below makes sense!.

I generated 100 clones trying to achieve the same orbital parameters reported in JPL Small-Body Database.

Ephemeris | Orbit Diagram | Orbital Elements | Mission Design | Physical Parameters | Close-Approach Data ]

[ show orbit diagram ]

Orbital Elements at Epoch 2458881.5 (2020-Feb-02.0) TDB
Reference: JPL 1 (heliocentric ecliptic J2000)
 Element Value Uncertainty (1-sigma)   Units 
e .4167294137837126 3.2093e-05
a 6.828937975484302 0.00042644 au
q 3.983118656195396 3.0111e-05 au
i 5.435887012485813 9.3305e-05 deg
node 136.6570425356324 0.0006689 deg
peri 8.692144095904881 0.0050162 deg
M 8.65720560933176 0.0015783 deg
tp 2458724.751493851214
(2019-Aug-29.25149385)
0.036878 TDB
period 6518.207463241558
17.85
0.61055
0.001672
d
yr
n .05522990822709547 5.1733e-06 deg/d
Q 9.674757294773208 0.00060415 au
Orbit Determination Parameters
   # obs. used (total)      85  
   data-arc span      443 days (1.21 yr)  
   first obs. used      2019-01-03  
   last obs. used      2020-03-21  
   planetary ephem.      DE431  
   SB-pert. ephem.      SB431-N16  
   condition code      4  
   norm. resid. RMS      .44614  
   source      ORB  
   producer      Otto Matic  
   solution date      2020-Mar-25 18:12:07  

Additional Information
 Earth MOID = 2.99577 au 
 Jupiter MOID = .379473 au 
 T_jup = 2.835 
P/2020 F1 (Leonard)
Classification: Jupiter-family Comet          SPK-ID: 1003664

Clones simulated


Clones Target
mean sd mean sd
q 3.98312397488 3.011474e-05 3.9831186562 3.0111e-05
e 0.41673463882 3.223462e-05 0.41672941378 3.2093e-05
i 5.43588826127 9.318419e-05 5.43588701249 9.3305e-05
peri 8.69166111114 0.00503993969 8.6921440959 0.0050162
node 136.65698385154 0.00067172871 136.65704253563 0.0006689
tp 2458724.74745393 0.03690546666 2458724.75149385 0.036878


Simulation Details
Mercury6 simulator by John E. Chambers.


)---------------------------------------------------------------------
) Important integration parameters:
)---------------------------------------------------------------------
 algorithm (MVS, BS, BS2, RADAU, HYBRID etc) = BS
 start time (days)= 2459000.5
 stop time (days) = -1d8
 output interval (days) = 100
 timestep (days) = 0.05
 accuracy parameter=1.d-12


Simulation Results

The comet P/2020 F1 Leonard - taking into account its nominal params, seems to have entered the solar system (conventional distance 100 AU) about 45K years ago while the first clones did it even earlier about 10-20K years ago.

Considering the close encounter with Saturn:
  • the "nominal" comet had the encounter on May 12, 1936 (distance 0.0046 AU - about  700000 km). Note that the simulation step was 0.05 days, I wonder if this "granularity" may explain the difference compared with the real nominal distance that was achieved on May 7th/8th.
note:  if you use the Horizons system via telnet interface
( telnet horizons.jpl.nasa.gov 6775 ), a similar date is found:

Close-approach results:

Time (JDTDB): 2428300.80754
Date (TDB): 1936 May 12.30754
Body: Satrn
CA Dist : .004603
MinDist : .000000
MaxDist: .022999
Vrel: 10.676

  •  more in general, 99 clones (including the nominal comet) had the close encounter with Saturn in 1936, the other one had it in 1937.
The minimum distance from Saturn was 0.0000727 AU (about 11000 Km ???).




Can the simulator manage such a situation? 
Not clear to me ... however, out of curiosity, let's say for a moment ... yes!
In the following plots we can clearly see the "orbital disruption" suffered by the comet when it passed near Saturn in the 1930's.





 

 


 


 

 
 


Kind Regards,
Alessandro Odasso

Sunday, March 1, 2020

2020 CD3 - new temporary mini moon

I understand looking at Tony Dunn's simulations (press orbit simulator view button in this page provided by Bill Gray's project pluto) and comments in MPML that chaos is playing a big role here.

For this reason, I am not sure that a backward simulation can be useful to get an idea of the asteroid behaviour.
Probably not .. .but just for curiosity let's do it and let's assume for a moment that 2020 CD3 is a natural object.

I generated 100 clones trying to achieve the "same" orbital parameters and sigma as provided by the JPL solution (Horizons Web Interface)


  Clones   Target
  mean sd   mean sd
q 1.00502954166 2.714862e-05   1.00503150094 2.7143e-05
e 0.01726251622 2.418728e-05   0.01726090999 2.4152e-05
i 0.6401240941 0.00012806312   0.64011545932 0.0001279
peri 46.79953402529 0.09813338369   46.79424491192 0.098245
node 83.09078802026 0.05641077311   83.08730279228 0.056433
tp 2458877.63623114 0.04030051738   2458877.6339221 0.040361

I gave a look at close encounters with other planets a part Eeath-Moon itself.
It seems that in order to see these hypothetical close encounters we need to go back many centuries.
I found that these encounters are more likely and more recent with Venus rather than Mars.
Could this be a hint that the origin of this object is from the inner part of the solar system?

Kind Regards,
Alessandro Odasso

100416 Syang (1996 CB) - is it part of a cluster?

Orbital parameters:

                              a         e        i        om        w
       (2014 PX11)     1.920100 0.1193356 17.32704 -40.72053 87.31196
100416 Syang (1996 CB) 1.920056 0.1196798 17.31632 -40.82830 87.34793
       (2013 SJ104)    1.919897 0.1197210 17.32132 -40.70037 87.14390

  ,



Thanks to Rob D. Matson for noting this: 
"2016 CP39 is also similar, though not quite as close as the others are to each other." 

Coming back to those three asteroids, I made a backward simulation with just a few clones going back about 278K years.
The most interesting couple is 2013 SJ104 and 2014 PX11. Of course, this is not a proof.




Kind Regards,
Alessandro Odasso