Project HOPE: Part I – Getting out of the Gate
On April 5, 2006, an initial development test was conducted onboard a sounding rocket flight (41.068) which collected analog ground imagery during the descent portion of the rocket’s trajectory and IMU and GPS data from launch to landing. This data was then used to further develop and test Terrain-Relative Navigation (TRN) computer algorithms.
The TRaiNED project is the next step in the development of this new technology. As a second developmental test flight, TRaiNED builds upon the first flight by expanding the data set to include exo-atmospheric imagery in addition to descent imagery.
At this point in the story, the team is two months into their project and they have just completed their System Requirements Review (SRR).
Learn more about Project HOPE:
APPEL Website – http://appel.nasa.gov/hands-on/hope/
ASK Magazine Part I – http://go.nasa.gov/1mJGs07
ASK Magazine Part II – http://go.nasa.gov/1mJGvsI
Related Resources
-
Houston, we had a problem…and we learned from it!Space is hard. Inevitably, problems may occur. We can all learn valuable lessons from past events to ensure the safety and success of current and future programs. Enjoy reading and learning from a selection of such events. This booklet produced by the Johnson Space Center Knowledge Management Office contains numerous lesson learned from NASA missions and projects.
-
Apollo 1-Challenger-ColumbiaEvery year as we get back in the saddle, our Remembrance Day signals us to think back to the tragic events of Apollo 1, Challenger and Columbia as well as the context surrounding them. We’re accountable for learning from not just what went wrong, but how we recovered. As an example, read these rules recorded by Wayne Hale, former NASA Flight Director and Space Shuttle Program Manager. By actually applying such lessons from the past to your current work, our actions can honor our lost crews beyond silent reflection.
-
Shuttle Software AnomalyCase Study–A few minutes after the Shuttle Endeavour reached orbit for STS-126 on Nov. 14, 2008, mission control noticed that the shuttle did not automatically transfer two communications processes from launch to orbit configuration. Primary communications continued to use S-band frequencies after they should have transferred to the more powerful Ku-band. The link between the shuttle and its payload — the Payload Signal Processor (PSP)–remained configured for a radio link rather than switching.
