RCRecallRecall

NHTSA make / model monitor

Tesla Model Y: recalls, complaints and investigations.

Results are official records from named sources. Coverage is incomplete. This site is not medical advice and does not publish drug labels, openFDA, Prop 65 or NIH DSLD records.
42historical campaigns
13campaigns in monitoring window
2,657complaint rows in window
9monitored investigations

Evidence summary

Evidence found
13 recent recall campaigns, 2,657 complaint rows, and 9 monitored investigations.
Source coverage
NHTSA complaint and current-action window 2024-08-24 to 2026-08-24; historical campaign count uses the complete official pre- and post-2010 recall files acquired for this release.
What this means
The records were matched to the NHTSA make/model identity “Tesla Model Y”. Each evidence type is reported separately.
What this does not mean
Complaint reports are allegations, not defect findings or a safety score. Counts are not normalised for sales, registrations, mileage or exposure, and a zero does not prove safety.

Official recall campaigns

Campaigns received in the monitoring window

All NHTSA campaigns

24V886Received 2024-11-22SEATS:FRONT ASSEMBLY:RECLINER

Tesla, Inc. recall 24V886

The seat back frame may not properly restrain the occupant during a crash, increasing the risk of injury.

24V935Received 2024-12-17TIRES:PRESSURE MONITORING AND REGULATING SYSTEMS

Tesla, Inc. recall 24V935

Driving with improperly inflated tires increases the risk of a crash.

25V002Received 2025-01-06BACK OVER PREVENTION:SOFTWARE

Tesla, Inc. recall 25V002

A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.

25V092Received 2025-02-14STEERING:ELECTRIC POWER ASSIST SYSTEM

Tesla, Inc. recall 25V092

A loss of power steering assist can require greater steering effort, especially at low speeds, increasing the risk of a crash.

25V359Received 2025-05-29VISIBILITY:WINDSHIELD WIPER/WASHER:LINKAGES

Tesla, Inc. recall 25V359

The inability to clean the windshield reduces the driver’s visibility and increases the risk of a crash.

25V410Received 2025-06-18SEATS:CRITICAL FASTENERS

Tesla, Inc. recall 25V410

The seat may not properly restrain the occupant, increasing the risk of injury during a crash.

25V490Received 2025-07-28ELECTRICAL SYSTEM:HORN

Tesla, Inc. recall 25V490

An inoperable horn may prevent the driver from alerting other drivers as needed, increasing the risk of a crash.

25V658Received 2025-10-01ELECTRICAL SYSTEM:WIRING

Tesla, Inc. recall 25V658

Reverse lights that fail to illuminate reduce visibility and may not alert pedestrians or other drivers that the vehicle is backing up, increasing the risk of a crash.

25V690Received 2025-10-10ELECTRICAL SYSTEM:PROPULSION SYSTEM:FUSES, RELAYS, CONTACTS, AND SHUNTS

Tesla, Inc. recall 25V690

A loss of drive power can increase the risk of a crash.

26V283Received 2026-05-04BACK OVER PREVENTION:SOFTWARE

Tesla, Inc. recall 26V283

A delayed rearview image reduces the driver's view behind the vehicle, increasing the risk of a crash.

26V315Received 2026-05-18EQUIPMENT:OTHER:LABELS

Tesla, Inc. recall 26V315

Missing weight information provided by the label may lead to unintentionally overloading the vehicle, increasing the risk of a crash.

26V445Received 2026-07-07AIR BAGS:KNEE BOLSTER

Tesla, Inc. recall 26V445

A noncompliant vehicle may have reduced occupant protections, increasing the risk of injury during a crash.

26V507Received 2026-08-04EXTERIOR LIGHTING:HEADLIGHTS

Tesla, Inc. recall 26V507

Headlight low beams that are too bright can reduce visibility for oncoming drivers, increasing the risk of a crash.

Consumer reports — allegations

Complaint aggregates by model year

Model yearComplaintsCrash flagsFire flagsInjuries / deaths reportedMost common components
2026552139139 / 0UNKNOWN OR OTHER (97); FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL (50); FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING (47)
202518768433 / 3FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL (24); UNKNOWN OR OTHER (23); FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING (21)
2024500115794 / 0FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL (61); FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING (54); BACK OVER PREVENTION: SENSING SYSTEM: CAMERA (47)
2023678146669 / 1SUSPENSION (103); STEERING (85); UNKNOWN OR OTHER (62)
202229869648 / 7UNKNOWN OR OTHER (31); ELECTRICAL SYSTEM (29); SUSPENSION (25)
20213611945 / 1ELECTRICAL SYSTEM (43); SUSPENSION (41); UNKNOWN OR OTHER (36)
202081704 / 0UNKNOWN OR OTHER (9); ELECTRICAL SYSTEM (7); FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL (7)

NHTSA says complaints are consumer reports. RecallCheck excludes narratives, VINs, names, contact details and locations. A crash, fire, injury or death flag is reported information, not an independently verified causal finding.

NHTSA defect investigations

Open or recently opened investigations

AQ25002: Compliance with Standing General Order 2021-01 Reporting Requirements open

Opened 2025-08-20Closed not closedELECTRICAL SYSTEM:ADAS

The Office of Defects Investigation (“ODI”) has identified numerous incident reports submitted by Tesla, Inc. (“Tesla”) in response to Standing General Order 2021-01 (the “SGO”), in which the reported crashes occurred several months or more before the dates of the reports. The majority of these reports involved crashes in which the Standing General Order in place at the time required a report to be submitted within one or five days of Tesla receiving notice of the crash. When the reports were submitted, Tesla submitted them in one of two ways. Many of the reports were submitted as part of a single batch, while others were submitted on a rolling basis. Preliminary engagement between ODI and Tesla on the issue indicates that the timing of the reports was due to an issue with Tesla’s data collection, which, according to Tesla, has now been fixed. NHTSA is opening this Audit Query, a standard process for reviewing compliance with legal requirements, to evaluate the cause of the potential delays in reporting, the scope of any such delays, and the mitigations that Tesla has developed to address them. As part of this review, NHTSA will assess whether any reports of prior incidents remain outstanding and whether the reports that were submitted include all of the required and available data. The SGO reports cited in the Opening Resume, can be found at NHTSA.gov/SGOCrashReporting under the following SGO 2021-01 report IDs: 13781-11020-1 13781-10844-1 13781-10843-1 13781-10530-1 13781-10160-1 13781-10159-1 13781-10157-1 13781-10146-1 13781-10122-1 13781-10098-1 13781-10097-1 13781-10096-1 13781-10095-1 13781-10094-1 13781-10093-1 13781-10023-1 13781-10022-1 13781-10021-1 13781-10020-1 13781-10017-1 13781-10016-1 13781-10015-1 13781-10014-1 13781-10013-1 13781-10012-1 13781-6047-1 13781-9930-1 13781-9917-1 13781-9928-1 13781-9925-1 13781-9924-1 13781-9923-1 13781-9922-1 13781-9835-1 13781-9834-1 13781-9833-1 13781-9832-1 13781-9831-1 13781-9830-1 13781-9829-1 13781-9827-1 13781-9818-1 13781-9780-1 13781-9779-1 13781-9778-1 13781-9777-1 13781-9775-1 13781-9774-1 13781-9773-1 13781-9772-1 13781-9771-1 13781-9770-1 13781-9728-1 13781-9688-1 13781-9715-1 13781-9714-1 13781-9713-1 13781-9712-1 13781-9711-1 13781-9710-1 13781-9709-1 13781-9696-1 13781-9695-1 13781-9694-1 13781-9693-1 13781-9692-1 13781-9691-1 13781-9690-1 13781-9687-1 13781-9686-1 13781-9342-1 13781-9319-1 13781-9019-1 13781-8910-1 13781-8732-1 13781-8712-1 13781-8310-1 13781-7897-1 13781-7895-1 13781-7835-1 13781-7798-1 13781-7797-1 13781-7758-1 13781-7757-1 13781-7756-1 13781-7755-1 13781-7667-1 13781-7399-1 13781-7398-1 13781-7397-1 13781-7396-1 13781-7395-1 13781-7394-1 13781-7393-1 13781-7389-1 13781-7388-1 13781-7387-1 13781-7386-1 13781-7385-1 13781-7383-1 13781-7187-1 13781-7186-1 13781-7185-1 13781-7184-1 13781-7181-1 13781-7023-1 13781-6399-1 13781-6389-1 13781-6388-1 13781-6387-1 13781-6386-1 13781-6379-1 13781-6378-1 13781-6377-1 13781-6375-1 13781-6214-1 13781-6172-1 13781-6155-1 13781-6154-1 13781-6122-1 13781-6120-1 13781-6118-1 13781-5800-1

Official NHTSA investigations information

DP23002: Sudden Unintended Acceleration open

Opened 2023-06-29Closed not closedVEHICLE SPEED CONTROL

The Office of Defects Investigation (ODI) received a petition requesting that ODI reevaluate its decision to deny DP20-001 on the basis that intermittent high electrical current demands on the vehicles' 12VDC systems may have caused some or all of the incidents examined by ODI in DP20-001. The petitioner bases this information on a review of open-source research and the DP20-001 denial. The petition and related materials can be reviewed at NHTSA.gov under the following ODI number: 11528471.

Official NHTSA investigations information

EA26002: FSD Collisions in Reduced Roadway Visibility Conditions open

Opened 2026-03-18Closed not closedELECTRICAL SYSTEM:ADAS

The Office of Defects Investigation (ODI) is opening this Engineering Analysis to evaluate Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) degradation detection system. The focus of this investigation will be to assess the system’s ability, when encountering reduced roadway visibility conditions, to detect degradation and alert the driver with sufficient time to respond. ODI will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications by Tesla to the degradation detection system, including the timing, purpose, and capabilities of the updates, and Tesla’s assessment of their safety impact. Tesla’s FSD is an advanced driver assistance system (ADAS) that relies exclusively on vision-based cameras and the related FSD software to detect and respond to the roadway ahead, projecting a path forward based on traffic control devices, vehicles, pedestrians, and the roadway itself. When Tesla began transitioning away from using both cameras and radars to an exclusively camera-based approach, known as Tesla Vision, in mid-2021, it developed and implemented a degradation detection system that it deployed by a software update to existing and new Tesla vehicles. On June 28, 2024, the day after Tesla submitted the SGO report of the November 28, 2023 fatal crash listed in this document, Tesla began developing an update to the degradation detection system. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI discussed individual incidents and its initial findings during the PE phase of its investigation with Tesla. As part of those discussions, Tesla’s post-incident analysis indicated that the update to the degradation detection system, had it been installed on the vehicles at the time, may have affected 3 of the 9 incidents identified by ODI. Tesla also described internal data and labeling limitations that prevented a uniform identification and analysis of crash events with the subject system engaged. ODI believes this limitation could have led to under-reporting of subject crashes over portions of the defined time-period. Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. Review of Tesla’s responses revealed additional crashes that occurred in similar environments and where the system either did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path. In upgrading PE24031 to an Engineering Analysis (EA), ODI will gather further information on the updated degradation detection system, including the status of updating vehicles and scope of compatible vehicles, the system’s visibility degradation detection capability, and alerts or warnings to the driver. Lastly, ODI will conduct analysis on six recent potentially related incidents. These incidents can be found at NHTSA.gov under the following SGO report identification numbers: 13781-11937, 13781-13211, 13781-13569, 13781-13633, 13781-13693, 13781-13788. The crashes included in the failure report summary can be found at NHTSA.gov under the following SGO report identification numbers: 13781-8004, 13781-7181, 13781-7381, 13781-7767, 13781-7964, 13781-8977, 13781-9267.

Official NHTSA investigations information

PE24031: FSD Collisions in Reduced Roadway Visibility Conditions closed

Opened 2024-10-17Closed 2026-03-18ELECTRICAL SYSTEM:ADAS

On October 17, 2024, NHTSA’s Office of Defects Investigation (ODI) opened a Preliminary Evaluation (PE24031) of Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) to assess: the ability of the FSD system to detect and respond appropriately to reduced roadway visibility conditions; whether any other FSD crashes had occurred under degraded roadway visibility conditions that are similar in nature to the four SGO-reported crashes identified in the opening document, and if so, the contributing circumstances for each of those crashes; and any updates or modifications by Tesla to the FSD system that may affect the performance of FSD in degraded roadway visibility conditions, including the timing, purpose, and capabilities of any such updates, and Tesla’s assessment of their safety impact. Tesla’s FSD is an advanced driver assistance system (ADAS) that relies exclusively on vision-based cameras and the related FSD software to detect and respond to the roadway ahead, projecting a path forward based on traffic control devices, vehicles, pedestrians, and the roadway itself. During this phase of the investigation, ODI reviewed the materials provided by Tesla detailing any actions taken, or changes, modifications, and updates made that may relate to the alleged defect. ODI reviewed information related to Tesla’s transition to a vision-only perception system, and its deployment of the strategy in vehicles. ODI’s findings include information on limitations of the vision-only perception system and updates made in response to known subject crashes. When Tesla began transitioning away from using both cameras and radars to an exclusively camera-based approach, known as Tesla Vision, in mid-2021, it developed and implemented a degradation detection system that it deployed by a software update to existing and new Tesla vehicles. On June 28, 2024, the day after Tesla submitted the SGO report of the November 28, 2023 fatal crash listed in this document, Tesla began developing an update to the degradation detection system. ODI reviewed certain public statements, including those made during an April 2025 earnings call, in which Tesla stated that it had developed a breakthrough “direct photon-counting” capability that eliminates the degradation that the camera-based system experiences when glare is encountered. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI has discussed individual incidents and its initial findings with Tesla. Based on Tesla’s post-incident analysis, the update to the degradation detection system, had it been installed on the vehicles at the time, may have affected 3 of the 9 incidents identified by ODI. Review of Tesla’s responses revealed additional crashes that occurred in similar environments and where the system either did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path. Tesla also described internal data and labeling limitations that prevented a uniform identification and analysis of crash events with the subject system engaged. ODI believes this limitation could have led to under-reporting of subject crashes over portions of the defined time-period. Available incident data raise concerns that Tesla’s FSD system fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants where the camera-based system performance degrades significantly. In the crashes that ODI has reviewed, the FSD system did not detect common roadway conditions that impaired its visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. ODI is upgrading this investigation (PE24031) to Engineering Analysis (EA) 26002 to further evaluate this matter. The crashes included in the failure report summary can be found at NHTSA.gov under the following SGO report identification numbers: 13781-8004, 13781-7181, 13781-7381, 13781-7767, 13781-7964, 13781-8977, 13781-9267.

Official NHTSA investigations information

PE24033: Actually Smart Summon sessions resulting in low-speed impacts. closed

Opened 2025-01-06Closed 2026-04-03ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING

On January 6, 2025, the Office of Defects Investigations (ODI) opened Preliminary Evaluation 24003 (PE24033) to investigate Actually Smart Summon (Summon) sessions resulting in crashes during active sessions. According to Tesla, Summon is a short-distance SAE Level 2 system, controlled by the user from a cell phone within a certain distance and intended for use in parking lots and on private property. ODI analyzed complaint data provided by Tesla as well as complaints submitted to ODI from consumers to identify Summon incidents resulting in crashes. ODI's analysis indicates that almost all Summon reported crashes involved minor property damage claims with no reported incidents involving a vulnerable road user, injury, fatality, or major property damage as indicated by an air bag deployment or vehicle tow away. Out of millions of Summon sessions, a fraction of 1% resulted in an incident. Almost all those incidents took place where, typically early in a Summon session, the system or person using the app failed to fully detect or respond appropriately to vehicle surroundings resulting in minor impacts. Incidents took place when app users did not have a complete 360-degree view of the surroundings in the app to assess situational awareness. This limited the app user’s ability to determine whether an impact was imminent during initial vehicle maneuvers such as reversing in close proximity to an obstacle or a curb. ODI found that the impacts most often occurred with parking gates, adjacently parked vehicles, and short parking bollards. During this investigation, ODI identified two Summon crashes related to camera blockages. In both crashes, Summon attempted to navigate a snowy parking lot with snow partially or fully obstructing the forward-facing cameras. Summon did not detect the camera blockage and the vehicles collided with unoccupied parked vehicles while navigating the parking lot. App users in both instances did not command a vehicle stop or pause despite the obstructed camera visible in the camera stream in the app. On January 15, 2025, Tesla released Over-the-Air (OTA) Software (SW) Update Action numbers 578998 and 579185 for vehicles in service to implement a camera blockage detection condition. Both OTAs improve camera blockage detection mechanisms. Additionally, on January 20, 2025, and January 30, 2025, Tesla identified additional system requirements associated with camera visibility checks and released OTA SW-578752 and SW-580322, respectively. These firmware updates reduce false negative camera blockage detections due to snow or condensation. In its investigation, ODI identified one Summon incident where the vehicle did not yield for a gate arm blocking a garage exit lane and the app user did not command a vehicle stop or pause, resulting in an impact. On February 6, 2025, Tesla deployed OTA SW-578839 to improve vehicle reaction to dynamic gates. This OTA update upgraded vehicle perception systems through a high-fidelity occupancy determination network, which uses data from vehicle sensory systems to improve reconstruction of field objects with high accuracy. On November 20, 2025, Tesla further improved vehicle performance by adding object detections from a separate neural network through OTA SW-580514. Owners of the affected vehicles received all six OTA SW updates. Tesla also released these SW updates to production vehicles. See online public file for detailed descriptions of all six OTA SW updates. Due to low incident occurrence and low incident severity, this preliminary evaluation is closed. The closing of this investigation does not constitute a finding that a safety-related defect does not exist. The agency reserves the right to take additional action if warranted by future circumstances. For additional information regarding this investigation, see the complete online public file.

Official NHTSA investigations information

PE25010: Electronic door handles become inoperative open

Opened 2025-09-15Closed not closedELECTRICAL SYSTEM:12V/24V/48V BATTERY

The Office of Defects Investigation (ODI) has received nine Vehicle Owners Questionnaires (VOQs) reporting an inability to open doors on Model Year (MY) 2021 Tesla Model Y vehicles. The most commonly reported scenarios involved parents exiting the vehicle after a drive cycle in order to remove a child from the back seat or placing a child in the back seat before starting a drive cycle. In those events, the parents were unable to reopen a door to regain access to the vehicle. Four of these VOQs reported resorting to breaking a window to regain entry into the vehicle. Although Tesla vehicles have manual door releases inside of the cabin, in these situations, a child may not be able to access or operate the releases even if the vehicle’s driver is aware of them. As a result, in these instances, an occupant who remains inside a vehicle in this condition may be unable to be rapidly retrieved by persons outside of the vehicle. Entrapment in a vehicle is particularly concerning in emergency situations, such as when children are entrapped in a hot vehicle. For awareness, NHTSA has a Child Heatstroke Campaign that highlights the dangers to children entrapped in hot vehicles. Based on ODI’s preliminary review, this condition appears to occur when the electronic door locks receive insufficient voltage from the vehicle. Available repair invoices report replacement of the vehicle’s low voltage battery after the incident. However, no VOQs reported seeing a low voltage battery warning prior to the exterior door handles becoming inoperative. The Tesla Owner’s Manual “Jump Starting” and “Opening the Hood with No Power” sections describe a multi-step process for restoring power to the electronic door locks in order to enable their operation from outside of the vehicle. This process requires applying 12 volts DC from a separate power source to two different points accessible from the vehicle’s exterior.The subject incidents suggest that this process may not be readily available to owners or well known. For instances where an occupant is able to access and operate interior door handles, the Tesla Owner’s Manual “Opening Doors with No Power” section identifies the manual door releases inside of the vehicle’s cabin. ODI is opening this Preliminary Evaluation (PE) to assess the scope and severity of this condition, including the risks that arise from the conditions reported in the VOQs. This investigation will also assess the approach used by Tesla to supply power to the door locks and the reliability of the applicable power supplies. At this time, NHTSA’s investigation is focused on the operability of the electronic door locks from outside of the vehicle as that circumstance is the only one in which there is no manual way to open the door. The agency will continue to monitor any reports of entrapment involving opening doors from inside of the vehicle, and ODI will take further action as needed. To review the ODI reports cited in the Opening Resume and the ODI Report Identification Number document, go to NHTSA.gov.

Official NHTSA investigations information

PE25012: Traffic safety violations while Full Self Driving ("FSD") is engaged open

Opened 2025-10-07Closed not closedELECTRICAL SYSTEM:ADAS

The Office of Defects Investigation (“ODI”) is opening this Preliminary Evaluation (PE) to assess the scope, frequency, and potential safety consequences of FSD executing driving maneuvers that constitute traffic safety violations. This investigation concerns versions of FSD that Tesla has labeled as "FSD (Supervised)" and "FSD (Beta)." Tesla characterizes FSD as an SAE Level 2 partial automation system requiring a fully attentive driver who is engaged in the driving task at all times. Level 2 partial automation systems are designed to support and assist the driver in performing certain aspects of the driving task, requiring a driver to supervise and intervene as necessary. The driver remains fully responsible at all times for driving the vehicle, including complying with applicable traffic laws. ODI’s investigation will therefore focus, in particular, on whether certain driving inputs within the control authority of FSD forestall the driver’s supervision when they are unexpectedly performed. ODI has identified a number of incidents in which the inputs to the dynamic driving task commanded by FSD induced vehicle behavior that violated traffic safety laws. Although reports of this nature span a variety of behaviors, the reports appear to most commonly involve two types of scenarios. The first type of scenario involves a vehicle operating with FSD proceeding into an intersection in violation of a red traffic signal. The second type of scenario involves FSD commanding a lane change into an opposing lane of traffic. With respect to the first type of scenario, ODI has identified 18 complaints and 1 media report alleging that a Tesla vehicle, operating at an intersection with FSD engaged, failed to remain stopped for the duration of a red traffic signal, failed to stop fully, or failed to accurately detect and display the correct traffic signal state in the vehicle interface. Some complainants also alleged that FSD did not provide warnings of the system's intended behavior as the vehicle was approaching a red traffic signal. ODI has identified six Standing General Order ("SGO") reports in which a Tesla vehicle, operating with FSD engaged, approached an intersection with a red traffic signal, continued to travel into the intersection against the red light and was subsequently involved in a crash with other motor vehicles in the intersection. Of these incidents, four crashes resulted in one or more reported injuries. At least some of the incidents appeared to involve FSD proceeding into the intersection after coming to a complete stop. ODI's pre-investigative work, including coordination with the Maryland Transportation Authority and State Police, indicated that the problem may be repeatable, given that multiple subject incidents occurred at the same intersection in Joppa, Maryland. NHTSA understands that Tesla has since taken action to address the issue at this intersection. With respect to the second type of scenario, ODI has identified 2 SGO reports, 18 complaints, and 2 media reports alleging that a Tesla vehicle, operating with FSD engaged, entered opposing lanes of travel during or following a turn, crossed double-yellow lane markings while proceeding straight, or attempted to turn onto a road in the wrong direction despite the presence of wrong-way road signs. Likewise, ODI has identified 4 SGO reports, 6 complaints, and 1 media report alleging that a Tesla vehicle, operating with FSD engaged, proceeded straight through an intersection in a turn-only lane or executed a turn at an intersection in a through lane despite the presence of lane markings or signals. Complaints also alleged that FSD did not provide warnings of the system's intended behavior. Some complaints alleged that more than one of these failures occurred and, as such, the numbers are not cumulative. Some of the reported incidents appeared to involve FSD executing a lane change into an opposing lane of travel with little notice to a driver or opportunity to intervene. ODI’s review will assess whether there was prior warning or adequate time for the driver to respond to the unexpected behavior or to safely supervise the automated driving task. This review will assess any warnings to the driver about the system's impending behavior; the time given to drivers to respond; the capability of FSD to detect, display to the driver, and respond appropriately to traffic signals; and the capability of FSD to detect and respond to lane markings and wrong-way signage. NHTSA's review will also consider any updates or modifications to the system(s) that may affect the performance of FSD with respect to obeying traffic safety laws and signals. This assessment will focus, in particular, on the types of traffic safety violations described above, as most reports identified thus far have centered around those behaviors. While the behaviors under investigation appear to occur most frequently at intersections, NHTSA’s investigation will encompass any other types of situations in which this behavior may arise, such as when traveling adjacent to a lane of opposing traffic or when approaching railroad crossings. If other evidence received during this investigation involve other types of traffic safety violations, those may be considered as part of this assessment as well. To review the ODI reports cited in the Opening Resume ODI Report Identification Number document, go to NHTSA.gov. The SGO reports cited in this Resume are listed below by report ID and are available for download at NHTSA.gov/laws-regulations/standing-general-order-crash-reporting. 13781-8739-1, 13781-8995-1, 13781-9623-1, 13781-10333-1, 13781-10872-1, 13781-10930-1, 13781-10939-1, 13781-10941-1, 13781-11069-1, 13781-11305-1, 13781-11579-1 Media reported allegations included as a separate attachment.

Official NHTSA investigations information

PE26006: Lower Lateral Link detachment open

Opened 2026-07-29Closed not closedSUSPENSION:FRONT:CONTROL ARM:LOWER ARM

The Office of Defects Investigation (ODI) has received 156 complaints alleging a suspension failure in model year (MY) 2018-2020 Model 3 and MY 2021-2023 Model Y vehicles. The suspension failure involves the detachment of the front lower lateral link, which potentially causes a loss of vehicle directional control. In most cases, there was no advance warning or indication that the suspension failure would occur. Some cases cite noises occurring prior to failure, but note that the vehicle provides no visual warnings. Once the failure occurs, the vehicle may not be drivable, thus requiring a tow. Tesla has previously recalled vehicles for lateral link detachments through two recalls. Recall 21V-835 addressed 2,791 MY2019-2021 Tesla Model 3 vehicles due to a production issue. Recall 23V-235 addressed 422 2018-2019 Tesla Model 3 vehicles that had experienced similar failures to those recalled under 21V-835. The subject failures for this investigation exceed the scope of these recalls and do not appear to be related to the production issue that prompted those recalls. ODI is opening this Preliminary Evaluation to determine the underlying cause, scope, and severity of the potential problem and to fully assess the potential safety-related issues. To review the ODI reports cited in the Opening Resume ODI Report Identification Number document, go to NHTSA.gov.

Official NHTSA investigations information

RQ24009: Recall 23V838 Remedy Effectiveness open

Opened 2024-04-25Closed not closedELECTRICAL SYSTEM:ADAS:DRIVER MONITORING:SOFTWARE

The Office of Defects Investigation (ODI) is opening a Recall Query to assess the remedy adequacy of Recall 23V838. On December 12, 2023, Tesla filed a Defect Information Report (Recall 23V838) applicable to all Tesla models produced and equipped with any version of its Autopilot system, which Tesla described as an SAE Level 2 (L2) Advanced Driver Assistance System (ADAS). Autopilot is the simultaneous engagement of Tesla’s Traffic-Aware Cruise Control (TACC) and Autosteer. In describing the safety defect, Tesla’s Defect Information Report (DIR) explained that “the prominence and scope of the system’s controls may be insufficient to prevent driver misuse,” and Tesla committed to the deployment of a multipart remedy aimed at improving system and engagement controls and reducing mode confusion. EA22002 (upgraded from PE21020) was opened to investigate whether Tesla’s Autopilot contained a defect that created an unreasonable risk to motor vehicle safety and involved extensive crash analysis, human factors analysis, vehicle evaluations, and assessment of vehicle control authority and driver engagement technologies. The work conducted in these investigations aligns with Tesla’s conclusion in its 23V838 recall filing. During EA22002, ODI identified at least 13 crashes involving one or more fatalities and many more involving serious injuries in which foreseeable driver misuse of the system played an apparent role. Tesla filed Recall 23V838 to address concerns regarding the Autopilot system investigated in EA22002. Following deployment of the remedy in Recall 23V838, ODI identified concerns due to post-remedy crash events and results from preliminary NHTSA tests of remedied vehicles. Also, Tesla has stated that a portion of the remedy both requires the owner to opt in and allows a driver to readily reverse it. Tesla has also deployed non-remedy updates to address issues that appear related to ODI’s concerns under EA22002. This investigation will consider why these updates were not a part of the recall or otherwise determined to remedy a defect that poses an unreasonable safety risk. ODI is therefore opening this Recall Query investigation to further evaluate the adequacy of the remedy for recall 23V838.

Official NHTSA investigations information