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

DOW-UAP-PR064, "AFSOC Kabul UAP Jul 2017"

This Release 02 item is an official Department of War / AARO video record from manifest row 124, published in the 5/22/26 WAR.GOV/PURSUE release and mirrored through DVIDS video ID 1007741. The uploader defined title is AFSOC Kabul UAP Jul 2017, but the release text is careful:…

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

DOW-UAP-PR064, "AFSOC Kabul UAP Jul 2017"

Investigation reading

This Release 02 item is an official Department of War / AARO video record from manifest row 124, published in the 5/22/26 WAR.GOV/PURSUE release and mirrored through DVIDS video ID 1007741. The uploader-defined title is AFSOC Kabul UAP Jul 2017, but the release text is careful: AARO says the video is likely derived from an infrared sensor aboard a U.S. military platform operating in the U.S. Central Command area of responsibility, and the release cautions that many responsive materials lack a substantiated chain of custody.

The official description is narrow. It describes a 17-second clip, with 00:00-00:13 labeled as no content and 00:14-00:15 as an area of contrast moving from the left edge of the sensor field of view to the right edge and out of view. That description is explicitly informational only; it is not an analytical judgment or a finding about the event's validity, nature, or significance.

What the released item appears to contain

The downloaded source media is a short grayscale / infrared-looking sensor-display video over a built-up ground scene. The imagery includes display overlays, magenta/purple reticle or marker graphics, and black rectangular masks or redaction/display blocks. The derived full-runtime contact sheet shows visible ground/sensor imagery before 13 seconds, so the official No content wording should not be read as a blank-screen claim from this review alone; it may mean no target-relevant content in the release description.

Around the official 14-to-15-second window, the scene brightness and contrast change, and a small dark dash-like contrast feature is visible in one sampled frame near the central display area. It is not continuously resolved across the sampled frames. The center-crop review supports cautious wording: the suspected target area contains a very small, ambiguous contrast feature embedded in terrain, display processing, redaction, compression, and changing contrast. The sampled stills do not establish object identity, distance, scale, speed, independent motion, or anomalous performance.

PR064 full-runtime one-second samples

PR064 official contrast-window full-frame samples

PR064 official contrast-window center-crop samples

Source asset review

The individual official DVIDS/CloudFront MP4 was downloaded and inspected directly rather than substituting the full Release 02 video ZIP. The direct media response returned 200, accept-ranges: bytes, content-length: 3233071, last-modified: Fri, 22 May 2026 11:30:56 GMT, and a byte-range probe returned 206 with content-range: bytes 0-0/3233071.

FieldSource-review value
Direct media URLhttps://d34w7g4gy10iej.cloudfront.net/video/2605/DOD_111719852/DOD_111719852.mp4
Downloaded size3,233,071 bytes
SHA-256915d855cc6f83aa0b0700d9acb23b2804f8fb53dcc20941a51c4b30a994c5cd8
CRC32 of downloaded direct MP4b7a581d0
ContainerQuickTime / MP4
Duration17.684333 seconds
Video streamH.264, 640x360, 30000/1001 fps, 530 frames, yuv420p
Audio streamAAC stereo, 48,000 Hz, about 17.652 seconds
Audio signal checkdecoded audio RMS 0.0, max absolute sample 0.0; effectively silent in this review
DVIDS filename / VIRINDOD_111719852 / 170702-D-D0360-8227
DVIDS listed length00:00:17

The Release 02 remote video-ZIP central directory lists video_2605_DOD_111719852_DOD_111719852.mp4 as 3,228,019 bytes with CRC32 36f2427f. That does not match the downloaded direct DVIDS MP4 size or CRC32. Until the ZIP entry is byte-compared against the direct DVIDS object, this should be treated as a source-custody/versioning lead, not as a substantive finding about the imagery.

Source custody and provenance

Primary public provenance for this page is the official WAR.GOV/PURSUE Release 02 landing page, the Release 02 manifest row, and the DVIDS page for video 1007741. The DVIDS page resolved to https://www.dvidshub.net/video/1007741/dow-uap-pr064-afsoc-kabul-uap-jul-2017, with title DOW-UAP-PR064, "AFSOC Kabul UAP Jul 2017", category Briefings, date taken 07.01.2017, date posted 05.22.2026 07:30, location field AF, filename DOD_111719852, and courtesy source All Domain Anomaly Resolution Office.

There are source-date and location tensions to preserve. The manifest row gives Incident Date: Not stated and Incident Location: CENTCOM; the title and DVIDS date metadata point toward Kabul / July 2017; and the DVIDS description text says AARO assesses the video is likely derived from a platform operating within the CENTCOM area of responsibility in 2021. Those fields should be reconciled against the release manifest, DVIDS metadata, and any future custody records before writing a timeline or location finding.

Graph context

No exact Release 02 graph record was returned for this slug, title, or DVIDS ID during this run's read-only graph context check. That is not a source-access problem; it means this page is currently anchored to official manifest/DVIDS provenance while graph ingest for Release 02 catches up. Future title-related or dataset-wide graph hits should be treated as leads until their provenance links resolve back to this exact official asset.

Leads to check

  • Reconcile the title and DVIDS date metadata (AFSOC Kabul UAP Jul 2017, 07.01.2017, VIRIN 170702-D-D0360-8227) with the DVIDS description's 2021 wording and the manifest's Incident Date: Not stated field.
  • Byte-compare the direct DVIDS MP4 against the Release 02 video-ZIP entry because the current direct-file size/CRC32 and ZIP central-directory size/CRC32 do not match.
  • Review the 14-to-15-second interval with stabilization or frame-differencing if higher-confidence motion assessment is needed. The contact sheets alone show an ambiguous contrast feature and changing display/contrast conditions, not a resolved object track.
  • Confirm whether the DVIDS AF location field is intended as Afghanistan metadata, a DVIDS location shorthand, or a generic/legacy field; do not infer exact coordinates from it.
  • Look for any paired platform, sensor, mission, or chain-of-custody record that could clarify range, platform motion, sensor mode, target geometry, and original upload history.

Limits

This is a short, redacted, low-resolution public video with no released platform telemetry, range, azimuth, altitude, sensor settings, target track file, or independent corroborating sensor record on this page. The visible display overlays, black masks, compression, contrast shifts, and background terrain make the small contrast feature difficult to separate from scene and processing artifacts. This page is a source-review draft and not a finding.

Sources