War.gov PURSUEDepartment of War
GovernmentMay 29, 2022Analysis complete

DOW-UAP-D014, Mission Report, Iraq, May 2022

The released record says a U.S. military operator reported observing one UAP flying north to northeast. File: DOW-UAP-D014, Mission Report, Iraq, May 2022. DOW-UAP-D014, Mission Report, Iraq, May 2022 combines an official, downloadable document, 5 extracted claims, 4 evidence records, and 4 timeline entries across 9 source pages, and file-level provenance that can be compared with related release records.

File
Document · Release 01
Date
May 29, 2022
Location
Syria
Extent
9 pages

Probed Assessment

The released record says a U.S. military operator reported observing one UAP flying north to northeast. File: DOW-UAP-D014, Mission Report, Iraq, May 2022.

Key takeaways

  • The observer reported following the UAP for as long as possible but was unable to positively identify it
  • The released record says weather was not a factor during the mission.
  • The released record says (S/ /REL) AT 001 lZ, ~ OBSERVED ONE PROBABLE SU-27 /35 LANDING IVO 36SYE681ual2~ WEATHER.

Why it matters

DOW-UAP-D014, Mission Report, Iraq, May 2022 combines an official, downloadable document, 5 extracted claims, 4 evidence records, and 4 timeline entries across 9 source pages, and file-level provenance that can be compared with related release records.

Corroboration

For DOW-UAP-D014, Mission Report, Iraq, May 2022, the release establishes official provenance but does not independently verify the record's statement that a U.S. military operator reported observing one UAP flying north to northeast.

Open questions

  • Which companion records, if any, independently corroborate the source claims extracted from this 9-page document?

Probed separates this editorial assessment from the source claims below. It summarizes what the released artifact supports; it is not independent verification.

Official Description from War.gov

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 flying north to northeast. The observer reported following the UAP for as long as possible but was unable to positively identify it. 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.

Preserved verbatim as source metadata. This wording is separate from Probed’s file-specific description and assessment.

File Context

Related entities

6
Research Map relationships require row-level claim or timeline references.

Tracker findings

1

Mission report separately recorded a probable SU-27/35 landing

The aircraft entry is separate from the report’s possible-small-UAP observation and should not be read as an identification of that UAP.

Release provenance

Release
Release 01
Official ID
release-01-file-041-dow-uap-d014-mission-report-iraq-may-2022
Cleared
May 8, 2026
Official release source

Referenced Timeline

  1. Page 4

    Takeoff from Sigonella Airbase

  2. Page 9

    Observation of SU-27/35 Landing

    Observed one probable SU-27/35 landing.

  3. Page 8

    UAP Initial Contact

    Observed a UAP flying north to northeast.

  4. Page 4

    Landing at LRCT

Source Claims

Claims are attributed to the released source and remain distinct from Probed’s assessment and tracker findings.

Source reportedAssertedPage 8

A U.S. military operator reported observing one UAP flying north to northeast.

1.4a I 1.4a !OBSERVED A UAP AT 0117Z FLY NORTH

Source reportedAssertedPage 8

The observer reported following the UAP for as long as possible but was unable to positively identify it.

AS LONG AS POSSIBLE.~SCREENER COULD NOT GET A POSITIVE ID ON THE UAP.

Source reportedObservedPage 8

Weather was not a factor during the mission.

MISSION AS PLANNED.~DID NOT VISUALLY ACQUIRE THE REPORTED ACFT. WEATHER • Weather: (U) WEATHER WAS NOT A FACTOR.

Source reportedAssertedPage 9

(S/ /REL) AT 001 lZ, ~ OBSERVED ONE PROBABLE SU-27 /35 LANDING IVO 36SYE681ual2~ WEATHER.

Gentext: (S/ /REL) AT 001 lZ, ~ OBSERVED ONE PROBABLE SU-27 /35 LANDING IVO 36SYE681ual2~ WEATHER

Source reportedAssertedPage 6

AT 2104Z,~ OBSERVED A GENERATOR OR POSS RADAR DISH IVO 36SYE6~~.

AT 2104Z,~ OBSERVED A GENERATOR OR POSS RADAR DISH IVO 36SYE6~~

Source reportedAssertedPage 1

The report separately recorded one probable SU-27/35 landing at Al Assad Airfield.

1.4a !OBSERVED ONE PROBABLE SU-27/35 LANDING IYO AL ASSAD

Source Material & Evidence

document

Mission Report DOW-UAP-D14

RELEASE-01-FILE-037-DOW-UAP-D14-MISSION-REPORT-IRAQ-MAY-2022

data

ISR Line 1

data

UAP Line 1

data

OBS Line 1

Research Map

6 entities · 0 grounded links

Lines appear only when two entities share a row-level source claim or dated timeline event. Unconnected nodes remain visible without implying a relationship.

UAP/Disclosure Graph
6 nodes0 links
No grounded pairwise links in this file