FIELD INTEL // AUGUST 28, 2026
AARO’s UAP report-document index lists Mission Report MR-75 for a July 14, 2024 incident in the Gulf of Aden. Its presence in the government archive establishes that a Defense component documented an event and that a report entered the public release pipeline. It does not, by itself, establish an unconventional craft.
The distinction matters because military mission reports are operational records, not finished scientific papers. They may preserve crew observations, sensor contacts, and immediate assessments while omitting the calibration, geometry, and comparison data needed to reproduce a performance claim.
A report is the beginning of analysis
For an airborne or maritime observation, apparent speed depends on range, viewing angle, platform motion, stabilization, and sensor mode. A small error in any one of those inputs can turn ordinary motion into an extraordinary-looking track. A defensible conclusion therefore requires the original sensor file, platform navigation data, time synchronization, and an explanation of every processing step.
What investigators should request
- The native recording and cryptographic hash
- Platform position, attitude, speed, and sensor line of sight
- Field-of-view, zoom, track gates, and automatic processing settings
- Nearby aircraft, ships, balloons, weather, and exercise activity
- The custody path from collection to AARO publication
The 2026 PURSUE release program is valuable because it gives outside analysts more material than a press quotation or witness recollection. Yet openness is most useful when the released package lets independent teams reproduce the government’s reasoning.
Assessment
Official provenance, incomplete public measurement chain. MR-75 deserves attention as a government case file. Any claim about anomalous acceleration, size, or origin should wait until the underlying geometry and original data are available.