DOW-UAP-D051, Email Correspondence, Pacific Time Zone, March 2023
This document is email correspondence describing the content of a mission report and requesting clarification on its content. All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.
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 431 words from pages 1, 2, 4, 5 of 6.
PAGE 1
Good morning! Thank you for your patience on this-- like I said, this was a first for me. Upon consulting internally here at HQ, our folks confirmed we do have the authority to process this as a derivative classification review, instead of a declassification request. Based upon the summary you provided below, I concur with using this at the UNCLASSIFIED level in your product. Consider your request approved. Please let me know if there's anything else I can do for you! OSI CI Collections and Operations PM Intelligence Oversight PM
PAGE 2
Good morning, Thank you for your request. Our process for declassifying IIRs is lengthy and requires AFOSI Commander signature so I'm exploring options akin to a security review of the UNCLASS summary you have provided below. This is a first for me so I appreciate your patience as I try to streamline this request for you! OSI CI Collections and Operations PM Intelligence Oversight PM
PAGE 4
CURRENT CLASSIFICATION S//NF-REQUESTED CLASSIFICATION UNCLASSIFIED Reported Appearance: An individual reported observing a large blue featureless triangular object with a solid, unwavering silhouette emitting powerful "whitish blue" light from multiple points along its perimeter. Reported Behavior: The reporter described the object as "hovering" stationary above or near a national security facility for approximately three minutes. They then reported observing it move to a position higher in their field of view. The reporter characterized the object's motion as "backing up" in a "jerking" or "jumping" manner inconsistent with "smooth" jet propulsion. The individual reported that they observed the object for approximately eight minutes. Other Observations: The reporter commented that they could not discern whether or how the object was controlled, could not identify its means of propulsion, and could not determine whether it had a defined "front or rear." They stated that they "didn't think" the object was a drone. The reporter also commented on behaviors and capabilities they did not directly observe. They stated that the object did not seem to travel along a defined flight path, possess any "photograph or data collection capabilities," emit a "vapor trail," or demonstrate "cloaking capabilities." Event Summary: Location: Pacific Time Zone Date: March 2023 Time of Day: Night Duration: Approx. 8 minutes Reporter Type: Civilian Obtained by: Personal cellular device Reported Characteristics: Altitude: Not reported
PAGE 5
Speed: Not reported Size: Large Shape: Triangular Color: Blue Material: Not reported Markings: Featureless Behavior: Emitting light, erratic movement The IIR and draft report are attached. This is a routine request, please confirm receipt. If you have any questions, please contact me. Information Disclosure Analyst Office of the Undersecretary of Defense for Intelligence and Security
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 #187 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #361 of 450.
That places it in the lower-scoring band of the archive (361 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.
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.
Reported by trained U.S. military personnel during an operational mission (3/23/26) - 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.
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.
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.
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.
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.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
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 →