NHTSA owner reports · September 18, 2026 snapshot.
What owners actually said
358 reportsMileage unknown · Aug 19, 2026
Forward Collision AvoidanceSteeringUnknown Or OtherCrash
This is what happened: While Full Self-Driving (FSD) was engaged, the vehicle approached an intersection and appeared unable to correctly follow the roadway. Instead of following the intended road path, the vehicle continued forward, drove over the curb, and struck a road sign. The impact knocked the sign down, and the sign sub…
Read full complaint
This is what happened: While Full Self-Driving (FSD) was engaged, the vehicle approached an intersection and appeared unable to correctly follow the roadway. Instead of following the intended road path, the vehicle continued forward, drove over the curb, and struck a road sign. The impact knocked the sign down, and the sign subsequently struck the vehicle, including the roof glass. The roof glass shattered and small pieces of glass entered the cabin, exposing both the driver and front passenger to a safety risk. Vehicle data obtained after the incident shows that the vehicle was in ACTIVE_FSD leading up to the collision. FSD changed from ACTIVE to UNAVAILABLE approximately 1.5 seconds before the crash algorithm wake-up. Significant braking occurred only very close to the collision, and no Automatic Emergency Braking intervention was recorded during the incident window. The data also shows multiple substantial steering movements shortly before the collision. Accelerator-pedal data does not establish driver acceleration as the cause of the collision. The available samples show an accelerator position of 2.0% shortly before the collision and 0.0% in the next recorded sample. The driver applied the brake shortly before impact. There were no prior warning lamps or messages indicating that FSD was about to become unavailable before the vehicle departed the roadway. The vehicle has been inspected/repaired following the collision, and vehicle data relating to the incident has been obtained and preserved. Police responded to the collision, and the incident was also reported to insurance. A police report was filed, and the case number is 2026-07160174. I have not yet received the formal CR-4 crash report. Following the collision, I experienced significant psychological distress and trauma-related stress symptoms as a result of the incident.
NHTSA ODI #11758061
2,000 miles · Aug 18, 2026
Electrical SystemPower TrainVehicle Speed ControlCrash
The contact owns a 2026 Tesla Model Y. While the vehicle was parked and attempting to shift into drive(D), the brake pedal was depressed, and the driver attempted to select the gear, but the gear display icon appeared semi-transparent. The driver was able to select the intended gear after several attempts; however, upon depressi…
Read full complaint
The contact owns a 2026 Tesla Model Y. While the vehicle was parked and attempting to shift into drive(D), the brake pedal was depressed, and the driver attempted to select the gear, but the gear display icon appeared semi-transparent. The driver was able to select the intended gear after several attempts; however, upon depressing the accelerator pedal, the vehicle unintentionally accelerated at a higher speed and struck a tree. The air bags did not deploy. No injuries were reported, and a Police report was not filed. No warning light was illuminated before or after the crash. Full Self-Driving (FSD) mode was not activated during the failure. The vehicle was driven to a collision repair center to repair the damage. The contact notified the manufacturer of the failure and requested assistance retrieving data from the Event Data Recorder (EDR); however, no assistance was provided. The vehicle was not diagnosed or repaired for the unintended acceleration. The failure mileage was approximately 2,000.
NHTSA ODI #11757772
Mileage unknown · Aug 17, 2026
Unknown Or Other
[XXX] [XXX] [XXX] [XXX] [XXX] [XXX] [XXX] Email [XXX] National Highway Traffic Safety Administration Office of Defects Investigation [XXX] [XXX] Re: Safety Concern – Tesla Structural Battery Pack Design Dear NHTSA, I am writing to raise a serious safety and durability concern regarding Tesla’s structural battery pack design, …
Read full complaint
[XXX] [XXX] [XXX] [XXX] [XXX] [XXX] [XXX] Email [XXX] National Highway Traffic Safety Administration Office of Defects Investigation [XXX] [XXX] Re: Safety Concern – Tesla Structural Battery Pack Design Dear NHTSA, I am writing to raise a serious safety and durability concern regarding Tesla’s structural battery pack design, in which the high-voltage battery is glued into the vehicle’s body and used as a load-bearing structural member. My primary concerns are as follows: See atrached PDF fe INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA ODI #11757570
13,001 miles · Aug 17, 2026
Electrical SystemForward Collision AvoidanceCrash
The contact owns a 2026 Tesla Model Y. The contact stated that while driving at an undisclosed speed with the Full Self Driving Mode activated, the vehicle struck the garage wall, damaging the rear passenger’s side door. No injuries were sustained. The contact stated that the dealer had previously provided mobile service to repl…
Read full complaint
The contact owns a 2026 Tesla Model Y. The contact stated that while driving at an undisclosed speed with the Full Self Driving Mode activated, the vehicle struck the garage wall, damaging the rear passenger’s side door. No injuries were sustained. The contact stated that the dealer had previously provided mobile service to replace the camera and that a second dealer, Tesla White Plains (250 Tarrytown Rd, White Plains, NY 10607), had performed a hard reset on the vehicle due to phantom braking; however, the failure persisted. The dealer was made aware of the failure but canceled an upcoming appointment and informed the contact that there was no failure found. The vehicle was not diagnosed or repaired. The manufacturer was made aware of the failure. The failure mileage was approximately 13,001.
NHTSA ODI #11757495
Mileage unknown · Aug 17, 2026
Forward Collision AvoidanceService BrakesCrash
On August 15, 2026, at approximately 5:00 PM, the vehicle was being driven with Full Self-Driving (Supervised) engaged during light rain. As the vehicle approached traffic ahead, it did not slow or brake as expected. The driver recognized that the vehicle was not slowing and attempted to intervene manually by pressing the brake…
Read full complaint
On August 15, 2026, at approximately 5:00 PM, the vehicle was being driven with Full Self-Driving (Supervised) engaged during light rain. As the vehicle approached traffic ahead, it did not slow or brake as expected. The driver recognized that the vehicle was not slowing and attempted to intervene manually by pressing the brake pedal multiple times. The driver reports that despite these attempts, the vehicle did not slow or respond to the brake pedal as expected, and a collision occurred. There were no known warning lamps or warning messages indicating a braking-system problem prior to the incident. The vehicle has not yet been inspected to determine the cause of the reported braking behavior. The incident has been reported to the manufacturer, and a request has been made to preserve and review available vehicle data surrounding the collision, including braking inputs, vehicle speed, Full Self-Driving status/actions, warnings, diagnostic information, and safety/event data. The vehicle is available for inspection. At this time, the cause of the failure to slow as expected is UNKNOWN.
NHTSA ODI #11757356
Mileage unknown · Aug 14, 2026
SteeringUnknown Or OtherCrashInjury
On August 3, 2026, my Tesla Model Y was traveling at approximately 50 mph with Tesla Full Self-Driving (FSD) engaged. At approximately 4:12:47 PM CDT, FSD became unavailable and then became available again. At 4:12:51.628 PM CDT, FSD was recorded as ACTIVE_FSD again. Approximately 2.36 seconds after FSD was re-engaged, at 4:12…
Read full complaint
On August 3, 2026, my Tesla Model Y was traveling at approximately 50 mph with Tesla Full Self-Driving (FSD) engaged. At approximately 4:12:47 PM CDT, FSD became unavailable and then became available again. At 4:12:51.628 PM CDT, FSD was recorded as ACTIVE_FSD again. Approximately 2.36 seconds after FSD was re-engaged, at 4:12:53.987 PM CDT, the vehicle's steering began a sudden and rapid rightward movement. I did not turn the steering wheel or intentionally provide a rightward steering input that initiated this maneuver. The recorded steering angle increased rapidly from approximately +11.4° to +20.7°, +33.3°, +83.3°, +137.9°, +154.7°, and ultimately approximately +282° within about 1.6 seconds. Importantly, FSD was still recorded as ACTIVE_FSD when the steering movement began. FSD changed to UNAVAILABLE at approximately 4:12:54.364 PM CDT, about 0.38 seconds after the steering movement had already started. The steering continued to escalate after FSD became unavailable.The vehicle subsequently experienced severe lateral acceleration of approximately 0.96 g, and crash detection activated at approximately 4:12:55.710 PM CDT. The accelerator was recorded at 0% during the developing steering event and increased only after crash detection. Hard braking and ABS activation occurred afterward.I do not have Tesla Dashcam footage, but I have retained Tesla's vehicle telemetry export containing FSD state, steering, steering-torque, accelerator, braking, vehicle-speed, stability-control, and crash-event data.I am concerned that Tesla FSD may have initiated or contributed to the unexpected steering maneuver that resulted in the collision. I am certain that I did not initiate the sudden rightward steering maneuver.I request that NHTSA investigate whether this represents a potential safety defect or unexpected FSD behavior, particularly the sequence of FSD re-engagement followed approximately 2.36 seconds later by the unexpected steering event while FSD was still ACTIVE_FSD
NHTSA ODI #11756945
Mileage unknown · Aug 13, 2026
Exterior Lighting
Screen provides alert that "center brake light condition deteceted". Shows up as VCRIGHT_a487 Tesla said "The condition is characteristic of the current firmware with no current fix at this time". Tesla is looking into this concern as it is affecting multiple vehicles at this time
NHTSA ODI #11756780
Mileage unknown · Aug 13, 2026
Unknown Or OtherVehicle Speed Control
I was operating my Tesla using Full Self-Driving (Supervised) when the vehicle approached an active school zone with flashing warning lights and a posted school-zone speed limit of 35 mph. FSD did not appropriately respond to the active school zone or reduce the vehicle's speed to the posted 35 mph limit, requiring me to disenga…
Read full complaint
I was operating my Tesla using Full Self-Driving (Supervised) when the vehicle approached an active school zone with flashing warning lights and a posted school-zone speed limit of 35 mph. FSD did not appropriately respond to the active school zone or reduce the vehicle's speed to the posted 35 mph limit, requiring me to disengage FSD and manually slow the vehicle. The incident was captured on the Tesla dashcam. The recording shows FSD active while approaching the school zone. At approximately 14 seconds into the recording, the vehicle was traveling approximately 52 mph with "Self-Driving" displayed while the flashing school-zone warning and SCHOOL pavement markings were visible ahead. The posted school-zone speed limit is 35 mph when the warning lights are flashing. Because FSD was not slowing the vehicle appropriately, I intervened and disengaged FSD. Immediately following my intervention, vehicle speed decreased from approximately 49 mph to 39 mph, 31 mph, and approximately 29 mph as I manually slowed the vehicle. This was the second time I experienced FSD failing to appropriately respond to this same active school zone. After this occurrence, I saved the dashcam recording and submitted a Bug Report through the vehicle. There were no warning messages indicating that FSD could not recognize or respond to the school zone. My safety concern is that FSD may proceed into an active school zone substantially above the posted school-zone speed limit unless the driver recognizes the failure and intervenes. The original dashcam recording is available and documents the vehicle speed, FSD status, active flashing school-zone warning, posted speed limit, and timing of my intervention.
NHTSA ODI #11756753
Mileage unknown · Aug 12, 2026
Back Over PreventionForward Collision Avoidance
Car is less than a year old and forward camera is reporting visibility problem. Safety features, forward collision and autonomous driving is severely degraded. Tesla will not repair under warranty which requires disassembly of the camera housing. Front camera housing has been redesigned by Tesla but they are not retrofitting thi…
Read full complaint
Car is less than a year old and forward camera is reporting visibility problem. Safety features, forward collision and autonomous driving is severely degraded. Tesla will not repair under warranty which requires disassembly of the camera housing. Front camera housing has been redesigned by Tesla but they are not retrofitting this fix for existing Model Y and have not issues a safety recall. This camera housing defect presents a risk to my safely and the safety of others.
NHTSA ODI #11756419
Mileage unknown · Aug 10, 2026
Back Over Prevention
I am submitting this complaint to report what I believe is a potential safety defect involving the Tesla Autopark feature on my 2026 Tesla Model Y Premium All-Wheel Drive. On 7/21/26 at approximately 7:40 a.m., I activated Autopark to park my vehicle in my driveway. A transit van was already parked nearby and remained stationar…
Read full complaint
I am submitting this complaint to report what I believe is a potential safety defect involving the Tesla Autopark feature on my 2026 Tesla Model Y Premium All-Wheel Drive. On 7/21/26 at approximately 7:40 a.m., I activated Autopark to park my vehicle in my driveway. A transit van was already parked nearby and remained stationary throughout the parking maneuver. While Autopark was controlling the vehicle, my Tesla continued reversing and failed to stop before striking the parked transit van. The collision caused damage to the right rear passenger side of my vehicle. Based on what I observed, the vehicle did not recognize or respond appropriately to the presence of the stationary van. This raises serious concerns regarding the ability of the Autopark system to detect nearby stationary vehicles and avoid collisions during low-speed automated parking. Although I understand that Tesla states the driver must supervise Autopark, I am concerned that the system continued reversing into an obvious stationary obstacle rather than warning the driver or stopping before impact. I respectfully request that Tesla: Preserve all vehicle diagnostic logs, camera data, and sensor data from approximately 7:40 a.m. on the date of the incident. Conduct a full engineering review of the Autopark event. Determine why the vehicle failed to detect or avoid the parked transit van. Advise whether this incident resulted from a software issue, hardware issue, sensor limitation, or another system malfunction. Provide me with a written response and a case number confirming that this has been recorded as a formal vehicle safety complaint. I am prepared to provide photographs, dashcam footage (if available), the exact incident location, repair estimates, and any additional information required to assist with your investigation. Thank you.
NHTSA ODI #11756048
Official recalls
8Aug 31, 2026
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.
Consequence & remedy
Consequence: A lateral link separation could shift the wheel alignment, causing a loss of vehicle control and increasing the risk of a crash.
Remedy: 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.
Additional source detail variants (2)
Suspension:critical Fasteners
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.
Consequence: A lateral link separation could shift the wheel alignment, causing a loss of vehicle control and increasing the risk of a crash.
Remedy: 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.
Suspension:front
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.
Consequence: A lateral link separation could shift the wheel alignment, causing a loss of vehicle control and increasing the risk of a crash.
Remedy: 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.
Jul 7, 2026
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 requirements of Federal Motor Vehicle Safety Standard numbers, 208, "Occupant Crash Protection," 201, "Occupant Protection in Interior Impact," and Part 581, "Bumper Standards."
Consequence & remedy
Consequence: A noncompliant vehicle may have reduced occupant protections, increasing the risk of injury during a crash.
Remedy: Tesla will repurchase noncompliant vehicles currently registered in the United States, free of charge. Owner notification letters are expected to be mailed September 5, 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.
Additional source detail variants (2)
Structure:body:bumpers
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 requirements of Federal Motor Vehicle Safety Standard numbers, 208, "Occupant Crash Protection," 201, "Occupant Protection in Interior Impact," and Part 581, "Bumper Standards."
Consequence: A noncompliant vehicle may have reduced occupant protections, increasing the risk of injury during a crash.
Remedy: Tesla will repurchase noncompliant vehicles currently registered in the United States, free of charge. Owner notification letters are expected to be mailed September 5, 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.
Air Bags:knee Bolster
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 requirements of Federal Motor Vehicle Safety Standard numbers, 208, "Occupant Crash Protection," 201, "Occupant Protection in Interior Impact," and Part 581, "Bumper Standards."
Consequence: A noncompliant vehicle may have reduced occupant protections, increasing the risk of injury during a crash.
Remedy: Tesla will repurchase noncompliant vehicles currently registered in the United States, free of charge. Owner notification letters are expected to be mailed September 5, 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.
May 18, 2026
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."
Consequence & remedy
Consequence: Missing weight information provided by the label may lead to unintentionally overloading the vehicle, increasing the risk of a crash.
Remedy: 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.
Oct 10, 2025
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.
Consequence & remedy
Consequence: A loss of drive power can increase the risk of a crash.
Remedy: 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.
Oct 1, 2025
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."
Consequence & remedy
Consequence: 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.
Remedy: 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.
Additional source detail variants (2)
Electrical System:wiring
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."
Consequence: 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.
Remedy: 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.
Exterior Lighting:back Up Lights
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."
Consequence: 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.
Remedy: 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.
Jul 28, 2025
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.
Consequence & remedy
Consequence: An inoperable horn may prevent the driver from alerting other drivers as needed, increasing the risk of a crash.
Remedy: 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.
Jun 18, 2025
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.
Consequence & remedy
Consequence: The seat may not properly restrain the occupant, increasing the risk of injury during a crash.
Remedy: 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.
May 29, 2025
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."
Consequence & remedy
Consequence: The inability to clean the windshield reduces the driver’s visibility and increases the risk of a crash.
Remedy: 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.
Model-level recall history does not show whether a particular VIN is affected or has received a repair. Check a VIN with NHTSA ↗
NHTSA investigations
4EA26002 · Fsd Collisions In Reduced Roadway Visibility Conditions
Opened Mar 18, 2026 · No close date supplied
Status: open (inferred from source dates) · Electrical System:adas
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.
PE25012 · Traffic Safety Violations While Full Self Driving ("fsd") Is Engaged
Opened Oct 7, 2025 · No close date supplied
Status: open (inferred from source dates) · Electrical System:adas
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.
AQ25002 · Compliance With Standing General Order 2021-01 Reporting Requirements
Opened Aug 20, 2025 · No close date supplied
Status: open (inferred from source dates) · Electrical System:adas
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
PE24033 · Actually Smart Summon Sessions Resulting In low-speed Impacts.
Opened Jan 6, 2025 · Closed Apr 3, 2026
Status: closed (inferred from source dates) · Electrical System:adas:autonomous/self Driving
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.
Illustration