BACK OVER PREVENTION:SOFTWARE; ELECTRICAL SYSTEM
2024 Tesla Model 3
Recalls, owner-reported complaints, investigations and safety data
Data refreshed
Overview
Our database contains 207 NHTSA owner-reported complaints for the 2024 Tesla Model 3, most frequently naming the driver assistance, electrical and steering categories. 4 safety recalls have been issued covering this model year; 7 NHTSA investigations name it; and 58 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 2024 | 1 | 1 |
| Apr 2024 | 3 | 4 |
| May 2024 | 3 | 7 |
| Jun 2024 | 11 | 18 |
| Jul 2024 | 14 | 32 |
| Aug 2024 | 17 | 49 |
| Sep 2024 | 7 | 56 |
| Oct 2024 | 15 | 71 |
| Nov 2024 | 11 | 82 |
| Dec 2024 | 14 | 96 |
| Jan 2025 | 16 | 112 |
| Feb 2025 | 8 | 120 |
| Mar 2025 | 7 | 127 |
| Apr 2025 | 4 | 131 |
| May 2025 | 2 | 133 |
| Jun 2025 | 4 | 137 |
| Jul 2025 | 3 | 140 |
| Aug 2025 | 6 | 146 |
| Sep 2025 | 3 | 149 |
| Oct 2025 | 14 | 163 |
| Nov 2025 | 10 | 173 |
| Dec 2025 | 6 | 179 |
| Jan 2026 | 4 | 183 |
| Feb 2026 | 2 | 185 |
| Mar 2026 | 1 | 186 |
| Apr 2026 | 4 | 190 |
| May 2026 | 3 | 193 |
| Jun 2026 | 5 | 198 |
| Jul 2026 | 6 | 204 |
| Aug 2026 | 3 | 207 |
What owners report
Complaints grouped by the component NHTSA recorded
- Driver assistance6329.2%
- Electrical4219.4%
- Steering3616.7%
- Exterior lighting2612.0%
- Airbags83.7%
- Suspension62.8%
- Other / unspecified62.8%
- Visibility52.3%
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
4 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.govTIRES:PRESSURE MONITORING AND REGULATING SYSTEMS
ELECTRICAL SYSTEM:SOFTWARE; LATCHES/LOCKS/LINKAGES:HOOD:LATCH
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
When disengaging Full Self Driving (FSD), a feedback notification pops up on the bottom left corner of the infotainment screen that fully blocks the media control panel and does not disappear until the driver provides feedback to Tesla for why FSD was disengaged. By forcing the driver to answer the feedback question in order to access the media controls, Tesla causes a distraction to the driver, who is forced to take their eyes off the road and select a feedback response to why they chose to disengage FSD, increasing the chance of an accident. This is an intentional but dangerous design decision.
- NHTSA ID
- 11756598
- Incident
- Aug 5, 2026
On July 18, 2026, at approximately 10:00 AM EST, my son was manually driving a 2024 Tesla Model 3 at approximately 26 MPH when the steering suddenly became extremely stiff and difficult to turn. He attempted to steer away from a roadside barrier but was unable to turn the steering wheel sufficiently, resulting in a collision. There was no warning or indication observed on the dashboard before the steering suddenly became extremely stiff. Autopilot, cruise control, and Full Self-Driving were not activated; the vehicle was being driven manually. Fortunately, my son did not sustain any physical injuries. However, a sudden loss of normal steering control is a serious safety concern and could potentially cause severe injuries to the driver, passengers, pedestrians, or occupants of other vehicles. After the accident, the vehicle was towed to the insurance-designated facility and is currently being examined by the insurance adjuster. Within a few minutes of the accident, the vehicle also became completely locked, preventing us from retrieving personal belongings. I previously reported this incident to NHTSA under complaint number 11751698, but all required documentation was not available at that time. I am therefore submitting the complaint again with the additional information and documentation now available. I respectfully request that NHTSA investigate this incident and determine the root cause of the sudden steering stiffness and whether there is a safety-related defect or condition that could affect other vehicles.
- NHTSA ID
- 11755390
- Incident
- Jul 18, 2026
Creaking noise coming from front of car when going over speed bumps or driving through a dip at low speeds. Tesla SC says normal but many others have replaced lateral and compliance links and issues has been solved. Known issue and raises a safety concern over safety of suspension.
- NHTSA ID
- 11754875
- Incident
- Aug 5, 2026
When cruise control is engaged on a Tesla (all models to my knowledge) the Auto Wipers automatically come on and then randomly wipe. There is no option to disabled the Auto Wipers, as you can only disable by manually selecting control panel and then turn off each time you engage cruise control. This creates a significant risk to driver safety as I have had numerous instances of wipers randomly starting (without any rain) and smearing the windshield. This forces me to look away from the road and go through a manual disable every time I use cruise control. NOTE: this is a software default that cannot be removed
- NHTSA ID
- 11753679
- Incident
- Jul 29, 2026
The tesla service center in Ridgepoint drive in Austin TX has repeated safety issues and almost cost my wife her life in the tire inspection and undercarriage check after a full service including full tire failures after 4 tire checks and in building service center.
- NHTSA ID
- 11753676
- Incident
- Jul 30, 2026
COMPLAINT SUMMARY: CRITICAL SAFETY REGRESSIONS IN TESLA FSD SOFTWAREI am filing a formal safety complaint regarding severe, high-risk behavior regressions introduced across the last three consecutive builds of Tesla’s Full Self-Driving (Supervised) software. These defects create immediate collision hazards, cause major route disruptions, and require frequent, urgent driver intervention to prevent accidents.1. INTERSECTION AND TRAFFIC CONTROL VIOLATIONSRed Light Violations: The vehicle correctly identifies a red traffic light and comes to a full stop. However, after a brief pause, the software erroneously treats the steady red light like a stop sign and attempts to accelerate directly into active cross-traffic.Green Arrow Dead-Stops: When approaching a dedicated turn lane with an active, protected green turn arrow, the vehicle frequently applies aggressive braking and comes to a complete stop, creating an immediate rear-end collision hazard for drivers behind me.Phantom Braking: The vehicle aggressively brakes without warning for empty crosswalks, shadows, or distant roadside elements.2. ILLEGAL LANE NAVIGATION AND ROUTING ERRORSErroneous Turn Lane Diving: The vehicle frequently dives into dedicated left or right turn lanes even when the navigation route explicitly commands the vehicle to continue straight. This behavior forces improper turns, requiring backtracking and causing significant destination delays.Incorrect Lane Turning: The system regularly misses dedicated turn lanes entirely. It then attempts to execute sharp left or right turns directly from middle lanes or straight-only lanes, cutting off adjacent vehicles.Turn Signal Failures: The software initiates a turn signal to merge but then cancels the action, or conversely, attempts to execute a physical turn blindly after disabling the turn signal.3. RESTRICTED SPACE TARGETINGHandicap Parking Violations: Upon arriving at destinations, the automated parking software fails to recognize painted stencils and act
- NHTSA ID
- 11752414
- Incident
- Jul 23, 2026
I am writing to report an accident involving my son who was driving Tesla 2024 Model-3 on July 18th 2026 approximately 10:15 AM EST. He was returning home from his volunteering with Emergency medical Service(EMS) when the vehicle's steering wheel suddenly froze. while attempting to maneuver the vehicle to safe location , it collided with a roadside barrier. fortunately , my son was not injured , but the vehicle sustained significant damage, including deployment of airbag and damage to front passenger side. this incident occurred at a speed of approximately 26 MPH
- NHTSA ID
- 11751698
- Incident
- Jul 18, 2026
2024 Model 3, under 20k miles; burning smell and brake drag from right rear wheel while driving; parking brake fault alerts UI_a019, EPBR_a176, EPBR_a182; dealer inspection found cracked EPB caliper case housing near the electrical connector; Tesla SB-20-33-002 documents this same crack occurring without external impact.
- NHTSA ID
- 11750946
- Incident
- Jul 15, 2026
Manufacturer communications
A bulletin sent by a manufacturer to its dealers. Not a recall, and repairs are not necessarily free.
SEATS
On some vehicles, degraded or excessive glue under the front seat cushion(s) may cause creaking noises during cornering or when pressing on the seat cushion(s). Upon customer complaint, inspect the vehicle for symptoms related to the condition. If symptoms are present, rework the front seat cushion(s).
SEATS
On some vehicles, insufficient lubricant at the front seat recliner tube ends may cause creaking noises during weight shifting when the seat is occupied. Upon customer complaint, inspect the vehicle for symptoms related to the condition. If symptoms are present, lubricate the front seat recliner tube ends.
SUSPENSION
A firmware diagnosis feature is being introduced on Model 3 and Model Y vehicles that monitors wheel alignment over time. This feature detects changes in wheel alignment that may be related to incorrect tire pressures, degraded ball joints, bushings or damaged suspension links. If the feature determines that an inspection at a Tesla Service Center is required, a customer-facing alert will appear on the touchscreen.
ELECTRICAL SYSTEM
Certain Model 3 and Model Y vehicles were manufactured with High Voltage (HV) batteries containing cell modules that do not meet Tesla’s internal quality standards, potentially resulting in a reduction of range.
SERVICE BRAKES
On some Model 3 vehicles, the RH front Wheel Speed Sensor (WSS) might have been misrouted, which may cause damage to the WSS harness.
SERVICE BRAKES
On some Model 3 vehicles, the RH front Wheel Speed Sensor (WSS) might have been misrouted, which may cause damage to the WSS harness.
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.