2019 Tesla Model S

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

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

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

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

On October 17, 2024, NHTSA’s Office of Defects Investigation (ODI) opened a Preliminary Evaluation (PE24031) of Tesla’s Full Self Driving Beta and Full Self Driving (Supervised) (collectively, FSD) to assess: the ability of the FSD system to detect and respond appropriately to reduced roadway visibility conditions; whether any other FSD crashes had occurred under degraded roadway visibility conditions that are similar in nature to the four SGO-reported crashes identified in the opening document, and if so, the contributing circumstances for each of those crashes; and any updates or modifications by Tesla to the FSD system that may affect the performance of FSD in degraded roadway visibility conditions, including the timing, purpose, and capabilities of any such updates, and Tesla’s assessment of their safety impact. Tesla’s FSD is an advanced driver assistance system (ADAS) that relies exclusively on vision-based cameras and the related FSD software to detect and respond to the roadway ahead, projecting a path forward based on traffic control devices, vehicles, pedestrians, and the roadway itself. During this phase of the investigation, ODI reviewed the materials provided by Tesla detailing any actions taken, or changes, modifications, and updates made that may relate to the alleged defect. ODI reviewed information related to Tesla’s transition to a vision-only perception system, and its deployment of the strategy in vehicles. ODI’s findings include information on limitations of the vision-only perception system and updates made in response to known subject crashes. When Tesla began transitioning away from using both cameras and radars to an exclusively camera-based approach, known as Tesla Vision, in mid-2021, it developed and implemented a degradation detection system that it deployed by a software update to existing and new Tesla vehicles. On June 28, 2024, the day after Tesla submitted the SGO report of the November 28, 2023 fatal crash listed in this document, Tesla began developing an update to the degradation detection system. ODI reviewed certain public statements, including those made during an April 2025 earnings call, in which Tesla stated that it had developed a breakthrough “direct photon-counting” capability that eliminates the degradation that the camera-based system experiences when glare is encountered. At this time, ODI does not have information on when the update was deployed and which vehicles have the updated system. ODI has discussed individual incidents and its initial findings with Tesla. Based on Tesla’s post-incident analysis, the update to the degradation detection system, had it been installed on the vehicles at the time, may have affected 3 of the 9 incidents identified by ODI. Review of Tesla’s responses revealed additional crashes that occurred in similar environments and where the system either did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path. Tesla also described internal data and labeling limitations that prevented a uniform identification and analysis of crash events with the subject system engaged. ODI believes this limitation could have led to under-reporting of subject crashes over portions of the defined time-period. Available incident data raise concerns that Tesla’s FSD system fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants where the camera-based system performance degrades significantly. In the crashes that ODI has reviewed, the FSD system did not detect common roadway conditions that impaired its visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred. ODI is upgrading this investigation (PE24031) to Engineering Analysis (EA) 26002 to further evaluate this matter. The crashes included in the failure report summary can be found at NHTSA.gov under the following SGO report identification numbers: 13781-8004, 13781-7181, 13781-7381, 13781-7767, 13781-7964, 13781-8977, 13781-9267.

The Office of Defects Investigation (ODI) is opening a Recall Query to assess the remedy adequacy of Recall 23V838. On December 12, 2023, Tesla filed a Defect Information Report (Recall 23V838) applicable to all Tesla models produced and equipped with any version of its Autopilot system, which Tesla described as an SAE Level 2 (L2) Advanced Driver Assistance System (ADAS). Autopilot is the simultaneous engagement of Tesla’s Traffic-Aware Cruise Control (TACC) and Autosteer. In describing the safety defect, Tesla’s Defect Information Report (DIR) explained that “the prominence and scope of the system’s controls may be insufficient to prevent driver misuse,” and Tesla committed to the deployment of a multipart remedy aimed at improving system and engagement controls and reducing mode confusion. EA22002 (upgraded from PE21020) was opened to investigate whether Tesla’s Autopilot contained a defect that created an unreasonable risk to motor vehicle safety and involved extensive crash analysis, human factors analysis, vehicle evaluations, and assessment of vehicle control authority and driver engagement technologies. The work conducted in these investigations aligns with Tesla’s conclusion in its 23V838 recall filing. During EA22002, ODI identified at least 13 crashes involving one or more fatalities and many more involving serious injuries in which foreseeable driver misuse of the system played an apparent role. Tesla filed Recall 23V838 to address concerns regarding the Autopilot system investigated in EA22002. Following deployment of the remedy in Recall 23V838, ODI identified concerns due to post-remedy crash events and results from preliminary NHTSA tests of remedied vehicles. Also, Tesla has stated that a portion of the remedy both requires the owner to opt in and allows a driver to readily reverse it. Tesla has also deployed non-remedy updates to address issues that appear related to ODI’s concerns under EA22002. This investigation will consider why these updates were not a part of the recall or otherwise determined to remedy a defect that poses an unreasonable safety risk. ODI is therefore opening this Recall Query investigation to further evaluate the adequacy of the remedy for recall 23V838.

The Office of Defects Investigation (ODI) received a petition requesting that ODI reevaluate its decision to deny DP20-001 on the basis that intermittent high electrical current demands on the vehicles' 12VDC systems may have caused some or all of the incidents examined by ODI in DP20-001. The petitioner bases this information on a review of open-source research and the DP20-001 denial. The petition and related materials can be reviewed at NHTSA.gov under the following ODI number: 11528471.

On March 21, 2023, the Office of Defects Investigation (ODI) received a petition requesting a “recall of all Tesla cars” produced from 2013 to the date on which the petition was filed due to what Petitioner considers to be the increased likelihood of pedal misapplication. Attached to the Petition is a paper authored by Petitioner. According to Petitioner, the differences in the operator controls between the subject Tesla vehicles and internal combustion engine powered vehicles promote driver pedal misapplication, leading to sudden unintended acceleration (SUA) incidents. To fix this alleged defect, Petitioner argues that the subject vehicles should be equipped with measures that require: (i) occasional removal of the driver’s foot from the pedals; and (ii) application of the brake pedal before fully stopping the vehicle. ODI evaluated the allegations by, among other things, reviewing the Petition and supporting technical paper, and analyzing Tesla’s response to ODI’s Information Request. ODI is denying this Petition. ODI has not found evidence that warrants the opening of a safety defect investigation into the Tesla vehicles as described in the Petition. The use of regenerative braking controlled by the accelerator pedal, or one-pedal driving, is common across most light vehicle manufacturers of electric vehicles and Tesla vehicles are not unique in this respect. Further, ODI identified only a handful of collisions potentially within the scope of the alleged defect; and corresponding vehicle data demonstrated that the subject vehicles responded appropriately to control inputs by their drivers. Moreover, ODI is unaware of any evidence to suggest that Petitioner’s proposed interlock would have prevented alleged SUA events as apparently described in the Petition and supporting materials. Accordingly, the Agency is denying the petition. As with all potential motor vehicle safety risks, NHTSA will continue to review any new information or incidents as they are submitted to the Agency.

NHTSA received a petition on or about July 18, 2022, requesting that Federal Motor Vehicle Safety Standard (FMVSS) 141 be applied to all electric and hybrid vehicles operating in the United States. The petition can be reviewed at NHTSA.gov under ODI Number 11486072. FMVSS 141 establishes performance requirements for pedestrian alert sounds for motor vehicles. The standard applies to hybrid and electric vehicles that have a gross vehicle weight rating of 4,536 KG or less or are defined as low-speed vehicles. The standard became fully applicable to all such vehicles manufactured on or after March 1, 2021.On January 27, 2023, NHTSA opened Defect Petition (DP) 22-005 to evaluate the subject matter described in the petition. On June 24, 2023 and as supplemented on June 25, 2023, the petitioner notified NHTSA he was withdrawing his petition. The petitioner indicated that, based on his review of data, there is no justification for asserting potential benefits that could be derived from actions sought by my petition. Based on the petitioner's withdrawal, DP22-005 is closed. Closure of this DP does not represent a determination by NHTSA regarding the subject matter of the petition.

The Office of Defects Investigation (ODI) upgraded PE21020 to EA22002 on June 8, 2022, to extend work and deepen the PE21020 crash analysis, to supplement that analysis with additional data, and to perform vehicle evaluations to understand how Tesla’s Autopilot system may exacerbate human factors or behavioral safety risks by undermining the effectiveness of the driver’s supervision. To support this work, ODI collected additional crash information and assessed vehicle control authority, driver engagement technologies, and related human factors considerations associated with partial automation via analysis of peer vehicle data and hands-on vehicle evaluation, assessments from NHTSA human factors subject matter experts, and reviews of related publications dedicated to partial driving automation. Autopilot is the simultaneous use of the features that Tesla calls Traffic-Aware Cruise Control (TACC) and Autosteer. TACC is a type of adaptive cruise control that, like traditional cruise control, maintains a set speed but also slows or accelerates as necessary to maintain the vehicle’s following distance from a vehicle in front. As designed, Autosteer detects lane markings and the presence of other nearby vehicles and objects to keep the vehicle in its driving lane. Autopilot is characterized by Tesla as an SAE Level 2 (“L2 system”) partial driving automation system that provides driver assistance through steering, propulsion, and braking within a specified driving environment under direct supervision of the driver. L2 systems should be designed to support the driver’s need to monitor the system in response to the constantly changing driving environment and, if necessary, take over the dynamic driving task. To ensure sufficient driver engagement, vehicles with L2 systems should employ driver engagement systems and usage controls that are appropriate and sufficient for the L2 system design and driver expectations. ODI completed an analysis of 956 crashes reported up to August 30, 2023. In approximately half (489) of those crashes, ODI found: 1.) that there was insufficient data to make an assessment; 2.) the other vehicle was at fault; 3.) Autopilot was found to not be in use; or 4.) the crash was otherwise unrelated to EA22002. Of the remaining 467 crashes, ODI identified trends resulting in three categories: collisions in which the frontal plane of the Tesla struck another vehicle or obstacle with adequate time for an attentive driver to respond to avoid or mitigate the crash (211), roadway departures where Autosteerwas inadvertently disengaged by the driver’s inputs (111), and roadway departures in low traction conditions such as wet roadways (145). ODI observed this pattern across all Tesla models and hardware versions. Crash and human factors assessment showed that Autopilot controls did not sufficiently ensure driver attention and appropriate use. At the same time, peer analysis and vehicle evaluations established that Autopilot invited greater driver confidence via its higher control authority and ease of engagement. This mismatch of weak usage controls and high control authority was evident in these crash categories, which included indications of driver disengagement from the driving task. This mismatch was also evident in roadway departures when the system was engaged in low traction conditions outside of Tesla’s recommendations.Additional information regarding NHTSA’s crash analysis is available in the EA22002 file. ODI reviewed these findings with Tesla during several conversations in Quarter 4 of 2023. On December 12, 2023, Tesla filed a Defect Information Report (DIR) (Recall 23V838) applicable to all Tesla models produced and equipped with any version of its Autopilot system. Tesla’s DIR described the functionality of this system, stated that the prominence and scope of the system’s controls may be insufficient to prevent driver misuse, and described a remedy to improve the effectiveness of driver warnings and to reduce mode confusion. ODI completed an extensive body of work via PE21020 and EA22002, which showed evidence that Tesla’s weak driver engagement system was not appropriate for Autopilot’s permissive operating capabilities. This mismatch resulted in a critical safety gap between drivers’ expectations of the L2 system’s operating capabilities and the system’s true capabilities. This gap led to foreseeable misuse and avoidable crashes. During EA220002, ODI identified at least 13 crashes involving one or more fatalities and many more involving serious injuries, in which foreseeable driver misuse of the system played an apparent role. ODI’s analysis conducted during this investigation, which aligns with Tesla’s conclusion in its Defect Information Report, indicated that in certain circumstances, Autopilot’s system controls and warnings were insufficient for a driver assistance system that requires constant supervision by a human driver. Given Tesla’s recall (23V838) of all vehicles equipped with Autopilot for insufficient controls to prevent misuse, ODI is closing EA22002. Concurrent with that closing, ODI has opened a Recall Query (RQ24009) to assess the effectiveness of the 23V838 remedy. To review the ODI reports cited in the Closing Resume ODI Report Identification Number document, go to NHTSA.gov.

The Office of Defects Investigation (ODI) opened Preliminary Evaluation (PE21-023) on December 21, 2021, to evaluate the driver distraction potential and use frequency / circumstances of in-vehicle game-play functionality referred to as ?Passenger Play? in certain model year (MY) 2017-2022 Tesla Model 3, S, X, and Y vehicles. Distracted driving can result in an increased risk of a crash. PE21-023 was prompted by the receipt of Vehicle Owners Questionnaire (VOQ) 11439598 from the owner of a 2021 Model 3 on November 6, 2021. ODI sent an Information Request (IR) letter to Tesla on January 20, 2022 and received Tesla?s response on March 4, 2022.On December 24, 2020, Tesla introduced Passenger Play to vehicles equipped with the Intel Atom processor (receiving an aftersale software update) via its 2020 holiday release. Passenger Play permitted occupants to play specific games selected by Tesla for primarily turn-based play style and limited gameplay motion with the transmission in Drive and the vehicle in motion. Under these conditions, a notification would display on the screen and the screen area devoted to the game would reduce from 100% to accommodate vehicle controls and driving task data readout. Specific changes varied among models. On December 21, 2022, Tesla voluntarily disabled Passenger Play capability with Firmware Release 2021.44.25.1 in response to NHTSA?s request. Tesla reported a month later that a 97% completion rate was achieved though Tesla?s Over the Air (OTA) update. ODI opened PE 21-023 to evaluate the driver distraction potential of Tesla Passenger Play while the vehicle is being driven including aspects of the feature, frequency, and use scenarios.Based on the analysis conducted, PE21-023 has been closed. The closing of this investigation does not constitute a finding by NHTSA that no safety-related defect exists. Furthermore, it does not foreclose the Agency from taking further action, if warranted, or the potential for a future finding that a safety-related defect exists through additional information the Agency may receive.See attached Closing Report for a detailed summary of the investigation findings.

From 2000 through 2017, Takata produced millions of air bag inflators using two types of phase-stabilized ammonium nitrate ("PSAN") propellant -- propellant 2004 and propellant 2004L. After prolonged exposure to high temperature cycles and humidity, inflators using propellant 2004 can degrade, causing the propellant to burn too quickly when ignited. The rapid burning can cause the inflator to rupture during deployment, potentially causing serious or even fatal injury to vehicle occupants. See 2016 Blomquist Report at www.nhtsa.gov/sites/nhtsa.gov/files/documents/expert_report-hrblomquist.pdf.Consequently, all frontal inflators using propellant 2004 that do not contain a "desiccant" (a substance that traps and holds moisture) in US vehicles are under recall. These "non-desiccated" inflators either have been or are required to be replaced.In some cases, the remedy part for these recalled inflators was, or will be, an inflator using either propellant 2004 or 2004L that does contain a desiccant. None of these "desiccated" remedy parts (which were installed in older model year vehicles) are currently under recall for a degradation concern. Certain subsets of desiccated PSAN inflators using propellant 2004 for use as original equipment, however, have been recalled for a degradation concern. All Takata inflators produced with propellant 2004L contain desiccant, and none of these desiccated inflators using propellant 2004L are under recall for a degradation concern. There have been no reported field ruptures in any non-recalled desiccated PSAN inflators.It is understood that desiccants fully saturate at some threshold, at which point any additional moisture will not be captured. This means the degradation process observed in non-desiccated inflators using propellant 2004 may also occur in non-recalled desiccated inflators using propellant 2004, assuming additional moisture enters the inflator and high temperature cycling occurs. Based on available information, desiccant saturation can occur within the first five years in the worst environments, and the time required for full saturation is affected by multiple factors. While no present safety risk has been identified, further work is needed to evaluate the future risk of non-recalled desiccated inflators using propellant 2004.Three entities -- Takata (now known as TK Global), the Independent Testing Coalition, and Exponent -- have been studying the long-term behavior of Takata desiccated PSAN inflators using propellant 2004L (as well as 2004) in the presence of moisture and temperature cycling. The research efforts, which include development of predictive modeling techniques and field sample analysis, are ongoing. To date, none of the researchers have identified field evidence showing that propellant 2004L is undergoing a degradation process that leads to aggressive deployment and potential rupture. However, the time in service of such inflators remains short compared to that of the inflators using propellant 2004. Further study is needed to assess the long-term safety of desiccated inflators using propellant 2004L.The Office of Defects Investigation is opening this investigation to examine whether a safety defect related to propellant degradation exists in non-recalled desiccated PSAN frontal inflators manufactured by Takata. This investigation will require extensive information on Takata production processes and surveys of inflators in the field. Lists of recall actions that may have used desiccated PSAN inflators as remedy parts, as well as the makes and models originally manufactured with them, is available with the downloadable version of this document (see nhtsa.gov/recalls?nhtsaId=EA21002 -- note this information is subject to change/revision as the investigation proceeds). This investigation does not supersede EA15-001, which remains open.

On August 13, 2021, NHTSA?s Office of Defects Investigation (ODI) opened a Preliminary Evaluation (PE21-020) to assess the performance of Tesla?s Autopilot system (a system characterized by Tesla as an SAE Level 2 driving automation system designed to support and assist the driver in performing the driving task) available in Tesla vehicles. The investigation opening was motivated by an accumulation of crashes in which Tesla vehicles, operating with Autopilot engaged, struck stationary in-road or roadside first responder vehicles tending to pre-existing collision scenes. Upon opening the investigation, NHTSA indicated that the PE would also evaluate additional similar circumstance crashes of Tesla vehicles operating with Autopilot engaged, as well as assess the technologies and methods used to monitor, assist, and enforce the driver?s engagement with the dynamic driving task during Autopilot operation.PE21-020 is upgraded to an Engineering Analysis (EA) to extend the existing crash analysis, evaluate additional data sets, perform vehicle evaluations, and to explore the degree to which Autopilot and associated Tesla systems may exacerbate human factors or behavioral safety risks by undermining the effectiveness of the driver?s supervision. In doing so, NHTSA plans to continue its assessment of vehicle control authority, driver engagement technologies, and related human factors considerations.The attached Detailed Summary further describes NHTSA?s review to date and the basis for upgrade to an EA.

On December 19, 2019, NHTSA received a petition from Mr. Brian Sparks requesting that the Agency recall all [Tesla] Model S, Model X, and Model 3 vehicles produced from 2013 to the present due to sudden unintended acceleration (SUA). In his petition and follow-up submissions, the petitioner identified a total of 232 non-duplicative complaints to NHTSA, including 203 reporting crashes. On January 13, 2020, NHTSA's Office of Defects Investigation (ODI) opened Defect Petition DP20-001 to evaluate the petitioner?s request. ODI's evaluation included reviews of all complaints and supporting information referenced by the petitioner, as well as 14 additional complaints to NHTSA related to SUA crash allegations that were either not selected by the petitioner or were submitted after the petitioner's most recent submission. The review also included analyses of available crash data (EDR, Tesla log data, and/or video data) the Agency acquired as part of the evaluation.After reviewing the available data, ODI has not identified evidence that would support opening a defect investigation into SUA in the subject vehicles. In every instance in which event data was available for review by ODI, the evidence shows that SUA crashes in the complaints cited by the petitioner have been caused by pedal misapplication. There is no evidence of any fault in the accelerator pedal assemblies, motor control systems, or brake systems that has contributed to any of the cited incidents. There is no evidence of a design factor contributing to increased likelihood of pedal misapplication. The theory provided of a potential electronic cause of SUA in the subject vehicles is based upon inaccurate assumptions about system design and log data.NHTSA is authorized to issue an order requiring notification and remedy of a defect if the Agency?s investigation shows a defect in design, construction, or performance of a motor vehicle that presents an unreasonable risk to safety. 49 U.S.C. ?? 30102(a)(9), 30118. Since the information before the Agency is not indicative of a vehicle-based defect, it is unlikely that any investigation opened because of granting this petition would result in an order concerning the notification and remedy of a safety-related defect. Therefore, upon full consideration of the information presented in the petition and the potential risks to safety, the petition is denied. The denial of this petition does not foreclose the Agency from taking further action if warranted or the potential for a future finding that a safety-related defect exists based upon additional information the agency may receive.The reference numbers for the complaints to NHTSA cited by the petitioner can be found in the petition submission documents in the public file for DP20-001. Those complaints and the 14 complaints ODI added to its evaluation can be viewed at NHTSA.gov. The reference numbers for the complaints added by ODI are: 11385350, 11383955, 11383233, 11383180, 11378492, 11378458, 11302076, 11299698, 11290006, 11190595, 11174504, 11115496, 11096644 and 11000097. The attached report, further detailing NHTSA?s reasons for denial of the petition, will be published in the Federal Register.

In a letter dated September 17, 2019, Mr. Edward Chen petitioned the NHTSA to initiate a defect investigation of certain Tesla Model S and Model X vehicles that received revised battery management software in one or more over-the-air (OTA) updates from Tesla, beginning in May 2019. The petitioner bases his request on vehicle fires that took place worldwide and OTA software updates Tesla made to the Battery Management System (BMS) of certain Tesla vehicles that resulted in loss of available vehicle mileage range and increased charging durations.On October 1, 2019, the Office of Defects Investigation (ODI) opened DP19-005 to evaluate the petitioner?s request. Information provided by Tesla in response to ODI's information request letter for DP19-005 indicated that a firmware update that may limit maximum voltage was installed in certain MY 2012 through 2016 Model S vehicles (subject vehicles). The voltage limiting firmware is a dynamic algorithm that is enabled in vehicles with high Supercharging use histories, which contributes to high usage stress to the high-voltage (HV) battery. Tesla sold approximately 61,781 subject vehicles in the United States and, through August 2021, the voltage limiting firmware had been enabled in approximately 2,062 vehicles. Through December 2020, ODI identified 59 complaints from consumers alleging reductions in battery capacity (52) or charging speed (7) in the subject vehicles. Log data from these vehicles showed that the voltage limiting firmware had been enabled in about 58 percent (30 of 52) of the complaints alleging range loss. Subsequent updates have restored some or all of the battery capacity to vehicles affected by the voltage limiting firmware coupled with updates enhancing BMS battery brick monitoring algorithms. None of the complaint vehicles have reported any thermal incidents or other safety hazards related to the HV battery.The five non-crash fires referenced in the petition include two fires that occurred in China in early 2019 involving vehicles that: 1) had recently completed Supercharging sessions; 2) were at a high state-of-charge (SOC) of the HV battery; 3) were parked with the battery cooling system shutoff; and 4) had histories of high-stress usage for the HV batteries. The three fires that occurred outside China did not involve the same fact patterns regarding vehicle state and charging history. The two fires that occurred in the United States include one involving a vehicle with no Supercharging history that was driving when the fire occurred and another in which the origin of the fire was external to the HV battery. The fifth fire, which also originated external to the HV battery, involved a vehicle in Germany that had been parked at a low SOC for an extended period. To date, incidents of fires involving parked vehicles with recent Supercharging and histories of high-stress use have only been observed in China, where high-stress use factors appear to be more common. NHTSA is authorized to issue an order requiring notification and remedy of a defect if the Agency?s investigation shows a defect in the design, construction, or performance of a motor vehicle that presents an unreasonable risk to safety. 49 U.S.C. ?? 30102(a)(9), 30118. Given the absence of any incidents in the United States related to fast charging, and the absence of any such incidents globally since May 2019, it is unlikely that an order concerning the notification and remedy of a safety-related defect would be issued due to any investigation opened as a result of granting this petition. Therefore, upon full consideration of the information presented in the petition, and the potential risks to safety, th