SpaceX aborted the 13th test flight of its Starship rocket on Thursday, July 23, 2026, after several engines failed to ignite [1], [2].
The failure halts the immediate testing of the upgraded V3 version of the spacecraft. Because this iteration of the rocket is central to SpaceX's long-term goals for lunar and Martian exploration, any delay in the flight sequence pushes back the timeline for validating the new hardware [2], [3].
The attempt took place at the SpaceX Starbase launch site in Boca Chica, Texas [1], [2]. Reports said the launch sequence progressed until the final moments when the system triggered an abort [3]. This safety mechanism is designed to prevent catastrophic failures on the pad when ignition parameters are not met [3].
This flight was designated as Flight 13 [1]. The mission aimed to test the capabilities of the upgraded Starship architecture, which includes modifications intended to increase reliability, and payload capacity [2]. The abort occurred at the last second, leaving the rocket stationary on the launch pad [3].
SpaceX has not yet released a detailed technical breakdown of why the specific engines failed to ignite. The company typically conducts a review of telemetry data following such events to determine if the issue was a software glitch or a hardware malfunction [2].
Boca Chica has seen numerous tests as SpaceX iterates on the Starship design. The company utilizes a rapid prototyping approach—building and testing vehicles quickly to learn from failures—which explains the frequency of these flight attempts [2].
“The launch aborted at the last second when several engines failed to ignite.”
The abort of Flight 13 highlights the ongoing volatility of the Starship V3 development cycle. While SpaceX relies on a 'fail fast' methodology, ignition failures at the final second indicate a need for further refinement of the engine sequencing or propellant systems. This setback may delay the certification of the upgraded vehicle for upcoming crewed or cargo missions.
