Reclassifying the Starliner test as a Type A mishap highlights serious safety and financial risks, compelling NASA and Boeing to overhaul design and management practices to safeguard upcoming crewed missions.
The video dissects NASA’s newly released, heavily redacted Starliner Orbital Flight Test‑2 (OFT‑2) report, which upgrades the incident from a "close call" to a Type A mishap—an event involving injury, loss of life, or damage exceeding $2 million. By reclassifying the flight, NASA acknowledges over $200 million in lost value, including missed crew launches and schedule setbacks for the International Space Station.
Key technical findings include a software clock error on OFT‑1 that kept the vehicle’s thruster‑control paddle engaged too long, prompting an abnormal number of firings. Subsequent analysis linked nine of ten thruster failures to worn pressure transducers in the service module, while thermal soak and two‑phase oxidizer flow issues further degraded performance on OFT‑2. The report also maps the cryptic thruster codes (e.g., B1, A3) to their physical locations, revealing that the starboard pod suffered disproportionate failures due to heat‑induced nitrogen‑tetroxide breakdown.
Scott Manley highlights concrete consequences: loss of six‑degree‑of‑freedom control during ISS approach, delayed docking, and the need to return the crew on SpaceX’s Crew Dragon. He notes that the service module, which houses the RCS thrusters, is jettisoned and burns up, leaving only telemetry for post‑flight forensics. The analysis underscores how off‑the‑shelf thrusters placed in non‑standard housings amplified the failure cascade.
The implications are stark. The $200 million cost, coupled with reputational damage, forces NASA and Boeing to revisit management practices, software validation, and thermal design of the service module. Future crewed flights will likely see stricter testing regimes and redesigns to mitigate similar thruster and sensor failures, affecting timelines and budgets for America’s commercial crew program.
Comments
Want to join the conversation?
Loading comments...