5-OBSERVABLES GAP REPORT
USS Russell 'Pyramid' Triangles (2019) — 5-Observables Gap Analysis
The released clip is a hand-held night-vision recording re-imaged through an SLR, showing flashing triangular shapes off San Diego. The Pentagon has stated the objects 'correlate to unmanned aerial systems' and that the triangular appearance is an optical artifact of the night-vision-plus-SLR path. The clip preserves none of the observer-side data classes required to evaluate the Pentagon 5 observables — and, separately, none of the lens/focus/sensor metadata that would let a third party independently confirm the optical-artifact explanation from the footage alone.
Scoreboard
This release supports evaluation of 0 of 5 observables in the Pentagon framework.
Per-observable analysis
Sudden / instantaneous acceleration
Cannot evaluate- Required to evaluate
- A calibrated angular reference and per-frame time ledger at the observer's position, plus observer-platform motion, to separate apparent motion from real motion.
- Released data
- Hand-held night-vision footage re-imaged by an SLR; no calibrated bearing, no frame-time ledger, and observer hand motion is uncontrolled.
- AeriTrax live capture would have provided
- A ground witness in the same scene would have a ~50 Hz magnetometer-derived bearing and accelerometer angular-rate stream with a per-frame timestamp ledger, enabling apparent-versus-real motion separation against a fixed reference.
Hypersonic velocity without signature
Cannot evaluate- Required to evaluate
- A synchronized audio track and an observer-derived velocity estimate.
- Released data
- No audio relevant to the objects; no range or velocity data of any kind.
- AeriTrax live capture would have provided
- Device-microphone audio correlated to capture timestamps plus a sensor-derived velocity envelope, supporting an absence-of-acoustic-signature claim grounded in recorded negative evidence.
Low observability
Cannot evaluate- Required to evaluate
- Continuous frame coverage at a known, logged frame rate plus a sensor-gap ledger, and lens focus state to interpret point-source rendering.
- Released data
- Uncontrolled hand-held capture; focus state is in fact load-bearing here (the triangular shape is attributed to defocus/bokeh through the NVG aperture) yet no focus or aperture metadata accompanies the clip.
- AeriTrax live capture would have provided
- A per-capture frame-timestamp ledger and fixed optical path with recorded focus state, so a point source rendering as a shape is distinguishable from a structured object — the exact ambiguity at the center of this case.
Trans-medium travel
Cannot evaluate- Required to evaluate
- Continuous tracking across a medium boundary plus altitude and location ground truth.
- Released data
- Short air-domain clip; no altitude reference, no boundary tracking.
- AeriTrax live capture would have provided
- GPS plus barometric-altitude logging at the observer and a continuous AR-overlay track that flags loss-of-frame separately from any medium transition.
Anti-gravity lift / propulsion without visible means
Cannot evaluate- Required to evaluate
- A reconstructable velocity vector and motion envelope comparable to known flight envelopes, plus an elimination chain for conventional traffic.
- Released data
- Flashing point sources only; no kinematic record, no traffic-correlation data — the very data later used to attribute the objects to drones.
- AeriTrax live capture would have provided
- A trajectory record from the sensor stream plus an ADS-B / Remote ID elimination chain at the moment of observation, which is precisely the correlation that resolved this case after the fact.
Method note
This report addresses only the publicly circulated night-vision clip. The forensic claim is narrow: the released footage does not preserve the data classes required to evaluate the Pentagon 5 observables. It is not a claim that the objects are anomalous — the Pentagon has stated the objects correlate to unmanned aerial systems and that the triangular appearance is an artifact of the night-vision-to-SLR optical path.
Why this case is instructive
The official explanation depends entirely on data the clip does not contain: a focus/aperture model to support the bokeh interpretation, and traffic-correlation data to attribute the lights to drones. The footage alone is consistent with the explanation but cannot establish it; that work required external reconstruction. A capture that recorded focus state and a traffic-elimination chain at the moment of observation would have made the same determination locally, without a multi-year analytical postscript.
What an AeriTrax live capture at a ground witness would have added
AeriTrax is a ground-observer instrument; it would not have stood on the deck of the Russell. The relevant question is what a credible ground witness in the same scene would have recorded: a bearing-stamped sensor stream, recorded focus state, a frame-timestamp ledger, and an ADS-B / Remote ID correlation against local traffic — anchored to a signed manifest. That trace would either have matched the lights to the drones the Pentagon describes or surfaced a documented residual. The released clip supports neither step on its own.