DOW-UAP-D108: Six Small Spherical Objects, "Agile" and Estimated at 480 MPH -- Mission Report, Middle East, 29 July 2025

Source file: DOW-UAP-D108_Mission-Report-Middle-East-2025.pdf Originating agency: U.S. Air Force, 65 SOS (special operations squadron), 1 SOW, AFSOC, Operation INHERENT RESOLVE, USCENTCOM; submitted to AARO Document type: Mission Report (MISREP) prod-dod-11604218, with a dedicated UAP section Date: Sortie 29-30 July 2025; UAP initial contact 2022:32Z on 29 July 2025 Classification: SECRET//NOFORN (markings struck through, "UNCLASSIFIED"); declassified by MG Richard A. Harrison, USCENTCOM Chief of Staff, on 10 July 2026; released 2026 Page count: 8 VIRIN: 260918-D-D0360-1097 PURSUE Release: 6

Summary

This is the fullest of the four MISREPs in this group. Like DOW-UAP-D107 it uses the newer "prod-dod" form with a dedicated UAP block, but here the observer filled in most of it: a description, speed, altitude and heading estimates, the aircraft's own heading and speed, and yes/no answers on propulsion, intelligent control, effects and reactions.

The sighting came early in a sortie of about 20 and a half hours. At 2022Z on 29 July 2025, while "transiting to" its target and scanning the ground, the crew saw "6X small spherical objects grouped together". The rest of the mission was routine collection: the ISR block logs one essential element of information observed, and a final "NIB" tasking found "no EEI related activity". The report is paired with the one-minute infrared video DOW-UAP-PR135.

Research Article

The sortie

The narrative (page 1) records a "7-LINE" tasking at 1554Z, a takeoff at 1734Z "VIA SLR" (an abbreviation not expanded in the document; in Air Force remotely piloted aircraft usage, satellite launch and recovery), the UAP at 2022Z, arrival at the start point at 2236Z, the call to return to base at 0930Z on 30 July, a new "NIB" tasking a minute later, landing at 1411Z and engine shutdown at 1426Z. The lines are not printed in time order: the 1554Z tasking follows the 2022Z UAP entry. The total-mission-time field is redacted; the printed takeoff and landing times give 20 hours 37 minutes.

Several values appear as the plain words "DATA MASKED" (the supported unit, the tasking number), printed as ordinary text rather than as a coded redaction box. The document does not say who applied that masking. Everything else sensitive is redacted under (b)(1)(B), the Freedom of Information Act exemption for classified information, or (b)(6) for personal details. The ISR block records "EEIs Observed: Yes", one EEI (essential element of information), clear weather with "No Impact", and "Intel Gap Filled?: No". Full-motion video "WAS EXPLOITED BY GET", unexpanded.

The administrative blocks set this report apart from the other three: the major command is AFSOC (Air Force Special Operations Command), the originator 65 SOS, the mission wing 1 SOW, while D106, D107 and D109 come from attack squadrons under ACC or AFCENT.

Six spherical objects

The GENTEXT/UAP (page 7) opens with the description field: "6X SMALL SPHERICAL OBJECTS GROUPED TOGETHER". The event description, marked "SECRET//REL TO USA, FVEY", begins "WHILE TRANSITING TO TGT [redacted] PERFORMED SCANS ON THE GROUND WHILE ENROUTE TO SUPPORT" and then disappears under two fully redacted lines (page 8). So the one narrative passage about how the sighting unfolded is almost entirely withheld.

Oddly, the field "Number of UAP Sighted" is blank even though the description gives six.

What the UAP block says

The UAP section (pages 6-7) is where the report is most informative:

• Initial Contact DTG and UAP Date of DoD Acquisition: both 292022:32ZJUL25, to the second.
• UAP Maneuverability Observations: "SEEMED TO BE AGILE, FREQUENTLY CHNAGING DIRECTION" (sic).
• UAP Anomalous Characteristics/Behaviors: "ABLE TO CHANGE DIRECTIONS QUICKLY AND SIMULTANEOUSLY". The report does not spell out whether "simultaneously" means the six changed direction together.
• Kinetic estimates, all marked "Estimated": altitude FL220, velocity "48OMPH" (the typed letter O stands in for a zero), trajectory SE; depth "UNKNOWN".
• Friendly aircraft: trajectory NW, speed 120 KIAS (knots indicated airspeed); its location and altitude are redacted.
• Physical state: "Solid". Propulsion, intelligent control, RF frequency and duration, event serial number: "UNKNOWN". Advanced capabilities or materials: "NO".
• Response to observer actions: "NONE"; observer engagement and interrogation of UAP: "NO" (no sensor was used to query or engage the objects).
• Effects on persons: "NO"; on equipment: "NONE"; material recovered: "NO".
• Observer: "SSGT/E5" (staff sergeant), name redacted; a third-party observer is also redacted.

One field is hard to read: "UAP Reaction to Observation, Interrogation, Engagement: NONE. FOLLOWED OF OWN ACCORD UNTIL LIST. REPORTED AFTERWARDS". "LIST" may be a typing slip for "lost", but the report does not say, and it is unclear whether the objects or the crew did the following.

Taken at face value, the estimated headings put the objects (southeast) roughly opposite to the aircraft (northwest). The observer's own assessment and the UAP signatures field are redacted.

The PR135 video and the blurbs

The official description of PR135 (1 minute, infrared) is short: no content for four seconds; at 00:05-00:10 "several areas of contrast transit the sensor field-of-view, entering from the top of the frame and exiting from the bottom"; from 00:11 to 00:47 the sensor pans to keep them centered; the last 12 seconds show a magnification change and no content. That fits a group of objects but gives no count.

The official D108 blurb quotes the maneuver field as "seem[ingle] agile"; the PR135 blurb has "seem[ingly] agile". Both paraphrase the report's "SEEMED TO BE AGILE". The official blurb for DOW-UAP-D109 repeats this D108 description almost verbatim, although the D109 report describes something quite different (see that article).

Significance

D108 is the most detailed of the four MISREPs here: a count, a shape, a grouping, a speed, an altitude, a heading, and explicit negatives on effects, advanced capabilities and reaction. Its 480 mph estimate is close to D107's 500 mph, filed three months later on the same form, and both reports mark the object "Solid". Unlike the 2022 reports DOW-UAP-D106 and D109, which describe erratic, 1-2 meter objects at 80-180 mph with altitude undetermined, D108 commits to an altitude. Every kinetic figure, however, is flagged "Estimated", the observer's assessment is redacted, and the narrative account of the encounter is almost entirely withheld.

Key People

Locations

Incidents

Notable Quotes

"AT 292022:00ZJUL25 [redacted] OBSERVED AN UAP (SEE UAP 1)." -- page 1

"UAP Maneuverability Observations: SEEMED TO BE AGILE, FREQUENTLY CHNAGING DIRECTION" -- page 6

"Kinetic Altitude: FL220 ... Kinetic Velocity: 48OMPH ... Kinetic Trajectory: SE" -- page 7

"UAP Reaction to Observation, Interrogation, Engagement (yes/no; if yes, describe): NONE. FOLLOWED OF OWN ACCORD UNTIL LIST. REPORTED AFTERWARDS" -- page 7

"UAP Anomalous Characteristics/ Behaviors: ABLE TO CHANGE DIRECTIONS QUICKLY AND SIMULTANEOUSLY" -- page 7

"UAP Description (e.g., size, shape, color, markings, recognizable features): 6X SMALL SPHERICAL OBJECTS GROUPED TOGETHER" -- page 7

"WHILE TRANSITING TO TGT [redacted] PERFORMED SCANS ON THE GROUND WHILE ENROUTE TO SUPPORT [redacted]" -- pages 7-8