Case No. 313·United States
1959·Redmond, Oregon
United States.Redmond, Oregon · police, FAA and six F-102s
Before dawn on September 24, 1959, police officer Robert Dickerson saw a bright object descend over Redmond, Oregon, and hover at about 60 meters, with the treetops lit up. He alerted the FAA office at the airport; the controllers observed it and the Klamath Falls GCI radar tracked it, after which six F-102 fighters were scrambled and a B-47 and an F-89 on routine flights joined the pursuit. Radar followed the object for about two hours, with altitude changes between 1,500 and 15,800 meters. The Air Force wavered between 'Venus,' 'a balloon' and 'insufficient data.'
Year
1959
Tier
S
Probability
74%
Category
Incident
Strong evidence: instrumental sensor record + multiple witnesses (typically military). Three independent axes: the «tier» measures the strength of the evidence; the «probability» estimates how genuinely unexplained the case is —a natural phenomenon can remain unexplained, so it does not equal «non-prosaic»—; and the partition of explanations (below) says what it most plausibly was. So a well-documented case can have a possible hoax as its most plausible cause, and a Tier B is not, for that reason, a hoax.
Primary documents · viewer

Context · Redmond (Oregon), where police, FAA and six F-102s tracked the object
Redmond, Oregon, Business Hwy 97.jpg · Wikimedia Commons · CC BY-SA 2.0 · open original
Part 01
The night in question
Shortly before dawn on September 24, 1959, police officer Robert Dickerson was patrolling the streets of Redmond, in central Oregon, when he saw a large, bright object descend over the town, stop abruptly and hover at about 60 meters. It was low enough that the tops of nearby trees glowed with its light. Dickerson — a trained witness, with the institutional credibility the corpus weighs — immediately drove to the Federal Aviation Administration (FAA) office at Redmond airport to report it before additional witnesses.
Around 5:10 a.m., the FAA controllers, who were already watching the object, relayed the report to the Seattle Air Route Traffic Control Center, which in turn escalated it to Hamilton Air Force Base in California. The object was also detected on the radar of the Klamath Falls ground-controlled intercept (GCI) site. With a police officer's visual, controllers' visual and radar track converging, six F-102 fighters were scrambled from Portland; as they climbed, air control radioed the crews of a B-47 bomber and an F-89 fighter on routine flights in the area and ordered them to join the search. The FAA controllers described the object as a disc-shaped body with protrusions from which colored flames seemed to emanate as it maneuvered. Radar held the target south of Redmond for about two hours, with altitude changes recorded between roughly 1,500 and 15,800 meters — a vertical profile incompatible with a drifting balloon.
The Air Force's official explanation mutated over time, and that mutation is part of the record. First the sighting was attributed to the planet Venus; then to 'a balloon'; when NICAP confronted the Air Force with the FAA logs and the witness accounts that made both explanations inconsistent, the conclusion became 'insufficient data'; and in 1963 the verdict reverted to 'Venus.' None of the versions accounted at once for the low descent and hover seen by the officer, the simultaneous deployment of six interceptors plus two diverted aircraft, and a two-hour radar track with vertical maneuvers of more than 14 kilometers in amplitude.
Part 02
Why this case moved the needle
Redmond concentrates in a single episode two of the markers this corpus uses to weigh a case: the institutional quality of the witnesses and the disproportionate response of the military apparatus. The first observer was a police officer; the next, FAA controllers; the target entered the Klamath Falls GCI radar; and the defense system responded by scrambling six F-102s and diverting two more aircraft in flight. That level of mobilization is not ordered over Venus. The two-hour radar track with vertical excursions of nearly 15 kilometers flatly rules out the balloon, the other official explanation: no balloon climbs and descends like that, nor hovers at 60 meters lighting up the treetops as the first witness described.
The case's analytical value lies as much in the event as in its subsequent handling, a textbook exemplar of the oscillating-explanation pattern. The Air Force ran through Venus → balloon → 'insufficient data' → back to Venus, each step forced by the evidence NICAP kept supplying — the FAA logs, the controllers' accounts — and each reversal revealing that the verdict answered less to the data than to the institutional need to close the file. Redmond is thus a double document: of the multi-witness radar-visual phenomenon that defines the ceiling of the Blue Book era, and of the bureaucratic dissolution mechanism this project tracks as a systematic bias of the official record. Candor requires noting the counter-hypothesis that gives the mundane channel its weight: the sighting occurred before dawn, when Venus was a bright morning star, and an initial misidentification of the stationary body cannot be entirely excluded — but it explains neither the low descent, nor the radar maneuvers, nor the scramble of six interceptors.
Part 03
What's left on paper
Documented evidence
- Initial visual contact by a police officer (Robert Dickerson): bright object descending and hovering at ~60 m, with treetops lit up
- Observation by FAA controllers at Redmond airport, with report to Seattle ARTCC and Hamilton AFB
- Detection on the Klamath Falls GCI radar
- Deployment of six F-102 fighters from Portland, plus a B-47 and an F-89 diverted from routine flights
- ~2-hour radar track with altitude changes between ~1,500 and 15,800 m (incompatible with a balloon)
- USAF's oscillating official explanation: Venus → balloon → 'insufficient data' → Venus (1963)
- NICAP documentation with the FAA logs and controllers' accounts contradicting the official explanations
Sources
- Expediente de Project Blue Book — Redmond, Oregon, 24 de septiembre de 1959 (NARA) — Includes the sequence of official explanations (Venus / balloon / insufficient data)
- NICAP — expediente Redmond 1959 — Compiles the FAA logs and the controllers' accounts that contradict the USAF explanations
- Registros de la FAA — Redmond Airport / Seattle ARTCC, 24 de septiembre de 1959 — Contemporary logs of the report and the escalation to air defense
Patterns it exhibits (2)
Location
Redmond, Oregon · 44.27°, -121.17°
Distribution of explanations
This case is classified among the model's hypotheses: the bar splits 100% by how much each explanation weighs (the uncertainty is spread across the hypotheses the case supports). Summed across the corpus they produce the comparable partition. It is a different question from the Probability above: that one estimates how likely the case is a genuinely unexplained phenomenon; this one splits which the explanation would be.
Modal hypothesis: Misidentification 43% · sums to 100%
Confused with: Astronomical
Structured analytical judgment, not a calibrated frequency. Forced classification: the mass the evidence cannot assign is spread across the hypotheses the case does support.
Related cases