- The problem
- Tesla, Inc. (Tesla) is recalling certain 2024-2025 Model 3, Model S, 2023-2025 Model X, and Model Y vehicles. The computer circuit board may short, resulting in the loss of the rearview camera image. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 111, "Rear Visibility."
- The risk
- A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.
- The fix
- Tesla released an over-the-air (OTA) software update, free of charge. Tesla will also identify any vehicles that experienced a circuit board failure, or stress that may lead to a circuit board failure, and replace the affected computers, free of charge. Owner notification letters were mailed March 7, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-00-001.
Driver assistance
2024 Tesla Model 3 Driver Assist problems
Owners have filed 57 complaints about the 2024 Tesla Model 3's driver assistance with NHTSA - 25% of all its complaints, most recently on October 9, 2026. They describe 13 crashes, 0 fires and 8 injuries. Phantom braking, automatic emergency braking, lane keeping, blind spot and collision warnings.
- Complaints
- 57
- Recalls
- 1
- Crashes
- 13
- Fires
- 0
- Injuries
- 8
- Deaths
- 0
Driver Assist recalls for the 2024 Tesla Model 3
Driver Assist complaints
On [redacted] at approx. 10:30 AM EST, my 2024 Tesla Model 3 was operating on Full Self-Driving (Supervised) on [[redacted]]. Without warning, the vehicle steered off the paved roadway. The driver attempted to take control by [turning the steering wheel / pressing the brake], but the vehicle did not respond to her input and FSD did not disengage. The car left the road and struck [the curb / roadside edge] before coming to a stop on the grass. Damage: rims cracked and bent, tires deflated and unseated from the...
Read the full complaint
rims, grass and soil packed into the wheels, wheel covers torn off, and scrape damage to the fender/wheel arch. The car could not be driven and was towed. Photos attached. Injuries: [none / describe]. Component/system: Full Self-Driving (Supervised) - steering control and driver override. The vehicle is at the Tesla Service Center in [LOCATION] and is available for inspection upon request. I have asked Tesla in writing to preserve all vehicle logs, event data and camera footage, and submitted a data privacy request for the incident data on [redacted] Safety risk: The driver could not regain control of the vehicle. With oncoming traffic, pedestrians or a deeper roadside hazard, this could have caused serious injury or death. Reproduced/confirmed by dealer: UNKNOWN. Tesla has not provided a diagnosis yet. Inspected by: Tesla Service (in progress). Warning lamps or messages before the failure: [None observed . I believe FSD failed to keep the vehicle on the road and failed to yield control when the driver intervened. I request NHTSA review this incident as part of its ongoing FSD investigation. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
My Tesla displays a mandatory FSD (Supervised) disengagement feedback survey on the center touchscreen while the vehicle is in motion. Whenever I disengage FSD and resume manual control, the vehicle automatically asks me to select a reason for the disengagement. On one occasion, after disabling the software due to fsd getting too close the construction, while being flustered,I attempted to disable the prompt and select a random option to get rid of it but kept pressing the wrong area of the screen due to trying to...
Read the full complaint
keep paying attention to the road and simultaneously trying to get rid of the prompt, in my frustration to do so,I side swiped one of the big construction cones, it was not a collision and there was no damage but it could have been worse, so I am selecting collision in the questionnaire. Attached as a file is the full complaint, the 2000 char limit is not enough.
On [redacted] at approximately 12:56 PM Pacific on [[redacted]], my 2024 Tesla Model 3 VIN [[redacted]] was operating in Full Self-Driving (Supervised). The system detected oncoming traffic, stopped, then reversed to yield and backed into a parked 2015 Ford Transit van that had an occupant inside. I am the registered owner. [[redacted]] was the driver. TeslaCam saved events at 12:56:33 and 12:56:43. There was little visible damage, no injuries logged, and no police report. Tesla's consumer privacy form does not...
Read the full complaint
accept a crash narrative. I requested a Vehicle Data Report / copy of my data on [redacted]. USAA/[[redacted]] claim [redacted] later assigned 100 percent fault to the Tesla driver for backing, treating this as a conventional reverse collision rather than an FSD commanded maneuver. I am reporting this as a safety defect in FSD (Supervised) because the vehicle reversed into a parked occupied vehicle while the feature was engaged. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
Date: [redacted], Time: 5.09.2026 State: [[redacted]] Location: [[redacted]] We were on Full Self Service Driving Mode A [[redacted]] came and hit my car in the passenger side behind the front wheel and front buffer. We were on left/fast moving lane and two semi-trucks were in the right lanes slight ahead of us (one had overweight sign). Something came out of the direction of trucks and hit our car with a big sound (moving object). When we stopped and checked the car later, it was evident that the damage was a...
Read the full complaint
sizable, it would have been something solid or heavy. Our concern is the Tesla was on Full Self Driving Mode, and it did not generate any alert, recording or more importantly, it did not break, change the driving direction nor try to avoid being hit by the object. This diminishes the reliability of Tesla FSD and raises serious safety concerns. We are in the process of filling insurance claim. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
I have been driving Tesla using FSD from [[redacted]] to [[redacted]] and passing [[redacted]] ([redacted] around 5 pm). We took an exit for rest room break near Gas Station. As soon as Car took exit using FSD, the car completely stopped suddenly in the middle of the road without any reason and warning. There was not any rain, visibility issue or driver distraction. There was not any alert or recording. As far as I remember, there was not a vehicle on the front 100ft. It was on a small bridge. My family was in the...
Read the full complaint
car (with [[redacted]]). This was a scary moment (had it happened on the highway or a vehicle behind crash) INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
After disengaging Tesla Full Self-Driving (FSD) and taking manual control of the vehicle, a feedback popup appears on the center touchscreen asking the driver to select a reason for disengaging FSD. The popup does not automatically disappear and remains on the screen unless the driver interacts with it. I believe this creates an unnecessary driver-distraction risk. The moment immediately following an FSD disengagement is precisely when the driver has resumed responsibility for manually controlling the vehicle and...
Read the full complaint
should be focused entirely on the road and surrounding traffic. Presenting a nonessential survey at that moment encourages the driver to look at and interact with the touchscreen. There should be an option to disable this feedback request, dismiss it without touchscreen interaction, or have it automatically disappear after a short period. I am reporting this because I believe requiring or encouraging touchscreen interaction immediately after transitioning from FSD to manual driving is a safety concern and should be reviewed.
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.
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
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.
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...
Read the full complaint
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.
- 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.
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.
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.
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 [[redacted]] pregnant, this abrupt stop was medically treated as a high-force accident. The trauma caused pregnancy...
Read the full complaint
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)
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.
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...
Read the full complaint
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.
Incident Description (in my own words): This incident occurred in the parking lot of the [[redacted]] 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...
Read the full complaint
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 (FOIA), 5 U.S.C. 552(B)(6)
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...
Read the full complaint
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.
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...
Read the full complaint
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.
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.
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.
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...
Read the full complaint
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
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.
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?
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...
Read the full complaint
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.
Tesla Model 3 driver assist complaints by year
Model 3 driver assist problems, every yearSource: U.S. National Highway Traffic Safety Administration (NHTSA) complaints and recalls, checked . Complaints are owners' own reports and are not verified. How we use the data