Project Blue Book records: a research guide

Start with the archive, not a retelling

The National Archives holds the declassified U.S. Air Force Project Blue Book records. Its reference page says the project closed in 1969 and describes finding aids organised by sighting date and location. That makes the archive a useful starting point for historical UFO research, rather than a source for every later sighting.

The same page reproduces a 1985 Air Force fact sheet. Read that material as a dated historical statement, not as a description of every agency’s current approach. Recording when a document was produced is part of understanding what it can—and cannot—answer.

Source: National Archives: Project BLUE BOOK
Archive background and historical reference material.

Identify the file before interpreting the event

Write down the archive identifier and the exact catalogue title. Keep the catalogue date separate from dates found inside the file. A date can refer to the event, the report, an interview or an administrative action. Do not turn a month-only date into a precise day simply to make a timeline look complete.

Anomaly Graph’s “Hungary, June 1947” entry is a concrete starting point. Its summary identifies it as indexed from National Archives metadata with page-level review pending. That is a useful limitation, not a reason to silently fill the gaps. Follow its source link and check the available pages before making claims about the incident.

• Archive identifier and original title.
• Source URL and date accessed.
• Event date versus document date.
• Page or image number for each quoted observation.
• Missing pages, uncertain dates and review limitations.

Read the page image alongside the searchable text

Searchable transcription is a route into a document, not a substitute for the document. OCR can misread place names, join adjacent columns or turn a damaged character into a different word. When an important match depends on a single term, compare that term with the page image if it is available.

Keep short transcriptions tied to their page references. Use brackets to distinguish your clarification from the original wording. If a word cannot be read confidently, mark it uncertain rather than selecting whichever reading best supports your hypothesis. Record an unavailable image as a retrieval gap; do not describe it as inspected.

Build a timeline of reporting as well as events

Create two linked sequences: what reportedly happened and how information about it travelled. For example, distinguish the observation, a written statement, a newspaper item and a later case summary. These are proposed categories for your notes, not claims that every file contains all four.

A later summary can be useful without being an independent witness. Trace repeated wording back to the earliest accessible account. If you cannot establish independence, say so. Several records pointing to the same original report should not become several votes for the report’s accuracy.

Compare cautiously and leave a clear next step

Once you have checked a file, search its specific descriptive details across the wider collection. Try a location, an observable feature and a time period separately before combining them. Retain records that contradict your preferred interpretation as well as those that resemble it.

End your notes with the most valuable unresolved task: locate a missing page, verify a place name, distinguish two similarly titled files or find the earlier account cited by a summary. A good archive investigation leaves an auditable trail that another reader can follow without trusting your conclusion first.

• A passage-backed observation, not just a catalogue title.
• The source and page supporting that observation.
• A separate explanation or assessment, with its author and date.
• Related records and whether they share a source.
• One explicit next research task.