Houston Cybertruck driver alleges FSD barrier crash caused injuries; Musk disputes system timing
A lawsuit reported by Electrek and Jalopnik alleges that a Houston Cybertruck driver was injured on 18 August 2025 when the vehicle headed into a freeway-overpass barrier while using FSD/Autopilot. She says she disengaged and grabbed the wheel too late to avoid impact; reported injuries include herniated discs and nerve symptoms. A later Tesla North report quotes Musk saying logs showed Autopilot had been disengaged four seconds before the crash. The petition, video and logs were not independently inspected, and the system's causal role remains disputed.
- AI system
- Tesla FSD / Autopilot (reported)
- Tesla
- Occurred
- 18 Aug 2025
- Reported
- 11 March 2026
- Event location
- United States
- What the AI did
- Acted on the person’s behalf
- Reported harm
- Physical Injury
- Whose AI use
- Their own AI use
- Setting
- Transport
- Evidence
- AI involvement disputed · Causal attribution disputed · 3 sources, 2 underlying accounts
- 3 claims: 3 reported. 2 open questions
- People reported harmed
- At least 1 person
AI system as recorded: Tesla Full Self-Driving / Autopilot driver assistance
What Happened
A lawsuit reported by Electrek and Jalopnik alleges that a Houston Cybertruck driver was injured on 18 August 2025 when the vehicle headed into a freeway-overpass barrier while using FSD/Autopilot. She says she disengaged and grabbed the wheel too late to avoid impact; reported injuries include herniated discs and nerve symptoms. A later Tesla North report quotes Musk saying logs showed Autopilot had been disengaged four seconds before the crash. The petition, video and logs were not independently inspected, and the system's causal role remains disputed.
Reported harm
Lawsuit-alleged injuries after the Houston barrier collision
What remains unknown
- The exact system version, timing and control state at impact are unresolved.
- The original petition, video and logs were not inspected; no court finding or medical record independently establishes causation.
What the evidence supports
AI involvement: disputed. Use before the crash is alleged by the driver; Musk's reported timing claim contests whether the system was active at impact. No dashcam footage, telemetry or original petition was inspected. AI involvement at the critical time and causation remain disputed.
3 claims: 3 reported. What the statuses mean
Reported The petition account dates the Houston crash to 18 August 2025 and alleges FSD/Autopilot headed into the barrier before the driver attempted manual intervention.
Causal attribution. The inspected reporting describes this account. Claims remain attributed and causation is alleged; multiple reports of the same victim or police/court account are one independence group.
- electrek.co(opens in new tab) supports · English
Electrek article section The crash: dated petition account and disengagement.
Reported The lawsuit reportedly alleges physical injuries including herniated discs and nerve symptoms after the collision.
Causal attribution. The inspected reporting describes this account. Claims remain attributed and causation is alleged; multiple reports of the same victim or police/court account are one independence group.
- jalopnik.com(opens in new tab) supports · English
Jalopnik article body: alleged crash injuries and lawsuit account.
Reported Tesla North quotes Musk saying vehicle logs showed Autopilot was disengaged four seconds before the crash.
Causal attribution. The inspected reporting describes this account. Claims remain attributed and causation is alleged; multiple reports of the same victim or police/court account are one independence group.
- teslanorth.com(opens in new tab) supports · English
Tesla North article body: 18 March statement about logs.
Sources
3 sources inspected, from 2 underlying accounts. Sources that repeat one account do not corroborate each other.
- Electrek, 11 March 2026, account of inspected petition(opens in new tab)
s1 · electrek.co · Journalistic · English · Inspected · 11 March 2026 · Shares an underlying account with another listed source · Primary
- journalistic supporting source(opens in new tab)
s2 · jalopnik.com · Journalistic · English · Inspected · Shares an underlying account with another listed source
- journalistic supporting source(opens in new tab)
s3 · teslanorth.com · Journalistic · English · Inspected
How the sources were read, and where the events happened
Event countries: United States. Affected-person countries: United States. Court countries: United States.
The crash is explicitly Houston, Texas, and litigation is in Harris County District Court. The driver is described as a Houston resident.
Reviewed for publication 2026-09-30: An inspected source describes a concrete person-level adverse experience connected to the specified AI use. Statements remain attributed, private identities are minimized, and unknown dates, counts and technical details are preserved.
People reported harmed in this case
At least 1 person
1 AI participant · 0 other people harmed
One driver reports injury while using the system. A child passenger is mentioned but no injury is reported, so the child is not counted.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). Houston Cybertruck driver alleges FSD barrier crash caused injuries; Musk disputes system timing. AI incidents. https://nope.net/incidents/2025-houston-cybertruck-driver-alleges-fsd-barrier-crash-injuries
BibTeX
@misc{2025_houston_cybertruck_driver_alleges_fsd_barrier_crash_injuries,
title = {Houston Cybertruck driver alleges FSD barrier crash caused injuries; Musk disputes system timing},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2025-houston-cybertruck-driver-alleges-fsd-barrier-crash-injuries}
} If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.