Local
What Vulcan’s failure means for the Cape
ULA’s Vulcan failed 10 minutes after liftoff from Cape Canaveral on Nov. 15 and is grounded pending an FAA-overseen investigation. The cause has not been established, and reports of a booster-stage problem are unconfirmed.
Two days after United Launch Alliance’s Vulcan rocket failed to reach orbit from Cape Canaveral, the official record is still short. The cause has not been established, the rocket is grounded pending an investigation the Federal Aviation Administration will oversee, and reports that the problem began in the booster stage remain unconfirmed.
What is confirmed
The rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. Eastern time on Sunday, Nov. 15. In a statement quoted by Ars Technica, ULA said the vehicle "suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit." The company said it did not immediately have "any specific data to understand what occurred" and would work to find the cause and "return to flight as quickly as possible." Ars Technica described it as the first total mission failure in ULA’s history.
The payload was 40 satellites for Amazon’s Leo broadband network. It was the first of 38 Vulcan launches for Amazon, following eight Amazon missions on ULA’s Atlas V, according to ULA’s mission page. Amazon, in a statement quoted by Ars Technica, said there is "risk with any launch," especially on a first mission, and called ULA a trusted partner.
The FAA said in a Nov. 16 statement that the mission "experienced a mishap" and that it is requiring ULA to conduct a mishap investigation. The agency said it will oversee the ULA-led investigation, be involved in every step and approve the final report, including any corrective actions. A return to flight depends on the FAA determining that any system, process or procedure related to the mishap does not affect public safety. During the event, the FAA said, it activated two Debris Response Areas and briefly slowed or held aircraft.
The earlier booster problem
Sunday’s flight was Vulcan’s fifth, Aviation Week reported, and its first since a solid-rocket-booster nozzle problem on a February launch. In a Nov. 10 blog post, ULA said its team, with booster supplier Northrop Grumman, the U.S. Space Force and other agencies, had identified three credible causes, taken steps to mitigate all of them and built those changes into the boosters for this flight. ULA said that investigation was continuing.
Aviation Week, in a Nov. 16 report otherwise behind a paywall, said the failed rocket "flew long enough to demonstrate modifications to the vehicle’s solid rocket boosters" were successful. Ars Technica reported the six boosters appeared to perform well in the first two minutes. ULA has not issued a public finding on the booster changes.
What is not confirmed
Ars Technica, citing multiple unnamed sources, reported that the anomaly occurred in the booster stage, not the Centaur V upper stage or the solid rocket boosters. It reported that the two Blue Origin BE-4 main engines, which were supposed to shut down just short of the five-minute mark, kept firing for at least 30 more seconds, that such an overburn could indicate the booster was underperforming, and that a telemetry-driven animation on ULA’s broadcast showed the rocket begin to spin after engine shutdown. Ars said it could not determine whether the engines, the propellant system or something else was the cause.
ULA has not confirmed a booster-stage failure, a BE-4 malfunction or an overburn. Neither ULA nor the FAA has given a timetable for the investigation. Ars Technica reported that the failure is expected to ground the rocket for an indefinite period.
National security launches were already moving
Sunday’s flight was commercial, but Vulcan is also on contract for roughly half of the military’s national security launches in the next few years, Ars Technica reported. The Space Force had grounded it for those missions in late February over the booster problem, according to Breaking Defense, which reported Monday that "by Oct. 1, the Space Force reassigned six NSSL missions previously manifested on Vulcan to SpaceX."
SatNews, in an Oct. 22 report, said Space Systems Command’s commander, Lt. Gen. Philip Garrant, disclosed the six transfers at an industry briefing on Oct. 21, and that the moves were trades for later Vulcan missions rather than cancellations. The two outlets give different dates, Oct. 1 and Oct. 21, and neither figure comes from a Space Force document reviewed for this article.
New Glenn shares the BE-4. No link has been established.
Blue Origin’s New Glenn uses a version of the same BE-4 engine that powers Vulcan’s booster. Vulcan’s Centaur upper stage uses different engines, RL10s. No link between Sunday’s failure and New Glenn has been established. Ars Technica and Breaking Defense both noted that a BE-4 finding, if one is reached, could have implications for New Glenn. That remains hypothetical.
New Glenn is grounded for a separate reason. A New Glenn exploded during a ground test in Florida in May, which Ars Technica reported knocked Blue Origin’s launch pad offline until at least the end of this year and was traced to a faulty valve on a BE-4 engine. With both rockets down, Breaking Defense reported, SpaceX’s Falcon 9 and Falcon Heavy are the only rockets currently authorized for the Space Force’s most critical payloads.
What it means locally
Complex 41 is where ULA had just opened a second processing lane, an Amazon-dedicated integration building and launch platform that ULA said would allow a higher launch cadence for all Vulcan customers. Sunday’s mission was the first to use it. How long Vulcan stays grounded, and what that means for work at the pad, is not addressed in the ULA or FAA statements.
Until ULA and the FAA say what failed, claims about a booster overburn, a BE-4 fault or a short grounding should be treated as unconfirmed.
Based on statements from United Launch Alliance and the Federal Aviation Administration and on reporting by Ars Technica, Aviation Week, Breaking Defense and SatNews. 321 Daily did not seek comment for this story.