Tesla’s own reports to federal safety regulators show its driver-assist software engaged in two crashes this year that killed six people in total. One was a fiery single-car crash in El Dorado Hills, California, and the other was on Interstate 75 near Naples, Florida. In both reports, Tesla marks Autopilot or “Full Self-Driving” as “Verified Engaged” and logs pre-crash speeds of 74 mph and 71 mph.12 Electrek published both cases on November 16 as part of its ongoing look at fatal crashes in Tesla’s NHTSA data. It matched each filing to the crash described by police.12
What the filings are
NHTSA’s Standing General Order requires automakers to report any crash where a Level 2 driver-assist system was engaged within 30 seconds of impact and someone was killed or hurt.1 The agency began requiring these reports in July 2021.3 In both new reports, Tesla says it confirmed through its own vehicle telematics that Autopilot or FSD was on.12
Both filings also redact the crash narrative, the software version and whether the road was inside the system’s approved operating domain, citing “confidential business information.” Electrek says Tesla treats 99.9% of its reports this way.12

The El Dorado Hills crash
Late on Saturday, September 12, 2026, a 2024 Tesla Model Y with four people inside was heading west on Serrano Parkway in El Dorado Hills, a residential community east of Sacramento.1 According to the California Highway Patrol’s Placerville office, the car left the road “for unknown reasons,” hit a tree on the north side of the parkway and caught fire. Officers were called at about 10:38 p.m., and when they arrived the car was fully engulfed.1
Charles Anthony Cameron, 30, of Sacramento, died at the scene. Alejandra Mendoza, 28, of Sacramento, and Kailauna Viola Mills, 28, of Roseville, were found inside after the fire was put out. A fourth person, a 28-year-old Sacramento woman, survived with major injuries.1 CHP says the cause is still under investigation. It has not said which of the two women was driving, and it has not released details on speed or impairment.1
Tesla’s report lists a 2024 Model Y, “Verified Engaged,” a pre-crash speed of 74 mph and a fatality, with CHP as the investigating agency. The report lists the roadway type and the object struck as “Unknown,” and it names the media as the only way Tesla learned of the crash.1 Electrek matched the report to the crash by time. Tesla logged the incident at 10:36 p.m. Pacific, two minutes before the call CHP responded to, and Electrek says it is the only fatal Tesla driver-assist report from El Dorado Hills in the data.1
The Naples I-75 crash
Just before 4 a.m. on Sunday, May 31, 2026, the driver of a 2014 Freightliner box truck lost control near the Pine Ridge Road exit in Collier County, Florida, and the truck flipped on southbound I-75, blocking the center and outside lanes, according to the Florida Highway Patrol.2 Jonathan Garcia Arias, a 25-year-old Naples man and former Marine, pulled over in his BMW and got out to help the truck driver.2
A southbound 2023 Tesla carrying five young men from Naples then reached the scene. FHP’s report says the front of the Tesla hit the underside of the overturned truck and Garcia Arias. Two of the Tesla’s passengers, aged 18 and 19, died at the scene, and Garcia Arias later died in the hospital. The 20-year-old driver and two other passengers were seriously hurt.2 Senior Trooper Kenn Watson said the Tesla driver would have seen only the truck’s underside, with “no lights, no reflectors, nothing warning them.”2
Tesla’s report identifies a 2023 Model 3 on a highway, marks it “Verified Engaged” and logs a pre-crash speed of 71 mph and a fatality. It says Tesla learned of the crash from police and the media.2 Tesla filed it as a 5-Day report, the urgent category for fatal crashes, but it only appeared in Tesla’s September filings, more than three months after the crash.2 Electrek matched the incident time Tesla logged, 3:56 a.m. Florida time, to the 3:54 a.m. in FHP’s report.2

What the reports can and cannot show
Electrek spelled out the limits of the data itself. “Engaged within 30 seconds” is only the reporting trigger. The 71 mph figure may be a telematics snapshot rather than the speed at impact. And because the software version is redacted, it isn’t possible to say whether Autopilot or FSD was running.2 In California, CHP has not said how the car left the road. Electrek also says it is not suggesting the doors played any role in the fire.1
In other words, the filings show that Tesla’s system was on in the seconds before each crash. They do not establish what caused either one. That will be up to the CHP and Florida Highway Patrol investigations.
Tesla’s position on driver supervision
Tesla has been clear for years that neither system makes the car drive itself. Its website has described Autopilot this way:4
Autopilot enables your car to steer, accelerate and brake automatically within its lane. Current Autopilot features require active driver supervision and do not make the vehicle autonomous.
Tesla also warns that Full Self-Driving still requires driver attention. It says using the features without supervision depends on reliability far beyond human drivers, shown over billions of miles, plus regulatory approval.4 In a 2018 review of an earlier crash, Tesla said drivers are repeatedly told the features do not make the car “autonomous” and that they must keep their eyes on the road and their hands on the wheel.5
Elon Musk has framed the case for the technology in terms of lives saved. Responding to that 2018 crash, he wrote:5
It certainly needs to be better & we work to improve it every day, but perfect is enemy of good. A system that, on balance, saves lives & reduces injuries should be released.
In December 2023, around a software recall of more than 2 million vehicles, Tesla said it had a “moral obligation” to keep improving its “best-in-class safety systems.” It called halting driver-assist rollout “morally indefensible,” citing what it described as data showing the technology saves lives.3 At the time, Tesla cited fourth-quarter 2022 data showing one crash for every 4.85 million miles driven with Autopilot engaged.3 None of the sources show Tesla commenting on the two new crashes.
The wider picture and the criticism
The NHTSA release that surfaced the Naples report covers filings through October 15. In it, Tesla reported 264 driver-assist crashes in September 2026, a new monthly high, up from July’s 236 and 135 in March. Electrek notes that the September number may still grow as late reports come in.2 Electrek’s merged dataset now holds 4,669 Tesla driver-assist crash reports since 2019, 69 of them flagged as fatal.2 The same release also included a fatal “Verified Engaged” report involving a Model X that hit a signal pole in Naples on September 30.2
Electrek is openly critical. It argues that Tesla’s redaction of the crash narratives keeps the public from learning what the cars did, and that trust in FSD has to be earned with data.12 Missy Cummings, a former NHTSA senior safety adviser, made a similar point in 2023: Tesla’s safety figures can’t be taken at face value unless they can be independently verified.3 Tesla’s side, as set out above, has been consistent for years. These are supervised systems, drivers are responsible for paying attention, and the company believes the technology makes driving safer overall.435
What to watch next
- CHP Placerville’s findings on how the Model Y left Serrano Parkway. Electrek says it has asked whether investigators knew the system was engaged and whether they received Tesla’s raw data.1
- The Florida Highway Patrol’s final account of the I-75 crash.2
- NHTSA’s next data release, which may add late September reports to the record count.2
- Any statement from Tesla on either crash. ENN will follow this thread as new facts come out.



