Starship Flight 15 on 11/13 plans to catch both booster and ship
SpaceX’s planned Starship Flight 15 aims for a major milestone: the first attempt to catch both the Super Heavy booster and Starship upper stage at the launch site after a 22‑hour, 14‑orbit mission. Commenters weigh the technical and economic trade-offs of flying only 26 Starlink V3 satellites—about half the vehicle’s advertised payload capacity—speculating on engine performance limits, risk management, and Starlink manufacturing strategy. Broader themes include SpaceX’s growing dominance in launch services, the implications for lunar missions and government funding, and concerns about environmental impacts and future concepts like space-based data centers.
Mission plan and objectives
- Flight 15 aims for the first full recovery of an orbital-class system: catching both Super Heavy booster and Starship with the launch tower.
- Profile: ~22-hour mission, ~14 orbits at ~275 km, multiple safe abort / early deorbit options over oceans.
- Booster: first catch attempt for a Super Heavy V3; objectives include launch, ascent, hot-staging, boostback, and tower catch.
- Ship: deploy 26 Starlink V3 satellites, then perform return-to-launch-site reentry and catch, contingent on system health checks.
- Heatshield: improved tile retention and new curved tiles to reduce gap heating; dedicated Starlink satellites carry cameras to inspect the shield.
Starlink payload size and performance concerns
- 26 Starlink V3s (~52 t) is roughly half the advertised ~100 t payload, leading to questions why Starship Block 3 is flying “half loaded.”
- Proposed reasons: keeping variables stable vs Flight 14, extra margin for engine-out cases, limiting satellite loss risk, dispenser limits, Starlink V3 immaturity, or Raptors underperforming initial thrust targets.
- Some see repeated half-load flights as a worrying performance signal; others argue this is normal test-program conservatism.
- Counterpoint: even a 52 t payload makes this one of the heaviest orbital missions ever, and Starship capability is expected to grow over later blocks.
Development philosophy and program risks
- Debate over whether Starship follows Falcon 9’s “make it work, then optimize” pattern or has become an over-ambitious, slower “cathedral” project.
- Some argue partial loads and iterative engine redesigns show healthy engineering iteration; others see schedule slips and risk of under-delivery for Artemis timelines.
Market power, competition, and policy
- Concern that SpaceX could quasi-monopolize access to space and, via Starlink, satellite internet, especially as launch capacity is increasingly reserved for internal payloads.
- Others note many competing rockets are in development and argue antitrust or nationalization is unlikely or complex.
- Discussion contrasts relatively small NASA HLS payments to Starship with much larger ongoing SLS/Orion costs, and questions whether Starship truly suits lunar exploration schedules.
Datacenters in space and priorities
- Some criticize focus on space (and speculative orbital datacenters) over terrestrial clean energy and data infrastructure.
- Others reply that markets should decide viability; technical feasibility of orbital datacenters (especially cooling) is debated, with no consensus on economic sense.
Environmental and atmospheric impacts
- Questions raised about large satellite constellations, frequent launches, and satellite reentry products affecting ozone and climate.
- Participants ask for more research; detailed answers in the thread remain limited and largely inconclusive.