United Launch Alliance loses Vulcan rocket and 40 Amazon Leo internet satellites in launch mishap

In a major setback for United Launch Alliance, the company’s new heavy-lift Vulcan rocket carrying 40 Amazon Leo Internet satellites failed during ascent into space on Sunday, dooming the payload and throwing a costly brake on both companies’ launch schedules. “Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 (at Cape Canaveral Space Force Station) suffered an anomaly 10 minutes into the flight and was unable to fulfill Amazon’s mission in orbit,” ULA said in a statement about 50 minutes after takeoff. “We will work closely with our customer and other appropriate organizations to find the cause, determine appropriate corrective action and return to flight as quickly as possible.” United Launch Alliance’s Vulcan rocket, powered by two methane-fueled BE-4 main engines provided by Jeff Bezos’ Blue Origin and six strap-on boosters built by Northrop Grumman, pulls away from Cape Canaveral carrying 40 Amazon Leo Internet satellites. Michael Cain/Spaceflight Now It was the first outright failure of a United Launch Alliance rocket since the company, a partnership between Boeing and Lockheed Martin, was formed in 2006. It was not immediately known what went wrong, but the Vulcan, the rocket that replaces ULA’s fleet of Atlas 5 rockets, will face a potentially significant grounding as engineers review telemetry and implement fixes for whatever caused the mishap. “There are risks to any launch, and that’s especially true for inaugural missions like LV-01,” Amazon Leo said in a post on X, using a designation that stands for Leo Vulcan Flight 1. “ULA has been a trusted partner to Amazon, and we believe they will learn from this mission and deliver on their long-term plans for Vulcan.” spoiled two previous flights. The solids appeared to function normally on Sunday, helping propel the rocket out of the dense lower atmosphere before burning up and falling. The two methane-burning BE-4 engines powering the Vulcan’s first stage continued the climb toward orbit, but appeared to fire more than expected under ULA’s pre-launch schedule. Following stage separation, the Vulcan’s hydrogen-fueled Centaur upper stage engines took over during a planned 12-minute, 15-second burn. According to the ULA update, something went wrong during the firing of Centaur, but no additional details were immediately provided. Sunday’s launch was the first of 38 Vulcan flights purchased by Amazon to launch its Leo satellites, designed to go head-to-head with Elon Musk’s Starlink and other space-based internet providers. ULA has already launched eight Leo flights using Atlas 5 rockets. Amazon has also booked 24 Leo launches aboard Blue Origin’s New Glenn rocket, 24 aboard Europe’s Ariane 6 and 13 aboard SpaceX’s Falcon 9. More than 3,300 Leo satellites will be needed to complete the constellation. Sunday’s flight would have brought the total number of launches to date to 436. But that was not the case. Instead, Amazon Leo will now have to wait for the ULA failure investigation to run its course before trying again with a Vulcan. The company is also waiting for Blue Origin, owned by Jeff Bezos, to fly its New Glenn rocket again after a catastrophic explosion on the pad last May. That failure was caused by a problem with an oxygen valve on one of New Glenn’s seven BE-4 first-stage engines. The BE-4, also built by Blue Origin, powers the Vulcan’s first stage, but the engines used on Sunday had been retrofitted with a fix by Blue Origin engineers. Racing away on a northeasterly trajectory across a cloudless blue sky, the Vulcan rocket put on a spectacular sky show over the weekend as it headed toward space. At this point, within the first two minutes of flight, there were no obvious signs of trouble. Michael Cain/Spaceflight Now While the cause of the failure is not yet publicly known, “ULA is committed to full transparency with our customers, and they will have visibility into the investigation process, which uses rigorous methodology and corrective actions,” the company said. NASA Administrator Jared Isaacman promised assistance if needed. “I appreciate you quickly keeping the public and your partners informed,” Isaacman wrote on the social media platform The 214-foot-tall Vulcan lifted off from Pad 41 at Cape Canaveral Space Force Station at 12:40 p.m. ET, flying on a northeastward trajectory on 3.8 million pounds of thrust from six Northrop Grumman strap-on solid-fuel boosters and two methane-burning BE-4s. A launch attempt on Friday was canceled after problems knocked out a nitrogen gas plant that supplies multiple launch suppliers. Another delay was ordered Saturday due to network issues between the Vulcan and ground systems. On Sunday, launch controllers requested a hold at the T-minus 20-second mark due to an unexplained technical problem with the rocket. By retargeting at the end of the launch window, ULA solved the problem, and the rocket roared to life and zoomed away at the end of the launch window. It is not yet known if the problem that interrupted the countdown played any role in the subsequent failure. In any case, the strap-on boosters helped propel the rocket out of the dense lower atmosphere, burning up and crashing about one minute and 40 seconds after liftoff. But the first stage seemed to burn hotter than anticipated in the company’s pre-launch schedule. The first stage also appeared to separate from the rocket’s hydrogen-fueled Centaur upper stage later than expected, and telemetry-based animation showed the Centaur making unusual guidance adjustments early in the burn. Months working to resolve issues with strap-on booster nozzles that occurred during two previous flights, one in 2024 and the other last February. While ULA was free to proceed with commercial flights, the US Space Force suspended launches of Vulcan national security payloads pending further analysis. “We have identified three credible causes (of the nozzle problem) and have taken positive steps to mitigate all of them,” ULA CEO Mark Peller told Aviation Week & Space Technology magazine in a pre-flight interview. The thrusters appeared to function normally on Sunday. As for the BE-4 engines, Peller said Blue Origin developed a “design improvement” to resolve the valve issue and performed a “retrofit” on the engines installed on the Vulcan Leo 1 rocket. “They were in our facility for probably a couple of months and we implemented that retrofit kit on the engines for this upcoming mission,” Peller said. “And they are working with us to review our engine inventory.” Go deeper with The Free Press on: