UNRESOLVED
CF-BBK-1950S1950S2F-33 UNRESOLVED
Odessa, Washington Light Formation Incident
CASE FILE — CF-BBK-1950S1950S2F-33 — CASEFILES CLASSIFIED ARCHIVE
Date Date when the incident was reported or occurred
1952-12-09
Location Reported location of the sighting or event
Odessa, Washington, United States
Duration Estimated duration of the observed phenomenon
Unknown
Object Type Classification of the observed object based on witness descriptions
light
Source Origin database or archive this case was sourced from
blue_book
Country Country where the incident took place
US
AI Confidence AI-generated credibility score based on source reliability, detail consistency, and corroboration
70%
On December 9, 1952, an unidentified aerial phenomenon was reported in Odessa, Washington, a small agricultural community in the central part of the state. This incident occurred during one of the most active periods of UFO reporting in Project Blue Book's history, falling within the wave of 1952 sightings that saw increased military and civilian reports across the United States. Odessa, located in Grant County along the Columbia Basin, was an unlikely location for such activity, being a rural farming community far from major military installations or air traffic corridors.
The case was documented in Project Blue Book's official files and assigned case number 9170320, indicating it was processed through standard Air Force investigation protocols. The timing places this sighting during the height of Cold War tensions, when the U.S. military was particularly vigilant about unidentified aircraft that might represent Soviet intrusions into American airspace. The December timeframe also places this incident near the end of the remarkable 1952 UFO wave, which had seen peak activity during the summer months with the famous Washington D.C. radar-visual incidents in July.
Despite being archived in Project Blue Book records, the available documentation for this case is limited. The sparse metadata suggests that either the original case file documentation was lost, incomplete from the start, or deemed insufficiently detailed to warrant extensive investigation. This was not uncommon for Blue Book cases from rural areas during periods of high reporting volume, when Air Force investigators prioritized incidents with multiple witnesses, physical evidence, or radar confirmation.
02 Timeline of Events
1952-12-09
Incident Occurs
Unidentified aerial phenomenon reported in or near Odessa, Washington. Specific time of day and circumstances unknown.
1952-12
Report Filed
Incident reported to authorities and entered into Project Blue Book system. Assigned case number 9170320.
1952-12
Initial Assessment
Case reviewed by Air Force personnel. Limited documentation suggests minimal investigative follow-up was conducted.
1969
Project Blue Book Closure
Case archived with Project Blue Book when the program officially terminated. Status: unresolved due to insufficient data.
03 Key Witnesses
Anonymous Witness
Civilian resident (presumed)
unknown
Identity and background unknown. Likely a resident of Odessa or the surrounding Grant County agricultural area in December 1952.
"No testimony available in case file."
04 Analyst Notes -- AI Processed
The lack of detailed information in the available case file is significant and typical of many Project Blue Book investigations from this era. The file number sequence (9170320) places this firmly within the authenticated Blue Book archival system, confirming it was officially logged and assigned for investigation. However, the absence of witness testimony, object description, duration, and investigative conclusions suggests either incomplete initial reporting or minimal follow-up by Air Force personnel.
The geographic location is noteworthy. Odessa, Washington, in 1952 was a small farming town with a population under 1,000 people. Its isolation from major population centers or military bases makes hoax or misidentification of conventional aircraft somewhat less likely than in urban areas with heavy air traffic. However, this remoteness may also explain why the case received limited investigative attention. The Columbia Basin region was undergoing significant development in 1952 due to irrigation projects and agricultural expansion, which could potentially introduce unusual lights or aerial activity related to construction or agricultural operations.
05 Theory Comparison
BELIEVER ANALYSIS
Genuine Anomalous Phenomenon
The 1952 wave included numerous well-documented cases with multiple witnesses, radar confirmation, and credible observers including military pilots. This Odessa incident occurred during this peak period of activity. Proponents argue that the lack of documentation may indicate a case that was deliberately under-recorded because it didn't fit conventional explanations, or that original files containing more detailed information were lost or removed. The rural location and limited witnesses would make this consistent with other isolated sightings from the era that lacked the evidentiary support for thorough investigation.
SKEPTIC ANALYSIS
Conventional Aircraft Misidentification
The most parsimonious explanation is misidentification of conventional aircraft, possibly military jets from Fairchild Air Force Base (approximately 100 miles northeast) or civilian aircraft. December weather conditions in eastern Washington can create unusual atmospheric effects that distort the appearance of navigation lights. The lack of detailed documentation may indicate Air Force investigators quickly determined the sighting was of conventional origin and saw no need for extensive follow-up.
Astronomical or Atmospheric Phenomenon
Eastern Washington's clear winter skies make celestial objects particularly visible. Bright planets (Venus, Jupiter, Mars), meteors, or unusual atmospheric conditions such as ice crystal halos or temperature inversions could create apparent aerial anomalies. The absence of detailed witness testimony prevents verification, but astronomical phenomena were common explanations for Blue Book cases.
06 Verdict
ANALYST VERDICT
This case remains officially unresolved due to insufficient documentation. The most likely explanation is that this was either a misidentification of conventional phenomena (aircraft, celestial objects, or atmospheric effects) that was inadequately documented, or a case where the witness report was too vague to pursue meaningful investigation. The sparse file could also indicate the report was quickly dismissed by initial screeners as lacking credibility or detail. Without access to witness testimony, object characteristics, or investigative notes, any conclusion is speculative. The case's significance lies primarily in its inclusion within the official Blue Book archive as a documented incident from the notable 1952 wave, but it offers little evidentiary value for serious UFO research. This represents one of hundreds of Blue Book cases that remain frustratingly incomplete for modern analysis.
AI CONFIDENCE SCORE:
70%
07 Community Discussion
VIEW ALL >// NO COMMENTS YET
Be the first field agent to contribute analysis on this case.
08 Live Chat 1 ROOM
ENTER LIVE CHAT
Real-time discussion with other field agents analyzing this case.