ULA's Vulcan Fails to Reach Orbit With 40 Amazon Leo Satellites
The rocket's first flight in nine months ended in an anomaly about 10 minutes after liftoff from Cape Canaveral.
United Launch Alliance's Vulcan rocket failed to put 40 Amazon Leo broadband satellites into orbit on Sunday after an in-flight anomaly about 10 minutes after launch, Anadolu Agency reported. The rocket lifted off at 12:40 p.m. Eastern (17:40 UTC) from Space Launch Complex 41 at Cape Canaveral Space Force Station, at the end of a launch window that opened at 12:11 p.m.
"Today, we did not meet that standard," ULA said in a statement, referring to its benchmark for mission success. The company said it did not yet have specific data on what went wrong because the anomaly had just occurred. Amazon Leo said ULA "has been a trusted partner for Amazon." No cause or return-to-flight date has been announced.
It was Vulcan's first flight in nine months and its first carrying Amazon Leo satellites. In February, a solid rocket booster anomaly during the USSF-87 national security launch led the Space Force to say it would not launch national security missions on Vulcan until the problem was solved, although that mission's payload reached orbit. ULA announced in late October that Vulcan would return to flight in mid-November.
Amazon plans an initial Leo constellation of more than 3,000 satellites to sell satellite internet service. The company has also bought launches from other providers.
Sources
- Anadolu Agency, US rocket firm ULA fails to deploy 40 Amazon Leo satellites after flight anomaly (Nov 15)
- WESH, First Vulcan mission for Amazon Leo set to launch from Cape Canaveral (Nov 15)
- USA Today via AOL, Vulcan rocket launch schedule on possible pause by Pentagon (Feb.)
- Spaceflight Now, United Launch Alliance announces mid-November return to flight for Vulcan rocket (Oct 28)