Starship V3 test flight met most objectives — Super Heavy booster was lost
- SpaceX flew the first Starship V3 test from Starbase, Texas, on May 22, completing ascent, staging, payload deployment and planned ship splashdown. - The clearest miss came during booster recovery: Super Heavy failed to relight all planned engines, made a partial boostback burn and hit the water hard. - SpaceX published Flight 12 results on its mission page; the next milestones are follow-up data review and another Starship test.
SpaceX’s first flight of Starship V3 answered several immediate questions at once. The May 22 test from Starbase, Texas, showed the upgraded ship and booster could get off the pad, separate cleanly, continue on the planned trajectory and complete a controlled upper-stage return profile. It also showed a major gap remains on the booster side, where Super Heavy was lost during its return sequence. That combination matters because Starship is built around full reusability, and the return phases are where much of the economic case has to be proven. ### What did SpaceX actually complete on this flight? At 5:30 p.m. Central time on May 22, Starship lifted off from Starbase on Flight 12, which SpaceX said was the first flight of the Starship and Super Heavy V3 vehicles, the first use of Raptor 3 engines on the system, and the first launch from Pad 2. The company said Super Heavy ignited all 33 engines at liftoff and that the mission completed first-stage ascent and hot staging. (spacex.com) SpaceX said the ship then continued to space despite losing one Raptor vacuum engine during ascent. The upper stage still reached its planned trajectory, which is a notable data point because engine-out tolerance is one of the system capabilities SpaceX has emphasized. ### Where did the booster fail? Super Heavy ran into trouble after stage separation. SpaceX said the booster performed a flip maneuver and attempted its boostback burn, but it “was unable to light all planned engines” and carried out only a partial burn that ended early. (spacex.com) The company said Super Heavy later tried to reignite for landing before making a hard splashdown in the Gulf. TechCrunch described the same sequence more bluntly: the booster’s engines did not properly re-ignite for the sustained burn needed to guide it back, and the stage tumbled into the water. (spacex.com) Reuters had reported before launch that SpaceX was not planning a pad catch on this test, but it was counting on controlled return maneuvers before splashdown. ### What did the ship do once it reached space? Starship completed one of the flight’s most visible demonstrations in space. SpaceX said the vehicle deployed 20 Starlink simulators and two modified Starlink satellites that were meant to image Starship during flight. That made the mission both a vehicle test and a test of how SpaceX could gather external imagery and data from nearby spacecraft. (techcrunch.com) During re-entry, SpaceX said Starship gathered heat shield and structural data, then performed a maneuver intended to stress the rear flaps and another banking move meant to mimic a future return-to-Starbase trajectory. The ship then executed a landing flip, landing burn and splashdown in the Indian Ocean on two engines, according to the company. ### Why is the result being described as mixed success? (spacex.com) Reuters described the flight as a key milestone after months of delays because V3 is the upgraded version SpaceX wants for more frequent Starlink launches and future NASA lunar missions. The mission checked off several high-value objectives, including ascent, stage separation, payload deployment and ship splashdown. The missing piece is return reliability for the booster. SpaceX’s architecture depends on bringing both stages back in a repeatable way, so losing Super Heavy means one of the most important validation targets remains open after the first V3 flight. That is an inference from the mission profile and SpaceX’s stated goal of a fully reusable system. ### What should watchers look for next? (wmbdradio.com) SpaceX’s next public clues will likely come from post-flight updates, telemetry discussion and the objectives it sets for the next Starship test. The company’s Flight 12 page already frames this mission as the first outing for multiple major upgrades — V3 hardware, Raptor 3 engines, Pad 2 and in-space imaging by modified Starlink satellites. Any follow-on flight will show whether the booster relight and return sequence was an isolated failure mode or a broader issue in the new V3 stack. (spacex.com) For now, the record from May 22 is straightforward: Starship made it through most of the flight plan, and Super Heavy did not make it back in one piece.