Tesla NHTSA filing says Autopilot on

Tesla’s own crash filing to U.S. safety regulators said Autopilot was active during a fatal crash in Clute, Texas, according to reports published on September 2. The filing, submitted under the National Highway Traffic Safety Administration’s standing crash-reporting order, described the system as “verified engaged” before the collision, adding a detail that had not been disclosed publicly by local police. The case has drawn attention because Clute police had previously described the crash as a medical episode. The report also adds to scrutiny of Tesla’s driver-assistance systems after other recent fatal crashes tied in filings to vehicles stopped in live freeway lanes. ### Which Texas crash is this about? Clute, Texas, is the location of the crash identified in the reporting. Electrek said the victim was 23-year-old Steven Alvarez and that the Tesla’s filing to NHTSA linked Autopilot use to the fatal wreck. The same report said the Tesla was traveling at 104 mph before the crash. Startup Fortune, citing Electrek’s findings, said the NHTSA filing showed Tesla’s driver-assistance system was active even though police had not publicly reported that detail. ### What did police say before this filing surfaced? Clute police had publicly characterized the crash as a medical episode, according to Electrek’s account cited by other outlets. (electrek.co) The newly highlighted federal filing did not erase that possibility, but it added a separate fact: Tesla reported Autopilot as engaged before the crash. That distinction matters because the public account from local authorities and the manufacturer’s federal crash report were not the same. (electrek.co) The newer reporting focused on the gap between what police had said and what Tesla told NHTSA. ### Why would Tesla have filed anything with NHTSA? NHTSA requires manufacturers and operators covered by its standing general order to report certain crashes involving automated driving systems and Level 2 advanced driver-assistance systems. (electrek.co) For Level 2 ADAS, the agency says a report is required if the system was in use within 30 seconds of a crash and the crash involved a fatality, an air bag deployment, or hospital transport. (startupfortune.com) NHTSA says the order is meant to give the agency timely notice of real-world crashes involving those technologies so it can investigate safety concerns and take enforcement action if needed. Tesla’s filing in the Clute case appears to have been made under that framework. ### Is this the only recent Tesla crash drawing attention? September 2 coverage linked the Clute case to at least one other fatal crash in which Tesla’s reporting indicated driver-assistance use before impact. (nhtsa.gov) TechRadar’s September archive listing shows an article about Autopilot and Full Self-Driving facing scrutiny after two fatal crashes where cars came to a complete stop. Electrek separately reported on another fatal case in Mesa, Arizona, in which a Tesla was stopped in a freeway lane with driver assistance “verified engaged” before being rear-ended. (nhtsa.gov) Those reports have fed broader questions about what Tesla discloses publicly and what can be inferred from the company’s redacted NHTSA submissions. ### What is known next? NHTSA’s standing order remains the main public mechanism through which these crash reports surface, and the agency says it can use the data for further investigation and enforcement. (techradar.com) The Clute filing is now part of that record, even if many details in Tesla submissions remain redacted in public-facing reporting. September 2 was the date multiple outlets published the Clute filing details, and any next step would likely come through additional NHTSA action, a local investigative update, or further reporting tied to Tesla’s crash submissions. (electrek.co) (startupfortune.com) (nhtsa.gov)