2026 Tesla Model Y complaints

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.

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.

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)

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.

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.

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

The contact owns a 2026 Tesla Model Y. The contact stated that while his wife was pulling into the driveway at an undisclosed speed while using Full Self-Driving mode, the vehicle came to a complete stop and unexpectedly crashed into the garage. The dealer was notified of the failure; however, the vehicle was not diagnosed or repaired. The contact attempted to reach the manufacturer, but was unable to make contact. The failure mileage was approximately 30.

Screen provides alert that "center brake light condition deteceted". Shows up as VCRIGHT_a487. Tesla has said it is a software condition that will be fixed in an update, yet several updates later, the condition persists with no fix in sight. This error has appeared since the time of new vehicle delivery in early May 2026 to the present.

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-r

On August 26, 2026, I sustained a significant injury when the door of my Tesla closed while my thumb was in the door area. The door caught my thumb and forcibly lifted/tore off most of my thumbnail, causing immediate bleeding and leaving the nail bed exposed. I am reporting this because I am concerned about the safety of the vehicle’s door closing mechanism and its ability to prevent this type of injury when a hand or finger is obstructing the door. The force of the closing door was sufficient to cause substantial physical injury rather than a minor pinch. There were no warning messages or alerts before the incident that I was aware of. At this time, I do not know whether the door, sensors, or closing mechanism malfunctioned or whether they were operating as designed. The cause is UNKNOWN and has not yet been confirmed by Tesla or an independent service center. The vehicle and door are available for inspection upon request. I am also reporting the incident to Tesla and requesting that Tesla inspect the door and related components and preserve/review any available vehicle diagnostic or event data associated with the incident. The injury has been photographed and documented. I am concerned that the same door behavior could cause serious injury to another occupant, particularly if a child’s hand or fingers were caught in the door.

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

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.

The front driver-side OEM Hankook tire (size: 235/55R18) on my 2026 Tesla Model Y Standard Range developed a severe 2-inch structural split/crack along the tire shoulder/sidewall under normal daily commuting on paved roads. There was no road hazard or curb impact. This sudden structural failure caused immediate, complete air pressure loss, creating a severe safety risk on the road. The failure was confirmed by an independent local tire repair technician, who inspected the tire and declared it irreparable, forcing an immediate out-of-pocket replacement. No prior warning lights or symptoms appeared before the incident. Photos of the defect, tire size, and DOT code are available upon request.

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 ob

The contact owns a 2026 Tesla Model Y. While the vehicle was parked and attempting to shift into drive(D), the brake pedal was depressed, and the driver attempted to select the gear, but the gear display icon appeared semi-transparent. The driver was able to select the intended gear after several attempts; however, upon depressing the accelerator pedal, the vehicle unintentionally accelerated at a higher speed and struck a tree. The air bags did not deploy. No injuries were reported, and a Police report was not filed. No warning light was illuminated before or after the crash. Full Self-Driving (FSD) mode was not activated during the failure. The vehicle was driven to a collision repair center to repair the damage. The contact notified the manufacturer of the failure and requested assistance retrieving data from the Event Data Recorder (EDR); however, no assistance was provided. The vehicle was not diagnosed or repaired for the unintended acceleration. The failure mileage was approximately 2,000.

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.

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.

[XXX] [XXX] [XXX] [XXX] [XXX] [XXX] [XXX] Email [XXX] National Highway Traffic Safety Administration Office of Defects Investigation [XXX] [XXX] Re: 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)

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-contro

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 th

Screen provides alert that "center brake light condition deteceted". Shows up as VCRIGHT_a487 Tesla said "The condition is characteristic of the current firmware with no current fix at this time". Tesla is looking into this concern as it is affecting multiple vehicles at this time

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.

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.

Tesla was in FSD and had the latest software update installed on 8/6/28 which included the new FSD version released. On 8/7/28 on the way to work that my wife takes every time she goes to work the FSD ran over a large pot hole which it had never done before on the previous FSD version. The car started having rattling of the steering wheel and a rattling noise from over the rear driver wheel area. The next available Tesla service appointment was on 8/27 but we walked in and Tesla offered to do an alignment and found that the driver front and rear rims were bent from the pothole and we had to be pay close to 1800$. Thereafter, the rattling over the rear wheel well is louder but Tesla has not accommodated us with an earlier service appointment and refused to make any accommodations for the FSD update resulting in this damage.

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.

I was driving the car inside the parking garage of the UCLA Medical Plaza in Westwood at around 3:10pm on XXX, looking for an appropriate parking spot. When entering the second basement floor and turning the steering wheel right, to follow the road, the steering wheel was unresponsive and the car felt as if in neutral gear. As the car was on a downward slope, it went straight into the car parked in front. It happened so fast, but it seemed as if the brakes were ineffective. The air bags on the sides were deployed. On the front, the airbag in the steering wheel came out but did not inflate. [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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

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.

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 f

The contact owned a 2026 Tesla Model Y. The contact stated that while her daughter was driving 16 MPH with the self-driving feature activated the vehicle failed to stop at a stop sign. Seconds later the contact's daughter attempted to disengage the self-driving feature and then depressed the brake pedal to stop from entering a right-turn-only minor road stop-controlled intersection. However, the front passenger’s side of the vehicle was struck by another vehicle, before striking another vehicle. The contact stated that the air bags on the passenger’s side of the vehicle deployed. The contact's daughter sustained minor leg injuries. Medical attention was not needed, and the contact was not sure whether occupants of the other vehicle required medical attention. A Police report was filed. The contact stated that the vehicle had not detected the oncoming traffic and that the crash could have been prevented. The vehicle was towed to a tow yard where it was deemed a total loss. The vehicle was not diagnosed or repaired. The manufacturer was notified of the failure. The failure mileage was 13,986.

On [XXX], at approximately [XXX], my 2026 Tesla Model Y (VIN: [XXX], delivered [XXX]) was involved in a rear-end collision while the Full Self-Driving (FSD) system was actively engaged. The dashcam footage clearly shows "Self Driving" displayed in blue on the instrument panel at the time of the incident, with the vehicle traveling at 3 KM/H in Drive (D) mode. What failed: The FSD/ADAS system failed to detect the stopped vehicle ahead and did not apply braking or issue any collision warning prior to impact. Safety risk: The system had full control of the vehicle at the time of the collision. I was not manually operating the vehicle. The failure of the FSD system to respond appropriately caused a rear-end collision. Dealer/service confirmation: Not yet confirmed by dealer. Incident occurred 2 days after vehicle delivery. Inspections: Under review by insurance. Police report pending. Dashcam video evidence preserved. Prior warnings: No warning lamps or alerts were displayed prior to the collision. The FSD system gave no indication of the impending failure. Dashcam footage showing active "Self Driving" status at time of crash is available upon request. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

When using Tesla FSD, the car insists on following the car in front at an unsafe following distance….frequently less than 1 second behind it.

Tesla Full Self Driving, installed version 14.3.6 is still unable to reliably obey speed limits. The driver of the car has no method of controlling Full Self Driving to slow down the car to meeting the new speed limit. The Full Self Driving (FSD) safety system must be disabled to regain speed control. Tesla claim in multiple social media posts that FSD is "significantly" safer than humans, but it will not reliably maintain accurate speed and instead will often attempt to significantly exceed the posted speed limits. XXX driving through [XXX] on Highway XXX heading west, with FSD controlling the car. The posted speed limit is 45, suddenly the car changed speed to 55, then faster. The only recourse is to disengage the FSD safety system to regain sensible speed. I have included one location, but this is a very widespread issue that covers much of [XXX], [XXX], [XXX] and [XXX]. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

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.

The Full Self-Driving (Supervised) software on my 2026 Tesla Model Y repeatedly performs unsafe driving maneuvers requiring manual takeover to avoid collisions. Documented incidents with timestamps since June 3, 2026 include: selecting the incorrect lane and then attempting a route correction against a red light; activating the left turn signal while executing a right turn; attempting to enter a freeway from an incorrect lane; repeatedly missing exits, on-ramps, and turns; and making unnecessary lane changes. In one drive on June 9, the system missed two exits, a freeway on-ramp, a left turn, a right turn, and a U-turn twice within 18 minutes. On July 8, 2026, hours after the vehicle was returned from service with the manufacturer's advised mitigation active, the system repeated the same errors and drove the wheel into a curb, causing wheel damage. My safety and that of other road users was put at risk by incorrect lane positioning, incorrect signaling, and a red light conflict. The manufacturer's service center has inspected the vehicle twice (completed July 8 and July 21, 2026). Both visits were closed with no repair performed. The only action was advising me to disable the Online Routing setting as a temporary workaround, which did not prevent recurrence. The manufacturer stated in writing on July 8 that this is a known software-related matter its engineering teams are actively working to resolve, and a service advisor described it verbally as a firmware issue. However, th

Vehicle: 2024 Tesla Model Y (VIN: [XXX]) Incident Date: [Insert Date] Current Mileage: 4,094 Description: "While operating the vehicle at low speed, the vehicle experienced a sudden, uncommanded acceleration event. Despite immediate and sustained application of the brake pedal, the vehicle failed to decelerate as intended, indicating a critical failure of the braking-override system and/or the drive-by-wire acceleration logic. This represents a catastrophic safety defect that resulted in an uncontrolled trajectory. Furthermore, Tesla Inc. has formally refused to release the Event Data Recorder (EDR) data associated with this VIN and timestamp (Ref: DOT Request #xxx). This refusal obstructs a transparent safety analysis of a known 'Sudden Unintended Acceleration' (SUA) event. I am requesting a formal Office of Defects Investigation (ODI) into this specific hardware/software failure and Tesla’s data-withholding practices regarding safety-critical events." I am a XXX and the threat is to take the loaner car away my only transportation from [XXX] to [XXX] for my XXX. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

On the day after taking delivery of my 2026 Tesla Model Y, FSD reversed into a visible stationary garage pillar while backing into my garage. The vehicle did not stop before impact and stopped only after contacting the pillar, resulting in more than $6,000 in vehicle damage. The following day, while FSD was attempting a left turn at an intersection, the vehicle nearly entered the opposing-traffic lane before making several hesitant steering corrections. I disengaged FSD and completed the turn manually to avoid a potential collision. Both incidents occurred within two days of delivery. Tesla has opened a service case, escalated the matter to its engineering team for review, and I have requested preservation of all available vehicle data. I am submitting this complaint because these incidents raise concerns about the safety of FSD behavior.

Center brake light fails intermittently when outside temperature is hot (115). Tesla is aware of the issue and has no fix. Side brake lights still seem to work when center fails.

My car was parked in a residential neighborhood and when I was driving home on the evening of July 4th I noticed the windshield had a small line in it. The next day during daylight hours I went to inspect it further and concluded that the hood made contact with the windshield on both sides and there were two distinct impact areas that matched perfectly with small paint damage on the hood. I made an appointment with Tesla and waited about two weeks to get in, and they summized that this is not a defective part issue and that a wind so powerful came along, lifted the hood up, overpowered the gas struts, broke the windshield and closed itself perfectly. They denied any responsibility and refused to cover it under their manufacturers warranty. This is Tesla of Wilmington, DE

My tesla model Y was driving on FSD (full self driving) and just did hard full stop brake at a traffic light and brought the car to a complete stop even when the light was green. Both of toddler kids in the back got pulled jolted forward where the seat belt hurt them. This stopping was random was unnecessary as no threat of other cars or the light was present. Luckily no one was behind us or they would have rear ended our car causing a serious accident. This really left my children in shock.

2026 Tesla Model Y (VIN [XXX]) running FSD Supervised v14.2.2.5 / software 2026.14.200 experienced two unintended phantom braking events while FSD was active. Incident 1: XXX, approximately 9:16 AM, XXX southbound off-ramp at [XXX] exit heading [XXX]. Vehicle braked abruptly and without warning at highway approach speed with no obstacle present. Incident 2: XXX, approximately 2:08 PM, [XXX] westbound atXXX northbound on-ramp [XXX]. Same abrupt, unwarned braking with no obstacle present. Tesla service performed diagnostics XXX, at the Delray Beach service center. No hardware fault was found. Vehicle has been unable to receive OTA software updates. A nearly identical vehicle, a 2026 Tesla Model Y in the same household (VIN [XXX]), is currently running software 2026.20.6.11 and FSD v14.3.6, several versions ahead of the affected vehicle. Tesla confirmed the software disparity is due to VIN batch rollout scheduling and cannot be manually accelerated. Tesla regional management and engineering review team have been notified. While children were not in the vehicle at the time of these specific incidents, they are frequent passengers in this vehicle and this braking behavior represents a serious safety concern for our family. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

The contact owns a 2026 Tesla Model Y. The contact stated that while driving approximately 55 MPH with the cruise control engaged the vehicle lost automotive power. No warning lights were illuminated. The failure had occurred on several occasions. The vehicle was not diagnosed or repaired. The manufacturer was notified of the failure and had received similar complaints; however, there was no fix available for the failure. The failure mileage was approximately 100.

Tesla took off from a parking lot and was uncontrollable, went through the grass, crossed the street and construction before hitting the barricades and fell into a sewer as the road ended there. There were 2 passengers in the car and luckily both passengers came unharmed. But FSD needs to be investigated on why this happened.

See attached document for complaint.

The vehicle's Indirect TPMS showed a "Pressure Sensor Fault (may clear next drive)" without issuing any "Low Tire Pressure" alert. On July 20, 2026, while driving, the rear right tire lost pressure and disintegrated over a 10-minute drive. Despite severe tire failure that triggered multiple safety system alerts (Traction Control, Stability Control, Automatic Emergency Braking, and Lane Departure Avoidance disabled), the vehicle software FAILED to issue a critical "Do Not Drive" command or explicit "Flat Tire" warning. Furthermore, the official Tesla App automated response advised that "Most alerts may resolve automatically on your next drive," encouraging continued driving. This total absence of critical emergency alerts and misleading system guidance created an extreme, life-threatening road hazard and resulted in severe tire and wheel destruction.