The US NHTSA says it has opened a probe into ~2.6M Tesla vehicles over reports of four reported crashes involving its “Actually Smart Summon” driverless feature
The U.S. National Highway Traffic Safety Administration said on Tuesday it had opened a probe into about 2.6 million Tesla …
Context & Ripple Effects
This is part of an expanding NHTSA record examining Tesla’s automated-driving features, following a 2.4 million-vehicle Full Self-Driving probe over low-visibility crashes and earlier Autopilot scrutiny involving emergency vehicles.
The Smart Summon case focuses on a distinct, low-speed feature, but it arrives as Tesla’s self-driving ambitions depend on confidence in software behavior across vehicle functions. NHTSA later closed this particular investigation after finding only low-speed incidents, while subsequent scrutiny shifted to FSD traffic-safety reports.
First-order effects
- NHTSA’s investigation puts Tesla’s Smart Summon feature and its deployment across roughly 2.6 million vehicles under formal safety review after the reported crashes.
- Tesla must provide information and face the prospect of regulator-directed changes if NHTSA identifies a safety-related defect; vehicle owners gain a regulatory channel for the feature’s incident record.
Second-order effects
- The probe adds compliance and validation pressure to Tesla’s broader driver-assistance stack, particularly as the agency later opened a separate FSD investigation tied to alleged traffic violations and crashes.
- Other automated-feature developers have an incentive to document low-speed edge cases more rigorously, since even parking-lot-style functions can draw fleet-scale scrutiny.
Third-order effects
- If such feature-specific investigations continue, automated-driving oversight is likely to assess safety claims by operational domain rather than treating “self-driving” capability as a single category.
- The eventual low-speed finding suggests outcomes will depend on incident severity and evidence, but repeated probes can still make regulatory review a continuing product-development constraint.
The trend: Automated-vehicle regulation is becoming more granular, with agencies testing individual software features against their real-world operating conditions rather than accepting broad autonomy labels.