A Tesla Cybertruck Crashed on FSD Because the Driver Had Already Stopped Paying Attention
What happened
In February 2025, a Tesla Cybertruck running on Full Self-Driving failed to navigate a lane merge in Nevada, struck a curb, and drove into a pole. The vehicle sustained significant damage, including a heavily damaged front end and a detached wheel. The driver, Jonathan Challinger, walked away unhurt. The crash would have been a routine incident report, except for what Challinger said about it afterward.
Challinger told the story himself. He had activated FSD at the start of a trip and then stopped watching. He had documented this tendency in a January post on X, describing how he would turn on FSD, forget his destination, then notice the car turning toward a fast-food restaurant before remembering he had set that destination himself. After the February crash, he praised the Cybertruck's passive safety features and warned other FSD users to stay vigilant, framing his own inattention as the cause.
Police records viewed by Reuters attributed the accident to an "unknown mechanical issue," not driver error. That gap, Challinger blaming himself while investigators pointed at the machine, has become a predictable feature of FSD incidents. When a system is marketed as sophisticated enough to handle real traffic, drivers begin to act as though it actually can. Challinger had used FSD long enough to become comfortable with it. He was not behaving recklessly by any standard he had absorbed from watching the system work for months. He was behaving the way people behave when they trust something.
The timing sharpened the stakes. Tesla was publicly preparing to launch autonomous taxi services later in 2025. FSD is a semi-autonomous system that demands constant driver oversight, and Tesla says so in its own terms. But the product name and the surrounding marketing consistently implied a level of capability that the crash record does not support. That gap, between how a system is described and how it actually performs under ordinary conditions, is precisely what determines how much attention a driver believes it deserves from them.
What the incident does not produce is a clear account of what FSD commanded in the moments before impact, and why. The "unknown mechanical issue" cited by police was never publicly explained. Challinger's reconstruction came from memory, shared on social media. There is no requirement that a system like FSD generate a retrievable, independently verifiable log of every decision it made, what the vehicle state was at each step, and where the failure originated. Without a provable record of what a system did, crash investigations start from competing narratives, and the pattern of failures accumulates without any structural means to learn from it.
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.