SpaceX’s Starship program faces a grounding order after the Federal Aviation Administration determined that Flight 12, conducted on May 22, 2026, ended in a mishap. The company had planned to fly Starship Flight 13 no earlier than early June from its Boca Chica launch site, marking the second flight of the upgraded V3 vehicle. That timeline now depends entirely on how fast SpaceX and the FAA can close a formal mishap investigation tied to the booster’s off-nominal return during Flight 12, which saw the ship continue its trajectory to a planned splashdown in the Indian Ocean while the booster fell short of its intended flight profile.
FAA mishap ruling puts the June window at risk
The core tension for Flight 13 is regulatory, not mechanical. The FAA classified Flight 12 as a mishap and now requires a SpaceX-led investigation before any Starship vehicle can fly again. That process locks the next launch to the agency’s safety findings, meaning SpaceX cannot simply fix a part and roll back to the pad. The regulator must review corrective actions, accept them, and formally clear the vehicle for flight. No injury or property damage resulted from the Flight 12 event, according to FAA’s determination, but the absence of harm does not shorten the procedural path.
The hypothesis that the FAA will impose new telemetry thresholds for booster re-entry, potentially exceeding the V3 vehicle’s current design margins, cannot be confirmed from available evidence. The agency’s public statements describe a standard mishap investigation framework rather than specific technical demands. What is clear is that the booster experienced an off-nominal return, which means the vehicle did not follow its planned flight path during the descent phase. Whether that failure traces to software, hardware, or environmental factors has not been disclosed.
For SpaceX, the practical consequence is a race against the calendar. An early June target leaves roughly two weeks from the date of the mishap to complete an investigation, submit corrective actions, and receive FAA clearance. Past Starship groundings have stretched weeks or months depending on complexity. The V3 vehicle’s relative newness adds a layer of scrutiny, since Flight 12 was its debut and regulators have less flight data to benchmark against.
Flight 12 booster failure and ship splashdown sequence
The May 22 flight followed a split outcome. The Super Heavy booster experienced problems during its return, failing to complete the intended profile. The ship, meanwhile, separated successfully and continued on its planned trajectory toward a splashdown in the Indian Ocean. That separation of outcomes is significant: it shows the upper stage performed as designed even as the booster did not, which could narrow the scope of the investigation to booster-specific systems.
The FAA oversees the investigation, and SpaceX leads the technical review. This division of labor is standard for commercial launch mishaps. SpaceX must identify the root cause, propose fixes, and demonstrate that those fixes address the failure mode before the agency will lift the grounding. The process typically involves telemetry review, debris analysis if applicable, and engineering simulations to validate corrective measures.
Because Flight 12 was the first V3 mission, the investigation carries extra weight. Any systemic design issue found in the booster’s return systems could require changes that affect not just Flight 13 but the entire V3 production line. A narrower finding, such as a sensor anomaly or a one-off manufacturing defect, would allow a faster return to flight. The distinction between those two outcomes will determine whether the early June target holds or slips further into the summer.
Open questions blocking the Flight 13 schedule
Several gaps in the public record make it difficult to predict when Flight 13 will actually launch. The FAA has not disclosed a projected timeline for the investigation or specified what data deliverables SpaceX must submit. SpaceX has not publicly released details about its internal corrective-action plan or acknowledged what specifically went wrong with the booster’s return sequence. Without those details, the early June target is best understood as aspirational rather than confirmed.
The nature of the booster’s off-nominal return is the single most important unknown. If the failure involved the vehicle’s grid fins, engine relight sequence, or guidance software, each of those systems carries different implications for how long a fix takes and how much hardware must change. A grid fin issue might require physical replacement and re-testing. A software fault could be patched and validated more quickly. An engine relight failure sits somewhere in between, depending on whether the root cause is mechanical or related to propellant management.
Readers tracking the Artemis program, commercial crew rotations, or satellite deployment schedules should watch the FAA’s newsroom for the formal close of the mishap investigation. That announcement will be the first concrete signal of when Flight 13 can proceed. Until then, the Starship fleet stays on the ground at Boca Chica, and any missions that depend on Starship’s heavy-lift capability face schedule uncertainty. The speed of this investigation will also set a precedent for how the FAA handles future V3 mishaps, making it a test case for the regulatory relationship between the agency and SpaceX as the vehicle matures.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
