SpaceX is preparing Booster 20 for the next Starship test flight, but the company cannot launch until it satisfies federal regulators that the problems behind Flight 12’s engine failure and hard impact have been fixed. The May 22, 2026 test ended with booster engines cutting out during the vehicle’s return phase, sending the stage into an unplanned impact instead of the controlled splashdown SpaceX had planned. No injuries or property damage resulted, but the Federal Aviation Administration has classified the event as a mishap and grounded the program pending a completed investigation.
Flight 12 grounding puts Booster 20 timeline in question
The tension at the center of this story is straightforward: SpaceX builds and iterates hardware at a pace that few aerospace companies can match, but every unplanned outcome on a test flight triggers a regulatory process that operates on its own clock. The FAA’s general statements on mishaps make clear that once a flight is classified this way, SpaceX must lead an investigation under FAA oversight and receive approval for corrective actions before any return to flight. Until that investigation closes, Booster 20 sits on the ground regardless of how quickly SpaceX can ready the hardware.
That dynamic creates a real question about what actually controls the schedule. The original engine anomaly, in which booster engines failed during the return sequence, may prove to be a narrow technical problem with a known fix. But the length of the grounding will likely depend less on the severity of that single failure and more on how many hardware or procedural changes SpaceX proposes in response. Each modification the company puts forward must be reviewed and accepted by the FAA before clearance is granted. A simple software patch and a sweeping engine redesign carry very different review timelines, even if both trace back to the same root cause.
This pattern has played out before in SpaceX’s Starship program. Past mishap investigations have stretched weeks or months depending on the scope of corrective actions, not just the scale of the incident itself. If SpaceX identifies multiple areas for improvement and bundles them into the return-to-flight proposal, the FAA review window expands accordingly. The company’s own ambition to fix more than the minimum can, paradoxically, slow down the next launch.
That trade-off is central to how the Starship program evolves. Rapid iteration is one of SpaceX’s defining traits, but each additional upgrade folded into the Flight 12 response will be scrutinized as part of the mishap closeout. In practical terms, that means every new sensor, software change, or engine tweak intended to make Starship safer and more capable could lengthen the time before the next test leaves the pad.
What the FAA record and flight data confirm
The verified record from the FAA and reporting by the Associated Press establishes a clear sequence. The Starship Flight 12 launch took place on May 22, 2026. During the booster’s return, engines cut out, and the vehicle experienced a hard impact rather than the planned controlled splashdown. According to an Associated Press account, the FAA classified this outcome as a mishap with no injury or property damage.
SpaceX must now complete a company-led investigation under FAA oversight. That investigation must identify the root cause, propose corrective actions, and receive FAA approval before the next flight can proceed. The regulatory language is specific: SpaceX leads the technical work, but the FAA holds the authority to accept or reject the findings and any proposed fixes. Only when the agency concurs that the corrective actions adequately address the problem can the Starship launch license be amended or reauthorized for future flights.
No official statement from SpaceX or the FAA has confirmed what role Booster 20 will play in the next test or when that flight could occur. The company has been publicly preparing the booster, but preparation and clearance to fly are separate milestones. The FAA’s process does not set a fixed deadline for investigation completion, which means the timeline depends on the quality and scope of what SpaceX submits. A concise, well-documented corrective plan that targets a single failure mode will generally move faster than a broad package of upgrades that touches multiple subsystems.
The absence of injuries or property damage is significant for the regulatory process. A mishap with casualties or third-party damage would trigger a more intensive federal response and could involve agencies beyond the FAA. The clean safety outcome here keeps the investigation within the standard SpaceX-led framework, which is the fastest path back to flight that the current regulatory structure allows. It also reduces pressure for immediate, sweeping policy changes that might otherwise ripple across commercial launch licensing.
Open questions shaping the next Starship launch
Several gaps in the public record make it difficult to predict when Booster 20 will actually fly. No primary source has disclosed the specific failure mode that caused the engine cutout. Was it a single engine that shut down, triggering a cascade? Was it a fuel delivery problem, a software command error, or a structural issue in the propulsion system? The answer matters because it determines whether SpaceX can address the problem with a targeted repair or needs to redesign a broader system that affects every booster in the fleet.
Equally unclear is how SpaceX plans to incorporate Flight 12 lessons into Booster 20’s hardware. If the booster was already built and stacked before the mishap, retrofitting changes could add weeks of work, particularly if they involve plumbing, wiring, or access to hard-to-reach engine components. If the company anticipated certain upgrades and designed Booster 20 with margin for modifications, the turnaround could be faster. No official statement has addressed this question directly, leaving outside observers to infer the level of rework from visible activity at the launch site.
The FAA’s investigation oversight adds another variable. The agency does not publish interim findings or progress updates for ongoing mishap reviews. Observers tracking the program will have to watch for indirect signals: test firings at the Boca Chica facility, environmental filings that reference a new launch window, or public notices indicating that SpaceX has submitted its corrective action plan. Even then, those signs will show momentum, not a guaranteed launch date.
For readers following the Starship program, the practical takeaway is that hardware readiness and regulatory readiness are two different things, and the second one controls the schedule. SpaceX can bolt Booster 20 to the launch mount, complete static fires, and declare the vehicle ready, but none of that substitutes for a signed-off mishap report and FAA-approved corrective actions. Until those documents are in place, the world’s most powerful rocket will remain a ground test article rather than a flight article.
That tension is likely to define the coming months. If SpaceX opts for a minimalist fix that addresses only the immediate engine failure, Booster 20 could see the pad sooner but carry more legacy risk into flight. If the company uses the mishap as an opportunity to fold in broader upgrades, Starship’s long-term prospects might improve at the cost of near-term delays. The FAA, for its part, will be focused on whether the Flight 12 lessons have been fully captured, documented, and engineered into the next launch attempt.
Until more technical detail emerges from the investigation, the only firm conclusion is that the pace of Starship testing is no longer set solely by how fast SpaceX can build and stack hardware. It is now equally governed by how thoroughly the company can explain what went wrong, how convincingly it can demonstrate that those issues are resolved, and how quickly regulators are satisfied that the next flight will be safer than the last.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
