PURSUE Release 01: DOW-UAP-D64, Mission Report, Iran, November 2020

DOW-UAP-D64 is a Department of War PDF released in PURSUE Release 01 on May 8, 2026. The release metadata identifies it as a redacted Mission Report for a November 2, 2020 incident in Iran, and describes MISREPs as standardized U.S. military reports whose GENTEXT sections can preserve qualitative UAP reporting context.¹

The seven-page PDF is labeled Misrep 5039166 and carries USCENTCOM MOR 26-0028 release markings. It was declassified by MG Richard A. Harrison, USCENTCOM chief of staff, on March 16, 2026, while retaining national-security and privacy redactions across aircraft, operation, personnel, and location fields.²

  CENTCOM ISR Mission

The record originated as an Air Force mission report from the 482 ATKS, with the 609th listed as operations center, Air Combat Command as major command, and USCENTCOM as combatant command. Its tasking fields identify the domain as air, the service tasked as Air Force, and the broader mission type as air reconnaissance.²

The narrative places the aircraft's takeoff from OKAS at 0608Z on November 2, 2020, and landing back at OKAS at 0250Z on November 3 after 20 hours and 42 minutes of mission time. The mission supported NAVCENT across the Arabian Gulf, Strait of Hormuz, and Gulf of Oman, with ISR tasking to characterize Iranian naval and IRGCN vessels, UAS activity, activity outside ports, and pattern-of-life activity.²

  Two UAP Sightings

The report records a 1012Z guard call from Iranian Air Defense during the same mission. The guard-call section lists the aircraft at FL210, describes the tone as professional, says standard orders were given, and states that the crew gave the standard response with no impact to the mission.²

The first UAP observation appears at 2143Z on November 2. The observation fields place the aircraft at FL220 and 105 KIAS, list full-motion video as the method of observation, and describe one unidentified aerial phenomenon near a redacted location with unknown altitude and a bearing of 080 degrees true.²

The second observation appears five minutes later, at 2148Z. The aircraft fields again show FL220, with airspeed listed as 107 KIAS, and the observation narrative says an additional UAP was traveling northwest near a redacted location.²

  PDF Without Paired Media

The release entry provides the D64 PDF and an official thumbnail image, but its video-pairing and PDF-pairing fields are blank. No paired PR media is identified for this record, so the public evidence is the written MISREP and its catalog summary rather than a separately released video or still-image package.¹³

  What D64 Establishes

D64 matters because it preserves two UAP observations inside a broader CENTCOM/NAVCENT ISR mission record. The PDF gives the reporting chain, mission timing, sensor method, aircraft state, guard-call context, and redaction boundaries, while still withholding enough platform and location detail to prevent a complete public reconstruction of the event.¹²

The narrow factual reading is that a U.S. military operator reported two UAP during a November 2, 2020 mission: one at 2143Z with unknown altitude and one at 2148Z described as traveling northwest. The record does not identify either object or establish unusual performance beyond the reporter's contemporaneous observation language.¹²

  References

  References

1. war.gov ↩ ↩² ↩³ ↩⁴

2. war.gov ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

3. war.gov ↩