Loading…
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 p...
Saved in:
Published in: | Journal of field robotics 2007-04, Vol.24 (4), p.339-354 |
---|---|
Main Authors: | , , , , , , , , |
Format: | Article |
Language: | English |
Citations: | Items that this one cites Items that cite this one |
Online Access: | Get full text |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Summary: | 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. © 2007 Wiley Periodicals, Inc. |
---|---|
ISSN: | 1556-4959 1556-4967 |
DOI: | 10.1002/rob.20177 |