A malfunction 10 minutes after liftoff prevents Vulcan rocket from delivering Amazon mission to orbit
Key Facts
United Launch Alliance’s (ULA) Vulcan rocket failed to deliver an Amazon mission to orbit after encountering a malfunction 10 minutes into the flight on November 15. ULA confirmed the malfunction, and the mission was carrying satellites for Amazon Leo, the company’s satellite internet service. The company said it did not have specific data explaining what happened immediately after the incident. It added that it would work with the customer and relevant authorities to determine the cause and appropriate corrective action. Amazon described launch risks as ongoing, particularly on inaugural flights, and expressed confidence that ULA would learn from the mission.
An Amazon representative said: "There are risks with every launch, and that is particularly true for inaugural missions like LV-01." The reference to the mission’s inaugural nature reflects that the flight was Vulcan’s first launch as part of Amazon Leo satellite deployments, according to the company. The payload loss comes as Amazon seeks to expand its satellite network, but the available information does not specify the cost of the loss or its financial impact. Nor does it include a confirmed estimate of any delay to the operational schedule resulting from the incident. The immediate focus is on determining the cause of the malfunction, which ULA said it would work to establish with the customer and relevant authorities.
The November 15 flight was Vulcan’s fifth since its debut in 2024 and came after a 9-month pause. The incident marked the first complete loss of a ULA rocket mission since the company was founded in 2006 as a partnership between Boeing and Lockheed Martin. That places the event in the context of the rocket’s short track record, as ULA begins reviewing flight data and determining corrective action. The company did not immediately announce specific technical details about the malfunction. Reuters estimated that a lengthy technical investigation could keep the rocket grounded for months, without that meaning the length of the pause has been determined.
Before this mission, Amazon had deployed 398 Leo satellites across 14 launches since 2025, according to Reuters. The agency estimated that this number represents about 12% of the satellites needed for global coverage, based on its estimate that 3,236 satellites are required. By contrast, the U.S. Federal Communications Commission’s license authorizes a first-generation constellation of 3,232 satellites and sets July 30, 2029, as the deadline for its full deployment and operation. These figures show the scale of the deployment program and the regulatory deadline Amazon is working toward. Information about the incident alone does not establish how much the loss of this mission will change the pace of deployment or the date for completing the constellation.
Amazon relies on more than one launch provider, while a coming mission using an Ariane 6 rocket is targeted for November 23, according to information about the company’s plan. Diversifying launch providers gives the company another route to continue deploying satellites as ULA investigates the cause of Vulcan’s failure. But the target date alone does not confirm whether the mission will proceed on schedule. ULA said it would determine the cause and corrective action with the customer and relevant authorities, while Reuters said the technical investigation could take long enough to keep the rocket grounded for months. Amazon shares closed at $266.66 on November 13, the last close before the incident in the market data available here.