DOW-UAP-D58, RANGE FOULER DEBRIEF, NA, OCTOBER 2020

About this document

DOW-UAP-D58, RANGE FOULER DEBRIEF, NA, OCTOBER 2020 is a declassified record from the U.S. United States Navy, dated 2020-10-27, 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.

Range Fouler Debrief Form

Please do not use the purple
"submit" button above. Save and
Declassified on: 20 March 2020
email the complete file manu
email the
(see below).
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-3
Squadron: 77 EFS
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): 10/27/20
Time of detection (hh:mm:ss Z): 01:12:21
Day / Nigh: Night
Side No.
Buna
DCA
Mission Description (CAS, BFM, etc): DCA
No
LFE?: No
Contact Working Area: <empty>
(Ex: W-72 1A): <empty>
Contact Latitute: <empty>
(DD:MM:SS): <empty>
N/S: <empty>
Contact Longitude: <empty>
(DD:MM:SS): <empty>
E/W: <empty>
Contact Altitude (Ex: 22000): 26000
Altitude Constant?: No
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): 060/20
Radar Equipped:: Other
AIM-9x Self-Track:: [ ]
Stable Trackfile?:: Yes
ATFLIR Autotrack:: [ ]
# of Contacts in "Group":: 2
Tally Achieved:: [x]
Please check all that apply:
Round:[ ]
Square:[ ]
Balloon-shaped:[x]
Wings/Airframe:[ ]
Other Shape:[x]
Apparent Propulsion:[ ]
Moving Parts:[ ]
Metallic:[x]
Markings:[ ]
Translucent:[ ]
Opaque:[x]
Reflective:[x]
EA Indications (Check all that apply):
[ ] ECM Arc
[ ] Letter Identifier
[ ] False Trackfiles
[x] 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.
KINGPIN DIRECTED ID OF UNKNOWN CONTACT. 1.4a OBTAINED RADAR LOCK AND TARGET POD VIDEO BUT UNABLE TO GET CLOSER THAN 16.9NM TO GET A BETTER ID. THE TARGET POD SHOWED 2 IR SIGNIFICANT CONTACTS. ONE RANGE FOULER WAS CIRCLING AROUND THE OTHER. IN 1/30TH OF A SECOND, THEY WERE GONE. TALLY ACHIEVED WAS 2X RED BLINKING STROBES AND NOISE JAMMING WAS RECIEVED. NOISE JAMMING WAS INDICATED BY TWO CHEVRONS.
<empty> FIRST DETECTION OF THE RANGE FOULERS WERE AT B/E ZIM 248/17 <empty> 1.4a
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)