general problems of the 2026 Tesla Model Y - part 1

While driving on freeway, driver door glass exploded and shattered into pieces without anything hitting it.

Subject: repeated fsd attempts to enter closed reversible express lanes – 2026 Tesla Model Y (hw4) I am submitting this complaint to report repeated potentially dangerous behavior involving full self-driving (supervised) on my 2026 Tesla Model Y equipped with hardware 4 (hw4). On multiple occasions, fsd attempted to enter closed reversible express lanes along interstate 75 in the atlanta, georgia area. These express lanes operate in different directions depending on the time of day, with physical barriers controlling access. Despite the entrances being closed, fsd repeatedly attempted to enter them, requiring my immediate intervention to prevent potential collisions. Incident 1: September 19, 2026, approximately 10:45 pm location: terrell mill road express lane access, I-75 northbound fsd version: 14. 3. 8 while traveling northbound on I-75, fsd indicated its intention to enter the express lanes through the terrell mill road access point, which was closed at the time. I attempted multiple times to redirect the intended maneuver using the turn signal. Despite these attempts, fsd continued toward the entrance and was about to execute the turn when I took manual control to prevent the vehicle from entering the closed roadway. Incident 2: October 6, 2026, approximately 6:30 pm locations: big shanty road access and barrett parkway access, I-75 southbound fsd version: 14. 3. 10 while traveling southbound on I-75, fsd signaled its intention to enter the express lanes through the big shanty road access point, which was closed. I intervened and disengaged fsd to prevent the vehicle from entering. After passing that entrance, I reactivated fsd. The system subsequently rerouted and attempted to enter the closed express lanes again through the barrett parkway access point. I had to intervene a second time to prevent another potentially dangerous maneuver. Incident 3: October 8, 2026, approximately 6:00 pm location: I-75 southbound express lane entry, north of hickory grove road fsd.

I am reporting two nearly identical safety incidents involving Tesla full self-driving (supervised) on my Model Y. In both cases, the vehicle failed to detect a stationary concrete pillar and did not apply automatic braking, resulting in collisions. First incident – September 16, 2026 while using fsd (supervised) to reverse into my residential driveway, the system hesitated due to a parked vehicle on the left side. Instead of completing the reverse maneuver, the vehicle moved forward and struck a door pillar / gate post. I intervened and took over control only after the impact had already occurred. The vehicle sustained visible damage (scuff/dent on the side/rear area). Photos are available. Second incident – October 4, 2026 again using fsd (supervised) in a similar residential parking/driveway situation, I believed the vehicle was reversing and would correct its path. Without any warning or automatic braking, the vehicle continued and struck a concrete pillar. I had essentially no time to react before contact. I stopped the vehicle after the impact. Additional damage occurred. Photos of the vehicle position relative to the pillar and the resulting damage are available.

On 10/2/26 at approx 9pm I was using Teslas fsd to return home from nyc to NJ. I entered the Lincoln tunnel expressway at 30th street and around 38th street the car suddenly entered a ramp marked with a do not enter sign and a red light. It was too quick to disengage and move to the left (green lit) ramp. Luckily there were no issues on the closed ramp (possibly it was closed in preparation for construction later that night). But I was very concerned that fsd could make this mistake.

On September 28, 2026, I was driving my 2026 Tesla Model Y dual motor northbound on interstate 17 in arizona near the sedona exit area. Full self-driving (supervised) was engaged. The vehicle was running software version 2026. 27. 11 and fsd (supervised) version v14. 3. 10. There was light rain in the area and the roadway was wet. I was traveling approximately 66–67 mph in a posted 75 mph zone. While fsd was engaged, the vehicle unexpectedly initiated a lane change. During or immediately following the lane change, the vehicle encountered the wet/standing-water area, lost control, and struck the concrete barrier. I am concerned about why fsd initiated this lane change under these roadway conditions and whether the system properly detected and responded to the wet roadway. I have requested that Tesla preserve and review all available fsd logs, vehicle telemetry, steering and braking data, lane-change and path-planning information, camera data, collision data, and other information associated with this incident. I am requesting that NHTSA review this incident as a potential safety issue involving full self-driving (supervised), particularly its lane-change behavior and operation under wet roadway conditions. I am very positive this incident wouldn’t have happened if fsd wasn’t in play. This is huge safety concern I want to share to avoid any issues!.

The vehicle itself will not follow safety lane control. Full self driving was in fact it crosses double white lines and toll roads and will merge into other lanes that has led to unsafe situation excessive ticketing, especially in the [xxx] area. This has happened several times, where it’ll go over the double white line ignore the laws and it will stay in the left lane, causing traffic and disruption. Today it did it several times and jerked into the toll lane when it was a double white line and caused a traffic issue instead of working through it. It signal quickly and then just moved over which was not ok and it was against the rules. Each state has their own set of laws and the cars should be able to adjust each state to follow those laws to ensure safety. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

I and other telsa drivers report Tesla fsd takes too long to enter a lane from which the car has to turn. Some drivers report “last minute” trying to get into turn lane or expressway off ramp. Twice last week my Tesla (model y built in June 2026) waited much too long to get into the required turn lane. On both occasions I was either in outside lane needing to turn left, or middle lane needing to turn left. One first occasion Tesla in fsd was only 0. 3 miles from the turn as cars behind stacked up preparing to make the left turn. On second occasion, car in fsd was only 0. 2 miles from turn, even indicating by led light strip turning red, that a car behind was in my blind spot. Yet, the Tesla wedged itself in front of the car behind already in the turn lane forcing that driver to slam on his brakes to let Tesla in for the turn. The second occasion could have resulted in an accident or incited a road rage incident from the driver behind. I asked grok to request Tesla engineers fix this fsd poor decision-making. Grok said he’s aware of this problem, correctly referring to it as a “lane change timing” issue, but stated he could not message Tesla engineers. At next opportunity, I sent a message via microphone in my car, though not during a “why did I take over intervention” request, because I did not intervene. Grok offered help saying I could use my turn signal to get in turn lane further in advance of the turn, or change speed mode to adjust for traffic behind, but that defeats use of fsd. Would NHTSA please make this a priority issue for Tesla engineers to fix?.

Tesla supervised full self driving sped southbound into a school speed zone. Flashing speed zone yellow lights required speed of 20 mph. Tesla continued at 49-50 mph. Driver intervention was required to slow down to 20 mph. There has been one other incident reported for this Tesla in the same school zone operating northbound last week.

Fsd failed to recognize the emergency vehicle and attempted to pull out into the intersection.

While I was driving on the highway in rainy weather, my electric vehicle suddenly made a very loud blast or popping sound and immediately stopped working. The vehicle lost power, and all electrical functions became inoperative while I was in the middle of the highway. This created a serious safety hazard because I was unable to continue driving or operate the vehicle normally. There was no visible damage to the exterior of the vehicle. The tires were intact and appeared to be in normal condition, with no tire damage or other external damage that could explain the sudden loss of power. The vehicle stopped unexpectedly while driving in wet conditions, without any apparent external impact or physical damage.

When using fsd in a Tesla, they are forcing you to take your eyes off the road to engage with their quationaire on why I disengaged with fsd. Its always because I want to. I am being forced to look at the screen which also it is blocking important information. I am not a slave and won't be forced to answer a questionaire several times a day while driving. It makes users angry having to do that and I truly believe it is a safety hazzard. There needs to be an option to either not participate or scroll down so it goes away.

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.

Vehicle disengages my turning signal after I enter the turning lane, leading me to have to turn it on again or risk unsafe turning situations. No fix or work around offered.

When I manually disengage Tesla fsd while the vehicle is moving, a persistent feedback popup appears. It cannot simply be dismissed and requires interaction or feedback to clear. This has happened every day since fsd 14. 3. 2 was released, including September 13, 2026, the incident date entered on this form. This creates visual and cognitive distraction at the exact moment I have assumed manual control and need to focus on driving. I sometimes disengage fsd simply because I want to drive; disengagement does not necessarily indicate an fsd failure. Feedback should be optional, readily dismissible, or deferred until the vehicle is parked. I request that NHTSA review this behavior as a potential driver-distraction safety issue.

The car came to a standstill at an intersection with a red light and the proceeded through the red light. I have the video, the car was on fsd I have the video , cannot load it below.

2026 Tesla Model Y was operating with autopilot engaged. While making a right turn at a school, the vehicle struck a brick area, continued forward, struck a wall and rolled over. The driver and passenger survived without apparent injury. The vehicle was towed and appears to be a total loss.

Vehicle: 2026 Tesla Model Y system involved: full self-driving (supervised) date of incident: September 2, 2026 approximate time: 5:20 pm location: I-10 area near tucson, arizona crash: no injury: no near-miss / safety-critical event: yes I am reporting a serious safety incident involving the full self-driving (supervised) system in my 2026 Tesla Model Y. On September 2, 2026, at approximately 5:20 pm near tucson, arizona, I was using full self-driving (supervised) while traveling toward I-10. The vehicle was expected to enter I-10 but did not enter the highway as intended. Instead, the vehicle proceeded onto a service road, then entered an abandoned parking lot. Rather than safely correcting the route it started towards highway ramp against the normal direction of traffic. I immediately took manual control,stopped in an empty emergency area between the ramp and the service road and activated my emergency hazard lights. I remained stopped while approaching traffic slowed after observing my vehicle. Once it was safe to proceed, I manually and slowly repositioned the vehicle in the correct direction and entered I-10 using the ramp. There was no collision and no injury. However, I believe this event created a serious and potentially fatal risk because the vehicle’s automated driving system directed the vehicle toward a highway ramp in the wrong direction, creating the possibility of a wrong-way conflict with incoming traffic. I am also notifying Tesla for evaluation. I wonder if more similar incidents were reported recently (I learned the fatal collision killing passenger on oct 31st in az due to fsd malfunction).

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.

We (my son was in the drivers seat)my daughter and I were in the Tesla with fsd on. The car was instructed to go to mcdonalds. It tried to make a u turn on a busy road ([xxx]) with oncoming cars and got stuck as it was unable to make a complete u turn. The oncoming cars started honking. My son took control of the car and maneuvered it to the side road. It was very scary because the cars kept coming and to back up with cars coming towards you was a nightmare. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

My fsd in my Tesla was engaged, all of sudden it stopped on the highway without enough warning, and it cause my car to ram into the wall next to hov lane.

Tire pressure machine monitoring system is malfunctioning on 25 occasions since purchase of the vehicle. Took vehicle to the manufacturers service center and they confirmed the problem but stated no fix was available at this time.

My wife just reported to me that the car ran a red light while driving in fsd.

I own a 2026 Tesla Model Y, and I subscribe to and use Tesla's full self-drive ("fsd") service. Whenever I have the car in fsd mode and take over control of the car, thereby turning off fsd, a box appears in the bottom left corner of the display screen in the car that the driver must use for all functions of the car. That box asks why I turned the fsd off and requires that I choose from 4 selections. The box remains on the screen until a selection is chosen and does not disappear after any period of time on its own, and there is no option to stop that box from appearing every single time I take over from fsd. The requirement that I divert my attention from the road to the bottom corner of that screen every single time I take control of my vehicle from fsd is a dangerous distraction that on more than one occasion has almost caused an accident. It is ridiculous that Tesla imposes this dangerous feedback box on its drivers with no ability to turn it off or make it disappear without taking our eyes off the road to answer it. Please do something to require them to get rid of this dangerous mandatory feedback box before it gets people hurt or killed.

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

On xxx, I was driving my 2026 Tesla Model Y all-wheel drive northbound on [xxx] toward the [xxx] exit in [xxx]. Tesla full self-driving (fsd) was engaged as the vehicle entered a single-lane exit ramp with a curve. The fsd system did not slow the vehicle sufficiently for the curve. I intervened by applying the brakes, but the vehicle struck a reflector pole with its front bumper area. No other vehicle was involved. I am reporting a suspected malfunction of the fsd system’s ability to recognize roadway curvature, select an appropriate speed, and slow the vehicle in time to navigate the curve safely. This created a safety risk because, despite my intervention, a collision occurred. Under similar circumstances, the vehicle could strike other roadside objects or cause a more serious crash resulting in injuries. To my knowledge, a Tesla service center or independent facility has not reproduced or confirmed the suspected malfunction. I request that NHTSA investigate and that Tesla preserve and examine available vehicle telemetry, event logs, fsd status, vehicle speed, braking inputs, and driver-intervention data from the incident. Tesla insurance reviewed the collision and determined me at fault. I disputed that determination and requested reconsideration. However, the insurance decision does not establish whether the fsd system malfunctioned. I did not receive a warning lamp or message alerting me in advance that the vehicle would not slow sufficiently for the curve. The problem became apparent as I approached and entered the ramp. I request investigation into whether this represents a safety defect affecting Tesla vehicles equipped with fsd and whether corrective action is necessary. I can provide additional incident information and make the vehicle available for inspection upon request, subject to availability. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

[xxx] [xxx] [xxx] [xxx] [xxx] [xxx] [xxx] email [xxx] national highway traffic safety administration office of defects investigation [xxx] [xxx] safety concern – Tesla structural battery pack design dear NHTSA, I am writing to raise a serious safety and durability concern regarding Tesla’s structural battery pack design, in which the high-voltage battery is glued into the vehicle’s body and used as a load-bearing structural member. My primary concerns are as follows: see atrached pdf fe information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

I am reporting this history because four windshield failures across two relatively new Tesla vehicles raises concern that there may be a recurring issue involving windshield durability, installation, fitment, glass stress, vehicle-body interaction, or another vehicle-related factor. I am also concerned about the following distances maintained by Tesla's automated driving and adaptive-cruise systems. In my experience, the vehicle frequently follows other vehicles more closely than I would choose when driving manually. While the vehicle may calculate that the distance is adequate for braking, closer following distances may increase windshield exposure to stones and roadway debris thrown from vehicles ahead. I cannot establish that automated following distance caused these windshield failures, and I am not presenting that as a proven cause. I am reporting it as one possible contributing factor that may warrant investigation along with windshield design, glass specification, installation, fitment, and structural stress. Because the windshield is an important visibility and structural safety component, I believe the repeated cracking history warrants documentation and review for a possible pattern involving Tesla vehicles. For the current August 17, 2026 incident, I have asked Tesla to inspect and document the apparent origin of the crack before replacing the windshield, including whether there is an identifiable external impact point or evidence of an edge-, fitment-, or stress-related crack. I am submitting this complaint so that NHTSA has a record of the repeated windshield failures and can determine whether similar complaints indicate a broader safety-related defect or trend.

I was operating my Tesla using full self-driving (supervised) when the vehicle approached an active school zone with flashing warning lights and a posted school-zone speed limit of 35 mph. Fsd did not appropriately respond to the active school zone or reduce the vehicle's speed to the posted 35 mph limit, requiring me to disengage fsd and manually slow the vehicle. The incident was captured on the Tesla dashcam. The recording shows fsd active while approaching the school zone. At approximately 14 seconds into the recording, the vehicle was traveling approximately 52 mph with "self-driving" displayed while the flashing school-zone warning and school pavement markings were visible ahead. The posted school-zone speed limit is 35 mph when the warning lights are flashing. Because fsd was not slowing the vehicle appropriately, I intervened and disengaged fsd. Immediately following my intervention, vehicle speed decreased from approximately 49 mph to 39 mph, 31 mph, and approximately 29 mph as I manually slowed the vehicle. This was the second time I experienced fsd failing to appropriately respond to this same active school zone. After this occurrence, I saved the dashcam recording and submitted a bug report through the vehicle. There were no warning messages indicating that fsd could not recognize or respond to the school zone. My safety concern is that fsd may proceed into an active school zone substantially above the posted school-zone speed limit unless the driver recognizes the failure and intervenes. The original dashcam recording is available and documents the vehicle speed, fsd status, active flashing school-zone warning, posted speed limit, and timing of my intervention.

My car locked itself with the phone key and the key card sitting in the car. My baby was trapped in the back seat. Eventually, I was able to get a hold of my husband and he was able to unlock the car from the app. I was talking to 911 when he saw my messages and unlocked the car. I think poor cell reception may have been the cause.

On August 3, 2026, my Tesla Model Y was traveling at approximately 50 mph with Tesla full self-driving (fsd) engaged. At approximately 4:12:47 pm cdt, fsd became unavailable and then became available again. At 4:12:51. 628 pm cdt, fsd was recorded as active_fsd again. Approximately 2. 36 seconds after fsd was re-engaged, at 4:12:53. 987 pm cdt, the vehicle's steering began a sudden and rapid rightward movement. I did not turn the steering wheel or intentionally provide a rightward steering input that initiated this maneuver. The recorded steering angle increased rapidly from approximately +11. 4° to +20. 7°, +33. 3°, +83. 3°, +137. 9°, +154. 7°, and ultimately approximately +282° within about 1. 6 seconds. Importantly, fsd was still recorded as active_fsd when the steering movement began. Fsd changed to unavailable at approximately 4:12:54. 364 pm cdt, about 0. 38 seconds after the steering movement had already started. The steering continued to escalate after fsd became unavailable. The vehicle subsequently experienced severe lateral acceleration of approximately 0. 96 g, and crash detection activated at approximately 4:12:55. 710 pm cdt. The accelerator was recorded at 0% during the developing steering event and increased only after crash detection. Hard braking and abs activation occurred afterward. I do not have Tesla dashcam footage, but I have retained Tesla's vehicle telemetry export containing fsd state, steering, steering-torque, accelerator, braking, vehicle-speed, stability-control, and crash-event data. I am concerned that Tesla fsd may have initiated or contributed to the unexpected steering maneuver that resulted in the collision. I am certain that I did not initiate the sudden rightward steering maneuver. I request that NHTSA investigate whether this represents a potential safety defect or unexpected fsd behavior, particularly the sequence of fsd re-engagement followed approximately 2. 36 seconds later by the unexpected steering event while fsd was still active_fsd.

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.

On July 31, 2026, at approximately 12:55 pm, my 2026 Tesla Model Y experienced a severe safety defect while operating in full self-driving (supervised) mode. The vehicle completely failed to detect, slow down for, or stop at a clearly visible and unobstructed stop sign at an intersection. The vehicle attempted to proceed through the intersection without yielding. I was fully attentive with my hands on the wheel and had to instantly apply heavy manual braking and steering intervention to prevent a collision with an oncoming vehicle that had the right of way. This failure of the automated driving system to recognize fundamental traffic control devices constitutes an immediate and severe collision hazard.

I was operating my Tesla using full self-driving (supervised) from my home to a coffee shop. The vehicle completed the entire drive under fsd without any manual intervention. After arriving at the destination, fsd automatically entered the parking lot, selected an available parking space, and initiated the parking maneuver on its own. I did not manually select the parking space or start the parking maneuver. During the automatic parking maneuver, the vehicle failed to detect a fixed square concrete bollard located within the parking space and continued moving until the front bumper made contact with the bollard, causing damage to the vehicle. No collision warning, parking collision warning, or automatic emergency braking occurred before impact. The vehicle remained under fsd control until the collision. The incident occurred in daylight with good visibility. The obstacle was a permanent concrete bollard, not a temporary object or a low parking curb. Dashcam footage of the incident has been preserved and has been provided to Tesla insurance. I believe Tesla should review the vehicle telemetry and fsd logs to determine why the system failed to recognize the fixed obstacle during the automated parking maneuver.

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.

Tesla full self driving has no way to limit the speed or lane changes, and even in its standard profile it keeps going 15+ over the limit. Chill mode occasionally goes 10+, and sloth switches between -10 and +5 erratically. It's unsafe to use and there's no way to do anything about it without a manual speed limit, like it used to have.