This is a Range Fouler Debrief, a standardized Navy reporting form completed after a crew detected an unidentified object during an intelligence surveillance and reconnaissance (ISR) mission on May 14, 2020, in the Middle East. The form captures details about the sighting, including the object's location, behavior, and the crew's ability to track it.
What is a Range Fouler Debrief?
A Range Fouler Debrief is a standardized reporting form the U.S. Navy uses to record the circumstances surrounding an unauthorized intrusion. The form asks crews to document contact information, radar data, visual characteristics, and a detailed narrative of what happened.
What did the crew observe?
During an ISR tasking, a solid white object flew through the camera's field of view. The crew initially lost sight of the object but re-acquired it shortly after. While following the object, the crew obtained 4x zoom but eventually lost it due to poor track placement. The form indicates the object appeared to make erratic movements above the water.
What sensor data was collected?
The form shows the contact was detected at 20:40:00 on May 14, 2020. The radar trackfile was intermittent, meaning it was not continuous. The crew was able to follow the object, and the sensor operator continuously adjusted the sensor to maintain visual contact, as evidenced by the visibility of water waves in the background changing throughout the recording.
How was the object described?
The form lists checkboxes for various characteristics like round shape, moving parts, metallic appearance, wings, and propulsion. However, the specific boxes checked or unchecked are not clearly legible in the provided document text. The narrative describes the object as solid white.
Full Document Text
Text extracted directly from the source PDF. Text extraction via abigailhaddad/ufo-releases; original file at war.gov.
Read the full text (6,502 characters)
--- PAGE 1 ---
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 View the official fileFrequently Asked Questions
What was the object's appearance?
The form describes the contact as a solid white object. The crew obtained 4x zoom magnification during the encounter, but the specific physical characteristics checked on the form (such as shape or metallic properties) are not clearly legible in the provided document.
Did the crew maintain continuous radar contact?
No. The form indicates the radar trackfile was intermittent, meaning the radar contact was not stable or continuous throughout the encounter.
Stable Trackfile?: Intermittent
Was the object moving?
Yes, the form confirms the contact was moving. The crew observed the object appearing to make erratic movements above the water, though they eventually lost it due to poor track placement.
Was the contact moving? Yes
What happened during the encounter?
While performing an ISR tasking, the crew detected a solid white object that flew through their camera's field of view. They temporarily lost the object but re-acquired it shortly after. The sensor operator continuously adjusted the sensor to maintain visual contact, and the crew obtained 4x zoom magnification. The encounter ended when the crew lost the object due to poor track placement.
Congressional Context
Where this record connects to the congressional record and the people in it.
- Involves OrganizationAARO (All-domain Anomaly Resolution Office)
- Referenced in LegislationNational Defense Authorization Act for Fiscal Year 2024Connected through AARO (All-domain Anomaly Resolution Office)
- Referenced in LegislationJames M. Inhofe National Defense Authorization Act for Fiscal Year 2023Connected through AARO (All-domain Anomaly Resolution Office)
- Referenced in LegislationServicemember Quality of Life Improvement and National Defense Authorization Act for Fiscal Year 2025Connected through AARO (All-domain Anomaly Resolution Office)
- Referenced in LegislationTo terminate the All-domain Anomaly Resolution Office of the Department of Defense, and for other purposes.Connected through AARO (All-domain Anomaly Resolution Office)
- Discussed in HearingSenate Armed Services Subcommittee UAP HearingConnected through AARO (All-domain Anomaly Resolution Office)
Related Intelligence
Range Fouler
A range fouler is a term that appears on official debrief and reporting forms used to document encounters for data collection purposes.
Open fileAARO (All-domain Anomaly Resolution Office)
AARO is a Pentagon office established in 2022 to detect, identify, and investigate unidentified anomalous phenomena across U.S. military operations.
Open file