SpaceX’s Starship Flight 13 successfully deployed 20 Starlink V3 satellites into orbit and executed a reentry before splashing down in the Indian Ocean, according to live mission updates from the company. The test mission, overseen at SpaceX’s Starbase facility in Texas, achieved a major milestone for thermal shield data collection even as its Super Heavy booster experienced a hard impact in the Gulf of Mexico during a separate descent.
Starship Flight 13 Launch and Ascent Timeline
The 407-foot megarocket lifted off from Pad 2 at Starbase during a 90-minute launch window, powered by 33 first-stage Raptor booster engines, according to SpaceX launch commentary led by Dan Huot. Following liftoff, the Super Heavy booster executed a hot-staging separation event from the Ship upper stage, completed a flip around, and initiated a five-engine burn for its return trip. NASA astronaut Anil Menon, a former SpaceX engineer currently aboard the International Space Station, shared views of the Starbase launch site on X prior to the flight. The mission followed multiple weather delays and a previous scrub on July 16 caused by an automated abort at T-0 when several Raptor engines failed to ignite.
Satellite Deployment and In-Space Maneuvers
Once in space, the Starship upper stage deployed 20 new Starlink Version 3 internet satellites from its payload bay door, marking the first time the V3 iteration has flown in orbit, according to mission briefings. Six of the deployed satellites carried high-resolution cameras to beam live exterior views back to Earth via the Starlink network. Following the payload release, the upper stage coasted for roughly 27 minutes before successfully igniting a single Raptor engine in an in-space maneuver test, which SpaceX noted is a critical capability for orbital insertion and departure on future missions.
Reentry and Indian Ocean Splashdown
The upper stage pushed through peak heating and maximum dynamic pressure during its descent, maintaining signal transmission via Starlink internet satellites despite plasma build-up that typically causes signal loss, according to SpaceX updates. The spacecraft ultimately achieved what Dan Huot described during live commentary as the “softest splashdown” ever recorded for the vehicle. “This is just the first time we’ve put a Starship into the water,” Huot said, adding that the water landing provided a “dream scenario” for engineers gathering heat shield data.
Pro Tip: Tracking Starship Reentry Data
SpaceX relies on live telemetry beamed through Starlink satellites to maintain communication during plasma-heavy atmospheric reentry phases, bypassing traditional signal blackout zones.
Super Heavy Booster Landing Anomalies
While the upper stage concluded its flight gently in the Indian Ocean west of Australia, the Super Heavy booster faced difficulties during its terminal descent in the Gulf of Mexico. SpaceX reported that the booster failed to light all 13 planned engines for its landing burn, causing the vehicle to hit the water with significantly more velocity than targeted. “It didn’t look like we lit all 13 engines that we were planning for that initial land and burn,” Huot stated during the post-burn assessment.
Frequently Asked Questions
What was the primary payload on Starship Flight 13?
Where did the Starship upper stage land?
The Ship upper stage completed a reentry and splashed down in the Indian Ocean, west of Australia.
Why was the launch delayed from its original July date?
The initial July 16 launch attempt was scrubbed due to a last-second engine ignition abort, followed by additional weather delays over the South Texas launch site.
Did you know? Starship Flight 13’s launch date coincided with the 57th anniversary of the Apollo 11 crew’s return to Earth in 1969.
To follow upcoming preparations for Starship Flight 14 and explore more aerospace reporting, subscribe to our newsletter or check out our complete mission archives.