Multi-country (Middle East).Middle East 2025 · six spheres, a white orb and a new UAP module

On 29 July 2025, an MQ-9 from the 65th Special Operations Squadron — 1st Special Operations Wing, under AFSOC — took off at 17:34 Z over satellite link for a Central Command tasking inside Operation Inherent Resolve, against violent extremist organisations. At 20:22:32 Z, while transiting to its target and scanning the ground en route, the crew saw something. The report's description field sums it up in seven words: 'six small spherical objects grouped together'. Manoeuvrability was recorded as 'seemed to be agile, frequently changing direction', and the anomalous-characteristics field as 'able to change directions quickly and simultaneously'. The kinematics on record: altitude flight level 220, speed 480 miles per hour, trajectory southeast, all marked 'estimated'. The friendly aircraft was at 120 knots indicated, heading northwest. The weather was clear and did not affect the mission. The observation is signed by a staff sergeant, grade E-5.

Three months later, on 29 October 2025 at 01:41 Z, another crew — this one from the 11th Attack Squadron, 432nd Air Expeditionary Wing — saw something on its feed while over a target. The report tells it twice, in two different fields and in the same words: 'from 290141:00ZOCT2025 to 290150:00ZOCT25, [redacted] observed a UAP on feed while on TGT, [redacted] stated it looked like a white round orbit, tracked for [redacted], observed UAP moving as fast as 500MPH, and [redacted] lost UAP IVO [redacted]. There is no additional information to be provided at this time.' Nine minutes of tracking and a trail that goes cold. The friendly aircraft was at about 22,500 feet. The observer is an airman first class, grade E-3: the sensor operator. The mission was against smuggling, ISIS and the Iranian threat network.

What makes these two documents singular is not what they describe but the container that holds it. The May 2022 Iraqi report this corpus already catalogues (↗) filed an equivalent observation in the generic observation block, with the field 'observed activity description' settled in one word. Three years later, the same command and the same form carry a block headed 'UAP' with its own battery of fields. There are: UAP event type, manoeuvrability observations, UAP response to observer actions, physical state, number of UAP sighted, propulsion means, payload, 'UAP under intelligent control (yes/no; if yes, describe)', signatures, 'advanced capabilities and/or materials (yes/no; if yes, describe)', RF frequency and duration, event serial number, effects on persons, 'objects/material recovered (yes/no; if yes, describe)', effects on equipment, observer interrogation and engagement of the UAP, first and last coordinates each with a radius, kinetic altitude, depth, velocity and trajectory each with its own accuracy flag, date of DoD acquisition, UAP reaction to observation, and anomalous characteristics or behaviours.

The two reports fill it unevenly, and the difference is instructive. The October one settles seven boxes — UAP incident, 'fast moving speeds up to 500MPH', the friendly altitude, physical state 'solid', effects on persons 'no', a radius of five on first and last position, and DoD acquisition four minutes after contact — and leaves the five kinetic fields marked 'estimated' without a single number. The July one goes considerably further: propulsion 'unknown', under intelligent control 'unknown', advanced capabilities or materials 'no', RF frequency and duration 'unknown', effects on persons 'no', material recovered 'no', effects on equipment 'none', interrogation 'no', engagement 'no', and a reaction to observation that reads 'none. Followed of own accord until lost. Reported afterwards.' There the numbers do appear — flight level 220, 480 miles per hour, heading southeast — but all three carry the same mark as everything else: estimated.

That mark is not bureaucratic carelessness but an exact description of what the sensor can give. An MQ-9's electro-optical ball measures angles, not distances: without range there is no true size, no altitude and no real speed, only angular rate multiplied by an assumed distance. That is where the 480 and the 500 miles per hour come from, and why accuracy reads 'estimated' in all five fields. It is the same limitation that in the 2022 Iraqi report produced a 'we were unable to determine altitude' and the one that in the Colorado file turned a light into an object 'about 300 feet up'. The form, meanwhile, asks about propulsion means, about the object's radio frequency and about whether it was under intelligent control. The distance between those questions and that sensor is the real state of the reporting programme at the end of 2025.

It is worth separating what each report contributes. The October one describes a white round dot: any balloon, bird, distant aircraft or sensor artefact explains it without effort, and the speed depends entirely on a distance nobody measured. The July one is harder to dismiss: six spherical objects grouped together that change direction 'quickly and simultaneously' describe a formation, and a formation implies coordination. There the readings divide: a coordinated drone swarm is exactly the sort of thing that existed in that theatre in 2025 — though not at 480 miles per hour and not at 22,000 feet — and a flock seen against the sky in infrared also changes direction simultaneously, which is what a flock does. The file leaves both on the table and does not choose, because the document gives nothing to choose with: the video was not published and every figure is estimated.

Both documents arrived by the same route. The July one was SECRET//NOFORN with automatic declassification set for 29 July 2050; the October one, SECRET//NOFORN with a date of 28 October 2050. They were declassified by Major General Richard A. Harrison, Central Command's chief of staff — the July one on 10 July 2026, the October one on 8 June 2026 — between twenty-four and twenty-five years early. The redactions fall under the (b)(1)(B) national-defence exemption of the Freedom of Information Act and under personal privacy: callsigns, aircraft types and tail numbers, bases, coordinates, supported units and names all disappear. The structure survives, which is what matters here.

A form is a theory of what can be known. When the Department of Defense adds to the mission report a block with fields for propulsion means, radio frequency, intelligent control, advanced capabilities and recovered material, it is declaring which questions it considers legitimate to put to a crew about an unidentified object. That administrative act is more informative than most public statements on the subject: nobody designs a field for 'objects or material recovered' in a routine surveillance report unless they contemplate its one day being filled in. The file records it as what it is — the shape of the reporting system, not evidence about the phenomenon — but it records it.

The second reading is less flattering and also the more useful. The block exists and gets half filled, with 'unknown' wherever the question exceeds the instrument. The sergeant who wrote 'propulsion: unknown' could not have known otherwise about six dots several kilometres away; what he had was a camera that measures angles. That is why the kinetic fields read 'estimated' even when they carry a number, and why the 480 miles per hour is not a measurement but an angular rate multiplied by a distance nobody determined. The form grew; the sensor did not. While that asymmetry holds, the collection will keep filling with incidents that have many fields and little data, and the temptation to read the empty fields as mystery — rather than as insufficient instrumentation — will remain the easiest mistake to make with this archive.

There is an exception worth not flattening, and it is why this file does not sit as low as its neighbours. 'Six small spherical objects grouped together' that change direction 'quickly and simultaneously' is not the description of an ambiguous dot: it is a description of structure and coordinated behaviour, written by a non-commissioned officer on a classified form nobody expected to be published. The content remains compatible with mundane explanations — a flock does exactly that, and so does a drone swarm — but the shape of the report differs from that of an 'area of contrast' or a 'light'. When an official document supplies morphology, number and collective behaviour, it supplies something a later probe can test; when it supplies an estimated speed, it does not.

It is worth reading the three reports together, because the sixth release published them on the same day and they describe a curve. In 2022, over Iraq, two crews from different squadrons saw objects one to two metres across on the same day, wrote 'UAPs' in the prose, and the matter closed with a 'did not hinder the mission'. In 2023, on a Colorado highway, a police officer filmed a light with his phone and the declassification erased everything that would have allowed it to be checked. In 2025, over the Middle East, two crews pour what they see into a module designed for the phenomenon, which gets half filled. Three points on one institutional trajectory: first there was nowhere to record it, then there was somewhere but nothing to put there, and in every case the bottleneck was the same — nobody could measure the distance to the object. That is the technical problem the programme would have to solve before any other, and no form solves it.