Starship's 13th test flight didn't get off the ground on 16 July 2026. With the countdown inside its final seconds, onboard telemetry showed four of the Super Heavy booster's engines failing to ignite, and the flight computer pulled the abort before the vehicle left the pad.
SpaceX founder Elon Musk confirmed the automatic abort was triggered by the ignition failure. Two Raptor engines are being swapped out, and the company is now targeting a retry on 23 July at 10:45pm UTC from Starbase, Texas. If that timeline sounds familiar, it should: Starship dates have a well-documented habit of slipping, and this is the vehicle's third scrub or abort cycle in 2026 alone. Treat 23 July as the earliest plausible date, not a confirmed one.
It's worth separating the abort from a failure. An automatic system that catches a bad engine before ignition and stops the flight is doing exactly what it's designed to do. The alternative, a Super Heavy booster with four dead engines actually lifting off, is a considerably worse outcome. Boring as it sounds, the computer noticing a problem and stopping is a genuine safety win, not a story about SpaceX getting something wrong.
What makes Flight 13 more than a routine test is the payload and the objective. Once it flies, Starship is carrying 20 Starlink V3 satellites, the first time the vehicle has attempted to deploy operational satellites rather than mass simulators. Six of those satellites are fitted with cameras specifically to monitor Starship's heat shield during ascent and re-entry, and several tiles have deliberately been left off or painted white to act as tracking targets.
That data matters more than the delay. Starship's heat shield has been the single biggest unresolved question standing between the vehicle and routine cargo and crew flights, including the lunar lander variant NASA is counting on for Artemis III. A clean Flight 13, whenever it actually happens, would be a bigger milestone than the exact date it launches on.