Week in Space Data, every Friday.
By the SpaceNexus Desk
AI-drafted analysis, fact-checked before it publishes
Drafted by AI, fact-checked before publishing, corrected in public. How the desk works
United Launch Alliance (ULA) announced on Wednesday, October 28, that it plans to return its Vulcan heavy-lift rocket to service on November 13. Ars Technica noted the date is a Friday the 13th. The announcement comes nine months after a solid rocket booster anomaly that, in Ars Technica's words, threw the company's 2026 launch schedule "into oblivion." Spaceflight Now describes the failure as a mid-flight nozzle failure on one of the vehicle's solid rocket boosters, and says the upcoming flight is the first for the rocket since that event.
The return-to-flight mission will carry 40 Amazon Leo broadband satellites to orbit. It is also the first Vulcan launch to use a full complement of six solid rocket boosters. That is the most powerful configuration the vehicle is designed to fly, and it places the largest mechanical and thermal loads on the boosters whose nozzle performance is the subject of the investigation.
Two facts from the sources matter most. First, ULA has chosen to return to flight with a commercial constellation payload, not a national security mission. Second, it has chosen the configuration that exercises the failed hardware the hardest. Neither source in our set gives the root-cause details, the corrective actions or the supplier-level fixes, so this analysis does not assume them.
Vulcan was built to replace the Atlas V and Delta IV lines and to serve both national security customers and commercial constellation operators. A nine-month grounding removes one of very few American heavy-lift vehicles from the market while demand for launch is high. The remaining operational alternatives are concentrated, with SpaceX's Falcon family dominant in cadence. Every month Vulcan is idle increases customer reliance on a single provider, which is a concern the Pentagon has voiced for years when discussing assured access to space.
Sources:
About this analysis
Written by the SpaceNexus Desk: a language model drafts each piece from the sources listed above, a second model pass fact-checks it against those sources, and drafts that fail that check are held for a person. No human typed this article. How the desk works · Report a correction
For information only, not investment advice. SpaceNexus is not a registered investment adviser, broker or dealer, and nothing here is a recommendation to buy, sell or hold any security. Data may be delayed, estimated or incomplete; check the source before acting. Full disclaimer
Returning with a six-booster configuration is a statement of confidence, and it also carries risk. The boosters, supplied to ULA by a third party, are the element implicated in the anomaly. Flying the highest-thrust variant on the first flight back means that the corrective work will be judged under the most demanding load case rather than a gentler one. If the flight succeeds, it validates the fix and opens the vehicle's full performance envelope for heavier payloads and higher-energy orbits. If it does not, the consequences for the program would be far greater than a single lost mission.
A payload of 40 satellites is a large share of any launch's value for a constellation builder. Amazon Leo needs multiple launch providers to meet deployment targets, and Vulcan is one of several vehicles the company contracted. The delay has constrained the pace at which Amazon can populate its constellation from this particular vehicle. A successful November 13 mission would resume a launch cadence for Amazon that was planned for 2026 and largely missed.
For constellation operators, the Vulcan grounding is a reminder that launch-provider concentration is a schedule risk. Operators with multi-vehicle manifests, as Amazon has, can reshuffle satellites between launchers, but only when the satellites, dispensers and processing flows are compatible. The return of Vulcan restores optionality. It also gives Amazon negotiating leverage with other providers and relieves pressure on the vehicles that absorbed its demand during the stand-down.
Satellite broadband is also a contested business. Operators compete for spectrum, customers and orbital shells, and deployment pace feeds directly into regulatory milestones and commercial service dates. A launch that places 40 satellites at once is therefore consequential well beyond the launch industry.
For U.S. government customers, the key question is not just whether Vulcan flies on November 13 but how quickly it can resume flying certified national security missions. The sources here do not specify the Space Force's certification actions following the anomaly, so readers should watch for official statements on how the service views the root-cause work. The Space Force has repeatedly said it values two domestic heavy-lift providers. A return that is clean and followed by a steady cadence would support that policy. A second failure would push mission planners to move payloads to other vehicles.
Solid rocket boosters have a narrow supplier base, and the nozzle is a high-precision, thermally stressed component. Any lasting fix involves design, materials or process changes at the supplier, with downstream inspection burdens on ULA. The broader industry lesson is that single points of failure in propulsion subcomponents can ground an entire vehicle for most of a year, regardless of how well the rest of the system performs.
ULA's schedule collapse also affects range and pad usage. Ranges and processing facilities were planned around a 2026 Vulcan cadence that did not materialize. A restart will require integrating a backlog of payloads while the Eastern Range accommodates other providers' high launch rates. Separate coverage of Space Force range modernization shows that the government is already working on throughput into the 2030s.
In the coming two weeks, the key indicators are the completion of static fire or other pre-launch testing, any statement on the root cause and corrective action, and weather and range conditions. Launch dates for new or recovering vehicles often slip, and the sources describe the date as planned rather than assured. Spaceflight Now characterizes the timeline as "mid-November," which leaves room for movement.
The sources do not allow us to assign probabilities to these outcomes, and we do not attempt to.
A successful return would ease pressure on Amazon's constellation deployment and on government payload queues. It would also bear on how the Pentagon thinks about dual-provider policy and launch-service procurement. A failure would intensify calls to diversify the launch base, including support for new entrants. Either way, November 13 will be one of the most closely watched launches of the quarter.
Because this analysis is about Vulcan.
Next Vulcan launch
HOLDVulcan VC6L · Amazon Leo (LV-01)
Fri, Nov 13 (time not set yet) · Cape Canaveral SFS
Follow Vulcan
Date changes and outcomes for its launches, and news mentions. One email a day, only when something changes.