The Super Heavy booster was supposed to flip around, relight its engines, and fly back toward a controlled splashdown in the Gulf of Mexico. Instead, multiple Raptor engines cut out during the boostback burn, and the 233-foot-tall steel cylinder tumbled uncontrolled into the water. SpaceX’s ninth integrated Starship test flight, launched from Starbase in Boca Chica, Texas, in early 2025, had gone well up to that point. The booster’s crash was the single unambiguous hardware failure on a mission that otherwise hit its marks.
The Federal Aviation Administration responded by requiring a mishap investigation, but its scope surprised many observers. The probe targeted only the loss of the Starship upper-stage vehicle, not the booster. The FAA said the booster’s crash fell under existing “test-induced damage” exceptions because all debris landed within designated hazard areas. No people, no property, no third-party risk. By the agency’s own framework, that made the booster loss a tolerable outcome, not a triggering event for a standalone federal investigation.
What the flight actually accomplished
Flight 9 was the latest in a rapid sequence of full-stack Starship tests that have accelerated since the program’s rocky debut in April 2023. That first integrated flight ended in a mid-air explosion and a launch pad cratered by exhaust. Since then, SpaceX has rebuilt the pad, redesigned the flight termination system, and pushed the vehicle further on each attempt. Flight 5, in October 2024, produced the program’s signature moment: the Super Heavy booster flying back to the launch tower and being caught mid-air by the tower’s mechanical arms.
On Flight 9, the Starship upper stage reached its intended suborbital trajectory and performed its planned maneuvers before it was lost during reentry or shortly after. SpaceX has not published a detailed timeline of the upper-stage failure, and the FAA’s investigation into that loss is the one that remains formally open as of June 2026. The booster, meanwhile, completed its primary job of pushing the upper stage to separation altitude and velocity. Everything after separation, including the boostback burn, was a secondary objective aimed at proving the reusability sequence that SpaceX needs for its long-term plans.
Those plans are not abstract. NASA is counting on Starship as the Human Landing System for its Artemis lunar missions. SpaceX has proposed using the vehicle to deploy next-generation Starlink satellites in bulk. And the company’s stated reason for existing, putting humans on Mars, depends on a fully and rapidly reusable Starship and Super Heavy stack. Every booster that crashes instead of landing is a booster that cannot fly again, which is the entire economic and operational premise of the program.
The regulatory logic behind the FAA’s narrow scope
The FAA’s decision to exclude the booster from the Flight 9 mishap investigation reflects how the agency has structured oversight for Starship from the beginning. SpaceX’s launch license for Starship flights from Boca Chica designates large swaths of the Gulf of Mexico as hazard areas. Ships and aircraft are cleared from those zones before every launch. If hardware falls inside those boundaries, the FAA treats it as a planned contingency, not an accident in the regulatory sense.
That framework is laid out in the agency’s stakeholder engagement materials for the Starship program. The Gulf serves as a controlled impact zone precisely so that boosters and upper stages can fail without creating public safety consequences. The FAA’s primary mandate is protecting people on the ground and in the air, not protecting the vehicle itself.
This is why the 63 corrective actions from the first flight test matter as context. After the April 2023 failure, the FAA conducted a thorough investigation and published a closure notice requiring SpaceX to complete all 63 actions before flying again under a modified license. Those fixes ranged from pad hardening and debris mitigation to flight termination system upgrades. The agency demonstrated on that occasion that it will ground the program and impose extensive requirements when a failure breaches safety boundaries. The Flight 9 booster crash did not cross that line.
What nobody outside SpaceX knows yet
The public record on the booster failure is thin. No FAA filing specifies how many Raptor engines failed, whether they shut down simultaneously or in a cascade, or what triggered the losses. SpaceX’s own webcast showed engines going dark during the boostback burn, and independent observers captured footage of the booster descending without controlled thrust, but the company has not released detailed telemetry or a root-cause statement.
Several specific gaps stand out. The FAA has not said whether debris from the booster was recovered from the Gulf. Recovery would be standard practice for diagnosing a structural or propulsion failure, but the agency has neither confirmed nor denied it. There is also no public comparison of the Flight 9 booster’s performance against earlier Super Heavy flights. Without that data, outside analysts cannot tell whether the engine failures represent a regression from previous flights or a new failure mode that appeared under different conditions.
The corrective-action trail is similarly opaque when it comes to engines specifically. The 63 actions from the first flight covered a broad range of systems, but the FAA has not broken out which ones apply to Raptor engine reliability or boostback burn procedures. SpaceX may well have addressed engine-related issues internally, but no public regulatory document confirms what changes were implemented on the booster hardware or software that flew on Flight 9.
It is also unclear whether the FAA imposed any temporary operating constraints on SpaceX after the booster loss. Regulators sometimes require additional margins, modified trajectories, or reduced propellant loads while an investigation is open. Because the agency’s public statements focus on the upper-stage investigation, any booster-specific limitations that may have been added to subsequent licenses or waivers remain out of public view.
A contained failure on a program built to absorb them
The Flight 9 booster crash fits a pattern that has defined the Starship program from the start: test aggressively, accept hardware losses, and iterate faster than any traditional aerospace development schedule would allow. SpaceX has been explicit about this philosophy. The company builds Starship and Super Heavy vehicles on a production line, not as one-off prototypes, and it treats flight tests as data-gathering exercises where losing a vehicle is an expected cost.
That approach works as long as two conditions hold. First, failures have to stay inside the safety boundaries that the FAA has approved. The Flight 9 booster met that condition. Second, each failure has to produce engineering data that prevents the same problem from recurring. Whether that second condition is being met is something only SpaceX and, to some extent, the FAA can evaluate, because the relevant telemetry and failure analyses are not public.
For anyone watching the program from the outside, the booster crash is a reminder that the gap between SpaceX’s internal knowledge and the public record is wide and deliberate. The FAA’s regulatory structure permits this. As long as debris lands where it is supposed to and license conditions are met, the agency does not require SpaceX to publish engine-failure root causes or detailed flight performance data. The company can keep testing at a pace that would be impossible under a more disclosure-heavy regime, while observers are left to piece together what went wrong from webcast footage, regulatory filings, and the occasional statement from SpaceX leadership.
Multiple engine losses during a boostback burn are not a minor engineering problem. The boostback burn is the maneuver that turns a spent booster around and sends it back toward its landing site. If that burn fails, the booster has no way to reach a controlled landing, whether on a barge, at the launch tower, or in a designated splashdown zone. For a vehicle SpaceX wants to catch at the tower and refly within hours, reliable boostback performance is not optional. It is the foundation of everything the company says Starship will eventually do.
The Gulf of Mexico absorbed the failure this time. The regulatory system treated it as a tolerable loss. But every booster that crashes instead of landing is a data point about how far the hardware still has to go before Starship becomes the rapidly reusable launch system that NASA, SpaceX’s commercial customers, and the company’s own Mars ambitions all require.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
