View original document (1.8 MB)
A newly released U.S. Department of War document details a 2020 incident in which a U.S. Navy pilot reported encountering three unidentified aircraft over the Arabian Sea, describing them as having a “wings/airframe” structure. According to Department of War records released under the PURSUE archive on May 8, 2026, the document, titled “DOW-UAP-D56, Range Fouler Debrief, Arabian Sea, August 2020,” is a standardized reporting form used by the Navy to record unauthorized intrusions into controlled airspace during active operations or training.
Document Details: The August 2020 Encounter
The report, dated August 24, 2020, states that a U.S. military operator—identified in the form as a pilot with the rank of O-3, assigned to squadron HSM-73—detected three “unidentified small air contacts” over the North Arabian Sea. The time of detection was recorded as 00:04:30 Zulu at night. The operator reported that the first object was initially bearing on a westerly heading. The pilot tracked one UAP before losing sight of it behind a cloud. Upon regaining visual contact, the operator reported observing two additional UAP to the east of the first object. The document notes that all three objects then “appeared to maintain their relative course, speed, and altitude.”
The form includes a checklist for describing the objects’ characteristics. The operator indicated a “wings/airframe” structure, and checked boxes for “Metallic” appearance and “Other Shape,” while leaving boxes for “Balloon-shaped,” “Translucent,” “Opaque,” “Reflective,” and “Markings” unchecked. The report also notes that the operator did not achieve a “Tally” (visual acquisition) and that the radar trackfile was not stable. The contact’s speed was listed as “UNK” (unknown), with a direction of 270 degrees. The operator reported no electronic attack (EA) indications. The form lists the contact altitude as 31,000 feet, with a wind direction of 310 degrees and a constant wind speed of 5 knots.
The Department of War’s official description of the document emphasizes that all descriptive and estimative language reflects the reporter’s subjective interpretation at the time of the event. The agency cautions that such characterizations “should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.” The document’s summary offers limited detail beyond the operator’s narrative, noting that the form is used for data collection purposes and that the Navy’s SPEAR office sanitizes all reports of identifying information.
Context and Broader UAP Background
The release of this document is part of the Department of War’s PURSUE archive, a public repository for UAP-related records. The document itself is a Range Fouler Debrief Form, a standardized tool the Navy uses to record unauthorized airspace intrusions. The form includes fields for mission description—in this case, “LFE” (likely a large force exercise) was marked “Yes”—and notes the pilot’s crew position and the aircraft’s Bureau Number (Buno), though identifying details have been sanitized per policy.
Per a Wikipedia summary of reported UFO sightings, unidentified flying objects are generally considered to include any perceived aerial phenomenon that cannot be immediately identified or explained. The Wikipedia entry notes that upon investigation, most UFOs are identified as known objects or atmospheric phenomena, while a small number remain unexplained. The entry also explains that the term “unidentified anomalous phenomena” (UAP) is sometimes used to avoid cultural associations with UFO conspiracy theories. This document, filed as a UAP report, falls under that broader category of unexplained aerial observations.
The incident occurred in the Arabian Sea, a region of active military operations and training. The document does not specify the exact mission type beyond “LFE,” and the operator’s report does not identify the objects as any known aircraft or drone. The lack of a stable radar trackfile and the operator’s inability to achieve visual tally suggest the encounter was brief and inconclusive from a tracking perspective.
What Remains Unanswered
Several questions remain unanswered by this document. The report does not provide any explanation for the objects’ origin, propulsion, or purpose. The operator’s description of “wings/airframe” structure suggests a conventional aircraft design, but the absence of electronic attack indications and the objects’ ability to maintain formation after the pilot’s initial loss of contact leave the nature of the encounter open to interpretation. The Department of War’s caution that the report reflects subjective interpretation underscores the limitations of the data.
Readers should watch for future PURSUE archive releases, which may include additional debrief forms, sensor data, or analysis from other incidents in the region. The Department of War has not indicated a schedule for further releases, but the PURSUE archive remains a public resource for reviewing historical UAP reports. As with this document, future records may provide further context for understanding the frequency and characteristics of unauthorized airspace intrusions reported by U.S. military personnel.
