Jump to content

1952 Washington, D.C., UFO incident

From Wikipedia, the free encyclopedia
Washington National Airportterminal in 1944
UFOsandufology
Flying saucer from the National Archives and Records Administration
Notable sightings
Other Relevant Topics
Religions that have UFOs in their Literature
Lists of organizations, sightings, studies, etc.

From July 12 to 29, 1952, a series ofunidentified flying object(UFO)sightingswere reported inWashington, D.C.,and later became known as theWashington flap,theWashington National Airport Sightings,or theInvasion of Washington.[1]The most publicized sightings took place on consecutive weekends, July 19–20 and July 26–27. UFO historianCurtis Peeblescalled the incident "the climax of the 1952 (UFO) flap" — "Never before or after didProject Blue Bookand the Air Force undergo such a tidal wave of (UFO) reports. "[2]

1952 UFO flap

[edit]
Reports peaked in late July.

The 1952 UFOflapwas an unprecedented rash of media attention to unidentified flying object reports during the summer of 1952 that culminated with reports of sightings over Washington, D.C.[3][4][5]In the four years prior, the US Air Force had chronicled a total of 615 UFO reports; during the 1952 flap, they received over 717 new reports.[6]Project Blue BookdirectorEdward J. Ruppeltlater recalled: "During a six-month period in 1952... 148 of the nation's leading newspapers carried a total of over 16,000 items about flying saucers."[7]

On April 3, the Associated Press reported on an upcoming story inLifemagazinethat would reveal the Air Force was taking a serious interest in flying saucers.[8] The June edition ofLookmagazinefeatured a story where astrophysicistDonald Howard Menzelproposed flying saucers were optical mirages created bytemperature inversions.[9][10]American papers covered similar statements from French astronomerErnest Esclangonwho debunked the "flying saucer reports" by explaining they could not be supersonic craft because nosonic boomswere reported.[11]

On April 7,Lifemagazine published the Flying Saucer article under the title "Have We Visitors From Space?",becoming the most reputable outlet to seriously consider the possibility that flying saucer reports might be caused by extra-terrestrial spaceships.[12][13]Publicity surrounding the piece is believed to have contributed to the subsequent wave of reports that summer.[14][15]

Sightings over Washington

[edit]

At the height of the UFO flap, there were UFOs reported at the nation's capital on two consecutive Saturday nights.

Night of July 19

[edit]

At 11:40 p.m. on Saturday, July 19, 1952, Edward Nugent, anair traffic controlleratWashington National Airport,spotted seven objects on hisradar.[16]The objects were located 15 miles (24 km) south-southwest of the city; no known aircraft were in the area, and the objects were not following any established flight paths. Nugent's superior, Harry Barnes, a senior air-traffic controller at the airport, watched the objects on Nugent's radarscope. He later wrote: "We knew immediately that a very strange situation existed... their movements were completely radical compared to those of ordinary aircraft."[17]

Barnes had two controllers check Nugent's radar; they found that it was working normally. Barnes then called National Airport's radar-equipped control tower; the controllers there, Howard Cocklin and Joe Zacko, said that they also had unidentified blips on their radar screen, and saw a hovering "bright light" in the sky, which departed with incredible speed.[16]Cocklin asked Zacko, "Did you see that? What the hell was that?"[16]

At this point, other objects appeared in all sectors of the radarscope; when they moved over theWhite Houseand theUnited States Capitol,Barnes calledAndrews Air Force Base,located 10 miles from National Airport. Although Andrews reported that they had no unusual objects on their radar, an airman soon called the base's control tower to report the sighting of a strange object. Airman William Brady, who was in the tower, then saw an "object which appeared to be like an orange ball of fire, trailing a tail... [it was] unlike anything I had ever seen before."[16][18]As Brady tried to alert the other personnel in the tower, the strange object "took off at an unbelievable speed.[18]

On one of National Airport'srunways,S.C. Pierman, aCapital Airlinespilot, was waiting in thecockpitof hisDC-4for permission to take off. After spotting what he believed to be ameteor,he was told that the control tower's radar had detected unknown objects closing in on his position. Pierman observed six objects— "white, tailless, fast-moving lights" —over a 14-minute period.[19][16]Pierman was in radio contact with Barnes during his sighting, and Barnes later related that "each sighting coincided with a pip we could see near his plane. When he reported that the light streaked off at a high speed, it disappeared on our scope."[20]

Meanwhile, at Andrews Air Force Base, the control tower personnel were tracking on radar what some thought to be unknown objects, but others suspected, and in one instance were able to prove, were simplystarsand meteors.[21]However, Staff Sgt. Charles Davenport observed an orange-red light to the south; the light "would appear to stand still, then make an abrupt change in direction and altitude... this happened several times."[20]At one point both radar centers at National Airport and the radar at Andrews Air Force Base were tracking an object hovering over a radio beacon. The object vanished in all three radar centers at the same time.[22]

At 3 a.m., shortly before twoUnited States Air ForceF-94 Starfirejet fighters fromNew Castle Air Force BaseinDelawarearrived over Washington, all of the objects vanished from the radar at National Airport. However, when the jets ran low on fuel and left, the objects returned, which convinced Barnes that "the UFOs were monitoring radio traffic and behaving accordingly".[20]The objects were last detected by radar at 5:30 a.m.

Publicity and Air Force reaction

[edit]

The sightings of July 19–20, 1952, made front-page headlines in newspapers around the nation. A typical example was the headline from theCedar Rapids Gazettein Iowa. It read "SAUCERS SWARM OVER CAPITAL" in large black type.[23]By coincidence, USAF CaptainEdward J. Ruppelt,the supervisor of the Air Force'sProject Blue Bookinvestigation into UFO sightings, was in Washington at the time. However, he did not learn about the sightings until Monday, July 21, when he read the headlines in a Washington-area newspaper.[24]After talking with intelligence officers atthe Pentagonabout the sightings, Ruppelt spent several hours trying to obtain a staff car so he could travel around Washington to investigate the sightings, but was refused as only generals and senior colonels could use staff cars. He was told that he could rent ataxicabwith his own money; by this point Ruppelt was so frustrated that he left Washington and flew back to Blue Book's headquarters atWright-Patterson AFBin Dayton, Ohio.[25]Upon returning to Dayton, Ruppelt spoke with an Air Force radar specialist, Captain Roy James, who felt that unusual weather conditions could have caused the unknown radar targets.[26]

Night of July 26

[edit]

At 8:15 p.m. on Saturday, July 26, 1952, a pilot andstewardesson aNational Airlinesflight into Washington observed some lights above their plane. Within minutes, both radar centers at National Airport, and the radar at Andrews AFB, were tracking more unknown objects.[27]USAF master sergeant Charles E. Cummings visually observed the objects at Andrews, he later said that "these lights did not have the characteristics of shooting stars. There was [sic] no trails... they traveled faster than any shooting star I have ever seen."[20]

Meanwhile, Albert M. Chop, the press spokesman for Project Blue Book, arrived at National Airport and, due to security concerns, denied several reporters' requests to photograph the radar screens. He then joined the radar center personnel.[28]By this time (9:30 p.m.) the radar center was detecting unknown objects in every sector. At times the objects traveled slowly; at other times they reversed direction and moved across the radarscope at speeds calculated at up to 7,000 mph (11,250 km/h).[29]At 11:30 p.m., two U.S. Air ForceF-94 Starfirejet fighters from New Castle Air Force Base in Delaware arrived over Washington. Captain John McHugo, the flight leader, was vectored towards the radar blips but saw nothing, despite repeated attempts.[30]However, his wingman, Lieutenant William Patterson, did see four white "glows" and chased them.[31][16]He told investigators that "I tried to make contact with the bogies below 1,000 feet," and that "I was at my maximum speed but...I ceased chasing them because I saw no chance of overtaking them."[16]According to Albert Chop, when ground control asked Patterson "if he saw anything", Patterson replied"'I see them now and they're all around me. What should I do?'...And nobody answered, because we didn't know what to tell him. "[20]

After midnight on July 27, USAF Major Dewey Fournet, Project Blue Book's liaison at the Pentagon, and Lt. John Holcomb, aUnited States Navyradar specialist, arrived at the radar center at National Airport.[16]During the night, Lieutenant Holcomb received a call from the Washington National Weather Station. They told him that a slighttemperature inversionwas present over the city, but Holcomb felt that the inversion was not "nearly strong enough to explain the 'good and solid' returns" on the radar scopes.[30]Fournet relayed that all those present in the radar room were convinced that the targets were most likely caused by solid metallic objects. There had been weather targets on the scope too, he said, but this was a common occurrence and the controllers "were paying no attention to them".[32]Two more F-94s from New Castle Air Force Base were scrambled during the night. One pilot saw nothing unusual; the other pilot saw a white light which "vanished" when he moved towards it.[26]Civilian aircraft also reported glowing objects that corresponded to radar blips seen by Andrews radar operators.[16]As on July 20, the sightings and unknown radar returns ended at sunrise.[33]

White House concern and CIA interest

[edit]

The sightings of July 26–27 also made front-page headlines, and led PresidentHarry Trumanto have his air force aide call Ruppelt and ask for an explanation of the sightings and unknown radar returns. Truman listened to the conversation between the two men on a separate phone, but did not ask questions himself.[34]Ruppelt, remembering the conversation he had with Captain James, told the president's assistant that the sightings might have been caused by a temperature inversion, in which a layer of warm, moist air covers a layer of cool, dry air closer to the ground. This condition can cause radar signals to bend and give false returns. However, Ruppelt had not yet interviewed any of the witnesses or conducted a formal investigation.[23]

CIA historian Gerald Haines, in his 1997 history of the CIA's involvement with UFOs, also mentions Truman's concern. "A massive buildup of sightings over the United States in 1952, especially in July, alarmed the Truman administration. On 19 and 20 July, radar scopes at Washington National Airport and Andrews Air Force Base tracked mysterious blips. On 27 July, the blips reappeared."[35]The CIA would react to the 1952 wave of UFO reports by "forming a special study group within the Office of Scientific Intelligence (OSI) and Office of Current Intelligence (OCI) to review the situation. Edward Tauss reported for the group that most UFO sightings could be easily explained. Nonetheless, he recommended that the Agency continue monitoring the problem."[35]The CIA's concern with the issue would lead to the creation, in January 1953, of theRobertson Panel.[35]

Air Force explanation

[edit]
Maj. Gen. John A. Samford's Statement on Flying Saucers

Air Force Major GeneralsJohn Samford,USAF Director of Intelligence, andRoger M. Ramey,USAF Director of Operations, held a well-attended press conference at the Pentagon on July 29, 1952. In his opening comments, he noted that, out of the hundreds of UFO reports in recent years investigated by the Air Force, there was "a certain percentage of this volume of reports that have been made by credible observers of relatively incredible things" but that none of them posed any national security threat.[36]At the event, Samford stated that the visual sightings over Washington could be explained as misidentified aerial phenomena such as stars or meteors, and unknown radar targets could be explained by temperature inversion, which was present in the air over Washington on both nights the radar returns were reported. In addition, Samford stated that the unknown radar contacts were not caused by solid material objects, and therefore posed no threat to national security. In response to a question as to whether the Air Force had recorded similar UFO radar contacts prior to the Washington incident, Samford said that there had been "hundreds" of such contacts where Air Force fighter interceptions had taken place, but stated that they were all "fruitless".[37]It was the largest Pentagon press conference sinceWorld War II.[38]Press stories called Samford and Ramey the Air Force's two top UFO experts.[39]

Among the witnesses who supported Samford's explanation was the crew of aB-25bomber, which had been flying over Washington during the sightings of July 26–27. The bomber was vectored several times by National Airport over unknown targets on the airport's radarscopes, yet the crew could see nothing unusual. Finally, as a crew member related, "the radar had a target which turned out to be the Wilson Lines steamboat trip toMount Vernon... the radar was sure as hell picking up the steamboat. "[40]Air Force Captain Harold May was in the radar center at Andrews AFB during the sightings of July 19–20. Upon hearing that National Airport's radar had picked up an unknown object heading in his direction, May stepped outside and saw "a light that was changing from red to orange to green to red again...at times it dipped suddenly and appeared to lose altitude." However, May eventually concluded that he was simply seeing a star that was distorted by the atmosphere, and that its "movement" was an illusion.[41]At 3 a.m. on July 27, anEastern Airlinesflight over Washington was told that an unknown object was in its vicinity; the crew could see nothing unusual. When they were told that the object had moved directly behind their plane, they began a sharp turn to try to see the object, but were told by National Airport's radar center that the object had "disappeared" when they began their turn.

At the request of the Air Force, theCAA's Technical Development and Evaluation Center did an analysis of the radar sightings. Their conclusion was that "a temperature inversion had been indicated in almost every instance when the unidentified radar targets or visual objects had been reported."[42]Project Blue Book would eventually label the unknown Washington radar blips as false images caused by temperature inversion, and the visual sightings as misidentified meteors, stars, and city lights.[43]In later years two prominent UFO skeptics,Donald Menzel,an astronomer atHarvard University,andPhilip Klass,a senior editor forAviation Weekmagazine, would also argue in favor of the temperature inversion/mirage hypothesis.[44]In 2002 Klass told a reporter that "radar technology in 1952 wasn't sophisticated enough to filter out many ordinary objects, such as flocks of birds, weather balloons, or temperature inversions."[20]The reporter added that "UFO proponents argue that even then seasoned controllers could differentiate between spurious targets and solid, metallic objects. Klass disagrees. It may be that 'we had two dumb controllers at National Airport on those nights'...[Klass] added that the introduction of digital filters in the 1970s led to a steep decline in UFO sightings on radar."[20]

Criticisms

[edit]

In his book,The Report On Unidentified Flying Objects,author Edward J. Ruppelt wrote that radar and control tower personnel he spoke to, as well as some Air Force officers, disagreed with the Air Force's explanation.[40]

Michael Wertheimer,a researcher for the government-fundedCondon Report,investigated the case in 1966, and stated that radar witnesses still disputed the Air Force explanation.[45]

Former radar controller Howard Cocklin told theWashington Postin 2002 that he was still convinced that he saw an object, stating that "I saw it on the [radar] screen and out the window" over Washington National Airport. "[16]

The Robertson Panel

[edit]

The extremely high numbers of UFO reports in 1952 disturbed both the Air Force and theCentral Intelligence Agency(CIA). Both groups felt that an enemy nation could deliberately flood the U.S. with false UFO reports, causing mass panic and allowing them to launch a sneak attack. On September 24, 1952, the CIA's Office of Scientific Intelligence (OSI) sent a memorandum toWalter B. Smith,the CIA's Director. The memo stated that "the flying saucer situation... [has] national security implications... [in] the public concern with the phenomena... lies the potential for the touching-off of mass hysteria and panic."[43]The result of this memorandum was the creation in January 1953 of theRobertson Panel.Howard P. Robertson,aphysicist,chaired the panel, which consisted of prominent scientists and which spent four days examining the "best" UFO cases collected by Project Blue Book. The panel dismissed nearly all of the UFO cases it examined as not representing anything unusual or threatening to national security. In the panel's controversial estimate, the Air Force and Project Blue Book needed to spend less time analyzing and studying UFO reports and more time publiclydebunkingthem. The panel recommended that the Air Force and Project Blue Book should take steps to "strip the Unidentified Flying Objects of the special status they have been given and the aura of mystery they have unfortunately acquired."[46]Following the panel's recommendation, Project Blue Book would rarely publicize any UFO case that it had not labeled as "solved"; unsolved cases were rarely mentioned by the Air Force.

[edit]
  • The tenth and final episode of the first season of the 2019History Channeltelevision seriesProject Blue Bookis titled "The Washington Merry-Go-Round". It's based on the 1952 Washington, DC UFO incident.[47]

References

[edit]

Notes

[edit]
  1. ^Peebles 1994,p. 73.
  2. ^Peebles 1994,p. 78.
  3. ^Ruppelt ch 11 "The Big Flap"
  4. ^Peebles, Ch5 "The 1952 Flap"
  5. ^Zempter, Glenda S. (1993)."New York Times Coverage of the 1952 UFO Scare".
  6. ^Ruppelt, p141
  7. ^Ruppelt, Edward J. (28 May 2022)."The Report on Unidentified Flying Objects".
  8. ^"The Spokesman-Review 04 Apr 1952, page 27".Newspapers.Retrieved11 February2024.
  9. ^"Green Bay Press-Gazette 02 Jun 1952, page Page 6".Newspapers.Retrieved11 February2024.
  10. ^Ruppelt, p. 109
  11. ^Arizona Republic
  12. ^Ruppelt, p. 131-132, "Other very reputable magazines, such asTrue,had said it before, but coming fromLife,it was different "
  13. ^Lubbock Evening Journalnewspapers
  14. ^Lang, Daniel (March 15, 1954)."The Man in the Thick Lead Suit".Oxford University Press. p. 49 – via Google Books.
  15. ^Mazur, Allan (July 5, 2017).Implausible Beliefs: In the Bible, Astrology, and UFOs.Routledge.ISBN978-1-351-51322-7– via Google Books.
  16. ^abcdefghijCarlson, Peter; Carlson, Peter (21 July 2002)."50 Years Ago, Unidentified Flying Objects From Way Beyond the Beltway Seized the Capital's Imagination".The Washington Post.
  17. ^Clark 1998,p. 653.
  18. ^abClark 1998,p. 654.
  19. ^Clark 1998,p. 655.
  20. ^abcdefgGilgoff, Dan (14 December 2001)."Saucers Full of Secrets".Washington City Paper.Retrieved23 January2024.
  21. ^Peebles 1994,p. 74.
  22. ^Ruppelt 1955,p. 160.
  23. ^abMichaels 1997,p. 22.
  24. ^Ruppelt 1955,p. 210.
  25. ^Ruppelt 1955,p. 162.
  26. ^abRuppelt 1955,p. 163.
  27. ^Peebles 1994,pp. 75–76.
  28. ^Ruppelt 1955,p. 164.
  29. ^Ruppelt 1955,p. 159.
  30. ^abPeebles 1994,p. 76.
  31. ^Clark 1998,p. 659.
  32. ^Ruppelt 1955,p. 166.
  33. ^Ruppelt 1955,p. 165.
  34. ^Peebles 1994,p. 77.
  35. ^abc"CIA's Role in the Study of UFOs, 1947-90 — Central Intelligence Agency".cia.gov.Archived fromthe originalon October 1, 2019.RetrievedJul 9,2019.
  36. ^Lewis-Kraus, Gideon (April 30, 2021)."How the Pentagon Started Taking U.F.O.s Seriously".The New Yorker magazine.Archived fromthe originalon 23 June 2023.
  37. ^"Page 2 Project Blue Book - UFO Investigations - Fold3".Minutes of Press Conference Held By Major General John A. Samford Director of Intelligence, U.S. air Force 29 July 1952 - 4:00p.m. - Room 3E-869, The Pentagon.
  38. ^Peebles 1994,p. 80.
  39. ^"Los Angeles Times: Archives - U.S. SAUCER HUNTER DOUBTS THEY EXIST".pqasb.pqarchiver.
  40. ^abRuppelt 1955,p. 170.
  41. ^Peebles 1994,p. 62.
  42. ^Peebles 1994,p. 66.
  43. ^abPeebles 1994,p. 79.
  44. ^Peebles 1994,p. 360.
  45. ^"Condon Report, Sec III, Chapter 5: Optical & Radar Analysis".files.ncas.org.
  46. ^Peebles 1994,p. 102.
  47. ^"Project Blue Book | TV Guide".TVGuide.RetrievedJul 9,2019.
  48. ^"Project Blue Book Unknown." Top Secret UFO Projects Declassified, season 1, episode 1, Netflix, 2021. Netflix,https:// netflix /watch/81066337

Sources

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=1952_Washington,_D.C.,_UFO_incident&oldid=1239860857"