War.gov PURSUEDepartment of War
Government1955Analysis complete

DOW-UAP-D096 — Correspondence Relating to Project Blue Book, 1955

A 220-page Project Blue Book correspondence file documents public requests, interagency routing, overseas reports, standardized sighting collection, program statistics, and at least one reported object later identified as an upper-air sounding device. The collection reveals the administrative infrastructure behind Project Blue Book and shows why a case file can mix useful program records, resolved incidents, public speculation, and unresolved reports.

File
Document · Release 04
Date
1955
Location
Various
Extent
220 pages

Probed Assessment

A 220-page Project Blue Book correspondence file documents public requests, interagency routing, overseas reports, standardized sighting collection, program statistics, and at least one reported object later identified as an upper-air sounding device.

Key takeaways

  • The correspondence shows Blue Book functioning as an information and routing system for students, publishers, civilian researchers, military offices, and overseas attachés.
  • A reported falling object at Sardis Lake moved through intelligence channels before Air Weather Service identified it as atmospheric-sounding equipment, illustrating how investigation could produce a conventional resolution.
  • The fiscal-year summary described faster field investigation and broad explanation categories while retaining some insufficient-data and unknown cases.
  • Personal reports and speculative letters in the file document what correspondents claimed; their inclusion is not Air Force validation of those claims.

Why it matters

The collection reveals the administrative infrastructure behind Project Blue Book and shows why a case file can mix useful program records, resolved incidents, public speculation, and unresolved reports.

Corroboration

The documents directly corroborate correspondence, routing actions, forms, and official program statements. Individual civilian accounts remain unverified unless the file records a separate investigative result.

Open questions

  • • How many reports in this correspondence set can be linked to complete Blue Book case files?
  • • What effect did faster on-site investigation have on final case classifications beyond the program’s own summary?

Probed separates this editorial assessment from the source claims below. It summarizes what the released artifact supports; it is not independent verification.

Official Description from War.gov

This file contains correspondence relating to Project Blue Book, a 1952-1969 U.S. Air Force program to investigate the nature and origin of unidentified flying objects (UFO). The correspondence includes letters and memoranda sent between various departments and agencies of the U.S. Government, the Legislative Branch, and private citizens concerning UFO sightings and the research and findings of Project Blue Book.

Preserved verbatim as source metadata. This wording is separate from Probed’s file-specific description and assessment.

File Context

Related entities

18

Tracker findings

1

Air Weather Service identified one recovered object as an upper-air instrument

A February 1955 endorsement identifies the object discussed in the underlying letter as an atmospheric-detection device used for upper-air soundings. It asks that the instrument be returned to the Air Force's Radiosonde Rehabilitation facility.

Release provenance

Release
Release 04
Official ID
release-04-file-020-dow-uap-d096-correspondence-relating-to-project-blue-book-1955
Cleared
Jul 10, 2026
Official release source

Referenced Timeline

  1. Page 137

    Project Blue Book fiscal-year activity summarized

    The program compiled report categories and described changes in insufficient-data and unknown classifications.

  2. Page 94

    Sardis Lake object referred

    Army and Air Force offices routed a reported falling object for technical identification.

  3. Page 99

    Air Weather Service identified sounding device

    The Sardis Lake object was identified as an upper-air atmospheric-detection device.

  4. Page 137

    Civilian and publishing requests processed

    Project Blue Book and Air Technical Intelligence Center handled requests from researchers and organizations.

  5. Page 200

    Indonesian correspondence routed

    A Bandung letter was sent to the U.S. air attaché in Jakarta for action.

Source Claims

Claims are attributed to the released source and remain distinct from Probed’s assessment and tracker findings.

Source reportedAssertedPage 12

The Air Technical Intelligence Center forwarded replies and information about unidentified flying objects through Air Force intelligence policy channels.

AIR TECHNICAL INTELLIGENCE CENTER

Source reportedAssertedPage 15

A high-school student wrote Project Blue Book seeking material for a public-speaking assignment, illustrating the volume of educational and public requests handled by the program.

U.S. Air Force Project Bluebook

Source reportedUnverifiedPage 25

Another student letter asked the Secretary of the Air Force about secrecy, war, and public disclosure, reflecting public speculation rather than an official finding.

I have become extremely interested in flying saucers

Source reportedAssertedPage 41

A City College writer requested Air Force information for articles on interplanetary flight, another example of media and educational correspondence in the file.

engaged by "Main Events"

Source reportedAssertedPage 55

The Office of Naval Research asked Air Force intelligence for information on unidentified flying objects, documenting interagency interest.

Chief of Naval Research To: Director of Intelligence, U. S. Air Force

Source Material & Evidence

public_record

Official source document: DOW-UAP-D096, Correspondence Relating to Project Blue Book, 1955

RELEASE-04-FILE-020-DOW-UAP-D096-CORRESPONDENCE-RELATING-TO-PROJECT-BLUE-BOOK-1955

Research Map

18 entities · 10 grounded links

Lines appear only when two entities share a row-level source claim or dated timeline event. Unconnected nodes remain visible without implying a relationship.

UAP/Disclosure Graph
18 nodes10 links