Elon Musk confirmed Starship Flight 13 is targeting Thursday, July 16. That’s the one where SpaceX tries something it’s never done before, actually deploying payload from Starship.
SpaceX has the official mission page live for the thirteenth flight test. The 90-minute launch window opens at 5:45 PM CT from Starbase’s new Orbital Launch Pad 2. Musk confirmed the date on X, quoting SpaceX’s official announcement.
I covered the SpaceXAI rebrand a few days ago, and this launch sits in the same orbit, literally and figuratively. The rocket company that the AI division borrows its name from is moving fast.
What Makes Starship Flight 13 Different
Starship Flight 13 is the second flight of V3 hardware (Booster 20 and Ship 40), but the mission profile has one major addition. For the first time, Starship will carry and attempt to deploy 20 Starlink V3 satellites.
That’s roughly 34,100 kg of payload headed to a suborbital trajectory. The Starlink satellites will extend their solar arrays and antennas, attempt to connect with ground stations in South Africa, and link into the broader Starlink constellation via high-capacity lasers.
Six of those 20 satellites have been modified with cameras. Their job is to scan Starship’s heat shield during reentry and transmit the imagery to operators on the ground. SpaceX also painted several tiles white on this ship to simulate missing tiles and give the cameras clear targets. Data from this test feeds directly into the return-to-launch-site goal.
Hardware Fixes from Flight 12
Flight 12 had a few issues, and SpaceX incorporated fixes on this stack.
At stage separation, the booster’s directional flip was off by roughly 90 degrees because of timing differences in engine startup on the ship side. The startup sequence now handles timing variability better.
Five of the Super Heavy’s 33 engines failed to relight for the boostback burn, which cut the burn short. B20 has hardware modifications to improve relight reliability, plus updated engine alarms and abort thresholds.
Starship lost one of its three Raptor vacuum engines about 40 seconds after stage separation on Flight 12. The vehicle proved it could complete its mission with the engine out, but propulsion system modifications address the root causes. More improvements are planned on future Raptor versions.
B20 completed a full 33-engine static fire on July 10. S40 ran a six-engine static fire on July 1.
The Mission Profile
Super Heavy will boostback and land in the Gulf of Mexico. Starship continues on a suborbital trajectory, deploys the 20 Starlink V3 satellites about 16 minutes after launch, attempts an in-space Raptor relight demo around the 39-minute mark, then reenters and splashes down in the Indian Ocean at roughly T+65 minutes.
SpaceX also published “Critical Path”, a documentary episode covering engineers through the final days before the first V3 launch, if you want the behind-the-scenes story.
The webcast starts 30 minutes before liftoff on SpaceX’s website and on X @SpaceX. With all developmental testing, the schedule can change.
Why It Matters
Starship Flight 13 isn’t just another test flight. It’s the first time a Starship carries actual hardware it intends to deploy. The V3 Starlink satellites are designed to dramatically increase network capacity and user speeds, and every successful flight brings that capability closer.
The heat shield camera test is classic SpaceX. Instead of adding mass to the vehicle, they stuck cameras on the payload itself. If the data confirms tile integrity through reentry, that’s a big step toward rapid reuse.
I’ll update this when the launch window opens and I know whether Thursday sticks or the schedule shifts.
