1952 Washington, D.C., UFO Radar Incidents

Two July weekends and different observers

The Washington events were a cluster of reports across two July weekends, not one continuous encounter with a single verified object. Civil air-traffic controllers, military radar personnel, airline crews and ground observers contributed different observations around Washington National Airport, Andrews Air Force Base and the wider capital region. Project Blue Book preserved the reports because they involved operational radar, aviation traffic and a military response during an intense national wave of UFO publicity. [1] · [2] · [8]

During the night of 19-20 July, controllers reported unidentified returns that appeared and disappeared on scopes while several observers described lights in the sky. The surviving archival summaries establish a first weekend of radar and visual reports, but the public material does not provide a complete synchronized record linking each light to a particular radar track. That distinction prevents the episode from being treated as one fully measured target flying a continuous route over Washington. [1] · [5] · [8]

What the three radar sites reported

The better-preserved Project Blue Book case file for 26-27 July records returns on the Washington air-route traffic-control radar, the airport tower radar and the Andrews approach radar. Commercial and Civil Aeronautics Administration pilots also reported lights. One CAA crew described five glowing orange-to-white objects, while other accounts used terms such as a cigarette-like glow. The file says the main traffic-control display at times showed as many as twelve solid returns resembling aircraft returns but generally moving more slowly. [2] p. 3

The F-94 dispatch and missing flight reports

The Air Force Command Post was notified at 22:38 and the Air Defense Command chain at 22:45 on 26 July. Two F-94 interceptors were scrambled at about 23:00. Controllers attempted to vector the aircraft toward reported targets, usually without a successful intercept. The case file relays that one pilot reported four lights and later pursued one light he could not close on before it went out, but it also states that official interceptor reports had not reached the investigating office. The account is therefore a recorded operational report, not a complete flight-data package. [2] p. 3

The 26–27 July summary identifies its own limits at the outset: Fournet and Holcomb witnessed only part of the episode, and the rest was reported to them. Commercial and CAA pilots had not yet been contacted, and the office lacked the official interceptor reports. It describes two interceptor flights, distinguishing the first dispatch of two F-94s from a later flight that arrived after the strong returns had gone. Counting every passage as an independent, directly observed encounter would therefore overstate both the number of corroborating witnesses and the continuity of the tracking. [2] p. 3

Strong returns before the later weak echoes

Project Blue Book officers Major Dewey Fournet and Lieutenant John Holcomb reached the air-route traffic-control center around 00:15. Holcomb recorded seeing seven good, solid targets on the scope. A weather check found only a slight low-level temperature inversion at that time, and Holcomb doubted that it explained those strong returns. Later in the night, however, the operators saw dimmer, unstable returns that the report itself considered compatible with inversion effects. The contemporary file therefore contains both unresolved strong tracks and acknowledged weather-related clutter. [2] p. 3

What the later CAA tests established

The Civil Aeronautics Administration later conducted a technical study of unidentified radar targets at Washington and Indianapolis. Its May 1953 report concluded that many apparent targets could be secondary reflections produced by isolated refracting regions associated with temperature-inversion levels. The report gave a credible physical mechanism and documented conditions favorable to anomalous propagation during the summer of 1952. Its explicit Washington test conclusions concerned observations on 13 and 15 August, so it supports a class of explanation rather than proving that every return on both July weekends had that cause. [3]

The CAA report also explains why controllers could warn pilots without having identified an aircraft. A doubtful slow target on a possible collision course might be a helicopter, so a precautionary warning was preferable to ignoring genuine traffic. The study recommended more target plots, weather correlation and closer examination of individual echoes, including simultaneous observations with different radar bands. Those recommendations show the difference between managing an immediate traffic risk and determining the physical cause of a return. A warning or an intercept request is evidence of an operational response, not by itself an identification. [3]

The later Colorado Project interpretation

A later Colorado Project analysis, published in the Condon Report, reviewed the Washington case and judged most visual reports likely to involve meteors or scintillating stars, with the radar returns most likely caused by anomalous propagation. It also noted weak correlation among different radar sites and between radar and visual reports. That is an influential retrospective explanation, not a contemporaneous identification of each target; some reports remained too incomplete for a specific reconstruction. [5]

What remains supported and what remains open

The case belongs in the archive because official records confirm a consequential radar, aviation and military episode and also reveal why its strongest popular interpretation exceeds the evidence. Operators detected unexplained returns, pilots and observers reported lights, and interceptors were launched. The surviving record does not establish one structured craft, exceptional performance or non-human origin. DISPUTED with credibility B best reflects the combination of real operational documentation, incomplete correlation and technically plausible atmospheric explanations. [1] · [2] · [3] · [5]