Tesla remote operator crashed a ‘Robotaxi’ in Houston, NHTSA data shows
Machine-coded, not yet reviewed. Spot a mistake? Email a correction.
What coverage reports
Tesla’s filing says the Model Y was stopped on a dead-end residential road in Houston and needed help getting out. Tesla said the automated driving system was being supported remotely and that the remote assistance operator contacted a hidden tree stump while recovering the vehicle. The report says there was property damage and no injuries.
Machine-drafted from the reports listed below.
Tesla's latest NHTSA filings show four new 'Robotaxi' crashes, including a Houston incident where a remote operator drove the car into a tree stump.
Coded variables
Each value is followed by the passage it rests on. “Not stated” means the reports read did not say; it does not mean no. Definitions are in the codebook.
Incident
Incident dateincident_date | May 2026 “The incident, report 13781-15395, happened in May in Houston.” source |
|---|---|
Type of incidentincident_type | Collision “they made contact with a hidden tree stump.” source |
Collided withcollision_with | Fixed object “they made contact with a hidden tree stump.” source |
Vehicle makevehicle_make | Tesla “Tesla has filed four new “Robotaxi” crash reports with NHTSA” source |
Vehicle modelvehicle_model | Model Y “the Model Y “was stopped on a dead end residential road” source |
Model yearvehicle_model_year | Not stated in the reports read |
Place and time
City or localitylocation_city | Houston “happened in May in Houston.” source |
|---|---|
State or regionlocation_state_region | Not stated in the reports read |
Countrylocation_country | Not stated in the reports read |
Road settingroad_type | Urban or suburban street “a dead end residential road” source |
Time of daytime_of_day | Not stated in the reports read |
Automation
Automated-driving feature namedsystem_named | Robotaxi or driverless service “Tesla remote operator crashed a ‘Robotaxi’ in Houston” source |
|---|---|
Was the feature in use?engagement_status | Not stated in the reports read |
Who says it was in useengagement_claimed_by | Not stated in the reports read |
Someone in the driver's seatdriver_seat_occupied | Not stated in the reports read |
Driver condition mentioneddriver_condition_mentioned | Not stated in the reports read |
Harm
Deaths reportedfatalities | 0 “property damage only, no injuries, no airbag deployment, no tow” source |
|---|---|
Injuries reportedinjuries | 0 “property damage only, no injuries, no airbag deployment, no tow” source |
Who was harmedpersons_harmed | Not stated in the reports read |
Official response
Police actionpolice_action | Not stated in the reports read |
|---|---|
Criminal chargescriminal_charges | Not stated in the reports read |
Criminal case stagecriminal_case_stage | Not stated in the reports read |
Civil litigationcivil_litigation | Not stated in the reports read |
Regulator or safety boardregulator_involved | Not stated in the reports read |
Responsibility attributed toresponsibility_attributed_to | Driver “the remote assistance operator continued to recover the vehicle, they made contact with a hidden tree stump.” source |
Coverage
Stage of coveragecoverage_stage | Not stated in the reports read |
|---|
Who says what
- Manufacturer · Driver behaviorTesla’s report says the remote assistance operator contacted a hidden tree stump while recovering the vehicle.“As the remote assistance operator continued to recover the vehicle, they made contact with a hidden tree stump.” source
Sources
About this record
Coded by OpenAI gpt-6-luna on November 22, 2026, codebook version 0.1. 3 proposed values were removed because the supporting passage could not be found in the report.
Cite as: CrimConsortium. Self-Driving Incidents Explorer, case SDI-00052. https://selfdriving.crimconsortium.com/cases/SDI-00052.html