Declassified UFO / UAP Document
Responsibility for "Unidentified Flying Objects" (UFOBs)
AI-Generated Summary
This 1955 memorandum confirms the Physics and Electronics Division's ongoing, though inactive, responsibility for monitoring Unidentified Flying Objects. It outlines the administrative process for reviewing and filing reports, noting a monthly resource requirement of 10 to 25 analyst hours.
This office memorandum, dated August 8, 1955, from the Chief of the Physics and Electronics Division to the Acting Assistant Director for Scientific Intelligence, outlines the administrative status and responsibilities regarding Unidentified Flying Objects (UFOBs). The document references previous internal communications from 1953 and 1954 that established the Division's role in maintaining knowledge of such sightings. The memorandum clarifies that the project is currently considered inactive. The established procedure for handling incoming material involves periodic reviews to segregate recognizable and explainable phenomena from those that meet the definition of unidentified flying objects. Any material deemed to be of concern to national security is flagged, while other material is deposited into files for future reference. The document notes that since the issuance of the initial assignment, the project has required between 10 and 25 analyst hours per month, with approximately half that amount of time dedicated to clerical tasks. The memorandum serves to confirm that subsequent clarifications have not reduced the Division's responsibilities regarding this subject.
the project will be considered as inactive
Rendered preview of the original document image. Download original file
Official Assessment
The Physics and Electronics Division maintains responsibility for monitoring sightings of unidentified flying objects. The project is considered inactive, with incoming material reviewed periodically to separate recognizable phenomena from unidentified objects. Material is filed unless it presents an immediate concern to national security. The project requires between 10 and 25 analyst hours per month.