Command Palette

Search for a command to run...

Washington National Airport

Airport

Washington National Airport radars anchored the 1952 Washington UFO flap and shaped official explanations afterward

Status — Confirmed

Washington National Airport, now Ronald Reagan Washington National Airport, opened for business on June 16, 1941, at Gravelly Point along the Potomac after President Franklin D. Roosevelt selected the site in 1938 and dedicated the field in 1940.12 Its place in UFO history comes from the Civil Aeronautics Administration air-route center and tower radars that repeatedly generated, confirmed, and relayed the July 1952 Washington radar-visual reports to Andrews, Bolling, the Pentagon, and Project Blue Book.345

  Airport and CAA setting

The airport was conceived as a federally sponsored, government-owned commercial airport for Washington, D.C., replacing inadequate earlier fields and becoming what the National Park Service describes as the nation's first federally constructed commercial airport.1 The original terminal and south hangar line served for years as a Civil Aeronautics Authority model airport, while its runway layout, control tower, lighting, and instrument landing systems influenced later airport design across the United States.1

That federal-civilian operating environment mattered in 1952 because the Washington Air Route Traffic Control Center radar was not an isolated military sensor; it was part of the CAA traffic-control system responsible for separating aircraft around the capital.3 CAA Technical Development Report No. 180 later stated that "scores" of unidentified targets on Washington ARTC radar had created publicity and raised concern about possible effects on air-traffic control.3

  July 1952 radar anchor

On July 19-20, 1952, radar scopes at Washington National Airport and Andrews Air Force Base tracked unexplained blips, and CIA historian Gerald Haines later summarized the episode as one that alarmed the Truman administration and drew White House attention.6 Project Blue Book material for the second weekend reported unidentified targets on the ARTC Center radar and tower radar at Washington National, with additional tracking by Andrews Approach Control and visual reports routed to Andrews, Bolling, and the National ARTC Center.4

The July 26-27 Air Force summary identified the electronic evidence as VG-2 radar in the ARTC Center and ASR-1 radar in the Washington National tower.4 It listed CAA controllers including Harry Barnes among the ARTC crew, described the tower radar operators as experienced and reliable, and noted that normal commercial and known USAF traffic at Washington National had been identified separately from the unknown returns.4

NodeRole in the July 26-27 record
Washington National ARTC CenterTracked repeated unidentified returns, coordinated with the Air Force Command Post, and vectored interceptors toward targets.4
Washington National towerUsed ASR-1 radar and recorded tower-to-Andrews coordination while a large target crossed the Andrews area.4
Andrews Air Force BaseProvided approach radar confirmation and received visual reports during the same sequence.45
Bolling Air Force BaseAppeared in the reporting chain for visual observations connected to the Washington National radar events.4
Pentagon and Project Blue BookProject Blue Book officer Maj. Dewey Fournet and Navy electronics specialist Lt. Holcomb arrived at the National ARTC Center after midnight to observe the scopes and assess the inversion explanation.45

  Incident sequence

The first publicized weekend began late on July 19, when National Airport radar operators and controllers saw multiple unexplained returns and asked Andrews to check its own equipment.56 A Capital Airlines flight inbound to National Airport reported an unidentified light following the aircraft from the Herndon area to within about four miles west of the airport, with the report matched on ARTC radar.5

The second major sequence began on July 26, when Washington National ARTC radar tracked multiple sharp returns and civilian pilots reported glowing white objects around the Washington area.5 The Air Force Command Post was notified at 22:38 EDT, two F-94 interceptors were scrambled from New Castle AFB, and Washington National controllers directed the fighters toward returns that generally failed to produce sustained visual contact.4

Fournet and Holcomb reached the National ARTC Center shortly after midnight on July 27 and observed several solid targets before requesting a second intercept flight.45 The same Air Force material also records that controllers distinguished those strong returns from later dim, unstable returns they assumed were likely related to temperature inversion, preserving the central dispute between witness impressions and the official atmospheric explanation.4

  Official interpretation

The Air Force's July 29, 1952, Pentagon press conference attributed the Washington sightings to temperature inversions and other conventional causes, while also announcing a strengthened scientific evaluation effort.5 Haines's CIA history says the Air Force quickly offered the temperature-inversion explanation after the Washington headlines, and that a later CAA investigation found such radar blips common under inversion conditions.6

CAA Technical Development Report No. 180 was narrower than the public flap itself: it analyzed unidentified targets observed on air-traffic-control radars and concluded that most targets in its Washington study periods were ground returns associated with low-level temperature inversions.3 The report also framed the operational risk as mostly a radar-clutter nuisance, while recommending better logging, weather correlation, and more flexible radar study to distinguish spurious targets from actual aircraft.3

  Blue Book and disclosure context

Washington National became the civilian-airport anchor for a case that linked CAA controllers, commercial pilots, Andrews radar, Bolling reporting, Pentagon intelligence officers, and Project Blue Book files.45 NARA's Blue Book overview records that the Air Force later transferred the program's documentation to the National Archives and concluded, at program close, that investigated UFO reports showed no evidence of national-security threat, advanced technology beyond known science, or extraterrestrial vehicles.7

The airport therefore sits at an important intersection in early Cold War UFO history: it was not a remote base or folklore site, but a high-traffic civilian control center whose radars forced national-security officials to treat unusual returns as an air-traffic, public-information, and intelligence problem at the same time.367 See the Washington D.C. UFO Wave for the broader sighting chronology.5

  Current identity

The federal government transferred direct operation of National and Dulles to the Metropolitan Washington Airports Authority in 1987, and Congress renamed Washington National Airport as Ronald Reagan Washington National Airport in 1998.2 The airport's official designator is DCA, and MWAA continues to operate it as part of the region's two-airport system with Washington Dulles International Airport.28

  References

  References

  1. nps.gov 2 3

  2. flyreagan.com 2 3

  3. rosap.ntl.bts.gov 2 3 4 5 6

  4. project1947.com 2 3 4 5 6 7 8 9 10 11 12 13

  5. project1947.com 2 3 4 5 6 7 8 9 10

  6. cia.gov 2 3 4

  7. archives.gov 2

  8. flyreagan.com

Published on June 16, 1941

6 min read