The 1952 Washington DC UFO Flap

0:00Your SoCal Honda dealers are honored to help the community. Our program started the first deaf and hard of hearing football team of its kind in our league. The helpful SoCal Honda dealers surprised us with brand new uniforms giving our athletes more than just jerseys. A community investing in their program. And we want to help you too with 1.99% APR on a 2026 Rigeline for well-qualified buyers. At your SoCal Honda dealers, made through contract limited bus finance, our SoCal Honda financial services, not all buyers will qualify to take delivery by 1126. When you've got a job to do, Lowes knows how to help you keep it moving. Milo's pro rewards members save more with member volume discounts on eligible orders through a quote of $2,000 or more.

1:02Plus, safe time with job site delivery on select purchases. Not a member, join for free today. Exclusions, more terms and restrictions apply can be combined with any other discount, including but not limited to contract and or special price and loyalty programs subject to time. The most important thing is to get a free list of your own. This is episode 154 of UFO encounters. In this episode, I'm talking about the 1952 Washington DC UFO flap. Washington DC became the center of all the world's most popular platforms. This is episode 154 of UFO encounters. In this episode, I'm talking about the 1952 Washington DC UFO flap. Washington DC became the center of one of the most remarkable UFO episodes in American history during two weeks in July 1952. Unknown objects appeared on radar around the nation's capital. Airline pilots and military personnel reported unusual lights,

2:06and the United States Air Force fighters were sent into the area in an attempt to identify what was happening. The objects seemed to appear and disappear without warning, sometimes moving slowly, and at other times apparently accelerating away at extraordinary speed. The events took place close to some of the most sensitive buildings in the United States, including the White House, Capital and Pentagon, creating an obvious security concern. What became known as the Washington DC UFO flap unfolded mainly during the nights of 19th to 20th of July and 26th to 27th of July 1952 and became one of the most widely reported UFO incidents of the period. The first major incident began shortly before midnight on Saturday 19th of July, when air traffic controller Edward Nugent noticed seven unidentified targets on his radar screen at Washington National Airport.

3:07The targets were approximately 15 miles south southwest of Washington and did not correspond with any known aircraft in the area. They were also outside the normal flight paths used by commercial traffic. Nugent called the attention of his senior controller Harry Barnes who watched the returns for himself. Barnes was an experienced controller and believed the movements were unlike those of normal aircraft. Before assuming that something unusual was actually in the sky, the controllers checked the radar equipment and found no obvious fault. The targets remained, moving in ways that continued to attract the attention of the men monitoring the screen. Confirmation soon came from another radar installation at Washington National Airport. Barnes contacted the airport control tower, where controllers Howard Cochlin and Joe Zaco were using a separate radar set. They too reported unidentified targets.

4:10Cochlin then looked outside and saw a bright light hovering in the distance. As he watched, the light appeared to move away quickly. This was important because the incident was no longer confined to a single radar screen. Separate operators using different equipment were reporting unexplained returns, while at least one controller believed he could see something in the sky corresponding with the activity. The possibility of a simple equipment fault became harder to accept as the reports continued to build. The unidentified returns began appearing across different parts of the radar screen, including areas close to the centre of Washington. Some seemed to move near the White House and capital, prompting Barnes to contact Andrew's Air Force Base around 10 miles from Washington National Airport. Andrew's initially reported nothing unusual on its radar, but personnel at the base soon began making their own observations.

5:10Airman William Brady, who was working in the control tower, reported seeing what looked like an orange ball of fire with a tail. As he attempted to draw the attention of other personnel to it, the object appeared to move away at tremendous speed. Staff Sergeant Charles Davenport also reported an orange red light that appeared stationary before changing direction and altitude. Commercial pilots added another layer to the mystery as the night progressed. Capital Airlines pilot SC Pyraman was sitting in his DC-4 at Washington National Airport waiting for permission to take off when he noticed unusual lights. Over approximately 14 minutes, he reported seeing several bright objects moving rapidly through the sky. Pyraman remained in radio contact with the controllers, while the observations were taking place, allowing them to compare what he was describing with what appeared on their radar screens. According to Barnes, some of Pyraman's visual sightings seemed to match targets visible near his aircraft.

6:16When Pyraman reported one of the lights suddenly moving away, the corresponding radar return also disappeared. The apparent agreement between a pilot's visual observations and the radar picture became one of the most compelling features of the night. Radar operators at Washington National and Andrews continued following unidentified returns into the early hours of 20th of July. The targets behaved inconsistently, sometimes remaining almost stationary, and at other times moving across the screen before disappearing. Controllers attempted to determine whether they were seeing aircraft, whether effects, or some other form of interference, but no simple explanation emerged. At one stage, more than one radar installation reportedly followed an unknown target in the same general area. The continued uncertainty was serious enough for the Air Force to send to F-94 Starfire Jet Interceptors from Newcastle Air Force Base in Delaware.

7:20The fighters reached the Washington area at around 3 o'clock in the morning, but by then most of the unidentified targets had faded or disappeared from the radar screens. The arrival of the fighters did little to solve the mystery. Controllers attempted to guide the jets towards the locations where unidentified returns had been appearing, but the pilots were unable to make a clear interception. The targets seemed difficult to locate once the aircraft entered the area, and after some time the fighters were forced to leave because of fuel limitations. Shortly after their departure, unidentified returns reportedly began appearing again. Barnes later said the timing gave him the impression that the objects might somehow have been aware of the military aircraft, although there was no way to establish this. The remaining targets eventually disappeared in the early morning, bringing the first night of activity to end without any object being identified.

8:21A second wave of unexplained activity began almost exactly one week later during the night of Saturday 26th July to Sunday 27th July. Controllers at Washington National Airport once again detected unknown targets moving through the airspace around the capital. The similarity to the previous weekend immediately raised concern, and radar operators treated the returns seriously from the beginning. Reports of unusual lights also came from observers on the ground and from pilots in the area. The repetition made the situation much more difficult to dismiss as an isolated technical problem or a single mistaken observation. Air Force fighters were again sent towards Washington, and this time the attempts to intercept the unidentified objects became more intense. Radar controllers directed F-94 pilots towards the positions of the unknown targets, but the contacts repeatedly proved elusive.

9:25Some disappeared as the fighters approached, while others remained visible on radar without corresponding visual sightings from the pilots. One of the most frequently discussed moments came when Lieutenant William Patterson reported seeing several bright lights and attempted to move closer to them. According to later accounts of the incident, the lights appeared to surround his aircraft before disappearing. Patterson was unable to identify them, and no physical object was intercepted or recovered. The sight of military fighters operating over the nation's capital, while controllers attempted to direct them towards unknown radar targets, created obvious concern. The United States was deep in the Cold War, and unidentified aircraft approaching Washington could not simply be ignored. Radar systems formed an important part of national defence, and the possibility that unknown aircraft might be penetrating restricted airspace demanded attention.

10:27News organizations quickly learned that fighters had been scrambled, and reports of the Washington incidents appeared across the country. UFO sightings were already receiving widespread attention during the summer of 1952, but the appearance of unexplained targets over the capital gave the subject a new level of seriousness. The growing public attention led Major General John Samford, the Air Force Director of Intelligence, to hold a major press conference at the Pentagon on 29 July. He was joined by Major General Roger Raimi and other officers familiar with radar and the Air Force UFO Investigation Program. Samford acknowledged that some reports came from credible observers, who appeared to have seen something they could not explain. He also stated that the Air Force had found no evidence that the sightings represented a threat to the United States. Much of the discussion centered on the possibility that unusual atmospheric conditions had affected radar performance and visual observations around Washington.

11:35No aircraft, wreckage, or physical object was ever recovered as a result of the Washington incidents, and none of the fighter pilots succeeded in making a positive identification. The events therefore ended in much the same way it had begun, with experienced observers reporting something unusual, but without enough evidence to establish exactly what they had encountered. The radar context may have included a mixture of atmospheric effects, ordinary objects, and genuine unknowns, while some of the visual sightings could have had conventional explanations. What remains striking though is the scale of the response. Over two consecutive weekends, unidentified targets appeared on radar near the American capital. Pilots and ground observers reported strange lights. Military fighters were sent to investigate, and senior Air Force officials were forced to answer questions publicly. The 1952 Washington DC UFO flap endures because, despite the explanations offered afterwards, the events themselves were never reduced to one clear cause.

12:44Leaving behind a case in which radar, visual observation, and military response came together, without producing a final answer. In this episode I was talking about the Washington DC 1952 UFO flap. A my book, which is titled Aspects of Alien Abduction, is on Amazon, and you can get it in paperback, audio book, and Kindle. And if you enjoy this episode, please leave a review, and be sure to subscribe on Apple podcasts, Spotify, or via your favourite podcast app to make sure that you don't miss out on any episodes. And thanks for listening.