What 292 owners told NHTSA about the 2024 Tesla Model Y

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.

NHTSA ODI 11747817

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.

NHTSA ODI 11745089

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.

NHTSA ODI 11743816

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)

NHTSA ODI 11743171

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)

NHTSA ODI 11742365

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)

NHTSA ODI 11741960

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.

NHTSA ODI 11742029

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.

NHTSA ODI 11736067

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.

NHTSA ODI 11735191

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

NHTSA ODI 11724655

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)

NHTSA ODI 11720823

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.

NHTSA ODI 11720180

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.

NHTSA ODI 11716888

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.

NHTSA ODI 11714750

Incident Description (in my own words): We were driving southbound on [XXX] from New Hampshire back to Boston in our Tesla Model Y. Traffic became increasingly congested and slowed to a crawl. My wife was driving, and I was in the front passenger seat working on my laptop. As traffic built up, my wife became momentarily distracted and did not apply the brakes in time. I noticed, in my peripheral vision, the vehicle ahead of us—a truck—suddenly filling the windshield. At that point, I heard the forward collision warning alert, but it activated extremely late, essentially at the moment of impact. The vehicle did not automatically brake or stop, despite the low speed, close proximity, and clear visibility of the truck ahead. We collided with the truck in front of us. Damage was minimal (license plate damage and a small dimple on the front of the vehicle), but the safety concern is significant. Both of our Teslas are configured with forward collision warning set to “Early.” Under normal circumstances, this alert triggers frequently, sometimes conservatively. In this incident, however, the warning activated far later than expected, and there was no automatic braking intervention prior to impact. The front camera appeared clean and unobstructed. I am filing this complaint because this behavior undermines my confidence in the vehicle’s collision avoidance and automatic emergency braking systems. I am also filing a similar complaint for our Tesla Model 3. I am now anxious about whether the software will perform as expected in situations where driver attention lapses briefly—precisely the scenario these safety systems are designed to mitigate. I am requesting that NHTSA review this issue, as the system did not behave in a manner consistent with its intended safety function. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ODI 11709512

Autopilot was engaged and active at the time of the incident. The vehicle failed to detect a stationary piece of road debris (appearing to be a dropped vehicle part) located in the driving lane. The system did not provide any warning, slow the vehicle, or attempt an avoidance maneuver. The vehicle drove directly over the debris, resulting in damage to the lower exterior/body panel. Road and traffic conditions were normal. This raises concerns about Autopilot’s object detection and hazard response capabilities.

NHTSA ODI 11708026

My 2024 Tesla Model Y hit a parked vehicle on the right side of the street during FSD self driving. The car suddently slanted to the right and hit the parked vehicle. During FSD drive, it did not give any warning before the accident. My dauther was injured on her face. Clearly the new version FSD v14.1 software is very defective. I am located in San Jose, CA.

NHTSA ODI 11702107

My vehicle’s auto-high beam system does not properly recognize other traffic. It specifically fails to substantially dim the high beams when approaching oncoming vehicles or when behind other traffic on roadways. I have reported this to the manufacturer and attempted to have the dealership fix this on multiple occasions. The dealerships insist that the vehicle dims the required number of pixels in the headlights to not blind other drivers. However, this does not appear to be effective as other drivers that I have followed behind reported that they were being blinded by my highbeams while I was behind them. There is a notable difference between the highbeams and the low beams which the car fails to substantially adjust for when using this required feature to utilize the self driving/auto pilot feature.

NHTSA ODI 11701947

I am writing to report critical safety issues I’ve experienced while using Tesla’s Full Self-Driving (FSD) software version 14.1.3. The recent update has introduced several dangerous behaviors that were not present in previous versions. One issue occurs frequently on neighborhood roads: the vehicle performs sudden emergency braking for no valid reason. For example, during one drive, it abruptly stopped because a few leaves blew across the road. There were no pedestrians, vehicles, or real obstacles present. These false-positive braking events are alarming and could easily cause a rear-end collision. An even more concerning issue arises during highway driving. The car now repeatedly swerves partially into adjacent lanes—without signaling—and then abruptly returns to its original lane. This happens constantly, even in light traffic, and it did not occur in previous versions of the software. This erratic behavior is incredibly dangerous and could easily cause sideswipe accidents or create confusion for surrounding drivers. It is clear that version 14.1.3 is a regression from earlier versions. The system’s decisions are more erratic, less confident, and frequently unsafe. I no longer trust the FSD to operate reliably in environments where it previously performed well. I urge your agency to investigate this software update as it presents a real and growing hazard on public roads.

NHTSA ODI 11699446

While driving ~40 mph with no Autopilot or cruise control active, my 2024 Model Y suddenly braked itself from 40 → 0 mph for no reason. The road ahead was clear. I did not touch the brake. My 3-year-old was in the car. We were nearly rear-ended and could have been seriously injured. When I went to Tesla Service, the manager insisted I must pay a $270 diagnostic fee unless they “find a problem,” while also saying the incident was likely caused by “shadows.” This makes me believe they will simply say “no issue found” and charge me despite this being a severe safety malfunction. When I reached out to Tesla Customer Support, they stated it was a known issue. This poses a serious risk of rear-end collisions, injuries, or fatality, and Tesla is not addressing it.

NHTSA ODI 11699280

On November 8, my 2024 Model Y suddenly came to a complete stop from about 40 mph while I was driving with no cruise control or Autopilot active. This was extremely dangerous — my [XXX] was in the car, and we were lucky no one was behind us. It put myself, my child, and others in the absolute risk of collision and injury. When I contacted the service center they said it sometimes happened due to "shadows" or "sun". They refused to run a diagnostic on the car for free and wanted me to pay for it. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ODI 11698990

Tesla removed the speed limit offset feature in FSD version 14.1.4 and now only uses speed profiles called Sloth, Chill, Standard, Hurry, and Mad Max, and this has made my car extremely unsafe to drive. The problem is that these profiles make the car go either way too slow or way too fast and I cannot adjust it to match actual traffic conditions anymore. To make matters worse, the speed limit detection is broken and frequently shows the wrong speed limit for the road I am on. When I use Sloth, the car never goes over the detected speed limit no matter what, so if the system thinks I am in a 35 mph zone when I am actually on a 55 mph highway, my car crawls along at 35 while traffic is flying past at 60-70 mph. I have people tailgating me, honking, flashing their lights, swerving around me dangerously, and I have almost been rear-ended multiple times because my car is going so much slower than everyone else. Without the ability to set a maximum speed offset, I am stuck going whatever speed the broken detection system thinks is right. If I switch to Standard, Hurry or Mad Max to try to keep up with traffic, sometimes the car goes way too fast for the actual conditions or blows through school zones and residential areas at unsafe speeds. I cannot fine-tune the speed anymore to drive safely with the flow of traffic. I am forced to either be a rolling roadblock and risk getting hit from behind, or use an aggressive profile that might go dangerously fast. This happens every single time I use FSD now and the combination of broken speed limit detection plus no manual offset control has created a seriously unsafe situation. I feel endangered every time I drive and I am genuinely worried about causing or being in an accident.

NHTSA ODI 11696674

Recently Tesla released it's latest version of FSD, v14.1.4. One of the key features is the revamping of the driving modes: sloth, chill, standard, and mad max. Tesla also removed the ability to manually increase or decrease the speed of the car. This is a problem. Let me illustrate it with a real-life example. Yesterday I was driving of a 40 mph road and the car correctly set the speed. I was using the standard mode so the car allowed an overage of around 10% so the actual speed was 45 mph. In our area this is typical for most drivers. As we entered a village, the posted speed limit was changed to 30 mph. The panel was perfectly visible and readable. The car did not register it and continued at 45 mph. I changed to mode to "sloth" and the car decreased its speed to 40 mph but I was still 10 mph above the legal speed limit. I came across a second 30 mph panel and again the car "ignored" it. Because I did not have the ability to manually reduce the speed of the car, I had to disengage FSD and drive the car by myself. Tesla claims FSD must be supervised. Fine. But removing the ability to manually change the speed of the car should be a requirement not a design preference.

NHTSA ODI 11695980

New update to ASDS software allows the vehicle to do 15-25+ over the speed limit and no ability to control. This is unsafe and Tesla took away the ability to control speed. Either engaged or not, this is completely unacceptable and they seem set on this being the only way to go.

NHTSA ODI 11695948

There was a sudden unintended acceleration and the brake did not work, causing a major accident. Car caught fire and door would not open. The car has completely engulfed. There were no warning lamps, messages or other symptoms prior to the failure. Vehicle has been inspected by insurance and police, but not by manufacturer.

NHTSA ODI 11695221