Blue Origin rocket experiences anomaly during ground test

Blue Origin’s New Glenn suffered an anomaly during a May 28 static fire test at Cape Canaveral, with video appearing to show an explosion on the launchpad. No personnel were injured, but the event follows an earlier April 19 mission failure that triggered an FAA investigation and could delay the rocket’s return to flight and its planned mission carrying 48 satellites for Amazon Leo. NASA and the FAA both said they are aware of the incident and a root-cause investigation is underway.

Analysis

This is less a one-off launch mishap than a sequencing problem for a program that was already operating with minimal margin for error. A second major anomaly in quick succession increases the odds of a longer stand-down, which matters because heavy-lift launch schedules are highly path-dependent: each slip pushes revenue, payload recognition, and customer confidence into the next quarter. For ASTS, the near-term hit is not just the delayed payload; it is the widening gap between commercial ambition and available launch cadence, which can force more conservative assumptions into financing and deployment timelines.

The second-order loser is the ecosystem around clustered satellite deployment. If a single launch platform becomes less dependable, buyers with time-sensitive constellations will diversify away from it, benefiting incumbent launch providers and any vehicle with a cleaner reliability narrative. That can also ripple into suppliers and insurers: repeated pad-side anomalies tend to raise premia, tighten warranty terms, and increase contingency inventory requirements for mission hardware and ground support.

The key catalyst is the investigation timeline, not the headline. In the next few days, expect estimate revisions on launch cadence and a higher probability of schedule slippage for downstream payloads; over the next few months, the market will focus on whether the company can re-establish a credible test-to-flight rhythm or whether this becomes a multi-quarter qualification reset. If management can isolate a non-systemic root cause quickly and demonstrate a clean corrective action, the stock reaction in launch-adjacent names can reverse sharply; absent that, the overhang likely compounds into the next manifest update.

The contrarian angle is that the damage may be more reputational than structural if the anomaly proves confined to ground-test configuration rather than core flight hardware. In that case, the market may be overpricing a prolonged outage when the real effect is a few weeks of delay, not a program setback. But until the failure mode is known, the better asymmetry is to fade names whose near-term valuation depends on uninterrupted launch execution rather than to bottom-fish into the uncertainty.

Key Decisions for Investors

• Short ASTS for 2-6 weeks or buy put spreads into the next launch-manifest update; thesis is delayed constellation deployment and higher financing overhang, with upside risk limited if Blue Origin resets quickly.
• Long RKLB vs short ASTS as a launch-execution relative-value pair over 1-3 months; own the vehicle with more diversified demand and less single-counterparty dependence.
• Reduce exposure to launch-adjacent suppliers/ground-support names for 1-2 weeks until root-cause clarity; anomalies at this stage typically expand into procurement and insurance friction before they hit revenue.
• If using options, buy longer-dated ASTS puts rather than shorting outright; the risk/reward favors convexity because a clean investigation can produce a sharp relief rally.