Black Friday: S4 Declassification opens Nov 27, 2:14 AM ET

UFO115
Sign in Cartitems: 0
A night view across the river toward the capital, with orange glows low in the sky. AI-generated.

BEYOND THE PERIMETER

The Washington, D.C. UFO Incidents — 1952

Radar blips over the White House. Jets that found nothing. A press conference that explained it as weather.

UFO115-INC-1952-00119 July 1952Washington, D.C. (Washington National Airport / Andrews Air Force Base), United StatesOfficially investigated

AI-generated artistic reconstruction. UFO115 dramatization, not evidence and not a photograph of the event.

On the nights of 19 July and 26 July 1952, controllers at Washington National Airport and Andrews Air Force Base tracked unidentified radar targets while pilots and airmen reported lights, and F-94 jets were sent up from Delaware [1][4]. The reports reached the front pages, and after the second weekend President Truman had his air force aide call Project Blue Book chief Edward Ruppelt and ask for an explanation [1]. On 29 July Maj. Gen. John Samford held the largest Pentagon press conference since the Second World War and said the radar returns could be explained by temperature inversion, while calling that explanation about a 'fifty-fifty proposition' [1][4]. The Civil Aeronautics Administration (CAA) linked the targets to inversions and Project Blue Book settled on weather and misidentification, but some radar and control tower personnel and some Air Force officers disagreed [1].

WHAT KIND OF CLAIM IS THIS?

  • 2 DOCUMENTEDEstablished by records or contemporary reporting.
  • 2 OFFICIALWhat an official body stated or concluded.
  • 2 WITNESSWhat a witness reported. Not independently established.
  • 1 DISPUTEDContested between sources.
  • 1 ALLEGEDA claim made later, unsupported by the record.
  • 1 DRAMATIZEDUFO115 reconstruction, not evidence.
  1. DOCUMENTED At 11:40 p.m. on 19 July 1952 a Washington National Airport controller saw seven unidentified objects on radar, and no known aircraft were in the area [S1][S4]. [1][4]
  2. OFFICIAL On 29 July 1952 Maj. Gen. John Samford told a Pentagon press conference that the radar targets could be explained by temperature inversion and the visual sightings by stars or meteors [S1]. [1]
  3. OFFICIAL The Civil Aeronautics Administration technical centre concluded that an inversion had been indicated in almost every instance of unidentified targets or visual objects [S1]. [1]
  4. WITNESS Capital Airlines pilot Casey Pierman reported six fast-moving white lights over 14 minutes, and Barnes said each corresponded to a blip that vanished from the scope [S1]. [1]
  5. DISPUTED Chop recalled Lt. William Patterson saying 'I see them now and they're all around me'; a contemporary newspaper account has Patterson seeing two or three lights he could not rule out as reflections of ground lights or stars [S3][S4]. [3][4]
  6. WITNESS Lt. John Holcomb, a Navy radar specialist, judged the reported inversion not nearly strong enough to explain the 'good and solid' radar returns [S1]. [1]
  7. ALLEGED Life magazine suggested in August 1952 that the Air Force had known more about the blips than it admitted, and the City Paper says some read the Air Force's reluctance to address UFOs as a conspiracy [S3]. [3]
  8. DOCUMENTED The CAA's 1953 report drew on weather data from 13 and 14 August 1952, not from the two July weekends [S3]. [3]
  9. DRAMATIZED The 2019 History Channel series Project Blue Book dramatised the incident in an episode titled 'The Washington Merry-Go-Round' [S1]. [1]

WHAT HAPPENED

At 11:40 p.m. on Saturday 19 July 1952, Edward Nugent, an air traffic controller at Washington National Airport, saw seven objects on his radar, south-southwest of the city [1]. No known aircraft were in the area and the objects were not following established flight paths [1]. Senior controller Harry Barnes had two controllers check the set, and they found it working normally [1]. Controllers in the airport tower, Howard Cocklin and Joe Zacko, reported unidentified blips of their own and a hovering bright light that departed at great speed [1]. When objects moved over the White House and the Capitol, Barnes called Andrews Air Force Base, where Airman William Brady in the tower saw an orange ball of fire [1]. At 3 a.m., shortly before two F-94 Starfire jets from New Castle Air Force Base in Delaware arrived, the objects vanished from the National Airport radar; they returned after the jets left and were last detected at 5:30 a.m. [1].

A week later, at 8:15 p.m. on 26 July, a National Airlines pilot and stewardess saw lights above their plane, and within minutes both radar centres at National and the radar at Andrews were tracking more unknown objects [1]. Two F-94s arrived at 11:30 p.m., and the sightings and radar returns ended at sunrise on 27 July [1]. The Air Force held a press conference on 29 July [1].

At 11:40 p.m. on 19 July 1952 a Washington National Airport controller saw seven unidentified objects on radar, and no known aircraft were in the area [S1][S4].

DOCUMENTED From the file [1][4]

BACKGROUND

UFO historian Curtis Peebles called the Washington incident 'the climax of the 1952 (UFO) flap' [1]. In the four years before the flap the Air Force had logged 615 UFO reports; during the 1952 flap it received more than 717 new ones [1]. Project Blue Book director Edward Ruppelt recalled that 148 leading newspapers carried over 16,000 items about flying saucers in six months [1]. Life magazine had published 'Have We Visitors From Space?' on 7 April, and the publicity is believed to have contributed to the summer wave [1].

Ruppelt wrote that reports had already built up around Washington earlier in July, including airliner crews who reported lights or UFOs on 10, 13 and 14 July [2]. National Airport had two radars, a long-range set in the Air Route Traffic Control (ARTC) section and a shorter-range set in the control tower, and Andrews, about ten miles further east, had a third [2]. On 26 July Andrews had no interceptors because its runways were being rebuilt, so F-94s came from New Castle, Delaware, about 90 miles away [4]. Officials were also anxious: the CIA's Office of Scientific Intelligence warned in a 24 September 1952 memo of the 'potential for the touching-off of mass hysteria and panic' [1].

CHRONOLOGY

  1. Airliner crews report lights near Washington and Newport News, according to Ruppelt's later account [S2]. [2]

  2. Nugent sees seven objects on radar at National Airport; the National tower has blips too, and lights are seen from the National and Andrews towers [S1][S4]. [1][4]

  3. Objects vanish from National's radar shortly before F-94s arrive, return when the jets leave, and are last detected at 5:30 a.m. [S1]. [1]

  4. The Air Force discloses the reports to the press on the evening of 21 July; on 22 July General Landry's office asks for details at the President's request [S2]. [2]

  5. A National Airlines crew sees lights above their plane, and radar again tracks unknown objects [S1]. [1]

  6. F-94s from New Castle arrive at 11:30 p.m.; Fournet and Holcomb reach the National Airport radar center after midnight [S1]. [1]

  7. Samford and Ramey hold the Pentagon press conference, the largest since the Second World War [S1]. [1]

  8. The Robertson Panel meets for four days to review cases [S1]. [1]

  9. The CAA technical centre reports that an inversion was indicated in almost every instance [S4][S1]. [4][1]

WITNESS ACCOUNTS

Barnes later wrote that 'we knew immediately that a very strange situation existed' and that the movements were 'completely radical compared to those of ordinary aircraft' [1]. Capital Airlines pilot S. C. 'Casey' Pierman reported six white, tailless, fast-moving lights over 14 minutes, and Barnes said each sighting coincided with a pip near his plane that vanished from the scope when the light streaked away [1]. At Andrews, Airman William Brady described an orange ball of fire trailing a tail, and Staff Sgt. Charles Davenport described an orange-red light that would stand still and then change direction abruptly [1].

On 26 July, Lt. William Patterson, one of the F-94 pilots, said he saw four white glows and could not close on them, while his flight leader, Capt. John McHugo, saw nothing [1]. Albert Chop, the Blue Book press spokesman, recalled decades later that Patterson said 'I see them now and they're all around me' and that nobody answered [1][3][4]. A contemporary newspaper account instead had Patterson seeing two or three lights about ten miles away and not ruling out reflections of ground lights, or even stars [4]. Lt. John Holcomb, a Navy radar specialist, counted seven good, solid targets and did not think the reported inversion was strong enough to explain them [1][4]. Cocklin told the City Paper he thought at the time it was 'something alien' and still did; Chop said much the same [3].

Dim radar room with a lavender circular scope and figures seen from behind watching it
AI RECONSTRUCTIONA dim radar room with a circular scope showing a cluster of unidentified returns, as controllers at Washington National Airport described the night of 19 July 1952. AI reconstruction. AI-generated artistic reconstruction. UFO115 dramatization, not evidence and not a photograph of the event.

#NOMORESECRETS

WEAR THE STORY.

The full collection

WHAT THE INVESTIGATIONS FOUND

On 29 July 1952 Maj. Gen. John Samford, Director of Intelligence, and Maj. Gen. Roger Ramey, Director of Operations, gave what was the largest Pentagon press conference since the Second World War [1]. Samford said the visual sightings could be misidentified stars or meteors and that the unknown radar targets could be explained by temperature inversion; he also said the radar contacts were not caused by solid material objects and posed no threat [1]. He called the inversion explanation about a 'fifty-fifty proposition' [3][4]. Asked how radar had steered an airline pilot to lights he then saw, he said 'I can't explain that' [3][4]. An Air Force inspector general memo of the same day recorded that the Director of Intelligence considered the objects 'unexplained' [3].

The CAA's Technical Development and Evaluation Center concluded that an inversion had been indicated in almost every instance of unidentified radar targets or visual objects [1]. The City Paper notes that its report drew on weather data from 13 and 14 August 1952, not from the two July weekends [3]. Project Blue Book eventually labelled the radar blips as false images from inversion and the visual sightings as misidentified meteors, stars and city lights [1]. In January 1953 the CIA-sponsored Robertson Panel reviewed cases and recommended that the Air Force and Blue Book strip UFOs of their 'aura of mystery' [1][4].

EXPLANATIONS

The official explanation was temperature inversion, a layer of warm air over cooler air that can bend radar signals and produce false returns [1]. The astronomer Donald Menzel and the Aviation Week editor Philip Klass later argued the same case [1]. In 2002 Klass said that 1952 radar was not sophisticated enough to filter out ordinary objects such as birds, weather balloons or inversions, and suggested that 'we had two dumb controllers at National Airport on those nights' [1]. Some individual sightings had specific answers: a B-25 crew member said one radar target turned out to be the Wilson Lines steamboat trip to Mount Vernon [1], Capt. Harold May at Andrews concluded that a changing red, orange and green light was a star distorted by the atmosphere [1], and a fighter pilot on dawn patrol reported seeing two little patches of clouds and a lot of shooting stars [4].

The weather explanation has its own problems. Holcomb said the inversion was not nearly strong enough to account for the returns [1], and Ruppelt noted that an inversion formed over Washington on almost every night that summer without the scopes filling with targets [4]. A 1969 Air Force study of mirages found that inversions could not produce visual UFO sightings, though it did not address radar [3]. The researcher Jacques Vallée, writing in 1965, regarded the case as 'rather poor' by the standards of UFO files [1].

WHAT REMAINS DISPUTED

Some of those who watched the scopes never accepted the weather explanation [1]. Ruppelt wrote that radar and control tower personnel he spoke to, and some Air Force officers, disagreed with the Air Force explanation [1]. Michael Wertheimer, a researcher for the Condon Report, found in 1966 that radar witnesses still disputed it [1]. Cocklin told the Washington Post in 2002 that he saw the object 'on the screen and out the window' [1][4].

The record also disagrees with itself. Chop remembered the objects vanishing the instant the F-94s appeared and returning when they left [3], while Ruppelt's account has them relocating to Newport News, Virginia [3]. Ruppelt's own claim that nobody told Air Force Intelligence is countered by telex messages sent on 20 July, which suggest the report got little attention until it reached the press [2]. The City Paper reports that some people read the Air Force's reluctance to discuss UFOs as a conspiracy [3], while Saturday Night Uforia argues that the Air Force was caught unprepared rather than covering anything up [2].

QUESTIONS PEOPLE ASK

What happened over Washington in July 1952?

Controllers at Washington National Airport and Andrews Air Force Base tracked unidentified radar targets on the nights of 19 and 26 July, and pilots and airmen reported lights [1][4]. Jets from New Castle, Delaware, were sent up on both nights [1].

Did the Air Force explain the sightings?

Yes. Maj. Gen. John Samford said on 29 July 1952 that the radar targets could be explained by temperature inversion and the visual sightings by stars or meteors, though he called the inversion explanation about a fifty-fifty proposition [1][4].

Did President Truman take an interest?

Yes. After the 26–27 July sightings Truman had his air force aide call Ruppelt and ask for an explanation; Truman listened on a separate phone but asked no questions [1].

Did the controllers accept the weather explanation?

Not all of them. Cocklin told the Washington Post in 2002 that he saw the object on the screen and out the window [1], and Ruppelt wrote that radar and tower personnel disagreed with the Air Force [1].

What came of the CIA's interest?

The CIA set up a study group in 1952, and in January 1953 the Robertson Panel spent four days examining cases and recommended debunking and public education [1][4].

THE RECONSTRUCTION

A night view across the river toward the capital, with orange glows low in the sky. AI-generated.
AI RECONSTRUCTIONAI-generated artistic reconstruction. UFO115 dramatization, not evidence and not a photograph of the event.

A night view across the river toward the capital, with orange glows low in the sky. It shows what witnesses reported seeing, not an established object, and the small figures watch from a distance.

AI-generated artistic reconstruction. UFO115 dramatization, not evidence and not a photograph of the event. Hero image source: UFO115 reconstruction (local AI model, 2026).

SOURCES

  1. 1952 Washington, D.C., UFO incident. Wikipedia, read 2026-11-14. Read 2026-11-14. Link checked 2026-11-14 (HTTP 200).
  2. Saturday Night Uforia: General Samford Meets The Press. saturdaynightuforia.com, read 2026-11-14. Read 2026-11-14. Link checked 2026-11-14 (HTTP 200).
  3. Saucers Full of Secrets. Washington City Paper, read 2026-11-14. Read 2026-11-14. Link checked 2026-11-14 (HTTP 200).
  4. 1952 Washington UFO Sightings: Jets Scrambled Over the Capitol. ghostsofdc.org, read 2026-11-14. Read 2026-11-14. Link checked 2026-11-14 (HTTP 200).

CITE THIS RECORD

UFO115. "The Washington, D.C. UFO Incidents — 1952." UFO115 Evidence Timeline, record UFO115-INC-1952-001, version 1. Last reviewed 2026-11-14. https://ufo115.com/evidence-timeline/incidents/washington-d-c-incidents-1952

APA: UFO115. (2026). The Washington, D.C. UFO Incidents — 1952 (Record UFO115-INC-1952-001, v1). UFO115 Evidence Timeline. https://ufo115.com/evidence-timeline/incidents/washington-d-c-incidents-1952

MLA: "The Washington, D.C. UFO Incidents — 1952." UFO115 Evidence Timeline, UFO115, 2026-11-14, https://ufo115.com/evidence-timeline/incidents/washington-d-c-incidents-1952.

Last reviewed by The UFO115 desk. Record UFO115-INC-1952-001, version 1. Machine-readable record.

“BEYOND THE PERIMETER” is UFO115's editorial framing, not a claim that events happened as dramatized.