Um 'Range Fouler Debrief Form' documentando um encontro com UAP em 10/27/20. O formulário inclui campos estruturados para squadron (77 EFS), rank (O-3) e dados técnicos como altitude (26000 ft) e indicações de radar. Uma seção narrativa descreve um encontro com dois contatos exibindo 'noise jamming' e 'red blinking strobes'. Cinco pequenas rasuras estão presentes, cobrindo identificadores específicos e informações de contato usando os códigos (b)(6) e 1.4a.
Declassified by MG Richard A. Harrison usctf.le~~~.fil~ Aie-l~~raftUrple II!!! I Rl!!T 111 Ii IF 11 Oecla~M~ffif~R~li~Bffi',y~(?iS'e and Range Fouler Debrie Form email the complete file manually (see below). L,
0,9 · 100×12%
• 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
0,18 · 100×8%
0-3 . ._l11_E_F_S_ __, This information is for contact only. SPEAR sanitizes all r . ports of identifying information. 1 Absolutely no identifying information for aircrew or squadT< n will be recorded for analysis. 10/27/20 01:12:21 Night DCA No
0,26 · 100×8%
Date (mmldd,yy) Time of detection Day I Night Side No. Bimo Mission Description (CAS. BFM, etc) LFE? (hh:mm:ss Z) 26000 No Contact Wonting Area Contact Latitute N/S Contact Longitude E,W •ontact Altitude Altitude Wind Dir at Wind (Ex: W-72 1A) (DD:MM:SS) (DD:MM:SS) ( x: 22000) Constant? Contact Alt Speed (From) Please attempt to determine a Laf I Long for the contact at initial detection. We recommend
0,37 · 100×8%
using JMPS to reference the sensor-derived bearing and range relative to the bullseye you had Was the contact moving? Yes in use. If that method is not a vailable, any reasonable derivation of location will work, but please be as specific as possible and make a note in the comments section. These l ocations may be Direction/Speed us.e d to cue other means of tracking. (fa. 090115) 060/20 Radar Equipped: Other AIM-9x Self-Track: □ Please check all that apply: Stable Trackfile?: Yes A TFL/R Autotrack: □ Round: D Moving Parts: D Square: D Metallic: [Z] # of Contacts in "Group": 2 Tally Achieved: llJ Balloon-shaped: [Z] Markings:D EA Indications (Check all that apply): Wings/Airframe: D Translucent: D □ □ □ llJ Other Shape:[£]. Opaque: [{] ECM Letter False Trackfi/es Other/ Ambiguous Apparent Propulsion:□ Reflective: [Z] Arc Jdentmer Please use the field below to describe the contact and any inte action in your own words with as much
▓▓▓ (b)(1) 1.4(a) ▓▓▓— Specific identifier or location data in narrative text
1 detail as possible. Please be sure to include any detail not included in questions above. I KINGPIN DIRECTED ID OF UNKNOWN CONTACT.! 1.4a OBTAINED RADAR LOCK AND TARGET I 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 CHEVRONS.
▓▓▓ (b)(1) 1.4(a) ▓▓▓— Specific identifier or location data in narrative text
FIRST DETECTION OF THE RANGE FOULERS WERE AT B/E ZIM 248/17 t.__ _ ...;.;1•..;.;;;4a'---_ __,!. Don't use the purple "submit" button! Save this form with filenam "Date_Squadron_RF.pdf' and email it tol (b)(s) I
▓▓▓ (b)(6) ▓▓▓— Email address for reporting
▓▓▓ (b)(6) ▓▓▓— Phone number for troubleshooting
(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 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. liliiSI 959
▓▓▓ (b)(6) ▓▓▓— Repository link or identifier
I (b)(6) I USCENTCOM MOR 26-0038 to MOR 26-0046 Approved for Release to AARO 03/27/26 000001 I