A

Ask the Record

asktherecord.com

DOW-UAP-D58, Range Fouler Debrief, NA, October 2020

Department of War · 2020-10-27 · release 1

This document is a Range Fouler Debrief, a standardized reporting form the U.S. Navy uses to record the circumstances surrounding an unauthorized intrusion into controlled airspace during active military operations or training. These reports contain a narrative description of the observer’s experiences. A U.S. military operator reported an encounter with a group of two UAP. The operator described the UAP as “balloon-shaped,” metallic, and reflective, characterizing them as “2x red blinking strobes.” The report states that “one range fouler was circling around the other.” All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.

This is one record. The archive holds the rest — ask it anything across the UAP Files files and every answer is cited to the page.

Ask the archive about this →
II!!! I Rl!!T 111 Ii IF 11 Range Fouler Debrie Form Declassified by MG Richard A. Harrison usctf.le~~~.fil~ Aie-l~~raftUrple Oecla~M~ffif~R~li~Bffi',y~(?iS'e and email the complete file manually (see below). • Please complete this form to the best of your ability. If you do L,have the requested information, please leave the field blank. form for data collection purposes. You should receive a respons within 5 business days. If there was more than one "groupi," please report each on a separate Last Name. First Name Rank Squadron S/PR £mail Address Crew Position 0-3 . ._l11_E_F_S_ __, This information is for contact only. SPEAR sanitizes all r . ports of identifying information. Absolutely no identifying information for aircrew or squadT<1 n will be recorded for analysis. 10/27/20 01:12:21 Night DCA Date (mmldd,yy) Time of detection (hh:mm:ss Z) Day I Night Side No. Bimo Mission Description (CAS. BFM, etc) No LFE? Contact Wonting Area (Ex: W-72 1A) Contact Latitute (DD:MM:SS) N/S Contact Longitude (DD:MM:SS) E,W Please attempt to determine a LafI 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 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 us.ed to cue other means of tracking. 26000 •ontact Altitude ( x: 22000) No Altitude Constant? Wind Dir at Contact Alt (From) Wind Speed Was work, but please be as specific as possible and make a note in the comments section. These l ocations may be us.ed to cue other means of tracking. 26000 •ontact Altitude ( x: 22000) No Altitude Constant? Wind Dir at Contact Alt (From) Wind Speed Was the contact moving? Yes Direction/Speed (fa. 090115) 060/20 Radar Equipped: Other Stable Trackfile?: Yes # of Contacts in "Group": 2 EA Indications (Check all that apply): □ □ □ llJ Other/ False ECM Arc Letter Jdentmer Trackfi/es Ambiguous AIM-9x Self-Track: □ A TFL/R Autotrack: □ Tally Achieved: llJ Please check all that apply: Round: D Square: D Balloon-shaped: [Z] Wings/Airframe: D Moving Parts: D Metallic: [Z] Markings: D Translucent: D Other Shape:[£]. Opaque: [{] Apparent Propulsion:□ Reflective: [Z] Please use the field below to describe the contact and any inte detail as possible. Please be sure to include any detail not included in questions above. action in your own words with as much 1 I IOBTAINED RADAR LOCK AND TARGET KINGPIN DIRECTED ID OF UNKNOWN CONTACT.! 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. 1.4a FIRST DETECTION OF THE RANGE FOULERS WERE AT B/E Z 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. 1.4a 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 I(Also in the global) For troubleshooting, call! (b)(s) (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. I (b)(6) I liliiSI 959 USCENTCOM MOR 26-0038 to MOR 26-0046 Approved for Release to AARO I 03/27/26 000001

Original source: view the released document

More from the UAP Files files