What this disclosure says.

The oldest layer of the May 8 release is also the most procedurally important. The FBI's contribution to the war.gov UFO portal is a single headquarters case file, designation 62-HQ-83894, opened in June 1947 and active into July 1968. The release presents the file in two physical groupings: ten sequential sections, each running roughly one hundred eighty to two hundred pages, plus six numbered serials of supporting correspondence and field-office traffic. [65_HS1-834228961_62-HQ-83894_Section_1 p.1] The classification stem, 62, is the Espionage-and-Internal-Security file series. The HQ prefix locates the file at FBI Headquarters in Washington rather than at any single field office. The combination matters more than it sounds. A headquarters file in the 62 series is not the way the bureau filed an opportunistic curiosity. It is the way the bureau filed something it considered a sustained counterintelligence concern.

Twenty-one years is the second procedurally significant fact. Most FBI case files close inside months, not decades. A file that runs from the year of the Kenneth Arnold sighting through the end of Project Blue Book and then beyond it is a file kept open across nine attorneys general and four directors. The release notes that the version posted to war.gov supersedes the partially redacted copy on the FBI Vault and contains several pages newly declassified for the May 2026 release with only minor remaining redactions. [65_HS1-834228961_62-HQ-83894_Serial_449 p.1] That makes the 2026 cut materially more complete than the version that had been available to public researchers since the early 2010s.

The file's content is denser than the typical UAP-history shorthand suggests. The bureau is not running its own field investigations against discs. It is running a sustained intake operation against the civilian researchers who are. The pages catalog correspondence with John Edgar Hoover's office from APRO, NICAP, and a series of named individual UFO authors and lecturers. The file logs FBI field-office monitoring of organized meetings, conventions, and lectures, and it routes incoming public letters about specific sightings into Hoover-routed memoranda that go up the bureau's standard counterintelligence chain. [65_HS1-834228961_62-HQ-83894_Section_2 p.1] The file's posture is recognizable to anyone who has read a 62-series case file on any other topic: respectful, careful, internally distrustful of the people writing in, and unfailingly bureaucratic.

The early sections are the most evidentiarily exposed. Section 1 covers the immediate post-1947 wave and the bureau's earliest formal exchanges with the Army Air Forces over the disc reports. Section 10, the last formal section, covers late-1966 through 1968 and is dominated by FBI monitoring of civilian groups during the Condon Study era. [65_HS1-834228961_62-HQ-83894_Section_10 p.1] In between, the sections track the bureau's own learning curve on what kinds of public claims it considered intelligence-worthy and what kinds it shelved.

The May 2026 release does not include every page the file ever generated. Specific photographs referenced in the index remain absent or marked withheld. Witness identities are routinely redacted at the field-office level. Some serials cross-reference other case files that have not yet been released. The pattern is consistent with the way the bureau still handles internal-security material today. The fact of the case is public. The provenance, sources, and most of the photographic record stay restricted.

The procedural takeaway is the durable one. A twenty-one-year headquarters-level case file at the FBI is, by the bureau's own classification logic, a sustained intelligence priority. It is not a record of an institution that decided UFOs were nonsense and shelved them. It is a record of an institution that did not know what the reports were, decided not to dismiss them, and kept watching the people watching the sky. When the same bureau opened a new investigation in September 2023 and produced a composite sketch of a bronze metallic ellipsoid plus three Form 302 witness interviews, [FBI September 2023 Sighting - Composite Sketch p.1] the procedural posture had not changed. The file structure was the same. The classification logic was the same. The institutional answer was the same: take it seriously, write it down, keep the underlying provenance closed. The May 8 release puts those two ends of the FBI's UAP record into a single index for the first time.

The largest single block of the May 8 release is the modern military layer. Roughly fifty-seven standardized mission reports were filed by US Air Force, Navy, and Special Operations crews between November 2016 and April 2025 and routed through the All-domain Anomaly Resolution Office, the formal Pentagon office stood up to triage UAP encounters. [DOW-UAP-D12, Mission Report, Iraq, May 2022 p.1] The reports come in two families: detailed mission reports (the D-series) and shorter unresolved-incident summaries (the PR-series). Both use the same standardized AARO form. The D-series carries the per-incident narrative; the PR-series carries the disposition.

The geographic concentration is the first thing that reads off the corpus. Of the modern reports in this drop, the largest clusters originate from US Central Command theaters: the Arabian Gulf, Iraq, Syria, the United Arab Emirates, Kuwait, the Gulf of Aden, and the eastern Mediterranean over Greece. [Source: dow-uap-d12-mission-report-iraq-may-2022 p.1, dow-uap-d19-mission-report-syria-february-21-2023 p.1, dow-uap-d25-mission-report-greece-january-2024 p.1, dow-uap-d27-mission-report-united-arab-emirates-october-2023 p.1] These are not random global locations. They are theaters of active US military operations and persistent intelligence-surveillance-reconnaissance coverage. That alone does not tell us whether the phenomenon prefers operational theaters or whether US ISR platforms are simply more likely to encounter and document anything anomalous. It does tell us where the modern record can support correlation analysis and where it cannot.

The form itself is the second thing that matters. AARO's MISREP includes fields for altitude, velocity, heading, sensor modality, intelligent control, advanced capabilities, and resolution. The form was clearly designed to produce a categorical answer. The corpus shows that across most modern reports, the measurable fields come back populated and the analytical fields come back marked unknown, unable to determine, or unresolved. [DOW-UAP-D25, Mission Report, Greece, January 2024 p.1] Crews record altitudes to the flight level, velocities in knots, and headings in compass bearings; they record which sensor saw the object and how long the lock held. They do not record the object's propulsion system, origin, or intent, because the form's analytical column asks them to determine those things and they cannot.

The sensor stack is the third durable signal in the corpus. The reports document objects observed via TFLIR pods, electro-optical full-motion video, short-wave infrared, AESA radar, and unaided visual contact, often in combination. [DOW-UAP-D19, Mission Report, Syria, February 21, 2023 p.1] In several cases the modalities disagree about what they are seeing. An object visible in IR can be missing from radar. An object holding a radar lock can be invisible to the targeting pod. An object can be reported as benign by one observer and as executing high-rate maneuvers by another in the same flight. The form treats these mismatches as data, not as errors to be reconciled before filing. That is itself a procedural shift from the older parts of the corpus, where a single observer's report was the unit of record.

The range-fouler institutional layer is the fourth thing worth noting. The Navy's TOPGUN debrief for an October 2020 Range Fouler incident off the East Coast is one of the more compact documents in the modern set, and it is filed not as a mystery but as an aviation safety event that happens to involve unidentified contacts. [DOW-UAP-D58, Range Fouler Debrief, NA, October 2020 p.1] Range incursions by unidentified objects have been folded into the same flight-safety pipeline used for any unauthorized aircraft. That is what institutionalization looks like at the working level.

The unresolved-incident summaries in the PR-series close the corpus on the AARO side. Reports like the Kuwait May 2022 summary record an incident as observed, sensor-fixed, and reviewed, then mark it unresolved at the AARO disposition step. [DOW-UAP-PR20, Unresolved UAP Report, Kuwait, May 2022 p.1] The pattern across the PR-series is consistent. The military system can hold and process the data. The disposition that comes out the back end is not converging.

The point this chapter wants the reader to leave with is narrow. The modern MISREP corpus is not a leak. It is the product of a working form, run through a working office, by working crews, in working theaters, over roughly nine years. The data the form is good at recording is now public. The analytical column that the form was supposed to resolve, in case after case, is still open.

The fifteen NASA entries in the May 8 release are the part of the index that resists the standard skeptical reductions. The cases come from Gemini 7 in 1965, Apollo 11 and Apollo 12 in 1969, Apollo 17 in 1972, and Skylab through 1973 and 1974. [Source: nasa-uap-d3-gemini-7-transcript-1965 p.1, nasa-uap-d1-apollo-12-transcript-1969 p.1, nasa-uap-d2-apollo-17-transcript-1972 p.1, nasa-uap-d7-skylab-techincal-crew-debriefing-1973 p.1] The observers are trained mission crews working inside structured flight plans. The records are mission transcripts and technical debriefings produced for engineering review, not for public release. The category is small. It is also, on its face, evidentiarily distinct from anything else in the drop.

Gemini 7, December 1965, opens the layer. Frank Borman's transcript captures the "bogey" sighting in plain Mission Control phrasing, with crewmate James Lovell pointing out a nearby booster as a possible reference and Borman noting it separately. [NASA-UAP-D3, Gemini 7 Transcript, 1965 p.1] The transcript reads as the crew working a real-time identification problem, not as drama. The dialogue is the kind of conversational triangulation that would be unremarkable on any other contact and that records its uncertainty as it goes.

Apollo 11 carries a small, specific cluster. Buzz Aldrin's three-anomaly debriefing entry from the technical crew interviews places his memory of the in-flight observation on the record in technical-debrief format, not on a press call. [NASA-UAP-D4, Apollo 11 Technical Crew Debriefing, 1969 p.1] The Apollo 12 transcript carries the now-public lunar-orbit tracking-light disagreement, where the crew's reading of a moving light fails to match what Houston is tracking. [NASA-UAP-D1, Apollo 12 Transcript, 1969 p.1] Five annotated lunar-surface photographs from Apollo 12 accompany the transcripts, with surface features marked for engineering review. [NASA-UAP-VM1, Apollo 12, 1969 p.1] The annotated images are administrative artifacts of NASA's own internal photo-review pipeline, not journalism. They show that the agency's own photo analysts marked anomalies for follow-up.

Apollo 17 is the densest NASA cluster. The mission transcript runs sixteen pages and captures a three-day anomaly sequence under crew discussion. [NASA-UAP-D2, Apollo 17 Transcript, 1972 p.1] Harrison Schmitt's persistent-light-flash records show a working geologist's effort to characterize a recurring phenomenon under instrumented conditions, with multiple time-tagged observations. [NASA-UAP-D6, Apollo 17 Technical Crew Debriefing, 1973 p.1] A separate Apollo 17 photograph carries the triangular three-dot anomaly that the agency's internal annotation process kept rather than discarded. [NASA-UAP-VM6, Apollo 17, 1972 p.1]

Skylab closes the layer. The three-crew technical debriefings cover anomaly discussions across the 1973 and 1974 station rotations. [NASA-UAP-D7, Skylab Techincal Crew Debriefing 1973 p.1] Skylab matters because it is an orbiting station rather than a transient capsule, and because the crews had time to observe and re-observe. The debriefings record their judgments about what could be reflected hardware, what could be ice or paint flake, and what stayed unresolved after those checks ran.

The evidentiary point is procedural. Spaceflight crews are not the audience the skeptical literature was built to address. Bird and balloon explanations apply at altitude in atmosphere, not in lunar orbit. Civilian-witness reliability arguments apply to the public, not to a sitting astronaut filing into a NASA technical debrief at the Manned Spacecraft Center. Sensor-artifact arguments apply to single-instrument records, not to a Schmitt-style flash log that runs across multiple crew members and multiple sessions. Each of the standard reductions has a category boundary the NASA layer sits outside.

What the layer does not do is settle the question. The transcripts and debriefings record the crews' uncertainty as faithfully as they record their certainty. Borman's bogey gets a possible-booster reference. The Apollo 12 tracking-light disagreement leaves the disagreement on the record. Schmitt's flashes are logged as flashes and not labeled. The cumulative effect, across fifteen documents, is a set of professional observations made by trained crews under instrumented conditions, marked unresolved by the same crews. That is a different epistemic posture from a sensational claim. It is also the posture that is hardest for the next generation of UAP-skepticism to dismiss.

The shortest layer of the May 8 release is also the most institutionally telling. Five State Department UAP cables and one four-document FBI investigation, all of them brief, show that diplomatic posts and the present-day FBI still process UAP reports through their own normal paperwork. They do not produce mystery dossiers. They produce cables and Form 302 interviews, with whatever the underlying observation was treated as a fact to be filed.

The cables are dated 1985 through 2003, spanning a wide diplomatic geography. The earliest, from Papua New Guinea in January 1985, records a high-altitude aircraft report into the standard cable format. [State Department UAP Cable 1, Papua New Guinea, January 28, 1985 p.1] The Kazakhstan cable from January 1994 captures a Tajik 747 captain tracking an object across Kazakh airspace, again in routine action-cable form. [State Department UAP Cable 2, Kazakhstan, January 31, 1994 p.1] The 2001 Tbilisi cable handles Russia's framing of an alleged UAP incident over Georgian airspace and the diplomatic exchange that followed. [State Department UAP Cable 3, Tbilisi, Georgia, October 30, 2001 p.1] The Turkmenistan cable from November 2004 is the strangest of the five, recording how a local UFO society was put to politically useful purposes by the regime. [State Department UAP Cable 4, Ashgabat, Turkmenistan, November 5, 2004 p.1] The Mexico cable, dated September 2003 but covering the long-running Jaime Maussan claims that surfaced again in the 2023 Mexican congressional hearing on non-human bodies, closes the set. [State Department UAP Cable 5, Mexico, September 16, 2003 p.1]

What the cables share, despite their geographic and topical spread, is form. They are operational diplomatic traffic. They go through post-to-Washington routing. They get cleared by deputy chiefs of mission, action-tagged, and filed. The cable about a 747 captain over Kazakhstan reads the same procedural way as a cable about a missile test or a port closure. The fact that the State Department routinely handled UAP reports inside the working cable format means that the agency's machinery never carved out a separate, mystery-coded path for them. They were treated as facts on the ground that the embassy reported and that headquarters filed.

The 2023 FBI bronze-ellipsoid investigation is the modern counterpart on the domestic side. Four documents make up the case. A composite sketch produced by the FBI Laboratory shows the witnesses' description of a bronze metallic ellipsoid. [FBI September 2023 Sighting - Composite Sketch p.1] Three Form 302 interview records capture the witness accounts in the bureau's standard interview format. [Source: fbi-september-2023-sighting-serial-3 p.1, fbi-september-2023-sighting-serial-4 p.1, fbi-september-2023-sighting-serial-5 p.1] Two witnesses describe a bronze metallic object. A third describes a metallic-gray object. A separate interview records a test-site light observation tied to the same event window.

The most procedurally striking element of the 2023 case is the lab composite. The FBI Laboratory produces composite sketches for many kinds of investigations, often in support of suspect identification or evidence reconstruction. The decision to commission a composite of a UAP from witness statements puts the investigation into the same evidentiary category as any other case the lab supports. The bureau did not decide the witnesses were unreliable and shelve the case. It treated the witness statements as the basis for an evidence product and then filed the product with the case.

A connected document in the index, a US person's statement about a multi-hour orb encounter, gives an additional contemporaneous data point from a senior intelligence official. [USPER Statement about UAP Sighting p.1] The Western US event entry records seven federal agents reporting four categories of UAP across a single incident. [Western US Event p.1] None of these documents reads as exotic. They read as ordinary federal paperwork around a non-ordinary observed event.

What this layer adds to the May 8 release is procedural confirmation. The same bureaucratic logic that produced 62-HQ-83894 across two decades of FBI work in the mid-twentieth century still produces records today. The same diplomatic-cable logic that handled a Borman bogey radio loop in 1965 still handled a Mexican congressional claim in 2003. The institutions did not have to invent new forms to process UAP. They used the forms they already had. The May 2026 drop puts those routine-form artifacts in public view, side by side with the headquarters case files and the mission reports, and lets the reader watch how the federal government's own paper machine writes up something it has not yet been able to explain.