2024 Tesla Model 3 driver assistance problems

Filed Oct 9, 2026 · Brakes, Driver assistance · GA

On XXX at approx. 10:30 AM EST, my 2024 Tesla Model 3 was operating on Full Self-Driving (Supervised) on [XXX]. 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 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 XXX 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 the federal safety agency 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)

Filed Sep 29, 2026 · Driver assistance · NY · crash

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 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.

Filed Aug 27, 2026 · Driver assistance · CA · crash

On XXX at approximately 12:56 PM Pacific on [XXX], my 2024 Tesla Model 3 VIN [XXX] 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. [XXX] 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 accept a crash narrative. I requested a Vehicle Data Report / copy of my data on XXX. USAA/[XXX] claim XXX 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)

Filed Aug 16, 2026 · Driver assistance · TX

Date: XXX, Time: 5.09.2026 State: [XXX] Location: [XXX] We were on Full Self Service Driving Mode A [XXX] 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 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)

Filed Aug 16, 2026 · Driver assistance · TX

I have been driving Tesla using FSD from [XXX] to [XXX] and passing [XXX] (XXX 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 car (with [XXX]). 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)

Filed Aug 14, 2026 · Driver assistance · GA

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 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.

Filed Aug 12, 2026 · Driver assistance · CA

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.

Filed Jul 30, 2026 · Driver assistance, Visibility · NC

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

Filed Jun 23, 2026 · Driver assistance · CA · crash

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.

Filed Jun 5, 2026 · Driver assistance · NY

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.