Documents / Report

Project Blue Book Special Report (second copy)

Internet Archive · 309 pages · text from the file's own layer

This is Project Blue Book Special Report No. 14, "Analysis of Reports of Unidentified Aerial Objects," Project No. 10073, dated 5 May 1955. The study reduced about 4,000 sighting reports received by the U.S. Air Force between June 1947 and December 1952 to IBM punched cards and analyzed them statistically, including chi square tests comparing knowns with unknowns. It concludes that the reports very probably do not represent technological developments beyond present scientific knowledge, and it notes that no case produced physical evidence.

  • p. 7 …Air Force on unidentified aerial objects were reduced to IBM punched-card abstracts of the data…
  • p. 10 …form suit- able for transfer to IBM punched cards was extremely difficult ""and time consuming. For…
  • p. 14 …Thus, the selection of the IBM punched- card system for analysis of data forced the adoption…
  • p. 18 …Multiple punching elirninated the need to use several columns for discrete expression of the variations., Selection…
  • p. 22 …counting, and tabulating the information from the punched-card abstracts of reports of sightings. It was…
  • p. 23 f m translation and transcription from reports to punched cards, indicated that there would be relatively…
  • p. 63 …cosines, and tangents of angles had been punched for each 0.01 of a degree from…
  • p. 68 …These group numbers were punched on the cards and incorporated into the coding system. The number…
  • p. 296 Observer's Data Sheet Question WORK SHEET Punched Card Column Code Description 2 3 h Serial…
  • p. 297 Observer's Data Sheet Question Punched Card Column Code Description 6. 7. a. 1 0 . Ui…
  • p. 299 …If no data are available for any column, the Y (or 12 punch) should be used…
  • p. 300 …Air Force Technical Information Sheet Question Punched Card Column Code Description I. f? • f V : HIT…
  • p. 306 …Air Force Technical Information Sheet Question Punched Card Column Code Description 1. 1 2 k 12…
  • p. 307 …Air Force Technical Information Sheet Question Punched Card Column Code Description 3o hi U6 75* 76…
CODES
CODE 1. GENERAL
a. These cards (and the corresponding WORK SHEETS) contain data from
several sources. Columns referenced to the U. S, Air Force Technical
Information Sheet (Form A) must have at least one entry. If no data
are available for any column, the Y (or 12 punch) should be used,
b. Columns 22, 23, 2U, 25, 26, 36, 37, 38, 39, UO, Ul, 1*2, k}, UU, hS,
U6, hi $ U8, k9, SO, and 5>1 are calculated from data appearing in the
U. S. Air Force Technical Information-Sheet (Form A).'if the basic
data for these calculations are not available, the appropriate columns
are left blank.
c. If a number in any column is used to enter data, then X (or 11 punch)
qualifies the data as indicated in the Code for the specific column.
CODE 7 SIGHTING IDENTIFICATION
(Tiiis column may or may not
contain multiple punches) CODE 22 LOCAL SUN TIME
(Refers to date of G.C.T. observation)
X
Y
0
1
2
3
h
5
6
7
8
9
All sightings
Unit sightings, all observers
Unit sightings, single observers
Unit sightings, multiple observers
Object sightings
X
Y
0
1
2
3
U
6
7
8
9
Same day
Previous day
? CODE 23-26 LOCAL SUN TIME
(Calculated from G.C.T.,
date, latitude, and-longitude) CODE 27 LATITUDE CODE 31 LONGITUDE
X South Latitude
Y
0
1
2
3
h
5
6
7
8
9
X East Longitude
Y
0
1
2
3
k
$
6
•7
8
9
303

Cases discussed

About this file

Report, cited by the archive. The PDF is mirrored here; the original link is under it. 309 pages are in the text index: search them above, or from the library's search.