The Space Force has put up to $985 million more behind its three national security launch providers at a moment when only one of them has rockets flying. Space Systems Command awarded SpaceX, United Launch Alliance and Blue Origin up to $985 million in contract modifications for Phase 3, Lane 2 of the National Security Space Launch program, Defense Daily reported Nov. 16. The action landed one day after a ULA Vulcan failed roughly 10 minutes into flight, leaving SpaceX's Falcon 9 and Falcon Heavy as the only other rockets currently authorized for the Pentagon's most demanding payloads, with Blue Origin's New Glenn still grounded since a May launch pad explosion.

The modifications run through April 2033, according to SSC. The service did not publish a per-company breakdown in the portion of the announcement available to readers, so how the $985 million ceiling divides among the three providers remains unconfirmed. The figure also represents a ceiling: "up to" language in contract modifications sets the maximum value, not money already obligated to specific missions.

What the $985 Million Lane 2 Modifications Cover

Defense Daily's account frames the action plainly: the three companies received "up to $985 million in contract modifications for Phase 3, Lane 2 of the National Security Space Launch (NSSL) program," the outlet reported, adding that "Work is to finish by April 2033, SSC said."

Lane 2 is the part of Phase 3 that carries the Space Force's critical payloads, according to Breaking Defense's description of the program.

ULA, one of the three recipients, is a joint venture of Boeing and Lockheed Martin that has operated since Dec. 1, 2006, according to Defense Daily. Defense Daily's full article sits behind a subscriber wall; this account relies on the portion published openly, which does not specify the missions, task orders or dollar allocations attached to each company.

Why the Vulcan Failure Leaves Falcon as the Only Lane 2 Rocket Flying

The timing puts the award in an uncomfortable light. On Nov. 15, Vulcan "suffered an anomaly about 10 minutes after liftoff, preventing the rocket from reaching orbit and destroying 40 satellites for Amazon LEO’s planned broadband network for low-Earth orbit," Breaking Defense reported. The outlet said the failure "will likely trigger a lengthy investigation that could ground the rocket for months."

That leaves a short list of certified vehicles. "Aside from Vulcan, SpaceX’s Falcon 9 and Falcon Heavy are the only rockets currently authorized to carry critical payloads under the Space Force’s National Security Space Launch (NSSL) Phase 3 Lane 2 program — given that Blue Origin’s New Glenn also remains grounded following a launch pad explosion in May," Breaking Defense wrote.

Vulcan had already been sidelined from national security work before this flight. The Space Force grounded it in late February over persistent problems with its solid rocket boosters, and by Oct. 1 the service had reassigned six NSSL missions previously manifested on Vulcan to SpaceX, according to Breaking Defense. The Nov. 15 mission carried a commercial payload, but it was designed to serve as an important step toward Vulcan's return to the NSSL program.

Advertisement

The cause has not been announced. Breaking Defense, citing Ars Technica, reported that the problem appears to have occurred in the booster stage. That detail could matter beyond ULA: Breaking Defense noted that if the rocket's BE-4 engines were involved, the failure could also have implications for Blue Origin's New Glenn, which uses the same engines. In that case, both of the non-SpaceX Lane 2 providers could be affected at once.

"If the issue is with the BE-4 that is a particularly thorny problem — for the Pentagon, for NASA, for Amazon and for anyone who needs a ride to space," Clayton Swope, deputy director of the Aerospace Security Project at the Center for Strategic and International Studies, told Breaking Defense.

Can the Space Force Fund Three Providers While Only One Flies?

The modifications keep all three providers under Lane 2 contracts even as two of the vehicles sit on the ground. That arrangement would leave room to move missions back to Vulcan or onto New Glenn once those rockets return to flight, though neither source says how SSC plans to use the modifications.

Advertisement

The near-term reality, though, favors SpaceX. "We can hope that whatever caused this problem gets fixed. We can hope that Vulcan, New Glenn and other medium-lift vehicles come online soon, but this is really the same place we have been for the last several years," Swope said. "But the launch bottleneck is real and set to get worse."

SpaceX's own plans add a longer-term complication. Breaking Defense reported that the company plans to shift all of its own launch operations to Starship around 2030, phasing out Falcon rockets, and that in September SpaceX stopped taking commercial orders for Falcon rides after 2028. The company has not announced plans to offer Starship launches to commercial or military customers. Breaking Defense said those decisions have caused widespread concerns about a potential multiyear gap between demand for US launch services and available capacity. With Lane 2 work extending to April 2033, that could leave the service exposed if alternatives to Falcon are not certified and flying by the time Falcon winds down.

"I don’t see a magic wand here. I mean, the only thing that could happen is that somebody persuades Elon to keep Falcon 9 flying until there are viable alternatives," said Martin Halliwell, of Luxembourg-based private equity firm New Space Capital, according to Breaking Defense.

What It Means for Contractors

For satellite builders and payload integrators, the immediate effect is schedule risk. Missions assigned to Vulcan or New Glenn under Lane 2 now depend on the outcome of a Vulcan investigation with no public timeline and on New Glenn's return to flight from its grounding. The reassignment of six Vulcan missions to SpaceX by Oct. 1 shows the service will move payloads when a vehicle is unavailable.

For ULA and Blue Origin suppliers, including propulsion, avionics and ground-systems vendors, the modifications suggest the Space Force is keeping both providers under contract despite the setbacks. The contract ceiling runs through April 2033, but any work it supports depends on each rocket returning to flight and being authorized for critical payloads. Suppliers tied to the BE-4 engine should watch the Vulcan investigation closely, since a finding there could affect two launch vehicles.

For launch-adjacent firms and new entrants, the capacity squeeze is a potential opening. Swope's assessment that the bottleneck is "set to get worse" points to continued demand for range services, payload processing, and any medium- or heavy-lift vehicle that can reach certification. Companies hoping to join the program should watch how SSC uses these Lane 2 modifications, since the public reporting so far does not say whether the provider base will widen.

Sources