Asteroid operations

Here is some data for a given UTC time. The data is obtained by interpolating the most up-to-date NAIF's files (the maximum interpolation error is shown next to the interpolated value) for the following coverage windows:
S/C h:           START: , END: 
S/C v:           START: , END: 
S/C r, lat, lon: START: , END: 
Sun r, lat, lon: START: , END: 
Bennu - Earth:   START: , END: 
S/C - Earth:     START: , END: 
S/C x axis:      START: , END: 
S/C z axis:      START: , END:

The graph shows the location of the spacecraft (S/C) and the Sun on the surface of Bennu. The latitude and the longitude are calculated as explained here.

UTC:

S/C:
SUN:
Bennu - Earth:
S/C - Earth:

h is the s/c altitude (m). Please, take a look here for further details.
r in the line "S/C" is the s/c radius vector (m) relative to Bennu, while r in the line "SUN" is Bennu radius vector (km). The interpolation error is calculated as the distance between the interpolated position and the NAIF position.
v is the s/c inertial speed wrt Bennu (mm/s).
Bennu - Earth and S/C - Earth are the distances (km) between the center of the bodies.



Here's the 3D version of the previous map in the Bennu-fixed rotating reference frame.
Blue dot: spacecraft; red dot: Nightingale; gray dot: Osprey; yellow line: Sun direction; magenta line: Earth direction.

S/C axes pointing direction (R.A., decl.; deg): X: Y: Z:

The interpolation error for the pointing direction is calculated as the maximum error between the right ascension error and the declination error. The right ascension error and the declination error are calculated as the difference between the interpolated value and the NAIF value.
The pointing direction of the x and z axes is obtained from the interpolation, while the pointing direction of the y axis is obtained from the cross product of z and x.


The interpolation error for the values used in the map (the first graph) is calculated as: interpolated_value - NAIF_value. For example, an altitude shown as "h: 642.0 -6.5/1.3" means that the interpolated altitude above the sub-spacecraft point can be anywhere between NAIF_altitude - 6.5 and NAIF_altitude + 1.3. In other words, the following inequality holds: 642 - 1.3 ≤ NAIF_altitude ≤ 642 + 6.5. Please, note that the interpolation error has nothing to do with the uncertainty.
Usually the error on the s/c longitude is negligible, but when the s/c approaches the polar regions, the error on the longitude can reach several degrees.
For the s/c - Earth distance, the average interpolation error is less than half the maximum error.

According to NAIF's rotational constants updated to 2019 Sep 16, the location of Bennu prime meridian (longitude = 0) is:
W = 139.13621 + 2011.1459760340 · d + 1.815 · 10-6 · d2
where d represents days past J2000 (TDB) and W is the angle shown here ("Body" is Bennu; X, Y and Z axes represent the Bennu body-fixed rotating coordinate system used for the calculations).
Bennu north pole coordinates are: RA= 85.45218 deg, DEC= -60.36780 deg.

NAIF's data files

S/C orientation
 The s/c orientation is obtained from the predicted NAIF's data files (e.g. "orx_p_200309_200316_2011_od230_v01.bc"). The difference between the predicted orientation and the actual orientation obtained from the reconstructed data files (e.g. "orx_sc_red_200306_v02.bc") is usually negligible (it is less than 0.5 deg for each axis), but occasionally the difference can be as high as 6 degrees.
To accurately reproduce the s/c orientation during the Checkpoint Rehearsal phase, the following reconstructed files have been used: orx_sc_red_200413_v02.bc, orx_sc_red_200414_v02.bc and orx_sc_red_200415_v03.bc (the coverage window is from 2020-04-12 23:45:01 to 2020-04-16 00:14:59 UTC).
To accurately reproduce the s/c orientation during the Matchpoint Rehearsal phase, the following reconstructed file has been used: orx_sc_red_200811_v02.bc (the coverage window is from 2020-08-10 23:45:00 to 2020-08-12 00:15:00 UTC).

S/C position and velocity
orx_190601_191001_190614_od154-R-M4B-P-M2C_v1.bsp , tracking data: 01-JUN-2019 17:37:03 14-JUN-2019 17:34:18; orx_190612_190813_190730_od170-N_v1.bsp , tracking data: 12-JUN-2019 20:37:50 30-JUL-2019 17:35:03; orx_190712_190917_190814_od175-N_v1.bsp , tracking data: 12-JUL-2019 20:09:57 14-AUG-2019 16:34:46; orx_190809_191015_191004_od187-N-M2R-L-M5R_v1.bsp , tracking data: 09-AUG-2019 01:11:43 04-OCT-2019 17:22:03; orx_191001_191105_191021_od194-N-M9R-L-M13R_v1.bsp , tracking data: 01-OCT-2019 01:01:51 21-OCT-2019 16:33:00; orx_191015_191112_191028_od197-N-M12R-L-M13R_v1.bsp , tracking data: 15-OCT-2019 21:01:39 28-OCT-2019 16:33:13; orx_191027_200101_191104_od200-N_v1.bsp , tracking data: 27-OCT-2019 03:01:38 04-NOV-2019 16:18:44; orx_191101_200225_200214_od223-N_v1.bsp , tracking data: 01-NOV-2019 00:14:25 14-FEB-2020 16:32:30; orx_200127_200324_200311_od232-N-TR1T2-L_v1.bsp , tracking data: 27-JAN-2020 00:14:29 11-MAR-2020 17:33:13; orx_200226_200331_200316_od234-N_v1.bsp , tracking data: 26-FEB-2020 01:01:41 16-MAR-2020 16:36:02; orx_200305_200421_200406_od237-N-TR1P1-L_v1.bsp , tracking data: 05-MAR-2020 00:51:54 06-APR-2020 17:31:03; orx_200401_200421_200413_od240-N-TR1D-L-TR1BO_v1.bsp , tracking data: 01-APR-2020 01:01:41 13-APR-2020 17:33:46; Gap in the tracking data (Checkpoint Rehearsal phase) orx_200414_200519_200504_od248-N_v1.bsp , tracking data: 15-APR-2020 00:40:46 04-MAY-2020 16:40:34; orx_200430_200714_200629_od262-N-C3PO-L-BB8_v1.bsp , tracking data: 30-APR-2020 23:12:50 29-JUN-2020 17:31:57; orx_200616_200804_200720_od268-N_v1.bsp , tracking data: 16-JUN-2020 20:12:38 20-JUL-2020 17:35:48; orx_200709_200814_200814_od276-N_mprecon_v1.bsp , tracking data: 09-JUL-2020 23:14:42 14-AUG-2020 16:29:46; orx_200811_200908_200828_od280-N_v1.bsp , tracking data: 12-AUG-2020 00:12:16 28-AUG-2020 17:36:30; orx_200827_201103_201019_od292-N-T1D-L-T1R1_v1.bsp , tracking data: n/a.