2026 Tesla Model Y problems

UNKNOWN OR OTHER

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

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

BACK OVER PREVENTION: WARNINGS

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

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

STEERING

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.

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

UNKNOWN OR OTHER

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.

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

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

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.

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

POWER TRAIN

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.

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

VEHICLE SPEED CONTROL

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.

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

ELECTRICAL SYSTEM

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.

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

SERVICE BRAKES

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.

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

FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL

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.

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

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

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.

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

FORWARD COLLISION AVOIDANCE: AUTOMATIC EMERGENCY BRAKING

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.

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

ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING

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.

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

STEERING

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

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

UNKNOWN OR OTHER

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

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