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

DOW-UAP-PR48, Unresolved UAP Report, INDOPACOM, 2024

Open Sky release file MP4 Official DVIDS source page

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

DOW-UAP-PR48, Unresolved UAP Report, INDOPACOM, 2024

Evidence media

The Open Sky release-file copy is the public DVIDS MP4 for Video ID 1006110: a 116,761,162 byte H.264 video at 1920×1080, 30 fps, with SHA-256 bd1f002f45052b12ee067455a0a4b589b0bdaed40d75874d8da8fbf64eae8dd1. Treat this as the public release copy of infrared-sensor footage, not the original sensor export; the source metadata does not include reporter narration, coordinates, platform track, range data, or calibration details.

Investigation reading

This draft treats PR48 as a public DVIDS video release, not as a resolved case file. The verified Release 01 MP4 copy is 116,761,162 bytes with SHA-256 bd1f002f45052b12ee067455a0a4b589b0bdaed40d75874d8da8fbf64eae8dd1. The public file is a 1 minute 39.366 second H.264 video at 1920×1080 and 30 fps. It also carries an AAC stereo audio stream, but the decoded public audio is silent; there is no released narration or witness audio.

The DVIDS page describes the source as one minute and 39 seconds of infrared-sensor footage from a U.S. military platform submitted by U.S. Indo-Pacific Command to AARO. It also states that the reporter did not provide an oral or written description. The official video description is narrow: from 00:00 to 01:39, the sensor tracks an area of contrast while keeping it generally near the center of the frame. The same DVIDS text explicitly warns that this description is informational only and should not be read as an analytical judgment, investigative conclusion, or factual determination.

A full-runtime frame read-through shows a grayscale sensor-style scene with fixed magenta display symbology, a central reticle, several black redaction or masking blocks, and a moving background. From roughly the middle of the clip onward, multiple tall three-bladed tower-like structures pass through the field of view. A small unresolved contrast feature is visible near the reticle/center region in repeated samples, but it remains point-like or speck-like in the public MP4. Its apparent visibility changes with background tone, compression, scene clutter, and the fixed display overlay. The public copy does not resolve the feature's shape, range, scale, altitude, independent motion, or cause.

What the file appears to contain

The released file appears to contain a stabilized or tracked infrared-style public video clip. The central display reticle and magenta N/marker symbology are display overlays, not scene objects. The black blocks at the top, sides, and lower-right are release redactions or masking, not physical objects in the scene. The underlying scene shows broad gray terrain or surface texture, changing tonal gradients, and the three-bladed tower-like structures entering and leaving the frame.

The object-relevant content is limited to the official phrase area of contrast and to the small unresolved contrast feature seen near the reticle in the public copy. That feature should be described only as an unresolved contrast feature in released sensor imagery. The MP4 does not provide a mission report, sensor export, platform track, range/range-rate data, coordinates, calibration details, unredacted frame corners, or a witness narrative.

Source custody and provenance

The primary public source is the DVIDS page for Video ID 1006110, canonical title DOW-UAP-PR48, Unresolved UAP Report, INDOPACOM, 2024. DVIDS metadata lists Date Taken 01.01.2024, Date Posted 05.08.2026 07:50, category B-Roll, VIRIN 240102-D-D0360-9234, filename DOD_111689167, length 00:01:39, and location (UNDISCLOSED LOCATION). Release metadata summarizes the incident location as Indo-PACOM and the incident date as N/A, so the DVIDS date/VIRIN should be treated as source metadata until reconciled with the release row.

Open Sky's release-file route for the public MP4 is:

The release inventory associates this MP4 with SHA-256 bd1f002f45052b12ee067455a0a4b589b0bdaed40d75874d8da8fbf64eae8dd1. The graph also carries a current-row release-record anchor for PR48 and a nearby row-level collision where FBI Photo A2 has inherited the same DVIDS ID. That is a provenance-cleanup lead, not evidence that the still-photo record and this video describe the same observation.

Graph context

The graph has a VideoEvidence record for DVIDS 1006110 and a WAR.GOV/PURSUE release-record document for the PR48 title. The semantic layer currently shows 10 extracted claims, 8 entity mentions, 0 sensor-event records, and 0 table rows. Those extracted claims come from the manifest/DVIDS description, not from a transcript or underlying mission report.

The extracted entities are basic provenance terms: AARO, Department of War, INDOPACOM, DVIDS, the PR48 report identifier, and the 2024/2026 date references. The graph's lack of sensor_event rows should not be misread as proof that no sensor was involved; the public source itself says the footage came from an infrared sensor. It only means this semantic extraction did not create a separate structured sensor-event record from the available public text.

Related graph links to PR45 and the row-collision around FBI Photo A2 are useful navigation or audit cues only. They are not corroboration, not a finding, and not a source-backed relationship between the visible PR48 contrast feature and any other Release 01 item.

Leads to check

  • Reconcile DVIDS Date Taken 01.01.2024 and VIRIN 240102-D-D0360-9234 with the release field that lists the incident date as N/A.
  • Resolve the release-row/provenance tension around PR48's row anchor and the adjacent FBI Photo A2 record that appears to carry the same DVIDS ID.
  • Locate the original sensor export or mission package, if releasable: platform track, exact time, coordinates, range, range rate, sensor model, field of view, stabilization mode, and calibration are all needed before estimating motion or scale.
  • Determine whether the visible three-bladed tower-like structures can be tied to a real location or installation. That could support later weather, terrain, air-traffic, drone, bird, balloon, or debris checks, but the public MP4 alone does not give enough geometry.
  • Compare PR48 with nearby Release 01 video records only after source-level custody is established. Similar DVIDS formatting or graph adjacency is not enough to merge events.

Lead check notes

  • Checked — MP4 identity and source link: the release-file copy matches DVIDS Video ID 1006110, title DOW-UAP-PR48, Unresolved UAP Report, INDOPACOM, 2024, byte count 116,761,162, and SHA-256 bd1f002f45052b12ee067455a0a4b589b0bdaed40d75874d8da8fbf64eae8dd1 in the current release metadata.
  • Partial — date and VIRIN provenance: DVIDS lists Date Taken 01.01.2024 and VIRIN 240102-D-D0360-9234, while the release row keeps incident date as N/A. That remains a source-metadata reconciliation lead until a mission package or corrected release record ties the public date to the underlying observation time.
  • Partial — row and adjacent-record cleanup: available graph/release context keeps PR48's current-row anchor and the nearby FBI Photo A2 DVIDS-ID collision as provenance-cleanup issues only. They do not establish that the still-photo record and PR48 describe the same event, platform, or object.
  • Blocked — original sensor context: no original sensor export, platform track, range/range-rate data, field-of-view/stabilization details, coordinates, calibration record, operator log, or oral/written reporter description is present in the public release. Motion, size, range, altitude, and independent movement cannot be estimated from this MP4 alone.
  • Needs external source — location and ordinary-context checks: the tower-like structures in the public video are a useful visual lead, but the clip does not provide a confirmed location or geometry. Weather, terrain, air-traffic, drone, bird, balloon, debris, satellite, and lighting checks require an external location/time source or unredacted collection context.
  • Partial — adjacent video comparison: PR45 and other nearby Release 01 video records are navigation/context leads only. Similar DVIDS formatting, graph adjacency, or release-row proximity is not source-level custody for a shared observation.

Deep investigation — graph + web reconnaissance

Source and media reread

PR48 remains a video-only public release, not a complete incident file. The verified Open Sky release-file copy is a 116,761,162 byte MP4 with SHA-256 bd1f002f45052b12ee067455a0a4b589b0bdaed40d75874d8da8fbf64eae8dd1 and MP4 ftyp magic. The live DVIDS page was reachable during this check and preserved the same public identity fields: Video ID 1006110, VIRIN 240102-D-D0360-9234, filename DOD_111689167, title DOW-UAP-PR48, Unresolved UAP Report, INDOPACOM, 2024, Date Taken 01.01.2024, Date Posted 05.08.2026 07:50, category B-Roll, length 00:01:39, and location (UNDISCLOSED LOCATION).

A fresh official DVIDS thumbnail reread supports the existing cautious media posture. The visible frame is a low-resolution grayscale/infrared-style display with black masks/redactions, magenta HUD-style reticle/bracket/orientation symbology, and a noisy gray background. At most, a tiny point-like contrast speck is visible near the reticle area; it is not a resolved object shape and does not establish wings, body, range, scale, speed, altitude, or independent motion. The earlier full-runtime page review and this thumbnail check should both remain bounded by the same source limit: the public MP4 is a compressed, redacted presentation copy, not the original sensor export.

Graph connections and extraction quality

The graph has an exact VideoEvidence record for official:video:war-pursue-uap-release:dvids-1006110. That node preserves the canonical DVIDS URL, DVIDS short URL, CloudFront MP4 URL, related CSV row [105], incident date N/A, incident location Indo-PACOM, full_download_bytes 116,761,162, and the same MP4 SHA-256. It also carries one direct manifest-description text chunk.

Semantic graph coverage is narrow: the exact video asset currently has 10 machine-extracted Claim nodes and 8 EntityMention nodes, with 0 SensorEvent nodes and 0 exact CANDIDATE_CROSSLINK edges returned. The extracted claims are marked machine_extracted_needs_human_review / not_a_finding and mostly preserve source identity terms: AARO, Department of War, INDOPACOM, DVIDS, DOW-UAP-PR48, the 2024/2026 date cues, and the publisher's caution that the description is not an analytical judgment. One motion claim is just the manifest text clipped around the official description, and one witness_testimony claim miscasts the publisher caution as testimony; treat those as extraction-quality notes, not human testimony or a performance finding.

The companion Release 01 row records still show provenance drift. The PR48-titled release-record node is anchored to graph row 102 and can carry a stale PR45 final URL, while a current row-105 record titled FBI Photo A2 can carry PR48's DVIDS ID/final URL. The stable identity for this page is therefore the exact video ID, canonical DVIDS URL, MP4 bytes, and MP4 hash; the row/title collision is an audit-cleanup lead, not corroboration and not evidence that PR48 and FBI Photo A2 describe the same observation.

External provenance and official-source checks

Official-source custody is strongest at DVIDS for this item. The live DVIDS page returned 200, the DVIDS short URL resolved to the canonical PR48 page, and the public CloudFront MP4 object answered a byte-range request with 206 and Content-Range: bytes 0-2047/116761162. WAR.GOV/PURSUE landing and CSV probes returned 403 during this check; that is an access/custody limitation rather than a contradiction because the cached Open Sky release-file copy, DVIDS page, graph video node, and release inventory agree on the public video identity and hash baseline.

Internet Archive CDX also listed exact DVIDS-page snapshots from 2026-05-08 and 2026-05-17, which is useful provenance for the public source page. A CDX probe for the CloudFront MP4 timed out and the WAR.GOV landing CDX probe returned a temporary service error, so those are follow-up leads rather than replacement custody.

No companion mission report, reporter narrative, raw sensor export, platform log, unredacted metadata strip, range/range-rate source, sensor model/settings sheet, or AARO analytical packet surfaced in this graph-and-web pass. The DVIDS (UNDISCLOSED LOCATION) field, the Release 01 Indo-PACOM location, and the DVIDS 01.01.2024/VIRIN date cues therefore remain source-metadata fields, not enough context for event-level geometry.

Prosaic checks and open questions

Because the incident date is N/A, the location is only Indo-PACOM / (UNDISCLOSED LOCATION), and the source gives no platform track or line of sight, ordinary-context checks cannot yet produce meaningful exclusions. A literal 2024-01-01 graph probe returned no modeled astronomy, weather, or launch rows for that date, but that is only a graph-coverage note and should not be read as a real-world exclusion because the public source does not establish an exact collection date, coordinates, or viewing geometry.

The first ordinary-context lanes to preserve are sensor/display behavior, stabilization or tracking mode, compression and scaling, black-mask/overlay effects, gain/focus changes, possible glare/vignetting, parallax from platform/sensor motion, and ordinary small-object explanations such as birds, drones, balloons, debris, insects, aircraft, or terrain/water background features. Those checks require the missing original sensor material, unredacted metadata, platform/sensor geometry, weather, traffic, and environmental context.

Audit note

This section adds source-grounded graph and web reconnaissance only. It does not identify the visible contrast feature, convert machine extractions into findings, or assert a resolution. PR48 remains a verified public MP4 record with unresolved source-context gaps.

Limits

This page does not identify the contrast feature. It does not infer size, altitude, range, speed, distance from camera, independent motion, or prosaic/anomalous cause. The public MP4 is compressed, redacted, and overlaid with display symbology; it is not the raw sensor export. The release includes no oral/written reporter account, no mission form, no transcript, no coordinates, and no independent sensor logs.

The official description itself is bounded and informational. Until the original collection context is available, PR48 should remain a source-reviewed investigation draft with review_status: "graph_investigation_draft", investigation_status: "needs_human_review", and finding_status: "not_a_finding".

Sources