SpaceX is preparing to retry the 13th integrated flight test of Starship as early as Monday, July 20, after an automated abort stopped a July 16 launch attempt about one second before liftoff from Starbase, Texas. The fully stacked Starship and Super Heavy booster remained secured on the pad after several booster engines did not start during ignition. SpaceX began propellant offload operations immediately afterward and has said it will replace two Raptor engines before another attempt.[1][2]
The abort did not produce a vehicle loss or public-safety incident, but it adds another technical checkpoint to a program that is central to SpaceX’s plans for larger Starlink satellites and to NASA’s Artemis lunar architecture. Flight 13 is intended to test the second Starship Version 3 vehicle, deploy 20 test Starlink V3 satellites and gather more data on engine operations, atmospheric entry and spacecraft systems.[1][3]
An ignition abort, not a launch failure
The July 16 attempt opened during a 90-minute launch window beginning at 6:45 p.m. EDT, or 2245 UTC. During the final ignition sequence, Super Heavy’s automated systems aborted the countdown when engine performance did not meet launch criteria. Elon Musk, SpaceX’s CEO and chief engineer, said some engines did not start. Engine-status graphics shown during the company’s coverage indicated that four of the booster’s 33 Raptor engines failed to ignite; the remaining engines shut down and the vehicle stayed on the mount.[2]
That outcome matters operationally. A Super Heavy launch requires a tightly managed ignition sequence across 33 engines, and a launch commit system must determine whether the engine set is producing sufficient, balanced thrust before releasing the rocket. In this case, the system prevented an underpowered liftoff. Shana Diez, SpaceX’s director of Starship engineering, described the event as the first fully stacked Starship ignition followed by an automatic abort.[2]
SpaceX had not publicly provided a confirmed root cause for the engine-start anomaly as of July 18. Musk said two Raptor engines would be replaced before the next launch opportunity. SpaceX’s mission page lists the next attempt as early as July 20, though the schedule remains subject to vehicle work, licensing requirements and weather.[1][2]
What Flight 13 is designed to test
Flight 13 pairs Ship 40 with Booster 20, the second full Starship Version 3 stack. At roughly 407 feet, or 124 meters, tall, the vehicle is the 13th full-scale integrated Starship test flight since the campaign began in 2023. Super Heavy uses 33 Raptor 3 engines, while the Starship upper stage has six Raptors, including three vacuum-optimized engines for operation in space.[2][3]
The planned mission is suborbital. Super Heavy is expected to perform ascent and hot staging, then execute a full boostback burn before a controlled splashdown in the Gulf of Mexico. Starship is planned to continue on a trajectory across the Atlantic and splash down in the Indian Ocean about an hour after launch. Neither stage is scheduled for recovery on this flight.[3]
The upper stage has a more ambitious set of objectives:
- Deploy 20 functional Starlink V3 satellites.
- Test the satellite dispenser and associated communications links.
- Attempt an in-space relight of one Raptor engine.
- Collect further data on heat-shield performance during atmospheric entry.
- Complete a controlled Indian Ocean splashdown.[3]
The satellite deployment is a test rather than the beginning of operational Starlink service. Because the mission does not place Starship into orbit, the 20 satellites are expected to reenter and burn up around 20 minutes after deployment. Six carry cameras intended to inspect Starship’s heat shield and exterior during flight, providing imagery that could help engineers assess the vehicle after its high-energy reentry.[3]
Lessons from Flight 12
Flight 13 follows the May 22 Flight 12 mission, which debuted the Version 3 vehicle, Raptor 3 engines and Starbase’s Pad 2. Flight 12 reached its planned suborbital trajectory, but both stages experienced problems that are directly relevant to the new test.[3]
A Super Heavy engine failed during ascent. After separation, five engines did not relight during the booster’s boostback sequence, cutting that burn short and preventing the intended controlled splashdown. On the upper stage, a vacuum Raptor shut down about 40 seconds after separation, eliminating the planned in-space relight test.[3]
SpaceX also traced the booster’s off-nominal orientation after hot staging to a change in the upper-stage engine-start sequence. The sequence left Super Heavy about 90 degrees from its intended orientation at separation, complicating the booster’s subsequent flight profile. For Flight 13, SpaceX reported changes to the ship-engine startup sequence, Super Heavy hardware, and engine alarms and abort logic intended to better account for the dynamics of a 33-engine booster.[3]
The Federal Aviation Administration closed its Flight 12 mishap investigation on July 13 after accepting SpaceX’s findings and corrective actions, clearing the program to proceed under its normal launch-license and safety framework.[3] The July 16 abort is a separate event and means SpaceX must complete its own assessment before flying again.
Why the test has implications beyond Starbase
Starship is intended to become the launch system for SpaceX’s larger next-generation Starlink satellites. The company has said it aims to begin putting Starlink satellites into orbit with Starship by the end of 2026, followed by regular operational missions. Its proposed Starlink V3 spacecraft are larger than satellites currently launched on Falcon 9, making Starship’s payload volume and capacity strategically important to SpaceX’s broadband business and longer-term plans for space-based infrastructure supporting AI computing.[4]
The launch abort also drew investor attention because SpaceX is newly public. Reuters reported that SpaceX shares fell about 6% to $124.30 after the incident, below the reported $135 IPO price. The company’s stock had already fallen from a post-IPO high, meaning the reaction occurred amid a broader selloff rather than solely because of Flight 13. Chad Anderson, CEO of Space Capital and a SpaceX investor, characterized the market response as disproportionate to a precautionary abort, though that is an investor view rather than an independent engineering assessment.[4]
For NASA, the issue is schedule confidence as much as any one test result. The agency depends on a Starship-derived Human Landing System for future Artemis lunar operations and has selected SpaceX’s Starlink laser-communications technology to support Artemis III imagery from Orion.[5] Starship must still demonstrate capabilities that extend well beyond a suborbital test: reliable orbital operations, propellant transfer between vehicles, docking, refueling and ultimately an uncrewed lunar landing demonstration.
NASA’s Office of Inspector General said in a 2026 audit that Starship lander development was at least two years behind its original schedule. The audit highlighted the absence of a demonstrated vehicle-to-vehicle cryogenic propellant transfer and warned that the remaining Artemis milestones leave limited margin for additional technical failures.[6] The Center for Strategic and International Studies has similarly identified in-space cryogenic refueling and an uncrewed lunar demonstration as major outstanding readiness gates.[7]
A useful safety result, but another schedule test
The July 16 event demonstrated that Starship’s launch-abort logic can identify insufficient engine performance and hold a fully fueled vehicle on the pad. That is a meaningful safety result. It does not, however, resolve the program’s broader challenge: turning repeated test-flight lessons on engine reliability, relights, staging, reentry and operations into a dependable flight cadence.
Flight 13 is therefore more than another launch attempt. A successful mission would test revised booster systems, retry an in-space engine relight, demonstrate the Starlink V3 dispenser and return additional reentry data. A further delay or anomaly would not by itself determine Starship’s future, but it would continue to consume margin in programs that depend on the vehicle’s eventual operational maturity.
Editor’s Take
The pad hold is the outcome you want when a 33-engine booster is not meeting commit criteria: the system recognized an unacceptable start condition and kept a fully fueled vehicle on the mount. Replacing two engines may be a straightforward turnaround task, but the important unanswered question is whether the non-starts point to isolated hardware or a repeatable issue in ignition, control, or ground-interface processes.
I would watch the next attempt less for the headline of liftoff than for the quality of the booster sequence after hot staging: engine availability, boostback relights, and attitude control are the practical indicators of whether Version 3 is becoming operationally repeatable. The Starlink dispenser and upper-stage relight are valuable tests, but neither should be confused with demonstrated orbital delivery or the propellant-transfer capability NASA ultimately needs. The market may overreact to a clean abort, yet it is right to price in that Starship still has substantial reliability and cadence work ahead.
References
- SpaceX – https://www.spacex.com/launches/starship-flight-13
- Associated Press – https://apnews.com/article/starship-spacex-rocket-musk-nasa-455927b93b0fdc5512a4567a53eb3228
- Space.com – https://www.space.com/space-exploration/launches-spacecraft/spacex-targets-july-16-for-starship-flight-13-reveals-what-went-wrong-on-previous-launch
- Reuters, via KELO – https://kelo.com/2026/07/17/spacex-targets-next-week-for-another-starship-launch-attempt-as-shares-slide-on-abort/
- NASA – https://www.nasa.gov/blogs/missions/2026/07/16/nasa-taps-spacexs-starlink-to-deliver-artemis-iii-imagery-from-orion/
- NASA Office of Inspector General – https://www.oversight.gov/sites/default/files/documents/reports/2026-03/IG-26-004.pdf
- Center for Strategic and International Studies – https://www.csis.org/analysis/what-comes-next-artemis
