PURSUE Record — DOW-UAP-D65, Mission Report, Persian Gulf, July 2020: Persian Gulf · 7/16/20

Record DOW-UAP-D65 is a declassified U.S. military Mission Report (MISREP) documenting a Persian Gulf operation on July 16, 2020. Released by the Department of War on May 8, 2026 as part of the PURSUE Release 01 disclosure, it logs a U.S. military operator's account of three separate UAP encounters during a single operational window — making it one of the more densely documented single-day cases in the release.

What this record contains

The document is a single-part PDF released under PURSUE Release 01 by the Department of War. It takes the form of a MISREP — a standardized military format used to record the circumstances surrounding operations and one of the primary conduits through which service members report UAP encounters to the All-domain Anomaly Resolution Office (AARO). The GENTEXT field — a "general text" section designed to capture qualitative, contextual detail rather than numerical data — contains the core reporting. According to the official description, a U.S. military operator documented three distinct UAP encounters on July 16, 2020, at 1830Z, 1920Z, and 2345Z: three events spanning roughly sixteen hours of a single operational period. The release includes a standard caveat that all descriptive and estimative language reflects the reporter's subjective interpretation at the time, and should not be read as a conclusive indication of any intrinsic object features or performance characteristics.

Historical & documentary context

The Persian Gulf sustained intensive U.S. military operations throughout 2020, with patrol and surveillance assets routinely operating in the theater. MISREPs from that environment are filed as a matter of course; what distinguishes DOW-UAP-D65 is that one operator logged three separate anomalous observations across a single duty cycle. The MISREP format is worth understanding as an instrument: it is the same standardized reporting architecture used to document equipment failures, hostile contact, and mission deviations. When a service member files a MISREP for an unexplained observation, they are doing so inside a bureaucratic structure designed for precision, not anecdote — which lends institutional weight to the record's existence regardless of what the encounters ultimately represent.

The timing also matters. By mid-2020 the U.S. Navy had formalized UAP reporting procedures, and AARO's predecessor offices were actively aggregating military encounter data. DOW-UAP-D65 reflects a military culture that had begun to systematically document what operators observed rather than informally dismiss it — a shift that the broader PURSUE Release 01 disclosure was designed to make visible.

What this does and does not prove

What this record establishes is that a U.S. military operator submitted a standardized report describing three anomalous observations during a Persian Gulf operation on July 16, 2020. It does not establish what was observed, whether a conventional explanation exists, or whether the three events are connected. The public release does not include sensor data, imagery, or supplementary analysis alongside this MISREP, and the official description explicitly frames all descriptive language as the reporter's subjective characterization at the time. The case is catalogued as unresolved in the PURSUE Release 01 set — meaning it has not been explained, not that anything extraordinary has been confirmed.

How it fits PURSUE Release 01

DOW-UAP-D65 belongs to the Department of War contemporary mission report strand of the 162-document PURSUE Release 01 disclosure — the portion drawn from active military operational reporting rather than the release's FBI historical files (dating to 1947) or NASA archive imagery. Alongside other MISREPs in the release, it illustrates how the modern U.S. military documents UAP encounters at the operational level and how AARO aggregates those reports into a formal investigative record. For broader coverage of cases across all three strands of the release, see the full PURSUE Release 01 coverage on the SkyLens blog.

Editorial note: This analysis is independent commentary on a publicly released document. The original record, source links, and full release metadata are catalogued on the SkyLens UAP files page alongside every other case in the PURSUE Release 01 set.