Unresolved UAP Report, Arabian Gulf, 2020

66
⬇ Download HD (111.4 MB) 📖 Deep dive: The 27 AARO Unresolved UAP files at score 66 This file is part of the densest cluster in the archive - all 27 walked through, by region READ →
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
VIDEO
Event Date
n/a
Released
2026-05-08
Size
111.4 MB
Location
Arabian Gulf
Status
REDACTED

The United States Central Command submitted a report of an unidentified anomalous phenomenon to the All-domain Anomaly Resolution Office (AARO) consisting of one minute and 34 seconds of video footage from an infrared sensor aboard a U.S. military platform in 2020. The reporter did not provide any oral or written description of the observation. Video Description: 00:01: An area of contrast enters the sensor field-of-view from the bottom third of the left side of the screen. 00:02-01:34: The sensor pans from left to right, tracking the area of contrast and keeping it generally centered within the field-of-view. This video description is provided for informational purposes only. Readers should not interpret any part of this description as reflecting an analytical judgment, investigative conclusion, or factual determination regarding the described event’s validity, nature, or significance.

The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.

Where this file fits in the PURSUE archive

This file is one of DoD's 143 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #56 of 143 by Anomalousness Index. Across the entire 294-file archive it ranks #67 of 294.

That places it tied with 26 other files at 66 - the densest single-score cluster in the archive, anchored by AARO-submitted military infrared captures.

For the broader cluster context, this file is part of AARO Unresolved UAP - the 27-file AARO unresolved cluster tied at 66. The cluster page walks through all 27 member files with regional grouping, sensor breakdown, and standout analysis.

Anomalousness Index: 66/100

Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.

🤖 AI-ASSISTED SCORING · methodology

The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.

sensor quality (single sensor military) 80 × 0.25 = 20.0

Captured by a single U.S. military sensor platform (typically infrared, occasionally short-wave infrared or dual EO+IR), aboard a mission aircraft or operational platform. Instrumented, time-stamped, and recoverable. Lower than a multi-sensor capture only because cross-modality confirmation is the rubric's higher bar.

witness credibility (military personnel) 80 × 0.2 = 16.0

Trained U.S. military personnel reporting from an operational mission context. The second-highest credibility tier in the rubric. This is the witness profile shared by the entire AARO-submitted infrared-capture cluster that anchors the 66-point score band.

corroboration (single witness instrument) 60 × 0.2 = 12.0

Single-witness or single-instrument capture. Every file in the PURSUE archive scores at this corroboration tier on the released metadata - the rubric records the honest limit of the underlying record rather than inferring multi-witness corroboration that the released summaries do not establish.

kinematic anomaly (no kinematic data) 30 × 0.15 = 4.5

No kinematic measurements - speed, acceleration, vector - are published in the released file with sufficient precision to score on the kinematic axis. The rubric does not infer kinematic anomaly from narrative observer estimates. Every file in the archive carries this value, which is itself an observation about the disclosure: kinematic-grade telemetry was not part of what was released.

mundane explanation available (weak mundane candidate) 70 × 0.1 = 7.0

A conventional candidate explanation has been considered but is not dispositive. Every file in the archive scores this way - reflecting that the underlying release metadata systematically caveats strong determinations in either direction. The released summaries warn against reading them as conclusive analytical judgments, and the rubric respects that.

official disposition (unresolved no review) 60 × 0.1 = 6.0

Catalogued as unresolved with no formal review process having concluded. This is the AARO baseline disposition for the 27-file score-66 cluster - the reports are logged into the system as unresolved, but no formal review has finalized. The rubric distinguishes this from 'open after review' because the absence of review is itself a status signal.

Bottom line on the score: the Anomalousness Index of 66/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.

Related files in DoD

Other PURSUE files in the same category, ranked by Anomalousness Index.

DoD · VIDEO SCORE 68

DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…

DoD · VIDEO SCORE 66

Unresolved UAP Report, Middle East, May 2022

DoD · VIDEO SCORE 66

Unresolved UAP Report, Iraq, May 2022

DoD · VIDEO SCORE 66

Unresolved UAP Report, Syria, July 2022

DoD · VIDEO SCORE 66

Unresolved UAP Report, Iraq, December 2022

DoD · VIDEO SCORE 66

Unresolved UAP Report, United Arab Emirates, October 2023

BROWSE ALL 294 FILES →

Verification

SHA-256:

ea6b86de5ec070a789e515456fb7ed2ef0bfbe536b30025117ef47cefa59c503

This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →

Source (DVIDS): https://www.dvidshub.net/video/1006094/dow-uap-pr41-unresolved-uap-report-middle-east-2020

Direct video file: https://d34w7g4gy10iej.cloudfront.net/video/2605/DOD_111689083/DOD_111689083.mp4