Cases › operational mistake › LR-2026-0633

Tesla Robotaxi remote operator crash into tree stump, Houston (May)

Preliminary Why: Publisher not yet named · subject to change

Status: action reported, no fix

Severity minor

Reported 20 Jul 2026

Developer and model Tesla

No source states: loss or records, agent tool, could do, deployer, industry.

A Tesla Model Y operating in the Robotaxi service in Houston was stopped on a dead end residential road when it needed help getting out. While the system was being supported remotely out of the road, the vehicle entered a grassy slope. As the remote operator continued to recover the vehicle, it made contact with a hidden tree stump. The damage was minor, with no injuries and a pre-crash speed of 2 mph. Tesla filed the crash with NHTSA and listed the operator type as remote, the first time it has done so across its 22 unique ADS reports. The filing was one of four Robotaxi crash reports Tesla submitted to NHTSA in this batch.

What happened

1 · What it reached or didThe remote assistance operator made contact with a hidden tree stump while recovering the vehicle.

2 · How it was caughtTesla reported the crash to NHTSA in a crash report.

What was done

Damage was minor and property only, with no injuries and no tow.

Risks

Physical harm
Primary43 incidents

Agent takes destructive or unapproved actions
Also63 incidents
Rising: 5 vs 2.2 a week

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Stop control

Application

Physical safety interlocks · Human approval for high-impact actions · Live behaviour monitoring · Adversarial testing before deployment

Similar incidents

Tesla Robotaxi crash reported to NHTSA (Austin, January 2026)2026-03-16

Tesla Robotaxi drives through Austin bollards and traffic barriers2026-08-18

Tesla Cybercab strikes water-filled pothole on first reported crash2026-10-15

NHTSA petition case DP26010 over Tesla robotaxi speeding in school zones2026-10-13

All cases of this kind ›

Evidence

No source states: what the AI was doing, what went wrong, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.

Show every field, with its source and grade

The AI system

Developer

Tesla

C one secondary source states it

What happened

Earliest source we hold

2026-07-20

D inferred by us from the described behaviour, reason shown

What went wrong

operational mistake

D inferred by us from the described behaviour, reason shown

Impact

Severity

minor

D inferred by us from the described behaviour, reason shown

Notes on gaps

The date of disclosure is not stated; the Electrek article date of 2026-07-20 is not used as a disclosure date. No remediation was reported, so remediations are empty. Electrek commentary and Waymo comparisons concern other companies or opinion and are excluded. Tesla's own narrative on the vehicle stopping is quoted as stated and the Electrek note on a backing contradiction concerns a different (Austin) report and is excluded.

LR-2026-0633 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON