100 likes | 119 Views
This case study examines the failure of the Archana Jagarlamudi spacecraft mission in 1997 and identifies factors that directly and indirectly contributed to its failure. Recommendations for future programs are also provided.
E N D
Lewis Spacecraft Mission Failure Archana Jagarlamudi EE 585: Fault Tolerant Computing EE 585: Case Study
Description • Launched into a 300 km parking on 23 august, 1997. • Lost control on 26 August , 1997. • Brought into atmosphere and destroyed on 28 September , 1997. EE 585: Case Study
Background • SSTI Program Description • Request For Proposal (RFP) • Significant Contract Changes EE 585: Case Study
Anomalies • Autonomous Switch over to the B-side Processor. • Solid State Recorder Failure. • Contact Lost for Two Orbits. • Spin about the Principal Axis. EE 585: Case Study
Factors Directly Contributing to Failure. • Flawed ACS Design and Simulation. * Flawed ACS Design. * Flawed ACS Simulation. • Inadeqaute Spacecraft Monitoring. * Single Crew Operations. * Failure to declare an Emergency. EE 585: Case Study
Factors Indirectly contributing to Failure • Requirement Changes without Adequate Resource Adjustment. • Cost and Schedule Pressure. • Move from Chantilly to Redondo Beach. • Inadequate Ground Station Availbility for Initial Operations. • Frequent TRW Personnel Changes. EE 585: Case Study
Recommendations in Future Programs. • Balance Realistic Expectations of Faster , Better , Cheaper. • Balance Well Understood Roles and Responsibities. • Adopt Formal Risk Management Practices. EE 585: Case Study
Contd…. • Formalize and implement Independent Technical Reviews. • Establish and Maintain Effective Communications. EE 585: Case Study
References EE 585: Case Study