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

DOW-UAP-PR19, Unresolved UAP Report, Middle East, May 2022

Official DVIDS page: https://www.dvidshub.net/video/1006056/dow uap pr19 unresolved uap report middle east may 2022 Open Sky release file copy: war gov dow uap pr19 unresolved uap report middle east may 2022 1006056 DVIDS MP4 source URL: https://d34w7g4gy10iej.cloudfront.net/vid…

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

DOW-UAP-PR19, Unresolved UAP Report, Middle East, May 2022

Evidence media

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

Playable Open Sky release-file copy of the official DVIDS MP4. The clip is about 5.4 seconds at 1920 x 1080; it shows a grayscale sensor-style view with fixed overlays and a small unresolved contrast feature moving across the lower portion of the frame. The video itself does not provide scale, range, platform geometry, or an identification.

Investigation reading

This Release 01 item is the public DVIDS video paired to DoW-UAP-D10, Mission Report, Middle East, May 2022. It is a short MP4, not the full mission report and not an adjudication. The reviewed source package preserves a verified 6,814,452-byte MP4 with SHA-256 a38432ae56298abadf50de06103a6fbd591ea539e124ab1db25a4a511468cfb6; DVIDS lists the public clip as 5 seconds long, B-roll, filename DOD_111688723, video ID 1006056, VIRIN 220501-D-D0360-6497, location (UNDISCLOSED LOCATION), date taken 05.01.2022, and date posted 05.07.2026 23:17.

A frame-sampling pass over the verified MP4 shows a grayscale sensor-style display with fixed overlays and one small moving contrast feature in the lower portion of the image during the later part of the clip. The DVIDS description says that, at about the two-second mark, the video depicts an area of contrast moving left to right across the bottom third of the sensor field of view. The visible video supports that narrow description, but it does not provide enough public information to identify the feature, estimate distance or speed, or decide whether it is airborne, ground-related, sensor-related, or something else.

The paired mission report is important context but must stay separate from the clip. D10 is the text MISREP; PR19 is the released five-second video. This page is a graph_investigation_draft; it remains needs_human_review and not_a_finding.

What the file appears to contain

The MP4 is an H.264 video stream at 1920 x 1080, 30 fps, with a duration of about 5.4 seconds and an AAC audio stream. No public transcript or caption track was found in the DVIDS page metadata checked for this item. The video itself is monochrome/grayscale and appears to be a sensor-display recording. It shows a mottled low-contrast background, a central crosshair-like marker, an N orientation marker, fixed black mask/overlay blocks along the top and edges, and a large dark block in the lower-right corner.

Across sampled frames from roughly 1.5s to 3.0s, a small high-contrast area becomes clearer in the lower portion of the frame. It appears near the lower central/left area around the middle of that interval and then moves generally toward the lower-right edge by about 3.0s. The feature is small and poorly resolved in the public MP4; the surrounding scene is compressed, grainy, and partially obscured by display overlays. The source video provides no scale bar, range, platform position, sensor mode, exact look angle, or object label in the imagery itself.

The companion D10 report gives the strongest text context. Rendered-page and OCR review of the six-page PDF show typed MISREP-style pages only, with no embedded photographs, maps, radar plots, raw sensor frames, or video stills. Page 6 records Observation DTG 061514:00ZMAY22, observed activity description 1X UAP, method of observation FMV, and a GENTEXT/OBSERVATION passage stating that from 1514Z to 1934Z a redacted observer saw 5X UAP FLY ACROSS THE SCREEN. The same passage says the 1514Z observation involved a UAP with wording around a possible redacted MISSILE moving across the field of view, and that the four remaining UAP fit closer to the profile of possible birds. Page 6 also states that dust hindered most FMV collection of the ground.

Those D10 statements are source-language leads, not Open Sky conclusions. The public PR19 video appears to be the short released clip associated with the report; it does not show the full 1514Z to 1934Z observation span or the four other reported objects.

Source custody and provenance

The release records carry a provenance cleanup lead. The selected video inventory ties this item to CSV rows 35 and 79, while the graph release-record node for PR19 surfaces row 76 and the paired D10 record is row 35. Treat that as row-number/source-manifest tension until the release CSV history is reconciled. There is also a date tension between the DVIDS Date Taken: 05.01.2022 metadata and the paired D10 observation date of 06MAY22.

Graph context

Open Sky currently models PR19 as a VideoEvidence node and a related Release 01 record document. The exact graph records preserve the DVIDS URL, DVIDS video ID 1006056, official-primary provenance, related rows, and incident-location strings Iraq / Middle East. The graph links this video to the D10 PDF asset/record and to nearby Release 01 records, including PR22 and D74, but those related rows are navigation/context until a human source comparison proves an evidentiary connection.

The semantic graph has 27 extracted claim records, 12 entity mentions, 0 sensor-event records, and 10 candidate crosslinks for PR19. The useful source-backed claims are narrow: D10 is the companion report; the video is five seconds of infrared-sensor footage; the D10 narrative describes one possible missile-like observation and four other possible-bird observations; the public video description says a small contrast area moves left to right across the bottom third. Candidate crosslinks are review leads, not findings.

The companion D10 page has richer graph context: 114 extracted claims, 75 entity mentions, and 9 sensor-event records. Those sensor-event records should be read carefully because many come from MISREP form fields and equipment prompts. The strongest source-backed sensor context for the PR19/D10 pair is simply FMV / full-motion-video exploitation by DGS1; the public record does not release raw telemetry, platform geometry, or independent radar/IR plots.

Leads to check

  • Confirm the exact mapping between the five-second PR19 clip and the D10 page-6 1514Z observation. The report says there were five observed UAP over a longer interval; the public PR19 video appears to depict only one short clip.
  • Reconcile release-row and date metadata: rows 35/79 versus graph row 76, and DVIDS 05.01.2022 versus D10 06MAY22.
  • Human-transcribe D10 page 6 around the phrase rendered as VISRECCE / OCR-normalized as presence, the possible redacted MISSILE phrase, the redacted MGRS-like location fragments, and the observation DTG 061514:00ZMAY22 versus OCR variants.
  • Look for the uncompressed or longer source FMV segment, adjacent frames, platform/sensor metadata, field of view, sensor mode, platform position, altitude, range, and exact timestamp.
  • Run ordinary explanation checks before escalation: birds, missile/munition activity, aircraft, ground/scene parallax, sensor-display artifacts, compression, atmospheric/dust effects, and line-of-sight ambiguity.
  • Compare the PR19 DVIDS clip with the paired D10 PDF and any future AARO/WAR.GOV updates without merging the PDF context into a video conclusion.

Lead check notes

  • Checked — PR19/D10 source separation: PR19 is the five-second DVIDS MP4; D10 is the six-page mission-report PDF. The PR19 page and paired D10 page keep the clip, PDF text, and graph context separate, so D10 wording should not be treated as a video conclusion.
  • Partial — clip-to-observation mapping: the release description and D10 page 6 both point to an FMV observation associated with a moving contrast feature / possible redacted MISSILE wording, but the public PR19 MP4 is only a short excerpt and does not expose an in-frame timestamp, range, platform geometry, or the full 1514Z-to-1934Z observation span. Exact mapping still needs the source FMV export, clip-export metadata, or an authoritative AARO/WAR.GOV update.
  • Partial — release-row and date metadata: release metadata for the video preserves rows 35/79, while the graph release record surfaces row 76; DVIDS lists date taken 05.01.2022, while the paired D10 observation text is dated 06MAY22. Treat this as source-manifest/date-custody cleanup until release history or DVIDS/WAR.GOV metadata clarifies it.
  • Partial — D10 page-6 transcription: the paired D10 page review supports 061514:00ZMAY22 and visually favors VISRECCE OF A POSSIBLE [redacted] MISSILE; redactions and OCR variants still require human source-image transcription before quoting the line as final.
  • Blocked — source FMV and sensor context: the current public record exposes a compressed 6,814,452-byte MP4 only. It does not include the uncompressed or longer FMV segment, adjacent frames, exact timestamp overlay, sensor mode, field of view, platform position, altitude, range, line of sight, or raw telemetry.
  • Needs external source — ordinary checks: bird, missile/munition, aircraft, ground-scene/parallax, sensor-display artifact, compression, dust/atmospheric, and line-of-sight explanations require unredacted coordinates/time, platform geometry, weather/traffic/activity context, and fuller source video. The D10 possible missile and possible birds phrases remain source-language leads, not Open Sky findings.

Deep investigation — graph + web reconnaissance

Source and media reread

The official DVIDS page remains the best public source for the video record. It is live at https://www.dvidshub.net/video/1006056/dow-uap-pr19-unresolved-uap-report-middle-east-may-2022 and lists video ID 1006056, VIRIN 220501-D-D0360-6497, filename DOD_111688723, category B-Roll, length 00:00:05, location (UNDISCLOSED LOCATION), date taken 05.01.2022, date posted 05.07.2026 23:17, and courtesy video credited to AARO.

A source-file check reverified the cached official DVIDS MP4 as 6,814,452 bytes with SHA-256 a38432ae56298abadf50de06103a6fbd591ea539e124ab1db25a4a511468cfb6. MP4 container parsing confirms an M4V/ftyp file with a 5.4-second movie duration, one avc1 video track at 1920 x 1080 with 162 samples over 5.4 seconds (30 fps), and one mp4a audio track. DVIDS thumbnail frames show a monochrome sensor-style view with a central reticle/brackets, an N orientation marker, black mask/overlay blocks, heavy compression/noise, and a tiny bright or contrast feature; the still frames alone do not establish scale, range, speed, platform geometry, or identification.

The paired D10 mission report remains context, not a video conclusion. A page-6 source-image reread supports Observation DTG 061514:00ZMAY22, method of observation FMV, and a GENTEXT/OBSERVATION passage saying that from 1514Z to 1934Z a redacted observer saw 5X UAP FLY ACROSS THE SCREEN. The same page describes the first 1514Z object with OCR-sensitive VISRECCE/similar wording around a possible redacted MISSILE, then says the four remaining UAP fit closer to the profile of possible birds. The page also repeats that dust hindered most FMV collection of the ground. Those phrases are source/operator language and should not be promoted into Open Sky findings.

Graph connections

Read-only Neo4j review finds the PR19 item as an exact VideoEvidence asset with DVIDS ID 1006056, the DVIDS page URL, MP4 URL, full-download SHA-256 above, 6,814,452 MP4 bytes, related CSV rows 35 and 79, and official-primary provenance. The same title also appears as a current Release 01 row-record document for row 76. The useful graph trail is therefore PR19 video asset -> row-record metadata -> paired D10 PDF asset/row record -> source-text claims.

The semantic graph for the PR19 VideoEvidence asset contains 27 machine-extracted Claim nodes and 12 EntityMention nodes, with no SensorEvent nodes under the video asset's source_asset_id. Direct relationship counts from the video asset show the manifest-description text chunks, extracted claims, one official Release 01 Source, and RELATED_TO links to the D10 PDF asset/record. A direct source_asset_id check did not return public-useful CANDIDATE_CROSSLINK edges; any older candidate-crosslink count attached to this page should be treated as a review-summary/data-hygiene lead until reconciled.

The graph also preserves a metadata-cleanup issue: the PR19 video asset carries related rows 35 and 79, while the PR19 row-record is row 76; nearby relationships can surface D10, PR22, or D74 row/final-URL drift. These are custody and manifest-hygiene leads, not corroboration and not evidence that unrelated release rows describe the same event.

External provenance and official-source checks

The DVIDS page and DVIDS MP4 endpoint were reachable during this check. The MP4 endpoint returned a valid byte-range response, 206 with Content-Range: bytes 0-15/6814452, and the returned bytes begin with the expected ftyp MP4 box. Direct WAR.GOV/PURSUE probes for the paired D10 PDF, release CSV, and landing page returned 403 from this environment, so the public page relies on the verified cached official-primary release file plus the DVIDS official page. Internet Archive availability probes for the exact DVIDS page, MP4 URL, and WAR.GOV PDF returned 429 Too Many Requests during this check and were not used as custody substitutes.

The DVIDS metadata date (05.01.2022) remains in tension with the D10 source-page observation date (06MAY22). Until WAR.GOV, DVIDS, or AARO publishes a reconciliation note, preserve that as a date-custody issue rather than changing the event chronology.

Prosaic checks and limits

The first ordinary-explanation lanes are source-internal: possible missile/munition activity for the first observation, possible birds for the four later observations, and dust/weather limits on FMV collection. The video itself adds ordinary media-analysis lanes: single compressed five-second excerpt, display overlays, black masks, low contrast, possible sensor/display artifacts, compression, scene/parallax ambiguity, and lack of raw frame metadata.

A bounded graph date-context probe for the public D10 observation date found one modeled LaunchEvent on 2022-05-06 (Starlink 4-17, Kennedy Space Center, 09:42Z) and no same-date AstronomyEvent or WeatherEvent rows; the graph exposes a Satellite label, but that label currently has zero nodes. That is graph-coverage context only. Because the public record redacts exact coordinates, platform track, look direction, range, altitude, and sensor mode, it does not support a responsible launch/satellite/astronomy/weather correlation or exclusion.

Follow-up leads

  • Obtain an authoritative source FMV export or release note that maps the five-second PR19 clip to the D10 1514Z observation and separates it from the four later possible-bird observations.
  • Reconcile DVIDS 05.01.2022 metadata with D10 06MAY22 source text and the row 35/76/79 graph metadata drift.
  • Seek unredacted or less-redacted platform/sensor context: exact grid, aircraft position, altitude, range, look angle, field of view, sensor mode, frame timestamp, and weather/visibility data.
  • Treat D10 page-6 wording (VISRECCE/similar, possible redacted missile phrase, and redacted MGRS fragments) as a human-transcription lead before final quotation.

Audit note

This section is based on the current wiki page, paired D10 source page/render, DVIDS official page/media, read-only graph review, and official-source web probes. No Neo4j writes were made, and no Finding, Hypothesis, or ResolutionDecision conclusion is asserted.

Limits

The public file is a compressed five-second MP4. It has no released raw sensor export, no range or scale, no unredacted coordinates, no platform identity, no sensor-mode details beyond the release description, no public transcript, and no full observation sequence. The visible moving contrast feature is small and unresolved.

The companion D10 report is heavily redacted and source-language tentative. Phrases like possible missile and possible birds belong to the reporting chain, not to Open Sky analysis. This page therefore preserves provenance, visual reading, and graph context only; it does not identify the feature, make a finding, or resolve the event.

Sources