Home / Case Studies / NG-4 Blast & Debris Analysis
Forensic Engineering · Open-Source Analysis

New Glenn NG-4 — Blast & Debris Forensic Analysis

This is our best effort at reconstructing what happened at LC-36, Cape Canaveral on 28 May 2026 — built entirely from public footage, frame by frame, and now cross-checked against a second, independent camera. Two cameras, the same physics: where they agree we hold the result with more confidence; where they diverge, we widen the error bars and say so. No insider data — just geometry, physics, and careful measurement. Every figure here is a considered estimate, not the final word.

Event
28 May 2026
Location
LC-36, CCSFS, Florida
Propellant
1,815 t LOX / LCH₄
Methods
Sedov-Taylor · Kinney-Graham · Roberts · ballistic tracking
Sources
2 independent cameras
Range Safety & Licensing

The safety system worked

New Glenn's static fire failure released energy equivalent to roughly 200 tonnes of TNT. A 500-metre fireball burned for 35 seconds. And yet: no personnel casualties, no structural damage beyond 375 metres, critical infrastructure intact. That outcome doesn't happen by accident — it is the result of quantity-distance analysis, hazard zoning, and safety case work done long before the vehicle arrived at the pad.

Star Industry has contributed this kind of analysis to real programmes — including work supporting licensing for Orbex Prime and Sutherland Spaceport. Range safety analysis and safety case development is a service we offer to launch operators, spaceport developers, and regulatory applicants. Get in touch to discuss your programme needs.

Reconstructed Sequence · Two Cameras

Chain of events

Times are relative to the initiating anomaly: t = 0 is the first frame showing flame above the launch platform (the prior frame still shows the water deluge active, ignition imminent). Reconstructed from two independent fixed cameras at broadly similar locations (~9–9.5 km, similar bearing); what differs between them is framing and exposure, not vantage point — so this is a cross-check on measurement and processing, not a parallax solution. Distances are stated as minima — motion is assumed perpendicular to each camera's line of sight. Each step links to the detailed section below.

A two-stage, thermally-dominated deflagration. A primary base fire burns through into a secondary bulk propellant release, which deflagrates as a vapour-cloud explosion. Because ignition was continuous, the cloud never accumulated into a detonable charge: the front stayed subsonic, overpressure was modest, and thermal radiation from the several-hundred-metre fireball governed. Two independent camera angles place the event in the same regime — the disagreements are in magnitudes, not in kind.
Independent Cross-Check

Where the two cameras agree — and where they don't

A second, independent camera was run through the same pipeline. Both cameras sat at broadly similar locations and bearings — they differ in framing and exposure, not vantage point — so this is a check on measurement and processing rather than a true multi-angle (parallax) solution. Agreement firms up a result; divergence widens its error bars. Below, “reinforced” means the two solutions land within tolerance; “diverges” means the figure carries more uncertainty than a single camera would suggest.

ParameterCamera A · fixed (~9 km)Camera B · drone (~9.5 km)Verdict
Regimedeflagration (R ∝ t¹∙⁰)deflagration (slope 0.12)✓ Reinforced
TNT-equivalent yield~210 t (~5%)~215 t (~5%)✓ Reinforced
Peak front speed322 m/s (Mach 0.94)210 m/s (Mach 0.61)~ Both subsonic; magnitude diverges
Fireball diameter~495 m~415 m (Roberts 425)△ Diverges → widen band
Fireball duration~35–40 s (timed off video)~22 s (Roberts model)— Not a frame measurement; indicative only
Origin height~18 m (±17)29 m (±15), base initiation✓ Consistent within error
Min. debris range~700 m~1.0–1.05 km△ Diverges → use larger
Damage validation (170/320/375/450 m)consistentconsistent✓ Reinforced

On 28 May 2026, Blue Origin's New Glenn vehicle — a 98-metre-tall rocket loaded with 1,815 tonnes of liquid oxygen and liquid methane — exploded during a static fire test at Launch Complex 36. Local news station WRAL captured the event on a fixed camera, providing a side-on view from several kilometres away.

This analysis uses that footage, supplemented by pre- and post-event Planet Labs satellite imagery and Google Maps measurements, to reconstruct the blast wave, estimate the explosion energy, and determine where on the vehicle the failure originated.

No proprietary data, Blue Origin internal documents, or government reports were used. Every number derives from publicly available sources and first-principles physics.

Scale calibration The two lightning protection masts flanking the pad are 73 m apart, spanning 61 pixels in the raw frame — giving 1.197 m/px. The explosion origin was fixed to the tower midpoint horizontally, and determined from circle-fitting blast arcs across 10 early frames in the vertical direction, arriving at a point ~28 m above pad-ground level (±17 m).
01
Annotate the shock front

The blast arc was traced in 13 unique frames from t = 4.0 to 4.8 s. Where hidden by the fireball, the arc was extrapolated by eye using the known symmetry of an expanding sphere.

02
Fit circles, find origin

A geometric circle was fitted to each frame's arc. The fitted centres, stable across early frames (std ±17 m), give the explosion origin — constrained to the tower midpoint in x.

03
Extract R(t), fit blast physics

Radius vs time gives blast front velocity. Its rate of deceleration identifies the blast regime: Sedov-Taylor strong shock (R ∝ t⁰·⁴), acoustic (R ∝ t), or — as seen here — late-stage acoustic decay.

04
Cross-check with observed damage

Tanks at 170 m (no damage), integration facility at 320 m (no damage), tented structure at 375 m (blast damage), and trees at ~450 m (thermal scorching in satellite imagery) each validate a different part of the model.

Per-frame blast arc grid with fitted circles
Fig 1 — Each panel shows a unique video frame (S5–S24), colour-coded blue→red chronologically. The ink-annotated shock front arc, fitted circle, and hybrid origin are shown. The dotted circle is fitted to the raster ink point cloud with the tower midpoint as the x-constraint.
322
m/s Phase 1
t=4.0–4.4 s
Mach 0.94
274
m/s Phase 2
t=4.6–4.8 s
Mach 0.80
335
m phase kink
at t ≈ 4.44 s
0.973
r² Phase 1
linear fit

Both phases are subsonic throughout the measurement window — the blast front was already below the speed of sound at t = 4 s, meaning the acoustic transition occurred before the camera captured anything useful. The Sedov-Taylor strong-shock phase was over well before 4 seconds.

The slight kink in R(t) at ~335 m reflects a change in acoustic decay rate as the pressure pulse spreads into an ever-larger volume of air. It is not a Mach 1 crossing — both phases are firmly subsonic.

The overall R ∝ t¹·⁰ relationship (rather than R ∝ t⁰·⁴ of Sedov-Taylor) confirms we are observing a decaying far-field blast, not the prompt shock of a detonation.

Why not Sedov-Taylor? The Sedov-Taylor scaling law — used to estimate nuclear weapon yields from photography — predicts R ∝ t⁰·⁴. Here we see R ∝ t¹·⁰, the acoustic limit. This confirms the strong-shock phase ended before our first frame, which in turn confirms the explosion was a deflagration, not a detonation.
R(t) blast wave radius vs time
Fig 2 — Shock front radius R versus time (fixed camera). Phase 1: 322 m/s, Mach 0.94, r² = 0.973. Phase 2: 274 m/s, Mach 0.80, r² = 0.941. Error bars = std of point distances within each fitted circle. Hybrid origin used throughout.
Both cameras · data overlaid

The drone angle traces the front at 210 m/s (Mach 0.61) decaying to 16 m/s, with a log–log R(t) slope of 0.12 — far below the Sedov–Taylor 0.4 of a strong shock. The original fixed camera measured a faster front (322 m/s, Mach 0.94). Both remain firmly subsonic, so the deflagration conclusion is reinforced; the absolute front speed carries more uncertainty between the two cameras.

Why the speeds differ. Front velocity is the least robust quantity here — it is a derivative, recovered by differentiating a noisy radius–time curve over a front that decelerates sharply in its first instants. Three things plausibly drive the ~Mach 0.3 gap, all tied to the cameras differing in framing and exposure rather than position: (i) exposure — a brighter or longer exposure records more of the faint, fast leading edge, so the luminous front appears to expand further per frame and reads as a higher velocity; (ii) time-zero alignment — catching the usable inked frames a fraction of a second earlier samples a faster part of the decay; and (iii) scale calibration — each camera carries ~±8% on its m/px, which maps linearly onto velocity. None of these change the regime: both log–log slopes sit far below Sedov–Taylor, so both cameras independently see a deflagration, not a shock.

Blast-front R(t) — both cameras overlaid on one axis
Both cameras — Fitted blast-front R(t) for both angles on one axis. Both fronts stay well below Mach 1 throughout — the deflagration regime is shared; only the absolute speed differs. Lines are the published two-phase fits (per-frame scatter was not available to overlay).

The lightning protection masts (182.88 m / 600 ft tall) serve as a vertical ruler in the image. At a camera distance of several kilometres, perspective distortion over the vehicle height is less than 1°, so the horizontal pixel scale applies equally vertically.

The mast tops appear at y = 660 px. Projecting down using the known mast height gives mast-base ground level at y = 819 px. The explosion origin at y = 794.8 px sits 28 m above mast-base ground.

The launch platform itself is elevated above that reference level — estimated at approximately ~10 m by comparing mast and platform shadow lengths in Google Maps satellite imagery at the same sun angle. This estimate carries its own uncertainty of similar magnitude, and we treat it as a round-number correction. Subtracting it, the explosion origin sits approximately ~18 m above the launch platform surface — the true base of New Glenn — with a ±17 m uncertainty.

At ~18 m above the vehicle base, the origin straddles the boundary between the BE-4 engine section (0–15 m) and the base of the lower booster / propellant tank section (15–60 m). The wide uncertainty band means no firm distinction between the two is possible, but the central estimate points to the engine/booster interface.

~10m
Platform elevation
(shadow est.)
~18m
Above platform
±17 m
~18%
Up New Glenn
range 1–36%
Structural context New Glenn first stage: engines (0–15 m) → lower booster / tanks (15–60 m) → interstage (60–68 m) → upper stage (68–98 m). The ~18 m central estimate sits right at the engine-booster interface. The ±17 m uncertainty band spans most of the engine section and the base of the booster.
Explosion-origin estimate on the New Glenn stack — both cameras
Fig 3 — Explosion-origin estimate on the 98 m stack, both cameras. Camera A (fixed): ~18 m above base (±17 m). Camera B (drone): ~29 m (±15 m), marking the luminous-fireball centroid — which sits high because the fireball rises; the initiation itself appears to be at the base. The overlapping bands straddle the engine / lower-booster interface.

New Glenn carried 395 t of liquid methane (LCH₄) and 1,420 t of liquid oxygen at a mixture ratio of 3.6:1. The lower heating value of methane gives a total chemical energy of 19.75 TJ — equivalent to 4,720 t of TNT if every molecule reacted perfectly.

In practice, an explosion converts only a fraction of its chemical energy into blast wave. This fraction — the blast efficiency — separates a slow fire from a city-levelling detonation. Our measurement is consistent with a blast efficiency of roughly 4–6%, giving an effective yield of ~210 t TNT — characteristic of a moderately energetic vapour cloud explosion.

It is worth noting that this measured efficiency is considerably lower than values used in regulatory licensing. US DoD and FAA standards for LOX/hydrocarbon propellants at launch pads use 20% TNT equivalence as the baseline for quantity-distance calculations. For LOX/LNG (methane) specifically, NASA's interim blast model notes the potential for methane-oxygen mixtures to behave as a sensitive high explosive under certain mixing conditions, adding further uncertainty that justifies the conservative regulatory approach. The gap between the measured ~210 t and the licensing basis ~944 t (20% of 4,720 t) is not a discrepancy — it is the difference between what happened in this particular event and the worst-credible-case that must be bounded for public safety.

ScenarioEfficiencyYield
Poor deflagration1%47 t
Typical VCE2%94 t
This explosion (est.)~4–6%~210 t
Near-DDT transition10%472 t
FAA / DoD launch pad standard20%940 t
Detonation (e.g. ANFO)~40%1,888 t
Some solid / confined systems100%4,720 t
Beirut 2020 (ref.)~1,100 t
Regulatory context US DoD and FAA standards for LOX/hydrocarbon launch pads require 20% TNT equivalence for quantity-distance calculations — ~10× more conservative than the ~4–6% measured here. This is the worst-credible-case that must be bounded to protect the public, not a prediction of what will happen.
Overpressure vs distance
Fig 4 — Peak overpressure versus standoff distance (linear R, log P). Five yield scenarios spanning 2–100% blast efficiency. Green band = measured range. Damage thresholds from NFPA / UFC 3-340-02.
Both cameras · data overlaid

The drone camera independently returns ~215 t TNT-equivalent (~5% VCE efficiency), against ~210 t from the fixed camera (100% chemical yield ≈ 4,340 t vs 4,720 t). Strongly reinforced — two independent geometries land within ~2% on yield, and both sit far below the regulatory detonation curves.

Overpressure vs distance — both cameras
Both cameras — Kinney–Graham peak-overpressure curves for the two measured yields (200 t / 215 t) — they fall within ~2% of each other. Observed damage at 170–450 m lies orders of magnitude below even these detonation curves, confirming a deflagration. Dashed grey: 20% and 100% planning bounds.

The explosion produced a fireball that grew to approximately ~495 m diameter before rising and dispersing, burning for a duration timed by eye off the live video at ~35–40 s. That duration is indicative only — neither set of screengrabs spans the full burn, so it is not a photogrammetric measurement (for comparison, the Roberts correlation predicts ~22 s). The diameter, by contrast, was measured from the video frame at maximum extent: the left edge extends off-screen, so the right-side half-width from the origin was doubled assuming symmetry.

These observed values bracket the predictions of standard fireball correlations — Roberts (1982), Moorhouse & Pritchard, and TNO Yellow Book — all developed for hydrocarbon releases of roughly 1–10 tonnes. Extrapolating nearly 400× beyond their calibration range, the agreement within 15–20% is notable.

The slightly larger measured diameter likely reflects the LOX co-oxidiser providing additional internal oxygen, making combustion more complete — and the fireball marginally bigger and longer-burning — than a pure hydrocarbon release would produce.

CorrelationDiameterDuration
Roberts (1982)425 m33 s
Moorhouse & Pritchard360 m46 s
TNO Yellow Book450 m30 s
Measured (video)~495 m~35–40 s*

* Duration timed by eye off the live video — neither camera's frame set spans the full burn, so this is indicative only, not a photogrammetric measurement.

Calibration note All correlations calibrated on 1–10 t hydrocarbon releases. New Glenn carried ~395 t of LCH₄. Agreement within 15–20% at 400× the calibration mass validates these correlations for order-of-magnitude thermal hazard estimation at this scale.
Fireball at maximum extent
Fig 5 — The fireball at or near maximum extent from the WRAL footage. The left edge extends beyond the frame; assuming symmetry about the explosion origin (x = 146.5 px), the measured right half-width gives a total diameter of ~495 m. Scale: 61 px = 73 m.
Second camera · drone footage (~9.5 km)

Measured on the detached, near-spherical fireballs, the drone camera gives a ~415 m diameter — within ~2% of the Roberts model (425 m); the fixed camera measured ~495 m. The diameters diverge here, so the size band should be widened, with the drone figure the closer match to first-principles correlations. On duration, neither camera is authoritative: neither set of screengrabs spans the full burn, so the ~22 s is the Roberts-model prediction and the ~35–40 s was timed by eye off the live video — both are indicative, not photogrammetric measurements.

Maximum detached fireball extent ≈ 415 m (drone camera).
Cam B — Maximum detached fireball extent ≈ 415 m (drone camera).
DistanceStructureOutcomeΔP (200 t)Thermal fluxDominant hazard
170 mPropellant / pressurant tanks✓ No damage0.87 kPa250 kW/m²— (steel: threshold >10,000 kPa)
320 mIntegration facility✓ No damage0.25 kPa110 kW/m²— (RC concrete: robust to both)
375 mTented structure⚠ Blast damage0.19 kPa80 kW/m²Blast (fabric fails at ~0.1–0.3 kPa)
450 mTrees (satellite imagery)🔥 Thermal scorching0.14 kPa56 kW/m²Thermal (veg. ignition ~12 kW/m²)

The survival of steel pressure tanks at 170 m while a tented structure at 375 m was damaged resolves through material thresholds: steel pressure vessels survive tens of thousands of kPa, while tented fabric fails at as little as 0.1–0.3 kPa. Both outcomes are consistent with the same blast yield.

More revealing is the tree scorching at 450 m. The blast overpressure there is 0.14 kPa — below any structural threshold. But the thermal flux from a ~500 m fireball burning for 35 seconds is approximately 56 kW/m² at that distance — well above the ~12 kW/m² threshold for vegetation ignition.

Beyond ~300–400 m, thermal radiation was the dominant hazard. This is the defining signature of a large VCE / deflagration. A detonation shows exactly the inverse relationship.

Energy partitioning With ~5% blast efficiency, approximately 1 TJ went into the shock wave. But roughly 35% of the total chemical energy — around 7 TJ — was radiated as heat from the fireball. That is seven times more thermal energy than blast energy. Conventional high explosives convert ~40% to blast and ~10% to heat: the exact opposite ratio.
Thermal radius Predicted vegetation ignition radius (Roberts model): ~950 m. Observed: ~450 m. The discrepancy likely reflects incomplete fuel participation — not all propellant joined the fireball simultaneously.
Blast overpressure vs thermal flux
Fig 6 — Blast overpressure (left axis) and thermal flux (right axis) versus standoff distance. Observed damage markers on both axes. Blast model: Kinney-Graham. Thermal model: Roberts (1982) fireball correlation.
~85
m/s ejection
(lower bound)
at ~68° elevation
~360
m apogee
~10 s after event
~310 m downrange
650–770
m impact range
incl. scale
uncertainty
2.5%
landmark ratio
error (geometry
validated)

Alongside the blast and thermal hazards, the footage shows numerous incandescent fragments thrown clear of the fireball. One bright fragment was tracked across 8 consecutive frames, one second apart, to reconstruct its trajectory and estimate where it came down.

The scale is anchored to the 73 m separation of the two lightning masts (measured from satellite imagery via two independent workflows). This horizontal baseline is chosen over the towers' height — it needs no estimate of ground level or of the tower tops, which bloom into the fireball. To pin the scale and check the camera geometry, three landmarks at known coordinates (the masts, a water tower, and the Cape Canaveral lighthouse) were measured in a clearer frame: the observed pixel-separation ratio (lighthouse-to-tower vs water-tower-to-tower) matched the prediction from their surveyed positions to 2.5%, confirming the camera location (~9.1 km SSW) and that the view is within ~6° of broadside to the mast line — so the parallax (foreshortening) correction is negligible (~0.99) and the on-screen mast gap is the full 73 m. Fragment positions were then measured against this validated scale; the integration facility base sets the altitude datum.

The eight points trace a clean ballistic arc — apogee ~360 m, reached roughly 10 s after the event (video t ≈ 24 s; event onset taken as t ≈ 14 s). The per-second vertical drop accelerates consistent with gravity, confirming ballistic motion. Projecting the descending limb forward to the ground gives an impact of ~650–770 m: the spread combines the drag-vs-no-drag fall with the residual (few-pixel) scale uncertainty.

Two independent checks support the reconstruction. First, the landmark geometry: surveyed coordinates predict the on-screen spacing of three reference points to 2.5%. Second, the back-extrapolation: tracing the fitted arc backwards returns it to the launch vehicle near the mast midpoint. The measured arc and the geodetically-anchored scale converge on an origin at the pad, where the rocket stood.

01
Track the fragment

One bright fragment located in 8 frames, 1 s apart, against the WRAL footage. Position read in each frame relative to fixed pad structures.

02
Scale & datum

73 m mast separation (satellite-confirmed, geodetically cross-checked to 2.5%) sets the horizontal metres-per-pixel; integration facility base sets the altitude datum.

03
Fit the arc

Altitude vs downrange distance fits a parabola. Per-second vertical drop accelerates consistent with gravity — confirming ballistic motion.

04
Project & back-trace

Forward to impact (drag and no-drag bracket); backward to origin as an independent check — the arc returns to the launch vehicle.

Ejection velocity From the apogee height (energy method) and the ~10 s rise time (event onset at t ≈ 14 s), the vertical launch component is ~80 m/s, for a total ejection speed of ~85 m/s at ~68° above horizontal. This is a lower bound — drag during the climb means the true value is somewhat higher.
Scale reference: lightning towers and integration facility
Fig 7 — Scale reference, pre-fireball frame. The two lightning masts (73 m apart, satellite-confirmed) provide the horizontal scale; the integration facility base sets the altitude datum. Three surveyed landmarks (masts, water tower, lighthouse) cross-check the scale and camera geometry to 2.5%.
Reference distance (DESR 6055.09)ValueFragment vs reference
Default storage hazardous fragment distance (HFD)381 m (1,250 ft)Fragment ~1.7–2.0× beyond
Estimated fragment impact650–770 m— (this analysis)
Emergency withdrawal — facilities1,219 mFragment falls short
Emergency withdrawal — railcars1,524 mFragment falls short
Robust-munition maximum fragment distance (MFD)2,251 m (7,385 ft)Well within

Placing the result against US DoD explosive-safety separation distances (DESR 6055.09) is instructive. The estimated impact at ~650–770 m is roughly 1.7–2.0× the default storage hazardous fragment distance of 381 m. It falls within the emergency-withdrawal distances and well within the maximum-fragment-distance figures, so it sits comfortably inside the site's wider explosive perimeter.

The point that has always quietly nagged at me: the standard hazardous fragment distance is treated as effectively bounded above a certain net explosive weight. Yet here is a single fragment, from a vehicle far in excess of that quantity, landing at up to roughly twice that bound. Containment still held — it stays well within the site's wider explosive perimeter, so this is not a safety finding. But it is a tangible reminder that the bounded-distance assumption and the physics of a very large energetic event do not sit together quite as tightly as the tidy number implies.

Why this matters Fragmentation is the third hazard mode alongside blast overpressure and thermal radiation. Unlike those two — which decay smoothly with distance — a single energetic fragment can deposit its hazard at a discrete point far outside the blast and thermal contours, as this one did.
Caveats Every distance is a minimum: the analysis assumes the fragment travelled perpendicular to the camera line of sight. At the ~9.1 km camera range this depth ambiguity is small (a few percent), but it is a contributor to the residual uncertainty, captured in the 650–770 m band. It is also a single fragment, not the full debris field.
Debris fragment trajectory with DESR reference distances
Fig 8 — Reconstructed fragment trajectory (t = 0 at event onset), scaled to the 73 m mast separation (geodetically validated to 2.5%; parallax negligible). Orange: parabola fitted to the 8 measured points; purple: extrapolated arc (ascending limb and no-drag descent); blue: drag-projected fall. Shaded band: impact range (650–770 m) combining drag and residual scale uncertainty. Red vector: ejection velocity. Dotted: DESR 6055.09 storage HFD (381 m). The fitted arc back-extrapolates to the vehicle.
Both cameras · data overlaid

Tracking a fragment through zoom-corrected frames, the drone camera gives a minimum impact range of ~1.0–1.05 km (ejection ~95 m/s @ 48°, apogee ~250 m, vertical acceleration −8.3 m/s² ≈ g) — about 2.6× the 381 m DESR 6055.09 hazardous-fragment distance, but short of the 1,219 m emergency-withdrawal distance. The fixed camera tracked a fragment to ~700 m. These diverge — most likely because each camera tracked a different fragment (see below).

Why they differ. With the per-frame tracks in hand, both arcs are internally consistent parabolas — so this is not one camera failing to close. The fixed camera tracked a steeper, slower fragment (ejection ~85 m/s at ~68°, apogee ~364 m) landing near ~700 m; the drone tracked a shallower, faster one (~95 m/s at ~48°, apogee ~250 m, vertical deceleration −8.3 m/s² ≈ g) carrying to ~1.0–1.05 km. Those launch geometries are too different to be the same object — and with the fixed camera’s coarse 1-second frame interval and a different scale calibration (1.62 m/px vs 0.88 m/px), the two almost certainly tracked different fragments. For siting, the governing number is the larger range — take ~1 km as the minimum.

Debris fragment trajectory — both cameras, measured tracks + ballistic fits
Both cameras — Measured per-frame tracks (★ = apogee) and fitted ballistic arcs. Steeper fixed-camera fragment (apogee ~364 m) lands ~700 m; shallower drone fragment (apogee ~250 m) carries to ~1.0–1.05 km — almost certainly different fragments. Dotted line: DESR 6055.09 hazardous-fragment distance (381 m).
Deflagration — what happened

Subsonic flame propagation

Combustion front travels at subsonic speed through the vapour cloud, building pressure progressively. Blast efficiency ~4–6%. Large, long-burning fireball. Thermal hazard extends further than structural blast damage.

Detonation — what didn't happen

Supersonic shock initiation

A supersonic shock wave initiates combustion in microseconds. Blast efficiency 30–50%. Compact, brief fireball. Structural blast damage dominates at distance. Characteristic of confined high explosives or deliberately initiated events (e.g. Beirut 2020).

  • Blast speed was subsonic from the first frame (Mach 0.94 at t = 4 s). Detonation-driven blast waves are supersonic for far longer and at greater radii.
  • Blast efficiency of ~5% is typical of unconfined vapour cloud explosions. Detonations achieve 30–40%.
  • Thermal damage extends further than structural blast damage — trees scorched at 450 m while the integration facility at 320 m was undamaged.
  • Fireball diameter (~495 m) consistent with large hydrocarbon fireball correlations, not a compact detonation event (duration ~35–40 s timed by eye — indicative only).
  • Physically expected: cryogenic LCH₄/LOX requires controlled vaporisation and mixing to detonate. An accidental release is extremely unlikely to achieve detonation conditions.
Six-panel complete analysis
Fig 9 — Complete six-panel analysis: R(t) with two-phase fits; log-log regime identification; overpressure vs distance; New Glenn height schematic; TNT equivalence table; analysis summary.
Second camera · drone footage (~9.5 km)

Both reconstructions converge on the same regime: a two-stage, thermally-dominated vapour-cloud deflagration. The headline call is robust across two independent cameras — the differences are confined to specific magnitudes (fireball size/duration, front speed, debris range), which the cross-validation table above flags explicitly.

Six-panel summary from the independent drone-camera reconstruction.
Cam B — Six-panel summary from the independent drone-camera reconstruction.
Physical models used
  • Sedov-Taylor blast scaling (1950)
  • Kinney-Graham overpressure model (1985)
  • Hopkinson-Cranz scaled distance
  • Rankine-Hugoniot shock relations
  • Roberts fireball correlation (1982)
  • TNO Yellow Book fireball model
  • Geometric circle fitting (orthogonal-distance least squares)
Data sources (all open)
  • WRAL News camera footage (25 fps, YouTube)
  • Planet Labs satellite imagery (pre/post event)
  • Google Maps satellite view (structure distances, shadow measurements)
  • Blue Origin public specifications (propellant mass)
  • NFPA / SFPE damage threshold tables
  • UFC 3-340-02 blast effects on structures
  • Camera geometry. All measurements assume the WRAL camera is viewing roughly horizontally. An upward tilt introduces systematic error in the height estimate; at several km distance this is likely small but unquantified.
  • Scale calibration. The 73 m mast separation was confirmed from satellite imagery. Any error propagates directly into all distance and size estimates.
  • Blast yield. The ~210 t TNT estimate carries at least a factor of 2–3 uncertainty. We are in the acoustic regime where simplifying assumptions break down.
  • Platform height. The ~10 m platform elevation estimate carries uncertainty comparable to the figure itself; the shadow measurements that produce it are approximate.
  • Fireball correlations. Roberts, Moorhouse, and TNO were all calibrated at 1–10 t scale. Extrapolating 400× introduces significant uncertainty.
  • Fireball symmetry. The diameter assumes symmetry about the origin. The fireball rose and elongated; the video measurement is a cross-section at one moment.

All analysis is based on publicly available information only. No proprietary data, Blue Origin internal documents, or government reports were used. This is a forensic estimate, not an official investigation.