THE SOURCE
DOW-UAP-D25, D28, D55, D74 and D75, five mission reports from the U.S. Department of War’s PURSUE Release 01, published at war.gov/ufo on 8 May 2026. All five were filed by U.S. Central Command and contain the structured “UAP Event Report” form embedded in each MISREP. D25 covers 25 January 2024: the release files it under Greece, and its catalogue row gives the incident location as the Mediterranean Sea. D28 covers Iraq, 20-21 September 2024. D55 covers Syria, November 2016. D74 covers Syria, 9 November 2023. D75 covers the Gulf of Aden, 14 July 2024.
What this briefing is
Release 01 Briefing 7 read a single Central Command mission report, the F-15E over Syria. Release 01 Briefing 20 read a batch of them as a pattern. Between those two, five mission reports went unbriefed individually: D25, D28, D55, D74 and D75. They are not duplicates of anything in the earlier briefings, and four of them carry the same structured form, the standardised UAP Event Report fields that the military fills in for these incidents.
This briefing closes the document tail of the CENTCOM mission-report set by reading the five together, both for the encounters they describe and for the form they share. The general grounding for reading PURSUE primary documents is in Release 01 Briefing 1.
TL;DR
The five mission reports are dated, in order, November 2016 (Syria), January 2024 (the eastern Mediterranean), November 2023 (Syria), July 2024 (Gulf of Aden) and September 2024 (Iraq). All five were filed by U.S. Central Command. Four of them, D25, D28, D74 and D75, are born-digital documents that contain the same structured “UAP Event Report” template with named fields for event type, physical state, signatures, manoeuvrability observations, anomalous characteristics, description, propulsion, payload, and several others. D55, the 2016 Syria report, is older and shorter and contains a “possible missile launch” line that earlier readers would already recognise as the conventional candidate the aircrew themselves named.
Inside the forms, four distinct encounters stand out. D25’s UAP was a round, diamond-shaped object with a straight “tail”, flying at approximately 434 knots in January 2024 over the eastern Mediterranean, which the release files under Greece and its catalogue row places in the Mediterranean Sea. Its description matches the PR28 clip covered in Release 01 Briefing 5, but reading the two as one event is this site’s inference: the catalogue pairs PR28 with a different report, D7. In D28, over Iraq, the crew saw an unidentified object “fly” through the aircraft’s sensors at high speed just after an AGM-176 was released, recorded an IR lens flare it created on the sensors, and left open whether an object detached from the primary UAP before it left the field of view. D74’s aircrew described a probable high-confidence UAP “shaped as a bouncy ball” over Syria, which dropped altitude and passed their aircraft at a steady speed of about 424 knots before moving out of range after seven minutes of watching. D75 records a Gulf of Aden encounter in which the UAP, on a straight flight path at the same altitude, was faster than the observing aircraft could keep up with.
Taken together: these are tier 2 primary documents, the same source class as every other CENTCOM mission report in the release. Each contains specific, falsifiable aircrew observations rather than vague impressions. Each described behaviour fits one or more ordinary candidates in the same theatre and era. The form itself, the standardised UAP Event Report, is the institutional feature the cluster surfaces most clearly.
The standardised UAP Event Report
Open any of the four 2023-2024 mission reports here and the same form appears inside the MISREP. It has named, structured fields: UAP Event Type, UAP Physical State, UAP Signatures, UAP Maneuverability Observations, UAP Anomalous Characteristics and Behaviors, UAP Description, UAP Propulsion Means, UAP Payload, UAP Under Intelligent Control, UAP RF Frequency, UAP RF Duration, UAP Effects on Persons, UAP Effects on Equipment, UAP Reaction to Observation Interrogation or Engagement, UAP Objects or Material Recovered, UAP Date of DoD Acquisition, and others.
This is the same kind of finding Release 01 Briefing 9 made about the Range Fouler debrief form: a standardised intake template, with predefined fields the aircrew are required to fill in, is itself a statement that the military treats these encounters as a recurring, expected category that needs structured paperwork rather than free-text notes. The fields are not exotic. The form asks whether the UAP was “Benign”, what its “Physical State” was, whether it appeared to be “Under Intelligent Control”, whether it had any effect on persons or equipment, and whether material was recovered. Each field is a small, routine question. Across the four reports, the answers cluster heavily towards “Benign”, “Solid”, “Unknown” and “No”.
That is itself a result. A standardised UAP form, filled out by aircrew across multiple incidents, that consistently produces “Benign” classifications and “No” answers to the more striking questions, is the bureaucratic shape of a phenomenon that the people closest to it are not, at the form level, treating as a threat or as an extraordinary event.
D25, and what pairs with PR28
D25 records an encounter on 25 January 2024 over the eastern Mediterranean. The war.gov file is named for Greece, and the aircraft took off from and landed back at a Greek airfield, the form giving the ICAO code LGLR for both. The sighting itself came four hours into the sortie, while the aircraft was in transit, and the form’s own grid squares put it out over open water: the aircraft in 35S QT, the UAP first seen in the same square and last seen one square west in 35S PT, which puts the sighting at roughly 34 degrees north and 29 degrees east, in the stretch of sea between Crete, Cyprus and the Egyptian coast. The release catalogue’s row for the file gives the incident location as the Mediterranean Sea. The form’s description field reads “ROUND DIAMOND SHAPE WITH STRAIGHT, NON MANUEVERABLE ‘TAIL’”, and the event narrative describes it as “DIAMOND IN SHAPE WITH A NON-MANUEVERING PROBE AT THE BOTTOM”. The signature is Short Wave Infrared in white, and the narrative adds that “THE UAP ONLY APPEARED ON THE SWIR CAMERA”. The object was flying at approximately 434 knots, and the anomalous-characteristics field reads “MAINTAINED STEADY FLIGHT PATH, INCREASED AND DECREASED ALTITUDE PROFILE, DID NOT CHANGE TRAJECTORY”. The event lasted about two minutes and was classified “Benign”, with the UAP physically “Solid”.
PR28, the clip covered in Release 01 Briefing 5, is tagged Greece, January 2024, and its catalogue entry says an accompanying mission report described the UAP as “diamond-shaped”, moving at approximately 434 knots and detectable only on a short-wave infrared sensor. That is D25’s wording, line for line. The accompanying report the catalogue actually names is a different file, DOW-UAP-D7, a 2020 Arabian Gulf report about an object that “look[ed] like a balloon”. So reading D25 as the written half of PR28 is this site’s inference from the date, the theatre and the matching description, not the catalogue’s pairing. Read that way, the speed (434 knots, roughly 500 mph) and the SWIR-white signature put numbers and a sensor band against the visual track.
Four hundred and thirty-four knots is fast for a small drone but well within the cruise envelope of a small jet or a cruise missile. The “diamond” shape is consistent with the appearance of a small fixed-wing UAV or a kite-shaped balloon viewed end-on. Steady flight path at that speed is not the behaviour of a balloon. The combination, fast, diamond, steady, white-hot in SWIR, is consistent with a small jet-propelled drone or cruise missile in the same kind of theatre. The same form also records the straight tail or probe and an altitude that rose and fell.
D28, a fly-through of the sensor view
D28 covers an encounter on 20-21 September 2024 in Iraq. The document names the location: the event narrative has the aircraft entering “AYN AL ASAD AIRBASE’s (AAAB) RESTRICTED OPERATING ZONE (ROZ) RAINDROP” to “CONDUCT A WEAPONS CALIBRATION”. The crew then “RECEIVED A CALL FOR FIRE AT APPROXIMATELY 2025Z TO EMPLOY AN AGM-176”, and the manoeuvrability field ties the sighting to that shot: “UAP FLEW THROUGH [redacted] SENSOR IN BETWEEN MUNITION RELEASE AND MUNITION IMPACT”. The form adds that the UAP “MOVED AT A HIGH RATE OF SPEED THROUGH THE SENSOR FIELD OF VIEW”, that its IR signature was “DETECTABLE BY MX-20 & MX-25”, and that it “CREATED AN IR LENS FLARE ON THE MX-20 & MX-25 SENSORS, WHICH INDICATED A SIGNIFICANT HEAT SIGNATURE COMING FROM THE OBJECT”.
The event narrative gives the sighting in one sentence: “AFTER WEAPONS RELEASE, THE WEAPONS SYSTEMS OFFICER (WSO) AND COMBAT SYSTEMS OFFICER (CSO) OBSERVED AN UNIDENTIFIED OBJECT ‘FLY’ THROUGH THE AIRCRAFT SENSORS AT A HIGH RATE OF SPEED”. The passage it describes is through the sensors, and the uncertainty the report records concerns something else: “IT IS UNKNOWN AT THIS TIME WHETHER AN OBJECT DETACHED ITSELF FROM THE PRIMARY UAP IMMEDIATELY BEFORE LEAVING THE SENSOR FIELD OF VIEW”. The crew “MAINTAINED LASER ENERGY UNTIL THE MUNITION IMPACTED ITS DESIRED TARGET” and did not observe the UAP again. Lines like these, recorded in the aircrew’s own words, are much more useful than any later analyst’s summary. The IR lens flare detail is honest about the sensor’s own contribution to the captured image, and a reader of Release 01 Briefing 3’s lens-flare section will recognise the pattern.
D74, “shaped as a bouncy ball”
D74 covers a 9 November 2023 encounter in Syria. The aircrew describe a probable high-confidence UAP “SHAPED AS A BOUNCY BALL” that came “FROM THE SOUTH AT NEAR CO-ALT”, and record that they “OBSERVED THE PROB UAP DROP ALTITUDE AND SAFELY PASS THEIR AIRCRAFT WHILE CONSISTANTLY MAINTAINING ~424KN”. After seven minutes of watching, the object “BECAME OUT OF RANGE”. The form’s advanced-capabilities field repeats the figures, “YES, TRAVELED ~424KN CONSISTANTLY FOR AT LEAST 7MINS IN THE SHAPE OF A BOUNCY BALL”, and the kinetic velocity is logged as an estimated 424 knots. The report classes the UAP as Benign and Solid. Separately, the same report notes the aircrew observed a “WHITE SUV” on the ground, an unrelated ground observation that the same mission picked up.
“Bouncy ball” is an unusually specific shape word: small, spherical, bright. It fits the same family of spherical clips that the rest of Release 02 worked through in Release 02 Briefing 19, and the same candidates apply, balloon, small drone, and so on. The descending behaviour is consistent with a balloon losing buoyancy or a drone in deliberate descent. The report logs the object’s speed through that descent as a constant 424 knots or so, estimated, and says it held that speed for at least seven minutes. None of this is extraordinary; the value of the report is in the aircrew’s exact wording at the time.
D75, an object faster than the aircraft
D75 covers a 14 July 2024 encounter in the Gulf of Aden, coordinated with NAVCENT and AFCENT. The form records a straight flight path at the same altitude as the observing aircraft and an anomalous note that the UAP’s speed was faster than the aircraft could match. The crew followed it “TILL THE DISTANCE BECAME TOO FAR TO FOLLOW”.
The U.S. military aircraft tracking objects in the Gulf of Aden range across many platforms, including slow surveillance aircraft and helicopters. Speed relative to a P-8 maritime patrol aircraft in level flight differs from speed relative to a slower platform. Without the observing platform identified, “faster than the aircraft” is a relative figure. The report itself records the observation and stops there, as the form requires.
D55, the older one
D55 stands apart from the other four. It dates from November 2016, the oldest mission report in this set, and is shorter and lighter on structured form content. The relevant line is brief: an “UNIDENTIFIED LOW-FLYING OBJECT” at 55 nautical miles, described as a “possible missile launch from an origin unknown” detected via a sensor identifier that is now redacted.
A “possible missile” classification, in the same vein as Release 01 Briefing 22’s short-clip aircrew descriptions, is the aircrew’s own first-pass conventional candidate. D55 is the oldest mission report in the released set and reads accordingly: a brief, contemporaneous candidate identification, not an exotic claim.
What the file says
They establish that U.S. Central Command logged five additional unidentified-object encounters across 2016 to 2024 in Syria, the eastern Mediterranean, Iraq and the Gulf of Aden, that each was filed through the proper chain, and that four of the five carry the structured UAP Event Report form with named fields for the encounter’s characteristics. They establish, in D25, a January 2024 eastern Mediterranean encounter whose description matches the clip PR28 shows, on a date and in a theatre that fit, although the catalogue pairs PR28 with another report. They establish in D28 an unidentified object that the crew saw “fly” through the aircraft’s sensors between an AGM-176’s release and its impact, an IR lens flare on the sensors, and an open question over whether an object detached from the primary UAP; and in D74 a spherical “bouncy ball” UAP that the aircrew watched drop altitude and pass their aircraft at a logged 424 knots or so, held for at least seven minutes. They establish, across all four 2023-2024 reports, that aircrew consistently classified these UAPs as “Benign” and “Solid” within the form’s own categories.
What the file does not say
It does not establish that any of the objects were anomalous. The aircrew’s own classifications cluster on “Benign”, and the described behaviours fit ordinary candidates in each theatre.
It does not, on its own, identify any object. The reports record observations and classifications, not closed conclusions.
It does not lift the form from “infrastructure” to “discovery”. The standardised UAP Event Report shows the military processes these encounters routinely; it does not make any individual encounter remarkable.
And it does not rise above tier 2. The five reports finish the unbriefed CENTCOM mission-report set with the same evidentiary weight, and the same honest limits, as the rest of the cluster.
What to watch
The UAP Event Report’s fields, Physical State, Under Intelligent Control, Effects on Equipment, Objects or Material Recovered, are the same questions on every mission report; across the four 2023 to 2024 reports the answers cluster on Benign, Solid, Unknown and No. D25 and PR28 describe the same object in the same words, which is the reason for reading them side by side here; the catalogue’s own pairing points elsewhere.
Read the file. Decide for yourself.
References and further reading
- DOW-UAP-D25, D28, D55, D74 and D75, PURSUE Release 01, U.S. Department of War, hosted at war.gov/ufo
- Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
- AARO UAP Records, All-domain Anomaly Resolution Office, www.aaro.mil/UAP-Records
- Signals from the Periphery, Release 01 Briefing 5, on PR28 and what the catalogue pairs it with; Release 01 Briefing 7, on reading a single mission report; Release 01 Briefing 9, on the standardised Range Fouler form; Release 01 Briefing 20, on reading the CENTCOM mission reports as a batch; Release 01 Briefing 22, on aircrew candidate identifications in the short-clip reports