2024 Tesla Model 3 Driver assistance Problems

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

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

While turning right, I slowed down and put on my turn lights. The vehicle accelerated all of a sudden and did a sharp right. There was a vehicle in front of me in the opposite direction and my car turned very sharply to avoid it. The accelerator pedal was fully pressed down and for that fraction of a second, it didn’t allow me to control the speed.

NHTSA ID

11746845

Incident

Jun 26, 2026

On June 7, 2026 an accident occurred on Overlook Parkway, Riverside southbound (near chabot ct intersection) involving my 2024 model 3 that was in FSD mode (Full self driving). The car be veered from the street and hit a light pole as the road was curving to the left. Airbags were deployed, and the car was a total loss, but nobody was hurt. The carhad automatic emergency braking and lane keeping assistance and despite this in FSD Full self driving mode managed to hit the lightpole and the accident occured. Can you investigate if this is a defect in the safety features of the car, or Tesla's FSD software or Automatic emergency braking and lane keeping assistance software? Thank you.

NHTSA ID

11746042

Incident

Jun 7, 2026

Speed profiles do not allow safe operation of the vehicle. Changes in speed profiles result in unsafe behavior. Standard speed profile regularly results in speed up to 73+ in a 55mph zone being selected by the vehicle. Chill mode results in speeds of 58 when traffic is traveling at 65mph. Switching profiles from standard to chill results in a rapid deceleration within the lane leading to problems with traffic behind the vehicle. In active school zones, system regularly does not acknowledge school zone speed limit and proceeds at 25-30mph in a 15 mph school zone even on Sloth profile. European FSD has a max speed setting that allows these problems to be prevented, but it is missing as a critical safety feature in the US version of FSD 14.

NHTSA ID

11742280

Incident

Jun 4, 2026

- Tesla FSD - My son was driving on FSD on state highway, while on FSD, the car suddenly turned left and hit the concrete barrier and spun out of control. All the air-bags were deployed and car front crashed completely. The car is near totaled, My son was able to get out the car with a bruise on right hand. -No -No -No warning was on, the car was on full FSD and suddenly turned left and drove into the concrete barrier and crashed and spun , I had no time to react/take over.

NHTSA ID

11741100

Incident

May 25, 2026

I was using actual smart summon to get my vehicle out of my garage. While standing behind the vehicle, it indicated that the car was in drive with no reversing lights on. The vehicle then rapidly lurches backwards, striking me and a freezer. After reviewing the dashcam footage the vehicle stated it was in drive and never once activated its reverse lights, even when they was objects and a human behind the car, still reversed at a high rate of speed.

NHTSA ID

11739971

Incident

May 25, 2026

2024 Tesla model 3 driving on the turnpike heading south of NJ right between exit 5-6 when my vehicle suddenly and spontaneously spun out into the guardrail, while at the same time the automatic emergency brake was disabled. Weather conditions were slightly rainy, there was no signs of traction issues or alerts regarding any concerns. Luckily no other vehicles were hit. The vehicle has not been inspected by any other of the above questioned. No such warning signs, lamps, or symptoms prior to this failure. I do have the dash cam footage that shows the incident.

NHTSA ID

11732592

Incident

Feb 22, 2026

On March 21, 2026, the vehicle’s Automatic Emergency Braking (AEB) and Traffic-Aware Cruise Control (TACC), suffered a severe "phantom braking" failure. While driving, the vehicle engaged in a violent, full-force emergency brake application without any external hazard or driver input. This unprompted deceleration caused the seatbelt to exert extreme pressure and trauma on my abdomen. As I was [XXX] pregnant, this abrupt stop was medically treated as a high-force accident. The trauma caused pregnancy abnormalities, requiring a 20-hour hospital admission for observation and fetal monitoring. I contacted Tesla customer service multiple times. Initially, I was told a service check was necessary, but the Service Center stated they could not provide assistance for "automatic behavior" issues. A corporate representative (Angel) admitted the vehicle should have been flagged for a formal medical claim and instructed me not to visit the service center. Despite this, I took the vehicle to the Service Center on April 15, 2026. Technicians confirmed they had no findings or solutions regarding the phantom braking event. No warning lamps, audible alerts, or system messages appeared prior to the failure. Upon requesting the vehicle data logs for the date of the incident, I noticed that the specific timeframe of the event was "missing" from the record. The manufacturer cited a VIN-matching error as the cause for the data gap. On April 20, 2026, Tesla corporate denied that a claim had ever been filed and stated they would not take responsibility for injuries related to pregnancy or a fetus, claiming these do not meet their internal threshold for medical injury. The vehicle remains available for inspection. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11732498

Incident

Mar 21, 2026

I continue to experience phantom "forward collision avoidance" warnings. Tesla has looked at this several times, even once charging me $60 to clean the cameras (should be under warranty in my opinion). Latest response to problem: known issue, no known hardware cause. In other words live with it. They even suggested buying FSD package at $1200/yr as a solution! One more than one occasion the TACC and Autosteer disengaged with traffic behind me. Very scary.

NHTSA ID

11720733

Incident

Feb 26, 2026

Screen is black and no app access. No power to accelerate.

NHTSA ID

11712810

Incident

Jan 19, 2026

I purchased a 2024 Tesla Model 3 a little over a year ago. Recently, and after an update, myself, and other drivers in my life, noticed the self-driving feature was malfunctioning - to the point I used the audio reporting feature to report this problem twice to Tesla. The car would veer off the road when flasing lights appeared and would jerk suddenly for no reason when it thought there was a obstruction in the road (sticks, plastic bags, etc.). Last month this malfunction has caused an accident, and my car has been totaled, my insurance will not cover it, and I have been advised by two separate attorneys to sue. This has been litigated in court with lawsuits against Tesla (See Benavides v. Tesla; see also IN RE: TESLA ADVANCED DRIVER ASSISTANCE SYSTEMS LITIGATION). I had notified Telsa twice of this issue, the car left the lane and did not notice a concrete barrier on the left side going north on I-95 in or around Broward County. To my knowledge no one has inspected the car. I was not warned that this car would cause an accident, the problem first appeared when I reported the issue using the voice reporting feature around November 2025. It is currently located at a tow facility in Broward County, FL and can be inspected there.

NHTSA ID

11712202

Incident

Dec 3, 2025

Incident Description (in my own words): This incident occurred in the parking lot of the [XXX] in Bretton Woods, New Hampshire. It was evening after sunset. The parking lot was dark but illuminated by overhead parking lights. My Tesla Model 3 headlights and vehicle lights were fully on. I was reversing slowly out of a tight parking space, traveling approximately 2–3 miles per hour. I was intentionally moving cautiously. My attention at the time was focused on the front right corner of the vehicle, as clearance there was tight. While reversing, the rear of my vehicle struck a parked truck behind me. The truck was relatively high (its headlights were positioned high on the vehicle). Neither I nor my passenger heard any rear collision warning, cross-traffic warning, or parking alert prior to impact. The vehicle also did not apply automatic braking. The contact occurred at very low speed and resulted in only minor cosmetic damage (a small dimple/deformation), but I was surprised that no warning or braking intervention occurred. Based on prior experience driving this vehicle, the collision and parking warning systems are typically configured to warn early, and I had confidence that a warning or automatic braking would activate in this scenario. Following the incident, I conducted a simple test by placing cones in front of the vehicle to see whether forward collision warnings would activate. They did not. While I understand cones may not trigger frontal collision alerts, this further contributed to my concern about object detection reliability in low-speed scenarios. The vehicle’s cameras were clean and unobstructed. I regularly clean the camera lenses. I am filing this complaint because my confidence in the vehicle’s collision warning and automatic braking systems has been shaken. I recently submitted a similar complaint regarding a collision involving our Tesla Model Y, and these two incidents—on two different Tesla vehicles—raise concerns for me INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT

NHTSA ID

11709516

Incident

Oct 22, 2025

Component/system that failed: Tesla Full Self-Driving (Supervised) software version 14.x (2025.38.x and later). The issue is software-only and remains installed on any vehicle updated to v14. Description of safety defect: FSD v14 deliberately removes the driver’s ability to set or adjust maximum speed offset using the right scroll wheel (feature present in all prior versions including my current v13.2.9). As a result, the system routinely exceeds posted speed limits by 5–20 mph with no way for the supervised driver to correct it short of fully disengaging FSD. The vehicle ignores speed-limit signs, relies on inaccurate map data, and follows surrounding traffic speed instead of the legal limit, even in school zones, construction zones, residential areas, and adverse weather. This significantly increases risk of collision, injury, and traffic citations. Reproduced/confirmed: Widely reproduced by thousands of owners on Tesla forums, Reddit, and X immediately after v14 rollout in late 2025. I have chosen to remain on v13.2.9 to avoid this exact defect. Inspected by manufacturer or others: No in-person inspection required; Tesla has full remote log access. Multiple owners have submitted in-car bug reports. Warning lamps/messages: None. The speed-offset control is simply grayed out and non-functional by design in v14. Vehicle available for inspection upon request.

NHTSA ID

11701831

Incident

Nov 27, 2025

The forward-facing camera on my vehicle repeatedly fogs up inside the sealed camera housing, creating a light to severe haze across the camera lens. This internal fogging obstructs the camera’s view and affects the vehicle’s safety systems that rely on it, including forward collision warning, automatic emergency braking, lane keeping, and adaptive cruise control. The components are available for inspection upon request. This obstruction puts my safety at risk because these systems either disable themselves or operate unpredictably when the camera view is blocked. The issue occurred again this year under normal outdoor temperatures, and the fogging cannot be cleared by the driver or by using defrost or cabin heat. The problem has been confirmed previously by a Tesla service center, where technicians inspected the camera area and told me my vehicle had one of the worst cases they had seen and told me this is a common issue. They attempted a repair, but the issue has returned, making it a recurring defect. No police or insurance representatives have inspected it. During the first occurrence, the vehicle displayed messages indicating that features like Autopilot, cruise control, and lane assist were disabled due to camera obstruction. The current recurrence produced visible internal haze over the camera lens and a warning message appeared which I do have that Tesla acknowledges this is an issue and that rather than fixing it, you can bring your car in for expedited cleaning. I have read others stating Tesla changed their windshield design and it doesn't heat up this area properly any longer. This issue has happened in multiple winter seasons and directly affects the proper operation of safety-critical driver assistance systems.

NHTSA ID

11699992

Incident

Nov 17, 2025

While driving with FSD engaged and set to standard profile, FSD accelerated to 76mph in a 55 zone. This is on software version 14.1.4. Unfortunately this new update no longer allows you to set your speed while using FSD, you can only select sloth, chill, standard, hurry, or mad max.

NHTSA ID

11699081

Incident

Nov 11, 2025

I was in process of completing a right hand turn, likely doing around 30 - 35 mph, when the vehicle suddenly and significantly applied the brakes, slowing the vehicle almost instantly down to around 12 mph, from what I had noticed. The road was entirely clear of any other vehicles, hazards, pedestrians or cyclists, with exception of a few parked cars along the curbs. There was absolutely NO reason for this abrupt braking maneuver, and it is at least the second time it has occurred within the past 11 months, both on a right hand turn. Today's incident jerked my head and neck abruptly, leaving me with a headache. It has undermined my confidence in the vehicle.

NHTSA ID

11697482

Incident

Nov 4, 2025

In early 2025, while reversing the vehicle, the backup camera proximity alert system failed to provide audible warnings of an obstacle. The visual display worked, but the system provided no beeping or audible alerts as I reversed toward a pole in the vehicle's blind spot, even though I was within the range where warnings should have been activated resulting in over $4K in damages. The same alert failure happened on 10/23/25 as I backed out of a parking space. I no longer live in the local area, but reported the safety issue in person during a visit on August 27, 2025. The acting service manager told me to expect a response in 10-14 days. After not hearing back, I followed up via the app on September 28, 2025. When I received a response on October 2, 2025, I was told my request is beyond the timeframe of when this could be inspected (30 days). The vehicle is covered under Tesla's 4-year/50,000-mile New Vehicle Limited Warranty, which covers defects in materials and workmanship. A failed backup camera system is precisely such a defect. California Song-Beverly Act: California's lemon law (Civ. Code § 1790 et seq.) requires manufacturers to repair defects covered by warranty. There is no 30-day reporting requirement under CA law. Federal Safety Standards: The backup camera is required safety equipment under 49 CFR 571.111. A malfunctioning backup camera renders the vehicle non-compliant with federal safety standards. Presumption of Manufacturing Defect: Under California law, defects occurring within 18 months/18,000 miles are presumed to be manufacturing defects (Civ. Code § 1793.2(d)(2)). This accident was well within that window. When I reported this defect to Tesla, they initially refused to: Conduct a safety inspection of the proximity alert/parking sensor system Retrieve diagnostic data or video footage to verify the system failure Test or repair the defective equipment under warranty As of 10/30/25, the local dealer agreed to a vehicle inspection

NHTSA ID

11697172

Incident

Jan 5, 2025

Yesterday I had another near miss collision and like all the others there was zero reaction from the car, an accident would happen long before the car would react. How many deaths are you going to allow to happen before you take proper action? It’s obvious someone there is being bought because the dangers can be easily proven over and over. My previous car would have braked long before I would have had to steer away from the oncoming vehicle, my Tesla has given me zero protection from front end collisions like the pictures provided.

NHTSA ID

11696818

Incident

Oct 30, 2025

A recent update has caused the vehicle to no longer acknowledge an important speed sign. This was confirmed by another Tesla, it is due to an update. This is unsafe and is capable of allowing the vehicle to travel through town at 75 mph where pedestrians cross the highway. If the camera gets blinded at the wrong time then it will NOT see people or vehicles as it plows into them. I made Tesla service aware and tried to submit a bug report but Tesla app simply says they are aware that the camera may not always read the signs. However, this was never an issue until a recent update. When are you going to make them liable?

NHTSA ID

11695584

Incident

Oct 1, 2025

On October 17, 2025, while Full Self-Driving (Supervised) was engaged, the vehicle made an abrupt, uncommanded steering input to the right, causing a collision with a tunnel wall. This crash appears to be the result of a critical vehicle hardware failure. In the 24 hours prior to the crash, the vehicle logged multiple critical steering errors, including EPAS3P_a086_dasMia, which indicates the Electric Power Assisted Steering system was "Missing in Action" and not communicating. Furthermore, the vehicle has logged daily, recurring hardware faults for the Steering Column Control Module (SCCM_a016_hardwareError) since it was purchased. The uncommanded steering action created an extremely dangerous safety condition resulting in a collision. All stability and traction control faults appeared at the exact moment of impact, not before, indicating the steering system failure was the root cause. The problem has been confirmed by the vehicle's own internal diagnostic logs. The vehicle is available for inspection.

NHTSA ID

11695128

Incident

Oct 17, 2025

Recently I had three back to back near miss head on collisions on highway early morning still dark. These three along with a previous near miss the vehicle had zero reaction to the imminent collision with roughly half a second to spare. It happened so fast that I must have let go of the record button as there was no saved video. I am working with lemon law firm and class action firm, get your crap together because these recent accidents reported in AZ are also your fault for not reacting appropriately to previous complaints.

NHTSA ID

11694033

Incident

Oct 1, 2025

Possible unintended acceleration incident While approaching the driveway the car accidentally accelerated on its own, cause a collision. We request that Tesla preserve all vehicle logs and telemetry data for safety investigation. VIN: [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11693178

Incident

Oct 13, 2025

Subject: FSD lane-selection issues at three specific Santa Clara locations Vehicle: [2024 Model 3], software [2025.32.8], FSD [v13.2.9] 1) 2025-10-12 [approx time 6:30pm PT] – Westbound [XXX] crossing [XXX] . Expected: proceed straight in through lane. Observed: FSD moves into left-turn lane to cross [XXX] . 2) 2025-10-12 [approx time 1pm PT] – Southbound toward [XXX] . Expected: choose left-turn lane. Observed: FSD sometimes stays in straight-through lane when attempting a left turn. 3) 2025-10-12 [approx time 4pm PT] – [XXX] exit to [XXX] approaching [XXX]. Expected: merge left lane before making a left turn. Observed: FSD sometimes stops at green in the through lane after failing to merge left. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11692997

Incident

Oct 12, 2025

My Model 3 was T-boned in an intersection, hitting both the front and rear doors, as a result of a vehicle running a red light. The driver that hit us was speeding and didn’t hit brakes. The impact pushed the Tesla almost in a complete 360 on an adjacent street where the driver side of the car jumped a curb and stopped after hitting a pole slightly on the driver side. Red light etc all substantiated by police report. Airbags deployed on the passenger side from the seat and upper panels. Front airbags failed on both sides. There was also a delayed airbag deployment from the back of the driver seat that only ripped the seat but never deployed fully. The smell of fire / burning and debris was all that happened from the driver seat. I requested a crash report from Tesla which outlines the speed and airbag deployment. The report says that knee level airbags deployed but they never did. I crossed referenced crash test speed data and various complaints about Tesla airbags. The data reviewed seems to indicate that I experienced failed equipment which is currently under review. I’ve also reviewed various sources of information about 7 2024 Model 3 driver side airbag known issues, where Tesla only recalled one vehicle. I’ve been told that other recalls for this issue are u see evaluation and to keep checking my vin for details. I share this because serious injuries can be caused by this failure, especially when hit by an SUV. The vehicle was totaled, not drivable and towed from the scene. Please be cautious if you have a 2024 model 3 and demand that Tesla look into the airbag manufacturing issues promptly and issue relative recalls. The collision alert also failed.

NHTSA ID

11692742

Incident

Sep 21, 2025