PURSUE Release 01: DOW-UAP-PR31, Unresolved UAP Report, Syria, October 2024

  PR31 Syria Clip

DVIDS identifies DOW-UAP-PR31 as a courtesy video from the All-domain Anomaly Resolution Office, posted on May 7, 2026, with Video ID 1006076, VIRIN 241002-D-D0360-8752, filename DOD_111688970, location SY, and a five-second runtime.¹ PURSUE Release 01 metadata pairs PR-31 with DoW-UAP-D32, a Department of War mission report for Syria in October 2024.²³

The DVIDS record says USCENTCOM submitted a UAP report to AARO based on five seconds of full-motion video from a U.S. military platform in 2024.¹ Its clip description places the visible event in the first second, when an indistinct multi-colored area moves right to left along the top edge of the sensor display.¹⁴

  The D32 Mission Report

The paired D32 PDF is a USCENTCOM MISREP marked "SECRET//REL TO USA, FVEY" before declassification by MG Richard A. Harrison on October 24, 2025, and approval for release to AARO.³ Its administrative fields place the sortie under Operation Inherent Resolve in the air domain, identify USCENTCOM as the combatant command, list AFSOC as major command, name the 609th operations center, and give 12 SOS as the originator.³

The mission timeline records takeoff from OJMS at 0823Z on October 20, 2024, ISR tasking with FMV as the primary sensor, and a dynamic target-development period beginning at 1230Z in which UAP activity was logged from 1559Z to 1644Z.³ The UAP form lists initial contact at 201559:00ZOCT24, describes light or glare crossing the FMV camera feed, and records no response change, no sensor interrogation, no observer engagement, no reported effects on persons, and no recovered material.³

In the GENTEXT/UAP section, the reported appearance is a "misshapen and uneven ball of white light"; the narrative describes multiple glares or lights from unknown origin, three direct FMV-camera crossings, and halo effects at the top of the feed at 1609Z and 1620Z.³ The same section says the aircrew assessed no mission impact or change and considered the UAP benign; another UAP field says the crew assessed it was not a lasing event.³

  What the Pairing Adds

PR31 matters because the public clip is only five seconds long, but the paired document anchors it to a longer ISR sortie, a specific observation window, sensor context, reported aircraft state, and the contemporaneous language used inside a military UAP form.¹³ That context helps separate what the media record depicts from what the mission report says the crew logged.¹³

The record also keeps the evidentiary boundary visible. DVIDS presents the video description as informational and cautions readers not to treat it as an analytical judgment or final determination about the event's validity, nature, or significance.¹

  References

  References

1. dvidshub.net ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

2. war.gov ↩

3. war.gov ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹

4. d34w7g4gy10iej.cloudfront.net ↩