Tesla Cybercab Hit in Austin: What Owners Should Know
Machine-coded, not yet reviewed. Spot a mistake? Email a correction.
What coverage reports
The report says a Tesla Cybercab collided with a party bike in downtown Austin on October 30, 2026, and that a piece of the vehicle’s door was torn off. It describes the collision as appearing low-speed and says no injuries had been reported. The report says whether the autonomy system was engaged or a remote operator was supervising had not been confirmed; neither Tesla nor Austin law enforcement had issued an official statement.
Machine-drafted from the reports listed below.
A Tesla Cybercab operating in downtown Austin, Texas was involved in a minor collision with a party bike on October 30, 2026, resulting in a piece of the vehicle's door being torn off.
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 | October 30, 2026 “on October 30, 2026” source |
|---|---|
Type of incidentincident_type | Collision “was involved in a minor collision with a party bike” source |
Collided withcollision_with | Other “a party bike” source |
Vehicle makevehicle_make | Tesla “A Tesla Cybercab” source |
Vehicle modelvehicle_model | Cybercab “A Tesla Cybercab” source |
Model yearvehicle_model_year | Not stated in the reports read |
Place and time
City or localitylocation_city | Austin “downtown Austin, Texas” source |
|---|---|
State or regionlocation_state_region | Texas “downtown Austin, Texas” source |
Countrylocation_country | Not stated in the reports read |
Road settingroad_type | Urban or suburban street “busy urban streets” source |
Time of daytime_of_day | Not stated in the reports read |
Automation
Automated-driving feature namedsystem_named | Self-driving feature (product not named) “the Cybercab's autonomy system” source |
|---|---|
Was the feature in use?engagement_status | Under investigation “Whether the Cybercab's autonomy system was engaged at the time, or whether a remote operator was supervising, has not been confirmed.” source |
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 | Not stated in the reports read |
|---|---|
Injuries reportedinjuries | 0 “No injuries have been reported in connection with the incident” 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 | Not stated in the reports read |
Coverage
Stage of coveragecoverage_stage | Not stated in the reports read |
|---|
Sources
About this record
Coded by OpenAI gpt-6-luna on November 22, 2026, codebook version 0.1. 0 proposed values were removed because the supporting passage could not be found in the report.
Cite as: CrimConsortium. Self-Driving Incidents Explorer, case SDI-00020. https://selfdriving.crimconsortium.com/cases/SDI-00020.html