< ARCHIVE

> FILE / FC4CA2EE

DOW-UAP-D58, RANGE FOULER DEBRIEF, 77 EFS, OCTOBER 2020

A range fouler debrief form completed by an O-3 pilot from the 77 EFS detailing an encounter with two unidentified aerial contacts. The report notes radar lock, target pod video acquisition, and active electronic noise jamming during the incident. The document serves as a formal record for UAP data collection and analysis.

AGENCY
DEPARTMENT OF WAR
TYPE
DEBRIEF
INCIDENT DATE
2020-10-27
LOCATION
N/A
PAGES
1
EXTRACTED
1 / 1
STATUS
READY

> PAGES INDEXED [001]

OPEN A PAGE BELOW

  1. Page 1P.1DECLASSI

> PAGE TEXT

PAGE 1

form

A Range Fouler Debrief Form completed by an O-3 from the 77 EFS regarding an encounter with two unknown contacts on October 27, 2020, involving radar lock, target pod video, and noise jamming.

[REDACTED] 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
Rank
O-3
Squadron
77 EFS
SIPR Email Address
Crew Position

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.

10/27/20
Date (mm/dd/yy)
01:12:21
Time of detection (hh:mm:ss Z)
Night
Day / Night
Side No.
Buno
DCA
Mission Description (CAS, BFM, etc)
No
LFE?

Contact Working Area (Ex: W-72 1A)
Contact Latitute (DD:MM:SS)
N/S
Contact Longitude (DD:MM:SS)
E/W
Contact Altitude (Ex: 22000)
26000
Altitude Constant?
No
Wind Dir at Contact Alt (From)
Wind Speed

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
Stable Trackfile?: Yes
# of Contacts in "Group": 2
EA Indications (Check all that apply):
ECM Arc
Letter Identifier
False Trackfiles
Other/ Ambiguous [CHECKED]

AIM-9x Self-Track:
ATFLIR Autotrack:
Tally Achieved: [CHECKED]

Please check all that apply:
Round:
Square:
Balloon-shaped: [CHECKED]
Wings/Airframe:
Other Shape: [CHECKED]
Apparent Propulsion:
Moving Parts:
Metallic: [CHECKED]
Markings:
Translucent:
Opaque: [CHECKED]
Reflective: [CHECKED]

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.

FIRST DETECTION OF THE RANGE FOULERS WERE AT B/E ZIM 248/17 1.4a

Don't use the purple "submit" button! Save this form with filename "Date_Squadron_RF.pdf" and email it to [REDACTED] (Also in the global). For troubleshooting, call [REDACTED]

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.
[REDACTED]
[REDACTED]
USCENTCOM MDR 26-0038 to MDR 26-0046 Approved for Release to AARO 03/27/26 000001