The U.S. Space Force is using contract flexibility to protect launch schedules that United Launch Alliance’s grounded Vulcan cannot currently meet. The result is a revealing split between operational reality and procurement policy.
Six national-security missions have reportedly moved from ULA to SpaceX rockets since Vulcan became unavailable, including three GPS launches, a Space Development Agency mission and two higher-energy flights. Those last missions cover the first Next-Generation Overhead Persistent Infrared satellite in geostationary orbit and the Oracle cislunar-surveillance experiment. Later payloads originally assigned to SpaceX are expected to move to ULA in exchange.
SpaceNews reported the wider manifest reshuffle on 24 October. The development matters beyond six launches: Washington is preserving a two-provider market contractually while relying on one provider to protect near-term military schedules.
A successful flight still produced a grounding
Vulcan’s immediate problem dates to the USSF-87 launch on 12 February 2026. The rocket delivered its payload directly to geosynchronous orbit, but ULA confirmed a “significant performance anomaly” on one of four solid rocket motors. The company said the Vulcan booster and Centaur upper stage otherwise performed nominally.
That distinction is important. USSF-87 was not a launch failure, and ULA has not said Vulcan is fundamentally unviable. However, it was the second solid-booster irregularity in four Vulcan flights, after a nozzle problem during the vehicle’s October 2024 certification mission. The Space Force paused national-security launches pending investigation and corrective action.
The pause converted a technical anomaly into a portfolio problem. Missile-warning, navigation and space-domain-awareness spacecraft can spend years and billions of dollars in development. Leaving completed satellites in storage to protect one launch provider’s backlog would transfer launch risk into the satellite programmes.
Mission trades protect schedules and suppliers
The government’s response is not simply to cancel ULA awards. It is exchanging missions between providers. In March, Space Systems Command formally moved a GPS III launch from Vulcan to Falcon 9 while assigning the later USSF-70 mission to ULA.
The broader set of swaps follows the same logic. Schedule-sensitive payloads move to available Falcon rockets; ULA receives later missions that give Vulcan time to return to flight. Public reporting indicates that ULA’s launch-service revenue is being deferred through exchanges rather than erased, although pricing adjustments and the complete replacement manifest have not been disclosed.
This is capacity insurance embedded in acquisition contracts. It offers the government resilience without immediately weakening the second provider’s backlog. For ULA, that is commercially valuable: a conventional cancellation would damage revenue visibility, supplier planning and the business case for Vulcan production.
SpaceX gains operational share without owning every contract
SpaceX is the near-term beneficiary. Falcon 9 can absorb navigation and proliferated-constellation missions, while Falcon Heavy provides the energy required for demanding geostationary and beyond-geostationary trajectories. Falcon Heavy also completed its first National Reconnaissance Office mission in early October, reinforcing its credentials for sensitive high-energy payloads.
Yet the economic gain is more complicated than six new awards. Mission exchanges may preserve the original provider’s contractual value, and SpaceX will surrender later payloads. The more durable advantage is operational: every successful remanifested flight strengthens SpaceX’s position as the launch system the government can call when another provider slips.
That creates an uncomfortable concentration. The National Security Space Launch programme is designed around competition, but competition on paper does not guarantee interchangeable capacity. Payload qualification, fairing dimensions, software interfaces, mission assurance and range availability can all prevent a rapid switch.
High-energy missions reveal the strategic stakes
The two most technically demanding transfers show why the Space Force could not simply wait.
Next-Gen OPIR GEO is intended to provide missile warning from geostationary orbit. Delaying it would affect the transition to a new generation of strategic sensors. Oracle is a pathfinder for detecting and tracking objects near the Earth–Moon region. Advanced Space describes Oracle as a two-year experiment near the Earth–Moon L1 region, testing custody of satellites, rocket bodies and debris in cislunar space.
Moving both missions to Falcon Heavy therefore does more than protect dates. It assigns SpaceX a larger role in two expanding military markets: missile warning and cislunar surveillance. Those capabilities sit upstream of future sensor constellations, data services and command-and-control spending.
Redundancy now depends on Vulcan’s cadence
The Space Force’s exchange mechanism reduces immediate disruption, but it cannot create launch capacity indefinitely. Later ULA-assigned missions will still require Vulcan to clear its investigation, return to flight and establish a repeatable cadence. A growing queue of defence, civil and commercial customers will then compete for launch slots.
ULA’s challenge is consequently larger than fixing one booster component. It must demonstrate that corrective actions survive flight, rebuild customer confidence and process missions frequently enough to absorb the payloads being pushed into later years. Its Amazon Leo commitments add commercial pressure to the same industrial system.
Blue Origin provides a potential third heavy-lift option under the current NSSL framework, but government eligibility and an awarded task order do not make every vehicle immediately substitutable for every mission. Until New Glenn and Vulcan offer sustained operational cadence, SpaceX remains the practical backstop.
Milestones that will determine whether the insurance works
The first milestone is formal clearance of Vulcan’s solid-rocket-motor corrective action, followed by a return-to-flight mission. The more meaningful test will be its next national-security launch and the interval to the flight after that.
For the transferred payloads, watch the Falcon Heavy dates for Next-Gen OPIR GEO and Oracle, as well as any changes required to qualify the spacecraft for a new vehicle. The Space Force should also clarify which later SpaceX missions are moving to ULA and whether the exchanges alter contract values or only timing.
The six swaps demonstrate that launch competition has value even when one provider is temporarily unavailable: contracts can be traded to protect both missions and the industrial base. They also expose its limit. Real redundancy exists only when multiple rockets can fly the same classes of payload on the timelines customers need.