2026 Tesla Model Y driver assist problems

LANE DEPARTURE: ASSIST

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.

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

FORWARD COLLISION AVOIDANCE: WARNINGS

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.

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

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)

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

LANE DEPARTURE: ASSIST

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)

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

BACK OVER PREVENTION: WARNINGS

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)

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

LANE DEPARTURE: ASSIST

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.

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

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.

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

LANE DEPARTURE: BLIND SPOT DETECTION

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

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

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.

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

LANE DEPARTURE: ASSIST

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.

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

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.

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

LANE DEPARTURE: ASSIST

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 NHTSA investigate this aggressive software behavior and compel Tesla to restore the option for owners to permanently set Lane Departure Avoidance to "Warning" or "Off".

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

Phantom braking while using the TACC on the tesla

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

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

Phantom braking while using the TACC on the tesla

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

LANE DEPARTURE

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.

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

FORWARD COLLISION AVOIDANCE: WARNINGS

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.

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

BACK OVER PREVENTION: WARNINGS

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.

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

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

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.

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

BACK OVER PREVENTION: WARNINGS

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.

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