Archive review · October 2, 2026. The Pentagon's September 18 release pairs an unusual operator account with a sensor sequence that demands careful reading. DOW-UAP-D107 records a reported speed of up to 500 mph. Its companion infrared video, DOW-UAP-PR133, is listed as unresolved, and the official description says the automatic tracking reticle fails to establish a lock during one short interval.

What the government record establishes

The PURSUE catalogue identifies a Central Command submission containing 4 minutes and 58 seconds of infrared footage. The D107 description attributes the appearance and speed characterization to the military operator. It expressly warns that descriptive and estimated characteristics represent the reporter's interpretation at the time, rather than a conclusive determination of the object's intrinsic features or performance.

That distinction is central. An official record can reliably establish that an observation was reported without independently validating every estimate inside it. The report deserves examination; the numerical claim still needs its measurement basis.

The interval worth checking

Between 02:29 and 02:36, the official PR133 timeline describes an auto-tracking reticle that does not lock onto the contrast feature. After it disengages, the sensor stops panning and the feature leaves the frame to the right. Other intervals describe changing magnification, panning, loss from the field of view, and reacquisition.

Our analytical inference is limited: motion across this changing display cannot, by itself, be treated as a complete world-space trajectory. A failed lock does not show that an object defeated the sensor, and it does not identify the object. Estimating physical speed requires connecting image coordinates to distance, timing and platform motion.

A year discrepancy remains visible

The official title and incident-year fields place the case in 2025, while the PR133 introductory description says the platform footage was from 2024. The paired D107 description says 2025. UFO Data's October 1 transcription reports an October 29, 2025 mission timestamp and flags the mismatch. We preserve that discrepancy rather than silently harmonizing the records.

What would advance the case

Useful follow-up would identify how the speed estimate was obtained and publish sufficient range, calibration and platform data to reproduce it. NASA's UAP work likewise emphasizes data quality and calibrated measurements. That is methodological context, not independent corroboration of this encounter.

This review checks the government's catalogue text and supporting transcription; it does not claim a fresh frame-by-frame reconstruction or a solved identification. The current public record supports a documented unresolved report with important sensor and metadata limitations.

Hero image: original AI-generated editorial illustration; not a photograph of an event, document, or recovered object.