Texas Robotaxi demos reveal navigation failures and required remote interventions

- Tesla robotaxi demos and newly unredacted crash filings on May 23 showed navigation problems in Texas, including remote interventions and low-speed collisions in Austin. - Two Austin crashes happened while teleoperators remotely drove stopped Tesla vehicles, one into a metal fence and another into a construction barricade at 9 mph. (techcrunch.com) - NHTSA’s crash-reporting order and Tesla’s updated filings provide the next public record for Austin robotaxi incidents and any additional Texas disclosures. (nhtsa.gov)

Tesla’s robotaxi testing in Texas is drawing renewed scrutiny after a May 23 Motley Fool report and earlier published crash narratives described navigation failures, remote-operator takeovers and at least two low-speed crashes in Austin. The reports said some Tesla robotaxis struggled with basic routing and lane decisions, while one Dallas ride turned what should have been a roughly 20-minute trip into nearly an hour. (techcrunch.com) Newly unredacted filings with the National Highway Traffic Safety Administration added detail to those problems. Tesla had previously redacted the narrative sections of its automated driving system crash reports, but updated filings published this month now describe 17 Austin incidents from July 2025 through March 2026 involving 2026 Model Y vehicles with the automated system engaged and a safety monitor present. (nhtsa.gov) ### What do the Texas demos show about how the robotaxis were operating? The May 23 Motley Fool report said recent user demonstrations and reports from Texas showed Tesla robotaxis having trouble with basic navigation and needing remote-operator help. (fool.com) In Dallas, the report said at least one trip took a dramatically inefficient route that stretched a short ride to nearly an hour. Those accounts focused less on high-speed failures than on ordinary urban driving tasks. The issue described in the reports was that vehicles sometimes could not complete straightforward navigation without outside help, even inside the areas where Tesla was already operating or testing the service. (electrek.co) ### What happened in the two Austin crashes involving remote operators? TechCrunch reported on May 15 that Tesla robotaxis had crashed at least twice since July 2025 while a teleoperator was remotely driving the vehicles, citing newly unredacted information Tesla submitted to NHTSA. Both crashes happened in Austin, occurred at low speeds, had safety monitors behind the wheel and carried no passengers, the report said. (fool.com) In one July 2025 case, the filing said Tesla’s automated driving system had trouble moving forward while stopped on a street. After the safety monitor requested help, a teleoperator took control, increased speed and turned the vehicle left, where it went up a curb and hit a metal fence, according to the filing as described by TechCrunch. (fool.com) In a January 2026 case, the filing said a safety monitor requested support to assist with navigation after the vehicle stopped on a street. The teleoperator then proceeded straight and the Tesla made contact with a temporary construction barricade at about 9 mph, scraping the front-left fender and tire, according to the report. (techcrunch.com) ### Why are the unredacted crash records getting attention now? Electrek reported on May 15 that Tesla had unredacted all 17 of its autonomous driving system crash narratives filed with NHTSA, after previously marking every narrative as confidential business information. The outlet said Tesla had been the only automated driving system operator to fully redact those crash descriptions for much of the past year. (techcrunch.com) Business Punk, in a May 22 German-language report, said Tesla had blacked out robotaxi crash reports for 10 months before the records were opened. A separate report from Not a Tesla App said Tesla updated its historical filings to make full narratives public for Austin test-fleet incidents. (techcrunch.com) ### What do the federal filings require Tesla to disclose? NHTSA says companies covered by its Standing General Order on crash reporting must report an automated driving system crash if the system was in use within 30 seconds of the incident and the crash resulted in certain property damage or injury. (electrek.co) Those reports form the public record that outside researchers and reporters used to reconstruct Tesla’s Austin incidents. The latest batch of Tesla filings, as summarized by Electrek, covers Austin incidents from July 2025 through March 2026. Future updates to those filings, and any new Texas incidents that meet NHTSA’s reporting threshold, are the next public documents likely to show whether the navigation and intervention problems persist. (business-punk.com) (electrek.co) (nhtsa.gov)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.