NHTSA owner reports · September 18, 2026 snapshot.
Forward Collision Avoidance complaints
106 reportsClear category filterMileage unknown · Feb 11, 2026
Forward Collision AvoidanceLane DepartureSteering
I am reporting a safety incident involving my Tesla while Autopilot/Full Self-Driving was engaged. On February 11, 2025 at approximately 9:22 am, on Waccamaw Medical Park Ct Conway, SC 29526, I was driving on a normal city street with the system actively controlling steering and speed. Without any warning or alert, the vehicle …
Read full complaint
I am reporting a safety incident involving my Tesla while Autopilot/Full Self-Driving was engaged. On February 11, 2025 at approximately 9:22 am, on Waccamaw Medical Park Ct Conway, SC 29526, I was driving on a normal city street with the system actively controlling steering and speed. Without any warning or alert, the vehicle suddenly steered to the right toward the curb and struck it. I was very attentive, but the steering movement happened too quickly for me to safely prevent the impact. No forward collision warning, lane departure alert, or disengagement occurred prior to the incident. The impact caused damage to the wheel and tire (see attached photo). This behavior appears to be an incorrect steering decision by the automated driving system after misinterpreting the roadway edge or lane boundary. I am requesting review of the vehicle logs and investigation of the system behavior during this event.
NHTSA ODI #11717428
Mileage unknown · Jan 27, 2026
Forward Collision AvoidanceVehicle Speed Control
Vehicle equipped with Tesla Full Self-Driving (Supervised v 14.2) software exhibits unsafe automated following behavior. The system maintains following distances that are too short at steady speeds, including behind stable lead vehicles with no braking or traffic disturbances. Tesla’s own Safety Score system flags this behavior…
Read full complaint
Vehicle equipped with Tesla Full Self-Driving (Supervised v 14.2) software exhibits unsafe automated following behavior. The system maintains following distances that are too short at steady speeds, including behind stable lead vehicles with no braking or traffic disturbances. Tesla’s own Safety Score system flags this behavior as “following too closely,” indicating elevated collision risk. However, the driver has no available control to adjust minimum following distance or impose safer headway while using FSD This represents unsafe autonomous tailgating behavior with loss of driver control authority over safe following distance, creating increased risk of rear-end collision and hazardous automated driving conditions. Tesla offers several controls (Sloth, Chill, Standard, Hurry, and MadMax) modes, none of which solve the issue if the driver in front is driving the speed limit. My car under FSD will crowd (or tailgate) the front car regardless of the mode. In one instance, I was following a car under FSD in sloth mode and it made the car in front of me pull over just to get me off their tail.... this is certainly now how I wish to drive, and don't want my car driving this way. Failure mode: automated headway policy dominance, lack of driver override, unsafe autonomous following distance.
NHTSA ODI #11713624
Mileage unknown · Jan 27, 2026
Forward Collision AvoidanceVehicle Speed Control
Vehicle equipped with Tesla Full Self-Driving (Supervised v 14.2) software exhibits unsafe automated behavior due to removal of driver speed control. The system infers speed limits and driving speed without allowing the driver to set a safe maximum speed. In residential neighborhoods with children, pedestrians, and shared socia…
Read full complaint
Vehicle equipped with Tesla Full Self-Driving (Supervised v 14.2) software exhibits unsafe automated behavior due to removal of driver speed control. The system infers speed limits and driving speed without allowing the driver to set a safe maximum speed. In residential neighborhoods with children, pedestrians, and shared social spaces, the vehicle drives at model-inferred speeds that are socially and physically unsafe. Driver is unable to impose a lower safe speed limit without disengaging. Tesla removed previous option for driver to adjust speed. In a state park campground, the system failed to detect a posted 15 mph speed limit and inferred a 55 mph limit. The vehicle accelerated to unsafe speeds on narrow, pedestrian-heavy roads, with no driver ability to cap speed while under FSD. This represents a loss of human override authority and unsafe autonomous system behavior, creating pedestrian hazard and safety risk. Failure mode: automated speed inference dominance, map prior misclassification, lack of driver override, unsafe autonomous acceleration in pedestrian environments.
NHTSA ODI #11713614
Mileage unknown · Jan 26, 2026
Forward Collision Avoidance
On full self driving, there is no way to change the follow distance and it follows way too close very often. This generates incidents that the car reports to Tesla insurance and we are penalized for something we can't always control. We also can't change our speed but I'm more concerned about the follow distance on highways. …
Read full complaint
On full self driving, there is no way to change the follow distance and it follows way too close very often. This generates incidents that the car reports to Tesla insurance and we are penalized for something we can't always control. We also can't change our speed but I'm more concerned about the follow distance on highways. Last incident at 7:46PM on 1/25/2026.
NHTSA ODI #11713351
Mileage unknown · Jan 20, 2026
Forward Collision AvoidanceLane Departure
On January 20, around 9:35 am, Phoenix time, I had the car in self-driving mode for a left-hand turn at the intercession of Camino Real and River Road in Tucson, Arizona. A real-time view shows that it’s a tricky and dangerous left-hand turn. For the past 3 weeks, the car navigated it well, waiting until it was perfectly safe …
Read full complaint
On January 20, around 9:35 am, Phoenix time, I had the car in self-driving mode for a left-hand turn at the intercession of Camino Real and River Road in Tucson, Arizona. A real-time view shows that it’s a tricky and dangerous left-hand turn. For the past 3 weeks, the car navigated it well, waiting until it was perfectly safe to do so. Today, however, the car moved quickly and unexpectedly into the center of River Road, narrowly escaping a head on collision with a west-bound car, and then paused, squeezed in between west and east-bound lanes when I tapped the brake and took the wheel. Everything happened so quickly. I made the left turn into the east-bound lane, but, looking back, I don’t know how an accident didn’t occur, as traffic was still moving in east-bound lanes rapidly. There must have been enough distance between two cars at just the right time, that nothing hit me.
NHTSA ODI #11712177
Mileage unknown · Jan 20, 2026
Forward Collision Avoidance
The vehicle repeatedly [XXX] [XXX], and [XXX] displays critical safety alerts indicating failure of the parking brake and automatic vehicle hold systems. Specific error codes documented include: •DI_a246: Automatic vehicle hold disabled (Use brake pedal when stopping) •EPBL_a179: Parking brake functions degraded (Parking brake m…
Read full complaint
The vehicle repeatedly [XXX] [XXX], and [XXX] displays critical safety alerts indicating failure of the parking brake and automatic vehicle hold systems. Specific error codes documented include: •DI_a246: Automatic vehicle hold disabled (Use brake pedal when stopping) •EPBL_a179: Parking brake functions degraded (Parking brake may not apply or release) •UI_a019: Parking brake functions degraded INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA ODI #11712063
Mileage unknown · Jan 7, 2026
EngineForward Collision Avoidance
I was driving in full self driving mode on my Tesla model Y. The car stopped at the left turn stoplight as it does normally. And then while the light was still red and the cross traffic was green (traffic flowing), the Tesla released the brake, accelerating into the intersection. I stomped on the brake and kept the car from full…
Read full complaint
I was driving in full self driving mode on my Tesla model Y. The car stopped at the left turn stoplight as it does normally. And then while the light was still red and the cross traffic was green (traffic flowing), the Tesla released the brake, accelerating into the intersection. I stomped on the brake and kept the car from fully entering the intersection, then continue home without using Full Self Driving mode any further. If I hadn’t intervened, the Tesla would have caused an accident, injury, or even death.
NHTSA ODI #11709468
Mileage unknown · Dec 19, 2025
Forward Collision Avoidance
When in self driving mode, which activates the adaptive cruise control, it is not possible to set the following distance. The following distance automatically selected by Tesla self driving is much too close to the vehicle in front of me. Tesla has removed the ability to set the following distance. It follows at approximately…
Read full complaint
When in self driving mode, which activates the adaptive cruise control, it is not possible to set the following distance. The following distance automatically selected by Tesla self driving is much too close to the vehicle in front of me. Tesla has removed the ability to set the following distance. It follows at approximately 2 seconds behind the car in front of me, regardless of my vehicle speed .... at 80 MPH 2 seconds is not enough time for a driver to react. Following distance should be controllable by the driver. Taking away this ability deprives a driver of driving within their own limitations.
NHTSA ODI #11706165
Mileage unknown · Dec 18, 2025
Forward Collision Avoidance
While driving on a residential street at night with Full Self-Driving (Supervised) engaged, the vehicle suddenly applied Automatic Emergency Braking without any visible obstacle, vehicle, pedestrian, or hazard present. The braking was abrupt and unexpected and did not correspond to traffic, road conditions, or driver input. No …
Read full complaint
While driving on a residential street at night with Full Self-Driving (Supervised) engaged, the vehicle suddenly applied Automatic Emergency Braking without any visible obstacle, vehicle, pedestrian, or hazard present. The braking was abrupt and unexpected and did not correspond to traffic, road conditions, or driver input. No collision occurred, but the sudden stop caused a whiplash effect to occupants, creating a risk of injury despite the absence of an external hazard. The driver immediately disengaged the system after the event. Tesla later reviewed vehicle data and confirmed that an Automatic Emergency Braking event occurred while FSD (Supervised) was active. Tesla identified the software version as FSD v14.2.1 and documented the incident as unexpected emergency braking, with the date, time, location, and environmental conditions recorded.
NHTSA ODI #11705810
Mileage unknown · Dec 17, 2025
Forward Collision AvoidanceService Brakes
There is a SERIOUS safety-related FSD (full self driving) fundamental design flaw with stop sign behavior. On previous versions AND on the latest and best version of FSD (currently that is v14.2.1.25) when FSD approaches a stop sign AND there is no white painted stopping line, FSD will make its full initial stop (also called th…
Read full complaint
There is a SERIOUS safety-related FSD (full self driving) fundamental design flaw with stop sign behavior. On previous versions AND on the latest and best version of FSD (currently that is v14.2.1.25) when FSD approaches a stop sign AND there is no white painted stopping line, FSD will make its full initial stop (also called the zero-speed stop) directly at or behind the stop sign instead of making the initial full stop beyond the stop sign at a location where the driver can see cross traffic. Sometimes the FSD initial full stop is 20, 30, 40, even 50+ feet back away from the edge of the road. At these distances from the edge of the road, most of the time, there is NO VISUAL of cross traffic left and right. The FSD stop then turns into the FSD "creep" where FSD, after stopping 30 feet back WILL THEN commit to the turn from 30 feet back giving drivers little to no time to see cross traffic. If I am the supervisor of FSD who is liable for my safety and my vehicle's safety, I need to be able to see cross traffic before my car (with FSD engaged) decides to commit to the turn, but FSD DOES NOT CARE IF THE DRIVER CAN SEE. The "creep" is perhaps the least human-like manuever that FSD performs. From the stopped location directly at the stop sign, they creep may inch up and stop again, it may inch up a COUPLE TIMES and stop again, it may pull up to the edge of the road and stop again, OR it may just pull out into oncoming traffic in one swift motion. Bc of this behavior, FSD has almost got rear ended countless times at stop signs. Also, cross traffic see's the creep and thinks i'm about to pull out in front of them Drivers go beyond the stop sign to a location where they can see to make their one and only full stop. To avoid this issue, FSD needs to do this too (i.e. make initial full stop at the edge of the road) This is legal in mostly every state (I live in PA) Tesla has not provided a single response to these reports and nothing seems to be getting done about it.
NHTSA ODI #11705498
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