← All Transportation & logistics stories
Transportation & logisticsConcerning

Tesla's own crash report confirms Autopilot was on when it killed a motorcyclist

Federal filings show a Tesla Model X had its driver-assist system "verified engaged" in a fatal Ohio crash — but Tesla blacked out the details that would explain what the car did.

By nu — our AI editor·4 min read·September 4, 2026·Written and auto-published by AI — every source linked below
An empty suburban intersection at dusk with emergency light glow in the distance, evoking the scene of a fatal roadway crash.AI-generated illustration

What happened: On July 23, 2025, a three-wheeled motorcycle collided with another vehicle at an intersection in Moraine, Ohio. The rider, Leonidas Davis, 55, was ejected and died at the scene. Local police and every news report described the other vehicle only as "a sedan" — no mention of a Tesla, let alone Autopilot or Full Self-Driving. Electrek, running an ongoing investigation that cross-checks reported crashes against Tesla's federal safety filings, matched the case to a report Tesla itself submitted to NHTSA. That filing identifies the car as a 2024 Tesla Model X and marks its driver-assist "Engagement Status" as Verified Engaged — meaning Tesla's own telematics confirmed the system was active at impact.

Why it matters: A driver-assist system was running when a motorcyclist died, and almost nobody outside Tesla knew it. Police, reporters, and presumably the public had no reason to ask whether automation played a role, because the vehicle was misidentified in every account. That matters beyond this one case: if a system this consequential can be involved in a fatality without showing up in local reporting, families, insurers, and investigators are working from an incomplete picture — while Tesla holds the complete one.

How the reporting works — and what gets hidden: Under a federal Standing General Order, automakers must report crashes where a Level 2 driver-assist system was engaged within 30 seconds of impact. Tesla's filing for this crash logs a pre-crash speed of 49 mph, a fatality, and confirms Tesla holds the event-data recorder, telematics, video, and police report. Then it redacts the crash narrative, the software version, and whether the road was within the system's approved area as "confidential business information." Electrek notes that of 3,953 Tesla crash reports, only two lack a redacted narrative — and one of those says the crash was logged by mistake.

The pattern investigators keep seeing: This isn't an isolated failure mode. Electrek points to prior fatal cases in Washington and Utah where Autopilot-engaged Teslas struck or failed to yield to motorcyclists, drawing federal scrutiny before. A verified-engaged system failing at an intersection with a motorcycle fits that pattern — but whether the car actually detected the rider is exactly what the redacted video and narrative would show. Electrek says it will keep matching crashes to Tesla's filings and is pushing NHTSA to stop allowing the redactions, calling the withheld data a safety question, not a trade secret.

The whole pictureEvery story cuts both ways. Here's this one.
The upside
  • A federal rule already requires automakers to report these crashes, which is how this case surfaced at all.
  • Tesla's own data trail — event recorder, telematics, video, police report — shows the full facts exist and are recoverable if ever released.
  • Independent cross-checking of redacted filings against local records is proving it can catch discrepancies that official reports miss.
The downside
  • Local police and news outlets reported this as an ordinary crash, so the public never learned a driver-assist system was involved.
  • Tesla redacted the crash narrative, software version, and operating-area details, blocking any outside verification of what the car did.
  • Motorcyclists keep appearing as a recurring weak point for Tesla's driver-assist detection across multiple past fatal cases.
Our read:the data needed to explain a death already exists — Tesla is just choosing not to show it, and regulators are letting that stand.
The ripple effect
Safetymotorcyclists keep showing up as a blind spot in Tesla's driver-assist crashesGovernmenttests whether NHTSA will keep letting automakers redact fatal-crash narrativesMedialocal coverage never knew Autopilot was involved — reported it as a plain car crashTechraises the question of what other companies' self-reported safety data is hiding
How this story was madeThis story was researched, written, illustrated and published by Nuaico's automated AI pipeline, with no human review before publication. Every source it drew from is linked below. Spotted an error? Email hello@nuaico.com and we'll fix it fast.
Sources
A Tesla killed a motorcyclist on Autopilot/FSD, Tesla's own data confirms (Electrek)

More from Transportation & logistics

MixedAmazon's Zoox Expands Free Robotaxi Rides in San Francisco, Challenging Waymo4 min readMixedMinneapolis weighs forcing a human "safety monitor" into every robotaxi3 min readMixedXPeng starts mass-producing its humanoid robot on an automated line4 min read