DOW-UAP-D38, Range Fouler Debrief, Middle East, May 2020
PDF Department of War INCIDENT 5/14/20 · Persian Gulf
DOW-UAP-D38, Range Fouler Debrief, Middle East, May 2020
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 observing a “solid white object [fly] through the [field-of-view]. The reporter described the UAP as making erratic [movements] above the water. 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.
loading viewer…
Download
Metadata
Extracted Text
show full text
Declassified by MG Richard A. Harrison
USCENTCOM Chief of Staff
Plea , o , us.~,;t , 13- 02
"submit" button above. Save and
email the complete file manually
Range Fouler Debrie Form (see below).
Please complete this form to the best of your ability. If you do 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 SIPR Email Address Crew Position
This information is for contact only. SPEAR sanitizes all r ports of identifying information.
Absolutely no identifying information for aircrew or squadmn will be recorded for analysis.
05/14/20 20:40:00 Night ISR
Date (mmldd/yy) Time of detection Day I Night Side No. Buno Mission Description (GAS, BFM, etc) LFE?
(hh:mm:ss Z)
28314 28314 N 49524 E 20000 Yes
Contact Working Area Contact Latitute NIS Contact Longitude EM' ' ontact Altitude Altitude Wind Dir at Wind
(Ex: W-72 1A) (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 detection. We recommend
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 available, any reasonable derivation of location will worl<, 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.
Direction/Speed
(Ex. 090/15)
Radar Equipped: AIM-9x Self-Track:
□ Please check all that apply:
Stable Trackfile?: Intermittent ATFLIR Autotrack:
□ Round: [Z] Moving Parts: D
Square: D Metallic: D
# of Contacts in "Group": 1 Tally Achieved:
□ Balloon-shaped: D Markings: D
EA Indications (Check all that apply):
Wings/Airframe : D Translucent: D
□ □ □ □ Other Shape:O Opaque: D
Apparent Propulsion:□ Reflective: D
ECM Letter False Other/
Arc Identifier Trackfi/es Ambiguous
Please use the field below to describe the contact and any interiaction in your own words with as much
detail as possible. Please be sure to include any detail not incl ded in questions above.
While preforming an ISR tasking (UL TN/Black Hot/Lin), a solid w ite 1object flew through the FOV. There
was a temporarily lose of the object but re-acquired shortly there after. The crew was able to follow the
object as it appeared to make erratic moments above the water. During the follow, crew was able to obtain
4x zoom on the object but lost the object due to poor track place ent. While following, the sensor operator
was continuously manipulating the sensor to maintain eyes on th1e object. This is apparent by the waves of
the water in the background being visible and not being visible.
Don't use the purple "submit" button! Save this form with filenam "Date_Squadron_RF.pdr' and email
it toj 3.sc, (b)(S) I
(Also in the global) For troubleshooting, cal/I 3.Sc, (b)(B)
Thank you for your time. Please ensure all display tapes are rip11ed for the entire time of interaction and
saved as a .wmv (Example: 4 May VFA-106 HUD.wmv). Squa 1ron lintel personnel shall upload those files
to the repository located at this link.
I 3.5c, (b)(B)
USCENTCOM MDR 26-0019
I Approved for Release to AARO 01/26/26 001
