When a Ford F-350 pickup slammed into the rear of a stopped Tesla Model 3 on eastbound Loop 202 near Dobson Road in Mesa last Halloween, initial reports described a routine two-vehicle freeway crash. Nearly ten months later, a redacted federal filing has revealed a detail no one disclosed at the time: the Tesla's driver-assist system was engaged when the car came to a stop in a live traffic lane, and it stayed there until the pickup hit it at 3 a.m.
The crash happened October 31, 2025, on the Red Mountain Freeway, according to 12News, which reported the Tesla sedan was stationary when the F-350 struck it. The Tesla driver died at the scene. At the time, the Arizona Department of Public Safety confirmed only that two vehicles were involved, and neither the make of the car nor the status of any driver-assist technology was mentioned in initial coverage, per the same station's report.
That changed when Tesla filed a crash report with the National Highway Traffic Safety Administration, as required under Standing General Order 2021-01, a federal rule mandating that automakers disclose any crash where an SAE Level 2 driver-assist system was engaged within 30 seconds of impact and the incident caused a fatality, hospitalization, airbag deployment, or struck a vulnerable road user, according to NHTSA. Electrek, which first connected the redacted filing to the Mesa crash, reported that the report confirmed the 2020 Model 3 was traveling at 0 mph with its automation status verified engaged, and that the Ford F-350 struck it across its entire rear.
What the Redacted Filing Does and Doesn't Show
Tesla's submission left major gaps. Under 49 CFR Part 512, automakers may withhold specific fields — including software build versions, whether the road fell within the driver-assist system's approved operating area, and the crash narrative itself — by filing confidential business information claims, according to NHTSA. Electrek reported that Tesla redacted the software version and crash narrative in this filing, and that such redactions appear on 99.9% of Tesla's submitted reports.
Electrek matched the redacted NHTSA record to the Mesa crash using unredacted fields — the city, vehicle model, month, and incident time in UTC — which lined up with a timestamp corresponding to roughly 3 a.m. Arizona time. The outlet has since filed a public-records request with the Arizona Department of Public Safety seeking the crash report and asking whether Tesla shared its data with investigators, and it told readers it does not know whether the driver-assist system caused the driver's death — only that it was engaged when the car sat motionless in a freeway lane.
A Nearly Identical Death in Florida
Electrek says the Mesa case is the second fatal crash it has documented with the same signature: a 2020 Tesla Model 3, verified engaged driver-assist, stopped at 0 mph in a live freeway lane, ending with the driver killed. The first happened October 6, 2025, when a 43-year-old Deltona man died after his 2020 Model 3 stopped in a live center lane of Interstate 4 near Lake Mary Boulevard in Seminole County, Florida, and was rear-ended by a semi-truck, according to the outlet's earlier reporting. Florida Highway Patrol said at the time that troopers could not explain why the vehicle had stopped in the middle of the highway.
Both crashes occurred in live freeway lanes within weeks of each other, one in Florida and one in Arizona, and Tesla holds the underlying telematics, video, and event-data-recorder information from both vehicles. Neither redacted filing discloses why the cars stopped, leaving open whether either crash involved a phantom-braking glitch, a system disengagement, or an unrelated medical emergency — a gap federal regulators and independent researchers have not yet resolved.
Phantom Braking and a Growing Federal Caseload
Tesla's Autopilot has a long-documented phantom braking problem, in which the system brakes hard for obstacles that aren't there, and that issue has drawn both an NHTSA investigation and a class-action lawsuit, according to Electrek's reporting. Federal regulators have separately opened multiple formal inquiries into Tesla's driver-assist systems examining phantom braking as well as failures to detect emergency vehicles and motorcyclists, per the Federal Register. Tesla is also currently under a separate NHTSA investigation over its crash reporting involving Autopilot and Full Self-Driving.
The volume of filings has climbed sharply. By mid-2026, Tesla vehicles accounted for more than 3,700 unique incident reports in NHTSA's Standing General Order Level 2 ADAS database — roughly half of all automated-driving-system crash reports filed by every automaker combined, according to EVBase. Regulators note the high count partly reflects Tesla's large fleet size and heavy ADAS usage rather than a normalized per-mile crash rate. Merged federal data reviewed by EVBase shows Tesla's monthly filings rising from 135 in March 2026 to 170 in April, then to a record 207 in May, a climb that coincided with expanded deployment of Tesla's Full Self-Driving Supervised software across its fleet.
Arizona Law and the Question of Driver Responsibility
Arizona law is unambiguous about stopping on a freeway. Arizona Revised Statutes § 28-870 bars drivers from stopping, standing, or parking in any freeway or controlled-access highway lane except during emergencies or when directed by law enforcement, according to AZ Law Now. Loop 202 carries high-speed commuter traffic where a stalled vehicle creates an immediate rear-end hazard, regardless of whether a driver-assist system or a human was in control when the car stopped.
The Arizona Department of Public Safety has maintained that Level 2 driver-assistance technology does not remove a driver's obligation to stay alert, warning that human operators are legally required to keep control of the vehicle and be ready to intervene instantly at all times. Hoodline reported those same DPS warnings following an Arizona driver's 78-mph blitz through an I-10 construction zone while allegedly relying on Autopilot. Electrek says it plans to continue matching future Tesla crash filings against redacted NHTSA reports as it works to identify more incidents with the same pattern.
In April 2025, federal regulators eased part of the reporting timeline for Level 2 crashes, extending automakers' deadline to submit reports from 24 hours to five days while keeping mandatory reporting in place for fatalities, hospitalizations, and airbag deployments, according to reporting at the time. That rule is what ultimately produced the paper trail connecting Tesla's confidential filing to the early-morning crash scene on eastbound Loop 202, where the freeway remained closed for hours while investigators worked.
