FaultScore

2026 Tesla Model 3 driver assist problems

14 of the 31 complaints about the 2026 Tesla Model 3 are about the driver-assist systems — 45% of everything reported for this model year.

F

14

Complaints

10

Crashes

0

Fires

0

Injuries

Exactly what failed

Adaptive Cruise Control 3 21.4%
Automatic Emergency Braking 3 21.4%
Warnings 3 21.4%
Blind Spot Detection 2 14.3%
Assist 2 14.3%
Warning 1 7.1%

Driver Assist & Collision Avoidance across every Tesla Model 3 year

2017 16 0.5%
2018 370 12.7%
2019 338 11.6%
2020 274 9.4%
2021 637 21.8%
2022 848 29.0%
2023 278 9.5%
2024 85 2.9%
2025 62 2.1%
2026 14 0.5%

What owners said

Filed with NHTSA, in their own words.

Sioux Falls, SD

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Driving on a 2 lane road going 65 with Traffic-Aware Cruise Control enabled at 65 MPH with a car behind and no car in front of us. the car phantom braked for no reason going from 65 to 40 mph in a matter of seconds. Luckily we were able to accelerate to avoid being rear ended

NHTSA complaint #11758118 — an unverified report by a vehicle owner.

Oro Valley, AZ

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

The vehicle is experiencing severe, unpredictable software and hardware regressions related to the Full Self-Driving (Supervised) system (v14.3.7, Software build 2026.21.5) that create an immediate, active traffic hazard and a high risk of rear-end collisions. Primary Safety Issues: 1. TRAFFIC STALLS UPON DISENGAGEMENT: When Full Self-Driving (FSD) is engaged, auxiliary sensors malfunction, causing the headlights to cycle on/off and windshield wipers to run at full speed in clear, dry, midday daylight. When attempting to manually disengage FSD to correct these malfunctioning systems, the vehicle fails to smoothly transition control. Instead, it triggers critical red flashing alert lights, sounds severe warning chimes, and initiates an immediate, aggressive brake application—stopping the vehicle dead in active, live traffic. 2. PHANTOM BRAKING: The vehicle routinely experiences sudden, severe, and unprovoked phantom braking events while driving at speed, without any forward obstacles or environmental hazards present. 3. STEERING INSTABILITY: When navigating parking lot entrances, the vehicle exhibits extreme "indecisive behavior," resulting in violent, rapid shaking of the steering wheel before completing the maneuver. Tesla customer service was formally notified of these dangerous system behaviors on August 14, 2026. A formal remote engineering log review has been requested from the manufacturer, as these sudden braking actions in active traffic pose an immediate threat to public safety.

NHTSA complaint #11757060 — an unverified report by a vehicle owner.

Knoxville, TN

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

After a recent Tesla software update, a mandatory Full Self-Driving disengagement feedback window appears every time I disengage FSD while the vehicle is still moving. The feedback window covers a large portion of the display with a black overlay, noticeable enough something popped up. There is no setting to disable it, dismiss it immediately, or postpone the response until the vehicle is stopped. I am required to select a disengagement reason before I can access the controls and information behind the overlay. While this window is displayed, I cannot properly view or control functions such as music and other touchscreen features behind the area. This is especially dangerous because it appears immediately after I take manual control from FSD—a moment when my full attention should be on the road and the vehicle. The system effectively requires me to look away from the road and interact with the touchscreen before I can make another needed adjustment. This occurs every time I disengage FSD and is consistently reproducible. This behavior began after software version FSD v14.3.3. My vehicle is a 2026 Model 3. The problem occurred everytime while traveling at any speed. I believe this mandatory, non-dismissible overlay creates a serious driver-distraction hazard by obstructing the center display and requiring touchscreen interaction while the vehicle is in motion. Tesla should allow the feedback request to be dismissed, delayed until the vehicle is parked, or disabled entirely.

NHTSA complaint #11752822 — an unverified report by a vehicle owner.

South Salem, NY Crash

LANE DEPARTURE: WARNING

Firstly, we were driving in the center lane on I-84W (three lanes), with Full Self Driving (FSD) at 55 mph. The car veered left on it owns (under FSD) into the center median with the front driver side of the vehicle struck the metal beam guardrail causing both air bags to deploy on the driver and left rear passenger sides. The car continued to move forward in the next 4-6 seconds under FSD (approximately 10-20 feet range) and then came to a complete stop with flashing warning screen asking driver to take over the steering wheel immediately.

NHTSA complaint #11751300 — an unverified report by a vehicle owner.

South Salem, NY Crash

LANE DEPARTURE: ASSIST

Firstly, we were driving in the center lane on I-84W (three lanes), with Full Self Driving (FSD) at 55 mph. The car veered left on it owns (under FSD) into the center median with the front driver side of the vehicle struck the metal beam guardrail causing both air bags to deploy on the driver and left rear passenger sides. The car continued to move forward in the next 4-6 seconds under FSD (approximately 10-20 feet range) and then came to a complete stop with flashing warning screen asking driver to take over the steering wheel immediately.

NHTSA complaint #11751300 — an unverified report by a vehicle owner.

Anna, TX Crash

LANE DEPARTURE: BLIND SPOT DETECTION

Incident involving my 2026 Tesla Model 3 equipped with HW4 hardware and the latest FSD (Supervised) software. During a garage reverse maneuver performed under FSD supervision, the vehicle had sufficient time to assess the surrounding environment before initiating the maneuver. There were no pedestrians or moving obstacles nearby. An adjacent parked vehicle was present next to the intended reversing path. During the maneuver, the vehicle made initial contact with the adjacent vehicle. At no point did the vehicle provide any collision warning, alert, or indication that a collision had occurred. After the initial contact, the vehicle continued moving and a second impact occurred shortly afterward, resulting in additional damage. Immediately after the second impact, the driver intervened and took control of the vehicle to stop the maneuver, before further damage is caused. My main concerns are: 1. Why did FSD fail to identify the adjacent vehicle before the maneuver? 2. Why was no collision warning provided before or after the initial contact? 3. Why did the vehicle continue the reversing maneuver after the first impact instead of stopping till driver intervention? 4. What if is pediatrician who qualify ADA, children, elder was in the position of the adjacent vehicle, this failed sensing would cause imparable result. I would appreciate a technical review of this event and a detailed explanation of Tesla’s findings.

NHTSA complaint #11749677 — an unverified report by a vehicle owner.

Anna, TX Crash

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

Incident involving my 2026 Tesla Model 3 equipped with HW4 hardware and the latest FSD (Supervised) software. During a garage reverse maneuver performed under FSD supervision, the vehicle had sufficient time to assess the surrounding environment before initiating the maneuver. There were no pedestrians or moving obstacles nearby. An adjacent parked vehicle was present next to the intended reversing path. During the maneuver, the vehicle made initial contact with the adjacent vehicle. At no point did the vehicle provide any collision warning, alert, or indication that a collision had occurred. After the initial contact, the vehicle continued moving and a second impact occurred shortly afterward, resulting in additional damage. Immediately after the second impact, the driver intervened and took control of the vehicle to stop the maneuver, before further damage is caused. My main concerns are: 1. Why did FSD fail to identify the adjacent vehicle before the maneuver? 2. Why was no collision warning provided before or after the initial contact? 3. Why did the vehicle continue the reversing maneuver after the first impact instead of stopping till driver intervention? 4. What if is pediatrician who qualify ADA, children, elder was in the position of the adjacent vehicle, this failed sensing would cause imparable result. I would appreciate a technical review of this event and a detailed explanation of Tesla’s findings.

NHTSA complaint #11749677 — an unverified report by a vehicle owner.

Anna, TX Crash

BACK OVER PREVENTION: WARNINGS

Incident involving my 2026 Tesla Model 3 equipped with HW4 hardware and the latest FSD (Supervised) software. During a garage reverse maneuver performed under FSD supervision, the vehicle had sufficient time to assess the surrounding environment before initiating the maneuver. There were no pedestrians or moving obstacles nearby. An adjacent parked vehicle was present next to the intended reversing path. During the maneuver, the vehicle made initial contact with the adjacent vehicle. At no point did the vehicle provide any collision warning, alert, or indication that a collision had occurred. After the initial contact, the vehicle continued moving and a second impact occurred shortly afterward, resulting in additional damage. Immediately after the second impact, the driver intervened and took control of the vehicle to stop the maneuver, before further damage is caused. My main concerns are: 1. Why did FSD fail to identify the adjacent vehicle before the maneuver? 2. Why was no collision warning provided before or after the initial contact? 3. Why did the vehicle continue the reversing maneuver after the first impact instead of stopping till driver intervention? 4. What if is pediatrician who qualify ADA, children, elder was in the position of the adjacent vehicle, this failed sensing would cause imparable result. I would appreciate a technical review of this event and a detailed explanation of Tesla’s findings.

NHTSA complaint #11749677 — an unverified report by a vehicle owner.

Sandown, NH

LANE DEPARTURE: ASSIST

Lane keeping assistance turns on with every drive no matter how many times I set it to off. Where I live there are many potholes and poorly paved roads, along with poorly marked roads. As I am swerving around obstacles the car will fight the steering inputs I am giving it, trying to steer me back into whatever I was avoiding. This is a safety issue, and is not a problem on our older Tesla model 3 performance, as once that vehicle is set to off, it stays off. Now, as I start every drive I am navigating through a couple screens to turn off this "safety" feature.

NHTSA complaint #11748263 — an unverified report by a vehicle owner.

Gig Harbor, WA Crash

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

The vehicle's Full Self-Driving (FSD) system was actively controlling the vehicle while executing a reverse maneuver into a residential garage — a routine the system had successfully performed on multiple prior occasions. During this session, the FSD system misjudged the maneuver and the vehicle struck the wall of the garage, causing damage. The failed component is the FSD software/sensor system. The vehicle is available for inspection upon request. Safety was put at risk because the system was in full control of vehicle movement in a confined space. The unexpected behavior did not provide sufficient time for the supervising driver to intervene before impact. No warning lamps or messages appeared prior to the failure. The system gave no indication it would behave differently from previous successful executions of the same maneuver. The incident has not yet been confirmed by a dealer or inspected by the manufacturer, though a vehicle incident data report has been requested from Tesla.

NHTSA complaint #11733346 — an unverified report by a vehicle owner.

Gig Harbor, WA Crash

LANE DEPARTURE: BLIND SPOT DETECTION

The vehicle's Full Self-Driving (FSD) system was actively controlling the vehicle while executing a reverse maneuver into a residential garage — a routine the system had successfully performed on multiple prior occasions. During this session, the FSD system misjudged the maneuver and the vehicle struck the wall of the garage, causing damage. The failed component is the FSD software/sensor system. The vehicle is available for inspection upon request. Safety was put at risk because the system was in full control of vehicle movement in a confined space. The unexpected behavior did not provide sufficient time for the supervising driver to intervene before impact. No warning lamps or messages appeared prior to the failure. The system gave no indication it would behave differently from previous successful executions of the same maneuver. The incident has not yet been confirmed by a dealer or inspected by the manufacturer, though a vehicle incident data report has been requested from Tesla.

NHTSA complaint #11733346 — an unverified report by a vehicle owner.

Gig Harbor, WA Crash

BACK OVER PREVENTION: WARNINGS

The vehicle's Full Self-Driving (FSD) system was actively controlling the vehicle while executing a reverse maneuver into a residential garage — a routine the system had successfully performed on multiple prior occasions. During this session, the FSD system misjudged the maneuver and the vehicle struck the wall of the garage, causing damage. The failed component is the FSD software/sensor system. The vehicle is available for inspection upon request. Safety was put at risk because the system was in full control of vehicle movement in a confined space. The unexpected behavior did not provide sufficient time for the supervising driver to intervene before impact. No warning lamps or messages appeared prior to the failure. The system gave no indication it would behave differently from previous successful executions of the same maneuver. The incident has not yet been confirmed by a dealer or inspected by the manufacturer, though a vehicle incident data report has been requested from Tesla.

NHTSA complaint #11733346 — an unverified report by a vehicle owner.

Cupertino, CA Crash

BACK OVER PREVENTION: WARNINGS

On February 5, 2026, at 12:21 PM PST, my 2026 Tesla Model 3 (Hardware 4) collided with a 5-inch wooden pillar while using the Autopark feature. The system failed to provide any audio chimes or visual warnings prior to the impact. I officially requested the driving logs from Tesla to investigate the cause of this failure, but Tesla refused to provide any logs or data. Furthermore, Tesla Service Center technicians insisted there were no hardware defects, effectively confirming that the collision was caused by a software/algorithmic failure of the Tesla Vision system to detect a stationary vertical object. Despite Tesla’s claim that the vehicle is "operating as designed," the system's inability to recognize common infrastructure and its failure to warn the driver constitutes a severe safety risk. This defect must be investigated to ensure the safety of the Hardware 4 autonomous platform, as the lack of proximity alerts could lead to far more serious accidents involving pedestrians or other obstacles.

NHTSA complaint #11730303 — an unverified report by a vehicle owner.

Los Angeles, CA Crash

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

The vehicle's FSD system malfunctioned and initiated an unintended reverse toward a closing garage door. To prevent a total-loss event (the door crushing the glass roof and trunk), I was forced to perform an emergency manual takeover. Due to the vehicle's position caused by the malfunction, I had to maneuver through a confined space, resulting in the side-scrape. I am filing this as a malfunction claim because the damage was a direct consequence of the car's autonomous failure

NHTSA complaint #11711494 — an unverified report by a vehicle owner.

← Full 2026 Tesla Model 3 report