Skip to content
LIVE
The Executives BriefThe Executives BriefBeta

SpaceX loads 20 Starlink V3 satellites into Starship for its 13th test flight Thursday

A higher-pressure Starship run and fresh Starlink tech aim to validate laser links and interoperability in orbit.

ByOmar Al-BalawiTechnology Correspondent, The Executives Brief
·3 min read
SpaceX loads 20 Starlink V3 satellites into Starship for its 13th test flight Thursday
Executive summary

SpaceX is preparing Starship for its 13th test flight, potentially launching Thursday during a window that opens at 5:45 pm CDT (22:45 UTC). The mission puts 20 operationally representative Starlink V3 satellites into Starship's cargo bay to test deployment and brief laser communication links.

SpaceX is gearing up for Starship's 13th test flight later this week, with a potential launch as soon as Thursday. The launch window opens at 5:45 pm CDT (22:45 UTC), and the mission is expected to last about an hour, following a similar pattern to the previous Starship flight in May. But the headline detail is the one engineers will actually care about: this time, real, functioning Starlink satellites ride inside Starship's cargo bay.

Specifically, for this 13th full-scale test flight and the second to use the newest version of Starship, technicians have installed 20 Starlink V3 satellites into the ship's deployer system. That deployer is a mechanism of pulleys and cables designed to eject a stack of satellites one at a time through an opening on the side of the spacecraft. The satellites will not be added to SpaceX's operational Starlink network, but engineers will try to establish laser communication links between these Starlink V3s and other spacecraft already flying in low-Earth orbit.

Why does this matter beyond another “test flight” label? Because Starship is more than a rocket. In SpaceX's broader stack, it is the delivery system for fast iteration on satellite constellations, and Starlink is the money and momentum engine that lets SpaceX keep pushing hardware to the next rung. Even when a mission is “not operational,” the data is still operational in the engineering sense. Starship has to prove it can carry meaningful payloads under real conditions, move them out precisely, and do so in a way that supports future scale.

There is a clear continuity here. SpaceX previously tested the payload deployment mechanism using simulators that mimicked the mass and dimensions of the next-generation Starlink Version 3 broadband satellites. This flight switches from “look like” to “are.” By installing actual Starlink V3 satellites, the company is stress-testing not only the deployer mechanics but also the practical behavior of satellites after they are ejected into orbit. Deployment is one of those failure modes that can look fine on paper and then go sideways when physics gets involved, so swapping simulators for real units is an upgrade in how credible the test results will be.

The laser communication piece is the second half of the bet. Engineers plan to attempt briefly establishing laser communication links between the Starlink V3s and other spacecraft flying in low-Earth orbit. If successful, the goal is to validate Starlink V3's interoperability with SpaceX's previous generation of Starlink satellites. In plain terms, this is about “can the new talk to the old,” at least long enough to confirm the technology works when it matters: after launch separation, deployment, and the real timing constraints of orbital operations.

For decision-makers watching the space ecosystem, this is not just a technical footnote. Interoperability reduces integration friction. It can also lower the risk of rolling out new satellite versions in parallel with existing networks, which is how constellations typically evolve in the real world rather than with clean stop-start upgrades. When boards and investors think about space companies, they often focus on deployment cadence, manufacturing throughput, and launch reliability. Missions like this connect all three by treating satellite hardware changes as first-class payload requirements, not afterthoughts.

There is also a regulatory and risk-management angle, even though the mission details here are technical. Star missions take place within a framework of launch licensing and operational oversight, and even tests that are not part of a company’s active service must still be planned for how they will affect near-Earth space activity. The fact that these Starlink V3 units will not be part of the operational network signals that SpaceX is isolating what it needs to learn now without immediately committing the satellites to live service. That kind of staged approach is usually what regulators and operators prefer when new capabilities are being verified.

Ultimately, this flight is a boardroom story disguised as a deployment mechanism story. Starship’s 13th test flight is expected to look a lot like the May flight, but with key differences that sharpen the test objectives. By loading 20 real Starlink V3 satellites and attempting laser links in low-Earth orbit, SpaceX is using Starship to accelerate the next generation of its satellite system while also tightening the chain from launch to network capability. For leaders in adjacent aerospace and communications markets, the subtext is simple: the fastest movers are designing satellites, payload deployment, and in-orbit communications to evolve together, not in sequence.

Executive ActionsLocked

This story's Key Insights and Take-aways are locked.

Create a free account to unlock Executive Actions for one credit.

Register to Unlock

Always free for Executives Club members. Join the Club

More in Technology