DOW-UAP-D058, Range Fouler Debrief, NA, October 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 an encounter with a group of two UAP. The operator described the UAP as “balloon-shaped,” metallic, and reflective, characterizing them as “2x red blinking strobes.” The report states that “one range fouler was circling around the other.” 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 466 words from page 1 of 1.
PAGE 1
Declassified by MG Richard A. Harrison Range Fouler Debrie Form email the complete file manually L, (see below). Please complete this form to the best of your ability. If you do have the requested information, please leave the field blank. If there was more than one "groupi," 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 S/PR £mail Address Crew Position This information is for contact only. SPEAR sanitizes all r. ports of identifying information. Absolutely no identifying information for aircrew or squadT<1 n will be recorded for analysis. 10/27/20 01:12:21 Night DCA No Date (mmldd,yy) Time of detection DayI Night Side No. Bimo Mission Description (CAS. BFM, etc) LFE? Contact Wonting Area Contact Latitute N/S Contact Longitude E,W •ontact Altitude Altitude Wind Dir at Wind Please attempt to determine a LafI Long forthe 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. Ifthat method is not available, any reasonable derivation oflocation will work, but please be as specific as possible and make a note in the comments section. These locations may be us.ed to cue othermeans oftracking. 060/20 Radar Equipped: Other AIM-9x Self-Track: □ Please check all that apply: Stable Trackfile?: Yes A TFL/R Autotrack: □ Round: Moving Parts: # of Contacts in "Group": 2 Tally Achieved: llJ Square: Metallic: Balloon-shaped: Markings: EA Indications (Check all that apply): D D ECM Letter False Other/ Apparent Propulsion:□ Reflective: [Z] Arc Jdentmer Trackfi/es Ambiguous Please use the field below to describe the contact and any inte action in your own words with as much detail as possible. Please be sure to include any detail not inclu1 ded in questions above. KINGPIN DIRECTED ID OF UNKNOWN CONTACT.! 1.4a OBTAINED RADAR LOCK AND TARGET POD VIDEO BUT UNABLE TO GET CLOSER THAN 16.9NM TID GETA BETTER ID. THE TARGET POD SHOWED 2 IR SIGNIFICANT CONTACTS. ONE RANGE FOUL~ER WAS CIRCLING AROUND THE OTHER IN 1130TH OF A SECOND, THEY WERE GONE. TALLr ACHIEVED WAS 2X RED BLINKING STROBES AND NOISE JAMMING WAS RECIEVED. NOISE JAMMING WAS INDICATED BY TWO FIRST DETECTION OF THE RANGE FOULERS WERE AT B/E ZIM 248/17 t.__ _ __,!. Don't use the purple "submit" button! Save this form with filenam "Date_Squadron_RF.pdf' and email it (b)(s) (Also in the global) For troubleshooting, call! (b)(6) Thank you for your time. Please ensure all display tapes are rip •ed for the entire time ofinteraction and saved as a .wmv (Example: 4 May VFA-106 HUD. wmv). Squadron intel personnel shall upload those files to the repository located at this link. USCENTCOM MOR 26-0038 to MOR 26-0046 Approved for Release to AARO 03/27/26 000001
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 #193 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #367 of 450.
That places it in the lower-scoring band of the archive (367 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.
No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.
Reported by trained U.S. military personnel during an operational mission (10/27/20) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.
On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.
The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.
Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.
This file from the Department of War is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.
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 →
Source: https://www.war.gov/medialink/ufo/release_1/dow-uap-d58-range-fouler-debrief-na-october-2020.pdf