Much can be learned from well-written descriptions of the technical and organizational factors that lead to an accident. Subsequent analysis by third parties of investigation reports and associated evidence collected during the investigations can lead to additional insight. Much can also be learned from documented close calls that do not result in loss of life or a spacecraft, such as the Mars Exploration Rover Spirit software anomaly, the SOHO mission interruption, and the NEAR burn anomaly. Seven space shuttle incidents fall into the latter category Rendezvous Target Failure On STS-41B Rendezvous Radar Anomaly and Trajectory Dispersion-STS-32 Rendezvous Lambert Targeting Anomaly-STS-49 Rendezvous Lambert Targeting Anomaly-STS-51 Zero Doppler Steering Maneuver Anomaly-STS-59 Excessive Propellant Consumption During Rendezvous-STS-69 Global Positioning System Receiver and Associated Shuttle Flight Software Anomalies-STS-91 Procedural work-arounds or software changes prevented them from threatening mission success. Extensive investigations, which included the independent recreation of the anomalies by multiple Shuttle Program organizations, were the key to determining the cause, accurately assessing risk, and identifying software and software process improvements. Lessons learned from these incidents not only validated long-standing operational best practices, but serve to promote discussion and mentoring among Program personnel and are applicable to future space flight programs.
Lessons Learned from Seven Space Shuttle Missions
2007
52 pages
Report
No indication
English
Lessons Learned from Seven Space Shuttle Missions
NTRS | 2007
|Microbiological Lessons Learned From the Space Shuttle
AIAA | 2011
|Microbiological Lessons Learned from the Space Shuttle
NTRS | 2011
|Microbiological Lessons Learned from the Space Shuttle
NTIS | 2011
|Space shuttle orbiter venting: Lessons learned
NTRS | 1983
|