The FAA has authorized SpaceX to resume Starship test flights following its investigation into the Super Heavy booster failure during the May 22 launch. SpaceX is targeting July 16 for the second V3 Starship mission.

The FAA identified two probable root causes: heat damage to propulsion components during ascent, and incorrect settings in the engine alarm system. SpaceX's own analysis was more specific. The company determined that slight asynchrony in engine startup during stage separation caused the Super Heavy booster to rotate 90 degrees off-axis, compromising the return-to-launch-site maneuver. In response, SpaceX has modified the engine startup sequence, revised the alarm thresholds, and updated the abort logic to improve engine re-light reliability during booster descent.

The May 22 flight was the operational debut of V3 Starship—a major redesign featuring a taller stack, larger propellant tanks, and upgraded Raptor 3 engines. The upper stage successfully deployed 20 satellite simulators and two modified Starlink satellites, though it did lose one of its three vacuum-optimized engines along the way. The booster failure occurred after stage separation and triggered the FAA's formal mishap investigation on May 27.

Assuming the July 16 date holds, the next launch will carry the first production run of third-generation Starlink satellites—a milestone SpaceX has been building toward as it increases bandwidth per satellite ahead of full V3 constellation deployment. Twenty V3 Starlinks are manifested, six equipped with cameras specifically to image the Starship exterior during ascent and separation. This imaging payload is a direct lesson from May: the booster rotation was only pinned down with inference rather than clear visual evidence, and SpaceX would prefer firmer data now that it is flying commercial hardware.

The return-to-flight clearance arrives seven weeks after SpaceX completed its Nasdaq listing on June 12, raising approximately $86 billion. The timing shapes how this flight will be received. A company that went public and now operates a launch vehicle central to both its Starlink revenue and its NASA Artemis moon program contract faces different stakeholder expectations after a booster loss than a private company did during earlier Starship test failures. Public shareholders and engineers parse risk and success through different lenses, and the market's appetite for the iterative, hardware-intensive philosophy that has defined Starship development will be tested in ways it was not before the IPO.

One detail worth underscoring is the difference between how the FAA and SpaceX framed the root cause. The FAA's language—"heat effects" and "erroneous alarm settings"—remains more general than SpaceX's account of a 90-degree rotation driven by asynchronous engine startup. This gap reflects regulatory scope: the FAA's mandate is to verify that safety systems and licensing conditions held, not to produce a full engineering root-cause analysis. For readers assessing whether the fix actually addresses the failure mode or only the symptoms the FAA is positioned to evaluate, that distinction carries weight.

The pattern SpaceX has followed through prior Starship booster and stage separation failures holds here: rapid mishap reporting, targeted software and sequencing corrections rather than major hardware overhauls, and a quick return to launch operations. What differs this time is the payload. Flying operational V3 Starlink satellites instead of simulators and earlier-generation units means a booster or stage failure now carries direct financial cost beyond schedule delay. If July 16 proceeds cleanly and the separation sequence performs as modified, it will signal that V3's early propulsion troubles were rooted in control logic and alarm thresholds—not deeper mechanical issues with the redesigned Super Heavy.