DOW-UAP-D083, Narrative Statement 5, Western United States Event, 2023

53
⬇ Download HD (566.1 KB)
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
PDF
Event Date
October, 2023
Released
2026-06-12
Size
566.1 KB
Original Filename
DoW-UAP-D083_Narrative-5_Western-US-Event.pdf
Location
Westen United States
Status
REDACTED

This memorandum presents the first-hand narrative from Witness 5 provided to the All-domain Anomaly Resolution Office (AARO). Witness 5 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 991 words from pages 1, 2, 3 of 5.

PAGE 1

OFFICE OF THE UNDER SECRETARY OF WAR 5000 DEFENSE PENTAGON AND SECURITY MEMORANDUM FOR RECORD SUBJECT: Nairntive from Witness 5 -Western U.S. Event This memorandum presents the first-hand naiTative from Witness 5 provided to the All­ domain Anomaly Resolution Office (AARO). Witness 5 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. In response to AARO's request to provide a free-fo1m nairntive of the sequence of events exactly as they remember them, Witness 5 submitted the following text: 1. SA - and myself, headed for the-Gate ai·ound 1630. 2. We headed south on and took note of two males (20s) car and plate - I sedan; plate: - after we asked ifthey had car trouble. They responded with something like "Thank you for your concern, but we are just taking a few pictures." 3. There was a Trailer and white minivan to the left of the road sho1tly after as well. 4. We found our tum off towai·ds I just before the sign' Wildlife National park" (?name). The road was unpaved and rough. There were signs saying to not sleep in vehicle when we entered. About two miles into this road, there was a trailer, a white jeep wrangler, and an old red volkswagon van. I think I saw a screen on inside the trailer. 5. The sun was setting, but there was still sunlight to see the mountain fo1mations. On this road, ahead and slightly to our right, at 1858, we noticed a lai·ge orange light. Upon closer look, the orange light appeared to be placed on something, although nothing could be identified to be holding it up. It seemed to be hovering with zero resistance or movement, or to be suspended just over a distinctive peak in the ridge line. I think the light lasted less than or about a minute, but it was longer than just a flash of light.

PAGE 2

5.1. ■■ October 2023, looking at google maps of location, SA and I believe this orange light was at coordinates ■■■■■■ 6.We could not travel much farther in the vehicle, parked, and continued on foot around 1910. 7.Around 1918 we saw a large red orb at a further distance, facing North and slightly West, past the peak of . I am certain I saw two red, smaller orbs release from the larger one going west, towards . One released at a steady speed and horizontally. I also saw another small red orb go up, but it may have had a slight angle. This orb was fainter, than the horizontal one identified. They were simultaneously released, moving away from the larger orb. The larger orb did not move during this time, and all lights were gone from every orb in about 10 seconds. Either while the lights were on, or shortly after they were out of sight, we saw a white flash of light in the sky to the West. 8.We continued to hike west up the road and saw the large orb again, at 1937, but to our left -in front of . I don't recall if this had any smaller released, and the large orb lasted about 10 seconds again. There was a similar white flash of light in the sky more southwest. 9. Approximately 3 miles from where we parked the vehicle, we set up a camera in hopes to catch photos if anything returned to sight. 9.1.There was intermittent radio, but when we had radio, we could hear other teams, but after reconvening on ■■■ October, found out that other teams could not hear us when we were 10.We had heard the other teams leave around 2330, and started to pack our gear to hike back to the vehicle. 1.We made it to our vehicle around 0130. We made our way down the mountain and got turned around in the wildlife area on our way out. We made it back to Highway ■ about 0330 and to the-gate about 0415. 2.We were driving around- lake, headed towards- base. Around 0430, I notice two lights in the distance about 2-3ft above the ground. The lights stayed on the far side of the road, but directly over the pavement. One was white and square, the second was round and red. The red light was diagonally to the left above the white lite. I watched it and wondered if someone decided to take a bike ride. 3.Another vehicle started- approaching from the opposite traffic side as we were approaching the red and white light pair. I started to notice the pair drifting into the sand, off the side of the road. I pointed out to SA■■■ I that the lights seemed odd and asked if he could see it. We were quickly approaching the lights and started to slow down, maybe 100 ft or so in front of us. The lights made it hard to see what would have been displaying the lights themselves. It appeared that the lights may have been directly facing us.

PAGE 3

4.As we were slowing our vehicle, and the opposite traffic vehicle quickly approached, the red and white light pair hovered, with zero resistance, or change in height, over the bushes to the at about 15-20 mph. The light pair stopped just as we stopped our vehicle and I pulled out the Night Vision Goggles (NVGs) to take a look. I saw the light pair for a split second in the NVGs before the lights turned off and I saw a very thin line remain, maybe 4 ft wide, horizontal to the earth (See Image 1). It began moving at the same speed, 15-20 mph, and I could not see it for more than a second or two before I lost track of it. It also seemed to move up in height with this movement, but remained a flat line.

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 #202 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #376 of 450.

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

Anomalousness Index: 53/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 (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 53/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:

ad70e6d8f9091d432dd89d9cd803734c0a297f16cb211311feb609fb435ff360

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-D083_Narrative-5_Western-US-Event.pdf

📡 Subscribe via RSS 🔔 Watch on GitHub