A Rocket With a Troubled Record Gets One More Chance
United Launch Alliance announced Wednesday that its Vulcan rocket will return to flight on November 13 – a Friday the 13th – lifting off from Cape Canaveral Space Force Station in Florida, subject to range approval. The mission breaks a nine-month standdown that began after a solid rocket booster anomaly in February derailed the company’s entire 2026 launch calendar. For ULA, a company that has staked its next decade on Vulcan succeeding, the date carries more weight than the superstition attached to it.
The payload tells you everything about what’s at stake. Vulcan will carry 40 satellites for Amazon’s Project Kuiper low Earth orbit broadband constellation – the first delivery in a contracted run of 38 Vulcan flights Amazon has booked specifically to build out the bulk of its internet network. That contract is not a side arrangement. It is the commercial spine of Vulcan’s entire business case, and it has been sitting idle while engineers traced exactly what went wrong with the booster nozzles.
Nine months is a long time to be grounded.
What Actually Went Wrong – Twice
The nozzle failures on Vulcan’s solid rocket boosters did not happen once. They happened on two of the rocket’s first four missions, with the most recent incident occurring during the February flight that triggered the current standdown. In both cases, the nozzle failed and the rocket still completed its mission – which is the kind of engineering redundancy that sounds reassuring until you realize the US Space Force, ULA’s primary customer, publicly lost confidence in the vehicle anyway. Finishing a mission despite a hardware failure does not inspire the same confidence as a hardware failure that never happens.
The US Space Force’s reaction matters enormously here because the agency is not simply one customer among many. It is the anchor customer around which ULA’s launch cadence is structured. When military officials signal they have lost faith in a rocket, the commercial market notices. Amazon’s 38-flight contract provides a financial buffer, but no broadband constellation operator wants its satellites aboard a vehicle whose booster nozzles are under active investigation. The nine-month pause was as much about restoring institutional trust as it was about fixing hardware.
ULA has not publicly detailed the root cause or the specific fix applied to the booster nozzles before this return-to-flight attempt. What the company has confirmed is that November 13 is the target and that range approval from Cape Canaveral Space Force Station is still pending. The absence of a detailed technical disclosure is not unusual for return-to-flight announcements, but it does leave the February anomaly without a full public accounting as the countdown begins.
Amazon’s Kuiper Constellation and Why This Flight Has to Work
Project Kuiper is Amazon’s answer to SpaceX’s Starlink – a low Earth orbit broadband network designed to deliver internet access globally, with particular focus on underserved markets. Amazon has been slower to deploy than Starlink, which already operates thousands of satellites and serves millions of subscribers. The 40 satellites scheduled to fly on November 13 represent the first real movement on a deployment schedule that has been waiting on Vulcan to get back into rotation.
Amazon booked 38 Vulcan flights to carry the majority of its Kuiper satellites to orbit. That is not a small commitment. It means the pace of Kuiper’s network build-out is directly tied to how reliably Vulcan can launch through 2026 and beyond. Every additional delay compounds Amazon’s position relative to Starlink, which adds capacity on a schedule measured in weeks rather than months. The commercial urgency behind Friday’s launch is therefore not just ULA’s problem – it belongs equally to Amazon’s satellite internet ambitions.
Vulcan is ULA’s new flagship rocket, designed to eventually replace the Atlas V and Delta IV vehicles that built the company’s reputation over two decades. The pressure on this return-to-flight is therefore layered: restore Space Force confidence, deliver Amazon’s first Kuiper batch, and prove that a rocket which failed on two of its first four missions has genuinely been fixed rather than simply relaunched and hoped for.
The launch is set for November 13 from Cape Canaveral, range approval pending. If the nozzles hold this time, ULA gets its answer. If they don’t – and the rocket still somehow finishes the mission again – the question of whether that counts as a success will be considerably harder to answer than last time.
