Talk Around Town: Starship Flight 13 Claims Two Big Firsts — V3 Satellites and an Intact Splashdown

What Folks Are Hollerin' About

Well, slap the hood of a pickup and call it Sunday — SpaceX's Starship Flight 13, which flew on July 24, 2026, is being talked up as a genuine two-fer of milestones. According to SpaceNews, CNN, Engadget, and Universe Today, the mission carried 20 functioning Starlink V3 satellites into space for the first time, after six prior flights had hauled nothing but dummy stand-ins — about as useful for real-world testing as a screen door on a submarine. On top of that, SpaceX says the Starship upper stage survived its Indian Ocean splashdown in one wet but recognizable piece, which the company describes as a program first.

Now, before you start planning the parade, hold your horses. Those 20 satellites were riding a suborbital arc and burned up on reentry like a July Fourth sparkler — not a single V3 is up there serving customers right now. But the chatter in the space press is that what happened on Flight 13 represents meaningful progress toward the kind of high-cadence launches SpaceX will need to actually build out the V3 constellation it has described in regulatory filings.

What Is Actually Known and Confirmed

Multiple independent editorial outlets — SpaceNews, CNN, Engadget, and Universe Today — all corroborate that Flight 13 launched July 24, 2026, and that it carried 20 operational Starlink V3 satellites, the first functioning ones to fly on Starship rather than mass simulators. SpaceX engineer Kate Tice said on the webcast, per Universe Today and Engadget, that the team made contact with all 20 satellites and also established laser inter-satellite link communications with all of them — a key integration checkpoint that dummy spacecraft obviously cannot provide.

As for that soggy upper-stage landing: SpaceX spokesperson Dan Huot said on the live broadcast, as reported by SpaceNews and CNN, that this was the first time a Starship had been placed intact in the water. The vehicle also carried six satellites fitted with cameras pointed at Starship's heat shield, per Engadget and autoevolution, giving engineers imagery of how the tiles held up — data that's about as valuable as finding out your roof don't leak during the actual storm.

The Super Heavy booster made a controlled Gulf of Mexico splashdown, but SpaceX acknowledged on the webcast — reported by both CNN and SpaceNews — that not all Raptor engines required for the landing burn actually ignited, causing the booster to hit the water harder than intended. SpaceX spokesperson Dan Huot confirmed this anomaly. The full technical explanation has not been published as of reporting.

The V3 Spec Claims: Big Numbers From SpaceX's Own Filings

According to SpaceX regulatory filings, as cited consistently by Engadget, basenor.com, and Internet In Space, each V3 satellite is designed to deliver up to 1 Tbps of downlink capacity — the company says that's roughly ten times what a V2 satellite can manage — plus at least 160 Gbps of uplink. Engadget puts that uplink figure at about 22 times the V2 rate, though some other outlets cite figures north of 200 Gbps; SpaceX has not published a single unified spec sheet that independent press has verified on its own. Each V3 satellite, according to autoevolution, weighs approximately 1,760 kilograms and runs about 7 meters long — too big for a Falcon 9 to haul, making Starship the only ride in town for this hardware.

There is also a genuine disagreement in the specialist press worth flagging: Internet In Space reports that existing user terminals will remain compatible with V3 on Ku and Ka bands, while basenor.com reports that SpaceX has told customers their current dishes cannot tap into the full V3 downlink and will require a hardware upgrade. That may be a distinction between getting any signal and getting the full gigabit-class speeds SpaceX describes — but it ain't resolved, and customers planning to sit back and wait for the fast stuff to just show up should maybe temper their expectations.

What Remains Unverified and Murky as a Catfish Pond

Flight 12 in May 2026 was the debut of the Starship V3 vehicle configuration, according to autoevolution and Engadget, but it flew only mass simulators instead of live satellites. Flight 13 is described as the second outing of that hardware and the first with real spacecraft. However, the path from 'we launched some satellites that then burned up' to 'we are routinely deploying operational V3 constellations' runs straight through a swamp of unknowns: routine orbital flight certification, ongoing FCC approvals, and production ramp-up that SpaceX has described in its own materials but that no independent source has confirmed is on schedule.

Projections about future constellation scale, end-user upgrade timelines, and any claims about market dynamics or orbital data center applications circulating in less-sourced corners of the internet were not included in the primary claims here because they lack independent corroboration. The booster Raptor engine ignition failure during the landing burn also remains unexplained in any published technical detail — SpaceX acknowledged it happened, but 'not all engines lit' is about as complete an explanation as 'the truck wouldn't start,' and the investigation, if any, has not been made public.

Our Analysis: Real Progress, Real Asterisks

This is analysis, not settled reporting. If you squint at Flight 13 from a distance, it looks like two genuine engineering checkpoints arriving on the same day: satellites that actually talk back, and a vehicle that came down in something resembling one piece. Getting laser inter-satellite links working on a live V3 bird — even a suborbital one headed for a fiery demise — is a more meaningful integration test than bouncing signals off a weighted dummy. And heat shield imagery from those six camera-equipped satellites could accelerate the tile improvement program in ways that ground testing alone cannot.

That said, the gap between 'we touched these milestones' and 'we are ready to flood low Earth orbit with terabit-class internet capacity' is still wide enough to drive a combine harvester through sideways. Starship needs routine, reliable, certified orbital flight before V3 deployment means anything to end users. One booster that landed harder than planned because some engines didn't fire is a reminder that 'test flight' is not a marketing phrase — it's a description of where this program actually is. The optimism in the press coverage is warranted, but so are the asterisks.