Starship Flight 13 Deploys 20 Starlink V3s, Nails Splashdown
SpaceX’s 13th Starship test flight on July 24, 2026, marked the first deployment of 20 next‑gen Starlink V3 satellites and a controlled Indian Ocean splashdown. The mission validated critical systems—Raptor restart, heat shield upgrades, and payload bay operations—that pave the way for lunar landings and large‑scale constellation build‑out.
Key Takeaways
- SpaceX’s 13th Starship test flight on July 24, 2026, marked the first deployment of 20 next‑gen Starlink V3 satellites and a controlled Indian Ocean splashdown.
- The mission validated critical systems—Raptor restart, heat shield upgrades, and payload bay operations—that pave the way for lunar landings and large‑scale constellation build‑out.
Mentioned
Key Intelligence
Key Facts
- 1SpaceX completed the 13th Starship test flight on July 24, 2026, launching from Starbase, Texas, with the new Super Heavy V3 booster.
- 2For the first time, Starship deployed 20 next‑generation Starlink V3 satellites from its payload bay; the satellites burned up on reentry as planned.
- 3The Raptor engine successfully restarted in space, and the heat shield performance was significantly improved, enabling a soft, upright splashdown in the Indian Ocean without explosion.
- 4The Super Heavy V3 booster splashed down in the Gulf of Mexico; no catch attempt was made with the Mechazilla tower.
- 5The previous Flight 12 in May 2026 ended with Starship S39 exploding after splashdown; issues were resolved through software updates and fixes.
- 6The test was delayed from Thursday due to weather concerns that would have affected ground‑based heat shield imagery.
Splashdown confirmed! Congratulations to the entire SpaceX team on the 13th flight test of Starship!
Posted on X immediately after the Indian Ocean splashdown
Satellites were released from the payload bay and burned up during reentry approximately 20 minutes later, as planned
Analysis
For the space and defense community, Starship’s 13th flight test is more than a iterative milestone—it is a tangible demonstration of heavy‑lift payload delivery and system maturation that directly impacts national security space architecture and NASA’s Artemis timetable. The first release of 20 operational Starlink V3 satellites, even in a destructive reentry scenario, confirms that Starship can execute high‑volume constellation deployments in a single launch, a capability the DoD has been watching closely as it considers point‑to‑point transport and resilient orbital networks.
SpaceX's Starship program took a decisive step forward on July 24, 2026, with the 13th integrated flight test of the world's most powerful rocket. The mission lifted off from Starbase in Boca Chica, Texas, at approximately 6:45 p.m. CDT, propelled by the new Super Heavy V3 booster—the most advanced iteration yet. In a first, the upper stage deployed 20 next-generation Starlink V3 satellites from its payload bay, demonstrated a Raptor engine restart in space, and then survived hypersonic reentry without the catastrophic failure that marred the previous test. After a series of maneuvers, Starship executed an upright, soft splashdown in the Indian Ocean and continued transmitting video and telemetry data—an outcome SpaceX hailed as a success.
SpaceX's Starship program took a decisive step forward on July 24, 2026, with the 13th integrated flight test of the world's most powerful rocket.
The flight was the second outing for the third-generation Starship vehicle, following the May 2026 Flight 12, during which Starship S39 exploded shortly after splashdown. SpaceX engineers traced the failure and implemented software fixes and system updates, which evidently paid off. The heat shield—a critical barrier of thermal protection tiles—showed significantly improved performance, enduring the intense friction of atmospheric reentry. SpaceX had delayed the launch by a day due to weather that would have obscured ground-based imagery of the heat shield during peak dynamic pressure, underscoring how vital that data is for future refinements.
One of the most notable achievements was the deployment of 20 Starlink V3 satellites—the first operational payload ever released from a Starship’s cargo bay. Although the satellites burned up as planned during reentry roughly 20 minutes after separation, the act validated the vehicle’s ability to deliver a large number of spacecraft to orbit in a single mission. This capability has direct implications for the rapid expansion of the Starlink megaconstellation, as well as for national security space architectures that require heavy-lift launch for large satellite networks. The successful in‑space restart of a Raptor engine is another building block for deep‑space missions, enabling course corrections and orbital insertions needed for lunar and Martian trajectories.
The Super Heavy V3 booster performed a controlled splashdown in the Gulf of Mexico rather than attempting a catch at the Mechazilla launch tower, a maneuver that remains under development. The decision to forgo the catch allowed engineers to gather data on booster reentry and terminal guidance without risking damage to ground infrastructure. This conservative approach reflects SpaceX’s iterative philosophy: prioritize return of the most delicate part—the ship—while progressively hardening the booster’s recovery sequence.
What to Watch
From a market standpoint, the success strengthens SpaceX’s already commanding position in the heavy-lift sector. NASA’s Artemis program relies on Starship as the Human Landing System, and the Department of Defense is eyeing the rocket for point‑to‑point transport and rapid constellation deployment. Competitors such as Blue Origin and United Launch Alliance, as well as China’s state‑backed Long March super‑heavy concepts, face an accelerating cadence—13 flights in about three years—that sets a blistering pace. The ability to launch next‑generation Starlink satellites, even in a test context, hints at a near‑term operational future where Starship regularly fills orbits with hundreds of spacecraft at a time.
Looking ahead, SpaceX plans to test orbital refueling, a cornerstone of lunar and Mars architectures. Full reusability—catching both the booster and the ship with Mechazilla—will be the next grand challenge. Flight 13’s intact splashdown and continued data transmission from the upper stage suggest that a ship catch may not be far off. As the Starship system matures from experimental prototype to operational vehicle, the space industry is witnessing a shift in what is technically and economically possible.
Timeline
Timeline
Flight 12: Starship S39 Explodes After Splashdown
The first V3 Starship vehicle completed a suborbital flight but exploded shortly after a splashdown, prompting software and hardware fixes.
Launch Scrubbed Due to Weather
SpaceX postponed the 13th flight test by one day because cloud cover and visibility would have prevented clear heat shield imagery during ascent.
Liftoff of Starship Flight 13
Starship and Super Heavy V3 lifted off from Starbase, Texas, at approximately 6:45 p.m. CDT on a suborbital trajectory.
Booster Splashdown in Gulf of Mexico
After separation, the Super Heavy V3 booster performed a controlled descent and soft splashdown; no tower catch was attempted.
First Starlink V3 Satellite Deployment
Starship released 20 next‑generation Starlink V3 satellites from its payload bay; the satellites burned up during reentry about 20 minutes later as planned.
Starship Splashdown in Indian Ocean
The upper stage survived reentry, restarted a Raptor engine in space, and made a soft, upright splashdown while continuing to transmit telemetry and video.
Sources
Sources
Based on 2 source articles- yahoo.comStarship has successful flight test , splash down in Indian OceanJul 25, 2026
- Tass (RU)Starship completes test flight, successfully splashing down in Indian OceanJul 25, 2026
Cite This Page
"Starship Flight 13 Deploys 20 Starlink V3s, Nails Splashdown." Space & Defense Intelligence Brief, July 25, 2026. https://getspacebrief.com/story/spacex-starship-flight-13-20-starlink-v3-deployed-splashdown
How we covered this story
Every story in our space & defense coverage is assembled from multiple primary sources, cross-referenced for factual consistency, and scored along three independent dimensions: sentiment, operational impact, and source-cluster confidence. Single-source rumors and unverifiable claims do not pass our editorial gate. When a story shows "Verified by N sources" with N≥2, the development is independently corroborated; when N=1, we mark it explicitly so readers can weigh the signal accordingly.
Impact scoring uses a 1-10 scale weighted toward regulatory, financial, and operational consequence rather than coverage volume. A topic that runs in every outlet but moves no real decisions ranks lower than a niche regulatory filing that reshapes how operators in the space & defense space have to behave. Read our full methodology for the scoring rubric, our glossary for term definitions, and our trends index for the longitudinal view across the beat.
Sources are only linked to a story once they clear our classification pipeline at a minimum 35 percent relevance threshold. According to that methodology, reviewed July 2026, this follows multi-source corroboration standards recommended by journalism research bodies such as the Reuters Institute for the Study of Journalism.
See something wrong in this story — a wrong fact, a broken source link, a misattributed entity? Report a data issue.
| Signal on this page | What it tells you |
|---|---|
| Verified by N sources | Independent corroboration count. N≥2 is our confidence floor; N=1 is marked explicitly. |
| Impact score (1-10) | Regulatory + financial + operational weight. 8+ signals an experienced-operator action item. |
| Sentiment | Five-tier classification trained on labeled space & defense-specific corpora. |
| Timeline | Where applicable, the related-events sequence that contextualizes today's development. |