Fatal Crash Involving Tesla Full Self-Driving Claims Employee's Life

In May 2022, a Tesla employee, Hans von Ohain, died in a fatal crash in Evergreen, Colorado, after his Model 3 veered off a mountain road and struck a tree, resulting in a severe fire. While the driver was found to have a blood alcohol level significantly above the legal limit, the passenger alleged that the vehicle's Full Self-Driving (FSD) feature was engaged. Investigators noted the absence of skid marks and the presence of rolling tire marks, suggesting the vehicle's propulsion system remained active upon impact, though Tesla and CEO Elon Musk have disputed whether FSD was active or even installed on the vehicle.

A Tesla employee, Hans von Ohain, was killed in a crash while allegedly using the Full Self-Driving feature. The car failed to navigate mountain curves, leading to a fatal collision, possibly making von Ohain the first known fatality of the Full Self-Driving feature.

Source: AI Incident Database

Risk classification

  • Primary risk domain: 7 AI system safety, failures, & limitations
  • Primary risk subdomain: 7.3 Lack of capability or robustness

The primary failure was the AI system's inability to safely navigate a winding mountain road, resulting in the vehicle veering off course and crashing.

Additional risk subdomains

  • 5.1 Overreliance and unsafe use: The driver relied on the FSD system to navigate while heavily intoxicated, reflecting a false sense of security and overreliance on the technology.

Causal factors

  • Entity: AI
  • Intent: Unintentional
  • Timing: Post-deployment

The incident was caused by the Tesla FSD beta system unexpectedly veering off the road and failing to negotiate a curve after deployment.

EU AI Act risk tier

  • Risk tier: 2 High Risk

High Risk: The system is an AI safety component in road traffic and critical infrastructure (autonomous driving), which has significant implications for physical safety and public interest.

AI system and alleged parties

  • AI system: Full Self-Driving Beta (Tesla)
  • AI purpose: Autonomous Driving; Navigation Assistant
  • Behaviour type: Autonomous
  • Alleged developer: Tesla
  • Alleged deployer: Hans von Ohain
  • Alleged harmed parties: Hans von Ohain, Erik Rossiter

Harm severity

Severity ratings are based on this scale.

Highest direct severity in any category: Substantial. Severity is scored from Negligible to Catastrophic in each harm category, for harm the reports describe as caused directly or indirectly by the AI system.

  • Physical: direct Substantial, indirect Negligible
  • Infrastructure: direct Negligible, indirect Negligible
  • Property: direct Minor, indirect Negligible
  • Financial: direct Negligible, indirect Negligible
  • Environmental: direct Negligible, indirect Negligible
  • Malicious content: direct Negligible, indirect Negligible
  • Differential treatment: direct Negligible, indirect Negligible
  • Civil rights: direct Negligible, indirect Negligible
  • Democracy: direct Negligible, indirect Negligible
  • Privacy: direct Negligible, indirect Negligible
  • Psychological: direct Minor, indirect Negligible
  • Epistemic: direct Negligible, indirect Negligible
  • Child sexual exploitation and abuse: direct Negligible, indirect Negligible

Physical

Reported: The report explicitly describes physical harm to people caused directly by the incident.

Directly caused: Hans von Ohain died at the scene from smoke inhalation and thermal injuries after the vehicle crashed and caught fire. The passenger, Erik Rossiter, survived the crash with minor physical injuries.

Property

Reported: The report explicitly describes property damage caused directly by the incident.

Directly caused: The 2021 Tesla Model 3 was completely destroyed by the crash and subsequent fire.

Psychological

Reported: The report explicitly describes psychological distress resulting from the incident.

Directly caused: Erik Rossiter experienced severe trauma from surviving the crash and attempting to pull his screaming friend from the burning car. Nora Bass (widow) and family experienced severe grief and distress.

People affected

  • Occurrences reported: 1
  • People reportedly harmed: 2
  • People reportedly exposed: 2

Potential causes

Management

  • Misleading Marketing Claims: Promoted FSD as autonomous and better than humans, creating false safety.
  • Aggressive Software Deployment: Rushed beta software to public roads to boost company value and data.
  • Poor Post-Crash Communication: Company failed to acknowledge the death and sent a termination notice.

Technology

  • Erratic FSD Beta Navigation: Software struggled on curvy roads and swerved repeatedly before the crash.
  • Post-Impact Power Deployment: System continued sending power to wheels after collision without braking.
  • Lithium-Ion Battery Flammability: Undercarriage batteries fueled an intense fire that trapped the driver.

Data Inputs

  • Missed Road Markings: FSD software struggled with unclear lane markings and winding road geometry.
  • Inability to Transmit Logs: Remote country location prevented over-the-air transmission of crash data.

Human Factors

  • Severe Driver Intoxication: Driver BAC was 0.264, severely impairing reaction time and control.
  • Overreliance on Automation: Driver relaxed attention, trusting FSD to handle winding mountain roads.
  • Ignored System Limitations: Driver engaged FSD on curvy roads despite manual warnings against it.

Process and Methods

  • Testing Beta Tech on Public Roads: Releasing unfinished FSD Beta to public users increases real-world risks.
  • Inadequate Escape Training: Very few owners know how to use the manual door release if electronics fail.
  • Lack of Cabin Attention Checks: System failed to ensure driver kept hands on wheel and eyes on the road.

Regulatory Environment

  • Insufficient Autonomous Oversight: Lack of strict federal standards for deploying Level 2 beta software.

Information quality

  • Classification confidence: Medium
  • Reason for confidence: There is strong evidence from the passenger and crash dynamics (rolling tire marks, no skid marks) that a driver-assistance feature was engaged. However, because the vehicle was completely destroyed by fire, physical logs could not be recovered, and Tesla claimed it did not receive over-the-air data, leaving some ambiguity about whether FSD or Autopilot was active, or if it was active at all, which Elon Musk disputes.
  • Ambiguities identified: Whether FSD was actually active at the moment of the crash, as the vehicle logs were destroyed and Tesla/Musk deny FSD was downloaded or active.
  • Alternative interpretations: The crash could be interpreted purely as a drunk-driving accident where the driver fell asleep or lost control due to extreme intoxication (BAC 0.264), independent of any AI system involvement.
  • Missing information: The vehicle's internal telemetry logs and over-the-air data confirming whether FSD or Autopilot was engaged and active at the time of the crash.

A fatal crash involving a Tesla Model 3 potentially operating on Full Self-Driving beta in Colorado. While tragic, the incident is a consumer safety and regulatory issue with negligible implications for national security.

  • Overall national security impact: Negligible
  • Scope: Single nation
  • Primary target: No clear primary
  • Alleged perpetrator: Unknown

Threat characteristics

  • Imminence: Long-term. The incident represents an ongoing regulatory and safety concern regarding autonomous vehicle deployment rather than an immediate security crisis.
  • Autonomy: Human-supervised. Tesla's FSD beta is a Level 2 driver-assist system requiring active human supervision and intervention, which the intoxicated driver failed to provide.
  • Novelty: Established threat. Crashes involving Level 2 driver-assist systems and driver overreliance or inattention are well-documented and have occurred previously.

Impact by dimension

  • Physical security: Negligible. The incident was a localized consumer vehicle accident resulting in one fatality. It did not compromise critical infrastructure, military systems, or national physical security.
  • Information security: Negligible. There is no indication of intelligence compromise, classified data theft, or information warfare operations associated with this crash.
  • Sovereignty: Negligible. This safety event did not impact state authority, border control, electoral processes, or core government operations.
  • Economic security: Negligible. Economic impact was limited to the loss of a single consumer vehicle. There was no theft of strategic AI technology or systemic threat to financial markets.
  • Societal stability: Negligible. The crash was an isolated public safety incident and did not involve mass surveillance, algorithmic oppression, or threats to civil liberties.
Explore in the interactive Incident Tracker