DOW-UAP-D44, RANGE FOULER REPORTING FORM, GULF OF ADEN, OCTOBER 2020

About this document

DOW-UAP-D44, RANGE FOULER REPORTING FORM, GULF OF ADEN, OCTOBER 2020 is a declassified record from the U.S. United States Navy, dated 2020-10-15, 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
USCMC/COM Chief of Staff
Declassified on: 20 March 2020
Please do not use the purple "submit" button above. Save and email the complete file manually (see below).

Range Fouler Reporting 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: O-2
Squadron: 172 ATKS
SIPR Email Address: <empty>
Crew Position: Other
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): 10/15/20
Time of detection (hh:mm:ss Z): 14:18:39
Day / Night: Day
Side No.: <empty>
Buno: <empty>
ISR: <empty>
Mission Description (CAS, BFM, etc): <empty>
LFE?: <empty>
Contact Working Area (Ex: W-72 1A): <empty>
Contact Latitute (DD:MM:SS): <empty>
N/S: N
Contact Longitude (DD:MM:SS): <empty>
E/W: E
Contact Altitude (Ex: 22000): <empty>
Altitude Constant?: <empty>
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
Direction/Speed (Ex. 090/15): 261/30
Radar Equipped: <empty>
Stable Trackfile?: <empty>
# of Contacts in "Group": 1
AIM-9x Self-Track: [ ]
ATFLIR Autotrack: [ ]
Tally Achieved: [ ]
Please check all that apply:
Round: [x]
Square: [ ]
Balloon-shaped: [ ]
Wings/Airframe: [ ]
Other Shape: [ ]
Apparent Propulsion: [ ]
Moving Parts: [ ]
Metallic: [ ]
Markings: [ ]
Translucent: [ ]
Opaque: [ ]
Reflective: [ ]
EA Indications (Check all that apply):
[ ] ECM Arc
[ ] Letter Identifier
[ ] False Trackfiles
[ ] Other/ Ambiguous
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.
Contact at 14:18:39Z to 14:19:52Z on 15OCT2020. MGRS location 40Q BD 63 1.4a 19 1.4a (estimated lat/long 1.4a. While at 19,073 HAT over the Gulf of Aden we tracked a round, cold object in IR traveling 319 degrees at 20 mph. It made a few abrupt directional changes during the 1 minute contact. Our sensor was aimed -50 degrees below our altitude with a slant range of 4.06NM and ground range of 4.78KM. The IR sensor was set to black hot and the object in question was a bright white.
(b)(6)
Don't use the purple "submit" button! Save this form with filename "Date_Squadron_RF.pdf" and email
it to: (b)(6)
(Also in the global). For troubleshooting, call: (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.
(b)(6)

USCENTCOM MDR 26-0038 to MDR 26-0046
03/27/26 000001