This document is a Range Fouler Reporting Form, a standardized reporting form the U.S. Navy uses to record the circumstances surrounding an unauthorized…
Full Document Text
Text extracted directly from the source PDF. Text extraction via abigailhaddad/ufo-releases; original file at war.gov.
Read the full text (5,831 characters)
--- PAGE 1 ---
Range Fouler Reportin Form
Please complete this form to the best of your ability. If you do n~ot 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 respons within 5 business days. •
Last Name, First Name Rank Squadron SfPR Email Address Crew Position
0-3 1172 ATKS Other
This information is for contact only. SPEAR sanitizes all r ports of identifying information.
Absolutely no identifying information for aircrew or squadr, n will be recorded for analysis.
09/04/20 21 :09:00 Night ISR
Date {mmlddlyy} Time of detection Day I Night Side No. Buno Mi$$ion Description (CAS, BFM. etc) LFE?
(hh:mm:ss Z)
N E 23819
Contact Won,-ing Area Contact Latitute N/S Contact LongitrJ<Je E,W , ntact Altitllde Altitude W'incJ Dir at Wind
(Ex: W•721A) (DD:MM:SS) (DD:MM:SS) ~ : 22000} Constant? Contact Alt Speed
(From)
Please attempt to determine a Lat I Long for the contact at initial cJete<;t;on. We recommend
using JMPS to reference the sensor-derived beating and range mtat/ve to the bullseye you had Wes the contact moving? Yes
in use. If that methocJ is not available, any reasonable derivation of location will won,-, but please
be as specific as possible and make a note in the comments section. These locations may be
Direction/Speed
used to cue other means oftracking.
(Ex. 090/15) 168/277
Radar Equipped: AIM-9x Self-Track:
□ Please check all that apply:
Stable Trackfile?: A TFLIR Autotrack:
□ Round: [l] Moving Parts: D
Square: D Metallic: D
# of Contacts in "Group": 1 Tally Achieved:
□ Balloon-shapecJ: D Mar1<ings: D
EA Indications (Check all that apply):
Wings/Airframe: D Translucent: D
□ □ □
False
□ Other Shape: D Opeque:O
ECM . Letter Other/ Apparent Propulsion:□ RefTe<:tive: □
An; Identifier Trackfiles Ambiguous
Please use the field below to describe the contact and any inte action in your own words with as much
detail as possible. Please be sure to include any detail not incJJded in questions above.
Contact at 21 :09z to 21 :17z 04SEP2020. MGRS location 38P L ?(~a<aoimJ(estimated lat/long +
I (bJ(1 )1.4a ~. While at 23,819 HAT over the ~ulf of Aden we tracked a round, cold object
in IR traveling 168 degrees at 277 mph. It made a few abrupt dir~ctional changes during the 8 minute
contact. Our sensor was aimed -39 degrees below our altitude w th a slant range of 6.1 ?NM and ground
range of 8.81 KM. The IR sensor was set to black hot and the obj ct in question was a bright white.
Don't use the purple "submit" button! Save this form with filenam "Date_Squadron_RF.pdf" and email
it to I (blt61 3.5c. I(Also in the global). For troubleshooting, call I (bl(6l I 3.5c,
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). Squa ron inte/ personnel shall upload those files
to the repository located at this link.
( 0 3::c, c1:JJc61 , I
USCENTCOM 26.0028 Approved for Release to MRO - FOUO / PA applies 03/16/26 000001 View the official fileCongressional Context
No confirmed links between this file and the congressional record yet. Connections are added only when the source text supports them, never inferred.