DOW-UAP-D42, Range Fouler Debrief, Japan, 2023
PDF Department of War INCIDENT 8/31/20 · Arabian Gulf
DOW-UAP-D42, Range Fouler Debrief, Japan, 2023
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 observing an “object fly through the screen.” The observer described a second object surpassing the first, at a higher speed. The report describes a total of three UAP “moving amongst each 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.
loading viewer…
Download
Metadata
Extracted Text
show full text
•
MeasJN�o not �se . {tle,,.J?,-irp e
U., rsu6hirf r
· IH0 cl 1tted v Ml Ric {..;,. d (\ rr '>Of'
'&uf�� ��ov,e'":'� $aJJe and
[1 r I �sili , J,1
rH oltl G: b If r'Wri,'
\See ue ow.
Range Fouler Debrief Form f- 1uol1;<l!!'J"1eL_�)�q��p1l s y
9 manua
1
Please complete this form to the best of your ability. If you do not have the requested information,
please leave the fi�ld blank. If there was more t��n one "group!" � le�se rep�rt each on a separate
form for data collection purposes. You should receive a response within 5 business days.
j482ATKS
Rank
Pilot
Last Name, First Name Squadron SfPR Email Address Crew Position
0-2
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.
08/31/20 Dusk ISR No
Date (mmldd,YY) Time of detection Day I Ni;:,ht Side No. Buno Mission Description (GAS, BFM, etc) LFE?
{tlh:mm:ss Z)
{b)(1)Ua 118000 Yes
Contact Worl<ing Area Contact Latitute N/S Contact Longitude EMI Contact Altitude Altitude Wind Dir at Wind
(Ex: W-72 1A) (DD:MM:SS) (0D:MM:SS) ( x: 22000) Constant? Contact Alt Speed
(From)
Yes
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?
in use. If that method is not available. any reasonafJ/e derivation of location will worl<, but please
150/230
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
AIM-9x Self-Track: Please check all that apply:
(Ex. 090/15)
Radar Equipped: Other
A TFL/R Autotrack:
□
# of Contacts in "Group":
Stable Trackfile?:
□
• Tally Achieved: □
Round:
Square: D
D Moving Parts: D
Metallic: D
Balloon-shaped: D Markings: D
EA Indications (Check af/ that apply):
Wings/Airframe: D D
□ □ □ □
Translucent
Other Shape:[Z] Opaque: D
ECM Letter False Other/ Apparent Propulsion.@ Reflective: D
Plesse use the field below to describe the contact and any inte. action in your own words with as much
An: tdenlifii,r Trackfiles Ambiguous
detail as possible. Ple.ase be sure to include any detail not inc/ 1 ded in questions above.
MGRS Grid of initial contact: 39RWL2fijij.1:Mlm]a I
Saw the initial object fly through the screen and started tracking i . Initial object was surpassed by another
object of same size and shape but much higher speed. At one p4int during tracking the objects, there were
three on the screen at the same time moving amongst each other.
I
Don't use the purple "submit" button! Save this form with fl/enaml "Date_Squadron_RF.pdf" and email
it to I 3.5c, (bl{6l I (Also in the global)� For troubleshooting, call I 3.5c, <b)(6) I
Thank you for your time. Please ensure all display tapes are ripJed for the entire time of interaction and
saved as a . wmv (Example: 4 May VFA-106 HUD. wmv). Squa ron intel personnel shall upload those files
to the repository located at this link.
f 3.5c. {b)(6) I
USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26 000001
