Tesla unredacts robotaxi crash reports
- Tesla on May 15 unredacted 17 robotaxi crash narratives in a federal NHTSA database, disclosing two low-speed incidents that occurred during teleoperator intervention. - One filing said a teleoperator took control after a stop and drove into a construction barricade at about 9 mph, scraping the fender. - NHTSA’s crash-reporting rules for ADS systems remain posted on the agency’s website, which hosts the updated Tesla filings.
Tesla has published fuller descriptions of 17 robotaxi crashes in a federal database after previously withholding the narratives, giving the clearest public account yet of how its early driverless service incidents unfolded. The updated filings with the National Highway Traffic Safety Administration, or NHTSA, include two crashes in which remote human operators intervened while the vehicles were active. TechCrunch first reported the newly visible details on May 15, and Wired separately reported that remote operators slowly drove Tesla vehicles into a metal fence and a construction barricade. The disclosures matter because Tesla has described its robotaxi system as an automated driving system, or ADS, a category that triggers federal crash-reporting obligations when the system was in use within 30 seconds of a qualifying crash. NHTSA says ADS reporting thresholds are stricter than those for Level 2 driver-assistance systems because ADS is intended to perform the full driving task within its operating domain. (techcrunch.com) ### What exactly did Tesla newly reveal in the filings? Tesla’s revised reports now include narrative descriptions for all 17 robotaxi crashes filed with NHTSA since last year, according to TechCrunch and Electrek. Earlier versions had redacted the event descriptions as confidential business information, those reports said. The incidents span from July 2025 to March 2026, Wired reported. (nhtsa.gov) Several involved Tesla vehicles being struck by other road users, while others described contact with fixed objects or low-speed scrapes during maneuvering. ### Which two crashes involved teleoperators? One NHTSA filing described a Tesla vehicle that had stopped while the automated system was driving straight on a street. (techcrunch.com) TechCrunch reported that the safety monitor requested support, the teleoperator took over vehicle control, and the vehicle then continued straight into a temporary construction barricade at about 9 mph, scraping the front-left fender and tire. (wired.com) A second filing described a remote operator driving a Tesla robotaxi into a metal fence, Wired reported. Wired said the two teleoperation crashes were low-speed events in which human employees, not only the onboard system, played a direct role in the contact. ### Why does the teleoperator detail stand out? NHTSA’s reporting framework distinguishes ADS from lower-level driver assistance and requires companies to disclose qualifying crashes involving automated systems. (techcrunch.com) The Tesla filings show that, in at least two cases, a human remote-assistance layer was involved during the event sequence reported to regulators. (wired.com) NHTSA has separately been scrutinizing Tesla’s automated-driving technology in other contexts. The agency opened a preliminary evaluation in October 2025 into traffic-law violations involving FSD and in April 2026 opened an engineering analysis into FSD performance in reduced-visibility conditions, according to agency documents. ### Do the filings say Tesla caused most of the 17 crashes? (nhtsa.gov) Electrek reported that most of the newly described crashes did not appear to be Tesla’s fault. TechCrunch likewise said many incidents involved Tesla robotaxis being hit by other vehicles or encountering minor contact events, though the teleoperator cases added new detail about how Tesla handles edge cases. (static.nhtsa.gov) Wired reported that Tesla’s disclosures offered a rare look at the humans behind the system, including remote operators and safety monitors. Those details emerged as Tesla has been scaling its robotaxi network gradually rather than at the pace Chief Executive Elon Musk had once projected, according to TechCrunch. ### Where can readers see the filings and what comes next? (electrek.co) NHTSA hosts the Standing General Order crash-reporting system and says companies must file ADS crash reports when specified damage or injury thresholds are met. The agency’s public database remains the primary source for future Tesla robotaxi crash narratives as additional incidents, if any, are reported. (wired.com) May 15 is the date the unredacted narratives drew wider public attention through media reports, and NHTSA’s open investigations into Tesla’s automated-driving systems remain active in separate agency documents. Any further robotaxi crash filings would appear through the same federal reporting channel. (techcrunch.com) (nhtsa.gov)