Cases › physical harm › LR-2026-0294
Tesla Cybercab collides with party bike in downtown Austin
Preliminary Why: Publisher not yet named · subject to change
Severity minor: a low-speed collision with localized door-panel damage and no injuries reported, contained to a single vehicle and no third-party loss stated.
Earliest source we hold 2026-10-30 · Captured by AI Risk Wire 2026-10-31 03:27 UTC
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. The collision appears to have been low-speed, and based on footage circulating on X the damage was localized to a door panel with no structural damage apparent. No injuries were reported, and as of publication neither Tesla nor Austin law enforcement had issued an official statement. Whether the Cybercab's autonomy system was engaged at the time, or whether a remote operator was supervising, has not been confirmed. The source notes that the operational mode at impact, the exact sequence of events, and Tesla's internal review status remain unconfirmed.
Risks this incident falls under
| Risk | Role | NIST AI 600-1 | Incidents | Last 6 quarters |
|---|---|---|---|---|
| Physical harm | Primary | No exact NIST AI 600-1 category | 3 |
Sorted by rule from the case's fields; not yet read from the sources.
Control failure chain
L1 · ModelProvider not namedModel provider
Sources not yet read for controls.
Model version not linked to a model card.
L2 · HarnessHarness not namedAgent framework vendor
Sources not yet read for controls.
1 more for this risk at this layer
L3 · ApplicationDeployer not namedDeployer
Sources not yet read for controls.
4 more for this risk at this layer
L4 · Infrastructure / targetOrganisation hitOrganisation hit
Sources not yet read for controls.
HeldFailedGot aroundMissingNot mentionedNot read yetAttacker's ownOrder: model · harness · application · target
The same controls in other incidents of this risk
| Control | Layer | Here | Held elsewhere | Did not hold elsewhere |
|---|---|---|---|---|
| Stop control | L2 Harness | Not read yet | – | – |
| Human approval for high-impact actions | L3 Application | Not read yet | – | – |
| Live behaviour monitoring | L3 Application | Not read yet | – | – |
| Adversarial testing before deployment | L3 Application | Not read yet | – | – |
| Physical safety interlocks | L3 Application | Not read yet | – | – |
Risk grouping: Not yet classified
No source we hold states: who caused it, intended or not, before or after release, the ai's part.
What the sources state
- When it happened 2026-10-30
No source states: a step-by-step account, 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, what was done.
Others like this
Tesla Cybercab strikes water-filled pothole on first reported crash 2026-10-15
NHTSA petition case DP26010 over Tesla robotaxi speeding in school zones 2026-10-13
Show every field, with its source and grade
The AI system
What happened
Impact
Context
Notes on gaps
Tags are inferred from the described collision and robotaxi context. Extractor proposed values without quotes; dropped: .
LR-2026-0294 · version 1 · published 2026-10-31 after automatic checks; not yet checked field by field by a person · JSON