How to Read Declassified UAP Documents: A Beginner's Guide

The government posted its declassified UAP files on war.gov as a wall of links. You can download them, sure. Good luck finding the pattern. The UFO Papers archive takes those same files and maps them by theater, graphs them on a timeline, and lets you filter by agency, object shape, or location. Want every CIA report involving a green luminous object over Eastern Europe? A few clicks. Want to see which years the Department of War filed the most material? It's a chart now, not a guessing game. That's the difference. You stop scrolling and start exploring.

Once you're in there, though, the files themselves can read like a foreign language. Dense acronyms. Cryptic stamps. Black bars where text used to be. Two mistakes are easy here. 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. You'll learn 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, so you can read the files in the archive yourself. One rule holds throughout. 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. It's not a verbatim transcript. It's the agent's summary, written up after the fact. That distinction 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 documenting a February 2026 interview about a July 2025 orb sighting in the northeastern United States. The event itself is captured in video exhibit FBI-UAP-PR004. The written narrative ties directly to that video, and that pairing is exactly what you want to find. A description next to the actual footage lets you check one against the other.

The FD-1057

The FD-1057 is the form the FBI uses to record investigative activity, including first-hand narratives gathered from witnesses. Case FBI-UAP-D002 is an FD-1057 capturing a first-hand account of a UAP near Colorado Springs, Colorado, in 2022, and it's partially redacted. Read it next to ICA-UAP-D001, an All-domain Anomaly Resolution Office (AARO) intelligence analysis tied to the same Colorado Springs event, and you'll see how one incident can spawn multiple document types from different corners of the government. Two independent records of the same event let you start checking for consistency.

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 green object seen in the USSR in the summer of 1973. When you read an IIR, hold onto this. The report is a faithful relay of a source's claim. The agency is documenting the report. It isn't endorsing it.

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 for the opposite reason. It moves 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 "Flying Saucer" evaluation study, plus the AFSWP material in DOW-UAP-D017 from 1948 to 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 are hiding a witness's name, an agent's identity, a phone number, or a sensitive collection method. They aren't concealing the existence of anything exotic. 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. The CIA's 19 files include CIA-UAP-017, a never-before-released report on a 2008 sighting at Harare International Airport in Zimbabwe that got debated internally as a possible foreign reconnaissance device or an extraterrestrial explanation. That debate is visible in the surviving text, and it models the kind of measured uncertainty you should expect from a credible document.

Evaluating Sources Critically

Reading the mechanics is half the job. The other half is judgment. A few questions carry you a long way.

1. 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.
2. 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.
3. 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.
4. 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 precisely so these cross-references are possible.
5. 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, including Apollo-era records like NASA-UAP-D001 (Apollo 12) and NASA-UAP-D002 (Apollo 17), reference anomalous observations inside mission documentation. They're 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.

Work through those steps and you'll read declassified UAP records with the same caution and curiosity the documents were written with.

Start Exploring

Document literacy turns a wall of acronyms into a record you can actually read. Once you can tell an FD-302 from an IIR, spot a portion marking, and read around a redaction, the archive opens up. Every file becomes something you can evaluate on its own terms instead of taking on someone else's word.

Ready to put this to work? Browse the full collection at UFO Papers and start with the files referenced above to see these formats in the wild. Map them by theater, filter by agency, follow a shape across decades. If you want new declassified releases and reading guides as they drop, subscribe to our free newsletter. The documents are public. Now you know how to read them.