A Tesla Model 3 driver died after a truck rear-ended the vehicle while it was stopped in a highway lane near Mesa, Arizona, while a record Tesla submitted to the U.S. National Highway Traffic Safety Administration (NHTSA) showed that the driver-assistance system was activated before the crash. Electrek’s investigation says this is the second documented incident with the same characteristics within weeks, following a similar crash in Florida.
What happened on Highway 202
Shortly after 3 a.m. on October 31, 2025, a Ford F-350 truck rear-ended a Tesla sedan in the eastbound lane of Loop 202 near Dobson Road. The Tesla driver died at the scene, and the highway was closed for hours, according to reports from Arizona’s Family and 12News.
Initial coverage of the incident did not identify the vehicle as a Tesla and did not mention the use of Autopilot or Full Self-Driving. The Arizona Department of Public Safety also said that two vehicles were involved in the crash, without publishing extensive details about the injuries or the vehicle’s behavior before the collision.
What Tesla’s data reveals—and conceals
Electrek matched the crash details with a redacted report included in Tesla’s disclosures to NHTSA, under a standing order requiring automakers to report crashes in which a Level 2 driver-assistance system was activated during the 30 seconds preceding the collision.
The report identifies the vehicle as a 2020 Tesla Model 3 and classifies the activation status as “Verified Engaged.” It also records that the vehicle was stationary at zero speed in a highway lane, in clear weather and without unusual road conditions. The crash is described as a direct impact to the entire rear section of the vehicle by the front of the truck.
Tesla says it retains the event data recorder, telematics data, and video recordings. However, the report redacts three key fields: the crash narrative, the software version that would determine whether the system was Autopilot or Full Self-Driving, and whether the road was within the system’s approved operating domain. This information was classified as “confidential business information.”
Why does this pattern matter?
The record does not establish that the driver-assistance system caused the death. The vehicle may have stopped because of system behavior, or because of a medical condition affecting the driver while the system continued to keep the vehicle stopped; the redacted information could help distinguish between the two possibilities.
However, the crash matches another incident documented by Electrek in Florida: a 2020 Tesla Model 3, a driver-assistance system confirmed to be engaged, a zero-speed stop in a live highway lane, and then a fatal rear-end collision. The report notes that the known issue of phantom braking in Tesla systems is a possible explanation, not a proven conclusion in this incident.
Open questions for regulators
The broader issue is that public crash records may not reveal that a driver-assistance system was involved in the first place, while Tesla possesses the raw data and recordings capable of explaining what happened. Electrek says it submitted a public-records request to the Arizona Department of Public Safety and asked whether Tesla had shared telematics data or video with investigators; it also informed the department that Tesla’s record confirms the system was activated.
According to the report, Tesla is already under investigation by NHTSA regarding how it reports these crashes. Questions about why the vehicle stopped, the nature of the system in use, and whether the complete data reached investigators remain open pending the release of additional records or official findings.