Starship’s 13th test flight adds 20 real Starlink V3 satellites to the bay
A Thursday launch window, higher pressure, and laser link checks aim to validate Starlink V3 interoperability in orbit.

SpaceX is preparing Starship's 13th full-scale test flight, with liftoff possible as soon as Thursday, during a window opening at 5:45 pm CDT (22:45 UTC). The mission carries 20 real Starlink V3 satellites in Starship's cargo bay to test deployment and brief laser communication links in low-Earth orbit.
SpaceX is gearing up for Starship's 13th test flight later this week, and the change that matters is brutally concrete: instead of simulated payloads, technicians have installed 20 real Starlink V3 satellites into Starship's deployer. The launch window opens at 5:45 pm CDT (22:45 UTC) on Thursday, and the flight could take off as soon as then.
This is not a marketing demo. Engineers previously tested the payload deployment mechanism using simulators that mimicked the mass and dimensions of the next-generation Starlink Version 3 broadband satellites. This time, Starship’s 13th full-scale test flight, the second to use SpaceX’s newest version of Starship, will eject an actual stack of satellites one at a time through an opening on the side of the spacecraft, using a system of pulleys and cables. SpaceX is also planning to briefly attempt laser communication links between the Starlink V3s and other spacecraft flying in low-Earth orbit, specifically to validate Starlink V3 interoperability with SpaceX’s previous generation of Starlink satellites.
The headline stakes are straightforward for anyone tracking space execution risk: “real satellites” turn a deployment exercise into a systems integration test. Deployment mechanisms can work flawlessly with mass and dimensions that look right on paper, but real hardware has quirks: integration tolerances, environmental sensitivity, deployment timing, and how signals behave after separation. By putting working satellites into the bay, SpaceX is forcing the full chain to behave under the same kind of physics that will matter in later operational use. Even though these V3 units will not be part of SpaceX’s operational network, the mission aims to prove that Starlink V3 can interoperate with earlier Starlink generations through laser links.
There is also a reason this matters to decision-makers watching the company’s broader capital and regulatory trajectory, even if the test itself is “just” a flight experiment. Starship is designed for high-pressure test objectives, and Ars notes that the hour-long mission will look a lot like the last Starship flight in May, while still having key differences. When a launch schedule compresses and the vehicle’s flight profile is under scrutiny, payload-relevant failures can snowball into delays across future testing. That affects not just engineering timelines, but also how capital markets and regulators evaluate execution credibility. In other words, the technical goals are also schedule defense.
On the communications side, this mission is testing something more specific than “can it connect.” SpaceX says technicians will attempt to briefly establish laser communication links between the Starlink V3 satellites and other spacecraft in low-Earth orbit. If successful, that would validate interoperability between Starlink V3 and SpaceX’s previous generation of Starlink satellites. For boards and investors, that distinction matters. Interoperability reduces the uncertainty of fleet transitions because it suggests new hardware can blend into the existing constellation ecosystem. That can lower the operational risk of moving from one generation to the next, even if the V3 satellites on this flight are not going live in the operational network.
It’s also worth noticing how the test design handles verification without fully committing to operational deployment. SpaceX previously used simulators to test the deployment mechanism, which is a classic engineering approach: validate the mechanical system and its choreography before adding the cost and complexity of real satellites. This next step keeps the same general deployment approach, but swaps the simulators for 20 Starlink V3 satellites. The mission becomes a bridge between “mechanism works” and “payload works and communicates.” When you are trying to keep program risk contained, that kind of staged escalation is the difference between a manageable test campaign and an expensive spiral.
So what should similar operators and finance-minded leaders take from this? Starship’s 13th full-scale test flight is scheduled to occur during a launch window that opens at 5:45 pm CDT (22:45 UTC) on Thursday, and the payload change is the loudest signal in the plan. Installing 20 real Starlink V3 satellites into the deployer, then attempting laser communication links to validate interoperability, effectively turns a vehicle test into a communications systems milestone. If SpaceX pulls it off, it strengthens the argument that future Starship missions can support more than just transportation. They can also accelerate constellation evolution, not just by launching satellites, but by proving the new generation can integrate with the one already in orbit.
This story's Key Insights and Take-aways are locked.
Create a free account to unlock Executive Actions for one credit.
Register to UnlockAlways free for Executives Club members. Join the Club
More in Technology

Uber product chief Sachin Kansal says it won’t be “everything for everyone”
In a TechCrunch walkthrough of Uber’s hotels, robotaxis, AV Labs data, and AI rollout, Sachin Kansal explains the product strategy.

Meta eyes selling excess AI compute: $50B Louisiana expansion meets AWS-style cloud ambition
Meta plans to grow Hyperion datacenters and, per Zuckerberg, could monetize surplus compute like AWS, Azure, or Google Compute.

Meta spends $50B on AI data centers. Wall Street cheers, but overbuild alarms ring
The money is real. The question is whether it outpaces demand, and what that means for rivals’ capital plans.

