Verified Brief: Tesla Reported ADAS Engaged in Moraine Fatal Motorcycle Crash

Verified Brief · NHTSA Primary Record · September 3, 2026

30-Second Brief

• NHTSA’s public Level 2 ADAS CSV contains one matching Moraine record, report 13781-11411, submitted by Tesla for a July 2025 crash.
• The record identifies a 2024 Model X, a motorcycle crash partner, a fatality, ADAS and the engagement status “Verified Engaged.”
• It lists 49 mph as the subject vehicle’s pre-crash speed and marks EDR, police report, telematics and video as available.
• The automation feature version, operational-design-domain field and narrative are redacted. The public file cannot distinguish Autopilot from FSD.
• Engagement does not prove causation. Electrek linked the row to a July 23, 2025 Moraine police report, but the underlying files are not public in the dataset reviewed here.

What Happened

Electrek published its match on September 3, 2026 after comparing Tesla’s NHTSA submission with a fatal motorcycle collision reported in Moraine, Ohio. The outlet linked the row to a July 23, 2025 crash near Germantown Pike and Hemple Road.

Tesstudio independently downloaded the official NHTSA CSV and found exactly one report with ID 13781-11411. The released fields identify Moraine, a 2024 Model X, a motorcycle crash partner, fatality, 49 mph pre-crash speed and ADAS “Verified Engaged.” NHTSA’s public row reports only the month, not the exact day.

What Is Confirmed

• Reporting entity and vehicle: The public row names Tesla, Inc., a 2024 Tesla Model X and a consumer driver.
• Location and period: The row lists Moraine, Ohio, and July 2025. Electrek reports a July 23 date based on the local collision record.
• Automation field: “Automation System Engaged?” is ADAS and “Engagement Status” is “Verified Engaged.” This is information Tesla submitted under the SGO framework.
• Crash partner, outcome and speed: The row lists motorcycle, fatality and 49 mph pre-crash speed.
• Available data: The released record marks EDR, police report, telematics and video as available to the reporting entity.
• 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, right of way or the sequence immediately before impact. The public row also does not identify whether Autopilot, FSD or another Level 2 configuration was engaged.

The 49 mph value is a reported data field, not proof that software selected that speed. The released CSV does not include the underlying video, event-data-recorder data, telematics or police report, even though Tesla marked those materials as available. No causal conclusion should be drawn without reviewing that evidence.

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

1. Treat assistance as supervised. Tesla’s Model X manual says Autosteer requires an attentive driver who is ready to take immediate action.
2. 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.
3. Watch for motorcycles and intersections. Drivers remain responsible for yielding, speed, path choice and intervention whenever assistance is active.
4. Take over whenever conditions look unsafe. Brake, steer or disengage the feature as appropriate; do not wait for the system to resolve an obvious hazard.
5. Preserve evidence after an incident. Save available dashcam clips, photograph the scene when safe and provide accurate information to police, insurers and NHTSA.
6. Report suspected safety defects. Owners can file a complaint through NHTSA’s vehicle-safety reporting channel.

Tesstudio Analysis

Tesstudio scores this development 87.75 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

1. NHTSA: Standing General Order on Crash Reporting — primary explanation of reporting requirements, limitations, redactions and public data.
2. NHTSA: Level 2 ADAS Incident Report Data — primary CSV containing report 13781-11411.
3. Tesla Model X Owner’s Manual: Autosteer — company instructions on supervision, intervention and feature limitations.
4. Electrek: September 3 Moraine NHTSA-record report — specialist report that surfaced the record and linked it to the local crash.

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 report directly and labels Tesla-submitted fields as such. The victim’s name is omitted because it is not needed to explain the public-safety evidence.

Update & Correction Log

September 3, 2026: Initial publication. This brief reports a July 2025 event and does not present the underlying crash as new. It distinguishes verified engagement from causation, avoids naming the redacted feature and identifies 49 mph as a company-submitted public-record field.