DOW-UAP-D56, Range Fouler Debrief, Arabian Sea, August 2020
Department of War · 2020-08-24 · Arabian Sea · release 1
This document is a Range Fouler Debrief Form, 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 three “unidentified small air contacts” over the North Arabian Sea. The reporter described the UAP as having “wings/airframe” structure, and as initially bearing on a westerly heading. The operator tracked one UAP before losing sight of it behind a cloud. Upon regaining contact, the operator reported observing two additional UAP to the east of the first. The report states that all three objects then “appeared to maintain their relative course, speed, and altitude.”
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.
I D b ·
ange OU er e ne orm
S&Sli&i!lllll lfUI
F
F
R
Deel
u..
Deel;
(see below).
11 ,1son
d
purple
,Ge. ve and
manually
Please complete this form to the best of your ability. If you do
please leave the field blank.
form for data collection purposes. You should receive a response within ·5 business days.
If there was more than one "group " please report each on a separate
have the requested informafion,
L
Last Name, First Name
Rank
Squadron
S/PR Email Address
Crew Position
0-3
IHSM-73
Pilot
This information is for contact only. SPEAR sanitizes all reports of identifying information.
Absolutely no identifying information for aircrew or squadrJn will be recorded for analysis.
08/24/20
00:04:30
Night
705
168122
SSC
Date (mmlddlyy)
Time of detection
(hh:mm:ss Z)
Day I Night
Side No.
Buno
Mission Description (CAS, BFM. etc)
No
LFE?
21440
21440
1.4a
Yes
Contact Working Area
(Ex: W-72 1A)
Contact Latitute
(0D:MM:SS)
N/S
Contact Longitude
(DD.MM:SS)
Contact Aftitude
( ' · : 22000)
Altitude
Constant?
310
WtndDir at
Contact An
(From)
5
Wind
Speed
Please attempt to determine a Lat I Long for the contact at initial detection. We recommend
µsing JMPS to reference the sensor-derived bearing and range relative to the bullseye yo u had
in use. If that method is not available, any reasonable derivation of location will wolk, but please
be as specnic as possible and make a note in the comments section. The.se locations may be
used to cue other means of tracking.
recommend
µsing JMPS to reference the sensor-derived bearing and range relative to the bullseye yo u had
in use. If that method is not available, any reasonable derivation of location will wolk, but please
be as specnic as possible and make a note in the comments section. The.se locations may be
used to cue other means of tracking.
Radar Equipped: Other
Stable Trackfile?: No
# of Contacts in "Group": 3
EA Indications (Check all that apply):
AIM-9x Self-Track: □
A TFLIR Autotrack: □
Tally Achieved: □
Was the contact moving? Yes
Direction/Speed
(Ex. 090/15)
2?0/UNK
Please check all that apply:
Round: [Z]
SQuare: D
Bafloon-shapeq: D
Wings/A irframe: [Z]
Moving Parts: 0
Metallic: 0
Markings: D
Translucen t: 0
□ □ □ □
False
Other/
ECM
Art'
Letter
Identifier
Trackfiles Ambiguous
Other Shape:O
Opaque: O
Apparent Propuls io n:□ Reflective! 0
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 inclilided in questions above.
1.4a
!observed 3x possible unidentified small air contact I while conducting routine operations in the
J
North Arabian Sea. Negative ES, radar track, and IFF track. Distf nce to contact was unknown . Speed of
contact was unknown. Precise course of contact was unknown, but appeared to be on a westerly heading .
No interact~on took place betwee~I
unknown air contact and tracked It before losing sight as 1t went 9ehInd a cloud. When contact on the
unknown air contact was regained , 2x additional unknown air
was unknown. Precise course of contact was unknown, but appeared to be on a westerly heading .
No interact~on took place betwee~I
unknown air contact and tracked It before losing sight as 1t went 9ehInd a cloud. When contact on the
unknown air contact was regained , 2x additional unknown air corytacts were seen due east of the location of
the initial contact. All 3x unknown air contacts appeared to maintain their relative course, speed, and
altitude.
la~d the ~nknowp ai_r contacts. Initially observed 1x
1.4a
.
I
Don't use the purple "submit" button! Save this form with filename "Date_Squadron_RF.pdf' and email
it t~
J(Also in the global)j For troubleshooting, cal~
1•>1•>
1•>1•>
I
Thank you for your time. Please ensure all display tapes are ripAed 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
IIIRl ■ :1112 5771 I
I
(b)(6)
I
USCENTCOM MOR 26-0038 to 26-0046
Approved for Release to MR9
03/27126 000001