# Made by eph2tle, compiled Nov 24 2020 16:22:39 # Run at Wed Nov 25 16:15:14 2020 # # No updates (going to the moon) # # The following TLEs (Two-Line Elements) were generated by fitting # a numerically-integrated ephemeris, based on the orbit given below, # to the SDP4/SGP4 models. Each TLE is good for the interval between # its epoch and the epoch of the subsequent TLE (usually one day). # The maximum deviation between the numerically integrated ephemerides # and the TLE-based ephemeris, in kilometers, is given for each TLE # as the "worst residual". # # This fitting is done using the 'eph2tle' code packaged with Find_Orb. # The code has details on how the TLEs were computed : # # https://github.com/Bill-Gray/find_orb/eph2tle.cpp # # Be warned: the error given is that between the numerically # integrated ephems and the TLE model. There will usually be at # least some additional difference between the ephems and the actual # motion of the satellite, especially if the ephemerides are based # on a short arc. If the following orbital elements say something # like "[based on] 10 observations 2015 Jan. 1-13", and the TLEs # are for 2015 May, the extrapolation may be tenuous at best. If # your application requires a specific level of accuracy, you may # want to contact me; I can give you some idea as to the fit of the # underlying data (and possibly TLEs based on newer data). # # You can usually find the underlying observational data, and the # fitted orbit, residuals, ephemerides, and sometimes some comments # about the object, among the pages listed at # # https://www.projectpluto.com/pluto/mpecs/pseudo.htm # # Also, if you use a TLE outside the "correct" time range (between # its MJD and that of the next TLE), all bets are off. I've carefully # computed and minimized the worst error over the "correct" time frame, # but the ephemeris may (or may not) diverge wildly outside of it. # # Ephem range: 59177.000000 59181.000000 1.000000 # Created Wed Nov 25 16:14:54 2020 # Ephemeris start: 24 Nov 2020 0:00:00 # Ephemeris end: 28 Nov 2020 0:00:00 # Times are all TDT # Positions/velocities are in ecliptic J2000 # Orbital elements: 2020-087A = NORAD 47097 = Chang'e 5 s/c # Perigee 2020 Nov 23.87793779 +/- 0.000436 TT = 21:04:13.825 (JD 2459177.37793779) # Epoch 2020 Nov 25.0 TT = JDT 2459178.5 Find_Orb # M 38.20489988410 +/- 0.039 (J2000 equator) # n 34.04882505334 +/- 0.0229 Peri. 227.66196617 +/- 0.034 # a203486.414537 +/- 91.2 Node 2.20020643 +/- 0.037 # e 0.9681122001 +/- 1.95e-5 Incl. 21.29848854 +/- 0.0008 # P 10.57d H 27.6 G 0.15 U 10.2 # q 6488.73405513 +/- 1.49 Q 400484.095019 +/- 183 # 32 of 37 observations 2020 Nov. 25 (17.7 hr); mean residual 0".321 # # 1 NoradU COSPAR Epoch.epoch dn/dt/2 d2n/dt2/6 BSTAR T El# C # 2 NoradU Inclina RAAscNode Eccent ArgPeri MeanAno MeanMotion Rev# C # Worst residual: 107.72 km # MJD 59177.000000 (2020 Nov 24 0:00) 2020-087A = NORAD 47097 = Chang'e 5 s/c 1 47097U 20087A 20329.49919926 .00000000 00000-0 00000-0 0 10609 2 47097 021.2517 002.0693 9553394 227.9211 021.4926 00.08997058 09 # Worst residual: 36.85 km # MJD 59178.000000 (2020 Nov 25 0:00) 2020-087A = NORAD 47097 = Chang'e 5 s/c 1 47097U 20087A 20330.49919926 .00000000 00000-0 00000-0 0 10601 2 47097 021.1820 001.9510 9562760 227.7035 055.3331 00.09264023 06 # Worst residual: 53.95 km # MJD 59179.000000 (2020 Nov 26 0:00) 2020-087A = NORAD 47097 = Chang'e 5 s/c 1 47097U 20087A 20331.49919926 .00000000 00000-0 00000-0 0 10602 2 47097 020.9642 001.4577 9586896 227.8366 089.3256 00.09346337 09 # Worst residual: 243.27 km # MJD 59180.000000 (2020 Nov 27 0:00) 2020-087A = NORAD 47097 = Chang'e 5 s/c 1 47097U 20087A 20332.49919926 .00000000 00000-0 00000-0 0 10603 2 47097 020.0169 358.8329 9676980 229.6209 123.2070 00.09414094 06 Avg worst resid: 110.45 km Worst residual in entire run: 243.27 km on MJD 59180.0 1 3 10 30 100 300 1K 3K 10K km 0 0 0 0 2 2 0 0 0 0