THE DOCUMENT
(Unchanged: a cluster of US Central Command mission reports (MISREPs) in PURSUE Release 01, drawn from a single reconnaissance squadron flying a run of long-endurance missions over the Arabian Gulf, the Strait of Hormuz and the Mediterranean across 2020. Each report is a structured form, originally classified Secret with a 2045 declassification date, and each contains a routine logged observation of one or more UAP. This briefing reads several together, including the Persian Gulf and Strait of Hormuz reports of August and October 2020 and a Mediterranean report. Released in PURSUE Release 01, hosted at war.gov.)
Why this one is worth your time
Briefing 7 took a single military mission report, the F-15E report from Syria, and read it end to end as a worked example of the standard format. Briefing 9 did the same for the Navy’s Range Fouler intrusion form. This briefing does something the others have not: it reads the mission reports as a body, a cluster of them at once, because the mission reports are the bulk of PURSUE Release 01, and what a cluster shows that a single document cannot is the pattern. And the pattern is quiet. In report after report, the UAP is present, and the UAP is almost nothing: a single coded line, a time, a grid reference, a method, and the words “no impact to the mission”. This is the twenty-mark of the series, and it is worth one briefing on what that line does and does not hold.
What the file says
The reports in this cluster were filed by a single US Air Force reconnaissance squadron flying uncrewed, long-endurance missions, the kind that stay airborne for around twenty hours, out of a base in Kuwait. Their job in 2020 was to support US naval forces by watching Iranian vessels and activity in the Gulf. Each mission produced a MISREP, a mission report: a long structured form of dozens of fields covering call signs, timings, sensors, weather, radio calls and observations. Inside that form, a UAP appears as one observation among others.
What the form is for. A MISREP exists to account for a mission: which aircraft, which sensors, which hours on station, what was tasked, what was seen, whether anything affected the tasking. It is an accountability and intelligence-collection document, not a UAP investigation form. When a UAP appears in it, the UAP appears the way everything else does, as a field to be filled, briefly, in the unit’s reporting shorthand, and then the form moves on to fuel and weather.
Who, or what, is the witness. These were uncrewed aircraft. The observation was made through a sensor, full-motion video, and the video was exploited afterward by a ground station, a separate analytical unit. So a UAP entry in one of these reports means a sensor recorded something and an analyst flagged it. There is, in principle, video. The MISREP is the paperwork that points at the video; it is not the video, and it is not the analysis of the video.
The August 2020 Persian Gulf report. The aircraft flew a twenty-hour reconnaissance mission supporting naval forces in the Arabian Gulf. Buried in the observation section is the UAP: at a specific time, the aircraft “observed 1X UAP” in the vicinity of a grid reference, the observed activity logged as “transitting”, the method logged as full-motion video, the consequence logged as “no impact”. That is the whole of it. The same report devotes far more words to a single routine radio challenge from Iranian air defence, logged with its own time, location, heading, altitude and a note that the exchange was “professional”.
The October 2020 Strait of Hormuz report. This one shows the UAP in company. That mission logged five separate radio challenges from Iranian air defence, an unidentified aircraft on the runway at an island airfield, and one UAP. The report does not leave the aircraft unidentified: it records that the aircraft was first seen as unidentified and was then “assessed to be an ATR 72”, a common turboprop airliner. The UAP, on the same mission, gets the bare line and no resolution.
The Mediterranean report. This is the high-water mark for detail in the readable cluster. Its UAP entry adds a shape and a material: the object is described as “triangular and metallic”. It also records that the observation was made while the aircraft was transiting at altitude, and gives the aircraft’s own height and speed at the time. Two adjectives and a position. That is the most a UAP entry in this cluster ever says.
What the cluster is, as a body. It is not a special UAP file assembled by someone who decided these incidents mattered. It is a slice of ordinary 2020 reconnaissance reporting, classified Secret as routine for that traffic, later run through declassification review and routed to the Pentagon’s anomaly-resolution office and then into PURSUE. The reports are in the release because they contain the keyword and the coded field, the same mechanism Briefings 10 and 11 described. Across this cluster, a sensor recording an object that an analyst could not identify, on a tasked mission in contested airspace, happened repeatedly, mission after mission, in the same squadron, in the same months.
What the file does not say
It does not say what the observed objects were. The reports give, at most, a position and in one case two adjectives. They contain no kinematic data on the objects, no size, no assessed identity, and no resolution.
It does not say that the flat language conceals anything, in either direction. Everything in a MISREP is logged in the same terse register, the radio calls, the vessel sightings, the weather, the fuel. The “no impact to the mission” answers the form’s own question, whether the tasking was affected; it is not a statement about the object.
It does not contain the sensor data itself. The actual full-motion video and its exploitation by the ground stations are not in this cluster. The reports point at that material; they do not reproduce it.
From the record
“Observed 1X UAP” in the vicinity of a grid reference, activity “transitting”, method full-motion video, “no impact”. The August 2020 Persian Gulf report, in full
“Assessed to be an ATR 72.” The October 2020 Strait of Hormuz report, resolving the unidentified aircraft on the runway
“Triangular and metallic.” The Mediterranean report, the most descriptive UAP entry in the readable cluster
Where the case connects
Briefing 7 read a single military mission report field by field, and Briefing 9 did the same for the Range Fouler form; set beside them, this cluster shows the same standard format carrying a UAP entry repeatedly across one squadron’s 2020 traffic. Briefing 12 set out how a document that reaches a public release can be structurally thin, and these reports are thin in the same way: a logging line was never built to carry an investigation. Briefings 10 and 11 cover the keyword-and-coded-field mechanism that put the cluster into the release. Briefing 1 covers PURSUE Release 01 as a whole and the tier system.
The file also leaves its own loose ends. Each MISREP points at full-motion video and at a ground station’s exploitation of it, and neither the video nor the exploitation is in this cluster. The richest entry stops at “triangular and metallic”. Any later tranche that releases the underlying sensor data or the ground-station analysis for these missions lands in this series when it does.
Read it yourself
The mission reports in this cluster, including the August and October 2020 Persian Gulf and Strait of Hormuz reports and the Mediterranean report, are hosted at war.gov in PURSUE Release 01.
Read the file. Decide for yourself.
Related wiki entries
The wiki entries below give background on the programme and the publisher behind this briefing.
References and further reading
- Primary documents: US Central Command mission reports (MISREPs), 2020 reconnaissance missions over the Arabian Gulf, Strait of Hormuz and Mediterranean Sea, PURSUE Release 01, hosted at war.gov
- Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
- Briefing 7 in this series, on a single military mission report read field by field
- Briefing 9 in this series, on the Range Fouler form and standardised reporting
- Briefing 12 in this series, on how the document that reaches a public release can be structurally thin
- Briefing 1 in this series, on PURSUE Release 01 as a whole and the evidence tier system