The declassified UAP releases on war.gov arrive as lists of file links, named the way agencies name things: FBI-UAP-D009_FD-302-67_Northeastern-Orb-Sighting_2026.pdf. The UFO Papers archive organizes those same files, 294 of them, so they can be filtered by agency, date, object shape, and location. Organization gets you to the right file. It does not tell you how to read it. The pages themselves are written in the government's internal shorthand, dense with form numbers, classification stamps, redaction bars, and acronyms that assume the reader already works there.
Two mistakes are easy once you open one. You can over-read the pages and assume every redaction hides a smoking gun, or you can write the jargon off as noise. Both will steer you wrong.
This guide covers the practical mechanics of reading declassified unidentified anomalous phenomena (UAP) and UFO records the way a careful analyst would: what the common form types mean, how to read classification markings and redactions, and how to weigh a source. I'm not going to tell you what to believe. The point is literacy. Stay grounded in what the document actually says, and treat the rest as interpretation.
Why Document Literacy Matters
The UFO Papers archive collects 294 declassified U.S. government files spanning the Department of War, FBI, NASA, CIA, Department of State, and other agencies. These came out of the government's declassified UAP releases on war.gov, and the archive (the owner calls it PURSUE) is where they're organized and searchable. They're primary sources. A primary source beats any headline summarizing it, because the summary drops nuance, skips caveats, and now and then flips the document's actual conclusion on its head.
Government records get written for an internal audience that already knows the conventions. When a report calls a sighting "evaluated" or "unresolved," those words carry specific institutional weight. Reading the files on their own terms is what separates informed analysis from speculation. The same skill protects you in the other direction. A redaction isn't proof of a cover-up, and a classification stamp doesn't mean the contents are extraordinary. Plenty of the time they're mundane procedural matters that got classified for reasons that have nothing to do with the sighting.
Decoding FBI Forms: FD-302 and FD-1057
The FBI accounts for 86 files in the archive, and a lot of them land on standardized bureau forms. Two are worth knowing by name.
The FD-302
The FD-302 is the FBI's standard form for documenting an interview or an investigative activity. When an agent talks with a witness, the substance of that conversation gets written up on an FD-302 as the agent's after-the-fact summary. No verbatim transcript sits underneath it. That matters when you read one. You're reading an agent's account of a witness's account, so there are two layers of interpretation sitting between you and the original observation.
Take FBI-UAP-D009, an FD-302 recording a February 2026 interview with a U.S. person who described incidents potentially involving UAP. The sighting itself, an orb over the northeastern United States, carries only a year, 2026, in the archive metadata. The archive also notes that the subject matter described in FBI-UAP-D009 and FBI-UAP-D010, and depicted in the video footage FBI-UAP-PR004, "corresponds to reports originating from the same general area in the northeastern United States." Same general area is a deliberately loose phrase, and the file never claims the footage shows the sighting from the interview. Reading a written narrative alongside video is still worth doing. You just have to carry the actual strength of the link with you, and here the documented link is geography, nothing tighter.
The FD-1057
The FD-1057 is the form the FBI uses to record investigative activity. Case FBI-UAP-D002 is an FD-1057 holding a first-hand narrative of a UAP reported near Colorado Springs, Colorado, in 2022, and it's partially redacted. The witness gave the statement to FBI special agents to help produce a digital artistic interpretation of the incident. Read it next to ICA-UAP-D001, an analysis of the same 2022 incident produced by an Intelligence Community partner of the All-domain Anomaly Resolution Office (AARO), and you get a working example of one event generating multiple document types in different corners of the government. The partner agency assessed, with low confidence, that the phenomenon, which observers described as resembling an "angular, non-symmetrical potato," was attributable to sunlight backscattering: sunlight reflecting off mountain snow cover and lighting the underside of low-altitude clouds. AARO's consideration of the incident remains unresolved as of June 2026.
When you hit either form, note the date it was completed against the date of the event it describes. A long gap can dent reliability, and the forms usually make both dates visible.
Military and Intelligence Reporting: MISREP and IIR
The FBI's bureau forms aren't the whole story. Military and intelligence agencies run their own report structures.
A MISREP (Mission Report) is filed after a military mission or sortie. It documents what a crew observed, the conditions, and any anomalies during the operation. MISREPs are operational, so they tend to stay terse and stick to facts relevant to the mission instead of guessing at causes.
An IIR (Intelligence Information Report) is the standard format for pushing out raw, unevaluated intelligence, often from human sources (HUMINT). The key word is unevaluated. An IIR conveys what a source reported, not what the agency concluded. Case CIA-UAP-D001 is exactly that: a CIA Intelligence Information Report dated December 20, 1973, relaying a HUMINT source's account of a luminous, bright green object seen in the USSR in the summer of 1973. The source described concentric circles forming around the object over several minutes before it dissipated, said no sound attended the observation, offered no opinion on what it was, and could provide no further details. The report characterizes its own content as informational rather than finally evaluated intelligence. Filing it recorded that a source said this, and nothing more.
This is one of the most common places casual readers slip. An IIR shows up in an archive and gets treated like the government "confirmed" the contents. The format exists to move information forward before anyone has evaluated it. Read the contents as a claim waiting on corroboration.
Reading Classification Markings
Declassified documents almost always keep the markings they carried while classified. Reading them tells you how the originating agency once judged the sensitivity of the material.
- U or UNCLASSIFIED means no restriction.
- C // CONFIDENTIAL means disclosure could cause damage to national security.
- S // SECRET sits a tier up, where disclosure could cause serious damage.
- TS // TOP SECRET is the highest standard tier, reserved for material whose disclosure could cause exceptionally grave damage.
You may also run into portion markings, where each paragraph is tagged with its own classification in parentheses, like (U) or (S). These show you which specific passages drove the document's overall classification. A mostly unclassified report can carry a SECRET banner on the strength of one or two sensitive paragraphs. Spotting those portions tells you where the originating agency put the actual sensitivity, which is often more revealing than the cover banner.
Older records use older systems. The Department of War accounts for 143 files in the archive, including early study material like DOW-UAP-D084, a 1949 U.S. Army evaluation study of the "flying saucer" phenomenon, prepared to determine whether the origin could be traced to natural phenomena or the activities of a foreign power. There's also the Armed Forces Special Weapons Program material in DOW-UAP-D017, 116 pages covering 209 sightings of green orbs, discs, and fireballs reported near Sandia Base, New Mexico, from 1948-1950. The vocabulary and stamp formats from that era look different from modern conventions, so always read markings against the document's date.
Understanding Redactions
A redaction is the black bar (or white gap) where text has been withheld. The single most important thing to know is that redactions usually get made under specific legal exemptions, most often the ones written into the Freedom of Information Act (FOIA). These exemptions commonly protect personal privacy, intelligence sources and methods, and ongoing law enforcement matters.
In practice, most redactions in UAP files hide a witness's name, an agent's identity, a phone number, or a sensitive collection method. When you see redactions, look for the exemption codes printed in or near the black bar. They tell you the category of what was withheld, which is frequently more useful than the missing words.
Don't assume the redacted content is the most important part of the page. Analysts read around redactions: what survives, the shape of the sentence, the heading it falls under, the surrounding context. And the same restraint applies to what a document does say. The CIA's 19 files include CIA-UAP-017, a never before released report on a July 2008 UFO sighting at Harare International Airport in Zimbabwe. The archive's description gives the interpretive content in one sentence: individuals debated whether the sighting was an advanced reconnaissance device of a foreign government or of extraterrestrial origins. That sentence is the extent of the recorded debate, and any claim you build on this file has to fit inside it.
Evaluating Sources Critically
Knowing the form types and markings covers the mechanics. Weighing what a document is worth takes a few more questions.
- Who wrote it, and why? An FD-302 written by an interviewing agent does a different job than an IIR relaying a foreign HUMINT source. The author's role shapes what the document is trying to do.
- Is it first-hand or second-hand? A direct observer's statement is one thing. A summary of a summary is another. Most reports add at least one layer of interpretation between the event and the page.
- What does it actually conclude? Plenty of UAP documents reach no conclusion at all. "Unresolved" or "unidentified" means the originating body couldn't explain the observation. It doesn't mean anyone confirmed an extraordinary cause.
- Can it be corroborated? A written report paired with a video, image, or audio exhibit, or two independent records of the same event, beats a lone narrative. The archive spans 175 PDFs, 84 videos, 24 images, and 11 audio files, so cross-references of this kind are often possible.
- What's the era and context? A 1949 evaluation study and a 2026 interview were written under different doctrines, technologies, and threat assumptions. Judge each by the standards of its time.
The discipline is to let the document set the ceiling on your claims. NASA's 33 files include Apollo-era records like NASA-UAP-D001, an excerpt from the Apollo 12 air-to-ground voice transcript of November 1969, and NASA-UAP-D002, its Apollo 17 counterpart from December 1972. Both capture contemporaneous crew observations of unidentified phenomena inside routine mission documentation, valuable because they record what got noted at the time, without leaping to conclusions. Read them the same way.
A Simple Reading Checklist
Before you form an opinion on any file, run this quick pass.
- Identify the form type (FD-302, FD-1057, MISREP, IIR, or a study) and what that format is built to do.
- Note the agency, the author's role, and whether the account is first-hand.
- Compare the event date with the document date.
- Read the classification banner and portion markings to see where the sensitivity actually sits.
- Check redaction exemption codes to understand the category of withheld material.
- Look for corroborating exhibits or independent records of the same event.
- State the document's actual conclusion in plain words, including any "unresolved" status.
A reasonable first exercise is the Colorado Springs pair: FBI-UAP-D002 for the form type, the first-hand account, and the redaction pattern, then ICA-UAP-D001 for the partner analysis. One witness statement on a bureau form, one low-confidence assessment from an IC partner, and an incident still carried as unresolved as of June 2026.