SpaceX Starship livestreams show payload, landing
- SpaceX launched Starship Flight 12 from Starbase, Texas, on May 22, as livestreams tracked the first V3 mission through payload deployment and splashdown. - SpaceX said Starship deployed 20 Starlink simulators and two modified Starlink satellites, while the booster failed its planned boostback and ended in a hard splashdown. - SpaceX’s Flight 12 page lists the mission replay and test timeline, and Starship V3 updates remain on the company’s website.
SpaceX’s May 22 Starship Flight 12 test gave livestream viewers a fuller mission profile than the title cards suggested at first glance. The company said the flight was the first outing for Starship and Super Heavy V3, the first use of Raptor 3 engines on the system, and the first Starship launch from Pad 2 at Starbase, Texas. SpaceX’s own post-flight account said the vehicle reached its planned trajectory, deployed payloads during coast, and completed a controlled reentry and splashdown in the Indian Ocean, while the Super Heavy booster failed to complete its return profile. ### Which parts of the livestream titles were backed up by SpaceX’s post-flight account? SpaceX said on its Flight 12 page that Starship “successfully deployed all 20 Starlink simulators and two modified Starlink satellites that imaged Starship in space.” That means the payload language used across YouTube streams was tied to a real test objective, not just generic launch-show framing. Next Spaceflight, which tracks launch manifests and mission notes, described the upper-stage objectives before flight as deployment of 22 Starlink simulators and imagery of the heat shield by the final two satellites. (spacex.com) After launch, it updated the mission notes to say the in-space relight was canceled, but the rest of the mission continued. ### What actually happened to the booster during the landing phase? (spacex.com) SpaceX said Super Heavy ignited all 33 Raptor 3 engines at liftoff, but the return sequence broke down after stage separation. The company said the booster “was unable to light all planned engines” for boostback, performed only a partial boostback burn, and later experienced a “hard splashdown” in the Gulf of America after attempting its landing burn. (nextspaceflight.com) Next Spaceflight’s mission summary matched that broad outline, saying the booster failed to properly ignite for boostback, attempted a downrange landing burn, and crash-landed in the ocean. Livestream coverage that emphasized a propulsive landing maneuver was therefore consistent with an attempted landing sequence, but not with a full booster recovery. ### Did the ship itself complete the landing-style maneuvers viewers were watching for? (spacex.com) SpaceX said Starship lost one Raptor vacuum engine during ascent but still achieved its planned trajectory. The company then said the ship re-entered Earth’s atmosphere, gathered heatshield and structural data, performed a landing flip and landing burn, and splashed down in the pre-planned zone in the Indian Ocean on two Raptor engines. (nextspaceflight.com) The wording matters because SpaceX described a controlled end-of-flight sequence for the ship, not a pad landing or catch. The mission page says the ship used its four flaps to guide itself to the target zone before the burn and splashdown. ### Why was this test labeled V3 so prominently across streams? SpaceX said on May 12 that Starship V3 incorporated changes to both the ship and booster, including redesigned grid fins, a new integrated hot stage, a redesigned fuel transfer tube, and other propulsion and thermal-protection changes. (spacex.com) Flight 12 was the first test of that configuration and the first launch from the new pad, which explains why independent streams highlighted “Starship V3” as a headline item. SpaceX also said the modified Starlink satellites on Flight 12 were meant to image Starship in space. Next Spaceflight said those payloads were intended to help test methods for assessing heat-shield condition ahead of future return-to-launch-site missions. That description is from the tracking site, not a SpaceX quote, but it aligns with the company’s statement that Flight 12 gathered heatshield data during reentry. (spacex.com) ### So what should viewers take from the “payload and landing” framing? May 22’s mission record shows the livestream framing captured two real parts of the test: payload deployment by the ship and propulsive landing maneuvers by both stages. The outcome was mixed. SpaceX said the ship completed deployment, reentry, landing flip, landing burn and splashdown, while the booster missed its planned return profile and ended in a hard splashdown. (nextspaceflight.com) SpaceX’s next public reference points are already posted on its website. The company’s Flight 12 page carries the replay and event timeline, and its May 12 Starship V3 update lays out the hardware changes that future tests will continue to exercise. (spacex.com)