UNRESOLVED
CF-BBK-1960S1960S2F-92 UNRESOLVED
Washington D.C. Project Blue Book Case 8293249
CASE FILE — CF-BBK-1960S1960S2F-92 — CASEFILES CLASSIFIED ARCHIVE
Date Date when the incident was reported or occurred
1966-10
Location Reported location of the sighting or event
Washington, D.C., United States
Duration Estimated duration of the observed phenomenon
unknown
Object Type Classification of the observed object based on witness descriptions
unknown
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%
This Project Blue Book case from October 1966 involves an unidentified aerial phenomenon reported in the vicinity of Washington, D.C., the nation's capital. The case is catalogued under Blue Book identification number 8293249 and originates from the official U.S. Air Force systematic study of UFO phenomena that operated from 1947 to 1969. Washington, D.C. holds particular significance in UFO research history, most notably due to the famous 1952 Washington flap where multiple radar-visual sightings occurred over consecutive weekends near the Capitol and White House, prompting significant military and public concern.
The October 1966 timeframe places this incident during a period of heightened UFO activity across the United States. 1966 saw numerous high-profile cases including the Portage County, Ohio police chase, the Dexter/Hillsdale Michigan swamp gas incidents that led to public hearings, and widespread sightings that prompted congressional interest in the Air Force's handling of UFO investigations. Sightings in the Washington area would have received particular scrutiny given the capital's restricted airspace, military installations, and sophisticated radar coverage.
Unfortunately, the source metadata lacks the detailed documentation typically found in complete Project Blue Book case files—witness testimony, investigator reports, radar data, or photographic evidence. Without access to the actual PDF contents, we cannot determine the specific nature of the object observed, the circumstances of the sighting, witness credibility, or the Air Force's official conclusion. The case remains catalogued in the Blue Book archives, suggesting it was investigated to some degree by Air Force personnel or contracted scientific advisors.
02 Timeline of Events
October 1966
Incident Occurs in Washington D.C.
Unidentified aerial phenomenon reported in the Washington, D.C. area during October 1966. Specific date and time unknown from available metadata.
October 1966
Report Filed with Project Blue Book
Incident officially logged by the U.S. Air Force Project Blue Book program and assigned case identification number 8293249. This indicates the report met threshold criteria for formal investigation.
October 1966 - Unknown
Investigation Conducted
Project Blue Book investigators presumably conducted standard protocol investigation including witness interviews, evaluation of physical evidence if any, consultation of astronomical and meteorological data, and analysis of radar returns if applicable.
1966-1969
Case Filed in Blue Book Archive
Investigation materials compiled and archived as part of the official Project Blue Book collection, where they remained classified or restricted until the program's termination in 1969 and subsequent declassification.
03 Key Witnesses
Unknown Witness(es)
Unknown - potentially military, civilian, or radar operators
unknown
Witness information not available in source metadata. Given the Washington D.C. location and official Blue Book investigation, witnesses may have included military personnel, air traffic controllers, or civilian observers.
"No testimony available in source data"
04 Analyst Notes -- AI Processed
The significance of this case must be evaluated with considerable caution given the absence of detailed documentation in the available metadata. However, several contextual factors warrant attention. First, the Washington D.C. location automatically elevates any aerial anomaly report due to the area's exceptional air defense posture, multiple radar installations, and proximity to sensitive government facilities. Any unidentified object in this airspace would likely have been detected by multiple systems and prompted rapid response protocols.
Second, the 1966 timeframe is notable. This was a critical year for Project Blue Book when public and congressional pressure reached new heights following a wave of credible sightings. The Air Force commissioned the University of Colorado study (Condon Committee) in 1966 specifically to provide an independent scientific assessment, largely in response to criticism of Blue Book's methodology and conclusions. Cases from this period received more rigorous documentation and analysis than earlier years. The assignment of a specific case number (8293249) indicates the report was formally logged and presumably investigated according to Blue Book protocols, though we cannot confirm the investigation's depth or conclusions without the full file.
05 Theory Comparison
BELIEVER ANALYSIS
Genuine Unknown Aerial Phenomenon
Washington D.C.'s history of unexplained aerial incidents, particularly the well-documented 1952 events, establishes precedent for truly anomalous activity over the capital. If this case involved multiple credible witnesses, radar confirmation, and defied conventional explanation after thorough investigation, it may represent a genuine unknown phenomenon. The fact that it remained in Blue Book files rather than being quickly dismissed could indicate it was among the small percentage of cases (approximately 6% officially) that the Air Force could not explain. The capital's strategic importance and comprehensive surveillance make it unlikely that conventional explanations were overlooked.
SKEPTIC ANALYSIS
Conventional Aircraft Misidentification
Washington D.C. airspace in 1966 was among the busiest and most controlled in the world, with constant military and civilian traffic to Andrews Air Force Base, National Airport (now Reagan), and numerous government helicopter operations. The most parsimonious explanation is misidentification of conventional aircraft, possibly under unusual atmospheric conditions that affected visual appearance or radar returns. Temperature inversions, which famously caused the 1952 Washington radar incidents, remained common in the area and could create false radar targets or cause unusual refraction of light.
06 Verdict
ANALYST VERDICT
Without access to the actual case file contents, no definitive conclusion can be reached regarding this incident. The case merits a 'medium' priority rating based solely on its Washington D.C. location and official Project Blue Book documentation, both factors that typically indicate a certain baseline level of credibility and investigative attention. However, the absence of specific details prevents assessment of the actual phenomenon reported, witness reliability, or the strength of evidence collected. The case could range from a misidentified conventional aircraft or astronomical object to an unexplained radar contact of genuine scientific interest. To properly evaluate this incident, researchers would need to access the complete PDF file from the Archive.org repository, which should contain the original Blue Book record card, witness questionnaires, investigator notes, and any photographic or technical data collected. Until such documentation is reviewed, this case remains an intriguing but unverifiable entry in the Project Blue Book catalog from a historically significant year and location.
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.