Navy FLYOBRPT reporting instruction (1954)

From the UAP Encyclopedia, the open encyclopedia of UFO and UAP history · 🗓️ Event

Contents 7
Navy FLYOBRPT reporting instruction (1954)
Donald Keyhoe
Donald Keyhoe Photo: CBS, "The Mike Wallace Interview" 1958 March 8 · Public domain · via Wikimedia Commons
Date23 July 1954
TopicsOcean & underwater (topic)
PeopleDonald Keyhoe
TestimonyShellenberger testimony, p. 52
Year1954 in UFO history
Timeline1954 on the UAP Timeline
Sources4

On 23 July 1954 the commandant of the U.S. Navy's Potomac River Naval Command issued PRNC Instruction 3820.1, telling Navy units in the Washington area how to report unidentified flying objects. Reports were to be sent by message without delay to Air Force and Navy intelligence and air defence commands, headed with the code word "FLYOBRPT" (flying object report).[1]

The instruction

Illustration of official papers and files
Illustration: official papers and files. An artist's impression drawn for this site, not a photograph of the event.

The instruction defined unidentified flying objects as any airborne object which, by performance, aerodynamic characteristics or unusual features, did not conform to any known aircraft or missile. It noted that the Air Force had primary responsibility for collecting such information and had asked all naval activities to cooperate. It cited an earlier Chief of Naval Operations notice of 26 September 1952, the military communications directive JANAP 146(C) and an Air Force letter of April 1952.[1]

Reporting

The 445th Airlift Wing at Wright-Patterson Air Force Base, Ohio received its first C-17 Globemaster III Jan. 21,2010. The aircraft is on loan from…
The 445th Airlift Wing at Wright-Patterson Air Force Base, Ohio received its first C-17 Globemaster III Jan. 21,2010. The aircraft is on loan from… Photo: United States Air Force · Public domain · via Wikimedia Commons

Reports were to go for action to the Director of Intelligence at Air Force headquarters, the Air Technical Intelligence Center at Wright-Patterson Air Force Base, Air Defense Command at Ent Air Force Base in Colorado Springs and the Eastern Air Defense Force, with copies to the Director of Naval Intelligence, the Eastern Sea Frontier and the Potomac River Naval Command. They were to describe the object's shape, size, colour and number, and the circumstances of the sighting.[1]

Context

Illustration of a jet meeting an unknown object
Illustration: a jet meeting an unknown object. An artist's impression drawn for this site, not a photograph of the event.

The instruction closely matched the Air Force's revised regulation AFR 200-2, issued a few weeks later on 12 August 1954. Together they show the military treating UFO reports as an air-defence and intelligence matter at the height of the Cold War, when officials feared that Soviet aircraft could use unusual tactics or that reports might mask an attack.[1][2]

Publication

Illustration of an open book about flying saucers
Illustration: an open book about flying saucers. An artist's impression drawn for this site, not a photograph of the event.

The text was obtained by civilian researchers and appears in Donald Keyhoe's 1955 book The Flying Saucer Conspiracy. Keyhoe used it to argue that the Navy took UFOs more seriously than the Air Force's public statements suggested. The Naval History and Heritage Command has published background on how the Navy handled UFO reporting in this period.[1][3]

People and topics

Illustration of an object over the sea
Illustration: an object over the sea. An artist's impression drawn for this site, not a photograph of the event.

On the Timeline

Illustration of wreckage at a crash site
Illustration: wreckage at a crash site. An artist's impression drawn for this site, not a photograph of the event.

See every 1954 event on the UAP Timeline →

References

This page was last edited on 29 October 2026. Articles are written in our own words from the sources listed under References; disputed claims are attributed to the people who made them.

Discuss the article: missing sources, mistakes, or what should be added.

No discussion yet.

BrowseFeedArticlesTimelineOfficial filesMapTonight’s SkyStatsFavorites