Starship Finally Stuck Its Landing — Its Booster Didn't
SpaceX's Starship Flight 13 on July 24, 2026 achieved the first-ever controlled intact upper-stage splashdown without exploding, but the Super Heavy booster failed its landing burn and hit the Gulf hard, with neither vehicle recovered.

- 1Flight 13 launched July 24, 2026 after a scrubbed July 16 attempt caused by four of 33 engines failing to ignite.
- 2The Starship upper stage achieved the first controlled intact splashdown in the Indian Ocean without exploding and survived tip-over for the first time.
- 3The Super Heavy booster failed to complete its offshore landing burn and struck the Gulf of Mexico at high speed.
- 4The upper stage deployed 20 operational Starlink V3 satellites and lost only a few ceramic tiles during reentry.
- 5Neither stage was physically recovered or reused; the upper stage met its stated splashdown objective while the booster did not achieve a controlled landing.
The Full Investigation
7 sections · 8 min read
Confirmed facts and attributed reporting read normally; only contested, unverified, or speculative sentences are highlighted. Hover any sentence for its grade and sources.
A test program that had just been cleared to fly again
SpaceX builds and flies Starship, the largest launch vehicle it has developed, as a two-part machine: a Super Heavy booster with 33 Raptor engines at the base, and an upper stage — the Starship itself — that carries the payload and is meant to return from space. The company's stated ambition is full and rapid reusability, meaning both parts fly, land, and fly again.
The flight examined here did not happen in isolation. Two months earlier, on May 22, 2026, Flight 12 ended with the booster failing during its return and striking the Gulf of Mexico at high speed. That failure drew the Federal Aviation Administration, the U.S. regulator for commercial launches, into a formal mishap investigation, and the agency grounded the vehicle while it worked. On July 13, 2026, the FAA closed that investigation and cleared Flight 13 to proceed.
As of the July 24 launch, Wikipedia counted 13 Starship flights with eight successes and five failures, though it does not specify whether those tallies measure whole missions or individual stages. That ambiguity matters for how any single flight gets scored.
The most recent flight was Flight 13, launched July 24 after a scrubbed first attempt
SpaceX's most recent Starship test as of early August 2026 was the 13th integrated flight, and getting it off the ground took two tries. The first attempt, on July 16, was aborted at ignition. SciNews reported a hold on the booster just as the Raptor engines began to light. Both SpacePolicyOnline and Wikipedia independently reported the underlying reason: four of the 33 engines failed to ignite. Scientia Plus went further, attributing the failure to moisture freezing in the liquid-oxygen turbopumps and reporting that six engines were replaced — details that rest on that single outlet.
The successful launch came eight days later. On July 24, 2026, all 33 Raptor 3 engines fired on the Super Heavy first stage. The date is about as solid as anything in this report: four independent sources place the launch on July 24, and the apparent one-hour gap between the reported times — 6:51 pm Eastern and 22:51 UTC — match exactly allowing for Eastern Daylight Time (UTC-4). The vehicle flew from Starbase's second launch pad with Booster 20 and Ship 40.
The flight carried a real payload, not a dummy. Three independent sources agree the upper stage deployed 20 operational Starlink V3 satellites, with no variation in the count. On this point the record is unusually clean.
Open: The moisture-freezing root cause of the July 16 abort and the reported six-engine replacement rest on a single outlet and lack independent or official confirmation [C-011].
The upper stage survived intact for the first time; the booster did not
The headline achievement of Flight 13 concerns the upper stage, and here the evidence converges strongly. Three independent sources agree that the Starship splashed down intact in the Indian Ocean, roughly an hour after liftoff, without exploding. SpacePolicyOnline framed this as a genuine surprise: on prior flights, residual fuel caused the vehicle to burst into flames after tipping over, but this time it stayed intact and floated. Wikipedia adds that surviving the tip-over was itself a first, and that it let SpaceX image the heat shield, flaps and engine bay. Ars Technica reported that only a few ceramic tiles were lost and that the heat shield protected the vehicle through a controlled descent.
One caution belongs alongside all of this. A controlled, intact splashdown is not a recovery. The vehicle splashed down and was not retrieved or reused. What the flight demonstrated is controlled return and survival — the precondition for reuse, not reuse itself.
The booster is where the flight fell short. SpaceX's stated objective for the Super Heavy was to execute a landing burn at an offshore point in the Gulf, not a tower catch. It failed to complete that burn cleanly and hit the water hard. Beyond agreeing that the booster came down hard, the sources do not tell the same story about how many engines lit — a discrepancy examined in the next section.
Open: Whether the booster's hard splashdown was expected within test tolerances or represents a landing-burn failure is not resolvable from the available sources, since the only statement of the booster's objective comes from a single outlet [C-014].
The engine count on the booster's landing burn — and the failures that recurred
The clearest unresolved fact in this flight is a number: how many of the booster's engines actually lit for the landing burn. SpacePolicyOnline reported that 8 of the 13 engines meant to relight ignited before the stage hit the water hard. Scientia Plus and Wikipedia tell it differently — 10 of 13 started, then dropped to 5. These cannot both describe the same burn the same way. The analyst found no source offering the telemetry needed to reconcile them; one plausible reading is that the two accounts capture different moments in the sequence, an initial ignition count versus a sustained-operation count, but the evidence does not confirm this. Either way, every source agrees the booster lost thrust and impacted hard.
That outcome echoes Flight 12. In May, the Super Heavy's engines began dropping offline during the boostback burn, the stage lost the thrust it needed to reverse course, and it struck the Gulf at high speed. SPACE AFFAIRS reported three engines lost at liftoff and a boostback burn that ran too short. The FAA's own investigation named the two most probable root causes: heat effects on propulsion components during ascent, and erroneous engine alarm system settings. Space Daily separately reported one engine shutting down about a minute and 42 seconds into ascent and an upper-stage engine cutting out early, though those specific timings come from that single source.
The thermal protection system drew scrutiny even amid the upper stage's success. Ars Technica, examining SpaceX's own drone footage of the floating vehicle, described notable white streaks across the heat shield that all appeared to originate at the boundaries between tiles — a pattern suggesting hot gas may have penetrated those seams — along with cracked tiles and broken edges. The regulatory record notes real-world disruption as well: during Flight 12, the FAA counted six departure delays and five airborne holding events, though no diversions, and cited analysis that enlarged hazard areas could affect more than 13,000 commercial aircraft operations a year.
Open: No source provides the booster telemetry that would settle whether 8 engines lit, or 10 dropped to 5, during the Flight 13 landing burn [C-005][C-010].; Whether Flight 12's ascent engine failures numbered one or three is not resolved between Space Daily and SPACE AFFAIRS [C-022][C-032].
Does the outcome meet anyone's definition of a 'successful landing'?
The word 'landing' carries the whole dispute. The available statements of what SpaceX set out to do come almost entirely from a single outlet, SciNews, which reported that the upper stage's objectives were to deploy 20 Starlink satellites, relight a single Raptor in space, and make a controlled entry and splashdown in the Indian Ocean, and that the booster's objective was a landing burn at an offshore Gulf point rather than a tower catch. On those stated terms, the upper stage met its goals and the booster fell short of a controlled landing burn.
Measured against the program's broader ambition, the picture is harder. Full and rapid reusability requires vehicles that land and fly again, and no vehicle on Flight 13 was recovered. Scientia Plus reported a further upper-stage milestone — the longest in-space Raptor relight to date, about 14 seconds, around 39 minutes into the flight — but that figure rests on one source.
The scoring problem is structural. Flight 12 had a controlled ship splashdown but a booster failure; Flight 13 had a ship success but a hard booster splashdown. Wikipedia's tally of eight successes in 13 flights does not say whether it counts whole missions or individual stages, so it cannot cleanly settle whether Flight 13 belongs in the success column. The honest answer is that 'success' depends entirely on which yardstick — stage objective, whole mission, or eventual reuse — is applied.
Open: No official SpaceX mission-success criteria document is in the record; the stated objectives all trace to a single outlet [C-014][C-015].; Wikipedia's success/failure tally does not define whether it measures full missions or individual stages, leaving the historical scoring method unresolved [C-016].
Competing readings of what Flight 13 proved
The evidence supports several explanations at once, and they pull in different directions on the central question.
One reading holds that Flight 13 marked a real breakthrough for the upper stage. On this account, the first-ever controlled intact splashdown without explosion, the survival through tip-over, and the minimal tile loss together demonstrate a controlled orbital-vehicle return — the milestone that makes iterative improvement possible. The strongest support is that three independent origins converge on the intact splashdown, and the count of deployed satellites is uncontested. Nothing in the claim set contradicts the intact-splashdown finding itself.
A second reading holds that the booster landing was a partial failure that repeats a pattern. The Super Heavy came down hard, just as it did on Flight 12. What weighs against calling this a plain failure is the reported objective: SciNews describes the booster's aim as an offshore landing burn, not a recovery. The discriminating evidence — telemetry showing the exact ignition sequence and a stated acceptable engine count — is absent, so this reading stays plausible rather than settled.
A third reading concerns durability. Even on a flight the upper stage survived, Ars Technica's footage analysis documents cracked tiles and apparent hot-gas penetration at tile seams, and former NASA engineer Dan Rasky is reported to warn that the current thermal protection system is a dead-end for missions requiring rapid reuse. That warning is labeled speculative because it is a prediction, and it is directly contradicted by the same flight's low reported tile loss. A tile-by-tile damage map from a full post-flight inspection would discriminate between the two, and none is in the record.
The explanations are not mutually exclusive. The upper-stage success, the booster shortfall, and the open question about thermal durability can all be true of the same flight.
What the evidence forces us to conclude
The evidence forces a split verdict, not a single one. On the upper stage, the conclusion is firm: Flight 13 achieved a controlled, intact splashdown in the Indian Ocean without exploding, a documented first, corroborated across three independent sources. On the booster, the conclusion is equally firm in outcome even where it is uncertain in detail: the Super Heavy failed to complete a controlled landing burn and struck the Gulf hard. The exact engine count remains genuinely contested, and no source supplies the data to resolve it.
On the question the topic actually poses — did SpaceX successfully land Starship — the answer the evidence permits is: no vehicle was landed or recovered in the physical sense, but the upper stage did achieve a controlled return that met its stated ocean-splashdown objective. Calling this a 'landing success' requires accepting a definition centered on controlled return rather than retrieval and reuse; calling it a failure requires ignoring a documented first. Both framings are defensible, which is why the honest characterization is mixed.
One caution the evidence itself demands: much of the framing that casts the flight as a triumph, and much that casts it as a failure, is promoted by parties with stakes. SpaceX, which needs continued regulatory approval and investor confidence, has an interest in the breakthrough framing. The forward-looking claims — that Flight 14 could fly by the end of August as a first orbital and tower-catch attempt, and that the current heat shield is a dead-end — are both labeled speculative here and should be read as predictions, not findings. What is not speculative is that the upper stage came home intact and the booster did not.
Why it matters
SpaceX's Starship is central to plans for large satellite constellations and future crewed missions, and its progress toward reusability shapes launch economics for the whole industry [C-008][C-030]. The flight also carries public-safety weight: Flight 12's booster failure triggered an FAA grounding and mishap investigation, and the agency's analysis links Starship operations to thousands of potentially affected commercial flights each year [C-021][C-023][C-024]. How a flight like this is scored — breakthrough or repeated failure — directly influences regulatory clearance for the next attempt [C-025].
- No independent engineering assessment or official SpaceX telemetry corroborates the granular technical details — most rest on single sources, and much of the flight's granular reporting depends on lower-tier outlets.
- Whether SpaceX intends and can execute the shift to physical recovery and reuse — including the reported Flight 14 orbital and tower-catch plans — remains an unverified prediction [C-013].