Brian Kennedy

Navigation of the Deep Space 1 spacecraft at Borrelly

The navigation challenges posed by Deep Space 1s flyby of comet Borrelly were considerable due to the uncertainty in the knowledge of the comets ephemeris, as well as difficulty in determining the spacecrafts ephemeris caused by relatively large non-gravitational forces acting on the comet. The challenges were met by using a combination of radio, optical, and interferometric data types to obtain a final fly by accuracy of less than 10 km.

AutoNav Mark3 : engineering the next generation of autonomous onboard navigation and guidance

The success of JPLs AutoNav system at comet Tempel-1 on July 4, 2005, demonstrated the power of autonomous navigation technology for the Deep Impact Mission. This software is being planned for use as the onboard navigation, tracking and rendezvous system for a Mars Sample Return Mission technology demonstration, and several mission proposals are evaluating its use for rendezvous with, and landing on asteroids. Before this however, extensive re-engineering of AutoNav will take place. This paper describes the AutoNav systems-engineering effort in several areas: extending the capabilities, improving operability, utilizing new hardware elements, and demonstrating the new possibilities of AutoNav in simulations.

Locating the LCROSS Impact Craters

The Lunar CRater Observations and Sensing Satellite (LCROSS) mission impacted a spent Centaur rocket stage into a permanently shadowed region near the lunar south pole. The Sheperding Spacecraft (SSC) separated ∼9 hours before impact and performed a small braking maneuver in order to observe the Centaur impact plume, looking for evidence of water and other volatiles, before impacting itself.This paper describes the registration of imagery of the LCROSS impact region from the mid- and near-infrared cameras onboard the SSC, as well as from the Goldstone radar. We compare the Centaur impact features, positively identified in the first two, and with a consistent feature in the third, which are interpreted as a 20 m diameter crater surrounded by a 160 m diameter ejecta region. The images are registered to Lunar Reconnaisance Orbiter (LRO) topographical data which allows determination of the impact location. This location is compared with the impact location derived from ground-based tracking and propagation of the spacecraft’s trajectory and with locations derived from two hybrid imagery/trajectory methods. The four methods give a weighted average Centaur impact location of −84.6796°, −48.7093°, with a 1σ uncertainty of 115 m along latitude, and 44 m along longitude, just 146 m from the target impact site. Meanwhile, the trajectory-derived SSC impact location is −84.719°, −49.61°, with a 1σ uncertainty of 3 m along the Earth vector and 75 m orthogonal to that, 766 m from the target location and 2.803 km south-west of the Centaur impact.We also detail the Centaur impact angle and SSC instrument pointing errors. Six high-level LCROSS mission requirements are shown to be met by wide margins. We hope that these results facilitate further analyses of the LCROSS experiment data and follow-up observations of the impact region.

The challenges of deep impact autonomous navigation

On July 4, 2005 at 05:44:34 UTC the Impactor spacecraft (s/c) impacted comet 9P/Tempel 1 with a relative speed of more than 10 km/s. The Flyby s/c captured the impact event, using both the medium resolution imager and the high resolution imager, and tracked the impact site for the entire observing period following impact. The objective of the Impactor s/c was to impact in an illuminated area viewable from the Flyby s/c and telemeter high-resolution context images of the impact site prior to impact. The Flyby s/c had two primary objectives: (1) capture the impact event in order to observe the ejecta plume expansion dynamics and (2) track the impact site for at least 800 s to observe the crater formation and capture high-resolution images of the fully developed crater. All of these objectives were met by estimating the trajectory of each spacecraft relative to 9P/Tempel 1 using the autonomous navigation system, precise attitude information from the attitude determination and control subsystem, and allowing each spacecraft to independently select the same impact site. This paper describes the challenges of targeting and tracking comet 9P/Tempel 1.

Dawn Navigation and Mission Design at Dwarf Planet Ceres

Dawn, one of NASA’s Discovery Program missions, was launched on September 27, 2007, to explore two residents of the main asteroid belt in order to yield insights into important science questions about the formation and evolution of the solar system [1]. Its main objective is to acquire data from orbit around two complementary bodies, Vesta and Ceres, the two most massive objects in the main belt. From July of 2011 to September of 2012, the Dawn spacecraft orbited Vesta and returned much valuable science data, collected during the six planned mapping orbits at the protoplanet. Figure 1 depicts the Dawn’s interplanetary trajectory and timeline.

Modeling of Deadbanding DV for the Stardust Earth Return: Calibration, Analysis, Prediction and Performance

On January 15th, 2006, 0556 UTC, the Stardust spacecraft released a 42-kg Sample Return Canister (SRC) along a trajectory intended to impact a target on the Air Force Utah Test and Training Range (UTTR), near Dugway, Utah. Assurances of a successful SRC delivery to UTTR depended on identifying (and mitigating, if possible) a myriad of error sources. These sources included atmospheric effects, maneuver execution, Orbit Determination (OD) uncertainties and (Delta)V induced by the firing of the unbalanced Reaction Control System (RCS) thrusters needed for deadband attitude control. Every mm/s in prediction error at the TCM-19 epoch would amount to missing the target by approximately one kilometer. This paper will describe the work performed in analyzing and predicting the levels of (Delta)V caused by the attitude deadbanding, as well as prediction performance.