ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043)

[COLLISION]

Jan 1, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA

Failure Mode

COLLISION

Event Date

Jan 1, 2026

Primary Entity

Tesla

Robotic Platform

Tesla Robotaxi (Model Y ADS)

Jurisdiction / Location

Orlando, Florida, USA

Audit Standard

Physical State Verified

System & Fleet Architecture

Operating Manufacturer

Hardware Platform

Tesla Robotaxi (Model Y ADS)

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

  • https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-13781-14043

    https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-13781-14043

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043)?

ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043) is recorded as a collision involving the Tesla Robotaxi (Model Y ADS) at Orlando, Florida, USA on the DEPLOY registry. See the rendered page for sourced details.

When did this incident occur?

The incident is recorded as occurring on January 1, 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 ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043)?

Tesla Robotaxi (Model Y ADS) by Tesla is the recorded robot involved in this incident at Orlando, Florida, USA.

Has anyone responded to ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043)?

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 ADS crash report in Austin, TX involving a TESLA Model Y (NHTSA SGO 13781-14043)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.