DOW-UAP-D38, RANGE FOULER DEBRIEF, MIDDLE EAST, MAY 2020

About this document

DOW-UAP-D38, RANGE FOULER DEBRIEF, MIDDLE EAST, MAY 2020 is a declassified record from the U.S. United States Navy, dated 2020-05-14, classification SECRET//DECLASSIFIED. It is part of PURSUE Release 01 — the Pentagon's first public unsealing of UAP records under the Presidential Unsealing & Reporting System for UAP Encounters program, published on 2026-05-08 at war.gov/UFO/. UAP.WATCH has indexed the full text locally so the document can be read, searched, and cited without leaving the site.

Document text

Declassified by MG Richard A. Harrison
USCENTCOM Chief of Staff
Please do not use the purple
Declassified on: 22 January 2026
"submit" button above. Save and
email the complete file manually (see below).

Range Fouler Debrief Form

Please complete this form to the best of your ability. If you do not 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 response within 5 business days.
Last Name, First Name: <empty>
Rank: <empty>
Squadron: <empty>
SIPR Email Address: <empty>
Crew Position: <empty>
This information is for contact only. SPEAR sanitizes all reports of identifying information. Absolutely no identifying information for aircrew or squadron will be recorded for analysis.
Date (mm/dd/yy): 05/14/20
Time of detection (hh:mm:ss Z): 20:40:00
Day / Night: Night
Side No.: <empty>
Buno: <empty>
ISR
Mission Description (CAS, BFM, etc): <empty>
LFE?: <empty>
Contact Working Area: 28314
(Ex: W-72 1A): <empty>
Contact Latitute: 28314
(DD:MM:SS): <empty>
N/S: N
Contact Longitude: 49524
(DD:MM:SS): <empty>
E/W: E
Contact Altitude (Ex: 22000): 20000
Altitude Constant?: Yes
Wind Dir at Contact Alt (From): <empty>
Wind Speed: <empty>
Please attempt to determine a Lat / 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 in use. If that method is not available, any reasonable derivation of location will work, 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.
Was the contact moving? Yes <empty>
Direction/Speed (Ex. 090/15) <empty>
Radar Equipped: <empty>
AIM-9x Self-Track: [ ]
Stable Trackfile?: Intermittent
ATFLIR Autotrack: [ ]
# of Contacts in "Group": 1
Tally Achieved: [ ]
EA Indications (Check all that apply):
[ ] ECM Arc
[ ] Letter Identifier
[ ] False Trackfiles
[ ] Other/ Ambiguous
Please check all that apply:
Round:: [x]
Moving Parts:: [ ]
Square:: [ ]
Metallic:: [ ]
Balloon-shaped:: [ ]
Markings:: [ ]
Wings/Airframe:: [ ]
Translucent:: [ ]
Other Shape:: [ ]
Opaque:: [ ]
Apparent Propulsion:: [ ]
Reflective:: [ ]
Please use the field below to describe the contact and any interaction in your own words with as much detail as possible. Please be sure to include any detail not included in questions above.
While preforming an ISR tasking (ULTN/Black Hot/Lin), a solid white object 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 placement. While following, the sensor operator was continuously manipulating the sensor to maintain eyes on the 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 filename "Date_Squadron_RF.pdf" and email
it to: 3.5c, (b)(6)
(Also in the global). For troubleshooting, call: 3.5c, (b)(6)
Thank you for your time. Please ensure all display tapes are ripped for the entire time of interaction 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.
3.5c, (b)(6)
USCENTCOM MDR 26-0019
Approved for Release to AARO

01/26/26 001