Low spin · most spun: New York Post 20/100 See every outlet’s spin ↓Photo as used by The Jerusalem Post for “Rocket from Boeing-Lockheed firm fails mid-flight, destroys payload of Amazon satellites”How The Jerusalem Post framed it: The Jerusalem Post uses an illustrative image of a Vulcan launch streaking through the sky above a marina. The dramatic night-time scene gives visual prominence to the rocket, though the caption identifies it as an earlier launch.
A Vulcan rocket carrying 40 Amazon Leo satellites failed to deliver them to orbit on Sunday. United Launch Alliance confirmed the mission failure after launch from Cape Canaveral in Florida. The cause had not been established.
How the coverage differs
The Jerusalem Post provides the most background on earlier Vulcan technical investigations and Amazon’s deployment timetable. The Verge alone mentions the 38 contracted Vulcan flights and quotes Amazon’s response, while the New York Post presents a shorter breaking-news account. None of the three mentions the eight earlier Amazon deployment missions on Atlas V.
About 10 minutesTime after launch when ULA said the anomaly occurredS1
What happened
A Vulcan rocket carrying 40 satellites for Amazon’s Leo internet network failed to reach its intended orbit on Sunday. United Launch Alliance, the Boeing–Lockheed Martin joint venture, confirmed that an anomaly occurred about ten minutes after launch from Cape Canaveral Space Force Station in Florida.S1S2S3
ULA said it did not yet have enough information to explain what had happened. Reuters reported that the satellites were destroyed. The company said it planned to investigate the failure and return to flight as quickly as possible.S1S2
Why it matters
This was Amazon’s first flight on Vulcan, rather than the first launch of its satellite network. ULA’s mission overview records eight earlier Amazon deployment missions using its Atlas V rocket. The failed flight was intended to begin a series of 38 Vulcan launches for Leo.R1S3
The distinction matters for the deployment figures. Reuters says Amazon had already placed 398 Leo satellites in orbit across 14 launches since 2025. The 40 satellites aboard Sunday’s rocket were an additional batch; the failure does not mean that Amazon lost the spacecraft already deployed.S1
Amazon’s earlier launch plan also shows what is now uncertain. Before the failure, it expected the second Vulcan mission within weeks of a successful first flight. That expectation was explicitly conditional. The sources reviewed do not establish a replacement date or how long the investigation will take.R2S1
The background
Vulcan first flew in 2024, and Sunday’s mission was its fifth, according to Reuters. Its previous flight was nine months earlier. Two earlier missions had experienced solid-booster problems but still delivered their payloads, a different outcome from the loss of Sunday’s Amazon mission.S1
In a pre-launch update, ULA said it had investigated the February booster-nozzle anomaly and introduced changes to the nozzle’s design and manufacture. It said further analysis and testing would continue alongside the flight programme. Those statements concern the earlier problem; they do not establish the cause of this failure.R3
Reuters also described earlier work on Vulcan’s Blue Origin-supplied BE-4 engines. It said Sunday’s problem appeared to occur after separation of the first stage from the satellite-carrying second stage, while stressing that any engine involvement was unclear. The timing alone does not identify a faulty component.S1
What happens next
ULA has committed to investigating and returning to flight, without announcing a timetable in the statements reviewed. Amazon, in a response quoted by The Verge, expressed confidence in its launch partner and said it expected ULA to learn from the mission. That is Amazon’s assessment, not a finding about the technical cause.S2S3
Fact check: every point labelled
What is confirmed, what is only reported, and what is claim or speculation. Every point links to its source.
What we know
On the record or independently reported by more than one outlet.
confirmedULA confirmed an anomaly about ten minutes after launch from Cape Canaveral’s Space Launch Complex 41 and failure to deliver the Amazon mission to orbit.S1S2S3
confirmedThis was the first Amazon Vulcan mission in a contracted series of 38; eight earlier Amazon deployment missions used Atlas V.R1
Reported but not yet confirmed
Reported as fact, but from a single origin.
reportedReuters: The payload comprised 40 Amazon Leo satellites, which were destroyed.S1
reportedReuters: ULA is a Boeing–Lockheed Martin joint venture; Vulcan debuted in 2024 and this was its fifth mission and first in nine months.S1
reportedReuters: Amazon had deployed 398 satellites across 14 launches since 2025.S1
reportedReuters: Two previous Vulcan flights experienced solid-booster problems but successfully delivered their payloads.S1
reportedReuters: BE-4 engines had undergone earlier corrective work; Sunday’s anomaly appeared to follow stage separation, but engine involvement was unclear.S1
Claims and disputes
What people say. Not established fact.
claimedUnited Launch Alliance: The cause was not yet known; ULA planned to investigate and return to flight as quickly as possible.S1S2
claimedAmazon, before launch: The second Vulcan mission was expected within weeks of a successful first mission.R2
claimedUnited Launch Alliance, before launch: The February nozzle anomaly had been investigated and changes to design and manufacture incorporated, while testing and analysis continued.R3
claimedAmazon: ULA remains a trusted partner and will learn from the mission.S3
Still unknown
The cause of the failure and the date of Vulcan’s next launch have not been established.
Key questions
What happened to the Amazon satellites?
ULA confirmed that the mission failed to deliver them to orbit. Reuters reported that all 40 were destroyed.S1
What caused the Vulcan failure?
The cause had not been established. Earlier booster and engine investigations do not by themselves explain this mission’s failure.S1R3
Was this Amazon Leo’s first satellite launch?
No. It was the first Leo mission on Vulcan. ULA records eight previous Amazon deployment missions using Atlas V.R1
Spin meter
How each outlet framed this story, scored on the wording and choices in that article, not on the outlet’s reputation.
Headlines compared: The Jerusalem Post highlights the rocket venture’s Boeing and Lockheed Martin ownership, while the New York Post names ULA and emphasises a ‘total mission failure’. The Verge uses a shorter headline focused on the Vulcan rocket and Amazon satellites; all three describe the satellites as lost or destroyed, beyond the established fact that the mission failed to reach orbit.
New York PostFraming: Not political · Spin 20/100 · Headline matches story: partly
“ULA loses 40 Amazon Leo satellites in ‘total mission failure’ minutes after rocket launch”
Straight reportingHeavy spin
The New York Post leads with the loss of the satellites and ULA’s initial response in a short breaking-news report.
Why? 2 framing techniques
emphasistotal mission failure The headline stresses the scale of the failure, while the text describes an anomaly and does not use that phrase.
omission The report does not mention the 38 contracted Vulcan missions or the eight earlier Amazon deployment missions on Atlas V.
The Jerusalem PostFraming: Not political · Spin 18/100 · Headline matches story: yes
“Rocket from Boeing-Lockheed firm fails mid-flight, destroys payload of Amazon satellites”
Straight reportingHeavy spin
The Jerusalem Post frames the failure as a setback for ULA’s rocket programme and Amazon’s satellite network.
Why? 2 framing techniques
emphasisRocket failures threaten Amazon's satellite deployment plans The article emphasises the wider commercial setback alongside the confirmed launch failure.
omission The article does not mention the eight earlier Amazon deployment missions flown on Atlas V or the 38 contracted Vulcan missions.
The VergeFraming: Not political · Spin 14/100 · Headline matches story: yes
“Vulcan rocket fails, destroying 40 Amazon Leo satellites”
Straight reportingHeavy spin
The Verge frames the failure around Amazon’s satellite ambitions and includes both ULA’s and Amazon’s responses.
Why? 2 framing techniques
emphasisit has struggled to get off the ground so far The Verge places the failure in the context of Amazon’s slower satellite deployment relative to Starlink.
omission The article does not mention the eight earlier Amazon deployment missions flown on Atlas V.
This story was written and checked by AI agents using only the sources above, then published automatically. Facts are labelled by how well they are supported. If something is wrong, tell us: we check every report against the sources and publish corrections. Editorial policy
Vulcan launch fails to deliver 40 Amazon Leo satellites to orbit | NoDirection News