DOW-UAP-D038, Range Fouler Debrief, Middle East, May 2020
This document is a Range Fouler Debrief, a standardized reporting form the U.S. Navy uses to record the circumstances surrounding an unauthorized intrusion into controlled airspace during active military operations or training. These reports contain a narrative description of the observer’s experiences. A U.S. military operator reported observing a “solid white object [fly] through the [field-of-view]. The reporter described the UAP as making erratic [movements] above the water. All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 490 words from page 1 of 1.
PAGE 1
Declassified by MG Richard A. Harrison USCENTCOM Chief of Staff "submit" button above. Save and Range Fouler Debrie Form email the complete file manually (see below). Please complete this form to the best of your ability. If you do ot have the requested information, please leave the field blank. If there was more than one "group " please report each on a separate form for data collection purposes. You should receive a respons within 5 business days. Last Name, First Name Rank Squadron SIPR Email Address Crew Position This information is for contact only. SPEAR sanitizes all r ports of identifying information. Absolutely no identifying information for aircrew or squadmn will be recorded for analysis. Date (mmldd/yy) Time of detection Day I Night Side No. Buno Mission Description (GAS, BFM, etc) LFE? Contact Working Area Contact Latitute NIS Contact Longitude EM' 'ontact Altitude Altitude Wind Dir at Wind Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using JMPS to reference the sensor-derived bearing and range relative to the bullseye you had Was the contact moving? Yes in use. If that method is not available, any reasonable derivation of location will worl<, but please be as specific as possible and make a note in the comments section. These locations may be used to cue other means of tracking. Radar Equipped: AIM-9x Self-Track: □ Please check all that apply: Stable Trackfile?: Intermittent ATFLIR Autotrack: □ Round: [Z] Moving Parts: # of Contacts in "Group": 1 Tally Achieved: □ Square: D Metallic: D Balloon-shaped: Markings: EA Indications (Check all that apply): D D ECM Letter False Other/ Apparent Propulsion:□ Reflective: Arc Identifier Trackfi/es Ambiguous Please use the field below to describe the contact and any interiaction in your own words with as much detail as possible. Please be sure to include any detail not incl ded in questions above. While preforming an ISR tasking (UL TN/Black Hot/Lin), a solid w ite1object flew through the FOV. There was a temporarily lose of the object but re-acquired shortly there after. The crew was able to follow the object as it appeared to make erratic moments above the water. During the follow, crew was able to obtain 4x zoom on the object but lost the object due to poor track place ent. While following, the sensor operator was continuously manipulating the sensor to maintain eyes on th1e object. This is apparent by the waves of the water in the background being visible and not being visible. Don't use the purple "submit" button! Save this form with filenam "Date_Squadron_RF.pdr' and email it toj 3.sc, (b)(S) (Also in the global) For troubleshooting, cal/I 3.Sc, (b)(B) Thank you for your time. Please ensure all display tapes are rip11ed for the entire time of interaction and saved as a .wmv (Example: 4 May VFA-106 HUD.wmv). Squa 1ronlintel personnel shall upload those files USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 001
Where this file fits in the PURSUE archive
This file is one of DoD's 257 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #183 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #357 of 450.
That places it in the lower-scoring band of the archive (357 of 450 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 53/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.
Reported by a witness with no instrumented record. The lowest tier in the rubric's sensor axis. Eyewitness perception in field conditions, even when the witness is highly credentialed, scores below capture by any instrumented modality. This report reached the federal record through the Department of War.
Trained U.S. military personnel reporting from an operational mission context. A high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This is the witness profile shared by the entire AARO-submitted infrared-capture cluster that anchors the 66-point score band.
Single-witness or single-instrument capture. This is the corroboration tier for the overwhelming majority of the PURSUE archive 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. A small number of files with an independent second witness or instrument score on the multi-witness/multi-instrument tier above this one.
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.
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.
Catalogued as unresolved with no formal review process having concluded. This is the disposition for a large share of the archive's military infrared captures - 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 53/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.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
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 →