Within Oregon UFOs
Did Venus Explain The Redmond UFO Case?
The 1959 Redmond incident matters because police, radar and jet interceptors made a simple sky-light explanation harder to accept cleanly.
On this page
- The police and airport reports
- Radar returns and jet interceptors
- What the Venus explanation leaves unresolved
Page outline Jump by section
Introduction
The 1959 Redmond case is one of Oregon’s strongest aviation-linked UFO stories because it was not just a lone witness seeing a bright light before dawn. A Redmond police officer reported a descending, hovering object; Federal Aviation Agency staff at the airport reportedly watched it through binoculars; official communications referred to radar at Klamath Falls; and F-102 interceptors were scrambled from Portland. The later Venus explanation may account for a bright morning object in the sky, but it does not cleanly explain the reported low hover, colour changes, rapid movement, radar language and jet response unless several parts of the witness and log record were mistaken, conflated or later exaggerated. That makes Redmond a useful Oregon case not because it proves anything exotic, but because it shows how a plausible astronomical explanation can still leave awkward evidential gaps. [NICAP]nicap.orgAviation Personnel See UFO At RedmondAviation Personnel See UFO At Redmond [NICAP]nicap.orgOpen source on nicap.org.
Why Redmond became Oregon’s aviation case
The Redmond incident took place before dawn on 24 September 1959, at and around Redmond Airport in central Oregon. In the state’s UFO history, it sits in a different category from the better-known McMinnville photographs. McMinnville is a photographic case; Redmond is a police, airport, radar and interceptor case. That difference matters because aviation-linked sightings tend to attract more serious attention: they involve airspace, trained observers, flight-service communications and, sometimes, military response.
The case also belongs to the Project Blue Book era. The US Air Force investigated UFO reports from 1947 to 1969 under Project Blue Book, which eventually recorded 12,618 sightings, of which 701 remained “unidentified” when the programme closed. The Air Force’s official position after Blue Book was that no investigated UFO had shown evidence of a threat to national security, technology beyond known science, or extraterrestrial vehicles. Redmond therefore needs to be read in two layers: as a local Oregon event with unusual witness and radar claims, and as one entry in a wider Air Force system that generally sought conventional explanations. [Air Force]af.milUnidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display…
What keeps Redmond alive in UFO literature is not merely that someone said “UFO”. It is the combination of the setting and the claimed sequence. The core report has an object seen first from town, then from the airport, then mentioned in official communications involving Seattle Air Route Control Center and Hamilton Air Force Base, with jets reportedly scrambled from Portland. That is why the case remains harder to dismiss than a brief, anonymous light-in-the-sky report, even though some later retellings have probably added drama beyond the best-documented material. [NICAP]nicap.orgUFO ReportUFO Report
The police and airport reports
The central witness was Redmond police officer Robert Dickerson. NICAP’s published account says Dickerson was on patrol shortly before dawn when he saw what first looked like a bright falling object, “like a meteor”. Instead of burning out, it reportedly became larger, ball-like, stopped abruptly, and hovered about 200 feet above the ground, bright enough to illuminate juniper trees below it. Dickerson then drove towards it on the Prineville Highway before turning in at the airport. [NICAP]nicap.orgOpen source on nicap.org.
That first part is important because it is the portion least compatible with a simple Venus explanation. Venus can be strikingly bright near dawn and can be misjudged by observers, especially when seen low on the horizon. But Venus does not descend, stop over trees, illuminate local ground objects, or move to a new position near an airport. Either Dickerson seriously misperceived a distant astronomical object, or the report as later preserved does not accurately describe the original sighting, or more than one stimulus was involved.
At the airport, the report becomes stronger but also more complicated. Flight Service Specialist Laverne Wertz had reportedly just completed weather observations and had seen nothing unusual. According to the NICAP account, Dickerson, Wertz and others then studied the hovering object through binoculars. It was described as round and flat, with “tongues” of flame-like light periodically extending from the rim. [NICAP]nicap.orgOpen source on nicap.org.
A local 2022 retrospective in The Source Weekly gives a similar public-facing version of the case: Dickerson saw a mushroom-shaped object moving side to side, glowing in several colours, and bright enough to illuminate nearby treetops. The same article notes that the FAA and Air Force later leaned on Venus, while local historical commentary has treated that explanation as strained if the witnesses’ descriptions were accurate. [The Source - Bend, Oregon]bendsource.comThe SourceThe Source
The key phrase is “if the witnesses were reporting accurately”. That caveat should not be skipped. Early-morning sightings are vulnerable to errors of distance, altitude and motion. A stationary planet can appear to move when a witness is driving, when clouds pass, or when there are no good distance cues. Binocular viewing can also intensify brightness and colour effects. Still, those general cautions do not erase the problem: the Redmond report contains multiple observers, an airport setting and specific descriptions that go beyond simply “a bright star was seen”.
Radar returns and jet interceptors
The aviation part of the case begins with the reported communications. NICAP’s account says the Redmond station reported the object to Seattle Air Route Control Center at 1310Z, or 5:10 a.m. Pacific Standard Time, and that Seattle relayed the report to Hamilton Air Force Base. The same account quotes the Seattle log as saying the UFO was also seen on radar at the Klamath Falls Ground Control Intercept site and that F-102s were scrambled from Portland. [NICAP]nicap.orgUFO Evidence 1964UFO Evidence 1964
That does not mean radar proved the visual object was a solid unknown craft. Radar can produce misleading returns through ground clutter, anomalous propagation, equipment issues or fixed objects. But it does mean the case cannot be evaluated only as a visual misidentification. If the FAA log wording is accurately reproduced, official personnel were treating the matter as something serious enough to relay through air defence channels.
The reported timing also matters. As the observers at Redmond watched the object, they reportedly noticed a high-speed aircraft approaching. The log quotation preserved by NICAP says that as the aircraft approached, the object took on a mushroom shape, showed yellow and red flame from its lower side, rose rapidly, and disappeared above clouds. The object was then reportedly seen again briefly about 25 miles south of the airport, while radar continued to show something south of Redmond for about two hours. [NICAP]nicap.orgChallenge of UFOsChallenge of UFOs
Later UFO summaries make the story even more dramatic, adding claims of six F-102s, a B-47, an F-89, airborne radar, violent evasive manoeuvres and a target hundreds of feet across. Those claims appear in later UFO cataloguing and secondary case directories, but they require more caution. NICAP’s own Redmond directory notes that some versions published later were more sensational than the earliest NICAP and UFO Evidence accounts, and criticises Donald Keyhoe’s later “capture the UFO” version for giving no clear source for its most dramatic claims. [NICAP]nicap.orgsection 5section 5
That distinction is vital for a balanced reading. The restrained case is already interesting: police, FAA observers, reported radar language and scrambled interceptors. The expanded case, with near-collisions and a secret capture mission, is much weaker unless supported by original documents or first-hand pilot testimony. Redmond does not need the more cinematic version to matter within Oregon UFO history.
How the official explanations shifted
The strongest sceptical reading of Redmond is not simply “it was Venus”. The official and semi-official explanations, as reported by NICAP, appear to have moved through several stages. NICAP says an Air Force response in January 1960 described the case as carried in Air Technical Intelligence Center records as “insufficient information”, while suggesting the object was probably a balloon because it remained in the area for more than an hour. NICAP challenged that by citing Weather Bureau wind data and the lack of a local balloon launch. [NICAP]nicap.orgAviation Personnel See UFO At RedmondAviation Personnel See UFO At Redmond
The next explanation separated the radar from the visual sighting. According to the NICAP discussion, Air Force correspondence later said the radar return had been identified by senior controllers as an echo from a “gap filler” antenna on a mountain at the 8,010-foot level. On that reading, the radar was not tracking the same object witnesses described; it was a fixed radar echo misread during the search. [NICAP]nicap.orgOpen source on nicap.org.
That explanation has a real logic. A fixed ground-related radar return is far more plausible than a large unknown vehicle moving between 6,000 and 54,000 feet. It also allows for a split solution: the visual sighting could have been an astronomical object, while the radar return was unrelated clutter or a fixed echo. Many puzzling UFO cases become less mysterious when two ordinary things are accidentally joined into one story.
The difficulty is that the gap-filler explanation does not settle the visual sighting, and the Venus explanation does not settle the radar language. NICAP argued that the FAA log referred to changing measured altitudes, while the Air Force’s later version reportedly described a radar return that did not move. NICAP also noted the tension between treating the object as slow and lingering when a balloon explanation was useful, then emphasising rapid manoeuvres when separating the radar from the visual report. [NICAP]nicap.orgUFO ReportUFO Report
By 1963, according to NICAP, an Air Force information sheet attributed the object to refraction of light from Venus. NICAP’s rebuttal was that its astronomy advisers had already considered Venus, that Venus was indeed prominent in the eastern sky, but that witnesses said they did not see Venus during the UFO sighting and later identified it separately. That does not prove the witnesses were correct, but it does make the Venus explanation less tidy than a routine “bright planet mistaken for UFO” case. [NICAP]nicap.orgOpen source on nicap.org.
What Venus can explain
Venus is one of the most common causes of sincere UFO reports. It can be extremely bright, appears near dawn or dusk, and can seem startling when an observer is not expecting it. Low on the horizon, its light can flicker, redden or change colour because it is passing through more atmosphere. Movement by the observer, thin cloud, haze, and poor distance cues can make a fixed object appear to shift or pulse.
Applied to Redmond, Venus is not a foolish suggestion. The incident happened before dawn. NICAP itself acknowledged that Venus was prominent in the eastern sky that morning. A bright morning Venus could plausibly explain part of the experience: a brilliant object, colour effects, a lingering presence, and perhaps an impression of hovering. [NICAP]nicap.orgOpen source on nicap.org.
The best sceptical reconstruction is therefore a layered one. Dickerson may have first seen a meteor, aircraft light or other transient object, then later focused on Venus. Airport observers may have seen the same bright planet and interpreted it through the expectation created by the police report. The radar return may have been unrelated clutter or a fixed echo. The jet scramble may have been a precaution triggered by uncertainty, not evidence that an extraordinary object was physically present.
That reconstruction is possible, and it is probably stronger than treating every reported detail as literal. It also fits the broader pattern of Project Blue Book, where many cases were resolved as planets, stars, balloons, aircraft or radar errors, and where the Air Force ultimately said there was no evidence that unidentified cases represented extraterrestrial vehicles or advanced unknown technology. [Air Force]af.milUnidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display…
But “possible” is not the same as “fully demonstrated”. The Venus explanation works best when the witness descriptions are simplified to “bright object before dawn”. It works less well when the report is read in its full Redmond form: low hover, apparent descent, airport binocular observations, flame-like extensions, rapid climb, and official radar-related communications.
What the Venus explanation leaves unresolved
The Redmond case remains interesting because each conventional explanation solves one part of the story better than the whole. Venus explains a bright dawn object. A balloon explains lingering presence but struggles with the reported rapid climb, local wind objections and radar complications. A gap-filler radar echo explains a stationary return but not the visual account. Misperception explains some human testimony but becomes harder as the number and professional setting of witnesses increase.
The main unresolved points are these:
- The low-altitude claim. Dickerson’s reported estimate of a hover about 200 feet above the ground is the most dramatic part of the case. Witness altitude estimates can be badly wrong, especially at night or dawn, but this detail cannot be reconciled with Venus unless it is treated as a major error or later embellishment. [NICAP]nicap.orgUFO Evidence 1964UFO Evidence 1964
- The airport observation. The involvement of Laverne Wertz and other airport personnel gives the case more weight than a single roadside sighting. It does not make the report infallible, but it does make a purely casual misidentification less satisfying. [NICAP]nicap.orgChallenge of UFOsChallenge of UFOs
- The radar wording. The case is repeatedly described as involving Klamath Falls radar and scrambled F-102s. The Air Force’s later gap-filler explanation may explain the radar side, but it also separates the radar from the visual object rather than explaining both as one Venus sighting. [NICAP]nicap.orgsection 5section 5
- The changing explanation. The reported movement from “insufficient information” to probable balloon, then radar echo, then Venus, is one reason UFO researchers have treated Redmond as a case where the official answer looks reactive rather than decisive. NICAP used Redmond as an example of what it called changing or “zigzag” explanations. [NICAP]nicap.orgsection 5section 5
- The risk of later inflation. Some later versions include claims of near-collisions, turbulent wake and a secret mission to capture the UFO. Those details should be handled separately from the better-attested police, FAA and radar-log elements because the sourcing is less secure. [NICAP]nicap.orgsection 5section 5
This is why Redmond should be described as disputed rather than simply debunked or unexplained in a sensational sense. A cautious sceptic can assemble a plausible multi-factor explanation. A cautious UFO historian can still say that the official Venus answer, by itself, does not account for the most distinctive claims in the case.
How Redmond should be read today
Redmond’s value for Oregon UFO history is not that it provides a clean mystery with a dramatic answer. Its value is that it shows the messy middle ground where many serious UFO cases live. There are named witnesses, an aviation setting, an official response and a later mundane explanation. There are also uncertain secondary claims, possible reporting errors, and a strong temptation among believers and sceptics alike to make the case simpler than it is.
For readers comparing Oregon’s major UFO stories, Redmond sits between McMinnville and ordinary sighting reports. McMinnville turns on photographs and questions of possible hoaxing or image interpretation. Redmond turns on testimony, official communications and whether one explanation can cover several kinds of evidence at once. That makes it a useful internal link point for any wider Oregon UFO project: it connects local police testimony, airport reporting, Project Blue Book, radar cases and sceptical reinterpretation.
The most defensible judgement is modest. Redmond was a real reported incident that generated official attention and later dispute. Venus was a plausible contributor because the sighting occurred before dawn and Venus was prominent, but Venus alone does not comfortably explain the full published account. The radar may have been unrelated or misread, and some later dramatic details should be treated with caution. What remains is not proof of an extraordinary craft, but one of Oregon’s most instructive examples of how a UFO case can be partly explainable, partly overgrown, and still not neatly closed.
Amazon book picks
Further Reading
Books and field guides related to Did Venus Explain The Redmond UFO Case?. Use these as the next step if you want deeper reading beyond the article.
The Report on Unidentified Flying Objects
Strong fit for a radar, police and aviation-era UFO case.
eBay marketplace picks
Marketplace Samples
Example marketplace items related to this page. Use the search link to explore similar finds on eBay.
Endnotes
-
Source: nicap.org
Title: Aviation Personnel See UFO At Redmond
Link: https://www.nicap.org/reports/oregon4.htm -
Source: nicap.org
Link: https://www.nicap.org/ufoe/section_9.htm -
Source: bendsource.com
Title: The Source
Link: https://www.bendsource.com/news/uforegon-16707374/ -
Source: af.mil
Title: Air Force
Link: https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104590/unidentified-flying-objects-and-air-force-project-blue-book/Source snippet
Unidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display...
-
Source: nicap.org
Title: UFO Report
Link: https://www.nicap.org/590924redmond_dir.htm -
Source: nicap.org
Link: https://www.nicap.org/reports/oregon1.htm -
Source: in-the-sky.org
Link: https://in-the-sky.org/article.php?term=venus -
Source: nicap.org
Link: https://www.nicap.org/chronos/1959fullrep.htm -
Source: nicap.org
Title: UFO Evidence 1964
Link: https://www.nicap.org/ufoe/UFO%20Evidence%201964.pdf -
Source: nicap.org
Title: Challenge of UFOs
Link: https://www.nicap.org/books/coufo/coufo_complete.htm -
Source: nicap.org
Title: section 5
Link: https://www.nicap.org/ufoe/section_5.htm -
Source: in-the-sky.org
Link: https://in-the-sky.org/data/object.php?id=P2 -
Source: history.com
Title: ufo dogfight gorman us plane fargo
Link: https://www.history.com/articles/ufo-dogfight-gorman-us-plane-fargo -
Source: Wikipedia
Title: Project Blue Book
Link: https://en.wikipedia.org/wiki/Project_Blue_Book -
Source: britannica.com
Title: Project Blue Book
Link: https://www.britannica.com/topic/Project-Blue-Book
Additional References
-
Source: youtube.com
Link: https://www.youtube.com/watch?v=csiSZB7ZWTcSource snippet
UFOs, mysterious red lights in Oregon skies and perplexed pilots...
-
Source: youtube.com
Title: Project Blue Book: America’s Obsession with UFOs
Link: https://www.youtube.com/watch?v=Xu4oTBBI5UESource snippet
What Was Hiding on Venus All Along. Real Radar Images from NASA's Magellan Mission...
-
Source: cia.gov
Link: https://www.cia.gov/readingroom/document/cia-rdp81r00560r000100010001-0 -
Source: science.gov
Link: https://www.science.gov/topicpages/l/lunar%2Beclipse%2Bphotometry -
Source: nasa.gov
Link: https://www.nasa.gov/wp-content/uploads/2015/04/695726main_cominghome-ebook.pdf -
Source: southampton.ac.uk
Link: https://www.southampton.ac.uk/assets/imported/transforms/content-block/UsefulDownloads_Download/6EBAF0B27CD947C0AF99B959953F29A8/TAG%20BOOKLET%20DONE%20DEF.pdf -
Source: scribd.com
Link: https://www.scribd.com/document/51179838/UFOlogy-The-Book-NICAP-Database -
Source: facebook.com
Link: https://www.facebook.com/WIONews/posts/declassified-documents-raise-intrigueus-air-force-document-cites-12618-ufo-sight/1335121142060390/ -
Source: facebook.com
Link: https://www.facebook.com/RedmondMuseum/posts/1579653520783200/ -
Source: facebook.com
Link: https://www.facebook.com/RedmondMuseum/posts/1559928852755667/
Topic Tree