D75 USCENTCOM MISREP
The Department of War's PURSUE Release 01 identifies DOW-UAP-D75 as a redacted PDF mission report released on May 8, 2026, with an incident date of July 14, 2024 and the Gulf of Aden as the incident location.1 The release describes MISREPs as standardized military operational reports and notes that services often use them to pass UAP reporting to AARO, especially through narrative GENTEXT sections that add context beyond numeric fields.1
The PDF itself is USCENTCOM MISREP 10194673. Its repeated header and footer place it in USCENTCOM MDR 25-0072, show a June 2, 2025 recommendation by MG Brandon R. Tegtmeier as USCENTCOM Chief of Staff, mark the document SECRET//REL TO USA, FVEY with FOUO and Privacy Act handling, and show approval for release to AARO.2
July 14 ISR Sortie Timeline
The narrative describes an Air Force ISR sortie that took off at 0222Z on July 14, arrived on station at 0300Z, worked a NAVCENT target-development tasking from 0334Z to 0925Z, observed one UAP at 0517Z, then later worked an AFCENT target-development tasking from 1041Z to 2130Z before handback and landing at 2259Z.2 Many aircraft, unit, location, mission, and target details are redacted under national-security and privacy exemptions.2
The administrative fields identify the report type as MISREP, domain as air, operations center as 609th, major command as ACC, combatant command as USCENTCOM, originator as 124 ATKS, country tasked as the United States, and service tasked as Air Force.2 The mission sections list FMV as the primary sensor, describe support to NAVCENT and AFCENT taskings, and state that weather was not a factor for the NAVCENT segment.2
Benign UAP Entry
The UAP section records initial contact at 140517ZJUL24. It classifies the entry as a UAP incident, lists straight and same-altitude flight as the maneuverability observation, gives unknown response to observer actions, unknown propulsion, unknown intelligent control, and unknown advanced capabilities or materials, and marks the observer assessment as benign.12
The report records no sensor interrogation of the UAP, no observer engagement, no effects on people, no recovered material, and no equipment effects. It places the first and last coordinates in redacted military grid references, estimates the first and last sighting radii at five, lists altitude as low, depth as unknown, trajectory as northwest, and says the crew followed the UAP until it became too distant to track.2
The release metadata summarizes the same event as a U.S. military operator's report of one UAP on July 14, 2024. It also preserves the caution that descriptive and estimative language reflects the reporter's interpretation at the time and should not be treated as a conclusive determination of object features or performance.1
No Cataloged Video Pairing
The PURSUE metadata gives D75 an official PDF link and thumbnail preview, but leaves the video pairing, PDF pairing, DVIDS video ID, and DVIDS video title fields blank.13 This means the public D75 record is a document-and-thumbnail release, not a mission report formally paired in the catalog with a public PR video.1
What the Record Supports
DOW-UAP-D75 is useful because it preserves the path by which a Gulf of Aden sensor observation entered a military operational reporting workflow: an ISR mission report, a USCENTCOM review/release marker, and Department of War release metadata. The PDF supports a narrow conclusion that one UAP was reported during the NAVCENT portion of the sortie, assessed as benign by the observer, and recorded with several negative fields; it does not identify the object or establish extraordinary performance.12