Verified Brief: Tesla Reported ADAS Engaged in Naples I-75 Triple-Fatal Crash
Verified Brief · NHTSA Primary Record · November 16, 2026

A Tesla-submitted NHTSA record says ADAS was verified engaged in a fatal 2023 Model 3 crash on I-75 near Naples, Florida, in May 2026. It lists 71 mph pre-crash speed and telematics availability. The public file does not identify FSD or Autopilot and does not establish what caused the collision.
30-Second Brief
- NHTSA’s public Level 2 ADAS CSV contains one matching Naples record, report 13781-16748, submitted by Tesla for a May 2026 crash.
- The row identifies a 2023 Model 3, a highway traffic incident, a fatality, ADAS and the engagement status “Verified Engaged.”
- It lists 71 mph as the subject vehicle’s pre-crash speed, marks telematics as available and names Florida Highway Patrol as the investigating agency.
- WGCU reported that on May 31 the Tesla struck an overturned box truck and a person who had stopped to help; three people died.
- The feature version, operational-design-domain field and narrative are redacted. Engagement does not prove causation, and 71 mph is not necessarily impact speed.
What Happened
Electrek published its match on November 16, 2026 after comparing Tesla’s NHTSA submission with a fatal May 31 collision on southbound I-75 near Naples, Florida. Tesstudio independently downloaded the official CSV and found exactly one report with ID 13781-16748.
WGCU, citing a Florida Highway Patrol report, said an overturned box truck blocked two lanes shortly before 4 a.m. A southbound Tesla struck the underside of the truck and a person who had stopped to assist. Two Tesla passengers and the person who stopped died; the Tesla driver and two passengers were seriously injured. The local report did not identify driver-assistance use.

What Is Confirmed
- Reporting entity and vehicle: The public row names Tesla, Inc., a 2023 Tesla Model 3 and a consumer driver.
- Location and period: The row lists Naples, Florida, May 2026 and 07:56 UTC. WGCU dates the crash to May 31.
- Automation field: “Automation System Engaged?” is ADAS and “Engagement Status” is “Verified Engaged.” This is information Tesla submitted under the SGO framework.
- Roadway, outcome and speed: The row lists a highway traffic incident, fatality and 71 mph pre-crash speed.
- Available data: The released record marks telematics as available and names Florida Highway Patrol as the investigating agency.
- Redactions: The feature version, whether the vehicle was within its operational design domain and the narrative are withheld as claimed confidential business information.
What Remains Unconfirmed
The released record does not say the assistance system caused or contributed to the collision. It does not show steering, braking, accelerator input, driver-monitoring status or the sequence immediately before impact. The public row also does not identify whether Autopilot, FSD or another Level 2 configuration was engaged.
The 71 mph value is a reported pre-crash field, not necessarily the speed at impact and not proof that software selected the speed. The released CSV does not include the underlying telematics. No causal conclusion should be drawn without that evidence and the complete investigation record.
Why It Matters
NHTSA’s SGO data are one of the few public sources showing when manufacturers report driver-assistance engagement near serious crashes. The same agency page warns that reports can be incomplete, that reporting entities have different access to telemetry and that the data are not normalized by vehicle count or miles driven.
For safety reporting, the disciplined conclusion is narrow: Tesla reported verified ADAS engagement in this incident. Determining cause requires evidence that the public CSV does not contain. That distinction protects both the public’s right to know about engagement and the integrity of the investigation.
What Tesla Owners Should Know
- Treat assistance as supervised. Tesla’s Model 3 manual says Autosteer requires an attentive driver who is ready to take immediate action.
- Do not use engagement as a cause label. A crash report can show a system was on without proving it initiated the maneuver or prevented driver control.
- Take over around unexpected roadway hazards. Brake, steer or disengage when a stopped vehicle, debris, emergency scene or dark obstacle appears ahead.
- Do not rely on a displayed set speed. Drivers remain responsible for selecting a safe speed for visibility, traffic and road conditions.
- Preserve evidence after an incident. Save available dashcam clips and provide accurate information to police, insurers and NHTSA.
- Report suspected safety defects. Owners can file a complaint through NHTSA’s vehicle-safety reporting channel.
Tesstudio Analysis
Tesstudio scores this development 90.85 because a fresh specialist report surfaced a distinct, readable Tier 0 NHTSA record about a fatal collision, and Tesstudio independently matched every material released field. The evidence is sufficient to report engagement and the public data fields, but not to assign causation or name the redacted feature.
The editorial test is whether every strong verb maps to a field. “Verified engaged” does. “Caused,” “failed to detect” and “FSD crash” do not. Any later police finding, NHTSA investigation, unredacted data or Tesla statement should be added to this event page rather than spun into a duplicate.
Sources & Reporting Notes
- NHTSA: Standing General Order on Crash Reporting — primary explanation of reporting requirements, limitations, redactions and public data.
- NHTSA: Level 2 ADAS Incident Report Data — primary CSV containing report 13781-16748.
- Tesla Model 3 Owner’s Manual: Autosteer — company instructions on supervision, intervention and feature limitations.
- WGCU: May 31 Naples I-75 crash report — independent local reporting based on Florida Highway Patrol.
- Electrek: November 16 NHTSA-record report — specialist report that surfaced and matched the public row.
Reporting note: NHTSA says public SGO data reproduce information submitted by reporting entities except protected or redacted fields and should not be treated as a normalized safety-rate dataset. Tesstudio verified the row directly and labels Tesla-submitted fields as such. The names of the people killed are omitted because they are not needed to explain the public-safety evidence.
Update & Correction Log
November 16, 2026: Initial publication. This brief reports a May 31 event and does not present the underlying crash as new. It distinguishes verified engagement from causation, avoids naming the redacted feature and identifies 71 mph as a company-submitted pre-crash field rather than confirmed impact speed.



Hinterlasse einen Kommentar
Diese Website ist durch hCaptcha geschützt und es gelten die allgemeinen Geschäftsbedingungen und Datenschutzbestimmungen von hCaptcha.