Owners have filed 582 complaints
about the 2024 Tesla Model Y with NHTSA between 2024 and 2026.
The largest single group is the driver assist & collision avoidance.
Across this model's run it ranks 4 of 7 worst.
The letter says how bad. This says what kind — whether this year drew
an unusual number of complaints, unusually dangerous
ones, or failures that arrived unusually early.
The dashed ring is 50 — the national norm. Further out is worse.
Complaint volume — 28
Against the median year of the Tesla Model Y. 50 means typical for this
model; 100 means roughly double.
Severity — 100
38% of these complaints
involved a crash, fire, injury or death, against a national rate of
9.7%.
Early failure — 100
87% of failures with a mileage on record happened under
36,000 miles, against a national rate of
29%.
NHTSA files every complaint against a named sub-assembly, not just a
system. This is the difference between knowing it was "the engine" and
knowing which part of it — the list to hand a mechanic.
Adaptive Cruise Control
7024.6%
Automatic Emergency Braking
6121.5%
Camera
4716.5%
Warnings
3612.7%
Blind Spot Detection
269.2%
Assist
176.0%
Body
155.3%
Warnings
124.2%
When it fails
Odometer readings owners gave when they filed. About half of all
complaints include one.
Under 1,000 miles
619.4%
1,000 – 9,999 miles
1135.5%
10,000 – 24,999 miles
825.8%
25,000 – 49,999 miles
39.7%
100,000 – 149,999 miles
39.7%
When owners complained
A spike years after the car went on sale usually means a part wearing
out on schedule across the whole fleet — the kind of pattern no single
owner can see from inside their own car.
Feb 2024peak 174Aug 2026
NHTSA investigations into the 2024 Tesla Model Y
An investigation is the step before a recall: the agency has seen enough
complaints to look into a pattern itself. An open one means it thinks
something may be wrong and nothing has been fixed yet.
4
investigations are
still open.
EA26002Opened 18 Mar 2026Still openELECTRICAL SYSTEM:ADAS
FSD Collisions in Reduced Roadway Visibility Conditions
The Office of Defects Investigation (ODI) is opening this Engineering Analysis to evaluate Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) degradation detection system. The focus of this investigation will be to assess the system’s ability, when encountering reduced roadway visibility conditions, to detect degradation and alert the driver with sufficient time to respond. ODI will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications by Tesla to the degradation detection system, including the timing, purpose, and ca...
PE25012Opened 7 Oct 2025Still openELECTRICAL SYSTEM:ADAS
Traffic safety violations while Full Self Driving ("FSD") is engaged
The Office of Defects Investigation (“ODI”) is opening this Preliminary Evaluation (PE) to assess the scope, frequency, and potential safety consequences of FSD executing driving maneuvers that constitute traffic safety violations. This investigation concerns versions of FSD that Tesla has labeled as "FSD (Supervised)" and "FSD (Beta)." Tesla characterizes FSD as an SAE Level 2 partial automation system requiring a fully attentive driver who is engaged in the driving task at all times. Level 2 partial automation systems are designed to support and assist the driver in performing certain aspects...
AQ25002Opened 20 Aug 2025Still openELECTRICAL SYSTEM:ADAS
Compliance with Standing General Order 2021-01 Reporting Requirements
The Office of Defects Investigation (“ODI”) has identified numerous incident reports submitted by Tesla, Inc. (“Tesla”) in response to Standing General Order 2021-01 (the “SGO”), in which the reported crashes occurred several months or more before the dates of the reports. The majority of these reports involved crashes in which the Standing General Order in place at the time required a report to be submitted within one or five days of Tesla receiving notice of the crash. When the reports were submitted, Tesla submitted them in one of two ways. Many of the reports were submitted as part of a si...
The Office of Defects Investigation (ODI) is opening a Recall Query to assess the remedy adequacy of Recall 23V838. On December 12, 2023, Tesla filed a Defect Information Report (Recall 23V838) applicable to all Tesla models produced and equipped with any version of its Autopilot system, which Tesla described as an SAE Level 2 (L2) Advanced Driver Assistance System (ADAS). Autopilot is the simultaneous engagement of Tesla’s Traffic-Aware Cruise Control (TACC) and Autosteer. In describing the safety defect, Tesla’s Defect Information Report (DIR) explained that “the prominence and scope of the...
PE24033Opened 6 Jan 2025Closed 3 Apr 2026ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING
Actually Smart Summon sessions resulting in low-speed impacts.
On January 6, 2025, the Office of Defects Investigations (ODI) opened Preliminary Evaluation 24003 (PE24033) to investigate Actually Smart Summon (Summon) sessions resulting in crashes during active sessions. According to Tesla, Summon is a short-distance SAE Level 2 system, controlled by the user from a cell phone within a certain distance and intended for use in parking lots and on private property. ODI analyzed complaint data provided by Tesla as well as complaints submitted to ODI from consumers to identify Summon incidents resulting in crashes. ODI's analysis indicates that almost all Sum...
PE24031Opened 17 Oct 2024Closed 18 Mar 2026ELECTRICAL SYSTEM:ADAS
FSD Collisions in Reduced Roadway Visibility Conditions
On October 17, 2024, NHTSA’s Office of Defects Investigation (ODI) opened a Preliminary Evaluation (PE24031) of Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) to assess: the ability of the FSD system to detect and respond appropriately to reduced roadway visibility conditions; whether any other FSD crashes had occurred under degraded roadway visibility conditions that are similar in nature to the four SGO-reported crashes identified in the opening document, and if so, the contributing circumstances for each of those crashes; and any updates or modificatio...
PE22002Opened 16 Feb 2022Closed 29 Jun 2026FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL:SOFTWARE:SIGNAGE/SIGNAL RECOGNITION
Unexpected Brake Activation
On February 16, 2022, the Office of Defects Investigation (ODI) opened a Preliminary Evaluation (PE22002) to investigate reports of unexpected deceleration while driving with the adaptive cruise control system engaged in Model Year (MY) 2021 – 2022 Model 3 and Model Y vehicles manufactured by Tesla. The subject systems include Autopilot (all versions), Full Self-Driving (FSD) and Traffic Aware Cruise Control (TACC). These complaints have been colloquially referred to as “phantom braking”. ODI opened PE22002 to determine the scope and severity of the potential problem and to assess any resultin...
Recalls on the 2024 Tesla Model Y
A complaint is one owner's allegation. A recall is the point at which
the manufacturer or a regulator agreed the defect is real and dangerous
enough to fix for free — however old the car is.
United States — NHTSA
25V002000
BACK OVER PREVENTION:SOFTWARE
Tesla, Inc. (Tesla) is recalling certain 2024-2025 Model 3, Model S, 2023-2025 Model X, and Model Y vehicles. The computer circuit board may short, resulting in the loss of the rearview camera image. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 111, "Rear Visibility."
Risk: A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.
24V935000
TIRES:PRESSURE MONITORING AND REGULATING SYSTEMS
Tesla, Inc. (Tesla) is recalling certain 2024 Cybertruck, 2017-2025 Model 3, and 2020-2025 Model Y vehicles. The tire pressure monitoring system (TPMS) warning light may not remain illuminated between drive cycles, failing to warn the driver of low tire pressure. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard number 138, "Tire Pressure Monitoring Systems."
Risk: Driving with improperly inflated tires increases the risk of a crash.
24V886000
SEATS:FRONT ASSEMBLY:RECLINER
Tesla, Inc. (Tesla) is recalling certain 2024 Model Y vehicles. The weld attaching the seat recliner mechanism to the front seat backs may fail.
Risk: The seat back frame may not properly restrain the occupant during a crash, increasing the risk of injury.
24V554000
LATCHES/LOCKS/LINKAGES:HOOD:LATCH
Tesla, Inc. (Tesla) is recalling certain 2021-2024 Model 3, Model S, Model X, and 2020-2024 Model Y vehicles. The hood latch assembly may fail to detect an unlatched hood condition after the hood has been opened.
Risk: An unlatched hood can fully open, obstructing the driver's view and increasing the risk of a crash.
24V051000
ELECTRICAL SYSTEM: INSTRUMENT CLUSTER/PANEL
Tesla, Inc. (Tesla) is recalling certain 2012-2023 Model S, 2016-2024 Model X, 2017-2023 Model 3, 2019-2024 Model Y, and 2024 Cybertruck vehicles. An incorrect font size is displayed on the instrument panel for the Brake, Park, and Antilock Brake System (ABS) warning lights. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard number 105, "Hydraulic and Electric Brake Systems" and 135, "Light Vehicle Brake Systems."
Risk: Warning lights with a smaller font size can make critical safety information on the instrument panel difficult to read, increasing the risk of a crash.
Canada — Transport Canada
Canada runs its own recall programme, and its campaigns do not
always mirror the American ones.
Recall 202500224,733 units in Canada
Visual System
Issue: On certain vehicles, a software problem could cause the computer circuit board to short circuit. If this happens, the rearview camera image may not display. Canadian regulations require the rearview image to display when the transmission is shifted into reverse gear. Safety Risk: A rearview camera image that doesn't display could reduce a driver's ability to see behind the vehicle while backing up. This could increase the risk of a crash. Corrective Actions: Tesla has released an over-the-air software update to fix this problem. Tesla will notify owners by email. Tesla will also identify vehicles in which the computer circuit board experienced a short circuit, or damage that could lead to a short circuit, prior to the release of software versions 2024.44.25.3, 2024.45.25.6 or a later release. If your vehicle is identified, you will be advised to contact Tesla Service to replace the car computer.
Recall 2024427179,752 units in Canada
Electrical
Issue: On certain vehicles, the hood latch assembly could fail and cause the unlatched hood warning not to display on the instrument panel. As a result, you may not be aware that the hood isn't latched properly. If this happens, the hood could open suddenly while driving. Safety Risk: A hood that opens suddenly while driving can block the driver's view and increase the risk of a crash. Corrective Actions: Tesla will notify affected owners by email. Tesla has released an over-the-air software update to fix this issue. There is no further action required if your vehicle has software release 2024.20.3 or a later release.
Recall 2024283109,791 units in Canada
Lights And Instruments
Issue: A previous over-the-air (OTA) software update could cause the vehicle not to display the correct visual warning indicators when there are problems with the brake system or when the parking brake is applied. As a result, the BRAKE, PARK, and antilock brake system (ABS) visual indicators would display as text instead of symbols. Safety Risk: While there is a low risk to safety, Canadian regulations require visual warnings to use common symbols, instead of words, to avoid driver confusion. Corrective Actions: Tesla will notify affected owners by email. Tesla has released an over-the-air software update to fix this problem. There is no further action required if your vehicle has software release 2024.3.25, 2024.14.5, or a release later than 2024.14.5.
Reports where the owner recorded a crash, a fire, an injury or a death.
Livingston, NJCrash1 injured
VEHICLE SPEED CONTROL
While exiting a drive-thru, I pressed the accelerator and the vehicle unexpectedly accelerated at a high rate of speed on its own. I attempted to brake, but the brakes did not respond. The vehicle struck a concrete median. Police report on file: East Hanover Township PD, Case #2026-12503.
NHTSA complaint #11758962 — an unverified report by a vehicle owner.
Livingston, NJCrash1 injured
SERVICE BRAKES
While exiting a drive-thru, I pressed the accelerator and the vehicle unexpectedly accelerated at a high rate of speed on its own. I attempted to brake, but the brakes did not respond. The vehicle struck a concrete median. Police report on file: East Hanover Township PD, Case #2026-12503.
NHTSA complaint #11758962 — an unverified report by a vehicle owner.
Los Angeles, CACrash
UNKNOWN OR OTHER
During a software update, the vehicle was parked and no key was present inside the car. The car went into neutral and forward through my gate onto oncoming traffic. The car hit a parked car and then came to a stop. The software update proceeded and I was unable to move the car until it finished.
NHTSA complaint #11757481 — an unverified report by a vehicle owner.
Washington, UTCrash
VEHICLE SPEED CONTROL
I was using the Tesla FSD in stop and go traffic. At the moment I was moving with traffic at about 30 mph and then traffic started slowing down. The vehicle in front of me came to a complete stop. The FSD on my car started slowing down, but not fast enough. It rear-ended the vehicle at about 18 mph.
NHTSA complaint #11756721 — an unverified report by a vehicle owner.
Washington, UTCrash
FORWARD COLLISION AVOIDANCE: WARNINGS
I was using the Tesla FSD in stop and go traffic. At the moment I was moving with traffic at about 30 mph and then traffic started slowing down. The vehicle in front of me came to a complete stop. The FSD on my car started slowing down, but not fast enough. It rear-ended the vehicle at about 18 mph.
NHTSA complaint #11756721 — an unverified report by a vehicle owner.
at 19,891 milesClarksvile, MDCrash
ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING
The contact owns a 2024 Tesla Model Y. The contact stated that while driving at an undisclosed speed on the I-95 N to 175 W exit ramp, while approaching a traffic light in slow-moving traffic with the self-driving feature engaged, the vehicle failed to slow down as expected. To avoid a crash with the vehicle ahead, the contact veered to the right, leaving the roadway and traveling onto a slope and into the grass, where the vehicle struck a tree branch. There were no warning lights illuminated. A Police report was filed. There were no reported injuries or air bag deployment. The insurance company was notified of the issue. The local dealer was not contacted. The vehicle was not diagnosed or repaired. The manufacturer was notified of the issue, and a case was opened. The failure mileage was approximately 19,891.
NHTSA complaint #11753327 — an unverified report by a vehicle owner.
The most recent complaints
In the owners' own words, exactly as filed with NHTSA.
Livingston, NJCrash1 injured
VEHICLE SPEED CONTROL
While exiting a drive-thru, I pressed the accelerator and the vehicle unexpectedly accelerated at a high rate of speed on its own. I attempted to brake, but the brakes did not respond. The vehicle struck a concrete median. Police report on file: East Hanover Township PD, Case #2026-12503.
NHTSA complaint #11758962 — an unverified report by a vehicle owner.
Livingston, NJCrash1 injured
SERVICE BRAKES
While exiting a drive-thru, I pressed the accelerator and the vehicle unexpectedly accelerated at a high rate of speed on its own. I attempted to brake, but the brakes did not respond. The vehicle struck a concrete median. Police report on file: East Hanover Township PD, Case #2026-12503.
NHTSA complaint #11758962 — an unverified report by a vehicle owner.
Los Angeles, CACrash
UNKNOWN OR OTHER
During a software update, the vehicle was parked and no key was present inside the car. The car went into neutral and forward through my gate onto oncoming traffic. The car hit a parked car and then came to a stop. The software update proceeded and I was unable to move the car until it finished.
NHTSA complaint #11757481 — an unverified report by a vehicle owner.
Washington, UTCrash
VEHICLE SPEED CONTROL
I was using the Tesla FSD in stop and go traffic. At the moment I was moving with traffic at about 30 mph and then traffic started slowing down. The vehicle in front of me came to a complete stop. The FSD on my car started slowing down, but not fast enough. It rear-ended the vehicle at about 18 mph.
NHTSA complaint #11756721 — an unverified report by a vehicle owner.
Washington, UTCrash
FORWARD COLLISION AVOIDANCE: WARNINGS
I was using the Tesla FSD in stop and go traffic. At the moment I was moving with traffic at about 30 mph and then traffic started slowing down. The vehicle in front of me came to a complete stop. The FSD on my car started slowing down, but not fast enough. It rear-ended the vehicle at about 18 mph.
NHTSA complaint #11756721 — an unverified report by a vehicle owner.
Sanford, FL
UNKNOWN OR OTHER
Plastic trim around window switches on driver side door panel bubbled and popped. Tesla refused to warranty due to “wear and tear” when vehicle was purchased brand new 1.5 year ago.
NHTSA complaint #11756509 — an unverified report by a vehicle owner.
Palatine, IL
STEERING
Car making excessive noise, service department refuses to address at Tesla even though various cases of the same issue are easily available online. Issue is with half shaft lubrication being dried but Tesla is trying to charge and claiming that the part hasn’t failed. But to me a part failing due to lack of lubrication can lead to hazard road conditions. I don’t want to put my kids safety in harm but Tesla tells me that no lubrication will not result in part failure
NHTSA complaint #11755534 — an unverified report by a vehicle owner.
Brooklyn, NY
SUSPENSION
• What the issue is: Intermittent suspension noise/clunking that suggests a possible failing component. • Why it’s a safety concern: Potential suspension failure could cause loss of control. • What Tesla did: Tesla refused warranty service related to a safety issue involving the suspension because they said they could not hear the noise, despite repeated reports. I asked them to look at the suspension anyway and they refused my warranty service stating that since they could not hear anything they would not inspect and cancelled my appointment. • When it happens: speeds, bumps, turning, acceleration, etc. • Frequency: intermittent, constant, worsening. • Mileage: approximately 44000. • Weather/road conditions: any conditions • Whether the vehicle has been repaired or inspected: Tesla refused to inspect my vehicle under warranty for this safety related complaint and said if they can't hear a noise they won't look at it.
NHTSA complaint #11753674 — an unverified report by a vehicle owner.
at 19,891 milesClarksvile, MDCrash
ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING
The contact owns a 2024 Tesla Model Y. The contact stated that while driving at an undisclosed speed on the I-95 N to 175 W exit ramp, while approaching a traffic light in slow-moving traffic with the self-driving feature engaged, the vehicle failed to slow down as expected. To avoid a crash with the vehicle ahead, the contact veered to the right, leaving the roadway and traveling onto a slope and into the grass, where the vehicle struck a tree branch. There were no warning lights illuminated. A Police report was filed. There were no reported injuries or air bag deployment. The insurance company was notified of the issue. The local dealer was not contacted. The vehicle was not diagnosed or repaired. The manufacturer was notified of the issue, and a case was opened. The failure mileage was approximately 19,891.
NHTSA complaint #11753327 — an unverified report by a vehicle owner.
Chantilly, VACrash
AIR BAGS
At I-66 East and 495 Exit in Fairfax/Vienna, another car hit my Tesla car from the side at around 40-50 MPH. My car driver side had a heavy impact - Door scratched badly, rear window broke, rear tail lamp broke, rear tire got damaged, components on top of the front tire came off. Even the car was hit with this heavy force and had heavy damage, Airbags never deployed. Luckily THe driver didn't have any injuries as she was wearing a seat belt. How come the airbags never popped with this heavy impact accident? THe car that hit our car, didn't have as much damage as ours but their airbags deployed. Is this a defect with Tesla airbags?
NHTSA complaint #11752860 — an unverified report by a vehicle owner.
Carpentersville, ILCrash1 injured
STEERING
On June 7, 2026, I was driving westbound on I-290 in the leftmost lane in a 2024 Tesla Model Y. I recall FSD (Supervised) was engaged and making a lane change into the left lane. Instead of settling in the lane, the vehicle continued left and struck the divider/median. I braked. The vehicle then bounced back and moved right toward a large truck and collided. I did not receive a takeover warning before the event. The front bumper came off and the vehicle became inoperable. A fire truck traveling behind me blocked traffic after the crash. Tesla event data records a Crash Algorithm Wake-Up at about 9:49 a.m. Central and includes speed, steering, braking, acceleration, ABS, lane-assist, and cruise-control signals. I reported the safety concern to Tesla and asked for review of the FSD/software issue and data, but I have not received written findings. I do not have an expert determination that FSD caused the crash. I am asking NHTSA to review the incident and data for a possible driver-assistance, steering, or lane-control safety defect.
NHTSA complaint #11752838 — an unverified report by a vehicle owner.
Carpentersville, ILCrash1 injured
UNKNOWN OR OTHER
On June 7, 2026, I was driving westbound on I-290 in the leftmost lane in a 2024 Tesla Model Y. I recall FSD (Supervised) was engaged and making a lane change into the left lane. Instead of settling in the lane, the vehicle continued left and struck the divider/median. I braked. The vehicle then bounced back and moved right toward a large truck and collided. I did not receive a takeover warning before the event. The front bumper came off and the vehicle became inoperable. A fire truck traveling behind me blocked traffic after the crash. Tesla event data records a Crash Algorithm Wake-Up at about 9:49 a.m. Central and includes speed, steering, braking, acceleration, ABS, lane-assist, and cruise-control signals. I reported the safety concern to Tesla and asked for review of the FSD/software issue and data, but I have not received written findings. I do not have an expert determination that FSD caused the crash. I am asking NHTSA to review the incident and data for a possible driver-assistance, steering, or lane-control safety defect.
NHTSA complaint #11752838 — an unverified report by a vehicle owner.
Carpentersville, ILCrash
UNKNOWN OR OTHER
On August 25, 2025, I was in a crowded Trader Joe's parking lot using the vehicle's FSD parking feature. The vehicle was moving backward into a parking position. A stationary vehicle was in the area. Instead of detecting the other vehicle and stopping, the Tesla kept backing up and made contact with the stationary vehicle. The other vehicle was not moving, and there was enough room for the Tesla to park without contact. I do not remember the exact positioning or direction because of the time that has passed. I did not receive a warning that prevented the contact. I reported to Tesla that the vehicle appeared not to detect the stationary vehicle, but I did not receive an inspection result or written technical finding. I do not have an expert determination of the cause. I am asking NHTSA to review this as a possible FSD parking, parking-collision-warning, or automatic-emergency-braking safety defect.
NHTSA complaint #11752840 — an unverified report by a vehicle owner.
Carpentersville, ILCrash1 injured
LANE DEPARTURE: ASSIST
On June 7, 2026, I was driving westbound on I-290 in the leftmost lane in a 2024 Tesla Model Y. I recall FSD (Supervised) was engaged and making a lane change into the left lane. Instead of settling in the lane, the vehicle continued left and struck the divider/median. I braked. The vehicle then bounced back and moved right toward a large truck and collided. I did not receive a takeover warning before the event. The front bumper came off and the vehicle became inoperable. A fire truck traveling behind me blocked traffic after the crash. Tesla event data records a Crash Algorithm Wake-Up at about 9:49 a.m. Central and includes speed, steering, braking, acceleration, ABS, lane-assist, and cruise-control signals. I reported the safety concern to Tesla and asked for review of the FSD/software issue and data, but I have not received written findings. I do not have an expert determination that FSD caused the crash. I am asking NHTSA to review the incident and data for a possible driver-assistance, steering, or lane-control safety defect.
NHTSA complaint #11752838 — an unverified report by a vehicle owner.
On August 25, 2025, I was in a crowded Trader Joe's parking lot using the vehicle's FSD parking feature. The vehicle was moving backward into a parking position. A stationary vehicle was in the area. Instead of detecting the other vehicle and stopping, the Tesla kept backing up and made contact with the stationary vehicle. The other vehicle was not moving, and there was enough room for the Tesla to park without contact. I do not remember the exact positioning or direction because of the time that has passed. I did not receive a warning that prevented the contact. I reported to Tesla that the vehicle appeared not to detect the stationary vehicle, but I did not receive an inspection result or written technical finding. I do not have an expert determination of the cause. I am asking NHTSA to review this as a possible FSD parking, parking-collision-warning, or automatic-emergency-braking safety defect.
NHTSA complaint #11752840 — an unverified report by a vehicle owner.
Carpentersville, ILCrash
BACK OVER PREVENTION: WARNINGS
On August 25, 2025, I was in a crowded Trader Joe's parking lot using the vehicle's FSD parking feature. The vehicle was moving backward into a parking position. A stationary vehicle was in the area. Instead of detecting the other vehicle and stopping, the Tesla kept backing up and made contact with the stationary vehicle. The other vehicle was not moving, and there was enough room for the Tesla to park without contact. I do not remember the exact positioning or direction because of the time that has passed. I did not receive a warning that prevented the contact. I reported to Tesla that the vehicle appeared not to detect the stationary vehicle, but I did not receive an inspection result or written technical finding. I do not have an expert determination of the cause. I am asking NHTSA to review this as a possible FSD parking, parking-collision-warning, or automatic-emergency-braking safety defect.
NHTSA complaint #11752840 — an unverified report by a vehicle owner.
Sugar Land, TX
STRUCTURE:BODY
While driving through normal rain with ordinary standing water on the roadway (NOT flood conditions), the rear bumper fascia detached from my Tesla Model Y. There was no impact, no collision, and no debris strike - there are no impact marks or scratches on the bumper. The fascia was pulled off by water drag, tearing a welded body mount bracket from the vehicle structure and damaging the underbody shield. This is a road safety hazard: a detached bumper fascia can drag on the roadway, separate completely, and become a large road obstacle for vehicles behind me. Tesla documented this exact failure mode in Service Bulletin SB-20-12-003 (rear fascia detachment when driving through standing water, with damage to harnesses and body fasteners/mounts), yet the defect persists in Model Y vehicles. Notably, another Tesla directly next to mine suffered the identical bumper detachment in the same rainfall at the same time - two identical failures in identical ordinary weather conditions, indicating a systemic design defect rather than driver error. Tesla Service denied warranty coverage, characterizing normal rain as 'flood water.'
NHTSA complaint #11752663 — an unverified report by a vehicle owner.
Cypress, CACrash
STEERING
On 7/22/2026 between 6pm and 7pm PST, I was driving my Tesla Model Y on I-405 southbound in Orange County, CA, between the Westminster Blvd exit and Exit 73, with Full Self-Driving (Supervised) engaged. The incident occurred at an express lane ingress/egress transition zone where a physical barrier separates the express and general-purpose lanes. While in FSD mode, the vehicle initiated a lane change on its own. During the lane change, the FSD system misjudged the lane boundary and steered the vehicle into the lane divider/barrier. The vehicle struck the divider on the front right side. The failed system is the FSD/automated steering and lane change function. No forward collision warning sounded and no automatic emergency braking activated before impact with the fixed barrier. There were no warning lamps, alerts, or symptoms prior to the failure; the system initiated and executed the lane change without indicating any problem. The impact damaged the front right body panel, front right bumper area, and the right headlight. My safety and the safety of vehicles in adjacent lanes was put at risk, as the collision occurred at roadway speed during an automated maneuver I did not initiate. Had the divider been a vehicle or a pedestrian work zone, the outcome could have been far more severe. All FSD telemetry, camera footage, and vehicle data from the incident should be available from the manufacturer, and I have requested the vehicle data report from Tesla. The vehicle is available for inspection upon request and is being taken to a Tesla-certified collision center for repair. An insurance claim is being filed with my carrier. The vehicle has not yet been inspected by the manufacturer or police.
NHTSA complaint #11752331 — an unverified report by a vehicle owner.
Cypress, CACrash
LANE DEPARTURE: ASSIST
On 7/22/2026 between 6pm and 7pm PST, I was driving my Tesla Model Y on I-405 southbound in Orange County, CA, between the Westminster Blvd exit and Exit 73, with Full Self-Driving (Supervised) engaged. The incident occurred at an express lane ingress/egress transition zone where a physical barrier separates the express and general-purpose lanes. While in FSD mode, the vehicle initiated a lane change on its own. During the lane change, the FSD system misjudged the lane boundary and steered the vehicle into the lane divider/barrier. The vehicle struck the divider on the front right side. The failed system is the FSD/automated steering and lane change function. No forward collision warning sounded and no automatic emergency braking activated before impact with the fixed barrier. There were no warning lamps, alerts, or symptoms prior to the failure; the system initiated and executed the lane change without indicating any problem. The impact damaged the front right body panel, front right bumper area, and the right headlight. My safety and the safety of vehicles in adjacent lanes was put at risk, as the collision occurred at roadway speed during an automated maneuver I did not initiate. Had the divider been a vehicle or a pedestrian work zone, the outcome could have been far more severe. All FSD telemetry, camera footage, and vehicle data from the incident should be available from the manufacturer, and I have requested the vehicle data report from Tesla. The vehicle is available for inspection upon request and is being taken to a Tesla-certified collision center for repair. An insurance claim is being filed with my carrier. The vehicle has not yet been inspected by the manufacturer or police.
NHTSA complaint #11752331 — an unverified report by a vehicle owner.
On 7/22/2026 between 6pm and 7pm PST, I was driving my Tesla Model Y on I-405 southbound in Orange County, CA, between the Westminster Blvd exit and Exit 73, with Full Self-Driving (Supervised) engaged. The incident occurred at an express lane ingress/egress transition zone where a physical barrier separates the express and general-purpose lanes. While in FSD mode, the vehicle initiated a lane change on its own. During the lane change, the FSD system misjudged the lane boundary and steered the vehicle into the lane divider/barrier. The vehicle struck the divider on the front right side. The failed system is the FSD/automated steering and lane change function. No forward collision warning sounded and no automatic emergency braking activated before impact with the fixed barrier. There were no warning lamps, alerts, or symptoms prior to the failure; the system initiated and executed the lane change without indicating any problem. The impact damaged the front right body panel, front right bumper area, and the right headlight. My safety and the safety of vehicles in adjacent lanes was put at risk, as the collision occurred at roadway speed during an automated maneuver I did not initiate. Had the divider been a vehicle or a pedestrian work zone, the outcome could have been far more severe. All FSD telemetry, camera footage, and vehicle data from the incident should be available from the manufacturer, and I have requested the vehicle data report from Tesla. The vehicle is available for inspection upon request and is being taken to a Tesla-certified collision center for repair. An insurance claim is being filed with my carrier. The vehicle has not yet been inspected by the manufacturer or police.
NHTSA complaint #11752331 — an unverified report by a vehicle owner.
Wellesley, MA
POWER TRAIN
SAFETY DEFECT REPORT: Sudden Power Loss & Falsified Records 1. INCIDENT & 5-HR TOWING (XXX): On XXX at ~16:30, while executing a low-speed (<10 mph) left turn in Cambridge, MA, the vehicle had a sudden, total high-voltage failure mid-turn, losing all motive power and power steering without warning or error codes. Photos/videos were taken on-scene confirming ZERO physical impact or undercarriage collision. The dead vehicle stopped directly in the active lane, completely blocking traffic. With zero power, the driver and several helpful bystanders had to use extreme physical effort to manually push the dead car out of the road. AAA arrived at 18:00 but could NOT tow because total power loss completely locked all 4 wheels/brakes (no Tow Mode). AAA dispatched a 2nd specialized flatbed with dollies (arrived 21:00). Driver was stranded on-site for over 5 hours. Car reached Tesla Dedham Service at 22:00. On XXX at 10:00 AM, driver reported the driving power loss in person at Dedham, handed over key, and got a loaner. 2. WRITTEN NOTICE (XXX): On XXX, explicit written notice was sent to Tesla Service Manager Taso, re-confirming the exact mid-driving power loss hazard. 3. TESLA DIAGNOSIS & REPAIRS: Invoice #XXX confirms a severe high-voltage failure: "A hardware overcurrent event caused small high voltage battery brick imbalance and rear inverter failure." Tesla replaced Rear Drive Unit Inverter (3DU) and Pyrotechnic Battery Disconnect (Pyrofuse). 4. FALSIFICATION OF SAFETY ISSUE: Despite 5-hr towing from wheel lock-up, XXX in-person report, and XXX written notice detailing mid-turn power loss, Tesla falsely recorded on invoice: "customer states: vehicle will not charge." This is deliberate falsification and deceptive practice by Tesla to downplay a critical road hazard into a benign charging issue. I request NHTSA to investigate this high-voltage overcurrent/inverter failure pattern and Tesla's practice of altering safe INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11752044 — an unverified report by a vehicle owner.
Wellesley, MA
STEERING
SAFETY DEFECT REPORT: Sudden Power Loss & Falsified Records 1. INCIDENT & 5-HR TOWING (XXX): On XXX at ~16:30, while executing a low-speed (<10 mph) left turn in Cambridge, MA, the vehicle had a sudden, total high-voltage failure mid-turn, losing all motive power and power steering without warning or error codes. Photos/videos were taken on-scene confirming ZERO physical impact or undercarriage collision. The dead vehicle stopped directly in the active lane, completely blocking traffic. With zero power, the driver and several helpful bystanders had to use extreme physical effort to manually push the dead car out of the road. AAA arrived at 18:00 but could NOT tow because total power loss completely locked all 4 wheels/brakes (no Tow Mode). AAA dispatched a 2nd specialized flatbed with dollies (arrived 21:00). Driver was stranded on-site for over 5 hours. Car reached Tesla Dedham Service at 22:00. On XXX at 10:00 AM, driver reported the driving power loss in person at Dedham, handed over key, and got a loaner. 2. WRITTEN NOTICE (XXX): On XXX, explicit written notice was sent to Tesla Service Manager Taso, re-confirming the exact mid-driving power loss hazard. 3. TESLA DIAGNOSIS & REPAIRS: Invoice #XXX confirms a severe high-voltage failure: "A hardware overcurrent event caused small high voltage battery brick imbalance and rear inverter failure." Tesla replaced Rear Drive Unit Inverter (3DU) and Pyrotechnic Battery Disconnect (Pyrofuse). 4. FALSIFICATION OF SAFETY ISSUE: Despite 5-hr towing from wheel lock-up, XXX in-person report, and XXX written notice detailing mid-turn power loss, Tesla falsely recorded on invoice: "customer states: vehicle will not charge." This is deliberate falsification and deceptive practice by Tesla to downplay a critical road hazard into a benign charging issue. I request NHTSA to investigate this high-voltage overcurrent/inverter failure pattern and Tesla's practice of altering safe INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11752044 — an unverified report by a vehicle owner.
Wellesley, MA
ELECTRICAL SYSTEM
SAFETY DEFECT REPORT: Sudden Power Loss & Falsified Records 1. INCIDENT & 5-HR TOWING (XXX): On XXX at ~16:30, while executing a low-speed (<10 mph) left turn in Cambridge, MA, the vehicle had a sudden, total high-voltage failure mid-turn, losing all motive power and power steering without warning or error codes. Photos/videos were taken on-scene confirming ZERO physical impact or undercarriage collision. The dead vehicle stopped directly in the active lane, completely blocking traffic. With zero power, the driver and several helpful bystanders had to use extreme physical effort to manually push the dead car out of the road. AAA arrived at 18:00 but could NOT tow because total power loss completely locked all 4 wheels/brakes (no Tow Mode). AAA dispatched a 2nd specialized flatbed with dollies (arrived 21:00). Driver was stranded on-site for over 5 hours. Car reached Tesla Dedham Service at 22:00. On XXX at 10:00 AM, driver reported the driving power loss in person at Dedham, handed over key, and got a loaner. 2. WRITTEN NOTICE (XXX): On XXX, explicit written notice was sent to Tesla Service Manager Taso, re-confirming the exact mid-driving power loss hazard. 3. TESLA DIAGNOSIS & REPAIRS: Invoice #XXX confirms a severe high-voltage failure: "A hardware overcurrent event caused small high voltage battery brick imbalance and rear inverter failure." Tesla replaced Rear Drive Unit Inverter (3DU) and Pyrotechnic Battery Disconnect (Pyrofuse). 4. FALSIFICATION OF SAFETY ISSUE: Despite 5-hr towing from wheel lock-up, XXX in-person report, and XXX written notice detailing mid-turn power loss, Tesla falsely recorded on invoice: "customer states: vehicle will not charge." This is deliberate falsification and deceptive practice by Tesla to downplay a critical road hazard into a benign charging issue. I request NHTSA to investigate this high-voltage overcurrent/inverter failure pattern and Tesla's practice of altering safe INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11752044 — an unverified report by a vehicle owner.
Matteson, IL
UNKNOWN OR OTHER
This vehicle is hacked along with app. it's unsafe to drive at this point. I have contacted Tesla they are no help. my tesla app is hacked and the vehicle
NHTSA complaint #11751589 — an unverified report by a vehicle owner.
St Pete, FL
SERVICE BRAKES
My car will randomly break while I’m driving straight on a road. It seems to happen when I’m going between 30 and 45 mph. It breaks so hard that if a car behind me was following, they could run into me. Whenever it breaks, I have to put my foot on the accelerator to get the car to go back forward.
NHTSA complaint #11751573 — an unverified report by a vehicle owner.