Autopilot Was On, a Motorcyclist Was Dead, and Investigators Had Only the Driver's Account to Go On
What happened
In April 2024, a 56-year-old man driving a 2022 Tesla Model S through Snohomish County, Washington, told police he was using Autopilot and looking at his phone when he heard a loud noise. The car lurched, then accelerated. Beneath it was Jeffrey Nissen, a 28-year-old motorcyclist who was pronounced dead at the scene, trapped under the vehicle. The driver was arrested and charged with vehicular homicide, a charge that turns on what he was doing and what the car was doing when Nissen's motorcycle entered the vehicle's path.
According to the police affidavit, the driver had been returning home from lunch. He activated Autopilot, looked down at his phone, and only realized something had gone wrong after the collision. Autopilot is marketed by Tesla as a driver assistance system that automates steering, acceleration, and braking, but Tesla's own documentation requires the driver to remain attentive with hands available at all times. The driver in this case was not doing that. The distinction between those two things, what the system is supposed to be and how drivers actually use it, is where Nissen was killed.
That tension between how Tesla markets the feature and how drivers use it is not new. Safety researchers and regulators have documented a consistent pattern: drivers treat Autopilot as a hands-free mode rather than an assistance layer that still requires supervision. The feature name contributes to this. When a system is called Autopilot, a reasonable person infers that it can be trusted to pilot the vehicle without intervention. Tesla has resisted renaming the feature despite years of documented misuse, and the gap between its marketing language and its legal disclaimers has widened with each crash it is cited in.
What made this case harder to investigate cleanly was a detail buried in the authorities' statement: they had not independently verified whether Autopilot was actually engaged at the time of the crash. The driver said it was. Tesla's internal data logs may have confirmed his account or told a different story, but independent access to those logs was not automatic. A criminal case built on vehicular homicide requires establishing what a driver was relying on and what the system was actually doing at the moment of impact, and those two things were not available to investigators without the manufacturer's cooperation.
This is the accountability gap the incident exposes. A driver assistance system operating on a public road is not a private device, and when it contributes to a fatality, the burden of verifying its state should not rest entirely on the manufacturer's disclosure. A provable record of what a system did, when it was active, and what decisions it was executing at the critical moment would change what investigators can establish on their own. Without it, every crash involving a driver assistance feature begins with a credibility contest between a driver's account and a company's logs.
Reported impact
- Affected parties
- Not publicly disclosed
- Harm type
- Not publicly disclosed
- Scale
- Not publicly disclosed
- Financial impact
- Not publicly disclosed
- Regulatory action
- Not publicly disclosed
Classification
Relevant governance controls
Governance control mapping is not available for this record.
- No controls mapped
Not publicly disclosed
Control mapping is analytical. It does not state that any control would have prevented the incident.
Sources and evidence
This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.