Starship V3

· systems · Source ↗

TLDR

  • SpaceX reveals Starship V3 and Super Heavy V3 with Raptor 3 engines, new Pad 2, and full-reuse architecture targeting in-space propellant transfer and orbital data centers.

Key Takeaways

  • Raptor 3 sea-level thrust increases to 250 tf (from 230 tf); mass drops to 1,525 kg from 1,630 kg; ~1 ton vehicle-level mass savings per engine.
  • Super Heavy V3 moves from four to three larger grid fins, integrates a hot stage replacing the single-use interstage, and adds two separated quick disconnect propellant points.
  • Fuel transfer tube redesigned to Falcon 9 first-stage scale, enabling simultaneous startup of all 33 engines and faster flip maneuvers.
  • Starship gains ship-to-ship docking drogues, propellant transfer connections, 100% vacuum-jacketed header feed, and a cryogenic recirculation system for long-duration spaceflight.
  • Launch tower chopstick actuators switch from hydraulic to electromechanical; new bidirectional flame diverter eliminates post-launch ablation refurbishment on the mount.

Hacker News Comment Review

  • Commenters flag heat shield reliability as the conspicuous omission: V3 covers engine shroud deletion and tile upgrades but says nothing about the reentry tile failures seen in V2 testing, raising doubts about near-term crewed or return missions.
  • The SpaceX-xAI merger section generated the most skepticism; the orbital data center and “sentient sun” framing struck commenters as investor-pitch prose grafted onto an otherwise credible engineering document.
  • Tile complexity drew a direct Shuttle comparison: hex tiles of varying sizes across tail fin assemblies worry observers who remember how refurbishment became the long pole in Shuttle reuse.

Notable Comments

  • @Fordec: notes heat shield failures are V2’s biggest unresolved hurdle and suggests V3 roadmap prioritizes payload-up over return reusability.
  • @randallsquared: warns tile complexity risks repeating Shuttle refurbishment bottlenecks, calling it “a Shuttle re-run.”

Original | Discuss on HN