FBI-UAP-D019, Digital Rendering, Narrative Statement 2-4, Western United States Event, 2023

64
FBI-UAP-D019, Digital Rendering, Narrative Statement 2-4, Western United States Event, 2023
⬇ Download HD (505.6 KB)
SHARE Reddit X Facebook HN Email
Agency
FBI
Category
fbi
Type
IMAGE
Event Date
October, 2023
Released
2026-06-12
Size
505.6 KB
Original Filename
FBI-UAP-D019_Digital-Rendering_Incident-2-4_Western-US-Event_2023.jpg
Location
Western United States

This image is an artistic interpretation of a reported incident near a sensitive national security site in the western United States involving unidentified anomalous phenomena (UAP) over a period of two days in October 2023. This image is based upon a first-hand description provided by a federal law enforcement special agent, as described in DOW-UAP-D080. The Federal Bureau of Investigation prepared this digital rendering at the request of the Department of War in 2026.

The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.

Where this file fits in the PURSUE archive

This file is one of FBI's 87 files in the Trump PURSUE disclosure. Within the FBI agency block it ranks #12 of 87 by Anomalousness Index. Across the entire 334-file archive it ranks #127 of 334.

That places it in the mid-archive band (127 of 334 by score). The score reflects the rubric's read on evidentiary weight, not the underlying event's significance.

For the broader cluster context, this file is part of FBI Modern UAP Files - the FBI's modern UAP files: the 2022 Colorado Springs interview and the FBI-authenticated northeastern orb videos. The cluster page walks through all 30 member files with regional grouping, sensor breakdown, and standout analysis.

Anomalousness Index: 64/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 (photographic) 55 × 0.25 = 13.75

A still-photograph capture from the FBI, not a time-series sensor record. On the sensor-quality axis, a single frame carries less evidentiary weight than instrumented, time-stamped capture, because it can't show how the object behaved before or after the shutter opened - the temporal context that helps rule out artifacts.

witness credibility (federal agent) 90 × 0.2 = 18.0

The witness here is FBI personnel, entering the report into the federal investigative system through standard channels. That's a real credibility tier - trained federal investigative staff - though the rubric ranks it below mission-active military or astronaut testimony because the posture is reactive (responding to a report) rather than an active operational context.

corroboration (single witness instrument) 60 × 0.2 = 12.0

On corroboration, this file from the FBI - 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 (open after review) 90 × 0.1 = 9.0

This file was released as open by the FBI after a formal review process concluded - not simply logged and left pending. That's a stronger disposition signal than 'unresolved, no review': a review actually happened, and remaining open is the FBI's own published conclusion from it, not an absence of one.

Bottom line on the score: the Anomalousness Index of 64/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 FBI

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

FBI · VIDEO SCORE 70

FBI-UAP-PR001, “Triangle Orbs,” Northeastern United States, 2021

FBI · VIDEO SCORE 70

FBI-UAP-PR002, “Red Orb Rotation,” Northeastern United States, 2022

FBI · VIDEO SCORE 70

FBI-UAP-PR003, “Orbs Over the Pond,” 2024

FBI · VIDEO SCORE 70

FBI-UAP-PR004, “Northeastern Orb Sighting,” 2025

FBI · VIDEO SCORE 70

FBI-UAP-PR005, Digital Recreation, Narrative Statement 3-1, Western United States Event, 2…

FBI · VIDEO SCORE 70

FBI-UAP-PR006, Digital Recreation, Narrative Statement 3-2, Western United States Event, 2…

BROWSE ALL 334 FILES →

Verification

SHA-256:

623e02b31165d3a59f50ac19169d381750f00f79fedb3a3f762f5e1fc23e4c3d

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: https://www.war.gov/medialink/ufo/061226/release_03/documents/FBI-UAP-D019_Digital-Rendering_Incident-2-4_Western-US-Event_2023.jpg

📡 Subscribe via RSS 🔔 Watch on GitHub