RoadVitals

2026 Tesla Model 3 Owner Complaints

Reports submitted to NHTSA by owners and drivers, shown in full

Data refreshed

Complaints on fileComplaints are reports submitted to NHTSA by owners and drivers. NHTSA does not verify most reports before publishing them, and a complaint does not establish that a defect exists. Volume is influenced by how many of a vehicle were sold, how long it has been on the road, and how much attention an issue has received.
31
+3 complaints in 30 days
Crash or fire reportedComplaints whose submitter recorded that a crash or a fire occurred. These are the reporter's own answers on the NHTSA form, not verified findings.
10
Filed in the last 12 monthsReports filed with NHTSA in the trailing 365 days. Recent volume reflects attention and vehicle age as much as anything else.
31
Reports on file since Jan 16, 2026

What this page shows

Our database holds 31 NHTSA owner-reported complaints for the 2026 Tesla Model 3. Each one is a report filed by an owner or driver and published by NHTSA without most of them being verified. A complaint is not a confirmed defect, not a recall and not a manufacturer bulletin. Narratives are shown exactly as filed.

Complaints are reports submitted by owners and drivers to NHTSA. They are not verified and do not establish that a defect exists.

Complaints, most recent first

Showing 1–25 of 31 · page 1 of 2

ElectricalVisibility
Filed Nov 4, 2026

The contact owns a 2026 Tesla Model 3. The contact stated that while driving at 25 MPH in Full Self-Driving mode, an animal entered the roadway, causing the vehicle to hesitate before the autonomous braking system independently engaged with severe abnormal jerking. The contact stated that the bumper detached; however, the vehicle remained drivable. The dealer was contacted. The vehicle was taken to the dealer, where the contact was informed that paperwork authorization was required prior to diagnostic testing. The contact stated that while driving at night, the auto-dimming rearview and side mirrors failed to dim properly, requiring the driver to wear sunglasses at night. The manufacturer was notified of the failures and informed the contact that diagnostic testing required an out-of-pocket fee. The failure mileage was approximately 57,525.

NHTSA ID
11775622
Incident
Oct 15, 2026
Mileage
57,525 mi
Driver assistance
Filed Oct 27, 2026
Crash reported

• forward collision warning and automatic emergency breaking failed to work and are still currently an ongoing problem and not functioning. They are and have always Been enabled and can be inspected upon request. • my safety and those in my car and around me put at risk, by the system and software not functioning as intended and providing extra alertness and reaction to avoid collision. •the earliest service date I could get from Tesla is Nov 11. I have requested they preserve all data from dates Oct 20-27 2026 •no, my car has not been inspected yet. I have taken, Videos and have saved in car camera footage to show the ongoing defect. •no warnings lights or alerts prior to the incident. The problem first became apparent and clear Oct 26, 2026. I had FSD subscription that ended Oct 24, 2026 and the system warnings worked just fine during that time even while driving manually.

NHTSA ID
11774044
Incident
Oct 26, 2026
Filed Oct 15, 2026

On [XXX], the owner of a 2026 Tesla Model 3, left the garage of her house in the Tesla, and engaged the self-driving as the driver has done dozens of time in the past. The car proceeded down the driveway, as it has always done in the past. However, in an instant, before the driver had time to react, the car went straight where the driveway curved, and the car hit a tree. The video from the Tesla cameras was saved and confirms that the car was in self driving mode, there was no driver intervention causing the accident, and the driver did not have time to react and prevent the accident. This accident was due to a failure of the Tesla self-driving. The encrypted dashcam video was copied from the USB drive named [XXX], from the folder [XXX], and then accessed by logging into [XXX] and dragging and dropping the video file into the dashcam app. That was saved to our PC as [XXX}. Since the saved video did not show the telemetry data, the video was loaded into [XXX] and saved with the telemetry information visible. Another video was saved capturing the whole ExportDash.cam interface. That has bars showing where the car was actively steering, braking, or applying acceleration (“gas pedal”). This shows that the car was actively steering a second before the collision, but then stopped. There was no time for the driver to react to the car's failure to properly steer. The video showing the car in self-driving mode and failing to navigate a turn on the driveway can be accessed at this youtube link: [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID
11771457
Incident
Oct 13, 2026
BrakesSteering
Filed Oct 6, 2026

The contact owns a 2026 Tesla Model 3. The contact stated that while driving 65 MPH, the steering wheel independently turned to the left and the right. The brake pedal was depressed; however, the vehicle failed to stop as intended. The contact stated that the vehicle was shaking and uncontrollable. The contact depressed the brake pedal down, unbuckled, the seat belt and opened the door and the vehicle came to a stop. The Police was contacted and arrived on the scene. The Police removed the vehicle from the roadway onto the shoulder of the road. The contact was advised to tow the vehicle to the dealer. The vehicle was towed to the dealer, but the diagnostic test report was not provided to the contact. The contact was informed that the information was reported to the engineers. The contact was advised to contact the NHTSA Hotline to report the failure. The failure mileage was approximately 450.

NHTSA ID
11769327
Incident
Oct 2, 2026
Mileage
450 mi
Steering
Filed Oct 5, 2026

Car was in self-driving and struck a piece of concrete. The car was in hands free and was being monitored by me, the driver. This obstruction was in the left side of the lane, about 2" tall, a foot wide and 6" across. I thought the car would see it and miss it but I was wrong, it clipped the concrete, punctured the tires side wall and damaged the tire rim. Tesls'a position was that I shouldn't have trusted the car abilities to avoid the obstruction. This is a basic for collision avoidance, and this system should not be allowed to run in self-drive without hands on the wheel unless the car is capable of avoidance of obstructions large enough to disable the car. This car is dangerous if it can operate at freeway speeds, hands free, and not have the ability to avoid obstructions that could cause it to be out of control.

NHTSA ID
11769065
Incident
Oct 1, 2026
Electrical
Filed Sep 30, 2026

The contact owns a 2026 Tesla Model 3. The contact stated that while driving 35 MPH with the Autonomous Self-Driving feature enabled, the vehicle was driving in the left-turn lane and jerked over into the oncoming traffic. The failure mileage was approximately 9,999.

NHTSA ID
11768125
Incident
Sep 30, 2026
Mileage
9,999 mi
Filed Sep 26, 2026

I had FSD (Full Self Driving) (Supervised) enabled. The navigation map and turn instructions (which appear on the right side of the touchscreen) indicated that my car was to make a left turn at the upcoming intersection. After a full stop (at the Stop sign), my car crept out into the intersection, preparing to make an unprotected left turn (UPL) onto a major street (2 lanes of traffic in each direction). My car stopped (creeping out) when FSD “realized” that it was not yet safe to make the turn. My car, however had crept out far enough so that other vehicles coming from my left (in the right lane) had to swerve left to avoid hitting my car. There was another car behind my car so I could not “manually” back up (taking over from FSD) to remove the front of my car from the path of vehicles coming from my left. (If just one of the drivers of those vehicles coming from my left had been distracted, a likely collision with the front of my car could have occurred!) Eventually, there was a sufficient gap that I could (manually) make a right turn instead. Since this incident, I have had to preview the navigation map for every trip (before enabling FSD) and be prepared to route around any UPLs. After driving this car over 6500 miles (98 % on FSD), I have found FSD to be very safe overall! My only notable “risk of collision” event was the above-described UPL attempt! I have contacted Tesla Customer Service (via phone calls and online) on several occasions to report this hazard, but nothing has been done; (although on a live phone call, the representative acknowledged that others had also voiced my concern!) During a chat with Tesla’s “Grok” chatbot, Grok stated that a ‘Prefer Protected Turns’ option would be a low complexity addition that could coexist with continued UPL improvement”. Given this information, I think Tesla is being negligent by not adding the “Prefer Protected Turns” option to the vehicle user interface.

NHTSA ID
11767200
Incident
Sep 8, 2026
Filed Sep 22, 2026
Crash reported

On Sept 22 2026at approximately 10:26 AM, my Tesla vehicle was involved in a low-speed, 5 -10 mph rear-end collision while the Full Self-Driving (FSD) Supervised automation system was engaged. The vehicle failed to initiate a timely braking sequence for a lead vehicle, resulting in an impact. There was a sudden accleration right before the hit along with a sudden braking. Critical Safety Failures & Discrepancies: 1. Unwarned System Degradation: Following the incident, Tesla Service technicians reviewed my vehicle diagnostics and explicitly stated that internal logs flagged the FSD system performance as degraded or "suspect" since the beginning of September 2026. However, prior to the crash, the vehicle provided zero driver-facing warning messages, dashboard alerts, or mobile application notifications indicating that the automated safety systems were compromised or operating with a defect. 2. Telemetry Log Contradiction: Tesla's initial internal review claims that the vehicle's telemetry indicates an accelerator pedal override by the driver. I explicitly state that my foot was not on the accelerator pedal and no such override was physically made. There is an active sensor tracking or system logging discrepancy regarding driver inputs during this FSD failure. Evidence Maintained: I have preserved the complete, 4-angle synchronized TeslaCam dashcam footage of the incident on my computer as visual proof of the vehicle's un-accelerated 5 mph forward creep. Furthermore, I have submitted an official Data Privacy Request to Tesla to force the extraction of the raw, unredacted vehicle telemetry logs (DI_accelPedalPos) to legally dispute their pedal position claims. I am filing this report to assist NHTSA's active investigations into Tesla Autopilot/FSD traffic safety violations, specifically concerning automated braking failures and inaccurate driver-override telemetry classification.

NHTSA ID
11766182
Incident
Sep 22, 2026
Visibility
Filed Sep 18, 2026

The front windshield camera for FSD gets hazed and obstructs the front camera. Tesla say it’s from the gases that come from the interior from the vehicle being hot temperatures. My problem why did they not design the cameras like they did in the side puller protecting it from the interior gases. Now Tesla says they’ll clean it for 65.00. I just bought the car in March

NHTSA ID
11765379
Incident
Sep 11, 2026
Steering
Filed Sep 18, 2026

I was using the self driving feature and all of a sudden the steering wheel went haywire and was spinning. the car was swerving very aggressively in between lanes. putting my foot on the brake and hands on the wheel did not do anything.

NHTSA ID
11765239
Incident
Sep 18, 2026
Driver assistance
Filed Sep 12, 2026

When using Tesla's Full Self Driving (supervised) speed control is erratic and not subject to the driver's control, such as it would be when using adaptive cruise control. As a result, the available speed modes (sloth, chill, standard, hurry and Mad Max) can cause the vehicle to dangerously exceed speed limits and at times to drive well below the posted speed limit, causing confusion and frustration to following drivers. There is no reason why the software cannot be changed to a safer method that would permit the driver to select the speed at which the car will travel, i.e. the speed limit, similar to adaptive cruise control found in most modern vehicles. When the operator of a vehicle is not in charge of the vehicle's speed, this is inherently dangerous.

NHTSA ID
11763840
Incident
Sep 9, 2026
Driver assistance
Filed Sep 5, 2026

My Tesla was operating under FSD at 9pm on a dark country road. I was traveling at 45mph and vehicle randomly applied hard emergency braking and I had to take over. It appeared that the vehicle may have been responding to a dark oil stain or possibly a mailbox. Had another vehicle been closely behind me, there would’ve been a collision.

NHTSA ID
11762324
Incident
Sep 4, 2026
Driver assistanceSteering
Filed Aug 31, 2026
Crash reported

On August 26, 2026, at approximately 8:56 AM, I entered a public parking garage in Washington, DC. Full Self-Driving (Supervised) was engaged and controlling the vehicle during a reversing maneuver. I remained attentive to the vehicle's surroundings, including pedestrians and surrounding traffic. While reversing under FSD (Supervised), the vehicle's right rear corner collided with the corner of a stationary structural pillar in the parking garage. I did not command the vehicle to steer into the pillar. Upon becoming aware of the impact, I immediately applied the brake. There were no injuries. The collision resulted in damage to the right rear area of the vehicle. After the incident, I photographed and recorded the scene and vehicle damage and saved the available Tesla Dashcam footage. I also requested the vehicle data from Tesla. I am reporting this incident because the vehicle collided with a stationary structure while FSD (Supervised) was engaged and controlling the reversing maneuver. I do not know the specific technical cause of the incident. The vehicle and available recorded data can be made available for inspection upon request.

NHTSA ID
11761157
Incident
Aug 26, 2026
Filed Aug 31, 2026

“The affected system was Tesla Full Self-Driving (FSD) (Supervised). FSD correctly selected the northbound left-turn lane but, while executing the left turn to westbound Pecan Street, intermittently directed the vehicle into the eastbound lanes carrying opposing traffic.”

NHTSA ID
11761111
Incident
Aug 27, 2026
Driver assistance
Filed Aug 19, 2026

Driving on a 2 lane road going 65 with Traffic-Aware Cruise Control enabled at 65 MPH with a car behind and no car in front of us. the car phantom braked for no reason going from 65 to 40 mph in a matter of seconds. Luckily we were able to accelerate to avoid being rear ended

NHTSA ID
11758118
Incident
Aug 19, 2026
Driver assistance
Filed Aug 14, 2026

The vehicle is experiencing severe, unpredictable software and hardware regressions related to the Full Self-Driving (Supervised) system (v14.3.7, Software build 2026.21.5) that create an immediate, active traffic hazard and a high risk of rear-end collisions. Primary Safety Issues: 1. TRAFFIC STALLS UPON DISENGAGEMENT: When Full Self-Driving (FSD) is engaged, auxiliary sensors malfunction, causing the headlights to cycle on/off and windshield wipers to run at full speed in clear, dry, midday daylight. When attempting to manually disengage FSD to correct these malfunctioning systems, the vehicle fails to smoothly transition control. Instead, it triggers critical red flashing alert lights, sounds severe warning chimes, and initiates an immediate, aggressive brake application—stopping the vehicle dead in active, live traffic. 2. PHANTOM BRAKING: The vehicle routinely experiences sudden, severe, and unprovoked phantom braking events while driving at speed, without any forward obstacles or environmental hazards present. 3. STEERING INSTABILITY: When navigating parking lot entrances, the vehicle exhibits extreme "indecisive behavior," resulting in violent, rapid shaking of the steering wheel before completing the maneuver. Tesla customer service was formally notified of these dangerous system behaviors on August 14, 2026. A formal remote engineering log review has been requested from the manufacturer, as these sudden braking actions in active traffic pose an immediate threat to public safety.

NHTSA ID
11757060
Incident
Aug 14, 2026
Other / unspecifiedSteeringSuspension
Filed Aug 6, 2026

I purchased my car on 3/23/26. Since delivery I have noticed that the car bounces at low speeds 20-30mph and the steering wheel vibrates at highway speeds 65 - 80mph. I have had the car to tesla service center 6 times since march. They have replaced all 4 tires, found and replaced a bent wheel (rim) on the passenger side. Then this last visit they replaced the passenger right wheel hub. They claim that when comparing it to the 1 other car available to road test my car was the same even though it still has the wheel vibration at highway speeds. they claim it falls within specs and is safe. I do not feel this is acceptable because they dont know what else to do. Now if I want them to check the car they say I must pay for any diagnosis and repairs if needed because they say they fixed the car. I do not feel safe driving at highway speeds as I am not sure what may happen which could endanger myself or passengers

NHTSA ID
11755161
Incident
Apr 2, 2026
Filed Aug 3, 2026

The horn system on the new Tesla are not effective. Other drivers cannot hear The unit is facing the ground, and a high speed. Other drivers. Can I hear it specially when it’s raining. The use of the original point was effective and never had a problem on my previous last Tesla, or any other car for that matter. Please help before a serious. Ask her that happens.

NHTSA ID
11754350
Incident
Jun 12, 2026
Driver assistance
Filed Jul 25, 2026

After a recent Tesla software update, a mandatory Full Self-Driving disengagement feedback window appears every time I disengage FSD while the vehicle is still moving. The feedback window covers a large portion of the display with a black overlay, noticeable enough something popped up. There is no setting to disable it, dismiss it immediately, or postpone the response until the vehicle is stopped. I am required to select a disengagement reason before I can access the controls and information behind the overlay. While this window is displayed, I cannot properly view or control functions such as music and other touchscreen features behind the area. This is especially dangerous because it appears immediately after I take manual control from FSD—a moment when my full attention should be on the road and the vehicle. The system effectively requires me to look away from the road and interact with the touchscreen before I can make another needed adjustment. This occurs every time I disengage FSD and is consistently reproducible. This behavior began after software version FSD v14.3.3. My vehicle is a 2026 Model 3. The problem occurred everytime while traveling at any speed. I believe this mandatory, non-dismissible overlay creates a serious driver-distraction hazard by obstructing the center display and requiring touchscreen interaction while the vehicle is in motion. Tesla should allow the feedback request to be dismissed, delayed until the vehicle is parked, or disabled entirely.

NHTSA ID
11752822
Incident
Jun 8, 2026
Suspension
Filed Jul 22, 2026

Air Suspension Failure - Damping Control Disabled (Code TAS_a313)" Description: "Vehicle is 2 days old. Suspension control module lost communication with CAN bus. Vehicle is in 'fail-safe' mode. Tesla Service Center has refused to assist. Safety risk due to loss of adaptive ride control." Manufacturer Response: "No response / Ignored."

NHTSA ID
11752257
Incident
Jul 22, 2026
Driver assistanceSteering
Filed Jul 18, 2026
Crash reported

Firstly, we were driving in the center lane on I-84W (three lanes), with Full Self Driving (FSD) at 55 mph. The car veered left on it owns (under FSD) into the center median with the front driver side of the vehicle struck the metal beam guardrail causing both air bags to deploy on the driver and left rear passenger sides. The car continued to move forward in the next 4-6 seconds under FSD (approximately 10-20 feet range) and then came to a complete stop with flashing warning screen asking driver to take over the steering wheel immediately.

NHTSA ID
11751300
Incident
Apr 12, 2026
Electrical
Filed Jul 13, 2026

Complaint Title: Defective Horn System on 2026 Tesla Model 3 - Ineffective in Rain or Highway Conditions Description: The horn on my 2026 Tesla Model 3 Highland is dangerously inadequate. It uses a single pedestrian warning speaker instead of a proper horn, which is easily overpowered by road noise, tire noise from large trucks, and especially rain. I cannot reliably alert other drivers, including 18-wheelers, when they are drifting into my lane or failing to yield. This creates a serious safety risk in wet conditions and highway driving. Traditional horns have been effective for decades — this design fails basic safety expectations. I am requesting immediate investigation and a fix.

NHTSA ID
11750177
Incident
Jun 2, 2026
Driver assistance
Filed Jul 11, 2026
Crash reported

Incident involving my 2026 Tesla Model 3 equipped with HW4 hardware and the latest FSD (Supervised) software. During a garage reverse maneuver performed under FSD supervision, the vehicle had sufficient time to assess the surrounding environment before initiating the maneuver. There were no pedestrians or moving obstacles nearby. An adjacent parked vehicle was present next to the intended reversing path. During the maneuver, the vehicle made initial contact with the adjacent vehicle. At no point did the vehicle provide any collision warning, alert, or indication that a collision had occurred. After the initial contact, the vehicle continued moving and a second impact occurred shortly afterward, resulting in additional damage. Immediately after the second impact, the driver intervened and took control of the vehicle to stop the maneuver, before further damage is caused. My main concerns are: 1. Why did FSD fail to identify the adjacent vehicle before the maneuver? 2. Why was no collision warning provided before or after the initial contact? 3. Why did the vehicle continue the reversing maneuver after the first impact instead of stopping till driver intervention? 4. What if is pediatrician who qualify ADA, children, elder was in the position of the adjacent vehicle, this failed sensing would cause imparable result. I would appreciate a technical review of this event and a detailed explanation of Tesla’s findings.

NHTSA ID
11749677
Incident
Jul 9, 2026
Driver assistance
Filed Jul 4, 2026

Lane keeping assistance turns on with every drive no matter how many times I set it to off. Where I live there are many potholes and poorly paved roads, along with poorly marked roads. As I am swerving around obstacles the car will fight the steering inputs I am giving it, trying to steer me back into whatever I was avoiding. This is a safety issue, and is not a problem on our older Tesla model 3 performance, as once that vehicle is set to off, it stays off. Now, as I start every drive I am navigating through a couple screens to turn off this "safety" feature.

NHTSA ID
11748263
Incident
Jul 1, 2026
Body & structure
Filed Jun 20, 2026
1 injury reported

While the vehicle was parked outdoors and the powered rear trunk lid was fully open, I leaned/bent forward into the trunk to retrieve an item. The edge of the trunk lid near the taillight assembly made contact with my scalp, causing a laceration. The wound bled significantly。The trunk lid’s fully-open position, combined with the geometry/edge of the liftgate near the taillight, creates a head-strike hazard for an average-height adult bending into the cargo area. I am requesting that NHTSA investigate whether the powered trunk lid’s open-position geometry presents an unreasonable risk of head injury to vehicle occupants/owners during normal use.

NHTSA ID
11745391
Incident
Jun 20, 2026

Higher-selling and older vehicles accumulate more reports. Counts are not failure rates and are not directly comparable between vehicles that sold in very different numbers.

Narrow this down by component

Categories with enough reports to have a page of their own

Data sources

Data on this page last refreshed .