Air Force Regulation 200-2

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

Contents 7
Air Force Regulation 200-2
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.
Date26 August 1953
TopicsSecrecy & cover-up (topic), Government programs (topic), Congress & law (topic)
TestimonyShellenberger testimony, p. 49
Year1953 in UFO history
Timeline1953 on the UAP Timeline
Sources7

Air Force Regulation 200-2, "Unidentified Flying Objects Reporting", was the U.S. Air Force directive governing how UFOs were reported and investigated. Issued on 26 August 1953 and revised in August 1954, it gave field investigations to the 4602d Air Intelligence Service Squadron and restricted what the public could be told.[1][2]

Provisions

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

The regulation set out how Air Force bases should report UFOs. The 4602d Air Intelligence Service Squadron of Air Defense Command, based at Ent Air Force Base in Colorado, was given the job of preliminary and field investigations within the United States, while Project Blue Book at Wright-Patterson Air Force Base received and analysed the reports. The squadron's operations officer evaluated reports and supervised its investigators.[1][2][3]

Public information

Illustration of lights in formation over the landscape
Illustration: lights in formation over the landscape. An artist's impression drawn for this site, not a photograph of the event.

The regulation controlled what the public could be told: bases could release information only when a sighting had been positively identified as a familiar object, while unexplained cases were not to be discussed publicly. The 1954 revision kept these restrictions.[1][4]

Criticism and later changes

Scott Bray (deputy director of naval intelligence) and Ronald Moultrie (Defense Department’s under secretary for intelligence) testify to House…
Scott Bray (deputy director of naval intelligence) and Ronald Moultrie (Defense Department’s under secretary for intelligence) testify to House… Photo: U.S. House Permanent Select Committee on Intelligence · Public domain · via Wikimedia Commons

Critics argue that AFR 200-2 shifted the most interesting cases away from Blue Book, whose small staff and limited budget made it more of a public-relations office, while the 4602d and higher intelligence offices handled field work. A February 1958 revision returned investigations to local base commanders. By the late 1960s UFO reporting was governed by a successor, Air Force Regulation 80-17, which was cancelled when Blue Book closed in 1969.[4][5][6]

People and topics

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

On the Timeline

Flying saucer from the USA National Archives and Records Administration, cropped from the original here…
Flying saucer from the USA National Archives and Records Administration, cropped from the original here… Photo: Unknown author Unknown author · Public domain · via Wikimedia Commons
  • Kingman UFO crash (21 May 1953) — An engineer using the pseudonym Fritz Werner swears he investigated a crashed craft near Kingman, Arizona.
  • Lockheed–Kelly Johnson sighting (1953) (18 December 1953) — Lockheed test crew members flying a Navy aircraft follow a flying saucer over the Pacific.

See every 1953 event on the UAP Timeline →

References

Further reading

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