Forward Collision Avoidance. Review the 45 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
Lane Departure. Review the 19 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
Electrical System. Review the 17 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →

NHTSA owner reports · September 18, 2026 snapshot.

30 crash reports3 fire reports10 injury reports

What owners actually said

98 reports

Mileage unknown · Jun 25, 2025

Electrical SystemFire

Smoke began coming out of the vents while driving. Battery was at 2%. Driver pulled over, exited vehicle and within 2 minutes flames could be seen (on video) coming from the center, dash area of the vehicle. Fire developed rapidly. Lt. Copley Detroit Fire Department, Fire investigation section 313-237-0466

NHTSA ODI #11669250

Mileage unknown · Jun 23, 2025

Back Over PreventionLane DepartureCrash

Read full complaint

Shortly after purchasing the vehicle in late 2024, I began experiencing multiple safety-related malfunctions. These issues include: Full Self-Driving (FSD) malfunction: On the third use of FSD, the vehicle attempted to enter a left-turn lane but failed to fully move into the lane, resulting in the right front panel of the vehicle colliding with the bumper of a truck in the adjacent lane. There were no warnings from the system prior to the collision. The incident occurred at low speed. The truck sustained no visible damage, and the rubber from the truck's bumper transferred to the car, which was removed by hand later. This event raised serious concerns about the safety and reliability of the FSD system. No police report was filed, and the manufacturer was not present at the scene. Backup alert system failure: On several occasions while reversing, the car failed to issue audible or visual alerts despite vehicles being within 10–15 feet. In one instance, the screen finally showed a red zone when a car was within 10 feet, but still provided no audible warning. This issue has been intermittently reproducible but not consistent. It poses a significant risk to pedestrians and other drivers, particularly in low-visibility or driveway situations. Manufacturer's Response: The vehicle was inspected by Tesla. After one in-person service visit and extended discussions, Tesla service representatives stated there was “nothing more they could do” and that a buyback was the only next step. A buyback request was submitted by a Tesla representative but has not been acknowledged or resolved more than 45 days later.

NHTSA ODI #11668644

Mileage unknown · May 27, 2025

Unknown Or OtherCrash

My Model Y reversed twice in a month while in 'D' drive mode. In one incident, I was pulling my car out of the parking lot in a garage and shifted the gear stalk down multiple times to engage 'D' drive mode. Instead of moving forward, the car reversed and collided with the garage wall.

NHTSA ODI #11663073

Mileage unknown · May 22, 2025

Unknown Or Other

Read full complaint

I signaled for a slight turn to the right. And then within 100 yards I came to an intersection where the main path , my path, of travel beared left. As I approached this T and was about to bear left, I saw the driver on the leg of the T about to pull directly into my path… because they saw that my right turn signal was still on about 60 yards after my original partial turn. Fortunately, I slowed and they paused. That was when I realized the reason for the confusion…that my original right turn signal was still on. The indicator shuts off too late. I would say a good bit later than a typical turn signal.

NHTSA ODI #11662643

Mileage unknown · May 22, 2025

Vehicle Speed Control

Both my wife and I accidentally used the right side stalk to signal for a turn. Our mistake, except the car responded by suddenly accelerating. Fortunately we were both able to put on the brake. In the wrong situation this could be very dangerous.

NHTSA ODI #11662637

Mileage unknown · May 21, 2025

Exterior Lighting

Read full complaint

While vehicle was driving on FSD at approximately 75 mph on freeway, the vehicle in front of me kicked up a small piece of tire trend. the piece of tire hit the headlight and shattered the glass on the headlight assembly, while not damaging any other part of the car. I have owned quiet a few cars from all makes including another Tesla however it seems this cannot be normal for the headlight assembly to shatter with such a small piece of rubber. I have tried to reach out to Tesla but they of course refuse any possibility of defect with Model Y headlight assembly so I wanted to submit this incident in hope that if enough people have experienced similar incident with their headlight assembly it would be recalled

NHTSA ODI #11662280

Mileage unknown · Apr 26, 2025

Unknown Or Other

Read full complaint

Critical Safety Defect Report – Tesla Full Self-Driving (FSD) Malfunction on [XXX] I am writing to formally report a critical and potentially deadly safety defect involving Tesla’s Full Self-Driving (FSD) system. During a recent road trip with my husband and daughter from Boston, MA to Washington, D.C., I used Tesla's FSD feature. On our return trip on [XXX] while traveling on [XXX] under FSD control, the system demonstrated erratic and dangerous behavior that nearly caused a fatal accident. As we approached an intersection on [XXX] , I observed that the traffic lights were red. However, the vehicle—still under FSD control—continued traveling at approximately 70 mph without slowing down. Sensing something was wrong, I quickly intervened and manually stopped the car at the intersection, where cross traffic was moving at high speeds in both directions. Had I reacted even a second later—or had the lights remained red in our direction—we likely would have been struck and potentially killed by the oncoming traffic. After reviewing dashcam footage from the incident, I confirmed that the FSD system had not only failed to recognize the red traffic signal but had also directed the car onto the wrong path, leading us into the potential path of oncoming vehicles. This serious failure posed an extreme and unacceptable risk to my family’s lives. Following the incident, my young daughter was deeply traumatized and developed a high fever that night. This experience has left lasting emotional and psychological distress for all of us. I believe this event highlights a severe and urgent defect in Tesla’s FSD system. I respectfully urge the NHTSA to launch an immediate investigation to prevent similar occurrences that could result in injury or loss of life. I am prepared to submit the dashcam footage and relevant vehicle logs to support this report. Please advise on the next steps for providing this evidence. Thank you for your attention INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ODI #11656974

Mileage unknown · Apr 22, 2025

Visibility

Read full complaint

Vehicle Component: Exterior Mirrors Make: Tesla Model: Model Y Model Year(s): 2022, 2023, 2024 (and ongoing) Problem Description: Since the 2022 model year, the Tesla Model Y has exhibited a recurring issue with excessive vibration in the driver side exterior mirror at highway speeds. The vibration becomes noticeable around 50 mph and increases in severity with speed, making it difficult to clearly see vehicles in the adjacent lane. This issue persists even after mirror replacements or realignments, indicating a possible design or manufacturing defect affecting multiple vehicles. The vibration affects driver visibility and could pose a significant safety risk, particularly during lane changes or merging maneuvers. Numerous Model Y owners have reported similar complaints in forums and online communities, suggesting this may be a widespread issue. Tesla service centers have been unable to provide a consistent or effective fix for the problem. Safety Concern: The impaired visibility caused by the vibrating mirror compromises driver awareness and increases the likelihood of collisions. This defect should be investigated for potential recall or corrective action.

NHTSA ODI #11655993

Mileage unknown · Apr 17, 2025

Wheels

Read full complaint

"What component or system failed or malfunctioned, and is it available for inspection upon request?" The rear left tire (interior side) and rim assembly failed while driving under normal conditions. The tire experienced a sudden blowout, and the rim sustained significant damage. Based on the damage observed, it appears the rim may have failed first, puncturing the tire and causing the blowout. Yes, the damaged components are available for inspection upon request. "How was your safety or the safety of others put at risk?" The sudden tire blowout at freeway speeds (60+/- mph) could have posed a serious risk to my safety and the safety of other drivers. Fortunately, I was able to maintain control of the vehicle and safely pulled over to the shoulder. "Has the problem been reproduced or confirmed by a dealer or independent service center?" As of now, the issue has not yet been reproduced or confirmed by a Tesla dealer or independent service center, Tesla repair staff immediately ruled out any responsibilities as they perceived to be a foreign object hit the inside of the driver rear tire, which I did not feel anything hitting the car or the tires bumping any object. We went to an authorized Continental dealer/store to inquire for procedure on how to request for investigation for any tire defects, but we were told by the manager that if the tire is OEM, they do not accept. "Has the vehicle or component been inspected by the manufacturer, police, insurance representatives or others?" The vehicle and damaged components have not yet been formally inspected by Tesla, police, or insurance representatives, but I am preparing documentation and plan to submit everything for evaluation by Tesla and possibly my insurance. "Were there any warning lamps, messages or other symptoms of the problem prior to the failure, and when did they first appear?" There were no messages (Sentry by Tesla), or symptoms prior to the failure. The tire pressure was actively monitored.

NHTSA ODI #11655135

Mileage unknown · Apr 8, 2025

Forward Collision AvoidanceLane Departure

Read full complaint

While driving westbound on Lee Jackson Memorial Highway (U.S. Route 50) after passing the intersection with Stonecroft Boulevard in Chantilly, Virginia, the Autopilot system on my Tesla Model Y malfunctioned. Without any warning or obstacle in my lane, the vehicle suddenly and sharply veered to the right, directly toward two vehicles traveling in the adjacent lane. I was holding the steering wheel at the time and was able to immediately countersteer to prevent a collision. There were no audible or visual warnings from the vehicle before or during the incident. The Autopilot system did not display any messages or alerts, and no braking or turn signal was engaged by the system. The lane shift was abrupt and uncommanded. The dashcam footage clearly captured the incident, and it is available for inspection upon request. To my knowledge, the issue has not yet been reproduced or inspected by the manufacturer or service center. The vehicle has not been examined by police, insurance representatives, or others at this time. This unexpected maneuver created a serious safety risk for myself and nearby drivers.

NHTSA ODI #11653356

Official recalls

26V315000 · Equipment:other:labels

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.

25V002000 · Back Over Prevention:software; Electrical System

Jan 6, 2025

Tesla, Inc. (Tesla) is recalling certain 2024-2025 Model 3, Model S, 2023-2025 Model X, and Model Y vehicles. The computer circuit board may short, resulting in the loss of the rearview camera image. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 111, "Rear Visibility."

Consequence & remedy

Consequence: A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.

Remedy: Tesla released an over-the-air (OTA) software update, free of charge. Tesla will also identify any vehicles that experienced a circuit board failure, or stress that may lead to a circuit board failure, and replace the affected computers, free of charge. Owner notification letters were mailed March 7, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-00-001.

Additional source detail variants (2)

Back Over Prevention:software

Consequence: A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.

Remedy: Tesla released an over-the-air (OTA) software update, free of charge. Tesla will also identify any vehicles that experienced a circuit board failure, or stress that may lead to a circuit board failure, and replace the affected computers, free of charge. Owner notification letters were mailed March 7, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-25-00-001.

Electrical System

Consequence: A rearview camera that does not display an image reduces the driver's rear view, increasing the risk of a crash.

24V935000 · Tires:pressure Monitoring And Regulating Systems

Dec 17, 2024

Tesla, Inc. (Tesla) is recalling certain 2024 Cybertruck, 2017-2025 Model 3, and 2020-2025 Model Y vehicles. The tire pressure monitoring system (TPMS) warning light may not remain illuminated between drive cycles, failing to warn the driver of low tire pressure. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard number 138, "Tire Pressure Monitoring Systems."

Consequence & remedy

Consequence: Driving with improperly inflated tires increases the risk of a crash.

Remedy: Tesla released an over-the-air (OTA) software update, free of charge. Owner notification letters were mailed February 15, 2025. Owners may contact Tesla customer service at 1-877-798-3752. Tesla's number for this recall is SB-24-00-018.

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

EA26002 · 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 traﬃc 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 traﬃc 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 identiﬁed a number of incidents in which the inputs to the dynamic driving task commanded by FSD induced vehicle behavior that violated traﬃc safety laws. Although reports of this nature span a variety of behaviors, the reports appear to most commonly involve two types of scenarios. The ﬁrst type of scenario involves a vehicle operating with FSD proceeding into an intersection in violation of a red traﬃc signal. The second type of scenario involves FSD commanding a lane change into an opposing lane of traﬃc. With respect to the ﬁrst type of scenario, ODI has identiﬁed 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 traﬃc signal, failed to stop fully, or failed to accurately detect and display the correct traﬃc 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 traﬃc signal. ODI has identiﬁed six Standing General Order ("SGO") reports in which a Tesla vehicle, operating with FSD engaged, approached an intersection with a red traﬃc 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 identiﬁed 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 identiﬁed 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.