← Back to Files & Wiki
Wiki page · asset · graph_investigation_draft

DOW-UAP-PR21, Unresolved UAP Report, Iraq, May 2022

Official DVIDS page: https://www.dvidshub.net/video/1006059/dow uap pr21 unresolved uap report iraq may 2022 Open Sky release file copy: war gov dow uap pr21 unresolved uap report iraq may 2022 1006059 DVIDS MP4 source URL: https://d34w7g4gy10iej.cloudfront.net/video/2605/DOD 11…

Release 01#war-gov#pursue#release-01#official-source#evidence#video#dvids

DOW-UAP-PR21, Unresolved UAP Report, Iraq, May 2022

Evidence media

<video controls preload="metadata" src="/api/explore/war-gov/release-file/war-gov-dow-uap-pr21-unresolved-uap-report-iraq-may-2022-1006059" style="max-width: 100%; border-radius: 8px;"></video>

Playable Open Sky release-file copy of the official DVIDS MP4 for 1006059. The clip is about 10.27 seconds at 1920 × 1080, H.264, 30 fps; it shows a redacted grayscale sensor-display view with small unresolved contrast features near the center. The video itself does not identify those features or provide scale, range, platform geometry, or unredacted telemetry.

Investigation reading

This Release 01 item is the paired DVIDS video for DOW-UAP-D14, Mission Report, Iraq, May 2022. The Open Sky release-file copy verifies as 12,752,210 bytes with SHA-256 af62b4e40a2eb0fd39f98093be2a6ae50271a011e7d5caca2119b26aaabc1212. The video stream is 308 frames over about 10.27 seconds. An AAC audio track is present in the MP4 container, but the decoded samples are silent, so this page treats the released evidence as visual video plus publisher metadata rather than as a narrated clip or transcript.

The official release description says the United States Central Command submitted ten seconds of infrared-sensor footage from a U.S. military platform in 2022, and that the clip shows two areas of contrast moving together near the center of the field of view. It also links the clip to the D14 mission report and includes AARO's note that SU-27 and SU-35 are Russian Federation military-aircraft designations. That publisher description is important context, but it is not itself a resolution of what is visible in the clip.

A full visual pass of sampled frames and central crops shows a monochrome sensor-style scene over a mottled terrain-like background. The display includes fixed cyan symbology: a segmented central reticle, four bracket-like corner marks, and an N compass marker. Several opaque black blocks mask display areas around the top, left edge, lower center, and lower right. Those blocks are release/editor redactions or display overlays, not visible scene objects.

Within the central field, very small bright and dark contrast features appear near and around the reticle. They are pixel-scale to short-dash features, sometimes visible for adjacent frames, and they drift relative to the fixed reticle with the background texture. The clip therefore supports a cautious visible reading: unresolved contrast features are present in a redacted sensor-display view, but the released MP4 alone does not provide enough scale, range, platform geometry, or unredacted telemetry to identify them.

What the file appears to contain

  • A short official DVIDS MP4, not a PDF packet and not an independent analytic report.
  • A grayscale/infrared-looking sensor view over terrain or ground texture, with no horizon and no clear geographic reference visible in the released frames.
  • Fixed sensor/display symbology: central cyan reticle, cyan corner brackets, and an N marker.
  • Multiple black masked regions over display areas, including top readouts and a prominent lower-right block.
  • Small unresolved contrast features near the central field. The official description calls out two areas of contrast moving together near the center; direct frame review can describe only tiny unresolved bright/dark features and their apparent motion within the released display.
  • No visible caption track, no spoken narration in the decoded audio, no map overlay, no range scale, no unredacted coordinates, and no raw telemetry in the public video.

Source custody and provenance

Graph context

The graph has an exact VideoEvidence record for DVIDS 1006059 and a release-record Document for DOW-UAP-PR21. Related records include the paired DOW-UAP-D14, Mission Report, Iraq, May 2022 PDF and nearby Release 01 video/document records. No candidate crosslinks are currently listed for this video item.

The semantic graph currently preserves 24 source-text claim records, 12 entity mentions, 1 sensor-event record, and 0 table rows for PR21. These are navigation aids, not findings. The single sensor-event extraction is driven by publisher text around aircraft terminology in the AARO comment, not by a released radar plot, independent track file, or unredacted sensor log.

The paired D14 PDF is essential context but should not be collapsed into this video without human review. The D14 page separates the 300117:00ZMAY22 UAP line, which says the object was followed north to northeast until the screener could not get a positive identification, from the 300011:00ZMAY22 observation line describing one probable SU-27/35 observed landing by FMV. PR21's publisher description needs to be reconciled against that separation before any case-level narrative is promoted.

Leads to check

  • Compare the PR21 frames directly against D14 page 8's 0117Z UAP line and page 9's 0011Z probable SU-27/35 line. The current public materials create a timing/description tension that should remain open.
  • Obtain or locate the original full sensor file, unredacted display readouts, platform geometry, timecode, coordinates, range/altitude context, and any collection notes behind the edited DVIDS release.
  • Determine whether the two contrast areas named in the official description correspond to the small central features visible in the released frames, a masked/obscured display element, or a more obvious feature in the full-resolution source before compression/redaction.
  • Reconcile the Iraq video title, Iraq/Syria release metadata, and D14 mission-report context before using this asset as a location-specific case anchor.
  • If this becomes a case investigation, run ordinary aircraft, mission-context, weather, and sensor-artifact checks from the exact unredacted time/location rather than from the public video title alone.

Lead check notes

  • Checked — D14 source separation: the paired D14 page keeps the 300117:00ZMAY22 UAP line separate from the 300011:00ZMAY22 probable SU-27/35 observation line. PR21 should remain a video evidence page, not a shortcut resolution of the D14 PDF.
  • Partial — clip-to-report mapping: release metadata pairs PR21 with D14 and describes ten seconds of infrared-sensor footage, but the public MP4 has no in-frame timestamp, coordinates, range, platform geometry, or unredacted telemetry. Exact mapping to the D14 0117Z UAP line versus the separate 0011Z SU-27/35 line still requires source export metadata or an authoritative AARO/WAR.GOV update.
  • Partial — two contrast areas: the verified 12,752,210-byte MP4 supports a cautious visual reading of small unresolved central contrast features in a redacted sensor-display view. The public file is not enough to determine whether those are the same two contrast areas named in the official description or how they appeared in the uncompressed source.
  • Partial — title/location metadata: DVIDS titles the clip as Iraq, release metadata lists Iraq, Syria, and the paired D14 release record uses Syria/eastern-Mediterranean mission context. Keep this as release-metadata tension until manifest history or source records clarify the location label.
  • Blocked — source FMV and sensor context: the current public record exposes the compressed DVIDS MP4 only. It does not include the original full sensor file, adjacent frames, unredacted display readouts, exact timecode, coordinates, range/altitude context, platform position, sensor mode, or collection notes.
  • Needs external source — ordinary checks: aircraft, mission-context, weather, atmospheric, bird, ground-scene/parallax, compression, and sensor-artifact checks need exact unredacted time/location/geometry and external operational or environmental sources. The public video title alone is insufficient for those checks.

Deep investigation — graph + web reconnaissance

Source reread

This page is the PR21 video evidence record, not the full mission-report packet. The verified Open Sky copy is the DVIDS MP4 for video ID 1006059: 12,752,210 bytes, SHA-256 af62b4e40a2eb0fd39f98093be2a6ae50271a011e7d5caca2119b26aaabc1212, about 10.27 seconds, 1920×1080, H.264 at 30 fps, with a silent AAC track. The official DVIDS page titles it DOW-UAP-PR21, Unresolved UAP Report, Iraq, May 2022; live metadata lists VIRIN 220501-D-D0360-5022, filename DOD_111688762, category B-Roll, length 00:00:10, location (UNDISCLOSED LOCATION), date taken 05.01.2022, and date posted 05.07.2026 19:48.

The official description says the United States Central Command submitted ten seconds of infrared-sensor footage from a U.S. military platform, that the accompanying DOW-UAP-D14 mission report described the UAP as a probable SU-27/35, and that the video shows two areas of contrast moving together near the center of the field of view. That publisher wording is useful, but it creates a source-mapping tension: the D14 PDF page 8 carries the 300117:00ZMAY22 UAP line, while page 9 separately carries 300011:00ZMAY22 / ONE PROBABLE SU-27/35 OBSERVED LANDING with method of observation FMV.

A representative DVIDS thumbnail and the release-file visual review support only a cautious visible reading. The public frame shows a grayscale sensor-display scene with cyan reticle/bracket symbology, an N marker, black masked/redacted display regions, mottled background texture, and small unresolved contrast features near the central field. It does not expose readable range, scale, coordinates, timestamp, platform geometry, sensor settings, or unredacted telemetry. The released MP4 alone therefore does not prove whether the visible contrast features map to D14's 0117Z UAP line, the separate 0011Z SU-27/35 line, or a clipped excerpt from a larger FMV product.

Graph connections

Read-only graph review found the exact PR21 VideoEvidence node, the PR21 Release 01 row-record Document, and the related D14 PDF/row-record trail. The PR21 video node is linked to two manifest-description TextChunk records, 24 machine-extracted Claim records, 12 EntityMention records, and 1 SensorEvent record. The single PR21 sensor event is an unreviewed aircraft cue extracted from the AARO comment that SU-27 and SU-35 are Russian military-aircraft designations; it is not a released radar plot, telemetry track, or independent sensor return.

The graph also preserves the D14 context: the exact D14 PDF asset has the official WAR.GOV media URL, 7,463,660 bytes, SHA-256 1822564fbae08f152ad4541c8d067a6ec3b6014c4b4eb8209604e1facb5e1bb3, 9 OCR pages, 156 machine-extracted claims, 111 entity mentions, 13 sensor-event records, and direct chunks that contain the page-8 0117Z UAP line plus the page-9 0011Z SU-27/35 line. Those D14 sensor events remain machine-review navigation aids because several come from form prompts, FMV/source wording, or equipment context rather than from raw released instrument data.

No direct CANDIDATE_CROSSLINK records were returned for PR21 or D14 in this check. The graph does show row/current-manifest drift: PR21 page/inventory metadata points to rows 37 and 81, while the current PR21 row-record surfaced as row 78 and a nearby row 81 relationship points at PR26. Keep that as provenance cleanup, not case-level corroboration.

External provenance and context

The official DVIDS page was reachable and redirects the short /video/1006059 URL to the PR21 title slug. Its MP4 endpoint responded as binary/octet-stream with Content-Length: 12752210, Accept-Ranges: bytes, and Last-Modified: Fri, 08 May 2026 11:45:13 GMT, matching the verified Open Sky copy by size/hash. Internet Archive CDX also lists exact DVIDS page captures on 20260508200920, 20260508222320, and 20260517135425, which is useful custody corroboration for the public DVIDS page.

Live WAR.GOV probes for the Release 01 landing page, the official CSV, and the D14 PDF returned 403 during this check. That is an access/custody limitation, not a contradiction of the verified source copy: the Open Sky release-file copy, asset inventory, graph metadata, and D14 page renders all point back to the canonical WAR.GOV PDF URL for the paired mission report.

The DVIDS date-taken/VIRIN metadata (05.01.2022 / 220501) does not line up cleanly with the D14 mission timeline (29/30MAY22) or the release-record incident date (5/29/22). Treat that as a custody/date-cleanup lead until DVIDS, WAR.GOV, AARO, or the source export explains whether it is a production date, placeholder, upload metadata, or a true source-timeline clue.

Prosaic checks and limits

The first prosaic lane is already inside the source family: D14 documents conventional military-aircraft context in the same mission window, including a 2147Z possible SU-30 reaction and a separate 0011Z probable SU-27/35 landing observation. The UAP form itself says UAP Signatures: No and leaves RF frequency/duration blank. PR21 adds a sensor-media artifact lane: a short compressed public clip with display symbology, black masking, tiny contrast features, and no public range/scale/timecode/geometry.

Exact-date graph checks returned no modeled LaunchEvent, AstronomyEvent, or WeatherEvent rows for 2022-05-29 or 2022-05-30, and this graph has no populated Satellite label to query. Those are graph-coverage facts, not exclusions. Meaningful weather, aircraft, satellite/reentry, bird, ground-scene/parallax, and sensor-artifact checks require the unredacted location, platform track, look angle, range, frame timestamps, sensor mode, and source FMV or collection notes.

Follow-up leads

  • Obtain an authoritative mapping note or source export tying PR21 to D14 page 8's 0117Z UAP line, D14 page 9's 0011Z SU-27/35 landing line, or another redacted source line.
  • Seek the original or less-redacted FMV with readable timecode, coordinates, range/scale, sensor mode, platform geometry, and adjacent frames.
  • Reconcile DVIDS 05.01.2022 / VIRIN 220501 metadata against the D14 29/30MAY22 mission timeline and Release 01 row metadata.
  • Keep the PR21 row-number/PR26 linkage wrinkle in the graph data-quality backlog; do not use it as evidence that the cases are connected.

Audit note

This section is based on the PR21 source page/media metadata, the paired D14 PDF OCR and rendered pages, representative DVIDS thumbnail review, read-only Neo4j queries, and official/archive web checks. No Neo4j writes were made, and no Finding, Hypothesis, or ResolutionDecision conclusion is asserted here.

Limits

This page is a source reading and remains needs_human_review / not_a_finding. The released MP4 is short, redacted, and heavily dependent on display context that is not public in the clip. It does not provide a verified object size, distance, altitude, velocity, coordinates, platform type, sensor settings, or an independent track history.

The visible description above is limited to the public file: a sensor-style scene, fixed overlays/masking, and small unresolved contrast features. It should not be used to assert identification, non-identification, performance, intent, or origin. The D14 mission report and PR21 video are related evidence records, but their exact event mapping still needs source-level reconciliation.

Sources