UAP Overclassification: The Pentagon Approved the Day and Month — But the Year Was Classified
A heavily redacted email exchange from October 2024 captures the precise moment the military classification apparatus collided with basic chronology: an Information Disclosure Analyst had to formally request permission to release the year a UAP sighting took place, noting that only the day and month had been cleared for public release (90570293e61c9b22). This administrative correspondence, while seemingly mundane, exposes the profound friction of UAP overclassification and demonstrates how the internal machinery of the Pentagon processes anomalous events.
While public attention naturally gravitates toward sensor data and pilot testimonies, the administrative emails generated by the Department of Defense offer the most honest history of the post-AARO intelligence system. By examining how the bureaucracy argues over redactions, researchers can better separate the genuine operational mysteries from artifacts of the classification process.
The October 2024 SECRET//NOFORN Email
The correspondence that best illustrates this bureaucratic bottleneck occurred on October 31, 2024. A PAROC Intel Data Analysis Technician provided an unclassified "tearline"—a brief summary designed to be separated from a highly classified parent document—regarding a UAP incident.
In response, an Information Disclosure Analyst replied with a request that highlights the granular nature of military secrecy: "Could you please approve the use of the year this incident took place? Currently you have approved the month and the day, we request it includes the year" (90570293e61c9b22). The fact that the release of a calendar year required formal negotiation demonstrates a default posture of absolute secrecy, where even the most basic temporal metadata is treated as a potential vulnerability.
The Two-Hour Sighting Buried in the Bureaucracy
What makes the debate over the calendar year particularly striking is the actual content of the sighting being discussed. Almost forgotten in the administrative back-and-forth is a description of an extraordinary aviation encounter.
Once the tearline was approved, it read: "U.S Aircraft observed a possible UAP. It appeared to be oval/orb shaped, likely moving at a low speed. The U.S Aircraft had eyes on the poss UAP for over 2 hours" (90570293e61c9b22). In the context of military aviation, maintaining visual contact with an unidentified object for over two hours is a highly significant event, requiring sustained fuel management and airspace coordination. Yet, in the archival record, this remarkable operational detail is treated as secondary to the procedural hurdle of declassifying the year it happened.
Negotiating Tearlines at the Highest Levels
This friction is not isolated to a single Air Force unit. Documents from April 2025 show the Office of the Undersecretary of Defense for Intelligence and Security (OUSD(I&S)) directly involved in negotiating single-sentence tearlines for the INDOPACOM area of responsibility.
The emails show analysts confirming that basic descriptions of brief encounters can be considered unclassified. One approved tearline reads: "US AIRCRAFT OBSERVED 1X POSS UAP FOR 12 SECONDS AT 2353Z, FLYING AT UNK ALTITUDE AND UNK SPEED, NO INTERFERENCE WAS NOTED" (10c11e9bf4d66861). Another confirms a similar 23-second sighting. The correspondence reveals that simply stating the acronym "INDOPACOM" alongside these brief descriptions required explicit, documented approval from higher authorities. The sheer weight of the bureaucracy required to approve two sentences of basic observational data illustrates the systemic hurdles facing transparency efforts.
AFOSI Improvising the Declassification Process
The internal confusion over how to handle UAP data is explicitly admitted in a March 2023 exchange involving the Air Force Office of Special Investigations (AFOSI). The case involved a civilian who reported a large, blue, featureless triangular object hovering near a national security facility in the Pacific Time Zone. The object reportedly emitted a "whitish blue" light and moved in a "jerking" or "jumping" manner inconsistent with smooth jet propulsion (f21f4ae91e51810b).
The report explicitly notes that the data was "Obtained by: Personal cellular device" and that the reporter was a civilian. Despite the civilian origin of the footage, the internal correspondence was stamped SECRET//NOFORN.
When tasked with clearing a summary of the event, an OSI CI Collections and Operations Program Manager admitted in writing that the system was entirely unprepared for the request. "Our process for declassifying IIRs is lengthy and requires AFOSI Commander signature so I'm exploring options akin to a security review of the UNCLASS summary you have provided below," the manager wrote, adding, "This is a first for me so I appreciate your patience as I try to streamline this request for you!" (f21f4ae91e51810b).
Later in the chain, the manager confirms that headquarters granted them the authority to process the request as a "derivative classification review" rather than a formal declassification request. This exchange proves that the military's UAP disclosure apparatus is often improvising its own rules in real-time.
The Extremes of the Redaction Process
When the bureaucracy cannot figure out how to declassify information, it defaults to extreme redaction. The archive contains numerous examples where the physical structure of the documents breaks down under the weight of secrecy.
In one DoD UAP Report detailing an object moving at 40 knots between FL160 and FL170, the first four pages of the six-page document are 99% redacted. The pages show nothing but black boxes and the red text "1.4(a)", an exemption code indicating that the withheld information concerns military plans, weapons systems, or operations (af150a6b5139abc6).
An even more glaring structural anomaly appears in a separate DoD/IC UAP Report. The document describes a UAP observed at 1258Z with an estimated velocity of 321 knots that subsequently increased speed and changed direction toward the east. The PDF file contains exactly five pages. However, the final page containing the sighting description is clearly numbered "6" at the bottom (857deb5a9363aad6). A page has been entirely excised from the record before the PDF was assembled, leaving a silent gap in the archival sequence.
Recalibrating the Mystery
Understanding this meta-content is essential for anyone researching the UAP Archives. A significant portion of the "mystery" surrounding military UAP encounters is actually an artifact of the classification process. When a document is heavily redacted, it does not necessarily mean it contains paradigm-shifting truths; it often means the document intersected with a rigid, risk-averse bureaucracy that requires formal approval to release a calendar year or a civilian's cell phone video.
However, learning to read the redactions also recalibrates our understanding of what is truly anomalous. When we recognize the routine administrative friction that causes standard delays and (b)(6) privacy redactions, the redactions that cannot be explained by routine bureaucracy become much more glaring. The missing pages, the 1.4(a) national security exemptions applied to visual descriptions, and the two-hour aviation encounters buried in email chains point to the core data that the system is actively working to protect. By understanding the machine, researchers are better equipped to identify the true anomalies hidden within it.
What the document does not say
To maintain strict archival accuracy, it is necessary to outline what these administrative documents do not contain:
- The documents do not identify the nature, origin, or operators of the oval/orb, the blue triangular object, or the high-speed UAPs.
- The correspondence does not explain why the calendar year of the two-hour sighting was initially classified, only that permission was required to release it.
- The AFOSI emails do not contain the actual civilian cellular video of the blue triangular object, nor do they confirm the specific national security facility it was hovering near.
- The documents do not explain the contents of the missing page that causes a five-page PDF to end on page six.
Read it yourself
Explore the source documents directly through the links below:
