Starship V3 flies with Starlink V3: the week that space hardware got real

The headline from this week's spaceflight tally is not a number — it's a version number. Starship flew its V3 configuration for the second time on July 24, and this time it carried Starlink V3 satellites into a suborbital arc, deploying all 20 of them before the upper stage came back down. That's not a normal test. That's a hardware iteration at pace that no other rocket program on Earth is running. Here's what actually happened this week, and what it means for the cadence ahead.

The week's launches: three orbital, one suborbital milestone

The week of July 24–31 produced four tracked launch events — three orbital successes and one suborbital milestone that was more consequential than the orbital batch.

July 24 — Starship Flight 13 (Suborbital, Starbase TX): SUCCESS

Starship lifted off at 5:51 p.m. CDT / 6:51 p.m. EDT / 2251 UTC from Pad 2 at Starbase, Texas, marking the second flight of the Starship-Super Heavy V3 configuration — the vehicle variant that SpaceX has been working toward for operational reusability. The Super Heavy booster (Booster 20) and Starship upper stage (Ship 40) were not recovered; both targeted controlled splashdowns in the Gulf of Mexico and Indian Ocean respectively, consistent with the current test profile.

The payload was the first operational deployment of Starlink V3 satellites — 20 of them — released during the suborbital coast. The V3 satellites are a meaningfully different design from V2 Mini: larger antennas, higher bandwidth per satellite, and designed for the full Starlink V3 constellation architecture that will eventually serve as the backbone of SpaceX's next-generation broadband network. The Starlink V3 test was the unclassified payload highlight even though it flew under a suborbital trajectory.

The first Starship V3 attempt on July 16 aborted at T−0 — the vehicle's flight software triggered an automatic abort after six Raptor engines experienced oxidiser turbo-pump anomalies before liftoff. SpaceX resolved the issue and rescheduled for July 24, but Tropical Storm Bertha pushed the window another day. The successful flight on July 24 was, by SpaceX's own language, a moment the team was "over the moon" about.

July 25 — Falcon 9 Starlink 17-51 (LEO, Vandenberg SFB): SUCCESS

A Falcon 9 placed 24 Starlink V2 Mini satellites into low Earth orbit from Vandenberg Space Force Base at 8:51 a.m. PDT / 11:51 a.m. EDT / 1551 UTC. The first-stage booster, tail number B1100, flew its eighth mission and landed on the droneship Of Course I Still Love You in the Pacific Ocean. Delayed from July 23 and 24.

July 30 — Falcon 9 NROL-95 (LEO, Cape Canaveral SLC-40): SUCCESS

A Falcon 9 launched a classified National Reconnaissance Office payload under the NSSL Phase 2 contract at 3:10 a.m. EDT / 0710 UTC from Cape Canaveral Space Force Station. The first-stage booster, tail number B1096, flew its seventh mission and returned to a landing at Landing Zone 2 at Cape Canaveral — visible to the public from the coast. This was the third NRO mission under the Phase 2 procurement awarded to SpaceX in August 2024.

July 31 / August 1 — Falcon 9 Starlink 17-52 (Vandenberg SFB): PENDING

The planned launch of 24 Starlink V2 Mini satellites from Vandenberg had been delayed four times — originally targeting July 27, then July 28, July 29, July 30, and now July 31/August 1. The window opens at 7 p.m. PDT / 10 p.m. EDT / 0200 UTC. The booster is B1081, targeting its 26th flight. This mission has been a weather-and-range persistent, not a vehicle issue.

---

What this week's launches actually tell us

Starship is iterating faster than the industry can track. Flight 12 (June 2026) and Flight 13 (July 24) are 8 weeks apart — that cadence is exactly what SpaceX said it was targeting. The V3 hardware is mature enough to fly with payload, and the abort on July 16 was caught and fixed within 8 days. When a conventional launch provider scrubbed a NRO mission for engine issues, that story leads the news for a week. SpaceX catches an auto-abort at T−0 and flies eight days later with no significant coverage of the root cause fix.

NROL-95 is a reminder that the NRO is SpaceX's most reliable commercial customer. Three Phase 2 missions so far, all Falcon 9, all successful, all NRO (not disclosed in detail publicly — that's the nature of reconnaissance payloads). The fact that B1096 has seven flights on it and the NRO is comfortable flying on a booster that reused seven times tells you where the Air Force/NRO relationship with SpaceX reusability is: fully operational, not experimental.

Starlink 17-52 keeps slipping for reasons that don't matter much. Four delays in five days sounds alarming until you notice the booster (B1081) is at 26 flights and the satellites are standard V2 Mini. The range and weather in California have been busy with Starlink batch launches — when you fly this often, some missions step on each other's slots. That's a capacity problem, not a reliability concern.

Next week: the Roman Space Telescope and the next phase of Starlink V3

The week of August 4–9 is notably lighter in confirmed launch count, but one mission stands above everything else in significance:

Nancy Grace Roman Space Telescope — NET August 30, Falcon Heavy, Kennedy LC-39A

That's in the second half of August. The more immediate calendar:

The BlueBird 11-13 launch on August 5 is worth watching closely. AST SpaceMobile is deploying three Block 2 satellites, each with a 2,400-square-foot phased array — making them the largest commercial communications antennas ever placed in LEO. Three satellites at that scale, if they work, change the calculus for direct-to-device cellular broadband from orbit. This isn't a Starlink story; it's the most credible alternative architecture story in the commercial satcom space.

The H3 launch of QZS-7 from JAXA's Tanegashima Space Center on August 6/7 (NET, ~4:30 p.m. JST August 7 / ~3:30 a.m. EDT August 6) represents Japan's contribution to the Quasi-Zenith Satellite System — their GPS augmentation constellation. Ninth flight of H3, delayed from March 2026.

The most significant thing to watch beyond next week: Starlink V3 is no longer a test article. It flew on Starship Flight 13 and, once the operational constellation architecture is confirmed, the implication is that Starship becomes the primary deployment vehicle for the V3 shell. The cadence of Starship flights and the cadence of Starlink V3 deployments are going to be linked in a way they haven't been before. That's a story for the weeks ahead — but it started this week.

---

Next week: the BlueBird deployment, the Roman Space Telescope on the near horizon, and another Starlink V3 deployment that probably won't make the news but will change the map.

Sources

• Spaceflight Now — Starship Flight 13
• SpaceX — Starship Flight 13
• Wikipedia — Starship Flight Test 13
• Spaceflight Now — Falcon 9 Starlink 17-51
• Spaceflight Now — Falcon 9 NROL-95
• Spaceflight Now — Launch Schedule
• Spaceflight Now — Launch Log
• NASA Science — Roman Space Telescope Launch Countdown
• Business Wire — AST SpaceMobile BlueBird Launch Announcement