The Department of War’s release of a 2013 Middle East UAP report this week does not close a case. It opens a file drawer. The document, declassified under the PURSUE policy framework and processed by the All-domain Anomaly Resolution Office, describes a single encounter that lasted 90 seconds.
In that brief window, a sensor on an unspecified military aircraft tracked an object that accelerated rapidly and held high speed without any visible means of propulsion. No communications or electronic emissions came from it.
The report classifies the incident as “unresolved.” That word matters. It means the U.S. government looked at the data and could not match it to anything known — not a foreign jet, not a drone, not a weather balloon, not a sensor glitch. The object simply came, performed, and left.
The report is part of a series labeled PR38. The Department of War has not said how many reports are in that series.
It has not said whether similar objects appeared in the same region on other days. It has not identified the aircraft that carried the sensor. The lack of disclosure is itself a disclosure: there is more the department is not saying.
What is at stake here is not just a curious footnote from a decade ago. It is the credibility of a transparency policy that is supposed to inform the public about encounters military personnel have with things they cannot explain. The PURSUE framework was built to declassify historical UAP reports that do not compromise national security.
This release meets that standard. But it also demonstrates how thin that standard can be.
No adversary was blamed. No natural phenomenon was cited. No conclusion was reached.
The report does not even name the sensor platform. That means a routine mission in a volatile region was interrupted by an object that outperformed American military hardware, and the public gets a 90-second window and a filename.
The report’s filename — “dow-uap-pr38-unresolved-uap-report-middle-east-2013” — suggests it is one of many. The department has not released the others. It has not said how many PR38 documents exist.
It has not explained why this one was chosen for declassification now, or what criteria govern the release of the rest. For the military personnel who saw it, or whose sensors tracked it, the encounter is still unresolved. For the analysts at AARO who reviewed the file years later, it remains unresolved.
For the public, the resolution is not a conclusion. It is a promise that more documents exist, that more encounters happened, and that the government is still deciding which ones to show and which ones to hold back.
The 2013 incident happened during a routine operation. That is a crucial detail. It means the object was not responding to a test or a drill.
It appeared in the middle of ordinary military business. That is the kind of encounter that worries pilots and intelligence officers most — not the one that shows up for a scheduled exercise, but the one that arrives unannounced, performs beyond known limits, and disappears without a trace.
The Department of War has committed to transparency. This report is proof of that commitment. It is also proof of its limits.
The public now knows that something flew in the Middle East in 2013, that it flew better than anything the U.S. military has openly acknowledged, and that the government has no explanation for it. What remains unknown is how many times that has happened, and whether it is still happening now.
