2026 Tesla Model Y
Safety record from NHTSA: recalls, owner complaints, investigations and service bulletins.
Vehicles › Tesla › Model Y › 2026
Safety record from NHTSA: recalls, owner complaints, investigations and service bulletins.
These records cover every 2026 Tesla Model Y. To see whether one car still needs a recall repair, decode its VIN or check it with NHTSA.
8 recalls name the 2026 Tesla Model Y. Newest first.
Tesla, Inc. (Tesla) is recalling certain 2026 Model Y vehicles. One or more front suspension lateral link fasteners may not have been properly tightened, allowing the lateral link to loosen or separate from the sub-frame.
A lateral link separation could shift the wheel alignment, causing a loss of vehicle control and increasing the risk of a crash.
Tesla Service will tighten or replace the fasteners and check wheel the alignment, free of charge. In addition, Tesla Service will replace any related parts that may have been damaged as necessary. Owner notification letters are expected to be mailed October 30, 2026. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-26-31-004.
Tesla, Inc. (Tesla) is recalling certain 2026 Model Y and 2024 Model 3 vehicles. The vehicles were originally built for a foreign market and do not have knee air bags, may not be equipped with certain interior safety countermeasures, and may not have been tested for bumper impact resistance procedures. As such, these vehicles fail to comply with the…
A noncompliant vehicle may have reduced occupant protections, increasing the risk of injury during a crash.
Tesla will repurchase noncompliant vehicles currently registered in the United States, free of charge. Owner notification letters were mailed September 4, 2026. Owners may contact Tesla customer service at 1-877-798-3752 or resolutions@tesla.com. Tesla's number for this recall is SB-26-00-004.
Tesla, Inc. (Tesla) is recalling certain 2025-2026 Model Y vehicles. The certification label may not have been installed. As such, these vehicles fail to comply with the requirements of 49 C.F.R. Part 567, "Certification."
Missing weight information provided by the label may lead to unintentionally overloading the vehicle, increasing the risk of a crash.
Tesla Service will inspect and install a certification label as necessary, free of charge. Owner notification letters were mailed July 17, 2026. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-26-19-002.
Tesla, Inc. (Tesla) is recalling certain 2025 Model 3 and 2026 Model Y vehicles. The battery pack contactors may fail, causing a loss of drive power.
A loss of drive power can increase the risk of a crash.
Tesla Service will replace the battery pack contactors, free of charge. Owner notification letters were mailed December 9, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-16-005.
Tesla, Inc. (Tesla) is recalling certain 2026 Model Y vehicles. The reverse lights may fail to illuminate while the vehicle is in reverse, due to a defect in the wiring. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 108, "Lamps, Reflective Devices, and Associated Equipment."
Reverse lights that fail to illuminate reduce visibility and may not alert pedestrians or other drivers that the vehicle is backing up, increasing the risk of a crash.
Tesla Service will replace the reverse lights and reverse facia harness, free of charge. Owner notification letters were mailed November 26, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-17-011.
Tesla, Inc. (Tesla) is recalling certain 2026 Model Y vehicles. The ring terminal of the horn ground wire may be improperly secured, allowing the circuit to open and preventing the horn from sounding.
An inoperable horn may prevent the driver from alerting other drivers as needed, increasing the risk of a crash.
Tesla service will replace the steering wheel, free of charge. Owner notification letters were be mailed September 23, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-17-009.
Tesla, Inc. (Tesla) is recalling certain 2026 Model 3 and Model Y vehicles. The fasteners attaching the seat back to the seat bottom may have been improperly tightened.
The seat may not properly restrain the occupant, increasing the risk of injury during a crash.
Tesla Service Centers will inspect and tighten or replace the seat assembly fasteners as necessary, free of charge. Owner notification letters were mailed August 16, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-13-003.
Tesla, Inc. (Tesla) is recalling certain 2026 Model Y vehicles. The hose connector may block the windshield washer nozzles, preventing washer fluid from reaching the windshield. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 104, "Windshield Wiping and Washing Systems."
The inability to clean the windshield reduces the driver’s visibility and increases the risk of a crash.
Tesla service will inspect and replace the wiper arm elbow connector as necessary, free of charge. Owner notification letters were mailed July 25, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-20-001.
I am reporting a serious safety incident involving my 2026 Tesla Model Y while using Full Self-Driving (Supervised). While my vehicle was making a left turn with FSD engaged, the system unexpectedly disengaged midway through the maneuver. Instead of completing the left turn, the vehicle continued traveling straight toward a parked car. I immediately attempted to take control and correct the vehicle's direction, but there was insufficient time to avoid the collision. I received no apparent advance warning before the disengagement. Additionally, the forward collision warning and automatic emergency braking systems did not appear to activate or intervene before impact. The collision caused significant damage to the front passenger-side bumper of my Tesla, requiring the vehicle to be towed. The vehicle subsequently underwent repairs, leaving me without transportation for approximately one month. I had been using Tesla's FSD system regularly for several months before this incident. I reported the incident to Tesla and contacted its FSD malfunction team, but I have not received a response, investigation findings, or an explanation regarding the unexpected disengagement and apparent lack of collision avoidance intervention. I am concerned that FSD may unexpectedly disengage during an active turning maneuver without sufficient advance warning or time for the driver to react. The apparent lack of collision warning or automatic emergency braking intervention further raises concerns about vehicle safety. I am requesting that NHTSA investigate this incident and determine whether a malfunction or safety defect contributed to the crash.
The company markets the Quick Bandit license plate holder for the Tesla Model Y 2026 Juniper, stating it "does not obstruct Autopilot front camera or sensors." After installing the holder, during FSD (self-driving mode), the Tesla began stopping suddenly on roads and freeways. After stopping, the car will not move because the front camera is seeing non-existent people, as indicated on the screen display. This is a dangerous situation, which could result in a rear-ending accident. After many visits to the Tesla service department, it was diagnosed that the vertical brackets of the holder are causing the cameras to see non-existent pedestrians. I've reported the issue to Teslarati customer service and sent pictures of the problem, but they've responded only once and provided no resolution. They are now ignoring my emails and will not post my reviews. Their product is causing a serious road hazard.
On October 28, 2026 at about 3:57 PM EDT, my 2026 Tesla Model Y (Long Range RWD) was operating on Full Self-Driving (Supervised) as it turned left into our residential driveway in Watkinsville, GA. A family member's parked Subaru Forester was on the left side of the driveway with its right rear passenger door standing open. An adult was leaning into that doorway and a child was standing beside the car. The Tesla's dashcam (left pillar camera) shows the open door clearly in view for 6 to 8 seconds before contact. Despite this, Full Self-Driving did not stop or steer away. It slowed to about 2 mph but kept creeping forward alongside the Subaru, and the Tesla's left rear quarter panel struck the edge of the open door. The vehicle data export shows Full Self-Driving active and steering throughout, with no accelerator or brake input from me and near-zero steering torque from the driver. No forward collision warning or automatic emergency braking event was recorded. I braked about 5 seconds after contact, which disengaged Full Self-Driving. No one was injured, but a person was standing in the door opening the car struck. The Tesla has a V-shaped dent and gouge in the left rear quarter panel, with the paint cut through. Estimated repair cost is over $5,000. I expected the system to detect a stationary open door with a person in it and either stop or steer around it. I have the dashcam footage from all six cameras and Tesla's vehicle data export, and can provide both.
On October 20, 2026, at approximately 8:14 PM, I was starting a drive from a parked position in a parking garage. I engaged Full Self-Driving (Supervised), software version 14.3.10. Within less than 2 seconds of engagement, the vehicle moved forward and struck a concrete support pillar. I was seated in the driver's seat and supervising, but the vehicle hit the pillar before I could intervene. Failed systems: FSD (Supervised) steered the vehicle into a stationary, clearly visible obstacle. Automatic emergency braking did not prevent the collision. Safety risk: The vehicle drove into a fixed structure in a garage used by pedestrians and other vehicles. The same behavior near a pedestrian could cause serious injury. [No one was injured.] Warnings before the crash: None Evidence: I have the vehicle's dashcam footage of the collision. The clip's embedded telemetry shows FSD (Supervised) was active at the moment of impact. Footage is available on request. Inspection: The vehicle was inspected by the insurer and repaired at a Tesla-approved collision center. The problem has not been reproduced by a service center. The vehicle is available for inspection on request.
On October 27, 2026, my 2026 Tesla Model Y experienced a serious front hood safety incident. Before the incident, the hood would not fully latch closed and could not be reopened using the touchscreen or Tesla app. The vehicle displayed a hood warning and restricted acceleration. I contacted Tesla Roadside Assistance but was informed that complimentary towing was unavailable because the vehicle was considered drivable. I proceeded toward Tesla for service at a very low speed, approximately 16 mph or less. While traveling downhill on the freeway, the vehicle briefly reached approximately 30 mph. The hood suddenly flew open and struck the windshield, causing extensive cracking and severely compromising visibility. Fortunately, no one was injured. After the incident, the responding police officer observed that the hood could latch closed, although it had been unable to close properly beforehand. The vehicle was delivered to a Tesla-owned Collision Center and has since been disassembled. I have requested preservation of the original components, diagnostic data, and inspection records. The exact cause remains unknown, and Tesla's technical investigation is pending. I am concerned about a possible failure of the primary or secondary hood latch mechanism. This incident created a serious risk of losing visibility and control of the vehicle. I request that NHTSA investigate whether this represents a potential safety defect that could affect other Model Y vehicles.
Subject: Suspected Sudden Unintended Acceleration While Reversing — Tesla Collision on October 25, 2026 On October 25, 2026, at approximately 11:00 AM Pacific Time, I experienced an unexpected acceleration incident while reversing my Tesla on my property. I was reversing slowly when the vehicle lightly contacted another car that I own. Immediately afterward, the Tesla unexpectedly accelerated backward at a much higher speed and struck my garage with considerable force. The garage impact brought the Tesla to a complete stop. The vehicle subsequently moved forward and stopped. Fortunately, nobody was in the vehicle's path. However, the incident created a serious risk of injury, particularly if children or pedestrians had been nearby. I visited a Tesla Service Center after the incident. I was instructed to obtain a Tesla privacy data report, but I have not yet received a technical explanation. My preliminary review of Tesla's vehicle data indicates that the recorded accelerator signal increased from approximately 4.4% to 100%, reverse speed reached approximately 12.4 mph, and a crash-related event and braking activity were registered. I do not remember my exact foot position during the incident. I cannot determine whether the acceleration was caused by physical pedal input, an electronic or mechanical fault, or another factor. I am requesting that NHTSA review this incident as a potential vehicle safety concern. My primary objective is to understand what happened and help prevent similar incidents from causing serious injury or death. I can provide the original Tesla privacy report, photographs, and additional details upon request.
The contact owns a 2026 Tesla Model Y. The contact stated that for children or individuals with a small frame, the rear seat belt rode up across the neck instead of resting across the chest. The contact stated that the issue was a safety hazard and might cause a choking issue in the event of a crash. The dealer was contacted and stated there was no way to adjust the seat belt. The manufacturer was contacted by phone and made aware of the failure.
The contact owns a 2026 Tesla Model Y. The contact stated that while driving with the FSD engaged at approximately 2 MPH, while approaching a stop sign, the vehicle failed to come to a complete stop. In addition, the nearby board patrol witnessed the event and was able to advise the contact to stop the vehicle. The brake pedal was depressed, and the vehicle came to a stop. The failure mileage was approximately 96,038.
In regards to degradiation of driveway battery in my Tesla model Y I have lost 7.3 % of range vehicle now has 21,601 miles. The battery is at 90% health that the on board diagnosis has computed I’ve owned this Teslafor 18 months normal driving 17 times at the supercharger hall charging at level two at home. I feel that this battery pack made by Panasonic is degrading faster than expected, even though I have no faults or alerts. I believe this is unacceptable. I am hearing the same across the country. I have reported it to the Tesla service team and they say this is normal. I wish for a recall and or replacement.
Driver seat frame, cushion and backrest moves from side to side during cornering. This issue has gradually gotten worse, to a point that just shifting my body weight on the seat is able to move it. Tesla service center says it is within specification, but it does not feel safe.
The tesla while on FSD navigated me to Truck Ramp. I didn't have time to react. It didn't even warn. The car bounced 3 times and I had to tow it out. I didn't find the way to contact the service/customer care as it was Sunday. None of the other dealers wanted to touch tesla. The service availability is 24 days out, so for something this critical, there should be better customer service, accountability. I still need to pay for self-driving. I can't trust self driving at highway or night due to this. The tow operator said that he towed 7 tesla in last 3 months at exact same location.
I am reporting a serious safety concern involving my 2026 Tesla Model Y AWD. VIN: [XXX] Mileage: Approximately 16,000 miles At approximately 8:00 a.m. XXX Monday, I was driving manually uphill in bright sunlight. Sun glare affected my visibility, and I did not notice that the vehicle ahead had stopped. I did not receive a forward-collision warning before my Tesla struck the vehicle in front at approximately 25 mph. After the first impact, I felt the steering wheel move by itself. The vehicle then moved sideways and struck a tree. The resulting damage includes the front bumper, hood, front wheel area, and left-front door. The vehicle is undrivable. The airbags did not deploy. I am requesting a formal safety investigation into the unexpected steering movement, the absence of a forward-collision warning, and the vehicle's behavior after the first impact. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
On October 24, 2026, while washing my nearly new 2026 Tesla Model Y, I found the brake fluid reservoir cap loose in the windshield cowl area. I took delivery on October 1, 2026. The vehicle had approximately 529 miles when presented to Tesla Service Fremont that day. Tesla's repair invoice confirms that the brake fluid reservoir cap was found on the windshield cowl. It states that the technician inspected the frunk interior for other missing components, found none, performed a brake fluid test and found no moisture, and reinstalled the reservoir cap. I have retained the repair invoice. My safety concern is possible exposure of the brake fluid reservoir to moisture, wash water or debris while the cap was not installed. I do not know when the cap came off or whether it was properly installed at delivery. Contamination and any resulting internal damage have not been established. The invoice does not specify the reservoir's condition when inspected, the test method or numerical results. I am seeking clarification and a technical review of whether further action is needed. I am reporting a potential brake-system assembly or delivery-quality issue for safety review. I am not claiming that a crash or actual loss of braking occurred. The cause, exposure duration and prior warning-lamp status are UNKNOWN.
While using Full Self-Driving (Supervised), the vehicle drove appropriately on [XXX] through the school zone, stopped at the traffic light, and made a right turn onto [XXX]. Immediately after the turn the vehicle accelerated rapidly, changed into the left/inside lane, and reached 46 mph in the active 20 mph school zone. I was pulled over; the officer’s notes state actual speed 46 mph, active 20 mph school zone, inside lane pulling away from all traffic. The acceleration happened extremely quickly. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
My 2026 Tesla Model Y, delivered in June 2025 with about 93,000 miles, has tire pressure monitoring (TPMS) sensors whose batteries are failing early. In the vehicle's service menu, all four sensors read below 2.5 volts, the level the car itself flags as low. Two sensors haven't reported in several days, and one only reports about every other day, so the car can't reliably warn me about low tire pressure. That's a safety concern, especially since I drive about 70,000 highway miles a year. Tesla Service Bulletin SB‑25‑34‑003 (Dec 12, 2025) describes this exact problem on 2026 Model Y vehicles, saying the TPMS sensor battery may drain at an accelerated rate. But the service center told me my VIN isn't included in that bulletin, so the repair would be at my cost. Sensors that are only about 16 months old shouldn't be failing like this. I'm asking that this be reviewed and that the bulletin be expanded to cover affected vehicles like mine.
Tesla’s Full Self-Driving (Supervised) system includes Speed Profiles labeled “Hurry” and “Mad Max.” Both profiles are programmed to ignore and exceed posted speed limits. Mad Max additionally causes the vehicle to zigzag around slower traffic with frequent, unnecessary lane changes. These software design choices create an unreasonable risk to public safety by increasing speed-related crash risk and by introducing unpredictable movements that affect surrounding traffic. Higher speeds reduce available reaction time and increase stopping distances. Aggressive weaving forces other drivers to react, raising the chance of collisions. I assert that, in the interest of highway safety, the Hurry and Mad Max profiles must be eliminated so driver cannot exceed posted speed limits. Only a single speed profile that obeys posted speed limits should remain. I further recommend the return of the previous right-scroll-wheel speed adjustment feature. This would allow drivers to set a precise maximum speed and to travel below the posted limit when conditions make doing so the safer and more prudent choice. The vehicle is available for inspection. This complaint concerns a intentional software design that exposes the driver, passengers, and other road users at elevated and unnecessary risk.
My Tesla, operating on FSD V14, has repeatedly crossed double solid lines to exit the HOV lane on [XXX] in Houston, Texas, where lane changes are prohibited. This has occurred multiple times in both directions: southbound near [XXX] and northbound near [XXX]. On [XXX], while traveling northbound, FSD suddenly crossed the double solid lines into regular traffic without any lane-change command from me. The maneuver happened so quickly that I could not intervene. This is a recurring safety issue, not an isolated incident. I have reported similar incidents multiple times through Tesla's in-car feedback system using the "Critical" option. I am concerned that this unpredictable behavior could cause a collision or traffic violation. I request an investigation into this recurring FSD safety issue. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
I am filing this as a critical safety and accessibility complaint regarding repeated lockouts of my 2026 Model Y that trapped my disabled husband inside the vehicle and left both of us in dangerous situations. On October 21, 2026 I was walking to the car with both hands supporting my disabled husband, who requires physical assistance to walk. I pressed the open button on the door handle. The car locked me out because my phone was not connected as the key.I attempted to reconnect the phone key and could not. I then used the key card. The car continued to lock me out and repeatedly activated Sentry Mode. My husband’s wheelchair was locked inside the vehicle, so he had nowhere to sit while I tried to regain access.This created an immediate safety and accessibility hazard for both of us.Shortly after, a severe thunderstorm warning was issued with golf-ball-sized hail. I could not safely get my husband out of the car because I was afraid of being locked out again in the pouring rain and hail. We had to take refuge under a solar panel to wait out the storm.After the storm, I parked at a QT convenience store. The car was in Pet Mode. I took my phone inside the store and placed the key card on the pad, put the car in pet mode, expecting the car to remain accessible. Instead, the car locked me out again with my deaf and disabled husband inside. I had to bang on the window to get his attention. He does not know how to open the door manually. When he eventually managed to open it, the system reacted as if something was wrong because the car was still in Pet Mode.Prior history:My phone has functioned reliably as the key for months with no issues. These failures appeared suddenly and without warning. These lockouts placed my disabled husband in repeated danger, left him without access to his wheelchair, and forced us into unsafe conditions during severe weather.
Subject: Safety Complaint – Mandatory FSD Disengagement Feedback Obstructs the Touchscreen I am extremely frustrated with the mandatory feedback popup that appears every time I disengage Full Self-Driving (FSD) on my Tesla Model Y. Whenever I take manual control, the system immediately asks me to explain why I disengaged FSD. The popup remains on the touchscreen indefinitely unless I provide an answer, obstructing part of the display. This is not merely an inconvenience. It creates an unnecessary safety hazard. The moment I disengage FSD is precisely when I need to concentrate fully on driving. Forcing me to look at and interact with the touchscreen at that moment is distracting and potentially dangerous. Previously, I could dismiss the popup by quickly pressing the microphone button twice. However, recent software updates have removed this workaround, making the situation even more frustrating. I strongly request that Tesla: Provide an option to permanently disable mandatory FSD disengagement feedback. Allow drivers to dismiss the popup immediately without answering. Automatically remove the popup after a few seconds, or delay feedback requests until the vehicle is parked. Driver safety must take priority over Tesla's data collection. Please escalate this complaint to the FSD software development and vehicle safety teams and provide a response regarding how Tesla intends to address this issue.
Component or System: Hands-free liftgate auto-open feature (ultrasonic and camera-based proximity detection) on a 2026 Tesla Model Y.Description of the Incident: While the vehicle was parked in a tight residential garage on October 20, 2026, the hands-free liftgate auto-open feature activated automatically. The ultrasonic and camera-based proximity detection system behind the vehicle triggered the liftgate to open despite insufficient clearance. The liftgate struck the garage door, resulting in a section of paint chipping off the rear of the vehicle. Safety Risk: The unexpected automatic deployment of the liftgate in a confined space created a crush hazard between the liftgate and the garage door and could have struck a person standing nearby. The impact also damaged the vehicle’s rear structure; in a more severe case, this could compromise the liftgate’s ability to latch or seal properly.Reproduction / Confirmation Status: The issue has not yet been confirmed by a Tesla dealer or independent service center. A service request has been submitted to Tesla through the mobile app. The vehicle and the hands-free trunk system remain available for inspection upon request. Warning Signs: No warning lamps, chimes, or screen messages appeared before the event. The feature operated according to its designed behavior; the safety concern is that this normal behavior is unsafe in tight spaces with limited clearance.
I am formally requesting an investigation and corrective software update addressing Tesla Full Self-Driving (FSD) improperly navigating into closed HOV/express lanes. On October 14, 2026, at approximately 5:19 PM, my Tesla was operating with FSD engaged, Mad Max mode selected, and HOV lane navigation enabled. The vehicle entered a closed Georgia Peach Pass express lane, passed the first security barrier, and subsequently collided with a second barrier despite my attempt to intervene by braking. The collision shattered my windshield, damaged the windshield frame, and caused minor physical injuries. My primary concern is that FSD failed to recognize or appropriately respond to a physically closed express lane. This presents a potentially serious safety hazard for other Tesla drivers and surrounding motorists.
On Oct 19, 2026 at about 11:30 AM MT, my 2026 Tesla Model Y was operating on Full Self-Driving (Supervised) v14.3.12 (software 2026.38.5.1) and parking itself in my home garage. When the front wheels reached the rubber parking curb (wheel stop) at the front of the bay, the car did not stop. It drove into the curb, rolled back a few inches, then drove forward into it again, repeating this cycle several times until I pressed the brake. There was no damage and no injury, but the car repeatedly drove into a fixed obstacle under FSD and did not recognize the end of the parking space. Had a person, pet, or object been in front of the car, this could have caused harm. This follows other FSD parking problems on this car, including an illegal U-turn across a double yellow line on Sep 30, 2026 (FSD v14.3.10).
The car sways/oscillates side to side on highway speed. Took the car in for service on XXX. Multiple works performed on the car such as wheel alignment, Camera Pitch corrections, and tire balance. The service report indicated "The vehicle was released for the customer to monitor." After the car returned to me, I drove on the highway, on the way home, and found the oscillation amplitude has gotten worse. I reported the concern immediately to the [XXX] Tesla Service center. I was told they will call back. Subsequently I left two more urgent messages but never received a call back. This problem, per Tesla's message, asking the customer not to drive on highway due to safety concerns. Unfortunately, I am unable to avoid driving highway for practical daily purposes. On XXX, my daughter vomited (motion sickness) due to car oscillation side to side driving on highway XXX. The oscillation is especially bad when driving on [XXX]. This problem has made me and my family felt very unsafe to drive the car on highway which has prevented us from taking longer trips. This problem has prevented my for normal day to day driving needs and also affecting my family health. Tesla Technician personally ride with me and confirm the defect on XXX. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
2024 Tesla Model Y (FSD Supervised) Location: T intersection where Katyland Drive ends at Hwy Blvd (US 90), Katy, TX Summary: While stopped at a red light in the left turn only lane, I activated Tesla Full Self Driving (FSD). When the light turned green, FSD activated the right turn signal and attempted a right turn into the right turn only lane. I intervened immediately to maintain lane compliance. A vehicle in the right lane had to adjust its turn trajectory to avoid conflict. Notes: The lane markings at this intersection clearly indicate “Left Only” and “Right Only.” The behavior appears reproducible, but I have not attempted to repeat it for safety reasons.
While I was driving in Full Self-driving (FSD) supervise mode, somewhere either in [XXX] or [XXX] on xxx the railroad crossing barriers were down. My 2026 Tesla Model Y (Premium) Dual Motor, FSD (supervise) maneuvered from left to right around the barriers. The barrier in my lane was down although there was an opening to the left, and there was an opening to the right after the track. The barriers in the opposite direction were arranged the same way. The maneuver happened so quickly that I had no time to react or took over manually. My girlfriend was with me and was so frightened by the incident and so with I. I'm reporting this incident for safety concern. I tried to report this incident to Tesla but I could not reach them. I hope you can call the attention of Tesla regarding this incident. Thanks, [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA’s Office of Defects Investigation opened these reviews into vehicles including this one.
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.
Bars are owner complaints, dots mark years with recalls. Select a year to open its report.