Home  /  Players  /  Starship  /  Recovery & Landing

Recovery & Landing

Tower catch, no legs, no drone ship · 3 booster catches, all pre-Block 3 · no ship catch yet · status Q3 2026

Starship has no landing legs and no drone ship. Both stages are meant to fly back to the tower that launched them and be caught by its arms. The tower count is not the shortage — the constraint is the ship’s reentry corridor and the fact that no Block 3 vehicle has been caught. This is the least-discussed critical piece of the program.

Booster catches
3
Block 3 catches
0
Ship catches
0
Legs / drone ship
None
LC-39A landings
88 /yr
Confidence
Building

Catch, not land

Every Launch Tower Is Also a Catch Tower

Starship lands where it launches, so recovery capacity grows with every pad already planned.

Starship’s recovery architecture is a tower catch: the vehicle returns to the launch site and is caught by a pair of electric actuating arms on the tower, nicknamed Mechazilla, with no landing legs and no autonomous drone ship. Because a catch happens at the launch site, landing capacity is the pad count — and the licenses already treat the two separately. LC-39A’s approval covers up to 44 launches and 88 landings a year: two recoveries per launch, one booster and one ship. Louisiana adds 10 towers. The shortage, then, is not towers.

It sits in two places that get little public attention: the ship’s reentry path, and the fact that no Block 3 vehicle has yet been caught. This page holds both. Building

Two different returns

The Booster Comes Back in Minutes; the Ship Comes Back From Orbit

The two stages pose completely different recovery problems, and only one is close to solved.

The booster flips after staging, burns back, and reaches the tower about six minutes after liftoff — a short, fixed path entirely over water. That is the tractable case, and it has been demonstrated three times. The ship returns from orbit: its ground track has to pass over a catch site, and its final reentry leg crosses land or busy airspace before the flip-and-burn to the tower. That is the hard case, has never been attempted, and drives the corridor problem below.

Recovery methods

What Has Actually Been Recovered

Three catches, all pre-Block 3; everything else is still splashing down.

Recovery methods
MethodRecordNotesRated
Booster tower catch3: Boosters 12, 14, 15First on 13 October 2024. None yet with Block 3, whose grid fins now double as the catch pointsObserved
Ship tower catch0 attemptsPad 1 rebuild adds shielding for the ship’s three sea-level Raptors during the flip-and-burn. First attempt no earlier than Flight 15Projected
Ocean splashdownGulf, Indian Ocean, PacificCurrent test practice for both stages. Ship 40 was lifted intact from the Indian Ocean aboard Boskalis ForteObserved
Barge transportStarbase → FloridaMoves finished vehicles to the Space Coast until the Florida factory opensObserved
Offshore platformsAbandoned 2023Phobos and Deimos — see belowObserved
Net-catch ship (China)1, 10 July 2026The only working sea recovery of an orbital booster — see belowObserved

The reentry corridor

The Real Constraint Is Where a Returning Ship May Fly

This is argued in FAA environmental assessments, not headlines, which is why it seems undiscussed.

The ship’s ground track has to cross a catch site, and its last reentry leg crosses land or crowded airspace. SpaceX’s proposed orbital paths cross Florida, where the FAA estimated hazard areas would affect between 10 and 200 commercial flights an hour depending on time of day. Each return corridor needs its own FAA environmental review. The Flight 14 assessment added a new reentry path back to Starbase and a contingency landing area in the northeast Pacific for Florida-to-Starbase returns — and the same review took the ship catch off Flight 14.

Tower count is not the shortage. Three things are: no Block 3 catch has been shown; each tower both launches and catches, so a recovery occupies the pad until the vehicle is cleared; and missions too energetic for a booster flyback have no downrange landing option. SpaceX answers the last with orbital refueling, which keeps boosters on short return-to-launch-site paths.

Phobos & Deimos

The Offshore Platforms That Were Tried and Dropped

Sea platforms were the original high-cadence answer. They were abandoned.

In 2021 Musk said most Starship spaceports would sit about 20 miles offshore for noise reasons. SpaceX bought two oil rigs, named them Phobos and Deimos after the moons of Mars, and began fitting a catch tower to one at Pascagoula, Mississippi. It quietly abandoned the effort and sold both rigs by 2023. Starbase Louisiana effectively replaces the concept: a remote coastline where the noise argument for going offshore no longer holds.

The net-catch alternative

China Recovered an Orbital Booster at Sea Before Block 3 Did

The counterexample to tower catch, and the only working sea recovery.

On 10 July 2026, CALT’s Long March 10B reached orbit on its first flight and its booster was caught by a hook-and-net system on a vessel in the South China Sea — China’s first orbital booster recovery and the first net recovery of any rocket. It is the only working sea recovery of an orbital-class booster, and a Chinese booster was caught before any Block 3 Super Heavy. The full Chinese program is on Chinese Counterparts.

Contested

Deliberately Not Claimed

The load-bearing uncertainties, tagged with the confidence they actually earn.

Projected

The Block 3 catch is unproven. All three catches on record were four-fin Block 1 and Block 2 boosters with separate catch hardpoints. Block 3 integrates the catch pins into the grid fins, so a fin failure and a catch failure are no longer independent. No Block 3 catch has been shown.

Building

Tower turnaround is an unmeasured constraint. One tower both launches and catches, so a catch ties up the pad until the vehicle is cleared. How fast that cycle runs is untested at any cadence.

Projected

High-energy missions have no downrange option. A booster that cannot fly back has nowhere to land under the current architecture. SpaceX bets on orbital refueling to avoid the case; a downrange platform is not planned.

Record

Provenance and Data Sources

Confidence
Observed for demonstrated catches and splashdowns — Building for turnaround — Projected for the ship catch and Block 3 catch
Status date
Q3 2026
Catches
Flights 5, 8, 11 booster catches; Flight 14 FAA assessment; Flight 15 pairing reporting
Corridor
FAA environmental assessments for LC-39A and Flight 14; over-Florida hazard-area estimates
Offshore & China
Phobos/Deimos sale (2023); CALT Long March 10B recovery (10 July 2026)
Weakest link
The unproven Block 3 and ship catches, and tower turnaround time