2026 Tesla Model Y

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.

FSD Safety Incident – Collision While Exiting Parking Space My Tesla Model Y was operating in Full Self-Driving mode while exiting a parking space. Instead of proceeding straight out of the parking space, the vehicle accelerated while turning toward a basketball pole and collided with it. There was a clear, unobstructed path to exit straight ahead. The vehicle’s unexpected acceleration and turning maneuver happened so quickly that I did not have time to intervene. My hands were positioned next to the steering wheel, ready to take control. I believe this was an FSD driving error and am requesting a formal investigation.

NHTSA ID

11776855

Incident

Oct 10, 2026

On October 4, 2026, while driving my 2026 Tesla Model Y Performance downhill toward my home, the vehicle experienced a low-voltage electrical system malfunction, displaying multiple electrical and propulsion errors, including “Low voltage battery disconnected,” “Connector on low voltage battery is not secured,” and “Unable to drive.” Similar warnings had first appeared the previous day, prompting me to schedule a service appointment. I was able to reach my home and park safely, but the vehicle then became inoperable and could not be driven. Tesla Roadside Assistance towed it to a Tesla service center. The odometer was approximately 3,111 miles. On October 5, Tesla inspected the vehicle under warranty. According to its repair invoice, technicians inspected the low-voltage battery connections and found no physical issues. Tesla determined the battery required a configuration update, performed an “LV Battery - Recover” procedure, and reported that the warnings disappeared and the vehicle operated normally. Tesla returned the vehicle as repaired. Approximately one month later, in November 2026, the same electrical and propulsion failure symptoms returned while the vehicle was parked, again rendering it unable to drive. Tesla Roadside Assistance towed the vehicle a second time. It is currently at Tesla’s service center awaiting diagnosis and is available for inspection upon request. These recurring failures create a serious safety concern because the original malfunction occurred while the vehicle was moving. An unexpected loss of propulsion at highway speeds could result in a collision, endangering occupants and surrounding motorists. Tesla has inspected and attempted to repair the malfunction once, but the problem has recurred. No police or insurance inspection has occurred. I am requesting NHTSA investigate this recurring electrical and propulsion system safety defect.

NHTSA ID

11776478

Incident

Oct 4, 2026

My 2026 Tesla Model Y with Full Self-Driving (Supervised) engaged violates a posted "No Turn on Red" restriction on a daily basis at the intersection of South Street (eastbound) and Dedham Street in Needham, Massachusetts. When my vehicle is first in line at the red light at this intersection, FSD brings the vehicle to a stop and then proceeds to make the right turn on red, despite a clearly posted No Turn on Red sign. This happens every time I approach this intersection in FSD while first in line at a red light. On November 2 2026, at approximately 5:30–6:00 AM, the vehicle made this illegal turn into the path of cross traffic creating a situation where I could have been struck by another vehicle. I repeatedly need to intervene at this intersection and have reported this behavior to Tesla repeatedly over the last 3 months using the in-car voice feedback feature. The behavior has not changed. Software version: FSD v14.3.13 This behavior appears related to NHTSA investigation PE25-012 regarding FSD traffic-law violations, including running red lights.

NHTSA ID

11776394

Incident

Nov 2, 2026

The vehicle was taken to an offical Tesla Service Center for driver's seat foam repair. Following the service, the vehicle was returned to me in an extremely hazardous condition with severe assembly oversights on the driver's seat structural mountings: The rear-left bolt securing the driver's seat frame to the vehicle floor was COMPLETELY MISSING. The rear-right bolt was left ONLY HALFWAY THREADED and loose. The seat side trim and foam were improperly reinstalled. Safety Risk: An unanchored driver seat poses a critical safety hazard. During normal driving, the seat shifts and clunks on turns. In the event of a crash or hard braking, an unbolted seat can detach or structural seat rail failures could occur, severely compromising restraint systems (seatbelts/airbags) and causing life-threatening injury to the driver. Inspection Availability & Symptoms: The loose and missing bolts are visually confirmed, documented via photographs and videos, and remain available for official inspection upon request. Symptoms began immediately after picking up the vehicle from the service visit. this is a physical mounting fastener omission by service technicians.

NHTSA ID

11776375

Incident

Oct 27, 2026

On Friday evening, XXX, in the [XXX] area of [XXX], my Tesla 2026 Model Y was operating in Full Self-Driving (Supervised) on [XXX] and made a turn at [XXX] while running a red light. No collision or injury occurred. This follows my complaint #XXX from XXX, when the same vehicle in Full Self-Driving (Supervised) turned right on red against a posted "No Turn on Red" sign at [XXX], [XXX] and [XXX], and a second incident on XXX, at that same intersection, when the vehicle made an illegal U-turn into the intersection where turns are prohibited (driving mode not confirmed). The XXX maneuver violated a red traffic signal and created a risk to cross traffic and pedestrians. I request that NHTSA review this red-light incident together with complaint #XXXand the XXX incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11776353

Incident

Nov 6, 2026

i purchased an used 2026 Tesla Model Y Long Range Launch edition "launch edition" from Automotive Avenue in [XXX]. Tesla advertised the "launch edition" that has a non-transferable lifetime FSD. We do also own another launch edition that has no problem with the FSD attached to the car. However, this car only comes with 3 months of the FSD trial, and set to expire on XXX. I have reached out to the local Tesla dealership and NO ONE can give me an answer nor point it to the company policy regarding to the issue. I left my phone number, and never gotten a call back either. Tesla company website has no information regarding to the situation and I am demanding them to turn back on the FSD feature that is supposed attached to the "launch edition" I purchased. ref: [XXX] ref: [XXX] INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11775902

Incident

Aug 21, 2026

Component/system involved: Rear light bar (continuous taillight assembly) on both sides. Stress cracks have formed along the bottom edge of the light bar. The left side has cracked completely through. The cracked housing is allowing rainwater to enter the light assembly, which is shorting the brake lights and turn signals and causing them to malfunction. The light bar is still installed on the vehicle and is available for inspection upon request. Safety risk: When the brake lights and/or turn signals fail due to water intrusion, other drivers cannot properly see when the vehicle is braking or turning. This creates a risk of rear-end collision or other accidents, especially in wet conditions or at night. Reproduction / confirmation: Service has been scheduled for replacement of the rear light bar. The issue has not yet been inspected or confirmed in person by a dealer or independent service center. Inspection by others: None. The vehicle or component has not been inspected by the manufacturer, police, insurance representatives, or others. Prior symptoms / warning lights: Stress cracks first noticed on the bottom of the rear light bar on both sides. The left-side crack progressed until it went fully through, after which rainwater began entering and the brake lights/turn signals started malfunctioning. No warning lamps or messages appeared prior to the electrical shorting.

NHTSA ID

11775895

Incident

Oct 26, 2026

FORMAL SAFETY COMPLAINT – Multiple FSD Supervised Malfunctions – 2026 Tesla Model Y VEHICLE: 2026 Tesla Model Y VIN: 7SAYGDEDOTA664631 Current Software: 2026.38.5.11 FSD: v14.3.13 INCIDENT DATE: October 31, 2026 APPROXIMATE TIME: 9:00 PM PURPOSE OF COMPLAINT I am submitting this formal complaint requesting an engineering-level investigation into four recurring and unusual behaviors involving the Full Self-Driving (Supervised) system in my 2026 Tesla Model Y. These problems involve unexpected vehicle movement, apparent changes in steering and acceleration behavior, incorrect navigation instructions, inaccurate destination positioning, and repeated failures to identify my actual home driveway. Most concerning is an incident on October 31, 2026, when the vehicle unexpectedly accelerated in a straight line while exiting my garage, failed to make its previously established steering corrections, and nearly struck a fixed garage-door structure. These behaviors represent a significant departure from the vehicle’s previous operating characteristics. 1. UNEXPECTED CHANGE IN GARAGE-EXITING BEHAVIOR – NEAR COLLISION During the first six months of ownership, my Tesla consistently demonstrated cautious and controlled behavior when using FSD to exit my garage. The established behavior was as follows: I would program my destination while the vehicle was parked inside my garage. Upon activating FSD, the vehicle would slowly begin backing out. The steering wheel would make small, incremental corrections. Acceleration was gradual, with occasional near-stops followed by continued movement. The vehicle appeared to be carefully adjusting its position while exiting the garage However, on Saturday evening, October 31, 2026, at approximately 9:00 PM, its behavior changed dramatically. Immediately after activating FSD: The vehicle moved quickly in a straight line It did not exhibit the previously observed gradual steering corrections It did not appear to slow down as usual, hitting the wall

NHTSA ID

11775641

Incident

Oct 31, 2026

On some Model Y vehicles built before February 28, 2026, the design of the HVAC inlet duct may lead to water ingress into the air filter and/or vehicle interior. If the vehicle is brought into Service for cabin air filter replacement due to a musty or moldy smell from the HVAC system, water dripping from the vents or water pooling into the RH footwell carpet, inspect the vehicle for symptoms related to the condition. If symptoms are present, replace the HVAC inlet duct with an updated part or rework the existing HVAC duct, and replace the cabin air filters.

On some vehicles, degraded or excessive glue under the front seat cushion(s) may cause creaking noises during cornering or when pressing on the seat cushion(s). Upon customer complaint, inspect the vehicle for symptoms related to the condition. If symptoms are present, rework the front seat cushion(s).

On some vehicles, insufficient lubricant at the front seat recliner tube ends may cause creaking noises during weight shifting when the seat is occupied. Upon customer complaint, inspect the vehicle for symptoms related to the condition. If symptoms are present, lubricate the front seat recliner tube ends.

Some Model Y vehicles may emit rattling or knocking noises when driving over bumps or rough road. The condition can be improved by replacing the front upper control arm mounts, replacing the front damper assemblies (Model Y Premium and Performance only), and removing the wiper bracket pencil braces. Inspect the vehicle for symptoms related to the condition. If symptoms are present, replace the front upper control arm mounts with updated parts, replace the front damper assemblies with updated parts (Model Y Premium and Performance only), and remove the wiper bracket pencil braces.

Certain Model Y vehicles may emit rattling or knocking noises when driving over bumps or rough road. The condition can be improved by replacing the front upper control arm mounts, replacing the front damper assemblies, and removing the wiper bracket pencil braces. This document is for vehicles that have already had the front upper control mounts replaced and the wiper bracket pencil braces removed. Replace the front damper assemblies with updated parts.

On some vehicles, the LH and/or RH front seat backrest blower(s) may emit a loud grinding noise in the shoulder area of the backrest when front seat cooling is enabled. Inspect the vehicle for symptoms related to the condition. If symptoms are present, replace the LH and/or RH front seat backrest blower(s).