DOW-UAP-D042, Range Fouler Debrief, Japan, 2023
This file is a standardized U.S. Navy 'Range Fouler Debrief Form' used to record circumstances surrounding an unauthorized intrusion into controlled airspace during active military operations or training. According to the source page context, a U.S. military operator (an O-2 pilot) reported observing an object 'fly through the screen,' followed by a second object of the same size and shape moving at much higher speed, ultimately observing a total of three UAP 'moving amongst each other.' The form captures sensor/detection details including a detection time at dusk on 08/31/20, an MGRS grid reference, and contact shape characterized as 'other/ambiguous.' The releasing agency notes all descriptive and estimative language reflects the reporter's subjective interpretation and should not be treated as conclusive evidence of any object features or performance. The document is heavily redacted (identifying information for aircrew and squadron sanitized by SPEAR) and bears the control number USCENTCOM MOR 26-0028, 'Approved for Release to MRO.' Note a discrepancy: the filename references Japan/2023 while the source-page Incident Location field states Arabian Gulf and the form and page list an incident date of 08/31/20.
Description
A declassified U.S. Navy Range Fouler Debrief Form documenting an unauthorized airspace intrusion by unidentified anomalous phenomena during military operations, in which an operator observed multiple objects maneuvering on a sensor screen. Released by the U.S. Department of War with redactions.
Claims
The incident occurred at dusk on 08/31/20.
75%A U.S. military operator observed an object 'fly through the screen' during active operations.
70%A second object of the same size and shape surpassed the first at much higher speed.
70%A total of three UAP were observed 'moving amongst each other' on the screen simultaneously.
70%The observation occurred at dusk on 31 August 2020 over the Arabian Gulf at approximately 18,000 ft altitude.
70%A U.S. military operator observed an object 'fly through the screen,' followed by a second object of the same size and shape moving at much higher speed.
60%At one point three UAP were on the screen simultaneously 'moving amongst each other.'
60%The incident location was the Arabian Gulf (per source page), despite the filename referencing Japan.
55%
Events
Aug 30, 2020
UAP observation / range fouler event
Operator observed an object fly through the sensor screen, surpassed by a second faster object, with a total of three UAP moving amongst each other at dusk.
May 7, 2026
Public release by Department of War
Document released with redactions via war.gov UAP data release.
Aug 30, 2020
UAP observation over Arabian Gulf
Aircrew observed an object fly through the sensor screen, a second faster object surpassing it, and at one point three objects moving amongst each other, detected at dusk.
May 7, 2026
Official release by Department of War
Document released as part of a UAP data disclosure (release_3).
Dates mentioned
Keywords
Entities
Programs
Places
Extracted text (OCR)
•
·
IH
MeasJN�o not �se . {tle,,.J?,-irp e
r
U., rsu6hirf
'&uf�� ��ov,e'":'� $aJJe and
[1 r I �sili , J,1
rH oltl
G: b If
9 manua
y
)�q��p1l s
Range Fouler Debrief Form f- 1uol1;<l!!'J"1eL_�
\See ue ow.
1tted
0 cl
v Ml Ric {..;,. d (\
rr '>Of'
r'Wri,'
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.
Rank
Last Name, First Name
0-2
j482ATKS
Squadron
Pilot
SfPR 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 squadr! n will be recorded for analysis.
08/31/20
Date (mmldd,YY)
Dusk
Time of detection
Day I Ni;:,ht
{tlh:mm:ss Z)
Side No.
ISR
Buno
Mission Description (GAS, BFM, etc)
{b)(1)Ua
Contact Worl<ing Area
(Ex: W-72 1A)
Contact Latitute
(DD:MM:SS)
N/S
Contact Longitude
(0D:MM:SS)
EMI
118000
Contact Altitude
( x: 22000)
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
in use. If that method is not available. any reasonafJ/e 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.
# of Contacts in "Group":
Stable Trackfile?:
EA Indications (Check af/ that apply):
□ □ □ □
ECM
An:
Letter
tdenlifii,r
False
Yes
Wind Dir at
Contact Alt
(From)
Altitude
Constant?
Was the contact moving?
Direction/Speed
(Ex. 090/15)
AIM-9x Self-Track:
Radar Equipped: Other
No
LFE?
Wind
Speed
Yes
150/230
Please check all that apply:
□
A TFL/R Autotrack:
□
• Tally Achieved: □
D
Square: D
Balloon-shaped: D
Wings/Airframe: D
Round:
Other/
Ambiguous
D
Metallic: D
Markings: D
Moving Parts:
Translucent
Other Shape:[Z]
Opaque:
Apparent Propulsion.@
Reflective:
Plesse use the field below to describe the contact and any inte. action in your own words with as much
detail as possible. Ple.ase be sure to include any detail not inc/ 1 ded in questions above.
Trackfiles
MGRS Grid of initial contact: 39RWL2fijij.1:Mlm]a
D
D
D
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)
USCENTCOM MOR 26-0028
I
Approved for Release to MRO. FOUO / PA applies
03/16/26 000001
Related files
Connected through the network
SF-2026-000238
DOW-UAP-D058, Range Fouler Debrief, NA, October 2020
SF-2026-000248
DOW-UAP-D064, Mission Report, Iran, November 2020
SF-2026-000250