THE ROBOTAXI RACE

Involved in fatal crashes: 0

No deaths in any Robotaxi-service crash since the June 2025 launch

Consumer Autopilot / FSD cars are a separate program and are not counted here

Jul 2025 – Mar 2026 · 2 minor-injury crashes, 1 requiring hospitalization

36 unique Robotaxi incident reports on file with NHTSA's Standing General Order as of its September data release (up from 23 a month earlier), incl. two August crashes while remote operators were driving — five crash reports now involve a remote operator at the controls. A newly reported August filing shows a Cybercab with a safety monitor aboard drove into a water-filled pothole in an Austin parking lot at ~5 mph (no injuries, no passengers); the Austin American-Statesman counts 26 Austin Robotaxi crashes since the June 2025 launch. The 2 SGO injury crashes date from the earlier, monitor-era period; Tesla's new safety report, which covers only driverless miles, claims zero injuries. Most crashes were other drivers' fault. No matched per-mile rate can be computed.

Not calculable yet — Tesla's new Robotaxi Safety Report (Oct 21) self-reports ~3.1M driverless miles (Jan 22–Oct 18, safety-monitor miles excluded) with zero injuries or airbag deployments, but it publishes no count of non-injury collisions and NHTSA's crash file uses different cutoffs and includes monitor-era crashes, so no matched crashes-per-million-miles rate can be computed

Tesla's own benchmark says human drivers would have had ~9.1 injury collisions over the same miles; its methodology is not published and the data is not independently verified. Historical context only: an early-Austin estimate (Feb 2026) put the rate around 9–18 per million miles — 14 crashes ÷ ~0.8M estimated miles, most driven with safety monitors aboard — roughly 4× a human benchmark. That estimate covers a different window, fleet, and driving mode than Waymo's figures and is not comparable to them. Robotaxis must also report every minor contact while humans only generate police reports.

SF Bay Area not counted — rides there still require a human safety driver · Oct 29: operating hours extended to 6 a.m.–2 a.m. (Tesla did not say which markets); Tesla says 24/7 before year-end · Oct 26: Houston service area expanded ~10× to ~254 sq mi (Robotaxi Tracker estimate), served by ~34 Model Ys and no Cybercabs yet · Oct 27: after Gov. DeSantis asked for beach coverage in Miami and Tampa, Musk indicated it is coming (no date) · Oct 21: Tesla named Las Vegas, Jacksonville, Phoenix and San Antonio as “coming soon” (no dates) and said Cybercab service launches in Dallas in November · Unsupervised FSD for customer cars pushed to ~Q2 2027 · Tesla's answers to NHTSA's Cybercab certification audit were due Oct 30; no filing had been made public as of Nov 2 · NHTSA defect-petition file DP26010 (opened Oct 9) on alleged school-zone speeding covers ~1,000 vehicles; no crashes reported · Las Vegas NTA permit for up to 5,000 vehicles granted Aug 20; no service start yet

Community tracking (Robotaxi Tracker, via Electrek, Oct 26) counts 397 driverless vehicles in Austin — more than half Cybercabs — plus 34 unsupervised Model Ys in Houston; smaller counts in Dallas and Florida are older (Oct 11) · Tesla's own claim: “300+ Cybercabs serving Austin” (Oct 10) · Texas registrations rose to 1,244 on our Nov 2 pull (573 Cybercab + 671 Model Y), up from 970 a week earlier and above 1,000 for the first time on Oct 27 — registered ≠ deployed (TxDMV registrations via robotaxireport.com daily sync) · NHTSA estimates ~1,000 Model Y + Cybercab Robotaxis in its school-zone petition file · Tesla still discloses no total fleet number