Technical telemetry reviews from SpaceX engineering teams regarding the Super Heavy guidance anomaly, followed by scheduled orbital return maneuvers for Ship 42 and continued flight testing iterations at the Boca Chica facility.

Image: courtesy of Thenextweb
Why SpaceX Aborted Its Starship Booster Catch on Flight 15 — And What Orbit Still Proves
SpaceX launched Starship Flight 15 from Starbase, Texas, on November 13, 2026, executing a successful orbital insertion for Ship 42 while aborting the planned mechanical tower catch of its Super Heavy booster due to a guidance, navigation, and control anomaly.
Outlook
Background
Flight 15 represented an ambitious operational profile designed to test both satellite deployment via 26 Starlink V3 units and complete full-stack recovery. While the upper stage successfully entered a low Earth orbit at roughly 170 miles altitude, the Super Heavy booster experienced an autonomous abort sequence near the final descent phase, redirecting away from the launch tower toward a controlled self-destruction in the Gulf of Mexico.
See also
Precedents
SpaceX has historically treated test flights as empirical data collection exercises rather than flawless demonstrations. The company routinely pushes hardware parameters until structural or software limits trigger autonomous safety mitigations, using failures in specific subsystems like guidance and control to harden subsequent vehicle blocks.
The split outcome of Flight 15 demonstrates the complex reality of iterative aerospace development: upper-stage orbital mechanics and lower-stage precision recovery operate under vastly different technical thresholds. While missing the tower catch prevents an immediate double-catch milestone, the successful orbital insertion of Ship 42 confirms that the core propulsion and staging architecture remains sound under real flight stresses.
Scenarios
AnalysisSpaceX engineers could isolate the guidance, navigation, and control anomaly to software-level filtering and clear subsequent boosters for a tower catch attempt on Flight 16. Alternatively, hardware sensors may require physical redesigns, introducing delays to the broader cadence of full-stack reuse.
Timeline
Frequently Asked Questions
Discussion
Be the first to share your thoughts.