Text settings
Story text
SizeSmallStandardLargeWidth *StandardWideLinksStandardOrange
\* Subscribers only
Minimize to nav
SpaceX was more than lucky Friday, sending its 13th full-scale Starship test flight halfway around the world from South Texas to an on-target, intact splashdown in a remote section of the Indian Ocean.
Starship has made precise splashdowns before. This time, however, the ship gently tipped over and came to rest floating in a remote stretch of ocean west of Australia. Previous splashdowns ended with conflagrations, an outcome SpaceX officials have come to expect with each water landing of Starship.
The buoyant Starship looked to be in fine shape after reaching the Indian Ocean. SpaceX engineers flew drones over the vehicle to inspect its heat shield, getting their best look yet at how more than 18,000 ceramic tiles insulating the ship’s stainless steel airframe weathered the trip to space and back. The tiles withstood temperatures up to 2,600° Fahrenheit (1,430° Celsius) as Starship streaked back into the atmosphere at the end of its hour-long flight from Starbase, Texas.
Encouraged by the picture-perfect end to Friday’s flight, SpaceX is likely to take the next leap with Starship on the next launch, according to the company’s founder and CEO, Elon Musk. That would entail hurling Starship on a longer-range trajectory, perhaps into low-Earth orbit, to bring the vehicle back to the launch site. Mechanical arms on the launch tower will attempt to capture the ship as it slows to a hover. SpaceX has already done this with the rocket’s massive Super Heavy booster, which is larger and heavier than Starship itself, but comes back at a fraction of the speed.
“Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on next flight,” Musk wrote on X Friday evening.
Starship’s six Raptor engines afloat in the Indian Ocean.
Credit: SpaceX
Starship’s six Raptor engines afloat in the Indian Ocean.
Credit:
SpaceX
Hungry for data
Engineers have long identified the performance and durability of the heat shield as one of the toughest challenges for the Starship program. SpaceX’s ambition for Starship includes rapid turnarounds, and eventually multiple flights per day. If this is to be achievable, the heat shield has to be robust against the vibrations and extreme temperatures it sees during launch and reentry. It can’t be refurbished or replaced after every flight.
“This is the first time we’ve put an intact Starship in the water,” said Dan Huot, a SpaceX communications manager providing commentary on the company’s live webcast. “This is a dream scenario for the team that’s trying to get this heat shield data.”
The intact splashdown Friday also opens up the possibility for SpaceX to tow the rocket back to shore, probably somewhere in Australia, for more detailed inspections. Starship is designed for reuse, but not after exposure to salt water.
“This is so critical for refining the heat shield and everything else. The really good news is … you’re looking at a pretty intact-looking heat shield,” Huot said. “We were flying at a significantly higher dynamic pressure, so putting way more stress on this vehicle on the way uphill, and it’s sitting there in the water.”
SpaceX continued receiving signals from Starship after splashdown through the company’s Starlink satellite broadband network. A camera onboard Starship showed no signs of external damage to the vehicle’s six Raptor engines as water lapped against the lens.
Friday’s test flight was the 13th launch of SpaceX’s Starship on top of its massive Super Heavy booster, and the second flight of the latest iteration of the world’s most powerful rocket—Starship Version 3.
Starship and its Super Heavy booster lift off from SpaceX’s launch site in South Texas at 5:51 pm CDT on July 24, 2026.
Credit: Reginald Mathalone/NurPhoto via Getty Images
Starship and its Super Heavy booster lift off from SpaceX’s launch site in South Texas at 5:51 pm CDT on July 24, 2026.
Credit:
Reginald Mathalone/NurPhoto via Getty Images
The 408-foot-tall (124-meter) rocket lifted off from Starbase, Texas, a few miles north of the US-Mexico border, at 5:51 pm CDT (6:51 pm EDT; 22:51 UTC). Thirty-three methane-fueled Raptor engines on the Super Heavy booster steered the rocket east over the Gulf of Mexico and into the upper atmosphere, where the booster separated from Starship’s upper stage after burning most of its cryogenic propellant.
The only thing left incomplete on SpaceX’s checklist for Flight 13 was the controlled splashdown of the Super Heavy booster. It was supposed to relight its engines for a landing burn off the coast of Texas, simulating maneuvers required to return the booster back to the launch pad for recovery and reuse.
But some of the Raptor engines failed to restart for the landing burn, and the booster fell into the ocean at high speed. SpaceX also had trouble with the booster splashdown on the last flight in May. Friday’s flight showed some progress, but engineers have more work to do on recovering this version the Super Heavy booster. SpaceX previously recovered and re-flew Super Heavy boosters two times with the Starship Version 2 design, but not with Version 3.
“The booster successfully completed the high thrust portion of the boostback burn with all 33 engines, the first time with a Super Heavy V3, before ending the burn early,” SpaceX officials wrote in an update on the company’s website. “It attempted to relight its engines for the landing burn, with a subset successfully igniting before experiencing a hard splashdown in the Gulf.”
Success in space
Starship continued accelerating into space as the Super Heavy booster descended toward the Gulf, firing its six engines more than five minutes before beginning a half-hour coast over the Caribbean Sea, Atlantic Ocean, and South Africa.
A few minutes after engine shutdown, Starship opened its payload bay door and started deploying a stack of 20 Starlink satellites. The satellites are the first of SpaceX’s upgraded Starlink V3 model, with significant improvements in throughput and power. They are also larger and heavier than Starlink V2s, meaning they will not fit on SpaceX’s smaller, workhorse Falcon 9 rocket.
Starship released the Starlink V3s using its Pez-like deployer, tossing them overboard through a slit-like opening on the side of the spacecraft. The flat-panel satellites did not stay in space for long. They flew on the same arcing suborbital trajectory as Starship, and were designed to burn up as they fell back into the atmosphere less than an hour after launch.
In little time, SpaceX ground teams established contact with each of the satellites through radio and laser communication links, and “downloaded key telemetry” before their fiery demise. This provided engineers with their first look at the performance of Starlink V3s in space.
Powered by six Raptor engines, Starship is seen accelerating toward space Friday in this view captured by a camera on the Super Heavy booster moments after stage separation.
Credit: SpaceX
Powered by six Raptor engines, Starship is seen accelerating toward space Friday in this view captured by a camera on the Super Heavy booster moments after stage separation.
Credit:
SpaceX
With the satellite deployments complete, attention turned to a brief restart of one of the ship’s Raptor engines, something engineers forewent on the last flight. The burn lasted approximately 14 seconds, and was visible to observers in South Africa. SpaceX hailed the demonstration as “core capability for future orbital missions.” Gravity then pulled Starship back to Earth.
The next steps for Starship are getting to orbit and returning the ship to the launch site. Those achievements will give SpaceX the capability to begin launching operational Starlink V3 satellites, unlocking higher-speed direct-to-device connectivity for consumers and the US military, and the revenue to go along with it.
For NASA, an orbital flight puts SpaceX on a path toward orbital refueling. This demonstration is vital for any Starship flight beyond low-Earth orbit, including missions to the Moon in support of NASA’s Artemis program. NASA is working with SpaceX and Blue Origin to develop human-rated versions of Starship and the Blue Moon lander to ferry astronauts to and from the lunar surface.
“Excited for what will be learned from this mission,” NASA Administrator Jared Isaacman wrote on X after the launch of Flight 13. “When Starship comes online, its capabilities will be game-changing, not least of which will be ensuring we never give up the Moon again!”
SpaceX has one active launch pad in Texas, and a second Starship pad undergoing renovations there. Two Starship launch sites are under construction at Kennedy Space Center and Cape Canaveral Space Force Station in Florida. The orbital refueling demonstration will include two Starship launches, allowing the vehicles to rendezvous and dock with one another in orbit. One ship will then transfer methane and liquid oxygen propellants to the other through automated couplers.
It will take multiple refueling runs in rapid succession to refill a Starship with enough propellant to reach the Moon, requiring rapid reuse of Starships and the Super Heavy boosters at multiple launch pads. With Friday’s test flight, SpaceX seems poised to embark on the next phase of Starship’s iterative development program. It won’t be easy.
“Really critical data collected this mission on a demonstration deorbit burn for Raptor, and a first flight for the next generation Starlink satellites,” Shana Diez, SpaceX’s director of Starship flight reliability, wrote on X.
“It feels like we are ready to kick into gear on delivering payload to orbit, which I am very excited for,” Diez added. “Development vehicles are fun but at the end of the day, we are here to put things into space and I am psyched about this rocket’s game changing capabilities.”
Stephen Clark Space Reporter
Stephen Clark Space Reporter
Stephen Clark is a space reporter at Ars Technica, covering private space companies and the world’s space agencies. Stephen writes about the nexus of technology, science, policy, and business on and off the planet.
Comments
Loading comments...
Customize
Sign in dialog...
Read Original at Ars Technica →