SpaceX scraps Starship V3 launch after last-minute tower issue

SpaceX scrubbed the first launch attempt of Starship Version 3 after multiple holds in the final minute of the countdown at Starbase in southern Texas, stopping the rocket about 40 seconds before ignition and forcing engineers to troubleshoot a problem in the launch tower.

The company said the issue involved a tower component tied to ground support equipment. Elon Musk later said the hydraulic pin holding the tower arm in place did not retract, and SpaceX signaled it could try again on Friday, May 22, 2026, if the problem was fixed quickly. The scrub came on Thursday, May 21, after the rocket had already been fully fueled on the new pad.

The flight was SpaceX’s 12th overall Starship test and the debut of the third-generation vehicle, known as V3. At roughly 408 feet, or 124 meters, the rocket is bigger and more powerful than earlier versions, and SpaceX has described it as a step toward full reusability. That makes a no-launch day part of the work, not a detour from it. In a program this complex, a scrub can reveal just as much as a flight, especially when the failure sits at the interface between the rocket, the tower and the equipment that holds everything in place before liftoff.

The planned mission was suborbital. SpaceX intended for Super Heavy booster Booster 19 to splash down in the Gulf of Mexico and for Ship 39 to end its flight in the Indian Ocean. If the launch had proceeded, it would have added another data point to a development program built around rapid iteration, from fueling and hold sequences to tower choreography and booster separation.

The stakes extend well beyond one test. NASA sees Starship as part of its future lunar landing plans under Artemis, which puts extra weight on every tanking sequence, tower check and abort decision. SpaceX said it has invested more than $15 billion in Starship development, and that it spent $3 billion on Starship-related research and development in 2025 alone.

For engineers, a late scrub is a disciplined choice in a high-risk test program. It protects hardware, preserves data, and exposes weak links before a full-scale launch pushes the system harder. In that sense, Starship’s first V3 attempt did not end the work. It narrowed the next test.