Last-Second Abort Rattles SpaceX

Elon musk, X.com. Twitter, SpaceX, Tesla

SpaceX aborted Starship Flight 13 just seconds before liftoff on July 16, 2026, after an engine ignition failure scrubbed what would have been the most powerful rocket’s first operational satellite deployment.

Story Snapshot

  • SpaceX aborted Starship Flight 13 at the last moment due to an engine ignition failure during the countdown window on July 16, 2026.
  • The mission was set to deploy 20 real Starlink V3 satellites — the first time operational satellites would fly on Starship.
  • Super Heavy Booster 20 had passed a full 33-engine static fire test on July 10, clearing a major pre-flight hurdle before the abort.
  • SpaceX shares dropped roughly 4% in premarket trading after the scrub was announced.

Last-Second Abort Halts Historic Mission

SpaceX called off the Flight 13 launch just seconds before liftoff during the 90-minute window that opened at 5:45 p.m. Central Time on July 16. An automatic abort triggered after an engine ignition failure was detected during the final countdown sequence. Multiple live streams from major outlets — including NASASpaceflight and the Associated Press — captured the moment the attempt was called off, with hundreds of thousands of viewers watching in real time.

SpaceX announced it was “standing down” from the attempt, a standard phrase the company uses when a launch is scrubbed for technical reasons. No immediate timeline for a new launch date was released. This kind of last-second abort is not new for the Starship program. Flight 12 also faced multiple countdown stops before eventually flying, and Flight 8 was stood down due to technical issues during its own countdown.

What Was at Stake on Flight 13

Flight 13 carried higher stakes than most prior Starship tests. The mission planned to deploy 20 Starlink V3 satellites — actual operational hardware, not test weights. Six of those satellites were equipped with cameras to inspect Starship’s heat shield during re-entry. That kind of real-world data would have helped SpaceX improve the vehicle’s thermal protection for future crewed missions. Deploying working satellites would have marked a major step from “test flight” to operational rocket.

The upper stage, Ship 40, was also supposed to relight a single Raptor engine while in space and then attempt a controlled splashdown in the Indian Ocean. Meanwhile, Super Heavy Booster 20 — powered by upgraded Raptor 3 engines — was set to attempt a soft splashdown in the Gulf of America rather than a catch by the launch tower. SpaceX plans to attempt a tower catch on Flight 14, now pushed further down the road.

Strong Prep Work, But Abort Raises Questions

In the days before the launch, SpaceX cleared several key milestones. Booster 20 completed a full 33-engine static fire test on July 10, with all engines burning for about 25 seconds. The Federal Aviation Administration (FAA) had resolved its mishap investigation from Flight 12 and issued launch clearance. Both the booster and the upper stage finished pre-flight static fire testing at Starbase, Texas. On paper, the vehicle was ready.

Despite that preparation, the abort shows that even a well-tested rocket can hit a wall at the final moment. SpaceX shares fell about 4% in premarket trading after the scrub. The company has a strong track record of working through these issues quickly — Flight 12’s countdown glitch was resolved in about a day. Engineers will now review the ignition data to find the root cause before setting a new launch date. For SpaceX and American space leadership, getting Starship flying reliably matters more than any single launch window.

Sources:

insiderpaper.com, youtube.com, space.com, spacelaunchschedule.com, usatoday.com, rocketlaunch.org, techtimes.com