DOW-UAP-D080, Narrative Statement 2, Western United States Event, 2023

56
⬇ Download HD (1.0 MB)
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
PDF
Event Date
October, 2023
Released
2026-06-12
Size
1.0 MB
Original Filename
DoW-UAP-D080_Narrative-2_Western-US-Event.pdf
Location
Westen United States

This memorandum presents the first-hand narrative from Witness 2 provided to the All-domain Anomaly Resolution Office (AARO). Witness 2 was one of several United States (U.S.) federal law enforcement special agents who reported observing unidentified anomalous phenomena (UAP) over a period of two days in October 2023 in the western United States.

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

Text of the document

Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 996 words from pages 1, 2 of 8.

PAGE 1

OFFICE OF THE UNDER SECRETARY OF WAR 5000 DEFENSE PENTAGON AND SECURITY MEMORANDUM FOR RECORD SUBJECT: Nairntive from Witness 2 -Western U.S. Event This memorandum presents the first-hand naiTative from Witness 2 provided to the All­ domain Anomaly Resolution Office (AARO). Witness 2 was one of several United States (U.S.) federal law enforcement special agents who reported observing unidentified anomalous phenomena (UAP) over a period of two days in October 2023 in the western United States. ill response to AARO 's request to provide a free-fo1m naiTative of the sequence of events exactly as they remember them, Witness 2 submitted the following text: ill October 2023, my paitner and I were tasked to survey an area for individuals launching drones. My paitner and I were positioned in a valley, with mountain ranges to the west and east and more distant ranges to the north; we had teams positioned throughout the ai·ea as well. The weather was clear; we sat [a nd] watched the sunset as dusk trnnsitioned into darkness. At degrees above the n01thern/no1theastern horizon. Originally, the light was not dissimilar to that of a luminescent planet obse1ved in the night sky but grew slowly brighter. The bright orb-like light had a smaller red orb-like light within it. As the bright orb-like light grew lai·ger, it expelled three or four red lights from it. The red lights accelerated instantly and maneuvered with perfect, smooth coordination into a horizontal fonnation. The red lights were approximately 1/15 the size of the orb-like light. The bright orb-like light did not appear to be an aitificial neon glow, but rather a bright natural light with a slight halo effect. The red lights were less luminescent and appeai·ed to be more like artificial lights (e.g., taillights). Following the expulsion of the smaller red lights, the bright orb-like light dimmed and faded from sight. From approximately 1900 hours to approximately 1930 hours, I witnessed the process repeat approximately five times across the n01thern, northeastern, and eastern horizon. Our teams confnmed they obse1ved the same objects. The last grouping of red lights moved in a horizonal pattern to the southern horizon where they remained the rest of the evening. The three red lights were all aligned and remained equally spaced. From approximately 1930 hours until approximately 2300 hours, the red lights hovered above the southern horizon. The red lights sometime dipped below the horizon, out of sight but consistently rose back up. At

PAGE 2

approximately 2300 hours we departed the area. There were no acoustics, interreference or physiological effects experienced during the incident. The objects appeared to move with purpose in a coordinated fashion, but it did not appear to be a defensive countermeasure. It looked like a mix of mechanical deployment and biological division; it appeared too smooth and agile to be mechanical, but too structured/coordinated to be a biological division. To offer an obscure yet similar description, I find the characterization of portals oddly comparable to the event I witnessed. The bright orb-like light was small, grew larger, appeared to project objects out of it, and then it dimmed until it was no longer visible; not dissimilar to the opening and closing of a portal through which objects travel and deploy forward. I am not saying or suggesting that was what we observed but rather offering that as a In October 2023, my partner and I were tasked to survey an area for individuals launching drones. My partner and I drove northwest on a rural highway and turned right onto a dirt road heading north/northeast up a valley toward a mountain range. We drove for approximately 10 miles before parking a small hill at approximately 1800 hours. The weather was clear; we sat [and] watched the sunset as dusk transitioned into darkness. At approximately 1845 hours, I observed two circular orb-like lights appearing to be headlights of a vehicle to the south approximately five to seven miles away. The headlights sat still in the valley while we sat and continued to observe the area. At approximately 1900 hours, I observed a row of red lights appearing to hover approximately 15 degrees above the southern horizon (I do not recall how the lights entered the area). The lights were consistent with the glow of a taillight and appeared to be arranged in a triangular formation or attached to unobservable vehicle of some sort; they appeared to cover the area of a football field, hovering over a significant portion of the horizon. The object floated with an impossible, eerie stillness. At that same time, I observed the vehicle to the south of our location flash its lights toward us; the flashing appeared to be consistent with a white pulse. Soon after, what appeared to be headlights of a second vehicle approximately one mile east of the first vehicle, still approximately five to seven miles from our location. The second vehicle flashed their lights in the same manner as the first vehicle. The two vehicles appeared to hover within, approximately, a six-mile by six-mile box between the southern tips mountains ranges surrounding the valley. While the two vehicles moved in between the mountain ranges, the row of red lights remained in place, appearing to still hover above the southern horizon. At approximately 1915 hours, one of the vehicles appeared to move north toward our location. We decided to drive toward the objects. One set of lights turned off but the other remained in view. We drove with our headlights off only utilizing night vision equipment; at one point reaching approximately 70 miles per hour. At some point while driving toward it, the headlights morphed into one bright white/orange orb-like light with a halo-like glow. Around two or three miles north of the original highway we exited from, we appeared to be gaining on the object; at approximately 50 yards away we thought were going to encounter it. The object then accelerated instantly to the south, traveling at least one mile south in less than a

Where this file fits in the PURSUE archive

This file is one of DoD's 257 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #141 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #265 of 450.

That places it in the lower-scoring band of the archive (265 of 450 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.

Anomalousness Index: 56/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 (eyewitness only) 30 × 0.25 = 7.5

No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.

witness credibility (military personnel) 80 × 0.2 = 16.0

Reported by trained U.S. military personnel during an operational mission (October, 2023) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent 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 (open after review) 90 × 0.1 = 9.0

This file was released as open by the Department of War 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 Department of War's own published conclusion from it, not an absence of one.

Bottom line on the score: the Anomalousness Index of 56/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 450 FILES →

Verification

SHA-256:

2b011f25bb6fed4870766506b5799374cb3589d747c29e4227bab99ee779665b

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/DoW-UAP-D080_Narrative-2_Western-US-Event.pdf

📡 Subscribe via RSS 🔔 Watch on GitHub