LLE-UAP-PR003, Unresolved UAP Report, Colorado, October 2023
A local law enforcement officer submitted a report of an unidentified anomalous phenomenon to the All-domain Anomaly Resolution Office consisting of 27 seconds of video footage from a commercially available cellular device’s rear-facing camera in October 2023. The reporting officer described the phenomenon as “silent” and as featuring “red, blue, and green flashing lights.” Video Description: In the first 2 seconds of this video, AARO digitally altered this footage by blurring the bottom half to obscure information whose release could be reasonably expected to affect the privacy or other protected interest of a U.S. person or commercial entity. 00:00-00:27: The camera increases its level of magnification and focuses on an apparent light source for the duration of the video, keeping it generally centered and within the top third of the frame. AARO Comment: Cellular devices of the type used to capture this footage employ autofocus and other automated image-processing functions that may distort the apparent morphological and kinematic characteristics of distant subjects, particularly at high magnification.
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 Local Law Enforcement's 8 files in the Trump PURSUE disclosure. Within the Local Law Enforcement agency block it ranks #3 of 8 by Anomalousness Index. Across the entire 450-file archive it ranks #247 of 450.
That places it in the lower-scoring band of the archive (247 of 450 by score), typical of recordings that are not instrumented military sensor captures.
Anomalousness Index: 57/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.
A moving-image capture from local law enforcement recorded on a camera, not an instrumented sensor platform. On the sensor-quality axis the rubric scores that below military sensor capture, since the footage cannot be cross-checked against a second instrument, though it does show motion over time in a way a single frame cannot.
This account comes from a law enforcement officer, which the rubric weights a step below uniformed military personnel and above a credentialed civilian. The weighting reflects training in observation and reporting without the operational mission context that military reports carry. It is one of six score components, not a verdict on the event itself.
On corroboration, this file from local law enforcement - 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 local law enforcement 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 57/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 Local Law Enforcement
Other PURSUE files in the same category, ranked by Anomalousness Index.
ODNI-UAP-D001, USPER Narrative, Senior USIC Official
CIA-UAP-002, Scientific Advisory Panel on Unidentified Flying Objects, Report, 1952-1953
CIA-UAP-003, The Central Intelligence Agency and Overhead Reconnaissance; The U-2 and OXCA…
CIA-UAP-004, CASE 17708 (CLOSED) and DR. Leon Davidson
CIA-UAP-005, German Scientist's Article on 'Flying Discs'
CIA-UAP-006, Sighting Of Unconventional Aircraft
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 →
Source (DVIDS): https://www.dvidshub.net/video/1023414/lle-uap-pr003-unresolved-uap-report-colorado-october-2023
Direct video file: https://d34w7g4gy10iej.cloudfront.net/video/2609/DOD_111985850/DOD_111985850-1920x1080-9000k.mp4