Extracted text — DOW-UAP-D56, Range Fouler Debrief, Arabian Sea, August 2020

OCR text extracted from dow-uap-d56-range-fouler-debrief-arabian-sea-august-2020.pdf for full-text search.

Source PDF: </files/disclosure-dossier/dow-uap-d56-range-fouler-debrief-arabian-sea-august-2020.pdf>
Agency: Department of War
Incident: 8/24/20 · Arabian Sea

Declassified by MG Richard A. Harrison
USC Chief
Please do not use the purple
Declassing on. March 2026
button above Save and
Range Fouler Debrief Form
email the complete file manually
(see below).
Please complete this form to the best of your ability. If you do not 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 response within 5 business days.
Last Name, First Name
Rank
Squadron
SIPR Email Address
Crew Position
O-3
HSM-73
Pilot
This information is for contact only. SPEAR sanitizes all reports of identifying information.
Absolutely no identifying information for aircrew or squadron will be recorded for analysis.
08/24/20
00:04:30
Night
705
168122
SSC
No
Date (mm/dd/yy)
Time of detection
Day / Night
Side No.
Buno
Mission Description (CAS, BFM. etc)
LFE?
(hh:mm:ss Z)
21440
21440
1.4a
Yes
310
5
Contact Working Area
Contact Latitute
N/S
Contact Longitude
E/W
Contact Altitude
Altitude
Wind Dir at
Wind
(Ex: W-72 1A)
(DD:MM:SS)
(DD:MM:SS)
(Ex: 22000)
Constant?
Contact All
Speed
(From)
Please attempt to determine a Lat 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 work, 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 of tracking.
270/UNK
(Ex. 090/15)
Radar Equipped: Other
AIM-9x Self-Track:
Please check all that apply:
Stable Trackfile?: No
ATFLIR Autotrack:
Round:
Moving Parts:
Square:
Metallic:
# of Contacts in "Group": 3
Tally Achieved:
Balloon-shaped:
Markings:
EA Indications (Check all that apply):
Wings/Airframe:
Translucent:
Other Shape:
Opaque:
ECM
Letter
False
Other/
Apparent Propuision:
Reflective:
Arc
Identifier
Trackfiles
Ambiguous
Please use the field below to describe the contact and any interaction in your own words with as much
detail as possible. Please be sure to include any detail not included in questions above.
1.4a
observed 3x possible unidentified small air contacts while conducting routine operations in the
North Arabian Sea. Negative ES, radar track, and IFF track. Distance to contact was unknown. Speed of
contact was unknown. Precise course of contact was unknown, but appeared to be on a westerly heading.
No interaction took place between
1.4a
and the unknown air contacts. Initially observed 1x
unknown air contact and tracked it before losing sight as it went behind a cloud. When contact on the
unknown air contact was regained, 2x additional unknown air contacts 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.
Don't use the purple "submit" button! Save this form with filename "Date_Squadron_RF.pdf" and email
it to
(b)(6)
(Also in the global).
For troubleshooting, call
(b)(6)
Thank you for your time. Please ensure all display tapes are ripped 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.
(b)(6)
USCENTCOM MDR 26-0038 to 26-0046
Approved for Release to AARO
03/27/26 000001