Starship Flight 13 was the first flight in the program that looked like more than a rocket test. The ship carried functioning satellites, exercised them in space, restarted an engine, and reached the Indian Ocean intact enough for engineers to keep receiving imagery after splashdown.
None of that makes Starship operational. The Super Heavy booster still missed its planned landing profile, the satellites were short-lived test articles, and the vehicle did not enter orbit. But Flight 13 moved the program onto a more useful question: can SpaceX turn individual demonstrations into repeatable payload delivery and recovery?
Flight 13 at a glance
- Payload: Starship deployed 20 functioning third-generation Starlink satellites for a short suborbital test.
- Ship: The upper stage restarted a Raptor engine in space and survived reentry before splashing down intact.
- Booster: Super Heavy missed its planned landing profile after only some engines relit for the final burn.
- Next test: SpaceX may attempt an orbital flight and tower catch, subject to its review of the Flight 13 data.
Starship Flight 13 carried a real payload experiment
The July 24 flight was the second launch of the upgraded Starship V3 configuration. After launch from Starbase, Texas, the ship deployed 20 functioning Starlink V3 satellites—the third generation of SpaceX’s broadband spacecraft—on the same suborbital trajectory. SpaceX used their roughly 20 minutes in space to deploy solar arrays and antennas, establish radio-frequency and laser links, and download telemetry before the satellites reentered.
These were not operational satellites entering service. They were deliberately short-lived test articles, and describing the flight as a commercial deployment would overstate what happened. But they were also not inert mass simulators. The test exercised the payload bay, deployment mechanism, spacecraft commissioning sequence, communications links, and a new satellite design in the environment where those systems must eventually work.
Starlink V3 is the natural first customer. SpaceX controls the rocket, dispenser, satellite, and operating procedures, so it can change either side of the interface without negotiating with another company. That integration matters because Starship’s economic case depends on payloads that are too large, too numerous, or too awkward to package efficiently for smaller rockets.
An intact ship created a better engineering result
Payload deployment was only half of the test. Starship then completed a roughly 14-second relight of one methane-fueled Raptor engine, an essential maneuver for future orbital missions. The ship survived reentry and made a soft splashdown in the Indian Ocean about 65 minutes after liftoff.
Unlike previous water landings that ended quickly in fire or breakup, the ship remained afloat and continued returning imagery.
The intact vehicle gave engineers something previous splashdowns could not: a prolonged look at the hardware after reentry. SpaceX flew the ship through higher dynamic pressure, then kept receiving imagery of the thermal-protection system, airframe, control surfaces, and engines. Engineers can now compare sensor data with the visible condition of thousands of heat-shield tiles instead of reconstructing performance from wreckage.
A heat shield that works once but needs extensive replacement after every flight cannot support rapid turnaround. Flight 13 did not demonstrate reuse—the ship landed in salt water and will not fly again—but it produced the postflight evidence needed to judge whether the design is moving in that direction.
The booster remains the warning label
The ship’s condition made the final images memorable, but the booster told a less comfortable story. Super Heavy—the first stage that provides most of Starship’s launch thrust—completed the high-thrust portion of its boostback burn with all 33 engines, but the burn ended early. Only a subset of engines relit for the landing burn, and the booster struck the Gulf of Mexico harder than planned.
Launch cadence depends on recovering both stages. SpaceX has caught and reflown earlier Super Heavy versions, but V3 changes the hardware and resets part of the reliability curve. An intact ship does not create a reusable system if the booster cannot complete a controlled return.
Flight 13 also followed an aborted July 16 attempt in which four booster engines failed to ignite properly. SpaceX attributed that abort to off-nominal liquid-oxygen turbopump behavior associated with moisture that froze when exposed to cryogenic propellant. The company replaced engines and tested them before flying again. The recovery was fast, but the episode underscores the difference between fast troubleshooting and mature operations: operational systems must prevent repeatable ground and propulsion faults, not merely diagnose them quickly.
A tower catch would raise the stakes
That incomplete booster recovery is important context for SpaceX’s next ambition. Elon Musk said the company could attempt to catch the Starship upper stage with the launch tower on the next flight, subject to the Flight 13 data review. That would be a much harder test than placing the ship into the ocean.
A returning ship approaches from orbital speed, passes through the most demanding thermal and aerodynamic portion of the mission, and must then navigate back to a small recovery zone beside critical launch infrastructure. The catch requires precise guidance, navigation, control, engine performance, communications, and tower coordination. A miss would risk both the vehicle and the pad needed for future flights.
The payoff is real. A tower catch eliminates landing legs and places the ship directly into the ground system meant to inspect, service, and relaunch it. So is the risk: a late engine, guidance, or control failure could damage the pad needed for subsequent flights. Flight 13 supports attempting the catch only if the heat-shield, engine, and control-system reviews show enough margin to protect the tower when something degrades.
What Flight 13 means for Starlink and Artemis
Starship’s immediate operational customer is Starlink. The larger V3 satellites are designed around the volume and mass that Starship can deliver, while Falcon 9 remains the dependable system carrying today’s constellation. Moving V3 deployment onto Starship would convert flight-test progress into network capacity and revenue.
The National Aeronautics and Space Administration (NASA) is watching a different dependency chain. Its Artemis lunar missions require capabilities Flight 13 did not test: orbital insertion, long-duration storage of super-cold propellants, rendezvous and docking, fuel transfer between spacecraft, repeated tanker launches, and human-rated lunar operations. A successful payload deployment and intact splashdown do not close those gaps.
Flight 13 strengthened that foundation without closing the larger gaps. Engine relight, thermal protection, payload operations, and recovery accuracy are prerequisites for the orbital campaign NASA needs. The next milestone is therefore bigger than the tower catch alone: SpaceX must combine orbital flight with dependable booster and ship recovery, then do it again on a useful cadence.
Why Flight 13 matters
Flight 13 gave SpaceX its best Starship data set yet and its first useful satellite exercise. Flight 14 will show whether that was a turning point or another exceptional test. Operations begin when the achievements stop being exceptional.
That distinction reaches beyond one company. A reliably reusable Starship could reshape satellite design, lower the practical cost of very large payloads, expand commercial activity in orbit, and support NASA’s return to the Moon. Flight 13 did not deliver that future, but it made the path toward it easier to evaluate.
