SEAT BELTS:FRONT:WARNING LIGHT/DEVICES
2019 Tesla Model S
Recalls, owner-reported complaints, investigations and safety data
Data refreshed
Overview
Our database contains 43 NHTSA owner-reported complaints for the 2019 Tesla Model S, most frequently naming the driver assistance, suspension and brakes categories. 10 safety recalls have been issued covering this model year; 15 NHTSA investigations name it; and 66 manufacturer communications are on file.
Complaints are reports submitted by owners and drivers to NHTSA. They are not verified and do not establish that a defect exists.
Complaint activity over time
When owners filed reports about this model year
View as table
| Month | Complaints filed | Cumulative |
|---|---|---|
| Mar 2019 | 1 | 1 |
| Aug 2019 | 1 | 2 |
| Oct 2019 | 1 | 3 |
| Jan 2020 | 1 | 4 |
| Feb 2020 | 2 | 6 |
| Jul 2020 | 2 | 8 |
| Aug 2020 | 2 | 10 |
| Apr 2021 | 2 | 12 |
| Jul 2021 | 1 | 13 |
| Oct 2021 | 1 | 14 |
| Jan 2022 | 1 | 15 |
| Feb 2022 | 5 | 20 |
| Mar 2022 | 1 | 21 |
| Aug 2022 | 1 | 22 |
| Oct 2022 | 3 | 25 |
| Dec 2022 | 1 | 26 |
| Jan 2023 | 2 | 28 |
| May 2023 | 1 | 29 |
| Jul 2023 | 1 | 30 |
| Oct 2023 | 1 | 31 |
| Dec 2023 | 1 | 32 |
| Jan 2024 | 1 | 33 |
| Feb 2024 | 1 | 34 |
| Jun 2024 | 1 | 35 |
| Sep 2024 | 1 | 36 |
| Oct 2024 | 1 | 37 |
| Jan 2025 | 1 | 38 |
| Apr 2025 | 1 | 39 |
| Sep 2025 | 1 | 40 |
| Nov 2025 | 1 | 41 |
| Jan 2026 | 1 | 42 |
| Jul 2026 | 1 | 43 |
What owners report
Complaints grouped by the component NHTSA recorded
- Driver assistance1628.1%
- Suspension814.0%
- Brakes712.3%
- Electrical47.0%
- Steering47.0%
- Powertrain (other)35.3%
- Visibility35.3%
- Exterior lighting23.5%
Percentages are of component mentions. A single complaint can name more than one component, so these do not sum to the total complaint count.
Safety recalls
10 campaigns cover this model year
Recalls apply to specific vehicles, not to every vehicle of a model year. Check your VIN with NHTSA or your manufacturer's dealer to confirm whether a recall affects your vehicle.
Check a VIN on NHTSA.govELECTRICAL SYSTEM:SOFTWARE; FORWARD COLLISION AVOIDANCE: WARNINGS:EXTERNAL/PEDESTRIAN ALERT
ELECTRICAL SYSTEM: INSTRUMENT CLUSTER/PANEL
Safety investigations
NHTSA inquiries naming this vehicle. An investigation is not a finding of a defect.
FSD Collisions in Reduced Roadway Visibility Conditions
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.
Traffic safety violations while Full Self Driving ("FSD") is engaged
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.
Compliance with Standing General Order 2021-01 Reporting Requirements
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
Recall 23V838 Remedy Effectiveness
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.
Recent owner complaints
Reports submitted to NHTSA, shown in the owner's own words
Received error message on screen that a left front seat belt error occurred with an error code of rcm2_a564. Indications are that this error then disables the airbag deployment and the seat belt reaction to an accident. Since this is a safety issue, it should be subject to recall.
- NHTSA ID
- 11747590
- Incident
- Jun 22, 2026
Two of the rims cracked, right rear and left front, both on the interior edge.
- NHTSA ID
- 11710893
- Incident
- Jan 9, 2026
After a recent Tesla firmware update, the backup camera (FMVSS 111 rear visibility function) stopped working. When shifting into reverse, the display shows a black/blank screen instead of the required rearview image. However, the rear camera preview feed still functions, indicating the camera hardware is intact and the failure is likely in the MCU/deserializer routing or software handling of the reverse camera mode. Tesla Service refused to investigate the firmware or signal-routing path and instead recommended a full MCU replacement at my expense without providing diagnostic logs or evidence that the update was not the cause. They closed the case and declined further review while the federally required safety feature remains inoperative. This appears to be a software- or firmware-triggered failure of a federally mandated safety system following a Tesla-pushed update, and I request NHTSA review.
- NHTSA ID
- 11701794
- Incident
- Nov 10, 2025
Tesla’s software updates have rendered systems useless the vehicle wants to hug and sometimes cross the left double yellow lines. It cannot hold a constant speed and since their implementation of “supervised” full self driving, have made my vehicle unsafe
- NHTSA ID
- 11688285
- Incident
- Sep 17, 2025
My Tesla supervised FSD is a safety hazard. Promised programming updates have not improved the erratic, UNSAFE “assistance. I try it after each update, but I’m afraid to rely on it other than 5-10mph bumper to bumper road conditions. I don’t have one specific occurrence to report and thank goodness no fatality!
- NHTSA ID
- 11655710
- Incident
- Apr 1, 2025
Experienced rattling while driving. Brought car in and was told this is a known problem. Obtained copy of the bulletin from Tesla saying this was a “fix upon notification” rather than a recall. Then was forced to pay for the repairs. Upon investigation, this has been reported consistently since 2016. This seems fraudulent as it should cross the threshold of a recall. I would like Tesla to cover the costs of my repair as they would do under a recall.
- NHTSA ID
- 11638835
- Incident
- Jan 27, 2025
Rear trunk power lift gate would not open. There is an emergency release on rear lift gate if someone is stuck in the car. Emergency release doesn't work, pulled on it multiple times and it is jammed doesn't move. So in an emergency you are stuck. Appeared today for first time. I have called Tesla to fix this issue. There are three beeps when the system malfunctions but a lot of good that does you if emergency release to open the lift gate doesn't work. Seems to be a common problem reviewing complaints on the internet... not matter what it should release.
- NHTSA ID
- 11619468
- Incident
- Oct 12, 2024
Vehicle suddenly stopped on highway luckily there were no drivers behind me. The vehicle all of a sudden started beeping even though there was a clear path and no obstructions. Then stopped. I was panicked and in awe at what was happening. I couldn’t get the vehicle to drive I was just stuck for 10-15 seconds. I was finally able to get the car moving again but the problem hasn’t happened since. Any information as to what may have gone wrong may help other Tesla owners who may or may have not experienced this… yet
- NHTSA ID
- 11613861
- Incident
- Apr 19, 2024
Manufacturer communications
A bulletin sent by a manufacturer to its dealers. Not a recall, and repairs are not necessarily free.
ELECTRICAL SYSTEM
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.
Manufacturers file copies of the bulletins they send to dealers with NHTSA. These often describe diagnostic or repair procedures for a known condition. They are not recalls: repairs described in a bulletin are usually only free if the vehicle is still under warranty or the manufacturer has extended coverage.
Compare model years
Complaint and recall counts across every year of this model
Higher-selling and older vehicles accumulate more reports. Counts are not failure rates and are not directly comparable between vehicles that sold in very different numbers. Older model years have had longer for reports to accumulate.