The Marine Corps’ UAP Reporting Policy
A policy document is not a sighting report, and that distinction is the whole story here. The U.S. Marine Corps has released a procedure for passing Unidentified Anomalous Phenomena (UAP) information to the Pentagon’s All-domain Anomaly Resolution Office (AARO). What follows is an account of a bureaucratic mechanism, not of anything anyone claims to have seen.
A Request and a Release
The paper trail begins with a request. John Greenewald Jr., who runs the FOIA research site The Black Vault, filed a Freedom of Information Act (FOIA) request on April 14, 2024, seeking any Navy or Marine Corps policy, procedure, memorandum, or agreement governing how those services share UAP information with AARO, including anything carried over from the earlier UAP Task Force or the Airborne Object Identification and Management Synchronization Group (AOIMSG). The Marine Corps answered on July 25, 2024, roughly three months later, releasing a policy document dated December 8, 2023. That date had sat unseen for about eight months before the public got it. A related record moved on its own track: researcher Douglas Dean Johnson separately obtained a Joint Chiefs of Staff directive dated May 2023, released to him in March 2024. The two documents surfaced about four months apart, pulled loose by two different requesters through two separate FOIA channels.
What the Policy Actually Orders
The operative language is specific. Any UAP event, the document states, triggers an OPREP-3 Special Incident Report, a format the U.S. military uses to give immediate notice of an incident serious enough to draw national-level attention or touch on national security. The trigger is not whether the event affected a mission. It applies regardless of that. The policy sets a standard template for the report itself, and a separate template for transferring any data or physical material recovered. It also assigns a specific notification duty: the Marine Corps Operations Center (MCOC) is to alert the service’s counterintelligence element, housed within the Deputy Commandant for Information, whenever a UAP-related event occurs.
Whose Job This Becomes
Responsibility is spread rather than centralized. Combatant commands and individual services are each handed explicit duties for reporting incidents and moving data and material up the chain to AARO. The comparison to the Joint Chiefs directive matters here. The May 2023 Joint Staff message Johnson obtained sets specific clocks on parts of this process: UAP incident reports within 96 hours, reports of a “UAP engagement,” meaning a kinetic or non-kinetic response meant to deny, disrupt, or destroy the object, within 12 hours, and recovered material transferred within 30 days of coordinating with AARO. The Marine Corps document reiterates the combatant command and service reporting duties from that framework and adds guidance specific to how the Marine Corps carries them out. It tailors an existing skeleton. It does not build a new one.
What This Document Is Not About
Nothing in the released file describes an actual sighting. No witness is named. No aerial phenomenon is described, let alone explained. There is no incident attached to this policy, no photograph, no video, no narrative account of anything observed. The document is procedural from its first line to its last, and it was released and read as exactly that.
The Explanation That Isn’t Needed Here
There is no ordinary explanation to weigh against an extraordinary one, because there is no sighting on the table to explain. The mundane reading applies to the document itself: this is a compliance and reporting protocol, the kind of paperwork any large organization produces once it has been told to start keeping records of something. The dull, structural reason for its existence sits right in the text: it standardizes intake, so a unit encountering a UAP event knows which office to notify, on which form, and within what window. Nothing in the record supports reading a hidden motive into that.
The Three Things Not in the File
Three gaps remain on the record’s own terms. The document does not include or reference any incident reports, photographs, or video, only the reporting framework itself. It is unclear whether earlier UAP Task Force or AOIMSG procedures were formally folded into this policy or simply continue running alongside it; The Black Vault’s FOIA request asked that exact question, and the released document does not answer it. And the document states only when it was signed, December 8, 2023, not how long the framework it describes has actually been operating.
What The Black Vault Says It’s Doing Next
The Black Vault states that it is pursuing comparable FOIA requests aimed at nearly every military branch and agency that interacts with AARO. Some of those requests have already come back with a “no records” response. Others are still being processed. That is a description of effort underway, not a documented result, and no additional released files accompany this one.
Reading the Paperwork for What It Is
Ask someone to summarize a document like this one, and most people will call it “the Marine Corps UFO file” before the sentence is finished. It isn’t one. What was actually released governs who reports what, on which form, to whom, and within what window of time. That is a different story, not a smaller one, and mistaking a reporting procedure for evidence of a phenomenon rather than evidence of a process is the error this whole case exists to resist. The gaps named above haven’t been filled. Nothing in the record says they need to be yet.