CSR

Tesla · NHTSA safety record

2025 Tesla Model 3

Every safety complaint, recall and defect investigation the US government holds on this vehicle.

Owners have filed 127 safety complaints about the 2025 Tesla Model 3 with the US government. Of those, 29 describe a crash, 10 people were injured and no death is recorded. 3 recall campaigns are open against it.

The most complained-about system is forward collision avoidance, named in 30 complaints, 24% of the total. The typical failure was reported at 9,970 miles, the median across the 8 complaints that gave an odometer reading.

Compiled from NHTSA's complaint, recall and investigation files · Covers November 2024 to November 2026 · How this is counted

What is on file

127 complaints on file

127

Complaints

29

Describe a crash

0

Mention fire

10

People injured

0

Deaths

A complaint is an unverified account by the person who filed it, not a finding of fault. One complaint is one ODI number, which is how NHTSA counts them.

A recall is the manufacturer conceding a defect, and the repair is free. Whether one covers your particular car is a question only its VIN can answer, because a campaign covers a production range rather than a model year. A further 3 defect investigations are open and unresolved.

Which system owners named

Complaints naming each system
UNKNOWN OR OTHER 37 · 29%
FORWARD COLLISION AVOIDANCE 30 · 24%
STEERING 27 · 21%
ELECTRICAL SYSTEM 25 · 20%
LANE DEPARTURE 18 · 14%
VEHICLE SPEED CONTROL 15 · 12%
SERVICE BRAKES 13 · 10%
EXTERIOR LIGHTING 7 · 6%
STRUCTURE 6 · 5%
BACK OVER PREVENTION 5 · 4%
SUSPENSION 5 · 4%
ENGINE 4 · 3%
0 15 31

Red marks a system with a recall campaign against it. One complaint can name several systems, so these add up to more than 127.

When the complaints arrived

By the year NHTSA received them

By the year NHTSA received them, which is not the year the failures happened. They peaked in 2025 at 81.

88 66 44 22
24 25 26

This is the year the complaint was filed, not the year the failure happened. The range runs from 2024 to 2026, the last of them a part year, which is why its column is drawn faint.

Crash test ratings

NHTSA New Car Assessment Program

NHTSA has not crash tested the 2025 Tesla Model 3. Its New Car Assessment Program tests a selection of each year's vehicles and does not reach motorcycles, heavy trucks, motorhomes or most low-volume models, so an absence here says nothing about how the vehicle would perform. It is not a low score.

What owners have reported about this vehicle is below, and it is a different question: a crash test measures what happens to the people inside in a controlled impact, while a complaint records what broke during ordinary use.

Recall campaigns

3 on file

ELECTRICAL SYSTEM:PROPULSION SYSTEM:FUSES, RELAYS, CONTACTS, AND SHUNTS

25V690000 · October 10, 2025

The defect
Tesla, Inc. (Tesla) is recalling certain 2025 Model 3 and 2026 Model Y vehicles. The battery pack contactors may fail, causing a loss of drive power.
The risk
A loss of drive power can increase the risk of a crash.
The remedy
Tesla Service will replace the battery pack contactors, free of charge. Owner notification letters were mailed December 9, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-16-005.

Tesla, Inc. · up to 12,963 vehicles across all model years covered

BACK OVER PREVENTION:SOFTWARE

25V002000 · January 7, 2025

The defect
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."
The risk
A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.
The remedy
Tesla released an over-the-air (OTA) software update, free of charge. Tesla will also identify any vehicles that experienced a circuit board failure, or stress that may lead to a circuit board failure, and replace the affected computers, free of charge. Owner notification letters were mailed March 7, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-00-001.

Tesla, Inc. · up to 239,382 vehicles across all model years covered

TIRES:PRESSURE MONITORING AND REGULATING SYSTEMS

24V935000 · December 17, 2024

The defect
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."
The risk
Driving with improperly inflated tires increases the risk of a crash.
The remedy
Tesla released an over-the-air (OTA) software update, free of charge. Owner notification letters were mailed February 15, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-24-00-018.

Tesla, Inc. · up to 696,281 vehicles across all model years covered · fixed by software update

Defect investigations

4 on file

An investigation means NHTSA has decided a pattern is worth examining. A preliminary evaluation is often closed with no action; an engineering analysis is the stage that usually precedes a recall.

FSD Collisions in Reduced Roadway Visibility Conditions

EA26002

Still open engineering analysis · opened March 18, 2026

the electrical system

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 capabilities of the updates, and Tesla’s assessment of their safety impact. Tesla’s FSD is an advanced driver assistance system (ADAS) that relies exclusively on vision-based cameras and the related FSD software to detect and respond to the roadway ahead, projecting a path forward based on traffic control devices, vehicles, pedestrians, and the roadway itself. When Tesla began transitioning away from using both cameras and radars to an exclusively camera-based approach, known as Tesla Vision, in mid-2021, it developed and implemented a degradation detection system that it deployed by a software update to existing and new Tesla vehicles. On June 28, 2024, the day after Tesla submitted the SGO report of the November 28, 2023 fatal crash listed in this document, Tesla began developing an update to the degradation detection system. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI discussed individual incidents and its initial findings during the PE phase of its investigation with Tesla. As part of those discussions, Tesla’s post-incident analysis indicated that the update to the degradation detection system, had it been installed on the vehicles at the time, may have affected 3 of the 9 incidents identified by ODI. Tesla also described internal data and labeling limitations that prevented a uniform identification and analysis of crash events with the subject system engaged. ODI believes this limitation could have led to under-reporting of subject crashes over portions of the defined time-period. Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. Review of Tesla’s responses revealed additional crashes that occurred in similar environments and where the system either did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path. In upgrading PE24031 to an Engineering Analysis (EA), ODI will gather further information on the updated degradation detection system, including the status of updating vehicles and scope of compatible vehicles, the system’s visibility degradation detection capability, and alerts or warnings to the driver. Lastly, ODI will conduct analysis on six recent potentially related incidents. These incidents can be found at NHTSA.gov under the following SGO report identification numbers: 13781-11937, 13781-13211, 13781-13569, 13781-13633, 13781-13693, 13781-13788. The crashes included in the failure report summary can be found at NHTSA.gov under the following SGO report identification numbers: 13781-8004, 13781-7181, 13781-7381, 13781-7767, 13781-7964, 13781-8977, 13781-9267.

Traffic safety violations while Full Self Driving ("FSD") is engaged

PE25012

Still open preliminary evaluation · opened October 7, 2025

the electrical system

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 of the driving task, requiring a driver to supervise and intervene as necessary.  The driver remains fully responsible at all times for driving the vehicle, including complying with applicable traffic laws. ODI’s investigation will therefore focus, in particular, on whether certain driving inputs within the control authority of FSD forestall the driver’s supervision when they are unexpectedly performed. ODI has identified a number of incidents in which the inputs to the dynamic driving task commanded by FSD induced vehicle behavior that violated traffic safety laws. Although reports of this nature span a variety of behaviors, the reports appear to most commonly involve two types of scenarios. The first type of scenario involves a vehicle operating with FSD proceeding into an intersection in violation of a red traffic signal. The second type of scenario involves FSD commanding a lane change into an opposing lane of traffic. With respect to the first type of scenario, ODI has identified 18 complaints and 1 media report alleging that a Tesla vehicle, operating at an intersection with FSD engaged, failed to remain stopped for the duration of a red traffic signal, failed to stop fully, or failed to accurately detect and display the correct traffic signal state in the vehicle interface. Some complainants also alleged that FSD did not provide warnings of the system's intended behavior as the vehicle was approaching a red traffic signal. ODI has identified six Standing General Order ("SGO") reports in which a Tesla vehicle, operating with FSD engaged, approached an intersection with a red traffic signal, continued to travel into the intersection against the red light and was subsequently involved in a crash with other motor vehicles in the intersection. Of these incidents, four crashes resulted in one or more reported injuries. At least some of the incidents appeared to involve FSD proceeding into the intersection after coming to a complete stop. ODI's pre-investigative work, including coordination with the Maryland Transportation Authority and State Police, indicated that the problem may be repeatable, given that multiple subject incidents occurred at the same intersection in Joppa, Maryland. NHTSA understands that Tesla has since taken action to address the issue at this intersection. With respect to the second type of scenario, ODI has identified 2 SGO reports, 18 complaints, and 2 media reports alleging that a Tesla vehicle, operating with FSD engaged, entered opposing lanes of travel during or following a turn, crossed double-yellow lane markings while proceeding straight, or attempted to turn onto a road in the wrong direction despite the presence of wrong-way road signs. Likewise, ODI has identified 4 SGO reports, 6 complaints, and 1 media report alleging that a Tesla vehicle, operating with FSD engaged, proceeded straight through an intersection in a turn-only lane or executed a turn at an intersection in a through lane despite the presence of lane markings or signals. Complaints also alleged that FSD did not provide warnings of the system's intended behavior. Some complaints alleged that more than one of these failures occurred and, as such, the numbers are not cumulative. Some of the reported incidents appeared to involve FSD executing a lane change into an opposing lane of travel with little notice to a driver or opportunity to intervene. ODI’s review will assess whether there was prior warning or adequate time for the driver to respond to the unexpected behavior or to safely supervise the automated driving task. This review will assess any warnings to the driver about the system's impending behavior; the time given to drivers to respond; the capability of FSD to detect, display to the driver, and respond appropriately to traffic signals; and the capability of FSD to detect and respond to lane markings and wrong-way signage. NHTSA's review will also consider any updates or modifications to the system(s) that may affect the performance of FSD with respect to obeying traffic safety laws and signals. This assessment will focus, in particular, on the types of traffic safety violations described above, as most reports identified thus far have centered around those behaviors. While the behaviors under investigation appear to occur most frequently at intersections, NHTSA’s investigation will encompass any other types of situations in which this behavior may arise, such as when traveling adjacent to a lane of opposing traffic or when approaching railroad crossings. If other evidence received during this investigation involve other types of traffic safety violations, those may be considered as part of this assessment as well. To review the ODI reports cited in the Opening Resume ODI Report Identification Number document, go to NHTSA.gov. The SGO reports cited in this Resume are listed below by report ID and are available for download at NHTSA.gov/laws-regulations/standing-general-order-crash-reporting. 13781-8739-1, 13781-8995-1, 13781-9623-1, 13781-10333-1, 13781-10872-1, 13781-10930-1, 13781-10939-1, 13781-10941-1, 13781-11069-1, 13781-11305-1, 13781-11579-1 Media reported allegations included as a separate attachment.

Compliance with Standing General Order 2021-01 Reporting Requirements

AQ25002

Still open audit query · opened August 20, 2025

the electrical system

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 single batch, while others were submitted on a rolling basis. Preliminary engagement between ODI and Tesla on the issue indicates that the timing of the reports was due to an issue with Tesla’s data collection, which, according to Tesla, has now been fixed. NHTSA is opening this Audit Query, a standard process for reviewing compliance with legal requirements, to evaluate the cause of the potential delays in reporting, the scope of any such delays, and the mitigations that Tesla has developed to address them. As part of this review, NHTSA will assess whether any reports of prior incidents remain outstanding and whether the reports that were submitted include all of the required and available data. The SGO reports cited in the Opening Resume, can be found at NHTSA.gov/SGOCrashReporting under the following SGO 2021-01 report IDs: 13781-11020-1 13781-10844-1 13781-10843-1 13781-10530-1 13781-10160-1 13781-10159-1 13781-10157-1 13781-10146-1 13781-10122-1 13781-10098-1 13781-10097-1 13781-10096-1 13781-10095-1 13781-10094-1 13781-10093-1 13781-10023-1 13781-10022-1 13781-10021-1 13781-10020-1 13781-10017-1 13781-10016-1 13781-10015-1 13781-10014-1 13781-10013-1 13781-10012-1 13781-6047-1 13781-9930-1 13781-9917-1 13781-9928-1 13781-9925-1 13781-9924-1 13781-9923-1 13781-9922-1 13781-9835-1 13781-9834-1 13781-9833-1 13781-9832-1 13781-9831-1 13781-9830-1 13781-9829-1 13781-9827-1 13781-9818-1 13781-9780-1 13781-9779-1 13781-9778-1 13781-9777-1 13781-9775-1 13781-9774-1 13781-9773-1 13781-9772-1 13781-9771-1 13781-9770-1 13781-9728-1 13781-9688-1 13781-9715-1 13781-9714-1 13781-9713-1 13781-9712-1 13781-9711-1 13781-9710-1 13781-9709-1 13781-9696-1 13781-9695-1 13781-9694-1 13781-9693-1 13781-9692-1 13781-9691-1 13781-9690-1 13781-9687-1 13781-9686-1 13781-9342-1 13781-9319-1 13781-9019-1 13781-8910-1 13781-8732-1 13781-8712-1 13781-8310-1 13781-7897-1 13781-7895-1 13781-7835-1 13781-7798-1 13781-7797-1 13781-7758-1 13781-7757-1 13781-7756-1 13781-7755-1 13781-7667-1 13781-7399-1 13781-7398-1 13781-7397-1 13781-7396-1 13781-7395-1 13781-7394-1 13781-7393-1 13781-7389-1 13781-7388-1 13781-7387-1 13781-7386-1 13781-7385-1 13781-7383-1 13781-7187-1 13781-7186-1 13781-7185-1 13781-7184-1 13781-7181-1 13781-7023-1 13781-6399-1 13781-6389-1 13781-6388-1 13781-6387-1 13781-6386-1 13781-6379-1 13781-6378-1 13781-6377-1 13781-6375-1 13781-6214-1 13781-6172-1 13781-6155-1 13781-6154-1 13781-6122-1 13781-6120-1 13781-6118-1 13781-5800-1

Actually Smart Summon sessions resulting in low-speed impacts.

PE24033

Closed preliminary evaluation · opened January 6, 2025 · closed April 3, 2026

the electrical system

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 Summon reported crashes involved minor property damage claims with no reported incidents involving a vulnerable road user, injury, fatality, or major property damage as indicated by an air bag deployment or vehicle tow away. Out of millions of Summon sessions, a fraction of 1% resulted in an incident. Almost all those incidents took place where, typically early in a Summon session, the system or person using the app failed to fully detect or respond appropriately to vehicle surroundings resulting in minor impacts. Incidents took place when app users did not have a complete 360-degree view of the surroundings in the app to assess situational awareness. This limited the app user’s ability to determine whether an impact was imminent during initial vehicle maneuvers such as reversing in close proximity to an obstacle or a curb. ODI found that the impacts most often occurred with parking gates, adjacently parked vehicles, and short parking bollards. During this investigation, ODI identified two Summon crashes related to camera blockages. In both crashes, Summon attempted to navigate a snowy parking lot with snow partially or fully obstructing the forward-facing cameras. Summon did not detect the camera blockage and the vehicles collided with unoccupied parked vehicles while navigating the parking lot. App users in both instances did not command a vehicle stop or pause despite the obstructed camera visible in the camera stream in the app. On January 15, 2025, Tesla released Over-the-Air (OTA) Software (SW) Update Action numbers 578998 and 579185 for vehicles in service to implement a camera blockage detection condition. Both OTAs improve camera blockage detection mechanisms. Additionally, on January 20, 2025, and January 30, 2025, Tesla identified additional system requirements associated with camera visibility checks and released OTA SW-578752 and SW-580322, respectively. These firmware updates reduce false negative camera blockage detections due to snow or condensation. In its investigation, ODI identified one Summon incident where the vehicle did not yield for a gate arm blocking a garage exit lane and the app user did not command a vehicle stop or pause, resulting in an impact. On February 6, 2025, Tesla deployed OTA SW-578839 to improve vehicle reaction to dynamic gates. This OTA update upgraded vehicle perception systems through a high-fidelity occupancy determination network, which uses data from vehicle sensory systems to improve reconstruction of field objects with high accuracy. On November 20, 2025, Tesla further improved vehicle performance by adding object detections from a separate neural network through OTA SW-580514. Owners of the affected vehicles received all six OTA SW updates. Tesla also released these SW updates to production vehicles. See online public file for detailed descriptions of all six OTA SW updates. Due to low incident occurrence and low incident severity, this preliminary evaluation is closed. The closing of this investigation does not constitute a finding that a safety-related defect does not exist. The agency reserves the right to take additional action if warranted by future circumstances. For additional information regarding this investigation, see the complete online public file.

In owners’ own words

Quoted from the complaint file

Quoted from NHTSA's complaint file. These are unverified accounts by the people who filed them, not findings of fault.

AIR BAGS

2 injured · crash · towed

On June 7, 2025, I was a passenger in a 2025 Tesla 3. Driver of Tesla made an unsafe lane change coming off an Interstate and my side was struck almost T-bone style by an oncoming vehicle going between 45-55mph. Our seatbelts did not lock us in place causing the driver to hit his head on steering wheel and then on driver side window causing lacerations and possible concussion. My side tool the impact and no side curtain airbags deployed and neither did the dash airbags. I am concerned that the location and speed with which we were hit could have been much worse up to and including death as the airbags did not deploy nor seatbelts firmly lock us in place. The car was deemed a total loss and

NHTSA complaint 11681387, quoted in part. Filed by an owner and not verified by NHTSA or by us.

UNKNOWN OR OTHER

2 injured · crash · towed

-Full Self-Driving (FSD) was engaged when my vehicle unexpectedly and abruptly deviated from its expected course and collided with a vehicle on the other side of the road. My vehicle was totaled so I cannot confirm availability for inspection, however I have te vehicle’s USB drive which contains data about the vehicle and collision. -The abrupt and unexpected maneuver created an immediate safety risk to me and the public; had there been pedestrians in the area, that risk would have been severe and potentially catastrophic. Based on the vehicle data available to me, approximately 0.85 seconds elapsed between the vehicle’s departure from its expected course and the collision, leaving

NHTSA complaint 11764601, quoted in part. Filed by an owner and not verified by NHTSA or by us.

VEHICLE SPEED CONTROL:ACCELERATOR PEDAL

1 injured · crash · towed · 9,840 miles

The contact owns a 2023 Tesla Model 3. The contact stated that while in reverse (R) and backing up at approximately 5 MPH down a slight incline, the vehicle accelerated inadvertently. The contact stated that she turned the steering wheel to the right to get on the road. The contact had taken her foot off the accelerator pedal when the vehicle gained momentum and drove backwards about 50 feet and crashed into a tree with the rear end. The contact stated that the passenger side rear bumper and an aftermarket trailer hitch were dented, crumpled, and bent. The contact stated that the rear windshield was cracked on the driver's side. The contact stated that the regenerative braking feature never

NHTSA complaint 11681518, quoted in part. Filed by an owner and not verified by NHTSA or by us.

SERVICE BRAKES

1 injured · crash · towed

On September 7, 2025 at ~7:53 PM, my 2025 Tesla Model 3 operating with Full Self-Driving (FSD) engaged performed an aggressive, uncommanded turn while under computer control. The maneuver occurred so abruptly that I could not safely override steering before impact, and a crash resulted. The Tesla app Trip View for Trip 3 (7:34–7:53 PM) shows “Vehicle on FSD” for 18 min 54 sec and records an “Aggressive Turning” event at 7:53 PM (2.0 sec) immediately before the trip ended (screenshot attached). This reflects a steering/driver-assist control defect in FSD’s turning behavior and a failure of collision-mitigation to prevent the crash. I sustained bodily injuries and the vehicle incurred

NHTSA complaint 11686758, quoted in part. Filed by an owner and not verified by NHTSA or by us.

ELECTRICAL SYSTEM

crash

See attached document for complaint.

NHTSA complaint 11776207. Filed by an owner and not verified by NHTSA or by us.

VEHICLE SPEED CONTROL

crash · towed

The contact owns a 2025 Tesla Model 3. The contact stated that while driving 13 MPH and making a right turn, the Full Self-Driving mode engaged unintendedly, and the vehicle suddenly veered to the left, accelerated unintendedly, and struck a median curb. The vehicle then veered to the right and struck another curb before driving onto the grass near the hospital. The vehicle was towed to a collision center. The insurance company inspected the vehicle. The dealer service center was contacted and sent an email to the manufacturer regarding the failure; however, there was no response. The vehicle was repaired. The failure mileage was unknown.

NHTSA complaint 11776219. Filed by an owner and not verified by NHTSA or by us.

EQUIPMENT:ACCESSORY:FLOOR MAT
The carpet floor mat on the driver's side accordions up under the accelerator and brake pedals creating a driving hazard. The driver side floor mat is supposed to be secured in place by an approximately 1 inch wide strip of velcro running the length of the floor mat under the edge closest to the seat. The Velcro is secured to the mat on three exterior edges. The Velcro is not secured on the interior edge allowing the Velcro to fold upwards and lose grip with the underlying carpet. Once the Velcro detaches and folds from the mat, it loses all grip and begins to slide. I informed two different Tesla dealers about the incident and they simply suggested I buy an identical replacement mat. They

NHTSA complaint 11775741, quoted in part. Filed by an owner and not verified by NHTSA or by us.

ELECTRICAL SYSTEM
After an informal, photo-based preliminary repair estimate for minor cosmetic damage at Tesla Collision Center Fort Lauderdale in late XXX (estimate never finalized, no repair performed), Tesla's internal system flagged my 2025 Tesla Model 3 (VIN [XXX]) as salvage/total loss, revoked Supercharger access, and voided the manufacturer warranty. Tesla confirmed the salvage designation in writing on XXX. Neither the DMV nor any insurer declared this vehicle salvage or a total loss: DMV records show a clean title, Tesla Insurance canceled the claim (accident not my fault) with no total-loss declaration, and the at-fault driver's insurer, [XXX], confirms it never issued a salvage title. As a

NHTSA complaint 11774727, quoted in part. Filed by an owner and not verified by NHTSA or by us.

ELECTRICAL SYSTEM

crash · towed

Statement Regarding My 2025 Tesla Model 3 Accident I was driving my 2025 Tesla Model 3 when the accelerator pedal appeared to become stuck, causing the vehicle to continue accelerating. The vehicle reached approximately 70 mph, and I was unable to regain control. I attempted to stop the vehicle by applying the brakes, but the brakes felt hard or would not respond, and the vehicle would not stop as expected. I was driving the vehicle myself and was not using Autopilot or Full Self-Driving. Because I could not bring the vehicle to a stop, I collided with three other cars. I believe the suspected accelerator and braking malfunction contributed to the accident. The police responded to the

NHTSA complaint 11773590, quoted in part. Filed by an owner and not verified by NHTSA or by us.

EXTERIOR LIGHTING
This vehicle doesn't come with a turn signal stalk. To engage the turn signal, I have to use push-buttons on the steering wheel. Nearly every time I use them, I get the wrong direction, even after a year of ownership. It's functionally impossible to use them legally to exit a roundabout, and I really want you to reflect, it is impossible to use them to legally exit a roundabout -- I can not obey the law using them. It's functionally impossible. Additionally, they're too close to the edge of the steering wheel, causing light brushes to trigger a false turn signal, confusing nearby drivers. About 8 to 9 out of 10 turn signals I make are false or in the incorrect direction. This feature is

NHTSA complaint 11772903, quoted in part. Filed by an owner and not verified by NHTSA or by us.

Compare

Other years of the Tesla Model 3

Model year Complaints Recalls Deaths
2026 31 1 —
2024 224 5 —
2023 431 12 1
2022 775 18 1
2021 677 22 8
2020 455 20 2
2019 624 21 4
2018 1,040 18 1
2017 27 15 —

Other 2025 Tesla models

Model Y 116 Cybertruck 26 Model X 16 Model S 6

Complaints on file, same model year.

Every Tesla on this site — 46 vehicles.

If this is your car and a dealer keeps failing to fix it, your state's lemon law may require the manufacturer to replace it or buy it back. How many repair attempts it takes, and how long you have to file, is set by the state you bought in and by nothing on this page.

Where these numbers come from

A complaint is one owner's account and has not been verified by NHTSA or by us. A vehicle with more complaints is not necessarily worse: models that sold in larger numbers collect more of them. How this is counted.

Compiled and maintained by
Independent developer and analyst