2020 Tesla Model S

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.

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.

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

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.

The vehicle has been taken to Tesla multiple times due to ongoing controllability and safety concerns. The Autopilot system will occasionally brake unexpectedly at green lights or when another vehicle is passing on the right side. The vehicle has also experienced repeated drivetrain issues, including the half shafts failing at least four times within a short period. During acceleration, the vehicle can be difficult to control at times, and the wheels exhibit noticeable vibration. Despite replacing two full sets of tires within two years and completing multiple balancing and service attempts, the issue has not been resolved. These ongoing problems have contributed to premature tire wear and reduced stability, particularly in wet or rainy driving conditions. The vehicle has been serviced by Tesla at least 10 times, and each visit has resulted in replacement of half shafts or other drivetrain components. At one point, Tesla indicated that the drive module was “off center,” though no clear explanation was provided. These issues have been present since the vehicle was purchased in May 2024. In several instances, the vehicle was returned after service without the problem being resolved, requiring additional return visits. More recently, Tesla has suggested the issue may be related to tires and wheels. However, this contradicts earlier assurances that those components were not the root cause. All tires and two wheels have already been replaced, yet the same issues continue to occur. Months go by without any resolution and then when the tires go bad again, they tried to sell me on that when that never resolved the issue. They tried to force me to buy new tires and wheels for $8000 claiming that to be the issue. The main has fell twice in the last year and was replaced with a battery that was not of light kind. When the battery failed at a Tesla supercharger, the door would not open momentarily. I will estimate the date of the last service. Cannot open due to open ticket

NHTSA ID

11736972

Incident

Dec 1, 2025

The rear doors have emergency release cables in case the power is cut during a collision. These cables are hidden, not glowing, and have a small square pull on the end that is difficult to find and pull. I had great difficulty in testing the function to ensure the emergency cable pulls worked. They need to have a glowing T-handle on the end to facilitate location and movement, and the emergency cable location should be marked and visible in the car, just like the emergency hood and truck release are.

NHTSA ID

11703010

Incident

Dec 4, 2025

Rear emergency release cable does not open the trunk. The latch mechanism failed with a trunk full of groceries, I pushed down the rear setts to access the trunk compartment and crawled back and popped open the emergency release cable and it did not function. I have a service for the car scheduled for Dec 2nd to repair/replace the latch mechanism.

NHTSA ID

11702039

Incident

Nov 9, 2025

Wheels: From the original purchase of the vehicle, I had a small air leak from the right rear tire. I addressed this with Tesla and they said nothing was wrong. I lived with it adding pressure from time to time. When it was time to replace the tires because the originals were only good for 20,000 miles at most. Upon replacing the tires, it was discovered that the right rear rim was cracked which explained why it was leaking all this time. Not long after the tire replacement, I experienced another leak on the right front. I brought it back in to check for a leak in the tire and again discovered it was cracked also, but had 2 cracks in this one 😡. I discussed this with the tire shop and he stated he sees this very often with the Model S. He seems to believe the car is too heavy for the particular turbine wheels selected for the car. These wheels are a factory purchase upgrade. I called Tesla to address my concerns for feedback. They denied ever hearing of this issue as common. I did the research and lo and behold this defect is very common and people are very unhappy regarding this issue and the fact Tesla is blatantly being dishonest about it. For the foundation and a major component that binds a vehicle to the road should be taken seriously. In my opinion, a vehicle that has the potential for the wheels to crack and maybe just come apart is critical. And that depends on the actual speed of travel. This could be very bad.

NHTSA ID

11696968

Incident

Aug 13, 2021

On 09/18 , I was using the Smart Summon feature of my Tesla Model S in the parking lot of Costco, Greenwood (Indianapolis, IN). The intent was to have the vehicle autonomously navigate from its parked spot toward my location, as designed and advertised by Tesla. During the Summon operation: 1.The vehicle failed to correctly detect and avoid a fixed obstacle (the cart return stand where shopping carts are housed). 2.Instead of stopping or rerouting safely, the car collided with the structure, causing visible damage to the front of the vehicle. 3.While there was no damage to public property or injury to people, the incident demonstrated a serious safety risk, since pedestrians or nearby vehicles could have been struck had they been present. 4.The Smart Summon system did not provide sufficient warning or correction during this event, despite being marketed as capable of safely maneuvering in such environments. This failure shows that the Smart Summon feature did not perform as intended and behaved in an unsafe manner in a real-world public parking environment.

NHTSA ID

11689122

Incident

Sep 18, 2025

The contact owns a 2020 Tesla Model S. The contact stated that while the vehicle was parked, the driver’s side door failed to open from the inside as intended. The vehicle was restarted, but the failure persisted. The contact rolled down the driver’s side window and attempted to unlock the door from the outside; however, the failure persisted. The contact was trapped inside the vehicle. The contact climbed over to the passenger’s seat and exited the passenger’s side door without issue. The vehicle was taken to a dealer where it was determined that the door handle had an electrical issue, and an undisclosed part needed to be replaced. The vehicle was repaired. The manufacturer was notified of the failure. The failure mileage was unknown.

NHTSA ID

11687625

Incident

Jun 3, 2025

The contact owns a 2020 Tesla Model S. The contact stated while driving at various speeds, the vehicle started to vibrate in the shutter shaft unit. There were no warning lights illuminated. The vehicle was taken to the dealer and was diagnosed with front CV axle failure. The vehicle was repaired; however, the failure persisted. On a separate occasion, the vehicle started to shudder, and the vehicle was taken back to the dealer. The vehicle was repaired for the most recent failure however, the contact stated the vehicle had been repaired three times, for the CV axle failure. The manufacturer was made aware of the failure. The failure mileage was approximately 32,807.

NHTSA ID

11652390

Incident

Jun 22, 2022

Mileage

32,807 mi

Vehicle was tested for concern about self driving after test drive with tech told ok 3 days later Summoned car and immediately turned into adjacent vehicle all captured on video in 1-2 seconds. No issues with summons for over 4 years $2200 damage to adjacent vehicle but Tesla no damage left front wheel caused damage on start.

NHTSA ID

11641683

Incident

Feb 10, 2025

On certain Model S and Model X vehicles, the battery powered Pyrotechnic High Voltage (HV) Battery Disconnect will reach the end of its battery lifespan in the near future, which will trigger alerts and may limit the vehicle’s performance.

Tesla does not provide physical owner's manual copies. Instead, all available owner’s manual content is integrated into the vehicle software, and only the content relevant for a given vehicle, based on vehicle configuration and software version installed, is displayed on its touchscreen. This file contains all available owner’s manual content for the vehicle converted to PDF format, and given the distribution method and NHTSA’s submission format requirements, it is the best available representative copy of owner’s manual content. However, a customer who accesses the owner’s manual via their vehicle’s touchscreen would only see the parts of this PDF file that are relevant to their vehicle.

Tesla does not provide physical owner's manual copies. Instead, all available owner’s manual content is integrated into the vehicle software, and only the content relevant for a given vehicle, based on vehicle configuration and software version installed, is displayed on its touchscreen. This file contains all available owner’s manual content for the vehicle converted to PDF format, and given the distribution method and NHTSA’s submission format requirements, it is the best available representative copy of owner’s manual content. However, a customer who accesses the owner’s manual via their vehicle’s touchscreen would only see the parts of this PDF file that are relevant to their vehicle.

Tesla does not provide physical owner's manual copies. Instead, all available owner’s manual content is integrated into the vehicle software, and only the content relevant for a given vehicle, based on vehicle configuration and software version installed, is displayed on its touchscreen. This file contains all available owner’s manual content for the vehicle converted to PDF format, and given the distribution method and NHTSA’s submission format requirements, it is the best available representative copy of owner’s manual content. However, a customer who accesses the owner’s manual via their vehicle’s touchscreen would only see the parts of this PDF file that are relevant to their vehicle.

Tesla does not provide physical owner's manual copies. Instead, all available owner’s manual content is integrated into the vehicle software, and only the content relevant for a given vehicle, based on vehicle configuration and software version installed, is displayed on its touchscreen. This file contains all available owner’s manual content for the vehicle converted to PDF format, and given the distribution method and NHTSA’s submission format requirements, it is the best available representative copy of owner’s manual content. However, a customer who accesses the owner’s manual via their vehicle’s touchscreen would only see the parts of this PDF file that are relevant to their vehicle.

Tesla does not provide physical owner's manual copies. Instead, all available owner’s manual content is integrated into the vehicle software, and only the content relevant for a given vehicle, based on vehicle configuration and software version installed, is displayed on its touchscreen. This file contains all available owner’s manual content for the vehicle converted to PDF format, and given the distribution method and NHTSA’s submission format requirements, it is the best available representative copy of owner’s manual content. However, a customer who accesses the owner’s manual via their vehicle’s touchscreen would only see the parts of this PDF file that are relevant to their vehicle.