Model-year record

2024 Tesla Model Y
See the complaints, recalls, crash rating, and fuel economy in the public record. Then check the mileage and history of the car you found.
This page shows records, not a buy or avoid call.
The same model year can include a well-kept car and a neglected one. Use these records to plan what to check. Use the specific-car check when you know the mileage.
Complaints filed
299
Reports to NHTSA, 2024
Safety recalls
5
NHTSA campaigns on record
NHTSA crash test
Not rated
Overall NCAP rating
Combined MPG
118
EPA estimate
Known issues
Electrical System issues lead owner complaints (17% of 299 reports), followed by forward collision avoidance (17%).
+ 14 more component categories with fewer reports.
Share of all 299 NHTSA complaints for this model year, grouped by the component owners named. Bars are scaled to the largest category. Examples: ODI 11723291, ODI 11697194, ODI 11697079, ODI 11694996, ODI 11666241.
Individual complaint reports(299)
Showing the 50 most recent reportsService BrakesJul 2026 · ODI 11751573Details +Close −
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.
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherJul 2026 · ODI 11751589Details +Close −
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
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceJul 2026 · ODI 11751290Details +Close −
Whenever I cancel FSD in this Tesla for any reason, a highly distracting ‘forced feedback’ panel pops up on the single information screen, obstruction critical information. It only disappears when I select one of 4 feedback options, blocking my information screen view all that time. I am a regular driver, not a trained beta tester.
- Reported
- Jul 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Electrical SystemJul 2026 · ODI 11750529Details +Close −
On July 10, 2026, my 2024 Tesla Model Y (approx. 22,440 miles) lost all power (main/12V battery) while parked next to a Supercharger stall on Level 3 of the Harrah's Ak-Chin Casino parking garage, Maricopa, AZ. Ambient temperature was approximately 110F. My dog and cat were inside the vehicle. With the vehicle powered off, the key card, Tesla app, and interior door releases did not function, leaving no way to open the doors from outside or inside. Unable to find or access a working manual door release in time, we broke the rear quarter glass and damaged a door to physically extract the pets before they suffered heat-related harm. Maricopa Police Department and Ak-Chin Fire Department responded to the scene. This represents a serious safety defect: a loss of vehicle power should not eliminate all means of entry/egress, particularly when children or pets could be trapped in extreme heat. The vehicle, damaged door, and glass are available for inspection. Photos of the incident are available.
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Power TrainJul 2026 · ODI 11750667Details +Close −
SYSTEMIC POWERTRAIN SAFETY DEFECT: Catastrophic Loss of Propulsion & Failure of Dual-Motor Redundancy. 1. Incident & Safety Risk: While traveling in the far-left HOV lane of a 6-lane interstate highway, the vehicle experienced an uncommanded, unwarranted Automatic Emergency Braking (AEB) intervention during a controlled lane change. This sudden deceleration instantly triggered a complete powertrain collapse and total loss of propulsion. The vehicle came to a dead stop in a live highway lane. The driver (me), passenger, and our [XXX] infant were stranded in lane 3 of a 6 lane highway for ~35 minutes until Highway Patrol units arrived to manually push the vehicle across live traffic to the shoulder. This near-miss was an immediate, severe life-safety crisis not just for the occupants but also to others on the road. 2. Symptoms & Alert Codes: There were zero warning symptoms prior to the incident. Immediately upon the power collapse, the touchscreen displayed critical faults. Active diagnostic telemetry confirmed alert codes: DI_a137 (No Capable Drive Units) DI_a063 (System Graceful Power Off) 3. Manufacturer Confirmation & Inspection Status: The failure was confirmed in writing by the manufacturer’s service center. The diagnostic invoice explicitly states: "The rear drive inverter experienced an unintended reset due to an error. Sudden power reduction and shutdown while driving." The vehicle is currently held at the manufacturer's facility and is fully available for inspection. 4. Engineering Assessment: As a mechanical engineer, my assessment is the surge through the AEB event to the inverter’s DC-link was unable to damp this load, forcing a hardware logic reset. Crucially, the software logic failed to partition this fault. In a dual-motor architecture marketed as having built-in powertrain redundancy, a localized rear inverter reset should be isolated, leaving the front motor operational to safely navigate out of traffic, this did not happen. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jul 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
SteeringJul 2026 · ODI 11750293Details +Close −
Vehicle Safety Complaint On XXX, between approximately 9:45 PM and 9:52 PM, we were driving our Tesla Model Y eastbound on [XXX] and exited at [XXX] toward [XXX]. As my husband was making a left turn after exiting the freeway, the steering wheel suddenly became stuck or extremely difficult to turn. There was no warning, no unusual driver input, and no use of Autopilot or Full Self-Driving. The vehicle does not have Full Self-Driving capability. My husband had to use significant force to regain steering control to avoid striking the left side of the roadway/median. Because the vehicle did not respond as expected, the car behind us nearly rear-ended us. Our two children, ages [XXX] and [XXX], were properly restrained in the back seat. Fortunately, no collision or injuries occurred, but the incident could easily have resulted in a serious crash. This incident raises significant concerns about the safety and reliability of the steering system. I am requesting that this complaint be investigated and that Tesla review the vehicle’s logs from the time of the incident. The vehicle has also been reported to Tesla for inspection. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherJul 2026 · ODI 11749672Details +Close −
A Tesla vehicle passed by me and my kid while we are trying to get into the car, it just stopped in front of my parking spot to block my car. Then I got down and checked there is a no driver. I took a picture of the license plate and side view of car where no one is there in the car. It was terrifying since no one is in the parking lot we came after a movie and entered the parking lot to get our car. This smart driving needs to be banned or restricted without driver.
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherJul 2026 · ODI 11748960Details +Close −
I have a 2024 Tesla Model Y and while parked, the rear windshield spontaneously shattered while defrosting my window. My kids were sitting in the back seat when the incident happened. This has not been confirmed by a dealer or service center but me, my wife and brother were standing outside our car when it happened and saw no signs or external impact or object. The vehicle has not been inspected by any external parties at this time. The vehicle presented no warning lamps, messages or other symptoms prior to the incident.
- Reported
- Jul 2026
- Incident date
- Jul 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherJul 2026 · ODI 11749080 · crashDetails +Close −
On XXX, at approximately 12:30 PM, I was driving eastbound on XXX through [XXX]. The weather was mildly rainy, and I was traveling at approximately 65–70 mph. Without any input on my part, the vehicle suddenly steered sharply to the left, causing it to strike the center divider. The vehicle then crossed multiple lanes of traffic, slid toward the shoulder, and impacted barriers a second time. The collision resulted in the vehicle being declared a total loss, and all airbags deployed. Two days later, after reviewing the vehicle recordings, I observed that immediately after water splashed up from the vehicle in front of me, the Tesla appeared to make a sudden steering maneuver to the left as if attempting to avoid an object or hazard. Based on my review of the footage, I did not observe an actual obstacle in the roadway that would have required such an evasive action. As a result, I am concerned that the vehicle may have incorrectly detected a hazard and initiated an unintended steering maneuver. While I cannot determine the exact cause, the behavior appears consistent with a false or erroneous perception by the vehicle's automated driving or driver-assistance system. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jul 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
StructureJul 2026 · ODI 11749101 · 1 injuriesDetails +Close −
The rear hatch has shifted out of alignment, and has started to fall 5-10 inch's when opened intermittently. TESLA service can't fix the issue and pushing me to a body shop. There have been no accident or issues that would cause a body panel to shift over a quarter of an inch.
- Reported
- Jul 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- 1 injuries
Forward Collision AvoidanceJul 2026 · ODI 11747817Details +Close −
While driving on the highway with Tesla FSD engaged, the vehicle activated the right turn signal and began steering right as if taking an exit. There was no exit ramp, gore area, or valid right-turn path at that location. I took manual control to prevent the vehicle from leaving the highway/entering the shoulder. I believe this could have caused a crash if I had not intervened. I have dashcam footage of the event.
- Reported
- Jul 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Air BagsJun 2026 · ODI 11746167 · crashDetails +Close −
The contact owns a 2024 Tesla Model Y. The contact stated that while driving 25 MPH and making a right turn into an alley with another vehicle approaching, the contact stopped to reverse; however, while using the tap feature, the vehicle unintendedly accelerated and crashed into a concrete barrier twice. The vehicle was uncontrollable. The contact stated that the air bags failed to deploy. The crash was not captured on the camera inside the vehicle. A Police report was filed. There was no injury reported. The vehicle was towed to a towing lot and was next towed to the local dealer but was not yet diagnosed or repaired. The manufacturer was not contacted. The approximate failure mileage was 14,000.
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
StructureJun 2026 · ODI 11745234Details +Close −
After about 2 minutes from leaving a patients house, I was driving at approximately 25mph when my frunk(front trunk) of my Tesla flew open and hit my windshield. There was no alert through the Tesla app or in the car itself. I stopped the car stepped outside and the frunk would not close after when I tried to close by hand, it would stop at the latch. When I closed it from the Tesla app it was able to close properly
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherJun 2026 · ODI 11745322 · crashDetails +Close −
It was raining, when I was driving on I95 highway, the vehicle suddenly started to spin by itself, and out of my control. When I tried to hit the brakes, there was no response, then it swung out of the lane and hit on the tree. I have reported to police, and I just filed a claim with insurance company, and I will also report this to Tesla later. However, I think it is really very dangerous, and I hope it can be investigated for safety reason. I have video recordings, I can provide if you need them. Thank you.
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Unknown Or OtherJun 2026 · ODI 11745089Details +Close −
Whenever the self driving feature is disengaged, a pop up menu is forced into the user asking for a reason for the disengagement. The user is forced to submit a response for the pop up menu to go away. This menu shifts sections of the screen around and can cause distractions due to the user looking for specific information that is typically there but is not due to the pop up menu.
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Vehicle Speed ControlJun 2026 · ODI 11744795 · crashDetails +Close −
• FSD received a software update earlier this same morning. • While navigating a parking garage under FSD, the vehicle initiated an unprompted reverse maneuver. • The reversal happened with no warning and no meaningful time for driver intervention before impact. • The vehicle struck a structural beam, causing damage to the vehicle above the rear driver side door, as well as shattering and causing splintering of the roof glass.
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Vehicle Speed ControlJun 2026 · ODI 11744005 · crash · 2 injuriesDetails +Close −
VEHICLE INFORMATION Year: 2024 Make: Tesla Model: Model Y Mileage at time of incident:1,288 Date of incident: XXX Location of incident: [XXX] On XXX, I was operating my 2024 Tesla Model Y in [XXX] when the vehicle experienced a sudden and unexpected malfunction of its Autopilot/autonomous driving system. The vehicle activated in Autopilot mode without my intentional input, causing me to lose control and resulting in a serious crash. Prior to the collision, the vehicle's Autopilot system, engaged without my input and abruptly accelerated. I was seriously injured as a result. The vehicle, a brand-new 2024 Tesla Model Y, was in normal operating condition with no prior mechanical issues. I had not modified the vehicle in any way. Following the crash, Tesla provided data to attorneys regarding the incident which I believe to be inaccurate and inconsistent with my experience. I am requesting that NHTSA: 1. Open a formal investigation into this incident 2. Investigate the accuracy and completeness of data Tesla provides following Autopilot-related crashes 3. Preserve my complaint as part of any ongoing investigation into Tesla Autopilot/FSD systems Was I injured? YES Number of injuries: 2 Were there fatalities: NO Was there a police report? YES INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jun 2026
- Incident date
- Sep 2024
- Mileage
- Not provided
- Outcome flags
- Crash 2 injuries
Vehicle Speed ControlJun 2026 · ODI 11743816 · crash · 4 injuriesDetails +Close −
The Tesla Autosteer (equivalent of adaptive cruise control) failed to brake on seeing the car ahead braking. In the 5 seconds before impact, the car ahead had started braking. The autosteer did not brake for the first 3 seconds and then It asked me to take over 2 seconds before collision. It did not apply automatic emergency braking causing me to rear end the car ahead of me on the freeway at around 30mph This is supposed to be a safety driver assist feature which instead was the primary cause of the accident. The take control was too late to avoid collision. This is a serious safety issue.
- Reported
- Jun 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- Crash 4 injuries
Forward Collision AvoidanceJun 2026 · ODI 11743171 · crashDetails +Close −
Vehicle: 2024 Tesla Model Y Date of Incident: XXX Location: Southbound XXX Express Lanes near the [XXX]/[XXX] exit split in [XXX]. At the time of the incident, Tesla Full Self-Driving (FSD) Supervised was engaged. I was traveling in the Express Lanes and intended to remain in the Express Lanes. I was not attempting to take any exit. As the roadway approached a lane split/gore area, the vehicle began steering toward the striped boom barriers that prevent drivers from going into oncoming traffic, rather than remaining in the travel lane. There were not impending impact alerts or lane deviation alerts. There were no unusual weather conditions, and I did not observe any road conditions that would have made the lane path unclear to a human driver. As soon as I saw the vehicle veering into the boom barriers, I intervened by taking control of the steering wheel. The system disengagement alert/chime occurred only after I took over. Despite my intervention, the vehicle made contact with the boom barrier assembly. The impact caused significant damage to the windshield and driver's side door frame. Glass entered the passenger compartment. My infant child was in the vehicle at the time. Fortunately, no injuries were sustained. Tesla Dashcam footage of the incident was preserved and is available. A claim was opened with Tesla Insurance, and I was advised to submit a vehicle malfunction report for review of vehicle telemetry and FSD operation during the incident. After the collision I maneuvered the vehicle back into its lane, exited the toll highway and parked at a nearby shopping center to assess our injuries the vehicle. While there, another Tesla parked near me, and the driver had experience the same exact situation while his Tesla was in autodrive. I am requesting investigation into whether the vehicle's driver-assistance system improperly tracked toward the boom barriers rather than remaining within the intended travel lane. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Unknown Or OtherJun 2026 · ODI 11743208Details +Close −
On XXX, at approximately 5:00 PM, my daughter was operating our 2024 Tesla Model Y on [XXX] near the [XXX] exit in [XXX]. The vehicle suddenly became uncontrollable. According to the driver, the steering wheel appeared to move on its own, the vehicle accelerated unexpectedly, braking was ineffective, and the vehicle zig-zagged across multiple lanes of traffic from the far left lane to the far right lane. The vehicle reportedly performed approximately half of a 360-degree spin before control was regained. Several motorists reportedly pulled over after observing the vehicle’s erratic behavior. Tesla Service later inspected the vehicle and advised that no fault was found and that the vehicle was operating within factory specifications. However, no explanation was provided for the loss-of-control event. Due to the seriousness of the incident and the risk of severe injury or death, I am requesting that NHTSA investigate this matter as a potential vehicle safety defect. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Back Over PreventionJun 2026 · ODI 11742365 · crashDetails +Close −
On XXX, at approximately 8:01:49 AM Eastern Time, my 2024 Tesla Model Y (VIN: [XXX]) was operating under Full Self-Driving (FSD) software version 14.3.3 when the system directed the vehicle into the outer wall of my residential garage without driver input. FSD was actively engaged at the time of the incident. The vehicle sustained significant damage to the front bumper fascia and wheel well trim. Additional damage includes a cracked front fog light/corner lens assembly with surrounding fascia stress, also caused by the same incident. The incident also caused paint transfer damage to the garage wall trim. I have preserved dashcam footage documenting the incident, which is consistent with FSD-directed vehicle behavior. I am referencing NHTSA Preliminary Evaluation PE25012 as this incident is consistent with the pattern of uninstructed FSD-directed maneuvers currently under federal investigation. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Forward Collision AvoidanceJun 2026 · ODI 11741960 · crash · 1 injuriesDetails +Close −
I am reporting a safety defect in Tesla’s Full Self-Driving (Supervised) system. On XXX, while using FSD, my 2024 Tesla Model Y (VIN: [XXX]) failed to recognize that the road terminated into the desert after a roundabout on the [XXX] road near [XXX]. The vehicle accelerated straight instead of making the sharp 90-degree left turn, left the roadway, traveled down an embankment, and crashed. Airbags deployed and the vehicle was declared a total loss. Vehicle Data Recorder (VDR) data confirms that Autosteer was active and available during the critical braking sequence. I applied very strong sustained braking (brake master cylinder pressure exceeded 129 BAR with ABS activation). The tow truck driver, [XXX], stated at the scene that this was the fifth Tesla he had recovered from this exact same location due to similar crashes. This documented cluster of at least five identical Tesla crashes at one hazardous spot indicates that Tesla had actual notice of a dangerous defect in its FSD mapping and road geometry recognition but failed to correct it. This incident aligns with NHTSA’s ongoing investigations into FSD performance issues (including EA26002). I am also pursuing a private product liability claim for damages. I can provide supporting documents including VDR screenshots, the Wickenburg Fire Department report, and a witness statement. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jun 2026
- Incident date
- Aug 2024
- Mileage
- Not provided
- Outcome flags
- Crash 1 injuries
StructureJun 2026 · ODI 11742029 · crash · 1 injuriesDetails +Close −
On the evening of June 3, 2026, while driving on the I-575 Express Lanes in Cobb County, Georgia, the vehicle’s autopilot/driver assistance system malfunctioned and steered the vehicle into the express lane boom barrier. The boom bar struck the windshield, causing catastrophic windshield failure with glass imploding into the cabin. Glass shards covered the driver’s seat, floor, and dashboard. The driver sustained glass puncture wounds to both forearms and forehead, as well as neck, back, and right arm soft tissue injuries. Component failed: Autopilot/ADAS system. Vehicle is available for inspection. Tesla was notified directly at time of incident. Insurance company has been notified. SR-13 filed with Cobb County. No warning lamps or messages appeared prior to the autopilot malfunction. The root cause of the windshield damage was the autopilot system failure, not driver error or external road debris. Photographic documentation of vehicle damage and driver injuries exists.
- Reported
- Jun 2026
- Incident date
- Jun 2026
- Mileage
- Not provided
- Outcome flags
- Crash 1 injuries
Lane DepartureMay 2026 · ODI 11740070Details +Close −
I and others have noticed that once UNsubscribed from FSD, lane departure alerts and automatic corrections occur much more often than when subscribed to FSD, even if car is being driven by user. The alerts and corrections happen on almost every drive despite being within normal lane spacing. It feels like this is intentional to push users to subscribe back to FSD. Driving other makes of vehicles does not result in nearly this amount of warnings and corrections. Various online forum post corroborate this behavior. Even if there is an explained reason for it, Tesla does not notify the user of such changes that will happen once unsubscribing from FSD.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherMay 2026 · ODI 11740109Details +Close −
I am reporting an issue with Supervised FSD regarding school zones in Ohio. In my area, active school zones are indicated by flashing lights. The FSD system successfully recognizes these lights and reduces the vehicle's speed to the legal limit of 20 mph. However, if there is a traffic light within the school zone, the vehicle loses track of the school zone speed limit after stopping or cycling through the intersection (red/green transitions). Once the traffic light turns green, the car quickly accelerates back to the normal speed limit (e.g., 35 mph) while still inside the active school zone. I have posted this issue to @Tesla and @Tesla_AI on X, but have not received a response.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Visibility/WiperMay 2026 · ODI 11739805Details +Close −
I am reporting a safety‑critical issue with the automatic windshield wiper system on my 2024 Tesla Model Y. The vehicle uses a camera‑based “Auto Wiper” system, and it consistently fails to activate fast enough during heavy rain, spray from passing trucks, or sudden visibility loss. During moderate to heavy rain, the Auto wipers often stay on a slow or intermittent setting even when the windshield becomes fully covered with water. The system does not increase wiping speed quickly enough to maintain visibility. This results in several seconds where I cannot clearly see the road ahead. This problem is made worse because the Model Y makes it difficult to quickly switch to manual wiper control while driving on the freeway. The driver must look down at the touchscreen and navigate menus to adjust wiper speed, which is unsafe at highway speeds. The delay between losing visibility and being able to manually increase the wiper speed creates a dangerous situation. This behavior has occurred multiple times at highway speeds. When passing large trucks or encountering sudden water spray, the wipers do not react, and the windshield becomes momentarily opaque. This creates a serious risk of losing lane position or failing to see vehicles in front of me. This is a safety hazard because: 1.The Auto wipers do not clear the windshield when visibility is urgently needed. 2.Manual override requires taking eyes off the road to use the touchscreen. 3.The delay in response can lead to loss of visibility for several seconds. I am requesting that NHTSA investigate this issue, as it affects visibility and could lead to collisions, especially at highway speeds or during sudden heavy rain.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Electrical SystemMay 2026 · ODI 11739558Details +Close −
Component or system that failed: The GPS navigation system and cellular connectivity module in my 2024 Tesla Model Y (VIN: [XXX] ) have intermittently lost signal and become completely nonfunctional multiple times over the past month. Tesla's service documentation indicates this affects the vehicle's connectivity hardware or managing software. The vehicle is available for inspection upon request. Safety risk: Loss of GPS navigation while driving creates a safety hazard when traveling unfamiliar routes, in low-visibility conditions, or during emergencies. Loss of cellular connectivity simultaneously disables Tesla's roadside assistance and the vehicle's calling capability. The vehicle acknowledges this risk by displaying a yellow caution alert reading "Poor GPS location accuracy — Additional attention may be required" on the primary touchscreen while in motion, with no advance warning before the failure occurs. Reproduced or confirmed by a dealer or service center: Yes. On May 22, 2026, Tesla Service Columbia-Two Notch Rd, 6301 Two Notch Road, Columbia, SC 29223, confirmed this as a known issue. The service advisor stated Tesla is aware of the defect but has no repair available and instructed me to submit in-car bug reports each time it occurs. Inspected by manufacturer or others: Yes, by Tesla's service center on May 22, 2026. No independent, police, or insurance inspection has been performed. Warning lamps or prior symptoms: A yellow triangle caution icon with the message "Poor GPS location accuracy — Additional attention may be required" appears on the primary touchscreen during each failure, but only after GPS has already degraded — no advance warning is given. This has occurred four times since April 2026, with each event lasting between 15 seconds and over one minute. UNKNOWN as to specific trigger conditions. Photographic documentation has been retained. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherMay 2026 · ODI 11737157Details +Close −
After updating to Tesla FSD 14.3, whenever I take over from FSD, the vehicle displays a mandatory “intervention reason” prompt on the center screen. The prompt does not disappear unless the driver selects a reason. This occurs immediately after a disengagement/takeover, when the driver may still need full attention on the road. The prompt can cover map/navigation information and forces interaction with the touchscreen while driving. I believe this may create a driver-distraction safety risk.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceMay 2026 · ODI 11736067Details +Close −
I am reporting a software-induced driver distraction defect in Tesla’s Full Self-Driving (Supervised) system, specifically the post-disengagement “Why did you intervene?” dialog introduced in software 2026.2.9.8 and modified in 2026.2.9.9 and 2026.2.9.10, running FSD v14.3.2. Every time the driver disengages FSD via steering, brake, or accelerator input, a modal dialog appears on the center touchscreen asking the driver to categorize the intervention. It presents four options (Navigation, Preference, Discomfort, Critical) plus a voice memo prompt. The dialog cannot be dismissed or deferred. It remains on screen indefinitely until the driver reads the prompt and taps a selection. This creates a serious safety hazard: The dialog appears the moment the driver has resumed manual control, often in response to an unsafe FSD action requiring immediate attention to the road. Forcing the driver to read text and make a multi-choice touchscreen selection during this high-cognitive-load transition directly conflicts with NHTSA’s Driver Distraction Guidelines for in-vehicle devices. The dialog occupies a large portion of the center display and obscures the navigation map and surrounding-vehicle visualization, removing situational awareness at the moment it is most needed. Because it cannot be dismissed, drivers are coerced into touchscreen interaction while driving, including in active traffic, intersections, merges, and lane changes. The forced-choice design also incentivizes drivers to tap any option to clear the screen, defeating the stated data-collection purpose and increasing eyes-off-road time. Tesla provides no setting to disable this dialog. I request NHTSA investigate this as a driver distraction defect and require Tesla to provide a dismiss option, defer the prompt until Park, or remove the forced-interaction requirement. I am the vehicle owner and experience this on every FSD disengagement.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceMay 2026 · ODI 11735191Details +Close −
Hello, I am not writing about a specific incident, but rather wanted to alert the NHTSA to a potentially dangerous development with Tesla's Full Self-Driving (FSD) technology. In the latest software update being pushed to owners, Tesla now forces drivers to provide feedback if they disengage the FSD system for any reason. This feedback comes in the form of a box on the screen and it cannot be closed. You cannot interact with any part of the vehicle infotainment system until you complete the feedback. I believe that this can cause safety issues, especially in a stressful situation if someone is trying to access the car's map system, for example. Even in normal situations, the driver would be required to read the options and make a selection on the screen - while still driving. I would highly recommend the NHTSA look into this, as I believe this is a very shortsighted policy that will needlessly endanger drivers, other drivers, pedestrians and everyone on the road. To be clear for form purposes: I am not writing about a specific incident, but I am submitting this information via this form because I do not see a general information form.
- Reported
- May 2026
- Incident date
- May 2026
- Mileage
- Not provided
- Outcome flags
- None reported
SteeringApr 2026 · ODI 11734229Details +Close −
The contact owns a 2024 Tesla Model Y. The contact stated that while driving approximately 25 - 35 MPH, while driving near cones on the road, the contact manually turned the vehicle towards the right, and the steering wheel failed to perform as needed. The contact attempted to manually correct the steering wheel but was unable return the steering wheel to center because the steering wheel was independently turning to the left or the right. The contact believed that the vehicle was operating in self-driving mode; however, the vehicle was not equipped with the feature. The contact depressed the brake pedal to decelerate, almost stopping the vehicle, to regain control of the vehicle. The contact was able to drive to the destination. The contact stated that the failure had occurred while driving approximately 60 - 70 MPH, and the vehicle veered to the left and the right while the lane assist was activated. The contact depressed the brake pedal and decelerated almost to a stop to regain control of the vehicle. The manufacturer was informed of the failure, but the contact had not received a follow-up call. The failure mileage was unknown.
- Reported
- Apr 2026
- Incident date
- May 2025
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherApr 2026 · ODI 11734184 · crashDetails +Close −
Full self driving did not detect pole. I press the fsd of tesla going out of the parking lot and the car turned to the side where the pole is located hitting the side where the camera part right next to driver side. The sensor of the car did not detect completely that there is a pole on side
- Reported
- Apr 2026
- Incident date
- Apr 2026
- Mileage
- Not provided
- Outcome flags
- Crash
SuspensionApr 2026 · ODI 11732596Details +Close −
While driving, my vehicle released a loud pop and metal noise. After pulling over large bolts fell from the front of my car caused by a suspension issue. Tesla service later confirmed that the problem was due to improper torque in the suspension components, specifically the front lower links. This resulted in hardware failure, including bolts loosening or coming out of the suspension assembly. This is a serious safety concern, as it could have led to loss of control while driving. The vehicle required replacement of suspension components and hardware under warranty. This defect appears to be related to improper assembly or servicing rather than normal wear and tear. Tesla is now refusing to give me a detailed report of the manufactured defect cause.
- Reported
- Apr 2026
- Incident date
- Apr 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherApr 2026 · ODI 11732139Details +Close −
INCIDENT: On April 17, 2026 at ~8:30 AM, my 2024 Tesla Model Y was operating on FSD (Supervised) approaching Wunderlich County Park parking lot entrance, Woodside, CA. Clear daylight, 11-12 MPH, turning into the parking lot. WHAT HAPPENED: A stationary metal W-beam guardrail (~2-3m long, ~1m tall) was directly in the forward path, clearly visible. FSD failed to detect the obstacle, then silently disengaged 2 seconds before impact. TIMELINE FROM IN-VEHICLE REPLAY: - 08:30:23: Vehicle fully aligned with guardrail, direct collision course - 08:30:24: FSD actively engaged (Self-Driving indicator displayed), 12 MPH, guardrail clearly visible - 08:30:25: FSD disengaged - 08:30:27: Impact TWO FAILURES: 1) DETECTION: For ~2 sec (08:30:23-08:30:25), FSD in active control with clearly visible stationary standardized guardrail directly in path. System failed to detect, decelerate, or alter course. 2) SILENT DISENGAGEMENT: FSD disengaged at 08:30:25 with no audible alert, no haptic feedback, no visual alert in driver's forward field of view, no "Take Over" prompt. Only indication was center display change, outside driver's forward line of sight required by Tesla's Owner's Manual to keep eyes on the road. DRIVER STATE: I was monitoring road per Owner's Manual. I received no warning of FSD handoff. I had no awareness FSD disengaged. I took no manual action (no brake, no steer) because I was not notified. I discovered disengagement only upon reviewing in-vehicle dashcam replay the following day. The 2-sec interval was insufficient reaction time even for an informed driver (below AAA/NHTSA 1.5-sec baseline). Research on automated handoff indicates 3-7 sec needed even when notified. I was not notified at all. CRASH: Yes, vehicle collided with the guardrail. INJURIES: None. THIRD-PARTY DAMAGE: None. FIRE: None. CONSISTENCY WITH NHTSA PROCEEDINGS: Pattern matches concerns in Investigation PE21-020, Engineering Analysis EA22-002, Recall 23V-83
- Reported
- Apr 2026
- Incident date
- Apr 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Unknown Or OtherApr 2026 · ODI 11730715 · crashDetails +Close −
[XXX] [XXX] leaving [XXX] through residential gate using Tesla FSD, a car had passed through and the gate was closing. I expected the car to stop, it proceeded at a speed of 10 mph. The barrier struct the rear passenger side of the car. Significant damage. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Apr 2026
- Incident date
- Apr 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Electrical SystemApr 2026 · ODI 11728946 · fire · 2 injuriesDetails +Close −
On December 2, 2025, my Tesla was charging in the garage of my residence in [XXX] , when a fire appears to have originated in or around the vehicle area. Before the fire, I smelled smoke/burning and also heard popping sounds. The fire spread rapidly and resulted in the destruction of my home, creating an immediate and severe risk to the safety of all occupants and anyone nearby. This incident exposed those present to danger from flames, smoke inhalation, toxic fumes, and structural collapse, and it caused emergency evacuation and displacement. The fire department identified the garage or vehicle area as the origin. The exact component or system that failed is unknown at this time, but the circumstances indicate a possible failure involving the vehicle, charging system, battery system, or related electrical components. I am not aware of any prior battery, charging, or electrical warning messages before the incident. Emergency responders and insurance representatives were involved after the fire. I previously attempted to notify Tesla of this incident, but I did not receive a response. Because this event involved a catastrophic fire and total residential loss, I believe it should be reviewed as a serious vehicle safety matter and that all relevant vehicle data, charging data, components, and related evidence should be preserved for inspection. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Apr 2026
- Incident date
- Dec 2025
- Mileage
- Not provided
- Outcome flags
- Fire 2 injuries
Seat BeltsMar 2026 · ODI 11727359Details +Close −
Seatbeall does not click in
- Reported
- Mar 2026
- Incident date
- Mar 2026
- Mileage
- Not provided
- Outcome flags
- None reported
WheelsMar 2026 · ODI 11725046Details +Close −
These rims outter lip have a poor design and when hitting a pot all the outer lips add additional pressure and the rim causes the tire burst This is the 2nd time this has happened to me. In 2 the years I had the car. The first time it happened was in NY state
- Reported
- Mar 2026
- Incident date
- Mar 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceMar 2026 · ODI 11724655 · crashDetails +Close −
NHTSA COMPLAINT NARRATIVE — SAFERCAR.GOV Vehicle: 2024 Tesla Model Y Component/System: Full Self-Driving (Supervised) Software, Version 14.2.2.5 On March 14, 2026, at approximately 5:22 PM, a 2024 Tesla Model Y was traveling on U.S. Route 3 in Franconia, New Hampshire, at approximately 45 mph within the posted speed limit. The vehicle was operating with Full Self-Driving (Supervised) software version 14.2.2.5 actively engaged. Three occupants were present in the vehicle, including two minor passengers. All occupants were properly restrained with seat belts. Component/System That Failed: The Full Self-Driving (Supervised) system, version 14.2.2.5, failed to safely detect and respond to a snow-covered road surface. The system lost control of the vehicle upon encountering a snow patch on the roadway, causing the vehicle to strike a tree. The FSD system is the primary failed component. The vehicle has been towed and is available for inspection upon request. How Safety Was Put at Risk: The FSD system was in active control of the vehicle's steering, braking, and acceleration at the time of the failure. The system provided no auditory alert, no visual warning, and no driver takeover request prior to the loss of control event. The failure occurred without any warning whatsoever, leaving insufficient time for the driver to intervene and prevent the collision, despite the driver actively supervising the system in full compliance with Tesla's own supervision requirements. Three occupants were placed in immediate risk of serious injury or death. The vehicle struck a tree and was totaled. Emergency services responded and evaluated all occupants on scene. An official police report was filed. Prior Warning Lamps, Messages, or Symptoms: None. The FSD system issued zero warnings — no auditory alerts, no visual prompts, no haptic feedback, and no takeover requests — at any point prior to or during the loss of control event. The system was operating normally by all displayed indicato
- Reported
- Mar 2026
- Incident date
- Mar 2026
- Mileage
- Not provided
- Outcome flags
- Crash
Electrical SystemMar 2026 · ODI 11723291 · crash · 1 injuriesDetails +Close −
The contact owns a 2024 Tesla Model Y. The contact stated that while driving at 22 MPH in full self-driving mode, the vehicle inadvertently crashed into the rear driver's side of a parked vehicle on the shoulder lane. No warning light was illuminated. The other vehicle was unoccupied. The contact's front passenger side sustained damage. The contact stated that the automatic emergency braking system activated moments before the crash, but it was too late to prevent the collision. The air bags did not deploy. The contact suffered from cervical strain and rib contusion and received medical attention for the injuries. A police report was filed. The vehicle was towed to a body shop and was not deemed totaled by the insurance company. The manufacturer was not made aware of the failure. The failure mileage was approximately 25,000.
- Reported
- Mar 2026
- Incident date
- Mar 2026
- Mileage
- Not provided
- Outcome flags
- Crash 1 injuries
SuspensionFeb 2026 · ODI 11720600Details +Close −
Component/System: Braking System (Caliper Bolt) and Suspension (Control Arm/Linkage Bolt). Description of Incident: While traveling on a tollway at 70 mph, I heard a faint noise followed by a severe metallic scratching sound coming from the front driver-side wheel. Upon inspection at a tire service center, it was discovered that a brake caliper bolt had fallen out, causing the caliper to displace and score the inner rim of the wheel. The vehicle was towed to a Tesla Service Center, where the caliper and wheel were replaced under warranty. Tesla could not identify a root cause but stated they performed a quality check on all remaining wheels. Subsequently, a second failure occurred on the front passenger-side wheel. A different bolt—this time related to the suspension—loosened or fell out. The vehicle produced a severe grinding noise and felt unstable, as if the wheel was about to dislodge. Safety Risk: Both incidents posed an immediate risk of catastrophic mechanical failure at high speeds. A detached brake caliper can lead to total loss of braking or wheel lock-up, while a suspension bolt failure can cause a complete loss of steering control. Either scenario could have resulted in a high-speed collision, endangering my life and the lives of my two children. Confirmation/Inspection: • Confirmed by Dealer: Yes, Tesla Service Center performed repairs on both occasions. • Available for Inspection: The vehicle has been repaired, but service records and photos of the damage/missing bolts are available. • Other Inspections: Initial driver-side failure was visually confirmed by Discount Tire. Warning Signs: There were no dashboard warning lamps or messages. The only symptoms were a brief "pop" or "click" followed immediately by loud metal-on-metal grinding and vibration.
- Reported
- Feb 2026
- Incident date
- Oct 2025
- Mileage
- Not provided
- Outcome flags
- None reported
Lane DepartureFeb 2026 · ODI 11720823Details +Close −
Vehicle: 2023 Tesla Model Y VIN: [XXX] Mileage: Approximately 40,531 miles Software Version: 2025.45.9 FSD (Supervised) Version: v14.2.2.4 While driving on [XXX] near the [XXX] entrance in Mission Viejo, California, the vehicle was operating under Full Self-Driving (Supervised) mode. As the freeway lane ended/merged, the vehicle unexpectedly performed a sudden full stop at freeway speed. There was no visible obstruction in front of the vehicle. Multiple vehicles behind me had to brake abruptly to avoid a rear-end collision. The system did not provide any audible or visual warning before the sudden braking. This has created a serious safety risk due to the high-speed freeway environment. This issue appears to be related to lane-ending or merge interpretation by the FSD system. I am concerned that this behavior could result in a rear-end collision. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Feb 2026
- Incident date
- Feb 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceFeb 2026 · ODI 11720180Details +Close −
When Adaptive cruise control is on random phantom braking occurs. It can be very severe and drops speeds of 20-30 miles within seconds. Occurs on highways and is random and occurs daily. ( multiple times in a day) Has been serviced 4 times and Tesla cleans the cameras and adjusts them. It has progressively gotten worse and Tesla said don't bring it in because they cannot fix it. They describe it as a software update.
- Reported
- Feb 2026
- Incident date
- Dec 1969
- Mileage
- Not provided
- Outcome flags
- None reported
Electrical SystemFeb 2026 · ODI 11719238 · 1 injuriesDetails +Close −
Driver side front window auto rolled back up after pressing the button to once to roll it down. This happened while driving while the right hand was on the steering wheel. The left hand got caught inbetween the window glass and the window frame as it auto rolled back up on its own. It caused bleeding and pain to the left hand.
- Reported
- Feb 2026
- Incident date
- Feb 2026
- Mileage
- Not provided
- Outcome flags
- 1 injuries
SteeringFeb 2026 · ODI 11716888 · crash · fire · 3 injuriesDetails +Close −
On Saturday morning January 3, 2026 I was driving with my wife, daughter and dog. There was light rain at the time and I had my adaptive cruise set at approximately 72 mph. I was driving our 2024 Tesla Y. At approximately 10:21am the rear of car began to slide right as we entered gradual left curve, possibly because we hit water on road. I tried to slightly correct right and when I did that the steering wheel aggressively corrected back left which put us into a slide. Within a second we hit a tree on the passenger side. The impact was severe and on the passenger side door where my wife was sitting. At that time I theorize that my dog was ejected out of the back window and thrown across the freeway. We then rolled in the other direction (I dont know how many times) down a hill and settled upside down. I immediately smelled smoke and began to try get out of my seatbelt but I couldn’t. I carry a knife and I was able to cut myself out. I then tried to open door and could not so I began punching the glass and eventually got it moving and pushed on it and got it open. I slid myself out, turned around and saw car was on fire. I pulled my daughter out and then began extracting my wife. She was unconscious and had obvious orthopedic injuries. I am 100% confident that had I been driving my other vehicle (non Tesla) that this accident would have NOT occurred. The Tesla and its steering system caused this accident. On top of that, the batteries immediately caught fire, my seatbelt release button did not work, and the electric door button did not work. Had I not been carrying a knife and strong enough to punch door open this story would have ended up differently. The car completely burned. As far as I know, this was the first time this exact issue presented itself. However, when looking online its seems this issue is fairly common with Teslas in wet weather.
- Reported
- Feb 2026
- Incident date
- Jan 2026
- Mileage
- Not provided
- Outcome flags
- Crash Fire 3 injuries
Unknown Or OtherFeb 2026 · ODI 11716341Details +Close −
The emergency mechanical levers for BOTH of my front doors do not work at all. I pull them while pushing the door and they do not open the car. If the power dies in the car, there is no way for me or my passenger to escape the car. I reported this to Tesla and they are not able to immediately investigate it or provide me replacement vehicle.
- Reported
- Feb 2026
- Incident date
- Feb 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Power TrainFeb 2026 · ODI 11715422Details +Close −
Tesla Model Y 99,000 km It is known issue with many driver of same model and milage that Wire Harness connected to Oil pump gets hot and damage. This can also cause fire. Many people have been complaining about similar issue on Facebook group.
- Reported
- Feb 2026
- Incident date
- Jan 2026
- Mileage
- Not provided
- Outcome flags
- None reported
Forward Collision AvoidanceFeb 2026 · ODI 11714750 · crash · 3 injuriesDetails +Close −
Tesla's full self-driving software continues to malfunction. On January 30th at 9:50 a.m. mountain standard Time I was parked at work and discovered my vehicle was left unlocked with a partial window unrolled. This was my first indicator of many faulty problems signaling the vehicle was not operating properly. The vehicle has a proximity sensor via Bluetooth that locks and unlocks the vehicle on the owners approach was not properly working. On January 31st I experience a catastrophic failure with the software of the vehicle as I was locked out of my vehicle after utilizing summons feature that stopped the vehicle in the middle of the intersection obstructing traffic. Police arrived on scene within 30 minutes and we were unable to put the car in any gear to either drive the vehicle or place it in neutral to roll it out of the way. I have detailed video of the incident which is a better accounting of the incident on both occasions, the 30th and 31st of January. This is roughly the third or fourth occasion of Tesla's system producing a catastrophic failure resulting in damage to the vehicle or property damage.
- Reported
- Feb 2026
- Incident date
- Jan 2026
- Mileage
- Not provided
- Outcome flags
- Crash 3 injuries
Electrical SystemJan 2026 · ODI 11712254Details +Close −
Vehicle experienced PCS (Power Conversion System/DC-DC converter) failure, rendering it completely undrivable—no 12V power, cannot charge or start. PCS is physically integrated inside high-voltage battery pack per service manuals. High-voltage battery warranty active (8yr/120k miles). Tesla service denies coverage citing "associated component" in vague emails—provided only general warranty table, no specific exclusion language despite repeated requests for exact quote/formal written denial. Escalated to managers: Offered "view-only" internal service bulletin on screen at meeting—no print/copy/photo allowed. Explicitly refused formal written denial letter.
- Reported
- Jan 2026
- Incident date
- Jan 2026
- Mileage
- Not provided
- Outcome flags
- None reported
SteeringJan 2026 · ODI 11710550 · crashDetails +Close −
On [XXX], while operating my 2024 Tesla Model Y in Full Self-Driving (Supervised) mode, the vehicle experienced an Uncommanded Steering Input leading to a collision. The vehicle was traveling at a very low speed of approximately 5 mph in a clear, simple environment. Despite this walking pace, the FSD software failed to identify a visible concrete curb and initiated a sudden, sharp turn directly into the obstacle without any prior warning or driver input. The fact that the system executed such a violent and erroneous maneuver at 5 mph indicates a fundamental failure in the Neural Network's object detection and path planning logic. If this logic failure had occurred at higher speeds or near pedestrians, the results could have been catastrophic. The local Tesla Service Center (Watertown, MA) refused to conduct a physical inspection or a log review of the steering torque. They issued a Repair Estimate of $1,217.26 while claiming 'no hardware fault codes' were present, thus ignoring the documented software malfunction. As a leaseholder of this vehicle with only 15,489 miles, I am reporting this as a significant safety defect that the manufacturer refuses to investigate. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
- Reported
- Jan 2026
- Incident date
- Jan 2026
- Mileage
- Not provided
- Outcome flags
- Crash
This page shows the latest 50 reports to keep it usable. The count above includes every complaint NHTSA has returned for this model year.
Recalls(5)
Open a recall to read what NHTSA says is wrong, what can happen, and how it gets fixed. Check the VIN and remedy eligibility with a dealer; federal no-charge requirements have an age limit, though a manufacturer may offer more coverage.
Back Over PreventionJul 2025 · 25V002000Details +Close −
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.
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.
Open full NHTSA recall record →Electrical System · 24V051000Details +Close −
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.
Remedy: Tesla began releasing an over-the-air (OTA) software update, free of charge. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-24-00-003.
Open full NHTSA recall record →Latches/Locks/Linkages · 24V554000Details +Close −
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.
Remedy: Tesla has released an over-the-air (OTA) software update, free of charge. Owner notification letters were mailed September 24, 2024. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-24-00-012.
Open full NHTSA recall record →Seats · 24V886000Details +Close −
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.
Remedy: Tesla service will replace the seat assembly, free of charge. Owner notification letters were mailed January 21, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-24-13-004.
Open full NHTSA recall record →Tires · 24V935000Details +Close −
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.
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.
Open full NHTSA recall record →A campaign can apply to this model year without being incomplete on a specific vehicle. Check the VIN with NHTSA or a dealer to confirm whether a particular car needs repair.
Investigations
7 NHTSA investigations on record
Investigations are agency reviews, not findings that a vehicle is defective.
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.
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.
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
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.
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 modifications by Tesla to the FSD system that may affect the performance of FSD in degraded roadway visibility conditions, including the timing, purpose, and capabilities of any such 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. During this phase of the investigation, ODI reviewed the materials provided by Tesla detailing any actions taken, or changes, modifications, and updates made that may relate to the alleged defect. ODI reviewed information related to Tesla’s transition to a vision-only perception system, and its deployment of the strategy in vehicles. ODI’s findings include information on limitations of the vision-only perception system and updates made in response to known subject crashes. 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. ODI reviewed certain public statements, including those made during an April 2025 earnings call, in which Tesla stated that it had developed a breakthrough “direct photon-counting” capability that eliminates the degradation that the camera-based system experiences when glare is encountered. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI has discussed individual incidents and its initial findings with Tesla. Based on Tesla’s post-incident analysis, 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. 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. 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 FSD system fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants where the camera-based system performance degrades significantly. In the crashes that ODI has reviewed, the FSD system did not detect common roadway conditions that impaired its visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. ODI is upgrading this investigation (PE24031) to Engineering Analysis (EA) 26002 to further evaluate this matter. 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.
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 system’s controls may be insufficient to prevent driver misuse,” and Tesla committed to the deployment of a multipart remedy aimed at improving system and engagement controls and reducing mode confusion. EA22002 (upgraded from PE21020) was opened to investigate whether Tesla’s Autopilot contained a defect that created an unreasonable risk to motor vehicle safety and involved extensive crash analysis, human factors analysis, vehicle evaluations, and assessment of vehicle control authority and driver engagement technologies. The work conducted in these investigations aligns with Tesla’s conclusion in its 23V838 recall filing. During EA22002, ODI identified at least 13 crashes involving one or more fatalities and many more involving serious injuries in which foreseeable driver misuse of the system played an apparent role. Tesla filed Recall 23V838 to address concerns regarding the Autopilot system investigated in EA22002. Following deployment of the remedy in Recall 23V838, ODI identified concerns due to post-remedy crash events and results from preliminary NHTSA tests of remedied vehicles. Also, Tesla has stated that a portion of the remedy both requires the owner to opt in and allows a driver to readily reverse it. Tesla has also deployed non-remedy updates to address issues that appear related to ODI’s concerns under EA22002. This investigation will consider why these updates were not a part of the recall or otherwise determined to remedy a defect that poses an unreasonable safety risk. ODI is therefore opening this Recall Query investigation to further evaluate the adequacy of the remedy for recall 23V838.
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 resulting safety issues in the subject vehicles. The alleged defect is an unexpected and unrequested vehicle deceleration triggered by the subject system during subject system engagement. The alleged defect does not occur when the subject system is not in use and is separate and distinct from Automated Emergency Braking (AEB). During vehicle operation, AEB is actively monitoring in the subject vehicles regardless of subject system and its intervention is accompanied by audible and visual collision warnings. A Vehicle Owners Questionnaire (VOQ) trend originating in November 2021 prompted ODI to open PE22002. VOQ narratives reported unexpected brake activation while using TACC, Autopilot or FSD. The trend grew from 99 by the end of 2021 to 314 by February 16, 2022, when PE22002 was opened. ODI sent Information Request (IR) Letters to Tesla on May 4, 2022, and July 11, 2024, to request salient data to quantify vehicle production, field incidents, and the physical parameters of the phantom braking reports. ODI also requested information pertaining to Tesla’s internal assessments, problem resolutions, and their assessment of the alleged defect. Typically, the complaints to ODI and Tesla allege a 10-20 mph speed reduction at highway speeds over a 1-3 second time period.No collisions were identified. Drivers reported seeing no vehicles ahead in the travel lane that would have triggered the deceleration. Many complaints reported the conditions taking place on higher speed roadways in sunny conditions with shadows on the roadway. Complainants typically applied the accelerator to override the unexpected deceleration, and subject vehicles did not come to a complete stop or steer out of their travel lane. ODI analyzed data provided by Tesla in addition to consumer complaints submitted to ODI. Tesla’s complaint and field data exhibited some behavior that aligned with the transition from a radar-vision fusion system to vision-only in mid-2021. VOQ traffic coincided with public events such as Recall 21V846, the opening of PE22002, and several related media publications. In February and March of 2022, Tesla released firmware updates 2022.4.5.1 and 2022.4.5.17 respectively to target aspects of the subject system programming that affect unexpected deceleration. Incident traffic has dissipated substantially in the past years, with 45 incidents reported in 2024, 19 in 2025, and 3 since the beginning of 2026. The conditions reported, while concerning to the drivers, did not alter the vehicle’s lateral positioning in their lanes and did not cause significant loss in distance between the subject and following vehicle to lead to a collision. Complaint traffic to both NHTSA and Tesla reported the same conditions- vehicles traveling with the subject system engaged at higher speeds decelerating suddenly with no commensurate vehicle or obstacle ahead in the same lane. In view of these points, and a low demonstrated hazard to drivers, this Preliminary Evaluation (PE) is closed. The closing of this investigation does not constitute a finding by NHTSA that a safety-related defect does not exist. The Agency reserves the right to take additional action if warranted by future circumstances. To review the ODI reports cited in the Closing Resume ODI Report Identification Number document, go to NHTSA.gov.
Crash-test ratings
No NHTSA crash test is on record for this year. Some vehicles and model years were not tested or do not have a published NCAP result.
Fuel economy by trim
| Trim | Engine | Drivetrain | Transmission | City | Hwy | Combined |
|---|---|---|---|---|---|---|
| Model Y RWD | — | Rear-Wheel Drive | Automatic (A1) | 128 | 112 | 120 |
| Model Y Long Range RWD | — | Rear-Wheel Drive | Automatic (A1) | 128 | 112 | 120 |
| Model Y Long Range AWD-I | — | All-Wheel Drive | Automatic (A1) | 123 | 112 | 118 |
| Model Y Long Range AWD | — | All-Wheel Drive | Automatic (A1) | 122 | 112 | 117 |
| Model Y Performance AWD | — | All-Wheel Drive | Automatic (A1) | 111 | 98 | 105 |
EPA laboratory estimates by trim and engine. Actual mileage varies with driving, weather, load, and maintenance. EPA source.
Before you buy
Useful next checks
Federal records tell you about patterns. These checks can tell you more about the specific car in front of you.
These are affiliate links. TireKick may earn a fee if you use one.
Compare the year-by-year record
Open another year for its own evidence-gated decision. TireKick does not crown a best year from raw complaint totals.
2024 Tesla Model Y: frequently asked
What does the complaint record show for the 2024 Tesla Model Y?
Owners filed 299 NHTSA complaints about the 2024 Tesla Model Y. This is raw owner-reported complaint volume with no production or exposure normalization, so it is not a reliability score or a best/worst-year ranking.
What are the most common problems on the 2024 Tesla Model Y?
The most-reported problem areas are Electrical System (17% of complaints) and forward collision avoidance (17%).
How many recalls does the 2024 Tesla Model Y have?
5 recalls have been issued that affect the 2024 Tesla Model Y, covering components such as back over prevention. Check the VIN with NHTSA and ask a dealer to confirm remedy eligibility; federal no-charge requirements have an age limit, though manufacturers may offer more coverage.
What gas mileage does the 2024 Tesla Model Y get?
The EPA rates the 2024 Tesla Model Y between 105 and 120 mpg combined, depending on trim and drivetrain.