Did NHTSA find Tesla at fault?
No. An SGO crash report means a crash met a reporting rule. It is not a finding that Tesla or its software caused the crash.
Home · Crash reports
A crash report to NHTSA means a crash met a federal reporting rule. It is not a finding of who was at fault. The ADS file we downloaded on Nov 2, 2026 has 57 Tesla rows. One of them is a Cybercab: a low-speed contact with a water-filled pothole in an Austin parking lot, with a safety monitor aboard. Tesla's safety page claims about 3.1 million miles with no safety monitor from Jan 22 to Oct 18, 2026, and zero injuries as Tesla defines them. Utah has no robotaxi service.
D.R. Autonomy is an independent Utah company and is not affiliated with or endorsed by Tesla. This page is educational, not legal advice.
NHTSA's Standing General Order (SGO) 2021-01 requires companies to report certain crashes involving automated driving systems. Filing a report does not mean NHTSA found a defect. It does not mean the automated system caused the crash. Many reports involve only minor property damage.
Tesla's safety page, read Nov 2, 2026 through a page reader, says the SGO covers crashes on public roads when the automated system was engaged at any time in the 30 seconds before the crash. Tesla also says NHTSA publishes each report about a month or more after it is filed, so the public file runs behind. A direct request to tesla.com that day returned 403.
We downloaded NHTSA's SGO file for automated driving systems on Nov 2, 2026, from the static CSV linked below. The file's Last-Modified header was Oct 15, 2026. It has 1,595 data rows. Dates in the file are month labels, such as AUG-2026, not full calendar dates. The latest submission month in the file is September 2026. For rows where the reporting entity or the make contains Tesla (all 57 are Tesla, Inc. and make TESLA):
Report 13781-16672 is the only Cybercab row in the file. Model is Cybercab. City is Austin. Incident month is August 2026. Submission month is September 2026. Pre-crash speed is 5 mph. The driver/operator field is "In-Vehicle (Commercial / Test)." The injury field is "Property Damage. No Injured Reported." NHTSA's narrative says: "The ADS was proceeding straight in a parking lot going as fast as 5MPH and drove into a large pothole filled with water. The ADS had a safety monitor present in the vehicle with no passengers."
Tesla published a Robotaxi safety report. We read tesla.com/robotaxi/safety on Nov 2, 2026 through a page reader after a direct request returned 403. These are Tesla's numbers and Tesla's definitions. They are not an NHTSA fault finding.
Closed window: Jan 22 to Oct 18, 2026. The page shows "3.1 M" miles driven autonomously as of October 18, 2026. It also lists city miles: Austin 2,118,015; Dallas 608,130; Houston 225,964; Orlando 61,053; Tampa 53,117; Miami 46,262. Those six figures add to 3,112,541. TeslAnt reports the same 3,112,541 total for that window. One page-reader view of tesla.com/robotaxi the same day also showed 3,112,541 under "Miles Driven Autonomously."
Tesla says the report includes every crash it reports to NHTSA while Robotaxi is driving with no safety monitor in the car, including when a remote operator is assisting or has taken control. Tesla says it leaves out crashes and miles with a safety monitor aboard.
Tesla's page describes two events it did not count as injuries. In one, another vehicle hit an SUV and pushed it into a Robotaxi waiting at a stop sign; an occupant of the other vehicle went to the hospital. In the other, a rider claimed an injury after a Robotaxi drove over a pothole, and Tesla says its investigation found no injury.
Live counter. Tesla says the page has a live mileage counter that estimates miles at the fleet's current pace, separate from the closed Oct 18 window. Page-reader fetches on Nov 2, 2026 did not agree on one live figure. One safety-page read showed 4,276,590. One robotaxi-page read showed 3,112,541 in a similar headline, and a later robotaxi-page read showed a different figure near 4.28 million. Because those reads do not agree, this page does not treat any live total as a fact. The closed window remains the Oct 18 figure above.
Tesla's safety page links a spreadsheet, Robotaxi-SGO-Report_10_18_2026.xlsx. We downloaded that file on Nov 2, 2026. It has 32 data rows. The incident dates run from May 23, 2026 through Oct 18, 2026. Counted from that file:
TeslAnt reported those same 32 / 30 / 13 / 15 / 3 totals from Tesla's list. None of these rows is a fault finding. Tesla's list is not the same set as the 36 report IDs in the NHTSA file we downloaded. Tesla's page says its list leaves out crashes with a safety monitor aboard. The Cybercab row above is in the NHTSA file and is not in this 32-row spreadsheet.
No. An SGO crash report means a crash met a reporting rule. It is not a finding that Tesla or its software caused the crash.
Report 13781-16672. NHTSA's narrative says the ADS was proceeding straight in an Austin parking lot, going as fast as 5 mph, and drove into a large pothole filled with water. A safety monitor was in the vehicle and there were no passengers. The incident month is August 2026. The injury field is property damage with no injury reported.
Tesla says the report counts crashes it reported to NHTSA while no safety monitor was in the car, including when a remote operator was assisting or had taken control. Tesla says it leaves out crashes with a safety monitor aboard. Tesla says its injury and pedestrian counts include only collisions in which the Robotaxi made first contact.
Tesla says a live counter estimates miles at the current pace, separate from the closed window ending Oct 18, 2026. Page-reader fetches on Nov 2, 2026 did not agree on one live figure, so this page does not publish one.
There is no robotaxi service in Utah as of Nov 2, 2026. The Tesla rows in the NHTSA file we downloaded that day are from Texas and Florida.