5-OBSERVABLES GAP REPORT
Middle East Metallic Orb (MQ-9, 2022) — 5-Observables Gap Analysis
An MQ-9 Reaper's EO/IR turret recorded a spherical object passing over terrain in the Middle East. AARO presented it as a representative unresolved UAP while explicitly noting it shows no enigmatic capabilities; independent geolocation placed it northeast of Deir ez-Zor, and skeptics note its morphology is consistent with a commercial or scientific balloon. The clip preserves bearing and apparent shape but no range or scale anchor — so size, altitude, and velocity are all unconstrained, which is why 'unresolved' here means under-determined, not anomalous.
Scoreboard
This release supports evaluation of 0 of 5 observables in the Pentagon framework; the object's size and speed are unconstrained by the footage.
Per-observable analysis
Sudden / instantaneous acceleration
Cannot evaluate- Required to evaluate
- Range to the object over time, to convert the turret's angular motion into real acceleration.
- Released data
- Single airborne EO/IR turret; bearing and apparent size only, with the drone itself in motion. No independent range on the orb.
- AeriTrax live capture would have provided
- A ground witness contributes a separate bearing line; paired AeriTrax captures triangulate range and yield a real acceleration estimate rather than an angular one.
Hypersonic velocity without signature
Cannot evaluate- Required to evaluate
- A range-anchored velocity estimate plus an acoustic record.
- Released data
- No range anchor; EO/IR clip carries no relevant audio. Apparent motion is dominated by the platform's own flight.
- AeriTrax live capture would have provided
- Audio correlated to capture timestamps plus a sensor-derived velocity envelope at a stationary observer, where platform motion does not contaminate the estimate.
Low observability
Partial data- Required to evaluate
- Continuous coverage at a known frame rate plus a sensor-gap ledger.
- Released data
- Frame rate recoverable from the EO/IR record; the object is in fact continuously and unremarkably visible — AARO notes nothing enigmatic — but no independent scale is recorded.
- AeriTrax live capture would have provided
- A frame-timestamp ledger and continuous AR-overlay track, plus a known optical baseline that lets apparent size be tied to range rather than left free.
Trans-medium travel
Cannot evaluate- Required to evaluate
- Boundary-crossing tracking plus altitude and location ground truth.
- Released data
- Over-terrain clip; no altitude reference on the orb, no boundary event observed.
- AeriTrax live capture would have provided
- GPS and barometric altitude at the observer plus a continuous track flagging loss-of-frame separately from any medium transition.
Anti-gravity lift / propulsion without visible means
Cannot evaluate- Required to evaluate
- A range-anchored motion envelope plus a conventional-object elimination chain (aircraft, balloon, drone).
- Released data
- Apparent drift at unknown range; no wind/altitude context, no traffic or balloon-trajectory correlation — the data needed to test the balloon hypothesis is absent.
- AeriTrax live capture would have provided
- A trajectory record plus an ADS-B / Remote ID elimination chain and local wind context, enabling a drift-versus-powered-flight comparison and a direct test of the balloon explanation.
Method note
This report addresses only the released EO/IR clip. The forensic claim is narrow: the footage does not preserve the data classes required to evaluate the Pentagon 5 observables. AARO itself characterizes the object as showing no enigmatic technical capabilities, and this analysis takes no position beyond the data-completeness question.
Why this case is instructive
“Unresolved” is doing a specific kind of work here. The object is unremarkable on the footage; what is missing is not exotic behavior but the basic anchors — range, scale, altitude, wind context — that would let an analyst either confirm the leading mundane explanation (a balloon) or document a genuine residual. A single moving sensor with no ranging channel cannot supply them, so the case stays under-determined rather than either explained or anomalous.
What an AeriTrax live capture at a ground witness would have added
AeriTrax is a ground-observer instrument; it would not have flown the Reaper. A credible witness beneath the same object would have produced a bearing-stamped sensor stream, GPS and barometric altitude, local wind context, a frame-timestamp ledger, and an ADS-B / Remote ID correlation, anchored to a signed manifest — with a second observer adding a triangulation baseline. That trace is the difference between “a sphere we could not measure” and “a balloon drifting at a measured altitude and speed,” or a documented residual if it were neither.