The Lewis Spacecraft Mission Failure Investigation Board Report Term Paper

The Lewis Spacecraft Mission Failure probe Board Report - Term Paper ExampleAfter launch and successful insertion into range of mountains, the ballistic capsule lost contact with the ground station and later became a total way out. An Investigation Board inquired into the loss and determined that a problem with the Attitude Control System lead to the loss (NRC & NASA 54). They also place several factors that may have contributed to the catastrophic loss in the management and engineering rigor utilize in the jump out. This paper relates to the shortcoming and the lesson that a systems engineer in charge of a similar bug out can learn from it. The Lewis Spacecraft Mission Failure Investigation Board (LSMFIB) identified two deal factors, and several indirect factors contributing to the mission failure. The first direct factor identified was flawed end and simulation of the Attitude Control System (ACS). The send off of the ACS was such that in safe mode, the spacecraft would be in a power positive orientation (LSMFIB 9). However, an imbalance in the thrusters caused the spacecraft to face away(predicate) from the sun in such a way that the suns rays hit the edges of the solar panels powering the spacecraft. This led to draining of the batteries at a quick rate because of the power subsystem and thermal subsystem Safe Mode design (LSMFIB 9). ... The first reason was that there was pressure on the spacecraft development team to cut be hence they implemented a single shift. This made the discovery of anomalies very difficult. In fact, the actual problems occurred when no one was on duty. The second reason is that the ground crew failed to declare an emergency even later noting problems that would have justified such a declaration. These problems included the fact that the spacecraft was using the B-side processor when it reached orbit instead of the A-side processor. The second unusual person was that the solid state recorder would not play back the d ata previously recorded, which included the flight data that would have shown the anomalies that affected simulation (LSMFIB 11). The third anomaly was that the ground crew failed to get the space telemetry signal only for the spacecraft to reappear with an uncontrolled emplacement (LSMFIB 11). The fourth anomaly was that after leaving the spacecraft in safe mode for duration, it took on spin with the edges of the solar panels facing the sun. Any of these anomalies warranted the declaration of an emergency, which did not happen. The indirect causes of the mishap were actions taken that did not line up to industry standards. If the development teams stuck to the standards, then it is likely that the catastrophic failure would not have occurred. These include project scope creep, cost and schedule pressure, inadequately planned relocation of some production units that affected good review and testing, frequent changes to the personnel working on the program, and insufficient engine ering and management discipline (LSMFIB 12-14). The reasons