Incident · Recall
Autopilot Controls Insufficient to Prevent Misuse
Tesla, Inc. (Tesla) is recalling 2012-2023 Model S, 2016-2023 Model X, 2017-2023 Model 3, and 2020-2023 Model Y vehicles equipped with all versions of Autosteer leading up to the version(s) that contains the recall remedy. In certain circumstances when Autosteer is engaged, the prominence and scope of the feature's controls may not be sufficient to prevent driver misuse of the SAE Level 2 advanced driver-assistance feature.
[NHTSA campaign 23V838000] source: nhtsa.gov
Occurred 2023-12-12 · Tesla · Investigated by NHTSA
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-tesla-recall-23v838000.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/94195c5c-382f-46ae-8ed1-7f691632b917
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
What happened in Autopilot Controls Insufficient to Prevent Misuse?
When did this incident occur?
Who was involved in Autopilot Controls Insufficient to Prevent Misuse?
Has anyone responded to Autopilot Controls Insufficient to Prevent Misuse?
What is the current status of Autopilot Controls Insufficient to Prevent Misuse?
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-06-25
Verification posture
Verified
High confidence
Review state
Stable
Last reviewed 2026-06-25
Sources by quality tier
- 1
- primary-regulatory-filing
- Regulatory filing
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Autopilot Controls Insufficient to Prevent Misuse.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 94195c5c-382f-46ae-8ed1-7f691632b917