DOW-UAP-PR089, "31 AUG [CALLSIGN] [CALLSIGN] Observes UAP part2"

66
⬇ Download HD (114.1 MB) 📖 Deep dive: The 51 Release-02 Pentagon UAP videos (DOW-UAP-PR series) Themed clusters (formations, spherical, USO), geography (CENTCOM + NORTHCOM + Southeastern US), how this batch tripled the score-66 tier READ →
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
VIDEO
Event Date
2020
Released
2026-05-22
Size
114.1 MB
Location
CENTCOM
Status
REDACTED

On March 6, 2026, eight members of the U.S. House of Representatives requested access to 51 potentially UAP-related records allegedly held by the Department of War and the Intelligence Community. The All-domain Anomaly Resolution Office (AARO) identified a collection of responsive materials held on a classified network. Many of these materials lack a substantiated chain-of-custody. AARO assesses that this video, whose uploader-defined title is, “31 AUG 2020 [CALLSIGN] [CALLSIGN] Observes UAP part2,” is likely derived from an infrared sensor aboard a U.S. military platform operating within the United States Central Command area of responsibility in 2020. A user uploaded this video to a classified network in August 2020. Video Duration: 00:04:58 Video Description: 00:00-00:45: The sensor tracks an area of contrast near the center of the screen. 00:46-01:09: Another area of contrast enters the field-of-view from the lower right side of the screen. The sensor pans to track both areas, but the second area of contrast exits the field-of-view. 01:10-01:22: The sensor cycles contrast modes, causing the area of contrast to momentarily lose distinctiveness against the background. 01:23-02:35: Several areas of contrast enter and exit the frame. 02:36-02:41: The areas of contrast become indistinct against the background. 02:42-03:22: The areas of contrast become distinguishable again. 03:23-03:43: Several areas of contrast enter and exit the screen. 03:44-03:48: The sensor pans to track the area of contrast. 03:49-04:01: The area of contrast exits the sensor field of view from the right side of the frame. 04:02-04:58: No content. This video description is provided for informational purposes only. Readers should not interpret any part of this description as reflecting an analytical judgment, investigative conclusion, or factual determination regarding the described event’s validity, nature, or significance.

Note: war.gov publishes this same release note for all 51 Congressionally-requested DOW-UAP-PR records, so it is not specific to this file. This file's own specifics are in its title above, the video and metadata below, and the original analysis that follows.

Where this file fits in the PURSUE archive

This file is one of DoD's 171 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #47 of 171 by Anomalousness Index. Across the entire 334-file archive it ranks #61 of 334.

That places it in the archive's densest scoring band - 92 files tied at 66, anchored by AARO-submitted and Release-02/04 military infrared captures.

For the broader cluster context, this file is part of Release 02 Pentagon UAP Videos - the 51-file DOW-UAP-PR050-PR099 series released in PURSUE Release 02 on May 22, 2026. The cluster page walks through all 51 member files with regional grouping, sensor breakdown, and standout analysis.

Anomalousness Index: 66/100

Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.

🤖 AI-ASSISTED SCORING · methodology

The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.

sensor quality (single sensor military) 80 × 0.25 = 20.0

This file from the Department of War is a single-sensor military capture - one instrumented platform, one modality, time-stamped and recoverable rather than a witness account. The rubric scores it below a multi-sensor capture because cross-modality confirmation (the same object seen by two independent sensor types at once) is the higher bar on this axis, and that confirmation isn't present here.

witness credibility (military personnel) 80 × 0.2 = 16.0

Reported by trained U.S. military personnel during an operational mission (2020) - the rubric's second-highest witness-credibility tier, one step below astronaut testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.

corroboration (single witness instrument) 60 × 0.2 = 12.0

On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.

kinematic anomaly (no kinematic data) 30 × 0.15 = 4.5

The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.

mundane explanation available (weak mundane candidate) 70 × 0.1 = 7.0

Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.

official disposition (unresolved no review) 60 × 0.1 = 6.0

This file from the Department of War is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.

Bottom line on the score: the Anomalousness Index of 66/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.

Related files in DoD

Other PURSUE files in the same category, ranked by Anomalousness Index.

DoD · VIDEO SCORE 68

DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023

DoD · VIDEO SCORE 68

DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…

DoD · VIDEO SCORE 68

DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015

DoD · VIDEO SCORE 68

DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020

BROWSE ALL 334 FILES →

Verification

SHA-256:

bcc885a0448e836827dc46ee2114d0d54bd0cb8047589b3e244428863752f955

This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →

Source (DVIDS): https://www.dvidshub.net/video/1007712/dow-uap-pr089-31-aug-callsign-callsign-observes-uap-part2

Direct video file: https://d34w7g4gy10iej.cloudfront.net/video/2605/DOD_111719730/DOD_111719730-1920x1080-9000k.mp4

📡 Subscribe via RSS 🔔 Watch on GitHub