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

DOW-UAP-PR49, Unresolved UAP Report, Department of the Army, 2026

Open Sky release file MP4 Official DVIDS video page DVIDS video ID 1006111

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

DOW-UAP-PR49, Unresolved UAP Report, Department of the Army, 2026

Evidence media

The Open Sky release-file copy is the verified public MP4 for this DVIDS record: 17,266,193 bytes, SHA-256 dbf0b1a061cc741f88818ac9c938d6752fb5d1c0a3e729b1e6b42f4e859f472f. It is a compressed public release copy of an infrared-sensor video, not the original sensor export; use it for the time-coded source description and sampled-frame review below, not for object identification, range, scale, or speed claims.

Investigation reading

This page covers the DVIDS video record for 1006111, titled DOW-UAP-PR49, Unresolved UAP Report, Department of the Army, 2026. The reviewed source is a 17,266,193-byte MP4 whose SHA-256 is dbf0b1a061cc741f88818ac9c938d6752fb5d1c0a3e729b1e6b42f4e859f472f. The file is H.264 video at 1920×1080, 30 fps, about 1 minute 49.2 seconds long, with an AAC audio stream that is effectively silent in the cached release copy.

The official DVIDS page lists the asset as B-roll, Date Taken 01.01.2026, Date Posted 05.08.2026 07:50, VIRIN 260102-D-D0360-9604, filename DOD_111689168, length 00:01:49, location (UNDISCLOSED LOCATION), and unit All Domain Anomaly Resolution Office. The DVIDS description says the Department of the Army submitted a report to AARO consisting of video from an infrared sensor aboard a U.S. military platform in 2026, and that the reporter did not provide an oral or written description of the observation.

A full-video sampling pass was performed on the cached MP4 rather than relying only on the manifest prose. The review used whole-runtime key frames, denser one-second samples around 00:00-00:20, the described zoom/contrast interval around 01:04-01:08, and the final tracking interval through the end of the clip. The visible material remains low contrast and unresolved; this draft does not identify the object or resolve the case.

What the file appears to contain

The video is a dark infrared-style sensor display with a central reticle and sparse bright point-like or compact contrast features. Large black rectangular regions appear near the frame edges in later portions of the clip. These read as display masks, redactions, or interface blanking rather than scene content, and they limit what can be inspected near the edges.

The official time-coded description matches the broad structure of the video. From about 00:00-00:08, the sensor tracks an initial area of interest in a very dark field. Around 00:09-00:16, a brighter compact feature appears to the right of the reticle while the sensor pans or reframes; the feature looks like a small cluster or short bright streak in the sampled frames, not a resolved shape. From roughly 00:17-01:03, the field appears wider and darker with a stable central reticle, faint background gradients, and small unresolved points that shift subtly relative to the reticle.

Near 01:04-01:08, the video visibly cycles through contrast or zoom states. In the samples around 01:05, a small paired bright feature left of the reticle becomes more conspicuous, then fades or becomes less distinct as the display state changes again. The final interval from about 01:09-01:49 continues to show low-contrast point-like or compact features near the reticle and a persistent brighter point to the right side of the frame. None of the reviewed samples shows a clear body, wings, plume, appendages, or a stable resolved geometry.

The page therefore treats the visual evidence as released sensor video showing unresolved areas of contrast. The DVIDS wording says “two areas of contrast” during the early pan/zoom segment; the cached MP4 review supports that as a source-description phrase, but the video samples are not detailed enough to establish object identity, distance, size, or physical structure.

Source custody and provenance

The primary public source is the DVIDS page and MP4 for video ID 1006111. The Open Sky Release 01 file route serves the same release-file MP4 by slug and preserves the verified SHA-256 above. The DVIDS page’s public-domain/copyright note still says the work must comply with DVIDS restrictions, so reuse should point back to the official DVIDS page and Open Sky provenance record.

The WAR.GOV/PURSUE Release 01 graph also links this DVIDS ID to manifest-row material. One graph record identifies the PR49 video at current Release row 103; another video node carries related row numbers 106 and 107. The same manifest-derived text can also pull in FBI still-image descriptions and adjacent FBI Photo A-records. Those FBI photo references are not part of this video review and should be handled as separate image pages or provenance-cleanup leads, not folded into a conclusion about PR49.

The source itself gives a broad location as North America / undisclosed location and a 2026 date via DVIDS metadata. It does not provide the platform type, exact coordinates, altitude, range, weather, calibration data, mission report, or operator statement beyond the official description.

Graph context

The semantic graph currently has 22 extracted claims, 13 entity mentions, 2 sensor-event records, and 0 table rows attached to this asset. For this page, those counts are useful as navigation only. The most source-relevant video claims are the DVIDS identity, the 2026 date, AARO/Department of War/Department of Army custody, the one-minute-forty-nine-second infrared-sensor description, and the official timeline of tracking, panning, zooming, and contrast cycling.

The two graph sensor-event records currently surface STILL IMAGE text from the FBI-photo portion of the manifest-derived chunk. That is a provenance/extraction issue for this PR49 video page: it should not be read as two independent PR49 sensor tracks. Related graph links to PR46 and FBI Photo A3/A4 are also navigation or cleanup leads unless source custody proves a direct evidentiary relationship.

No candidate crosslinks were surfaced for this video in the asset context used for this draft.

Deep investigation — graph + web reconnaissance

Source reread and live provenance

The live DVIDS record for video 1006111 was reachable and still identifies the item as DOW-UAP-PR49, Unresolved UAP Report, Department of the Army, 2026. The page carries the same public identity already used on this wiki page: VIRIN 260102-D-D0360-9604, filename DOD_111689168, DVIDS B-roll framing, AARO/Department of the Army custody language, and the statement that no oral or written reporter description accompanied the video.

The public MP4 custody path also rechecked cleanly at the media layer. The DVIDS/CloudFront MP4 endpoint returned a byte-range response for DOD_111689168.mp4 with Content-Range: bytes 0-2047/17266193; the cached Open Sky release copy remains 17,266,193 bytes with SHA-256 dbf0b1a061cc741f88818ac9c938d6752fb5d1c0a3e729b1e6b42f4e859f472f. WAR.GOV/PURSUE landing and CSV fetches returned 403 during this check, so the authoritative public-source trail for this pass is the live DVIDS page, the ranged DVIDS MP4, and the verified Open Sky release-file copy.

A DVIDS-generated frame thumbnail for the video shows a dark infrared-style display with reticle/bracket overlays, black masked areas, and small bright unresolved features near the reticle. It does not show a resolved body, wings, plume, geometry, scale, range, or speed. That thumbnail is useful as a quick source-media sanity check, but it does not replace the full MP4 sampling summarized above.

Graph reconnaissance

The exact graph asset is official:video:war-pursue-uap-release:dvids-1006111. Direct relationships from that node currently include 22 HAS_EXTRACTED_CLAIM edges, 2 HAS_CHUNK edges, 2 DESCRIBES_SENSOR_EVENT edges, and 2 RELATED_TO edges. The semantic nodes attached by source_asset_id are 22 Claim, 13 EntityMention, and 2 SensorEvent records.

The content-level graph material is useful but needs strict separation from the source video. The strongest source-backed PR49 facts are the DVIDS identity, the AARO/Department of the Army custody statement, the infrared-sensor-video description, the 00:00-01:48 publisher timeline, and the explicit DVIDS disclaimer that the description is informational rather than an analytical judgment. The two SensorEvent rows, however, both say STILL IMAGE and quote FBI still-image language. Those rows are manifest-merge artifacts from adjacent FBI Photo A-series text, not independent PR49 sensor tracks and not evidence that this MP4 contains a still-image packet.

Exact DVIDS-ID/URL matching also surfaces graph hygiene issues: besides the PR49 video node and current Release row 103, the same DVIDS ID is present on FBI Photo A1/A3/A4 release-record nodes, and some row-record fields retain stale final_url or html_title values from neighboring PR46/PR47/FBI-photo rows. The RELATED_TO edges from the PR49 video to FBI Photo A3 and FBI Photo A4 should therefore be treated as provenance-cleanup/navigation leads only. They should not be used as corroboration, event pairing, or evidence that PR49 shares a platform, sensor, date, or observation with those still-image pages.

Prosaic checks and open limits

The public PR49 record does not provide exact time, coordinates, platform, sensor model, look angle, altitude/range, calibration metadata, mission packet, or raw sensor export. Because the location is broad/undisclosed and the date field is only coarse public metadata, weather, astronomy, launch/reentry, aircraft, drone, balloon, ground-light, and terrain checks cannot be run to a meaningful evidentiary standard from this page alone.

The first ordinary-context lanes remain sensor/display artifacts, compression, gain/contrast cycling, reticle or tracking-box behavior, distant lights/aircraft, balloons or drones, and scene/background points seen through an infrared display. None of those are confirmed by the public source; they are follow-up lanes that require the missing platform geometry, raw media, and environmental context. The page remains graph_investigation_draft / not_a_finding.

Leads to check

  • Reconcile the Release 01 row numbering for DVIDS 1006111: current row 103 versus related rows 106/107 in the video node.
  • Split or de-duplicate the manifest-derived text that blends the PR49 Department of the Army video description with FBI Photo A-series still-image descriptions.
  • Locate any uncompressed/original sensor export, mission packet, platform metadata, or chain-of-custody record behind the DVIDS MP4.
  • Determine whether the black rectangular blocks are release redactions, sensor-display masking, crop boundaries, or another overlay layer.
  • If a follow-up technical review is approved, compare adjacent frames at full resolution and evaluate whether the point-like features are tracked scene content, background lights, display artifacts, compression effects, or sensor-processing artifacts.
  • Check whether the DVIDS UAPVIDEOS tag has neighboring assets with shared production metadata that explain the reuse of DVIDS IDs or adjacent FBI photo rows.

Lead check notes

  • Checked — MP4 identity: Release metadata and the Open Sky release-file endpoint match DVIDS video ID 1006111, size 17,266,193 bytes, and SHA-256 dbf0b1a061cc741f88818ac9c938d6752fb5d1c0a3e729b1e6b42f4e859f472f.
  • Partial — row and description cleanup: Current release/graph context keeps the PR49 DVIDS video at row 103, while the video evidence node also carries related rows 106 and 107 and blended FBI Photo A-series text. That is a provenance-cleanup lead, not evidence that the PR49 video and FBI still-image pages share an event, platform, or observation.
  • Blocked — original sensor chain: The DVIDS page and Release 01 record do not provide the original sensor export, mission packet, platform track, field-of-view/stabilization data, range/range-rate, calibration metadata, or operator statement.
  • Partial — visual-feature review: The public MP4 supports the broad official time-coded description and shows low-contrast point-like/compact features, but the compressed video is not enough to determine object identity, size, distance, speed, or whether specific points are scene content versus display/compression/sensor-processing artifacts.
  • Partial — black rectangular blocks: The blocks are visible in the release video, but the public source does not identify them as redaction, interface masking, crop boundaries, or another overlay layer. Producer metadata or a less-processed source export is needed.
  • Needs external source — ordinary-context checks: Aircraft, drone, balloon, celestial, weather, terrain/ground-light, or sensor-artifact checks need exact time, coordinates, platform geometry, line of sight, and unredacted collection context that are not in the public DVIDS record.

Limits

The released file is a compressed public MP4, not a raw sensor recording. It has no transcript, no oral or written observer narrative beyond the official DVIDS description, and no mission report attached to the video page. The visible features remain small, bright, and unresolved against a dark low-contrast field. Sampling frames can confirm broad visual structure and source-timeline alignment, but it cannot establish speed, range, size, altitude, or identity.

This page is an investigation draft for source readability and graph hygiene. It is not a finding, not an identification, and not an analytical resolution of the event.

Sources