DOW-UAP-D062, Mission Report, Strait of Hormuz, September 2020
This document is a Mission Report (MISREP), a standardized reporting form the U.S. Military uses to record the circumstances surrounding its operations. U.S. military services often use MISREPs to report Unidentified Anomalous Phenomena (UAP) to AARO. The GENTEXT, or “general text” section of these reports often contains important qualitative, contextual information, distinguishing it from the more quantitative, or numerical, data found elsewhere in the report. A U.S. military operator reported observing one UAP at an estimated altitude of 1,800 feet. All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 962 words from pages 1, 2, 3, 4, 5, 6, 7, 8, 9 of 9.
PAGE 1
Declassified by MG Richard A. Hanison USCENTCOM Chief of Staff Declassified or: 22 January 2026 AT 2302Zn::iil]TOOK OFF FROM OK.AS. Af 2313Z,~ HANDED OVER FROM Tl:iE LRE, FROM 23462 TO l902Z,G1a:JCOLLECi ED SIGINT VIA AIRHANDLER. FROM 03182 TO GULF, STRAI'l OF HORMUZ AND GULF OF OMAN, SEE ISR!LINE 1. AT 04082.! 1.4a 'RECEIVED A GUARD CALL SEE GUARD CALL LINE 1. AT 042 IZ,[ii;JRECEIVED A GUARD CALL. SE'E GUARD CALL LINE 2. AT l 141Z.~ RECEIVED A GUARD CALL SEE GUARD CALL LINE 3. AT 1248Z,~ LOST LINK SEE EMJ LINE 1. AT 14142:J 1.4a !LOST LINK. SEE CLEARED TO RTB, AT 19232,G:;]BANDf:D BACK TO TliS LRE. AT l 958Z,~ LANDED AT TASKING PROSECUTED, 19.3 S1GTNT HOURS, 1 SIGINT TAS ING PROSECUTED. 2 TOTAL • Associated Caveats: • Classification Source (MS ot Classification Guide ID): MUL11IPLE SOURCES • Declassification Date (YYYYMMDD): 20450301 • Domain: AIR • Combatant Command (COCOl\'I): USCENTCOM • Originator (Unit or Squadron): 482ATKS • Submit Date (Auto-generated): USCENTCOM MOR 26-0019 Approved for Release to MRI 01/ 26/26 001
PAGE 2
• Tasking Order (ATOE;] • Mission Type: AREC • Country Tasked: US -UNITED STATES • Service: Air Force • Operations Center: 609 CAOC • Wing: Other • Service: Air Force • Operations Center: Other • Rank: SrA • Wing: Other • Service: Air Force • Operations Center: 609 CAOC USCENTCOM MOR 26-0019 Approved for Release to MRO 01/ 26/26 002
PAGE 3
Deel ., ed by MG Richard A Harr so Declass ed or 22 Ja uary 2026 • Phone Number: • Operations Center: • Radar Name or Destination: - • Radar Software Load or Mission Data: - • Radar Warning Receiver (RWR) Name or Designator: - • RWR Software Load or Mission Data: - • MWS Software Load or Mission Data: - • IRCM Name or Designator: - • IRCM Software Load or Mission Data: - • ECM Name or Designator: - • ECM Software Load or Mission Data: - • Num Chaff or Cartridges: - • Towed Decoy Name or Designator: - • Towed Decoy Software Load or Mission Data: - • Num Towed Decoys: - • Type of Radar-Guided AAM: - • Num Radar-Guided AAM: - • Type of IR-Guided AAM: - • Num IR-Guided AAM: - • Gun Name or Designator: - • Num Guo Rounds: - • Air-to-Ground Wpn to Include Num of Each: • Additional Avionics: AH_G MESH
PAGE 4
USCENTCOM Cl' ef of Staff • Last Land Location (ICAO Code): OKAS • Last Land Time: 161958:00ZSEP20 • Last Engine Shutdown Time: 162008:00ZSEP20 • Total Mission Time: 20 hours 56 minutes • Number of Aircraft: I- -- • Takeoff Location (ICAO Code): OK.AS • Mission Canceled: On Station • Mission Type: AREC • Did not Arrive On Station: USCENTCOM MOR 26-0019 Approved for Release to MRO 01/ 26/26 004
PAGE 5
• Tasking Type: PLANNED • BE Number (ifNTISR): - • Tasked Start Point: 40RCQ3@}~1.4a! • Activity Description: ISR • FMV or Image File Name (ifNTISR): - TO TAKE OFF. PRECOORD WAS SATISFACTORY. AT 03182, 1.4a ARRNED ON STATION ISO UAS ACTIVITY, ACTIVITY OUTSIDE OF PORTS, AND TO E~TABLISH PATTERN OF LIFE. FROM 03182 TO 18292,~CONDUCTED SCANS IAW Tl-Ir TARGET DECK IN THE ARABIAN GULF (AG). AT 0930Z~OBSERVED AN IR-!t-5 LAUNCHER IVO GUARD CALL. SEE GUARD CALL LINE 1. AT 04212,0]i] C~IVED A GUARD CALL. SEE GUARD CALL LINE 2. AT l 141Z~RECEIVED A GUAR.Ip CALL. SEE GUARD CALL LINE 3. AT 17322,~OBSERVED NOTEWORTHY ACTMTY. SEEIOBS LINE 1. AT 18292,~AS CLEAR.ED OFF TASKING AND RETURNED TO BASE (RTB) JSR ASSET UTILIZATION • Supported Unit: NAVCENT • Supported Operation: OPERATIOl'i 1.4a • Precoord Time: 24 HOURS • Precoord Effectiveness: SATISFACTORY • Weather: (U) WEATHER WAS NOT A FACTOR • Intel Gap Filled?: No USCENTCOM MOR 26-0019 Approved for Release to MRO] 01/ 26/26 005
PAGE 6
Declassified by MG Richard A. Harrsor USCENTCOM Chief of Staff Deciassmed or. 22 Jtnuary 2026 • Tota] Time On Station: 20 hours 10 minutes • Ground Station CalJsign: IRANIAN AIR DEFENSE • Number of Calls Noted from the Same Agency: 1 • Guardcall Tone: DIRECTIVE • Gentext: --■ AT 0408Z,~WAS HAILED ON GU~REQ BY IRANlAN AIR DEFENSE. STANDARD ORDERS GIVEN.~RESPONDED WITH THE STANDARD RESPONSE. NO IMPACT TO MISSION • Ground Station CaUsign: IRANIAN AIR DEFENSE • Number of Calls Noted from the Same Agency: I • Gentext: AT 042 lZ,~ WAS HAILED ON GU~FREQ BY IRANIAN AIR DEFENSE. STANDARD ORDERS GIVEN.~RESPONDED STANDARD RESPONSE. NO IMPACT TO MISSION USCENTCOM MOR 26-0019 Approved for Release to MRO 01/ 26/26 006
PAGE 7
• Ground Station Callsign: IRANIAN AIR DEFENSE • Number of Calls Noted from the Same Agency: 1 • Guardcall Tone: PROFESSIONAL • Gentext: --·AT l 141Z,~WAS HAILED ON GU 243.000 FREQ BY IRANIAN AIR DEFENSE. STANDARD ORDERS GIVEN.~RESPONDE WITH STANDARD RESPONSE. NO IMPACT TO MISSION • Type of EMI: UNKNOWN • EMI Duration: 11 minutes • Aircraft Airspeed: 89 KIAS • Mission Changed: Flight Path Deviation • EMI Impact to System: Complete • Mission Impact: MEDIUM REGAINED LINK AT 12592. THIS RESULTED IN A MEDIUM IMPACT TO TIIE MISSION USCENTCOM MOR 26-0019 Approved for Release to MROI 01/ 26/26 007
PAGE 8
USCENTCOM Cl' ef of Staff • Type of EMI: UNKNO\VN • EMI Duration: 27 minutes • Aircraft Altitude: FLI 80 • Mission Changed: Flight Path Deviation • EMI Impact to System: Complete • Mission Impact: MEDIUM REGAINED 14412. THIS RESULTED IN A MEDIUM IMPACT TO THE MISSION • Aircraft Airspeed: 90 KIAS • Relative Bearing or Clock Position: - • Observed Activity Location: 39RVMsrna1.4al • Observed Activity Description: UAP • Method of Observation: FMV USCENTCOM MOR 26-0019 Approved for Release to MRO 01/ 26/26 008
PAGE 9
Declassr ied by MG Richard A. Harrsor USCENTCOM Chief of Staff Deciassmed or. 22 Jtnuary 2026 • Weather: (U) WEATiffiR WAS NOT A FACTOR USCENTCOM MOR 26-0019 Approved for Release to MRI 01/ 26/26 009
Where this file fits in the PURSUE archive
This file is one of DoD's 257 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #196 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #370 of 450.
That places it in the lower-scoring band of the archive (370 of 450 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 53/100
Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.
🤖 AI-ASSISTED SCORING · methodology
The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.
No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.
Reported by trained U.S. military personnel during an operational mission (9/16/20) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.
On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.
The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.
Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.
This file from the Department of War is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.
Bottom line on the score: the Anomalousness Index of 53/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.
Related files in DoD
Other PURSUE files in the same category, ranked by Anomalousness Index.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →