DEPLOYDatabase

Retracted · 2026-10-11

Duplicate ingestion of the same event as nhtsa-sgo-13781-15395, the canonical record for "undefined". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction policy.

Incident · Property damage · Retracted

Tesla Robotaxi remote operator drives vehicle into tree stump in Houston

Original claim shown above is no longer asserted. See the retraction notice for context.

A Tesla Robotaxi Model Y was stopped on a dead-end residential road in Houston when a remote assistance operator took control to recover the vehicle. The operator drove the car onto a grassy slope and made contact with a hidden tree stump at approximately 2 mph.

This is the third crash Tesla has reported involving a remote operator causing a collision, and the first time Tesla formally coded the driver type as remote operation in its NHTSA filing. Damage was minor with no injuries.

Occurred 2026-05-15 · Tesla Robotaxi (Model Y ADS) at Houston · Tesla · Houston · Robotaxis

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.

Machine-readable surfaces

Sources (1)

  1. Electrek · https://electrek.co/2026/07/20/tesla-robotaxi-remote-operator-crash-houston/ · 2026-07-20

Status history

  • Retracted · 2026-10-11 · correction:tesla-cleanup-2026-10-11

    Duplicate ingestion of the same event as nhtsa-sgo-13781-15395, the canonical record for "undefined". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction policy.

Common questions

What happened in Tesla Robotaxi remote operator drives vehicle into tree stump in Houston?
A Tesla Robotaxi Model Y was stopped on a dead-end residential road in Houston when a remote assistance operator took control to recover the vehicle. The operator drove the car onto a grassy slope and made contact with a hidden tree stump at approximately 2 mph. This is the third crash Tesla has reported involving a remote operator causing a collision, and the first time Tesla formally coded the driver type as remote operation in its NHTSA filing. Damage was minor with no injuries. This incident was later retracted; see the retraction banner at the top of the page for the correction.
When did this incident occur?
The incident is recorded as occurring on May 15, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Tesla Robotaxi remote operator drives vehicle into tree stump in Houston?
Tesla Robotaxi (Model Y ADS) by Tesla is the recorded robot involved in this incident at Houston.
Has anyone responded to Tesla Robotaxi remote operator drives vehicle into tree stump in Houston?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Tesla Robotaxi remote operator drives vehicle into tree stump in Houston?
This incident is retracted on the DEPLOY registry. The page remains so the correction reaches readers, but the incident is suppressed from aggregate counts (company / model / location) so it no longer counts against anyone.
Methodology: Verified · 1 source (no primary) · last reviewed 2026-10-11

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-10-11

Sources by quality tier

1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Tesla Robotaxi remote operator drives vehicle into tree stump in Houston.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.


Canonical ID 2172b898-daae-4564-91b0-58f7920a6e2a