Who: SpaceX’s first Starship V3 test flight (Flight 12). When: launched May 22, 2026, with liftoff around 6:30 p.m. EDT (2230 GMT) and splashdown events late that evening. Where: launch from Starbase, Texas; upper-stage splashdown in the Indian Ocean west of Australia and booster splashdown in the Gulf of Mexico. What: Ship 39 deployed 22 dummy Starlink satellites, experienced an engine anomaly during ascent, completed reentry and performed a planned water landing that ended with the upper stage falling over and exploding on impact.
Key takeaways
- Flight 12 was the first Starship launch of 2026 and the debut of the redesigned Starship V3; the mission profile lasted roughly 65 minutes from liftoff to upper-stage splashdown.
- Ship 39 deployed all 22 dummy Starlink satellites, including two experimental ‘Dodger Dog’ satellites carrying lights and cameras to image the vehicle in flight.
- Telemetry showed at least one engine offline early in ascent for both stages: one of 33 first-stage Raptors registered out and the upper stage reported one engine out during ascent; teams continued the mission within analyzed trajectory bounds.
- The Super Heavy booster did not complete its boost-back burn and made an uncontrolled splashdown in the Gulf of Mexico; no at-pad recovery was planned for this flight.
- Ship 39 survived peak reentry heating with no visible heat-shield burnthrough, executed banking and flip maneuvers and conducted a landing burn using two of its landing-capable engines before capsizing and exploding on splashdown.
- SpaceX opted to forgo an in-space Raptor relight experiment on this flight; mission controllers cited trajectory and engine-out analyses in their decision.
- Pad 2 performed propellant loading and preflight operations, including a wet dress rehearsal; SpaceX reported faster prop load rates on Pad 2 compared with Pad 1.
Background
Starship Flight 12 marked the first flight of SpaceX’s Version 3 Starship, a significant evolution intended to increase payload capacity and to advance the vehicle toward NASA Artemis lunar lander certification. V3 incorporates larger tanks, Raptor 3 engines on the booster, and other systems-level changes intended to improve performance and turnaround. The vehicle returned to flight after a seven-month gap since Flight 11 in October 2025, a pause during which SpaceX completed upgrades and pad modifications.
Starship is central to multiple high-priority programs: an eventual lunar lander for NASA’s Artemis architecture, bulk delivery of Starlink satellites, and long-term plans for point-to-point and deep-space missions. SpaceX built a new Pad 2 at Starbase meant to speed fueling and enable quicker booster handling; teams emphasized that many systems on this flight were being exercised for the first time. Given those stakes, Flight 12 was treated as a high-value test focused on demonstrating new hardware and procedures rather than recovering both stages to the pad.
Main event
Fueling and countdown proceeded through May 22 with SpaceX declaring the team ‘go’ for prop load and a launch window opening at 6:30 p.m. EDT (2230 GMT). Liftoff occurred as planned; observers and SpaceX commentators noted one engine on the first stage failed to perform nominally during ascent but the booster continued to push the vehicle on a trajectory within preflight limits. Stage separation occurred and Ship 39 reached space.
After separation, the Super Heavy booster failed to complete its boost-back burn and was not recovered; it impacted the Gulf of Mexico in an uncontrolled splashdown. Ship 39 coasted in space, opened its payload door and deployed all 22 dummy Starlink satellites more quickly than on prior flights. The two ‘Dodger Dog’ units illuminated and attempted to image the Starship heat shield as they were released.
As Ship 39 reentered, SpaceX reported it passed peak heating and executed aerodynamic banking and attitude-control maneuvers. The vehicle performed a flip and a landing burn relying on two landing-capable engines; mission visuals and commentary showed the upper stage surviving reentry with no obvious heat-shield breach. The Ship then capsized and exploded as it impacted the Indian Ocean, a result SpaceX had not planned to recover the upper stage from.
Analysis & implications
Technically, Flight 12 delivered several objectives: a full payload deployment of 22 test Starlinks, demonstration of Pad 2 fueling and countdown operations, and a suborbital reentry profile that tested thermal protection under high heating loads. Those successes matter for iterative development: consistent payload deployments and an apparent intact heat shield during reentry reduce near-term thermal-protection risk for future, higher-stakes flights. The faster deployment cadence on V3 may improve Starlink mass-launch economics if repeated reliably.
The engine anomalies underline the developmental nature of Starship. Loss or degradation of one engine on either stage is not unexpected in flight test, but it constrains margins and forces trajectory and systems teams to adjust in real time. SpaceX’s decision to continue the mission with one engine out, and to skip an in-space relight demonstration, reflects a risk-managed approach: prioritize primary mission objectives when margins are reduced rather than pursue higher-risk experiments.
Programmatically, the uncontrolled booster splashdown in the Gulf highlights recovery and range-safety tradeoffs while SpaceX continues to refine boost-back and landing sequences. Until pad capture and routine booster returns are achieved, the company will rely on planned water landings for some tests. For NASA partners, Flight 12 supplies incremental evidence about Starship’s systems performance but does not change the need for additional qualification flights before human-rating or Artemis lander certification.
Comparison & data
| Item | Flight 11 (Oct 2025) | Flight 12 (May 22, 2026) |
|---|---|---|
| Upper-stage payload | Dummy Starlinks (varied) | 22 dummy Starlinks (incl. 2 Dodger Dogs) |
| Upper-stage reentry | Reentry with burnthrough observed | Passed peak heating; no visible burnthrough |
| Booster engines | 33 Raptors (varied performance) | 33 Raptors; 1 engine out during ascent |
| Mission duration (to splashdown) | ~1 hour | ~65 minutes |
The table contextualizes Flight 12 against the prior flight: Flight 12 carried more dummy payloads and demonstrated improved payload deployment speed. Observers should treat single-flight comparisons cautiously because configurations and flight objectives change between tests; nevertheless, the absence of visible heat-shield penetration on this flight is a noteworthy step forward.
Reactions & quotes
SpaceX public affairs and on-air commentators framed the flight as a controlled, informative test despite anomalies. They emphasized mission objectives completed and lessons learned for future flights.
“We are in on a trajectory that we had analyzed, and it’s within bounds,”
Dan Huot, SpaceX spokesperson (live commentary)
In post-flight commentary from mission coverage, analysts and editors highlighted the expected nature of the upper-stage outcome and the value of the data gathered.
“SpaceX never intended to land and recover the Ship 39 upper stage; it executed planned maneuvers and then fell over and exploded as expected,”
Tariq Malik, Editor-in-Chief (coverage summary)
Unconfirmed
- Any latent structural damage to Ship 39’s heat shield beyond visible imagery remains under analysis and has not been independently verified.
- The long-term durability impact of the reported ascent engine-out event on future Raptor cycle life is still unknown and under review by SpaceX engineers.
- Announcements about commercial crewed Mars flyby missions mentioned around the launch are separate proposals and have not been publicly confirmed as funded, scheduled missions by independent agencies.
Bottom line
Flight 12 advanced SpaceX’s V3 development path: it validated rapid payload deployment, exercised Pad 2 operations and supplied high-value reentry and thermal data after a full suborbital profile. The loss of a first-stage engine and the planned non-recovery of the upper stage confirm that risks remain, but the mission returned actionable engineering information that will inform subsequent flights.
For stakeholders — from Starlink operations to NASA planners — the flight is a mixed but generally constructive outcome. Continued, iterative testing remains necessary before Starship can be relied upon for crewed lunar landings or routine Starlink mass launches; Flight 12 tightened some technical unknowns while leaving others for follow-up tests.
Sources
- Space.com live coverage (media coverage and live reporting)
- SpaceX official website and livestream (official mission commentary and media)
- SpaceX posts (company social updates and mission status)