SpaceX has identified the root cause of the Starship explosion that occurred last month. According to a company statement, the incident was triggered by a series of interrelated events, including propellant leaks. SpaceX has subsequently addressed these issues in preparation for an eighth test flight, scheduled for as early as this Friday.
The investigation revealed that approximately two minutes after Starship ignited its engines, a flash was observed in the aft section of the vehicle. This flash was indicative of a propellant leak, leading to increased pressure and sustained fires in that area. Consequently, all but one of Starship’s engines shut down in a controlled manner, resulting in a loss of communication with the craft.
SpaceX believes the leaks were likely caused by vibrations that exceeded anticipated levels during testing. These vibrations put excessive stress on the propulsion system’s hardware, triggering the automatic in-flight abort system and subsequent self-destruction of the Starship.
The explosion generated a spectacular display over the islands of Turks and Caicos, prompting the Federal Aviation Administration (FAA) to divert several flights as a precautionary measure. SpaceX emphasizes that all debris fell within the designated Debris Response Area, which is typically negotiated with government agencies prior to flights.
In response to the incident, SpaceX has implemented modifications to the fuel lines, adjusted propellant temperatures, and incorporated additional vents and a new purge system. These changes are intended to enhance the aft section’s resilience to propellant leakage.
The FAA is currently reviewing the investigation’s findings and may either close the case or grant SpaceX authorization to conduct the upcoming test flight while the investigation continues. This is the first time SpaceX has faced a mishap investigation while CEO Elon Musk operates within the US government, with his Department of Government Efficiency actively participating.
Original source: Read the full article on TechCrunch
