The Range Fouler system, what a standardised intrusion form actually tells you

Mikey · 21 May 2026

THE DOCUMENT

A set of Range Fouler debrief and reporting forms from PURSUE Release 01: DOW-UAP-D38 (Middle East, May 2020), DOW-UAP-D42 (Japan, 2023), DOW-UAP-D44 (Gulf of Aden, October 2020), DOW-UAP-D56 (Arabian Sea, August 2020), DOW-UAP-D57 (Gulf of Aden, September 2020) and DOW-UAP-D58 (October 2020). US Navy aircrew records, internally declassified by USCENTCOM and published by the U.S. Department of War at war.gov/ufo.

What this briefing is

Most briefings in this series take one document and ask what it shows. This one takes six documents and asks what they have in common. The answer is the point. They are all copies of the same form.

Briefing 1 noted in passing that the Range Fouler debrief deserved a briefing of its own. This is that briefing. It is not really about any single sighting in these six files. It is about the form itself, and about what it means that the US military has a standardised, pre-printed intake form for logging objects that intrude into its airspace and cannot be identified.

This is tier 2 material, primary documents. The forms are authentic and official. That establishes the existence and shape of a process. It does not, on its own, establish that anything logged on them is anomalous.

What a “range fouler” is

“Range fouler” is older military shorthand. A range is a block of airspace or sea space set aside for training, weapons practice or operations. A range fouler is anything that intrudes into that space when it should not be there: a stray boat, a civilian aircraft, a drone, a balloon, or an object the crew cannot identify. The term is deliberately neutral. It describes a problem of airspace management, not a claim about what the intruder is.

What PURSUE Release 01 shows is that the US Navy turned this neutral category into paperwork. There is a printed form, titled “Range Fouler Debrief Form” or “Range Fouler Reporting Form”, and the release contains several filled-in copies of it.

The anatomy of the form

Read across the six files and the template is identical. It is worth walking through it field by field, because the structure is the finding.

The form opens with a banner instruction telling the user not to press the purple “submit” button, but to save the file with a set filename, “Date_Squadron_RF.pdf”, and email it manually. That single line tells you this is a routine, circulated document with version quirks and a known workflow, not a one-off memo.

It then asks for identifying details: last name and first name, rank, squadron, secure email address and crew position. Directly beneath that block sits an explicit notice: “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.” SPEAR is the program the release documents refer to for handling these reports. The form is built so that the analytical copy is stripped of names. That is a deliberate design choice, and it tells you the Navy expected these reports to flow into a central analysis process where the observer’s identity was irrelevant and protected.

The form then asks for the observation basics: date, time of detection in Zulu, day or night, side number and bureau number of the aircraft, mission description, and whether a large force exercise was underway. In the D38 file the crew were flying an ISR, intelligence, surveillance and reconnaissance, tasking. In D58 the mission is logged as DCA, defensive counter air.

Next comes a block of geometry and environment fields: contact working area, latitude, longitude, contact altitude, whether the altitude was constant, wind direction and wind speed. The form even includes a printed instruction recommending the crew use JMPS, a mission-planning system, to derive a position from the sensor bearing and range, and notes that “these locations may be used to cue other means of tracking.” That last phrase is significant. The form is not just an after-the-fact record. It is designed to feed other sensors and other assets, in something close to real time.

Then a block of sensor and tracking fields: radar equipped, stable trackfile, number of contacts in the group, electronic-attack indications, and tick boxes for AIM-9x self-track, ATFLIR autotrack and “tally achieved”, meaning the crew got eyes on the object.

Then a physical description checklist: round, square, balloon-shaped, wings or airframe, other shape, apparent propulsion, moving parts, metallic, markings, translucent, opaque, reflective. The observer ticks whatever applies.

Finally a free-text block, headed by an instruction to “describe the contact and any interaction in your own words with as much detail as possible”, and a closing instruction to rip all display tapes for the full interaction and save them as .wmv video files for upload to a repository.

Every one of the six files carries a declassification stamp, attributed to a USCENTCOM officer, and a line reading “Approved for Release to AARO”. That is the authenticity anchor described in Briefing 1.

What the six filled-in copies look like

The individual contents are secondary to the form itself, but they show the form in use.

D38, from the Middle East in May 2020, records a night ISR mission in which “a solid white object flew through the FOV”, the sensor field of view, and made “erratic moments above the water.” The crew ticked “Round.”

D44 and D57, both from the Gulf of Aden in late 2020, are near-identical in style: each describes “a round, cold object in IR” tracked for a minute or several minutes, making “a few abrupt directional changes”, logged with a heading and a speed. D44 puts the object at 319 degrees and 20 mph; D57 at 168 degrees and 277 mph. Both note the infrared sensor was set to black hot, with the object appearing bright white.

D56, from the Arabian Sea in August 2020, logs three “possible unidentified small air contacts” with “negative ES, radar track, and IFF track”, meaning no electronic signature, no radar lock and no identification-friend-or-foe return, all maintaining relative course, speed and altitude.

D42, from Japan in 2023, describes an initial object that “was surpassed by another object of same size and shape but much higher speed”, and a moment when “there were three on the screen at the same time moving amongst each other.”

D58, from October 2020, is the most detailed. A crew were directed to identify an unknown contact, “obtained radar lock and target pod video”, saw “2 IR significant contacts”, one “circling around the other”, and recorded that “in 1/30th of a second, they were gone.” The crew also logged noise jamming.

These descriptions vary in how striking they are. Some, given complete data, would likely resolve into drones, birds, balloons or sensor artefacts. The point of this briefing is not to adjudicate any one of them. It is that all six were captured on the same form, in the same fields, by the same process.

Why the form itself is the story

A government does not design, print, circulate and centralise an intake form for a problem it considers a novelty. Forms are what bureaucracies build for recurring, expected events.

The Range Fouler form tells you several concrete things about how the US military actually treats unidentified airspace intrusions. It treats them as a recurring operational problem, frequent enough to justify a standard template rather than ad hoc reporting. It treats them as something to be measured consistently, which is why the form forces every observer through the same geometry, sensor and shape fields, so that reports can be compared. It treats them as something to be fed into analysis, through the SPEAR sanitisation step and the central repository for sensor video. And it treats the location data as something that can cue other assets, which means these reports are part of an operational loop, not just an archive.

None of that is a claim about what the objects are. A balloon intruding into a training range is a range fouler, and the form would log it just the same. The value of the form is procedural. It is documentary proof that, inside the US Navy, encounters with objects aircrew cannot identify are normal enough to have their own paperwork, their own data fields, their own privacy-protection step and their own evidence-handling chain.

What it reliably establishes

It establishes that the US Navy maintains a standardised, structured intake form for logging airspace intrusions, including intrusions by objects the aircrew cannot identify. It establishes that this form is built to feed a central analysis process, that it strips identifying information before analysis through the program the documents call SPEAR, and that it requires the preservation and upload of the underlying sensor video. It establishes that this process generated multiple reports across several theatres, the Middle East, the Gulf of Aden, the Arabian Sea, Japan, within a short span of 2020 to 2023. And it establishes that these reports were classified, held, reviewed and released through an official, traceable channel to AARO.

What it does not establish

It does not establish that any object recorded on these forms is extraterrestrial, or even unexplained once fully analysed. The form is deliberately neutral. It would log a drone, a balloon or a sensor glitch in exactly the same fields. The descriptions in the six files are field observations, not verdicts.

It does not establish how many Range Fouler forms exist in total, how many describe genuinely puzzling objects versus ordinary intruders, or what SPEAR’s analysis concluded in any individual case. The release gives us the form and a handful of completed copies, not the full dataset or its findings.

And it does not establish a cover-up. A standardised reporting form is the opposite of suppression. It is the infrastructure of a process that expects these events, records them in a consistent way, and routes them somewhere to be looked at.

Related wiki entries

The wiki entries below give background on the people, programmes and document types behind this briefing.

PURSUE · Department of War · USCENTCOM · Range Fouler · U.S. Navy · AARO

References and further reading

• DOW-UAP-D38, Range Fouler Debrief, Middle East, May 2020, hosted at war.gov
• DOW-UAP-D42, Range Fouler Debrief, Japan, 2023, hosted at war.gov
• DOW-UAP-D44, Range Fouler Reporting Form, Gulf of Aden, October 2020, hosted at war.gov
• DOW-UAP-D56, Range Fouler Debrief, Arabian Sea, August 2020, hosted at war.gov
• DOW-UAP-D57, Range Fouler Reporting Form, Gulf of Aden, September 2020, hosted at war.gov
• DOW-UAP-D58, Range Fouler Debrief, October 2020, hosted at war.gov
• Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
• Briefing 1 in this series, on how to read PURSUE Release 01 and the evidence-tier system