The FAA has cleared SpaceX to resume Starship test flights, closing the investigation into the Super Heavy booster failure from the May 22 launch TechCrunch. SpaceX says the next flight, the second launch of the V3 Starship, could come as soon as July 16.

The FAA's determination points to two probable root causes: heat effects on propulsion system components during ascent, and erroneous settings in the engine alarm system TechCrunch. SpaceX has separately described the mechanism in more granular terms, attributing the failure to slight differences in engine startup on the ship during stage separation, which caused the Super Heavy booster to rotate 90 degrees in the wrong direction SpaceX. The company has since modified the engine startup sequence, engine alarm systems, and abort logic, aiming at more reliable re-light performance during the booster's return-to-launch-site maneuver.

The May 22 flight was the debut of the V3 Starship architecture, a substantial redesign over V2 with a taller stack, larger propellant tanks, and updated Raptor 3 engines. The upper stage on that flight managed to deploy 20 satellite simulators along with two modified Starlink satellites, but lost one of its three vacuum-optimized Raptor engines in the process TechCrunch. The booster failure occurred separately, after stage separation, and prompted the FAA to order a formal mishap investigation on May 27 Reuters. SpaceX subsequently submitted its mishap report for FAA review SpaceX, a process that under current commercial launch licensing rules must close before a return to flight is authorized.

Assuming the July 16 target holds, the upcoming mission will carry the first third-generation Starlink satellites, a payload class SpaceX has been building toward as it scales bandwidth per satellite ahead of broader V3 constellation deployment. Twenty V3 Starlinks are manifested for the flight, six of which carry cameras specifically to photograph the Starship exterior during ascent and separation SpaceX. That imaging capability is a direct response to the diagnostic gap exposed in May: without clear external visual data on engine startup behavior at separation, isolating a 90-degree booster rotation to a specific propulsion anomaly required more inference than SpaceX would prefer for a vehicle now flying with commercial payload obligations attached.

This return-to-flight authorization lands seven weeks after SpaceX completed a Nasdaq listing on June 12, raising close to $86 billion in the process TechCrunch. The timing is not incidental to how this flight will be read. A now-public company with a launch vehicle central to both its Starlink revenue stream and its NASA Artemis lunar lander contract carries a different burden of proof after a booster loss than a privately held one did during earlier iterative failures in the Starship program's history. Public shareholders parse "successful test" and "anomaly" differently than engineers do, and the market's tolerance for repeated hardware-rich iteration, the philosophy that has defined Starship development since its earliest hops, will be tested in a way it wasn't before the IPO.

Worth flagging: the FAA's own root-cause language — "heat effects" and "erroneous alarm settings" — is notably less specific than SpaceX's account of a 90-degree rotation triggered by asynchronous engine startup at separation. That gap between regulator and operator framing is not unusual in mishap investigations, where the FAA's mandate is to confirm public safety systems functioned and licensing conditions were met, not to produce full engineering root-cause analysis. But for a reader trying to assess whether the fix addresses the actual failure mode or merely the symptoms the FAA is equipped to evaluate, it is a distinction that matters.

The broader pattern here is consistent with how SpaceX has approached booster and stage separation failures on prior Starship flights: rapid mishap reporting, targeted software and sequencing fixes rather than major hardware redesigns, and a fast return to the pad. What is different this time is the payload risk profile. Deploying operational V3 Starlink satellites, rather than the simulators and modified prior-generation units flown in May, means a booster or upper-stage failure now carries direct commercial cost beyond program schedule slippage. If the July 16 flight proceeds and the booster separation sequence performs as modified, it will be the clearest signal yet that V3's early propulsion issues were sequencing and alarm-threshold problems rather than a deeper mechanical fault in the redesigned Super Heavy architecture.