Anomaly•Registry
AR-0144

The Washington, D.C. UFO Flap

Partially explained
Date 19 to 20 July and 26 to 27 July 1952
Location Washington, D.C., United States, and its approaches. The coordinates are Washington National Airport (now Ronald Reagan Washington National Airport), whose radars tracked the targets.
Coordinates 38.8521, -77.0377
Category Sky and Atmospheric

Summary

On two weekends in July 1952 radar at Washington National Airport tracked unidentified targets over the capital, including the prohibited airspace over the White House and the Capitol, while pilots and tower staff reported lights. Air Force jets were sent up; they found nothing on the first weekend, and on the second one pilot saw lights he could not close on.

The Air Force's press conference of 29 July was reported as blaming temperature inversions, though the Air Force's own investigator still carried the sightings as unknown. Later analyses, a Civil Aeronautics Administration study of 1953 and the Condon Report of 1968, concluded that the radar targets were most likely anomalous propagation and the lights mostly meteors and stars. The radar operators of 1952 disputed it at the time, and the verdict on record is "most likely", not certain.

the radar room in 1952, against the analyses of 1953 and 1968 THE RADAR ROOM, 1952 19 to 20 and 26 to 27 July eight targets at 11.40 pm, through the prohibited areas over the White House "very probably caused by solid metallic objects" the inversion "never strong enough" (Ruppelt) LATER ANALYSES CAA 1953; Condon Report 1968 targets moved with the upper winds at twice the wind speed radar returns "most likely" anomalous propagation lights: most probably meteors and stars, "with one or two possible exceptions" THE VERDICT ON RECORD IS "MOST LIKELY". the analyses fit the radar tracks; the 1952 observers disputed them, and one or two visual reports remain unidentified. Ruppelt: the 29 July inversion "answer" was the press's.
Figure Drawn by Anomaly Registry from Ruppelt's account (1956) and the Condon Report (1968), including Loren W. Crow's weather analysis and Gordon Thayer's summary of the 1953 Civil Aeronautics Administration study by Borden and Vickers. The left box is what the radar room said in July 1952; the right box is what the later analyses found.

What is documented

The first weekend. At 11.40 pm on Saturday 19 July 1952 two radars at Washington National Airport picked up eight unidentified targets. The radar at the airport's control tower also showed unidentified targets, and so did the radar at Andrews Air Force Base; Ruppelt records the tower operators at Andrews seeing "a huge fiery-orange sphere" hovering over their range station. Shortly after midnight a controller called the pilot of a Capital Airlines flight just taking off from National, who saw a light and over the next fourteen minutes reported six more. When he called out a light to his right and said it had gone, the controller saw a target to the right of the airliner disappear from the scope. The targets moved into every sector of the scope, through the prohibited areas over the White House and the Capitol. Most "loafed along at 100 to 130 miles an hour", with sudden bursts of speed; one was "clocked at 7,000 miles an hour". Interceptors were requested repeatedly. An F-94 arrived just about daylight, after the targets had gone, and its crew found nothing unusual.

The second weekend. The targets returned at about 10.30 pm on Saturday 26 July. By midnight two F-94s from New Castle County Air Force Base in Delaware were airborne. One pilot, Lieutenant William Patterson, reported: "I saw several bright lights. I was at my maximum speed, but even then I had no closing speed." Major Dewey Fournet went to the radar room with Lieutenant Holcomb, a Navy electronics specialist, and reported that everyone there was convinced the targets were "very probably caused by solid metallic objects".

Inversions. There was a temperature inversion on each night of the sightings. Edward Ruppelt, who ran Project Blue Book, judged that it was "never strong enough to affect the radar the way inversions normally do", and noted that inversions occurred on nearly every night of that summer while the targets appeared on only a few. When President Truman's air aide, Brigadier General Landry, called Air Force intelligence at the President's request, Ruppelt told him the targets could have been caused by weather but that there was no proof.

The press conference. On Tuesday 29 July at 4 pm Major General John Samford held what Ruppelt called "the largest and longest the Air Force had held since World War II". Captain Roy James, who had arrived in Washington that morning, handled the radar questions. Samford, in Ruppelt's account, "had to hedge on many answers" because he did not know them. Ruppelt wrote that the press took James's remarks on temperature inversions as the Air Force's answer, with headlines such as "AIR FORCE DEBUNKS SAUCERS AS JUST NATURAL PHENOMENA". Writing in 1956, Ruppelt said the twin sightings were "still carried as unknowns".

The wave. At the height of the 1952 wave, reports to Project Blue Book ran, in Ruppelt's account, at around forty a day, about a third of them classed as unknowns.

The later analyses. A 1953 study of radar tracks by Borden and Vickers for the Civil Aeronautics Administration found such targets moving with the upper winds at twice the wind speed, which suggested ground returns seen by partial reflection from moving layers of air. For the University of Colorado study directed by Edward U. Condon, the consulting meteorologist Loren W. Crow concluded in 1968 that "the conditions of the atmosphere were capable of generating anomalous propagation" on weather radar on both nights. The study's radar analyst, Gordon Thayer, concluded that the unidentified returns "were most likely the result of anomalous propagation (AP)", and that the visual objects were, "with one or two possible exceptions", most probably meteors and scintillating stars.

Leading explanations

Anomalous propagation in temperature inversions, for the radar targets (the CAA study of 1953 and the Condon Report of 1968; probable, disputed at the time). Under an inversion, radar energy can be bent back towards the ground and return echoes from ground features that appear as targets. Borden and Vickers read the targets' movement with the upper winds, at twice the wind speed, as the mark of reflections from moving layers of air. The operators of 1952 and Ruppelt thought the inversions too weak; the later analysts found the atmosphere capable of it on both nights.

Meteors and stars, for the lights (the Condon Report; probable for most). Thayer identified the visual objects as most probably meteors and scintillating stars, with one or two possible exceptions.

Solid unidentified objects (the view of the radar operators and some officers in 1952; not supported by the later analyses). Ruppelt considered the experience of the radar men, who dealt in human lives, the one big factor in favour of the targets being real. No physical evidence of any object was produced.

What the popular version gets wrong

"The Air Force explained it at the time as temperature inversions." In Ruppelt's account Samford hedged, the radar officer had arrived that morning, and the inversion answer was the press's reading of his remarks. Blue Book still carried the sightings as unknowns years later. The case for inversions rests on the analyses of 1953 and 1968, not on the press conference.

"Radar experts ruled out temperature inversions." The men in the radar room in 1952 did reject them, and so did Ruppelt. The later studies disagreed: the targets moved with the upper winds at twice the wind speed, and the atmosphere on both nights could have produced anomalous echoes. The disagreement is real, and the later verdict is "most likely", but it is not true that the experts who studied the tracks ruled inversions out.

Current status

Partially explained. The radar targets are most likely anomalous propagation, on the evidence of the 1953 and 1968 analyses, and most of the lights were most probably meteors and stars. What is not settled is a small residue: one or two visual reports, the reported coincidences between pilots' lights and radar targets, and the conviction of experienced radar operators that they were tracking solid objects. It is unlikely that any new record will settle it.

Sources

  • Ruppelt, E. J. (1956). The Report on Unidentified Flying Objects. Garden City, NY: Doubleday. Chapter 12, "The Washington Merry-Go-Round". Chapter text at sacred-texts.com; Project Gutenberg edition.
  • Thayer, G. (1968). "Optical and Radar Analyses of Field Cases." In E. U. Condon (scientific director), Scientific Study of Unidentified Flying Objects, Section III, Chapter 5. University of Colorado, under contract to the United States Air Force. Internet edition by the National Capital Area Skeptics.
  • Crow, L. W. (1968). "Weather Conditions and Radar Echoes near Washington, D.C., and Norfolk, Va., on 19-20 and 26-27 July 1952." Appendix L in Scientific Study of Unidentified Flying Objects. Dated 1 April 1968.
  • Borden and Vickers (1953). Civil Aeronautics Administration study of unidentified radar targets. Known to the registry through the Condon Report's account of it.
  • Condon, E. U. (scientific director) (1968). Scientific Study of Unidentified Flying Objects. University of Colorado. Preface dated 31 October 1968.

Last reviewed: September 2026. Records are provisional. Where the evidence changes, the entry changes. Found an error? Tell us.

Related records
AR-0137 The Mantell Incident A Guard pilot died chasing an object over Kentucky in 1948. He blacked out without oxygen; the object was probably a secret balloon. 7 January 1948 Later explained
AR-0130 Kenneth Arnold's Sighting In 1947 a pilot timed nine bright objects between two Washington peaks. The press called them flying saucers; he said he meant how they moved. 24 June 1947 Unsolved
AR-0063 The Lubbock Lights An arc of lights over Texas, investigated by the US Air Force. Usually put down to birds, which the investigator himself rejected. August 1951 Partially explained
AR-0015 Hessdalen Lights Recurring luminous phenomena in a Norwegian valley, under active scientific study. Documented since 1981 Partially explained

Advertise on Anomaly Registry

A documentary archive of 175 investigated cases, read slowly and at length by an audience that arrives on purpose. Below are the current delivery figures and what is available to buy.

Figures are rolling daily averages, current as of September 2026. They are restated as the traffic changes rather than left to age quietly, and we are happy to screen-share the underlying Ad Manager and analytics reporting before an insertion order is signed.

Anomaly Registry is a reference archive rather than a feed. Every one of its 175 records is written to a fixed structure, sourced to contemporaneous documents, inquest files, peer-reviewed literature or credible reporting, and each carries a section setting out precisely what the popular version of the story gets wrong. Cases that were later explained and cases that were comprehensively debunked are kept alongside the unsolved ones, because an archive that keeps only its mysteries is not an archive. That editorial position is the reason people stay.

It also explains the shape of the traffic. A session here runs to more than four pages and close to nine minutes, which is several times what a typical content site sees. Readers arrive looking for one case, find the sources laid out, and follow the cross-references into the next record. For an advertiser, the practical consequence is that a banner on this site is in front of a settled, attentive reader for minutes rather than seconds, and it is seen repeatedly across a single visit without ever being the reason someone leaves.

Three placements are available on every page. The leaderboard sits above the masthead and accepts 728x90, 970x90 and 320x50. The in-article unit sits inside the body of the record, where the reader is already stopped, and accepts 728x90, 300x250 and 336x280. The footer unit closes the page and accepts 728x90, 970x90 and 320x50. There are three slots per page and there will not be a fourth: the inventory is deliberately limited so that each impression is worth more than it would be on a page carrying eight.

What we do not run matters as much as what we do. There are no interstitials, no pop-ups, no auto-playing video, no content-recommendation chumboxes, and nothing that reflows the page after the reader has started reading. Ads are served in reserved space so the layout does not jump. This protects viewability for the advertiser as directly as it protects the reading experience, and it is the reason we can quote the session figures above with a straight face.

The editorial environment is unusually safe for a subject area that is often anything but. This site does not publish conspiracy content, it does not promote pseudoscience, and it does not treat a rumour as a finding. Its entire method is to separate what is documented from what has merely been proposed, and to say plainly when a famous mystery has an unglamorous answer. A brand placed here sits next to sourced, corrected, carefully hedged writing rather than next to speculation dressed as news.

The readership is a general-interest one with a research habit: people who read long-form nonfiction, follow science and history coverage, and check citations. In practice the categories that fit well are books and publishing, documentary and streaming, museums and exhibitions, education and online courses, audio and podcasts, consumer technology, outdoor and travel, and financial services. If your product rewards attention and explanation rather than impulse, this is a good room to be in.

Everything is delivered through Google Ad Manager, so you can buy the way you already buy. Direct-sold campaigns can be trafficked as a guaranteed line item with standard reporting on impressions, viewability and click-through. Programmatic demand can reach the same inventory through the open auction or through a preferred deal or private marketplace at a floor we agree in advance. We accept standard IAB display creative and HTML5, and we can accommodate a reasonable third-party ad server or verification tag.

Category sponsorship is available for advertisers who want something more durable than a rotation. The register is organised into seven categories, and a sponsor can take the whole of one, appearing across every record inside it with an acknowledgement in the page furniture. Sponsorship never buys editorial influence: a sponsor cannot commission a record, cannot review one before publication, cannot have a record altered, and cannot have one removed. That rule is not negotiable and it is the thing that keeps the inventory worth buying.

Some categories are declined outright, and it is fairer to say so up front than to discover it after an insertion order. We do not accept adult content, gambling, payday or high-cost short-term credit, cryptocurrency speculation and token sales, dietary supplements making health claims, political advocacy, psychic or clairvoyant services, or anything that reads as a scare advertisement dressed up as an article. Nothing may be styled to look like a record or like part of the editorial page.

Rates depend on placement, volume, whether the buy is run-of-site or targeted to a category, and how long it runs. There is no rate card on this page because a sensible number depends on what you are trying to do, and quoting one in the abstract usually wastes both parties' time. Tell us the campaign, the flight dates and the budget you are working to, and you will get a straight answer including whether we think the fit is wrong.

To start, write to or use the contact form and mark the message for the advertising desk. Include the flight dates, the placements you want, the creative sizes you have ready and any verification requirements, and we will come back with availability and a quote. Media buyers who want the underlying analytics before committing are welcome to ask; we would rather show the reporting than be taken on trust.

Privacy Policy

This policy explains what information Anomaly Registry collects when you visit this website, why it is collected, how it is used, and what choices you have. It applies to anomalyregistry.com and to any subdomain operated by us. It was last updated on the date shown at the end of this policy, and we will revise it if our practices change.

We have designed this site to collect as little personal information as possible. You do not need an account to read anything here. There is no login, no user profile, and no comment system. In the ordinary course of reading the register, you are not asked to identify yourself, and we do not ask you to.

Like virtually every web server, ours produces access logs. These logs record the internet protocol address of the requesting device, the date and time of the request, the page or file requested, the referring page if one was sent, and the browser user agent string. These logs exist for security, abuse prevention, and diagnosing technical faults. They are retained for a limited period and then discarded. We do not use them to build profiles of individual readers.

If you write to us through the contact form, we receive whatever you choose to put into it: typically a name, an email address, and a message. We use that information for the sole purpose of reading and answering your message. Writing to us does not add you to any list, and we do not sell, rent, or trade contact details with anyone.

There is one optional mailing list, and you only join it by asking. If you submit the subscribe form we store the address you gave, the time you submitted it, the IP address it came from, and the exact wording of the consent you agreed to. We keep that record because Canadian anti-spam law expects us to be able to show when and how you asked to hear from us. The list is used to say that records have been published or materially revised, and for nothing else. Every message carries a way to leave, and asking to be removed by email works just as well.

Corrections are a special case, and worth stating plainly. If you write to point out an error in a record, we may act on that correction and revise the entry. We will not publish your name or your email address in connection with a correction unless you explicitly ask us to be credited.

This site is supported by advertising served through Google Ad Manager. Advertising technology providers may set and read cookies or similar identifiers on your device in order to select advertisements, limit how often you see the same advertisement, and measure performance. These identifiers are set by those third parties, not by us, and the data they collect is governed by their own privacy policies rather than this one.

We do not have access to the personal data that advertising partners collect, and we cannot delete it on your behalf. If you wish to limit interest-based advertising, you can adjust the advertising settings offered by Google, use your browser's cookie controls, or use the industry opt-out tools that are available in your region. Details are set out in our Cookie Policy.

We may use privacy-respecting aggregate analytics to understand which records are being read and how people move through the register. Where we do, we configure it to avoid collecting information that identifies individual readers. Aggregate figures tell us that a case page is popular; they do not tell us who read it.

We do not knowingly collect personal information from children. This site is a documentary archive intended for a general adult and older student readership. If you believe a child has sent us personal information through the contact form, write to us and we will delete it.

Depending on where you live, you may have rights over personal data relating to you, including the right to ask what we hold, to ask for a copy, to ask for correction, and to ask for deletion. Because we hold so little, these requests are usually simple to answer. Write to us and we will respond within the period required by the law that applies to you.

Our servers are located in North America, and information sent to this site is processed there. If you are visiting from elsewhere, your request necessarily crosses borders in order to reach us. By using the site you understand that this transfer takes place.

If we change this policy, the revised version will be posted here with a new date. Material changes will be noted plainly rather than buried. Questions about this policy should be sent through the contact page.

Cookie Policy

A cookie is a small text file that a website asks your browser to store, and that your browser sends back on later requests. Similar technologies, including local storage and pixel tags, do comparable work. This policy explains which of these are used on Anomaly Registry, by whom, and what you can do about them.

The registry itself is a reading site. It does not require a cookie to show you a record. We do not set cookies to track you across the internet, and we do not operate a first-party advertising identifier of our own.

Strictly necessary cookies may be set to keep the site secure and functioning, for example to help mitigate automated abuse of the contact form. These are limited in scope and are not used for advertising or profiling.

Advertising cookies are set by Google Ad Manager and by the advertising technology partners that operate within it. Their purposes include selecting which advertisement to show, capping the number of times a given advertisement is repeated, detecting invalid traffic and click fraud, and measuring whether an advertisement was actually seen.

Some of these advertising cookies support interest-based advertising, in which the advertisement you see is influenced by inferences drawn from browsing activity over time and across sites. Whether this occurs depends on your region, your settings, and the choices you have already made with those providers.

We may use aggregate analytics to count page views and understand which records are read. Where an analytics tool is used, we prefer configurations that do not identify individual readers and that do not follow readers across other websites.

We do not embed social media widgets, share buttons, or tracking pixels from social networks. This is a deliberate choice for an archive of this kind, and it removes an entire category of third-party tracking that most content sites carry.

Your browser gives you direct control over cookies. Every major browser can block third-party cookies, delete existing cookies, and clear stored data on exit. Blocking third-party cookies will not prevent you from reading anything on this site, though it may make the advertising you see less relevant.

You can also manage advertising preferences with Google directly through its advertising settings, and through the industry opt-out mechanisms operated in various regions. Because these are operated by third parties, we cannot make the choice on your behalf.

Where the law in your region requires consent before non-essential cookies are set, a consent notice will be shown and your choice will be respected. Withdrawing consent later is possible through the same mechanism.

Advertising partners may change over time. Rather than publish a list that goes stale, we identify the advertising system in use, which is Google Ad Manager, and direct you to Google's own disclosures for the current set of partners operating within it.

If you have a question about cookies on this site that this policy does not answer, write to us through the contact page and we will answer it.

Anomaly Registry is an independent documentary archive. It is published as a work of reference and public interest reporting, and it is supported by advertising. It is not affiliated with, endorsed by, or acting on behalf of any government, university, police service, coroner, scientific institution, or investigative body named in any record.

The register documents real events, including in some cases deaths, criminal investigations, and inquests. Where a record concerns a criminal matter, nothing on this site should be read as an allegation of guilt against any living person. Where an individual has been named in the public record, we report the fact of that naming and its evidentiary standing; we do not accuse.

Records are written from sources. Where a source is a primary document, we say so. Where a claim rests on secondary reporting, we say so. Where sources conflict, we state the conflict rather than quietly choosing a side. Where a widely repeated claim cannot be traced to any source, we say that too, because an untraceable claim is itself a finding.

Every record separates what is documented from what has been proposed. Hypotheses are labelled as hypotheses and attributed to whoever advanced them, together with their standing: peer-reviewed, contested, dismissed, or untested. We do not advance theories of our own.

The registry treats its own entries as provisional. Records carry a review date, and they are revised when the evidence changes. A record you read today may be corrected tomorrow, and that is a feature of the method rather than a defect in it.

Despite this method, errors will occur. If you find one, write to us. Corrections supported by evidence are made promptly, and we would rather be corrected than be consistent.

Scientific and forensic conclusions reported here are the conclusions of the researchers and officials who reached them, not ours. Reporting that a study proposed a mechanism is not an endorsement that the mechanism is correct, and the status assigned to a case reflects the state of the evidence rather than our opinion of it.

Nothing on this site is legal, medical, psychological, financial, or safety advice. Records that touch on medical or psychological matters, including mass psychogenic illness, report the diagnoses reached by clinicians at the time and afterward. They are not a substitute for professional care.

Quotations from sources are used sparingly and for the purposes of reporting, comment, criticism, and review. Copyright in quoted material remains with its owner. If you hold rights in material you believe has been used improperly, contact us and we will address it.

Original text, structure, record numbering, and editorial apparatus on this site are the property of Anomaly Registry. You are welcome to quote briefly and link to us. Wholesale reproduction of records, including reproduction for the purpose of training generative models, is not permitted without written permission.

Outbound links are provided as references. We do not control linked sites and are not responsible for their content, their accuracy, or their handling of your data.

This site is operated from British Columbia, Canada, and these notices are governed by the laws applicable there, without regard to conflict-of-law principles.

Accessibility Statement

Anomaly Registry is built to be usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification, or other assistive technology. We treat accessibility as part of the build rather than as a later remediation.

We aim to meet the Web Content Accessibility Guidelines version 2.1 at level AA. This is a target we work toward continuously rather than a certification we claim to have completed.

The site is written as semantic HTML. Headings describe the real structure of a record, lists are marked up as lists, and the register is a genuine table with proper header cells, so that a screen reader can announce which column a value belongs to.

Every interactive element is reachable and operable by keyboard alone. Focus is visible at all times, and a skip link at the top of each page lets keyboard and screen reader users jump straight to the register without traversing the navigation.

Status is never conveyed by colour alone. Each status carries its written label in text, so a reader who does not perceive the colour difference between "Unsolved" and "Debunked" still receives the distinction.

Text colours have been chosen to meet or exceed the contrast ratios required at level AA against the page background. The typefaces are set at a comfortable reading size with generous line height, and the layout reflows to a single column on small screens without loss of content or function.

The site contains one animated element, an annotation on the home page. It respects the reduced-motion preference set in your operating system, and when that preference is on, the annotation appears without movement.

Text can be resized up to two hundred percent in the browser without breaking the layout or clipping content. Nothing on this site depends on a specific screen orientation.

Advertising is served by a third party. We control where advertisements are placed and label them as advertisements, but we do not control their internal markup, and their accessibility is ultimately determined by the advertiser.

We are developing an audio version of each record. When it is published, it will be an alternative way to receive the same content, not a replacement for the written entry, and the written entry will remain the authoritative version.

Accessibility work is never finished, and parts of this site will fall short of the standard we have set. If you encounter a barrier, we want to know about it. Please tell us what page you were on, what you were trying to do, and what assistive technology you were using.

Write to us through the contact page. We aim to respond within five business days and to fix genuine barriers promptly.

Terms of Use

These terms govern your use of anomalyregistry.com. By using the site you accept them. If you do not accept them, please do not use the site.

Anomaly Registry is offered as a free documentary reference. There is no account, no subscription, and no paywall, and nothing here is offered as a professional service of any kind.

You may read, quote briefly with attribution, link to, and print records for personal, educational, and research use. This is an archive, and it is meant to be used.

You may not reproduce records wholesale, republish the register or substantial parts of it, or scrape the site systematically. In particular, you may not reproduce this content for the purpose of training generative models. Permission for other uses can be requested through the contact page and is often granted.

Original text, the record numbering system, the status taxonomy, the editorial apparatus, and the design of this site are the property of Anomaly Registry. Third-party material quoted or referenced remains the property of its owners.

We work hard to make records accurate, and we correct them when they are not. Even so, the site is provided as it is, without warranty of any kind, express or implied, including any warranty of accuracy, completeness, or fitness for a particular purpose.

Records are provisional by design. A status can change, an identification can be confirmed or overturned, and a leading explanation can be displaced by a better one. Do not treat any record as a final word, and check the review date.

To the fullest extent permitted by law, Anomaly Registry and its operator are not liable for any loss or damage arising from your use of, or reliance on, anything published here.

If you send us a correction, a source, or a suggestion, you grant us permission to use it in the register. You will not be identified in connection with it unless you ask to be credited.

Do not use the contact form to send abuse, threats, spam, or automated submissions. We may block access to anyone who misuses the site or attempts to interfere with its operation.

Outbound links are provided as references and are not endorsements. We are not responsible for the content or conduct of any site we link to.

We may revise these terms. The version published here is the version in force. These terms are governed by the laws of British Columbia, Canada, and any dispute will be heard in the courts of that province.