While pulling into my driveway at 3–4 MPH and only a few feet away from the garage door, I suffered a sudden medical emergency and became unconscious. As my body froze, my right foot accidentally floored the accelerator pedal. The vehicle did not override my foot input despite the immediate obstacle ahead. It accelerated through the garage door and the dining room wall, coming to a stop in the kitchen. As a result of this crash, I requiring a three-day hospitalization. I am filing this report because vehicle safety systems should have a setting or protocol to prevent low-speed pedal misapplications from completely overriding automatic emergency obstacle braking. These settings save lives and there are no reasons that Tesla doesn't implement it. I had problems uploading photos. Please contact me at [XXX] to provide photos. Thank you. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
2026 Tesla Model Y driver assistance complaints
Page 3 of 7: complaints 41 to 70 of 172, newest first, as owners wrote them.
On XXX at about 6:14 AM, my 2026 Tesla Model Y drove into a flooded railroad underpass on [XXX] near [XXX], with Full Self-Driving (Supervised) engaged and a navigation route active. It was raining heavily (Newark Airport measured 1.25 in from 5:51 to 6:51 AM), the light was poor around sunrise, and the underpass was dark. The water depth was not apparent to me. At 6:12 AM the National Weather Service had issued a Flash Flood Warning naming [XXX] and listing underpasses. Tesla's data log (my privacy export) records FSD active from 6:12:02, my third FSD session that morning. With FSD active, speed rose from 7 to 27.4 mph between 6:14:04 and 6:14:31, with no accelerator input recorded. Speed then fell sharply (up to about 0.3 g), which I believe is when the car hit the water. FSD stayed active about 8 seconds (200 ft) more; the state changed to ABORTING at 6:14:39, at about 6 mph. I saw no warning, and the export shows none during the approach. We could not drive out. Water rose to about window level and entered the cabin. From 6:17 the log shows restraint system, AEB, ABS, stability and traction control alerts. I lowered a window at about 6:19. At 6:25 the log shows both front door releases activated repeatedly; neither door opened. We climbed out the window onto the roof. Our videos show us there at 6:31 with the front of the hood and headlights under water, and the Elizabeth Fire Department rescued us by boat at about 6:51. The car is a total loss. UNKNOWN: exact water-entry speed, what FSD perceived, and why it disengaged. I ask the federal safety agency to investigate whether FSD detects and responds to flooded roads in heavy rain and poor light, to obtain Tesla's data for this event, and to review escape from a flooded vehicle whose doors did not open. A report with the data timeline is attached. The full Tesla data export and videos are available on request. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
Full self driving (FSD) has taken away my ability to set a maximum speed. Car is frequently wrong about the speed limit, especially in constructions zones where the speed limit changes more often. Car goes way too fast, then thinks the speed limit dropped and slows way down and then speeds up again. In addition, the 4 speed profiles they gave us instead of a simple max speed setting are useless. Standard mode usually works best but will sometimes do more than 15 mph over what it thinks the speed limit is.
My Tesla Model Y FSD (Full Self Driving mode) malfunctioned when it unintentionally accelerated and swerved dangerously to avoid what it concluded as potential collision with a merging truck. By the time the driver intervened the vehicle had made contact with road barricades damaging both passenger side front and back door and tire fenders. No warnings were issued. - Component or system failed or malfunctioned - Full Self Driving (FSD) - Safety - FSD malfunctioned causing a crash
Lane departure pulls the car unsafely when two lanes merge or one lane splits. It has caused us to swerve a few times leading to major safety concerns. It's locked by software we are forced to turn off manually every time we drive. Even when off it seems to pull me around on certain roads
Lane departure pulls the car unsafely when two lanes merge or one lane splits. It has caused us to swerve a few times leading to major safety concerns. It's locked by software we are forced to turn off manually every time we drive. Even when off it seems to pull me around on certain roads
I was using FSD today and was driving along highway 24 in Orinda and the car almost hit the highway island at speed of 64 mph. I attached the bideo
On September 11, 2026 at 5:11:51 PM in San Jose, CA, FSD (Supervised) had been engaged continuously for 23 minutes. The vehicle was traveling straight in its lane at 32 mph and still accelerating. FSD disengaged with no takeover warning: no visual alert, no chime. My data export from the manufacturer (200 ms resolution) confirms the timestamp and shows the driver-monitoring channel never entered either of its warning states during the drive, though both appear elsewhere in my data. Nothing I did caused it. Steering torque stayed within sensor noise, with no rightward torque at any point. First brake application was 5.56 seconds after; first accelerator input 15.5 seconds after; no steering wheel button events near the event. Immediately afterward the steering angle moved about 7 degrees right over five seconds with my torque still near zero. The vehicle left its lane toward parked cars and came very close to striking them. No forward collision warning, no automatic emergency braking. I braked manually and stopped. I re-engaged FSD 36 seconds later and again two minutes later. Both times it steered right again and I disengaged. No warning lamps or messages appeared before any of this. The manufacturer reviewed logs remotely but has not inspected the vehicle or reproduced the problem. They attribute it to reduced forward camera visibility. My export shows one camera-related alert for that drive, logged 23 minutes earlier and absent from the incident window. They later stated the vehicle logged 30 non-customer-facing "low" obstruction events over two weeks, and that a customer alert appears only for significant obstruction. I drove extensively in that period without incident. A condition judged not worth notifying me about should not also explain withdrawal of steering control at 32 mph. Root cause is unconfirmed pending a paid diagnosis I have not authorized. Vehicle available for inspection. I have dashcam footage and the full export.
This is an issue with Tesla's Full Self Driving (Supervised). The categories above don't match this capability. Sunday, XXX, about 6:05 PM. FSD (Supervised) version 14.3.9. Leaving In-N-Out Burger, [XXX], FSD chose to exit westbound onto [XXX]. A vehicle coming from the east had gone around the queue on my right and was westbound on [XXX]. FSD pulled forward so the nose entered that westbound lane in front of that car. I intervened with throttle and steering. No contact. Since I didn't honk there was no saved dashcam clip. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
Using FSD- supervised the car hit the garage door opening denting the car while backing up to park in my garage
I had the car in Full Self Driving Mode. The car turned off the road into a ditch, in which I had to take over the car.
Whenever I disengage full self driving the car forces me to tell it why I did it via an on screen selection. It does not go away after a period of time. I used to be able to dismiss it by hitting the voice button twice but they've removed that loop hole. It's very distracting and forces me to interact with the screen while driving. The selection screen also blocks the blind spot cameras. It comes up even when disengaging to park. Someone is going to wreck messing around with this forced distraction.
It is a safety complaint about the automated parking/FSD reverse maneuver. My brand-new Tesla Model Y (VIN: [[XXX]]), which I purchased XXX and which had only 819 miles on the odometer at time of the incident. Following the over-the-air software update to version 14.3.7, the vehicle's behavior changed. It began automatically selecting a reverse parking maneuver into my garage. Over the days following the update, the vehicle successfully completed this maneuver approximately 7–10 times without incident, which established a reasonable expectation that the system was handling it competently. On XXX at 03:34 PM, while executing this same reverse parking maneuver under my supervision, the vehicle struck my garage, causing damage to the rear bumper and quarter panel area. The prior version of software stopped when not able to correctly park in garage. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
I recently purchased this vehicle. I love it. It has a trial of full self driving, which I love almost all of the time. However, I noticed there is not any of the 5 settings for FSD that do not speed in school zones. I want to use FSD as much as possible, but I will not speed in a school zone. I am amazed that Tesla has been allowed to program the FSD in a way that will allow speeding in a school zone. I have to turn off FSD to maintain safety and avoid a ticket. Please require TESLA to have at least one of the 5 settings that will obey school zone speed limits.
On approximately August 15th,2026, I experienced a serious near miss while driving my 2026 Tesla Model Y at approximately 70 mph on an interstate. I activated my turn signal and began moving toward another lane while another vehicle was in or approaching my blind spot. I did not receive an audible blind spot warning early enough to alert me before beginning the lane change. The audible warning occurred only after I was already moving toward the occupied lane and the situation had become dangerous. My previous vehicle, a 2015 Hyundai Santa Fe, provided an audible warning when the turn signal was activated and another vehicle was detected in or near the blind spot. That earlier warning gave an opportunity to cancel a lane change before a dangerous situation developed. I believe the Tesla Model Y should provide an optional early audible blind spot warning when the turn signal is activated and another vehicle is detected in or rapidly approaching the blind spot. This would supplement the visual warnings and could help prevent high-speed lane-change collisions without requiring the driver to look toward a display. I respectfully request that the federal safety agency evaluate whether the timing and design of audible blind spot warnings in the Tesla Model Y provide drivers with adequate advance warning and whether an earlier audible alert could improve safety and save lives.
I had brought my Tesla Model Y to a stop. Given that the car has an auto-park feature, I did not put the car in park. My daughter got out of the car and opened the rear passenger door. I moved towards the Tesla screen to open the rear trunk for her. As I moved, my foot accidentally hit the accelerator running the car over her foot and causing a possible fracture. She was in agonizing pain and I had to call emergency services. This situation can be easily avoided by Tesla by immobilizing the car (placing it in Park) when the car has been brought to a stop or has been brought to a very low speed and ANY door is opened. Right now, immobilizing the car happens only if the driver door is opened when the car has been brought to a stop or the speed is very low.
FSD routing Issue: it’s a repeatable FSD lane selection safety issue, France Avenue South to I-494. Description: when using FSD from France Avenue South onto I-494, the system turns into the westbound only lane instead of staying in eastbound lane. At the end of westbound lane, FSD performs a sudden, last-second swerve into the eastbound only lane, cutting off vehicles behind already existing n the eastbound lane. This has happened multiple times, including both before and after the latest update v14.3.8. Expected behavior: FSD should identify the correct east only lane well in advance and stay in it when the rout is set for east 494. Concern: the late lane change cuts off traffic and creates a collision risk.
Subject: Safety Hazard caused by Emergency Lane Departure Avoidance on [2026 Tesla Model Y] Description: I am writing to report a serious safety issue regarding the Emergency Lane Departure Avoidance (ELDA) feature on my US-spec Tesla. Starting with recent software updates, the vehicle forces the Lane Departure Avoidance setting back to "Assist" upon every single drive cycle, with no option to disable it permanently. This behavior creates an immediate safety hazard, especially in cold climate regions and during winter driving conditions. When attempting to steer around immediate road hazards such as open manholes, deep potholes, or debris, the vehicle's cameras fail to recognize the object in the road. If the driver maneuvers to avoid the hazard without a pre-activated turn signal, the ELDA system aggressively intervenes, jerking the steering wheel back into the path of the danger. On slippery, icy, or wet roads, this unexpected electronic intervention causes a sudden loss of traction, risking a severe crash. Forcing a driver to navigate multiple sub-menus on a touchscreen to change a safety-critical setting before every single drive is dangerous and distracting. In the United States, there is no federal mandate requiring this setting to reset to "Assist" on every drive. I request that the federal safety agency investigate this aggressive software behavior and compel Tesla to restore the option for owners to permanently set Lane Departure Avoidance to "Warning" or "Off".
Phantom braking while using the TACC on the tesla
The contact owns a 2026 Tesla Model Y. The contact stated that while driving manually over 40 MPH, the Lane Departure Avoidance system jerked the steering wheel abruptly to the other side while the vehicle was still inside the desired lane. The failure was a recurring issue. The dealer was contacted and informed of the option to turn off the feature. However, each time the vehicle was restarted, the feature was turned on by default. The manufacturer was made aware of the failure. The failure mileage was approximately 300.
i was in FSD mode and my car began parallel parking.As the car was in reverse it automatically accelerated and crashed into the car behind me. I did not step on the accelerator pedal, nor the brake and my hands were not on the steering wheel. I in no way caused this accident. What is most surprising is that there was no warning response. Normally if I get too close to any object a color warning shows up on the screen, if I decide to make a change while driving the screen comes up with 4 options as to why I took control but in this case with the car hitting an object there was no response at all.Teslas standard answer is always that it's my fault. I know what happened and it was not my fault.I now have a repair estimate for $1,897.98 which I must be responsible for
This is what happened: While Full Self-Driving (FSD) was engaged, the vehicle approached an intersection and appeared unable to correctly follow the roadway. Instead of following the intended road path, the vehicle continued forward, drove over the curb, and struck a road sign. The impact knocked the sign down, and the sign subsequently struck the vehicle, including the roof glass. The roof glass shattered and small pieces of glass entered the cabin, exposing both the driver and front passenger to a safety risk. Vehicle data obtained after the incident shows that the vehicle was in ACTIVE_FSD leading up to the collision. FSD changed from ACTIVE to UNAVAILABLE approximately 1.5 seconds before the crash algorithm wake-up. Significant braking occurred only very close to the collision, and no Automatic Emergency Braking intervention was recorded during the incident window. The data also shows multiple substantial steering movements shortly before the collision. Accelerator-pedal data does not establish driver acceleration as the cause of the collision. The available samples show an accelerator position of 2.0% shortly before the collision and 0.0% in the next recorded sample. The driver applied the brake shortly before impact. There were no prior warning lamps or messages indicating that FSD was about to become unavailable before the vehicle departed the roadway. The vehicle has been inspected/repaired following the collision, and vehicle data relating to the incident has been obtained and preserved. Police responded to the collision, and the incident was also reported to insurance. A police report was filed, and the case number is 2026-07160174. I have not yet received the formal CR-4 crash report. Following the collision, I experienced significant psychological distress and trauma-related stress symptoms as a result of the incident.
The contact owns a 2026 Tesla Model Y. The contact stated that while driving at an undisclosed speed with the Full Self Driving Mode activated, the vehicle struck the garage wall, damaging the rear passenger’s side door. No injuries were sustained. The contact stated that the dealer had previously provided mobile service to replace the camera and that a second dealer, Tesla White Plains (250 Tarrytown Rd, White Plains, NY 10607), had performed a hard reset on the vehicle due to phantom braking; however, the failure persisted. The dealer was made aware of the failure but canceled an upcoming appointment and informed the contact that there was no failure found. The vehicle was not diagnosed or repaired. The manufacturer was made aware of the failure. The failure mileage was approximately 13,001.
On August 15, 2026, at approximately 5:00 PM, the vehicle was being driven with Full Self-Driving (Supervised) engaged during light rain. As the vehicle approached traffic ahead, it did not slow or brake as expected. The driver recognized that the vehicle was not slowing and attempted to intervene manually by pressing the brake pedal multiple times. The driver reports that despite these attempts, the vehicle did not slow or respond to the brake pedal as expected, and a collision occurred. There were no known warning lamps or warning messages indicating a braking-system problem prior to the incident. The vehicle has not yet been inspected to determine the cause of the reported braking behavior. The incident has been reported to the manufacturer, and a request has been made to preserve and review available vehicle data surrounding the collision, including braking inputs, vehicle speed, Full Self-Driving status/actions, warnings, diagnostic information, and safety/event data. The vehicle is available for inspection. At this time, the cause of the failure to slow as expected is UNKNOWN.
Car is less than a year old and forward camera is reporting visibility problem. Safety features, forward collision and autonomous driving is severely degraded. Tesla will not repair under warranty which requires disassembly of the camera housing. Front camera housing has been redesigned by Tesla but they are not retrofitting this fix for existing Model Y and have not issues a safety recall. This camera housing defect presents a risk to my safely and the safety of others.
I am submitting this complaint to report what I believe is a potential safety defect involving the Tesla Autopark feature on my 2026 Tesla Model Y Premium All-Wheel Drive. On 7/21/26 at approximately 7:40 a.m., I activated Autopark to park my vehicle in my driveway. A transit van was already parked nearby and remained stationary throughout the parking maneuver. While Autopark was controlling the vehicle, my Tesla continued reversing and failed to stop before striking the parked transit van. The collision caused damage to the right rear passenger side of my vehicle. Based on what I observed, the vehicle did not recognize or respond appropriately to the presence of the stationary van. This raises serious concerns regarding the ability of the Autopark system to detect nearby stationary vehicles and avoid collisions during low-speed automated parking. Although I understand that Tesla states the driver must supervise Autopark, I am concerned that the system continued reversing into an obvious stationary obstacle rather than warning the driver or stopping before impact. I respectfully request that Tesla: Preserve all vehicle diagnostic logs, camera data, and sensor data from approximately 7:40 a.m. on the date of the incident. Conduct a full engineering review of the Autopark event. Determine why the vehicle failed to detect or avoid the parked transit van. Advise whether this incident resulted from a software issue, hardware issue, sensor limitation, or another system malfunction. Provide me with a written response and a case number confirming that this has been recorded as a formal vehicle safety complaint. I am prepared to provide photographs, dashcam footage (if available), the exact incident location, repair estimates, and any additional information required to assist with your investigation. Thank you.
While returning the Tesla during a demo drive, the car suddenly braked extremely hard in the middle of the road for no reason. It was bright and sunny, and we were coming up to a green light. It caused me to slam my head back into the seat. There was seemingly no reason for the emergency braking, and if someone were behind me, it would have caused a collision.
While using FSD feature continuously for more than 45 minutes without stopping the system locks on to the previous road speed limit and freezes and the car ignores any new different speed limits and runs into FULLY ROUGE MODE...and almost ran into a pedestrian without slowing down. Example - if road speed limit is 45 mph and car driving between 45-50 mph and when the road speed limit drops to 35 or 25 mph car continues to run at 45-50 mph. ex2: if car running at 35 mph and later enters highway the car continues at 35 mph on highway where speed is 65 mph and likely to cause accident. The tesla does not have any forum or email support or phone support to address this issue and says it will reset if i stop on highway and wait for 15 mins to reset and then start again. This occurs every time if you drive continuously without stopping ( turning off car) for 45 min or more
On the highway, a vehicle in the lane next to me on the right moved towards the white dividing line, but never actually crossed into my lane. My Tesla was operating on Full Self-Driving (Supervised). The system miscalculated the front vehicle's trajectory and severely overreacted to it approaching the line. Without driver input, the FSD system initiated sudden, heavy braking and violently swerved to the left, crossing the lane line. Because the Tesla swerved suddenly into the left lane, the driver already occupying that lane was unable to avoid a collision, striking the left rear corner of my vehicle. I have video recordings from my Tesla that provides objective proof that the vehicle in front did not sideswipe or cut off my car, but rather that an abrupt vehicle automation failure forced my car out of its lane, I had no chance to react quick enough to avoid the accident. It also provides context as to why the driver behind me could not avoid the impact. I have preserved the video files and am ready to submit them to you immediately. Best regards [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
While driving a 2026 Tesla Model Y Premium on [XXX] at approximately [XXX] PM on [XXX] using Full Self-Driving (FSD) Supervised mode, the vehicle was traveling in the center lane (lane 2 of 3) when it ran over a large whole tire (commercial truck-sized) that was positioned in the center of the lane. The FSD system failed to detect or avoid the tire prior to impact. This incident demonstrates a critical safety limitation: Tesla FSD cannot detect large road obstacles such as a whole commercial truck tire positioned in the center of a highway lane at night. The FSD system showed no warning, took no evasive action, and did not alert the driver prior to the impact. Prior to the incident, there were no warning lamps, error messages, or any abnormal symptoms. All systems were functioning normally. Following the collision, a "Coolant Low - Schedule Service / Climate and driving performance may be limited" warning appeared immediately on the display screen. Upon inspection, all coolant had leaked out completely. Damaged components include: underbody, front bumper lower section, and cooling pump. The cooling pump damage is particularly concerning as it prevents proper battery temperature regulation, creating a significant risk of battery overheating and potential fire. The vehicle is currently at a Tesla-approved collision center. Inspection is still in progress. The vehicle has been reviewed by Tesla Service Center technicians and insurance representatives. Safety concern: Tesla FSD failed to detect and avoid a large, visible whole truck tire in the center of the highway lane at night, resulting in significant underbody damage, complete coolant loss, and cooling pump failure — posing serious battery fire risk. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
VIN decoder
See the problems and recalls for an exact car
Buying a used 2026 Tesla Model Y?
Check the exact car before you pay: accidents, salvage or flood titles, odometer readings and previous owners.
Check its history