FaultScore

2017 Tesla Model S driver assist problems

133 of the 673 complaints about the 2017 Tesla Model S are about the driver-assist systems — 20% of everything reported for this model year. Half of the failures with a mileage on record happened before 26,000 miles.

D

133

Complaints

18

Crashes

0

Fires

0

Injuries

Exactly what failed

Adaptive Cruise Control 47 35.3%
Automatic Emergency Braking 27 20.3%
Assist 12 9.0%
Warnings 10 7.5%
Warning 9 6.8%
Back Over Prevention 8 6.0%
Warnings 8 6.0%
Blind Spot Detection 3 2.3%
Forward Collision Avoidance 3 2.3%
Rearview System Braking 3 2.3%

Driver Assist & Collision Avoidance across every Tesla Model S year

2013 17 2.6%
2014 17 2.6%
2015 73 11.0%
2016 91 13.7%
2017 133 20.0%
2018 84 12.6%
2019 20 3.0%
2020 37 5.6%
2021 77 11.6%
2022 51 7.7%
2023 32 4.8%
2024 34 5.1%

What owners said

Filed with NHTSA, in their own words.

Leesburg, VA

LANE DEPARTURE: WARNING

Backing out of driveway, the steering wheel was very hard to turn. The dash indicated the steering assist feature wasn't working. After restarting the software and the problem persisting, I investigated the assist motor/pump and found that the ground to the chassis was very corroded. I attempted to remove the nut to clean contacts and it sheared off. The grounding post had corroded through (white galvanic corrosion). I attached the assist motor ground to another point on the chassis and the power steering worked again.

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

Columbus, OH

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

This happens about 30%to 40% of the time when using Full Self Driving Supervised on HW3, FSD version 12.6.4, software version 2026.14.6. When changing marked lanes to the right, either initiated by FSD or the driver asking FSD to move to the right by engaging the right turn signals, it will do one of 2 things: 1. Change lanes properly about 70% of the time 2. Start and abort the lane. Hange swerving back and forth between the 2 lanes, ot 3. Does nothing and drives straight without changing lanes, all the while with the turn signals on. #2 is particularly dangerous.

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

Columbus, OH

FORWARD COLLISION AVOIDANCE: WARNINGS

Using FSD. Stopped at a stop sign making a UPL into a 4-lane 35 MPH posted street. TWICE now there was a small opening which would require an aggressive accelerator - it started the turn stopping a full car length into the first lane and decides it's going to wait for closing traffic from the right. Obviously stopping in the middle of new oncoming traffic from the left is not very wise. This has happened 3 times with 2026.8.3 and I've never seen it before - twice i gunned it to force the short turn but missed it once. Definitely a pucker maneuver.

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

Morgan Hill, CA

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

CRITICAL SAFETY FAILURE: Loss of Driver Override and Extreme HMI/Signaling Latency. 1. Loss of Override & Unintended Acceleration: While operating FSD (Supervised), the vehicle ignored a 65 mph set-point and accelerated to 80 mph. I attempted to reduce speed by pulling down on the steering stalk 4-5 times, but the vehicle ignored all manual inputs, requiring a hard disengagement. 2. Lane Departure / Path Failure: The vehicle failed to maintain lane centering, specifically crossing over the centerline into opposing traffic. This occured without warning or system-initiated steering alerts 3. False Signaling / Path Failure: I’ve seen at least two occurrences where system exhibits dangerous signaling conflicts, such as activating a right-turn signal while simultaneously executing a left-turn maneuver. One time it was on a 45–55 mph rural corridor where trailing drivers frequently overtake slower vehicles. A false right-turn signal acts as a dangerous "all-clear" for a trailing driver to pass on the left, creating a high- probability broadside collision scenario when the Tesla physically executes its left turn. I have no idea if this has occurred more than these two times as I don’t check this. The other time I caught on video, by chance, as I was trying to capture the surging behavior to show the Tesla service center 4. Audio & Visual HMI Latency: Audible instructions arrive 100+ feet after turns, and the map UI auto-zooms away from the driver’s focus, requiring constant manual screen contact to view street names. This forces significant Visual-Manual Distraction. 5. Confirmed Inadequacy: Tesla Service Invoice #[XXX] (Jan 27, 2025) documents: 'The current computer is a little too slow for full self driving function...' confirming the hardware is unfit for safety-critical processing. This incident is directly relevant to NHTSA Investigation PE25012. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

Morgan Hill, CA

LANE DEPARTURE: WARNING

CRITICAL SAFETY FAILURE: Loss of Driver Override and Extreme HMI/Signaling Latency. 1. Loss of Override & Unintended Acceleration: While operating FSD (Supervised), the vehicle ignored a 65 mph set-point and accelerated to 80 mph. I attempted to reduce speed by pulling down on the steering stalk 4-5 times, but the vehicle ignored all manual inputs, requiring a hard disengagement. 2. Lane Departure / Path Failure: The vehicle failed to maintain lane centering, specifically crossing over the centerline into opposing traffic. This occured without warning or system-initiated steering alerts 3. False Signaling / Path Failure: I’ve seen at least two occurrences where system exhibits dangerous signaling conflicts, such as activating a right-turn signal while simultaneously executing a left-turn maneuver. One time it was on a 45–55 mph rural corridor where trailing drivers frequently overtake slower vehicles. A false right-turn signal acts as a dangerous "all-clear" for a trailing driver to pass on the left, creating a high- probability broadside collision scenario when the Tesla physically executes its left turn. I have no idea if this has occurred more than these two times as I don’t check this. The other time I caught on video, by chance, as I was trying to capture the surging behavior to show the Tesla service center 4. Audio & Visual HMI Latency: Audible instructions arrive 100+ feet after turns, and the map UI auto-zooms away from the driver’s focus, requiring constant manual screen contact to view street names. This forces significant Visual-Manual Distraction. 5. Confirmed Inadequacy: Tesla Service Invoice #[XXX] (Jan 27, 2025) documents: 'The current computer is a little too slow for full self driving function...' confirming the hardware is unfit for safety-critical processing. This incident is directly relevant to NHTSA Investigation PE25012. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

at 98,787 miles Westbrook, ME Crash

FORWARD COLLISION AVOIDANCE

The contact owned a 2017 Tesla Model S. The contact stated that while starting the vehicle, an Autopilot disabled warning message system was displayed a day prior. The contact reached out to the Tesla hotline for assistance regarding the failure. The contact was advised to continue driving the vehicle, and the system error message was expected to clear. The contact stated that after multiple drives, the warning message did not disappear. The contact stated that while coming to a stop, the brake system became inoperable. The contact stated that the vehicle then accelerated to approximately 35 MPH, causing the contact to rear-end another vehicle. Multiple warning messages were displayed, including: traction and stability control disabled, automatic emergency braking system fault, battery management system critical fault, and electrical system reduced, as reported through Tesla chat assistance. The contact also stated that all air bags deployed. No injuries were sustained, and no medical attention was provided. A police report was filed. The vehicle was towed and deemed a total loss. The dealer was contacted; however, the vehicle was not diagnosed or repaired. The manufacturer was not made aware of the failure. The approximate failure mileage was 98,787.

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

Greeley, CO

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Software version 2025.32.3.1. Using Tesla’s auto-steer / enhanced autopilot (not fsd) causes many “phantom braking” events when going through several intersections on my commute. It’ll say a message “Curve Assist Active”, however I’ll be on a very straight and flat road with no curves. It’s 65 mph road and it will brake / slow down the car very hard and fast, if I don’t catch it in time it’ll get down to ~45 mph within a second. Even when traffic is going slow already, like 40 mph, it’ll still bring up the message and try to brake and slow down, though not as hard. Typically to about 25-30 mph. I usually can catch it and use the accelerator to prevent it, but sometimes it’ll happen so sudden and I worry about getting rear-ended by someone behind me. Very repeatable. Very startling and concerning when it happens when I don’t expect it to. I believe it’s a mapping issue as it has not been fixed in over a year and after several software updates.

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

at 66,573 miles Windsor Hills, CA

FORWARD COLLISION AVOIDANCE

The contact owns a 2017 Tesla Model S. The contact stated that while driving at an undisclosed speed, the Forward Collision Avoidance system became inoperable. There was no warning light illuminated. The contact stated that the Forward Collision Avoidance feature failed to activate, almost resulting in a crash with another vehicle. Additionally, the contact stated that the back over collision avoidance system was inoperable. The vehicle was taken to the dealer, where it was determined that the front radar and bracket had failed and needed to be replaced. The vehicle was not repaired. The contact expressed a concern that the failure posed a significant safety hazard, as the Forward Collision Avoidance was inoperable. The manufacturer was not made aware of the failure. The approximate failure mileage was 66,573.

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

Saint Louis, MO

LANE DEPARTURE: WARNING

While merging onto the highway an error message showed up on the dash stating "Steering Assist May be Reduced" upon immediately after the steering froze and could only be moved slightly using significant force. Approx. 75lbs. I am athletic and work out and had trouble moving the car to the side. If my wife or daughter had driven the car they would not have been able to steer and this could have caused a significant accident, injury or death. Upon pulling over, I rebooted both computers on the Tesla Model S 75 D and the problem went away. I immediately drove to the Tesla dealer in Chesterfield, MO. There they seemed unconcerned, and advised me it was likely just a firmware issue and wouldn't be able to look at the car until the next week. I was shocked. Since the systems seemed to work I drove home and parked the car. On the driveway, the same error showed up and steering seemed again to lock up. After rebooting problem went away. Looking at the Tesla forums this seems to have happened before and poses a serious danger to the driver, occupants and fellow drivers on the road. I no longer feel safe driving the car.

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

Columbus, OH

LANE DEPARTURE: ASSIST

Using software version 2025.14.1 with FSD (Full Self Driving) version 12.6.4. About 50% of the time the vehicle attempts and fails to change lanes when using FSD. It will: 1. Turn on signal and not change lanes, confusing cars around me. Or more often 2. Swerve between lanes indefinitely. See example at [XXX] It drives like a drunk driver. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

Columbus, OH

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Software 2025.14.1, Full Self Driving 12.6.4 (FSD). Vehicle when using FSD continuously slows to 10 MPH below the speed limit. You can manually press the accelerator to speed up but FSD will not brake when doing so and warns you of the same. After a minute of being back at the speed limit, FSD again slows down. Repeat this process constantly. Very dangerous.

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

Trent Woods, NC

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Stoped at intersection. While trying to engage signal lights, hit the stalk below that engages full self driving. Car immediately jumped into intersection .in front of another car and almost collided. Since the last update, Cars with my configuration wave been acting irradely and it is not safe to use FSD.

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

San Pedro, CA

BACK OVER PREVENTION: WARNINGS

Car auto accelerated in parking lot structure. Hit column; air bags did not deploy so no injury to me, the driver. Dealer refuses to confirm the data to support their conclusion that driver was at fault. Vehicle inspected by dealer owned collision center and dealer related insurance company. No warning or messages prior to auto acceleration.

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

Austin, TX Crash

FORWARD COLLISION AVOIDANCE: WARNINGS

I used Summon on [XXX] to bring my car to me because it was parked way at the end of the parking lot at Discount tire. There was only 1 car in the whole lot, which was parked next to my Tesla. While using the “come to Me” feature in Summon – My Tesla pulled forward and then turned and drove right in to the car parked next to mine. It did quite a bit of damage to my Tesla and the Mercedes parked next to me it ran into. When I called my local Tesla Service Center in Austin to ask what I am supposed to do, they told me they needed to run diagnostics to see if they can fix the “summon” issue. After running diagnostics they blamed the issue on the wrap I have on my car. They did not test the sensors obviously though, because they work fine through the wrap. Not to mention that Tesla offers wraps from the factory now. They also stated that Summon was aborted due to collision, so it did report their was a wreck. Repair Notes: The proximity sensors on the vehicle are being obstructed by the vehicle wrap, which results in interference or compromised sensor functionality. This interference can disrupt the accurate detection of surrounding objects, impacting the vehicle’s ability to engage safety features like autopark. Data analysis reveals that the autopark function was aborted during collision, due to the seat belt not being fastened at the time of the incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

Austin, TX Crash

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

I used Summon on [XXX] to bring my car to me because it was parked way at the end of the parking lot at Discount tire. There was only 1 car in the whole lot, which was parked next to my Tesla. While using the “come to Me” feature in Summon – My Tesla pulled forward and then turned and drove right in to the car parked next to mine. It did quite a bit of damage to my Tesla and the Mercedes parked next to me it ran into. When I called my local Tesla Service Center in Austin to ask what I am supposed to do, they told me they needed to run diagnostics to see if they can fix the “summon” issue. After running diagnostics they blamed the issue on the wrap I have on my car. They did not test the sensors obviously though, because they work fine through the wrap. Not to mention that Tesla offers wraps from the factory now. They also stated that Summon was aborted due to collision, so it did report their was a wreck. Repair Notes: The proximity sensors on the vehicle are being obstructed by the vehicle wrap, which results in interference or compromised sensor functionality. This interference can disrupt the accurate detection of surrounding objects, impacting the vehicle’s ability to engage safety features like autopark. Data analysis reveals that the autopark function was aborted during collision, due to the seat belt not being fastened at the time of the incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

Austin, TX Crash

BACK OVER PREVENTION: WARNINGS

I used Summon on [XXX] to bring my car to me because it was parked way at the end of the parking lot at Discount tire. There was only 1 car in the whole lot, which was parked next to my Tesla. While using the “come to Me” feature in Summon – My Tesla pulled forward and then turned and drove right in to the car parked next to mine. It did quite a bit of damage to my Tesla and the Mercedes parked next to me it ran into. When I called my local Tesla Service Center in Austin to ask what I am supposed to do, they told me they needed to run diagnostics to see if they can fix the “summon” issue. After running diagnostics they blamed the issue on the wrap I have on my car. They did not test the sensors obviously though, because they work fine through the wrap. Not to mention that Tesla offers wraps from the factory now. They also stated that Summon was aborted due to collision, so it did report their was a wreck. Repair Notes: The proximity sensors on the vehicle are being obstructed by the vehicle wrap, which results in interference or compromised sensor functionality. This interference can disrupt the accurate detection of surrounding objects, impacting the vehicle’s ability to engage safety features like autopark. Data analysis reveals that the autopark function was aborted during collision, due to the seat belt not being fastened at the time of the incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

The Woodlands, TX Crash

BACK OVER PREVENTION: WARNINGS

I activated Tesla's Smart Summon feature on the 2017 Tesla Model S to autonomously drive from the parking spot to the front entrance of the restaurant where I was waiting. Pulling out of the spot (my car was back in), the vehicle prematurely turned and contacted the front bumper of the adjacent vehicle (also backed in). My vehicle proceeded for a few feet causing severe damage to my driver side and the other vehicles bumper. I entered my vehicle and pulled away from other vehicle which is still in contact with. Take document with photos, I returned my vehicle to the location where it occurred (except not in contact). See photos. I contact that evening and they spent the next week investigating. They disavow and responsibility and said I was supposed to monitor the progress. The incident took a few second and there was not time to react to avoid damage.

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

Los Gatos, CA

BACK OVER PREVENTION: WARNINGS

Computer software failure. Intermittent problem that started with a recent software update. When backing out of a parking space, car will move a few feet then go into park and set the parking brake. Putting car back into reverse allows the car to move about 2 feet then the parking brake re engages. This has repeated more than 6 times in the process of backing out of a parking space. (There was at lease 3' of clearance to the sides of the vehicle and nothing behind the vehicle.) This is very dangerous when backing out of a diagonal parking space that is along the side of a busy road. I have scheduled Tesla service for the soonest appointment which is 2 weeks from now.

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

Dallas, TX Crash

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

While using the summon feature from my iPhone with the Tesla application my car drove into my house causing damage. I have video of this from my camera doorbell of the incident. I work in mobile application development and was told this was user error by Tesla when it first occurred.

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

Dallas, TX Crash

FORWARD COLLISION AVOIDANCE: WARNINGS

While using the summon feature from my iPhone with the Tesla application my car drove into my house causing damage. I have video of this from my camera doorbell of the incident. I work in mobile application development and was told this was user error by Tesla when it first occurred.

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

Dallas, TX Crash

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

While using the summon feature from my iPhone with the Tesla application my car drove into my house causing damage. I have video of this from my camera doorbell of the incident. I work in mobile application development and was told this was user error by Tesla when it first occurred.

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

Las Vegas, NV Crash

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Approaching my garage door as it was opening when the car suddenly accelerated smashing through the garage door, through the back wall of the garage, through the laundry room and finally stopped in the main bedroom with the front wheels off the ground as the car rested on top of the washing machine.

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

Orange, CA

BACK OVER PREVENTION: SENSING SYSTEM: CAMERA

See attached document for complaint

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

Renton, WA Crash

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

Full Self driving did not show signs of slowing down at Everett traffic slow down from about 60 miles to a standstill. I realized the speed not slowing down (about 5 car distance from stopped distance) I tried to apply the brakes that were completely nonresponsive, instead the car sped up. I avoided backend collision with the first car be maneuvering to the shoulder, however the next car was parked halfway into the shoulder that didn't leave enough room to not hit it. The car hit two other cars before coming to a full stop. While checking for any injuries for myself and passenger, after a delay and hitting 3 cars the airbags uselessly deployed. Total failure of brakes, auto emergency braking and airbag deployment. I have requested Tesla to look into the logs but havent gotten any feedback.

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

Tulsa, OK

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

I received a safety recall dated 2/8/2024, recall no 23V-838. Tesla has failed to remedy the defect & claims a remedy is not necessary. Specifically, I took my vehicle to Tesla on 3/18/2024 to update vehicle software to incorporate additional autosteer controls. See attachment: "Repair notes: "No update necessary", despite the vehicle running a software version less than 2023.44.30 as specified in the Recall Notice.

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

Tulsa, OK

LANE DEPARTURE: WARNING

I received a safety recall dated 2/8/2024, recall no 23V-838. Tesla has failed to remedy the defect & claims a remedy is not necessary. Specifically, I took my vehicle to Tesla on 3/18/2024 to update vehicle software to incorporate additional autosteer controls. See attachment: "Repair notes: "No update necessary", despite the vehicle running a software version less than 2023.44.30 as specified in the Recall Notice.

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

Tulsa, OK

LANE DEPARTURE: ASSIST

I received a safety recall dated 2/8/2024, recall no 23V-838. Tesla has failed to remedy the defect & claims a remedy is not necessary. Specifically, I took my vehicle to Tesla on 3/18/2024 to update vehicle software to incorporate additional autosteer controls. See attachment: "Repair notes: "No update necessary", despite the vehicle running a software version less than 2023.44.30 as specified in the Recall Notice.

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

Leander, TX

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Autopilot drove me off the road during turning right on Hwy 183 on April 4, 2023. 9:04 pm. My tesla Model S was on Autopilot and Car went off the road during right turn and about to hit the red light pole.

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

Leander, TX

LANE DEPARTURE: ASSIST

Autopilot drove me off the road during turning right on Hwy 183 on April 4, 2023. 9:04 pm. My tesla Model S was on Autopilot and Car went off the road during right turn and about to hit the red light pole.

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

Rutherfordton, NC

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Tesla has failed to provide the software updates to fix the recalls on my and ALL other MCU1 cars that have FSD paid for. This is because Tesla has not delivered sent FSD to these cars, and hopes owners will pay $2,000 to upgrade to MCU2. Tesla has LIED that all cars with FSD paid for will be upgraded to the required hardware necessary to use FSD. This has now became a safety issue as recalls are not being addressed!! Tesla States vehicles should be running software version 2023.44.30 or later... We are stuck at 2022.8.10!

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

Other 2017 Tesla Model S problems

← Full 2017 Tesla Model S report