SpaceX's Starship Flight 13 "NEVER Return" will Make History... Never seen Before! - Summary

Summary

**Summary**

SpaceX is pushing toward full reusability of its Starship system. While Flight 12 is being readied as the first operational flight of the next‑generation Starship, Flight 13 may or may not return to the launch site. The FCC filing allows three possible outcomes for Ship 40:

1. **Tower catch** – Mechazilla’s “chopstick” arms snag the vehicle mid‑air after a vertical flip, marking the first ever ship‑catch and a major step toward rapid reuse.
2. **Controlled ocean splashdown** – If conditions aren’t ideal for a catch, Starship performs a powered de‑orbit burn, re‑enters belly‑first, flips to vertical, and lands softly in the Pacific (with possible recovery afterward).
3. **No return** – The filing’s “may or may not return” wording also hints at the vehicle staying in orbit longer, though FCC rules require a de‑orbit maneuver; abandoning a 120‑ton Starship would create hazardous space debris, so a safe return is essential.

Regardless of the recovery method, Flight 13’s primary goal is to gather **real orbital data** that suborbital tests cannot provide: several hours of coast phase at ~250 km altitude to measure temperature swings, cryogenic propellant boil‑off, thermal‑control performance, heat‑shield durability, and Raptor‑engine restart capability. The mission will also test payload‑bay operations, deploy experimental Starlink satellites, and conduct small‑scale in‑space propellant transfers—key for NASA’s Artemis lunar‑landing architecture and future Mars refueling.

The return sequence involves a **de‑orbit burn** (1‑3 Raptor engines firing for seconds‑minutes), a 30‑90‑minute atmospheric re‑entry (belly‑flip maneuver protected by heat‑shield tiles and flaps), a flip to vertical, and a final landing burn to near‑zero speed. If a tower catch succeeds, it will be the first mid‑air retrieval in Starship history; otherwise, a soft ocean landing will still validate the vehicle’s re‑entry and landing systems.

SpaceX is accelerating its launch cadence: flights 1‑6 took ~2 years, while flights 7‑13 are being compressed into a single year thanks to improved Starbase production and testing infrastructure. The company is building a dual‑site strategy—manufacturing at Starbase (Texas) and launching from Pad LC‑39A (Florida) using specialized barges to move hardware across the Gulf of Mexico. Regulatory approvals allow up to 44 launches/year at LC‑39A, 25 at Starbase, and potentially 76 at a third Cape Canaveral site, giving a combined approved capacity of ~145 flights/year by 2026‑2027. Realistic expectations are 10‑20 flights in 2026, rising to 80‑150 (most likely 80‑100) in 2027 as additional pads come online.

Challenges remain: each launch consumes ~4,600‑5,000 metric tons of LOX/LCH₄ propellant, requiring hundreds of truck deliveries until on‑site air‑separation units produce LOX and LN₂ locally; each launch currently triggers airspace closures of 40 min‑2 hr, affecting hundreds of flights, though SpaceX and the FAA aim to shrink those windows to 30‑60 min as reliability improves. Overall, Flight 13 represents a critical test of Starship’s orbital performance, re‑entry, landing, and reuse concepts, bringing SpaceX closer to its vision of rapid, frequent, and fully reusable spaceflight.

Facts

1. SpaceX aims to achieve full reusability by catching the Starship vehicle with a tower.
2. Flight 12 is being prepared for launch.
3. According to an FCC submission, Starship 40 on flight 13 may or may not return to the launch site.
4. Starship 40 is already fully stacked.
5. The preferred outcome for flight 13 is a vertical capture of Starship 40 by the Mechazilla tower.
6. If captured, Starship 40 would be the first Starship to achieve a true orbital flight at ~250 km altitude.
7. After orbital insertion, Starship 40 would coast, perform a de‑orbit burn, re‑enter at ~27,000 km/h using heat‑shield tiles and four flaps, execute a flip maneuver, and attempt a powered vertical landing at Starbase.
8. Successful capture by Mechazilla would mark the first ever ship‑catch in Starship history.
9. If tower capture is not feasible, Starship 40 would follow a backup plan: a controlled re‑entry and a soft ocean landing in the Pacific, using Raptor engines for a final burn before sinking.
10. The dual‑profile approach (tower catch or ocean landing) provides flight‑13 flexibility.
11. The primary purpose of flight 13 is to gather real orbital data that cannot be obtained from suborbital tests.
12. In orbit, Starship 40 is expected to spend several hours in a coast phase collecting data on temperature swings, cryogenic propellant boil‑off, thermal‑control system performance, heat‑shield durability, and Raptor‑engine restart capability.
13. While in orbit, Starship 40 could deploy experimental Starlink satellites, test payload‑bay door operations, and conduct small‑scale in‑space propellant‑transfer tests.
14. These tests support NASA’s Artemis program and future Mars missions.
15. FCC rules require a de‑orbit maneuver and landing; leaving Starship in orbit would create ~120 t of space debris, risking Kessler syndrome.
16. The de‑orbit burn involves rotating engines forward and igniting 1‑3 Raptor engines using header‑tank fuel for a few seconds to a couple of minutes.
17. After the burn, Starship’s descent lasts 30‑90 minutes.
18. During re‑entry, Starship performs a belly‑flop maneuver; heat‑shield tiles and four flaps manage heating and stability.
19. The flip and landing burn occurs at Mach 2‑3, flipping the vehicle to vertical and igniting multiple Raptor engines to slow to near‑zero speed for landing.
20. Elon Musk has stated SpaceX will only attempt a tower catch after two perfect soft ocean landings.
21. Flights 1‑6 required roughly two years; flights 7‑13 are being compressed into a single calendar year due to improved Starbase infrastructure.
22. Planned roadmap: Flight 12 in May (debut of V3 rocket, in‑space Raptor relight).
23. Flight 13 possibly in late May per FCC documents: orbital insertion, possible early commercial Starlink VF‑3 deployment, booster recovery, and an attempted Starship catch.
24. Flight 14 could be the first full rapid‑reuse mission with both booster and Starship recovered and ready for turnaround.
25. SpaceX operates a dedicated Starship launch tower with Mechazilla‑style catch arms at PADL LC‑39A, Florida, while its primary manufacturing hub is at Starbase, Texas.
26. Two specialized barges transport fully or mostly assembled Starship vehicles and Super‑heavy boosters horizontally across the Gulf of Mexico (>1,000 nautical miles, 3‑7 days).
27. The FAA approved up to 44 Starship launches per year at LC‑39A (February 2026) with 88 total landings.
28. Starbase is currently capped at ~25 launches per year; a second dedicated catch‑and‑launch pad is expected mid‑2026.
29. SLC‑37 at Cape Canaveral has approval for up to 76 launches per year.
30. Combined approved launch capacity across the three sites is ~145 flights per year.
31. Realistic 2026 launch rates are projected at 10‑20 flights, beginning ~1 launch every 3‑6 weeks from Texas and accelerating in Q4 as Florida operations start.
32. By 2027 the target is 80‑150 launches per year, with 80‑100 being the most probable outcome.
33. Elon Musk’s long‑term vision is one launch per hour, though analysts consider this unlikely before 2030.
34. Achieving 500‑1,000 annual launches would require building 10‑20 new launch sites, ideally far from commercial air traffic.
35. Each Starship launch currently triggers airspace closures of 40 min‑2 hours, affecting 400‑600 aircraft and causing average delays of ~40 min (max up to 2 hours).
36. SpaceX and the FAA are working to shrink closure windows to 30‑60 minutes per event, similar to Falcon 9 procedures.
37. A fully loaded Starship stack consumes 4,600‑5,000 metric tons of propellant per launch (≈78 % LOX, ≈22 % CH₄).
38. Until on‑site propellant production is complete, each launch needs ~440 truck deliveries (270 LOX, 80 LN₂, 90 CH₄), totaling ~19,000 truck trips per year at the 44‑launch rate.
39. SpaceX is installing air‑separation units at each launch site to produce LOX and LN₂ on‑site, aiming to eliminate the truck‑delivery bottleneck.