Tesla Model Y collision warning problems

Filed Oct 30, 2026 · Driver assistance · CA

The vehicle experienced a hardware failure of its primary Autopilot computer module (Hardware 3) while parked overnight. Upon starting the vehicle, all advanced driver assistance systems (ADAS) were disabled, including Autosteer, Traffic-Aware Cruise Control, Automatic Emergency Braking (AEB), lane-keep assist, and blind-spot monitoring. The vehicle also completely lost its backup camera functionality, side-repeater camera feeds, and internal safety chimes. Vehicle Service Mode diagnostics showed that the primary processor (ECU Primary A) was stuck in a low-level boot loop, displaying a state of AP IN COREBOOT and a status of INIT. The vehicle gateway active fault code was PM_a041_dasMIA, indicating that the DAS CAN node is missing because the processor was non-responsive on the internal communication network. The failure also disabled the internal cellular modem network, preventing navigation from working unless connected to Wi-Fi. Tesla Service technicians diagnosed the failure as an internal short circuit within a sealed component. Because this module has no moving parts and failed while parked, it represents a premature electrical breakdown of a non-serviceable core component. The sudden loss of Automatic Emergency Braking, forward collision warnings, and the rearview camera creates a safety hazard during operation.

Filed Oct 30, 2026 · Driver assistance · CA

Following a software update (2026.38.3.2), without any prior warning messages or symptoms, the vehicle's onboard computer failed on 10/26/26, which resulted in the loss of critical driver-assistance and safety systems. The affected systems included the backup and side-view cameras, blind-spot monitoring, emergency braking, collision warning, lane departure warning/assistance, rear cross-traffic alert, GPS, and adaptive headlights. The loss of the cameras and blind-spot monitoring reduced my ability to identify surrounding vehicles and pedestrians, while the loss of automatic emergency braking, collision warnings, and lane-assistance features eliminated important safety functions designed to help prevent accidents. The problem was confirmed by a Tesla Service Center. According to Tesla's diagnostic findings: "In this instance, your vehicle's computer consists of both a primary and a secondary component. Our diagnostic findings indicate that both parts failed, not due to an internal short, but because of a complete loss of communication between the primary and secondary units." Tesla inspected the vehicle and determined that the computer required complete replacement. The vehicle is currently at the Tesla Service Center awaiting repair and will be unavailable for inspection. A previous recall (25V‑002) addressed a similar computer failure and relied on a software update as a remedy, however the recurrence of a related failure raises concerns about whether that remedy was sufficient. I am concerned that the automatic software update on 10/26/26 may have contributed to the failure of the car computer. The fact that the failure occurred after the update, without any prior warning, and resulted in the loss of multiple critical safety systems presents a serious safety concern. A software update should not leave a vehicle without essential safety equipment or render multiple driver-assistance systems inoperable.

Filed Oct 29, 2026 · Driver assistance · VA · crash

I am reporting a serious safety incident involving my 2026 Tesla Model Y while using Full Self-Driving (Supervised). While my vehicle was making a left turn with FSD engaged, the system unexpectedly disengaged midway through the maneuver. Instead of completing the left turn, the vehicle continued traveling straight toward a parked car. I immediately attempted to take control and correct the vehicle's direction, but there was insufficient time to avoid the collision. I received no apparent advance warning before the disengagement. Additionally, the forward collision warning and automatic emergency braking systems did not appear to activate or intervene before impact. The collision caused significant damage to the front passenger-side bumper of my Tesla, requiring the vehicle to be towed. The vehicle subsequently underwent repairs, leaving me without transportation for approximately one month. I had been using Tesla's FSD system regularly for several months before this incident. I reported the incident to Tesla and contacted its FSD malfunction team, but I have not received a response, investigation findings, or an explanation regarding the unexpected disengagement and apparent lack of collision avoidance intervention. I am concerned that FSD may unexpectedly disengage during an active turning maneuver without sufficient advance warning or time for the driver to react. The apparent lack of collision warning or automatic emergency braking intervention further raises concerns about vehicle safety. I am requesting that the federal safety agency investigate this incident and determine whether a malfunction or safety defect contributed to the crash.

Filed Oct 28, 2026 · Driver assistance, Steering · GA · crash

On October 28, 2026 at about 3:57 PM EDT, my 2026 Tesla Model Y (Long Range RWD) was operating on Full Self-Driving (Supervised) as it turned left into our residential driveway in Watkinsville, GA. A family member's parked Subaru Forester was on the left side of the driveway with its right rear passenger door standing open. An adult was leaning into that doorway and a child was standing beside the car. The Tesla's dashcam (left pillar camera) shows the open door clearly in view for 6 to 8 seconds before contact. Despite this, Full Self-Driving did not stop or steer away. It slowed to about 2 mph but kept creeping forward alongside the Subaru, and the Tesla's left rear quarter panel struck the edge of the open door. The vehicle data export shows Full Self-Driving active and steering throughout, with no accelerator or brake input from me and near-zero steering torque from the driver. No forward collision warning or automatic emergency braking event was recorded. I braked about 5 seconds after contact, which disengaged Full Self-Driving. No one was injured, but a person was standing in the door opening the car struck. The Tesla has a V-shaped dent and gouge in the left rear quarter panel, with the paint cut through. Estimated repair cost is over $5,000. I expected the system to detect a stationary open door with a person in it and either stop or steer around it. I have the dashcam footage from all six cameras and Tesla's vehicle data export, and can provide both.

Filed Oct 25, 2026 · Driver assistance · GA · crash · 1 injury

I am reporting a serious safety concern involving my 2026 Tesla Model Y AWD. VIN: [XXX] Mileage: Approximately 16,000 miles At approximately 8:00 a.m. XXX Monday, I was driving manually uphill in bright sunlight. Sun glare affected my visibility, and I did not notice that the vehicle ahead had stopped. I did not receive a forward-collision warning before my Tesla struck the vehicle in front at approximately 25 mph. After the first impact, I felt the steering wheel move by itself. The vehicle then moved sideways and struck a tree. The resulting damage includes the front bumper, hood, front wheel area, and left-front door. The vehicle is undrivable. The airbags did not deploy. I am requesting a formal safety investigation into the unexpected steering movement, the absence of a forward-collision warning, and the vehicle's behavior after the first impact. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Oct 16, 2026 · Acceleration, Airbags · 30,616 miles · CA · crash

The contact owns a 2023 Tesla Model Y. The contact stated that while pulling into a parking space with the brake pedal depressed, the vehicle unintendedly accelerated and struck an occupied parked vehicle ahead. Upon shifting into Reverse (R), the failure recurred, causing the vehicle to strike the front bumper of a parked and unoccupied USPS truck, which then struck a parked, unoccupied vehicle. The contact engaged the electric parking brake to stop the vehicle. The contact stated that the forward collision avoidance system failed to engage to prevent the collisions. The front driver's side air bag failed to deploy as expected. The vehicle sustained rear-end damage. The vehicle was towed to an auto collision center, where a superficial diagnostic inspection was performed, and the contact was informed that no failure was found. The manufacturer was notified of the failure and referred the contact to a Tesla Service center and to the federal safety agency Hotline for assistance. The failure mileage was 30,616.

Filed Oct 15, 2026 · Driver assistance · GA

On October 7, 2026 at about 5:01 PM, on I-75 near Acworth, Georgia, in clear daylight, my 2023 Tesla Model Y was operating with Full Self-Driving (Supervised) engaged at about 76 mph. The vehicle moved from a general traffic lane into an express lane that was closed, and continued toward physical barricades and an impact attenuator at the end of the closed lane. At least three advance signs indicated the express lanes were closed, including an overhead gantry reading EXPRESS LANES CLOSED directly ahead, and the word EXPRESS was painted on the pavement under the vehicle. The vehicle did not slow, issued no warning or takeover request, and made no evasive maneuver. I avoided the barricades with a reflexive steering input. At that moment there was a concrete divider on my left, a tractor-trailer in the lane to my right, and, as I learned only from the footage afterwards, a vehicle following in the lane I moved into. There was no collision and no injury. Tesla's own vehicle data export confirms the sequence. The Self-Driving state was ACTIVE_FSD continuously from 3:53 PM until 5:01:09 PM, when it changed to UNAVAILABLE in the middle of a rising steering torque (0.42 to 0.92 Nm, peaking at 2.01 Nm). That is consistent with a driver override, not a handover request. No automatic emergency braking event, forward collision warning or takeover alert is recorded in the surrounding two minutes. Speed was 76 mph before the intervention and 63 mph six seconds later, with no brake event. I have preserved all six dashcam cameras for the six minutes around the event, the vehicle data export, and a recording of the in-car dashcam viewer showing "70 MPH, Self-Driving" shortly before the event. The vehicle received a software update on October 11, so I cannot confirm the FSD version active on October 7. Tesla's support interface cited FSD v14.3.11 and software 2026.33.5. When I reported this through the Tesla app, it directed me to submit a bug report and report to the federal safety agency

Filed Oct 12, 2026 · Driver assistance · WA · crash

On XXX, I was involved in a collision in [XXX], while manually driving my 2022 Tesla Model Y (VIN: [XXX]). Neither Full Self-Driving (FSD) nor Autopilot was engaged. I was making a right turn at a red traffic signal while another vehicle was making a U-turn. My Tesla collided with the passenger-side door of the other vehicle. Before the collision, I did not receive any audible or visual Forward Collision Warning (FCW). I also did not observe the Automatic Emergency Braking (AEB) system activating or attempting to slow the vehicle before impact. My approximate speed at the time of the collision is unknown. No injuries occurred. I am concerned that the vehicle's Forward Collision Warning and Automatic Emergency Braking systems did not respond to the collision risk. I understand these systems have operating limitations, particularly during turning maneuvers, but I would like this incident documented as a potential vehicle safety concern. I request that the federal safety agency review this incident to determine whether further investigation is warranted, including whether the vehicle detected the collision risk and whether the safety systems were functioning as designed. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Oct 10, 2026 · Driver assistance, Electrical · NC

Subject: Urgent Safety Defect: Post-Disengagement Touchscreen Prompt Causes Acute Driver Distraction Feature Involved: Full Self-Driving (Supervised) Post-Takeover Feedback Modal Safety Concern: When a driver manually disengages FSD (Supervised), it is almost always because the vehicle entered a complex, unexpected, or hazardous scenario that demanded immediate human intervention. At the exact second the driver assumes physical control of the vehicle—when 100% of driver visual attention and cognitive bandwidth must be on the roadway—the center display flashes a persistent multi-choice survey requesting feedback on why the disengagement occurred. The Hazard: Visual Diversion During Critical Moments: Presenting bright, interactive UI cards requiring glance time and manual touch interaction immediately after a takeover directly contradicts basic human-factors engineering and crash avoidance principles. Cognitive Overload: Instead of stabilizing the vehicle in manual control, the driver's attention is competed for by an on-screen prompt asking for data categorization. UI Contradiction: While the cabin camera actively penalizes drivers for split-second glances away from the road, the vehicle OS simultaneously prompts the driver to look at and touch the center screen during the most dangerous phase of a driving sequence. Requested Remediation: Provide a toggle under Controls > Autopilot to disable post-disengagement prompts entirely (e.g., "Prompt for Takeover Feedback: OFF"), or suppress all on-screen interactive surveys until the vehicle is placed in Park. Driver telemetry collection should never compromise active collision avoidance. --- This issues happens whenever disengaging fsd. Its not a one time thing. They have updated the software in my car multiple times but haven't fixed this. My location doesn't matter, speed doesn't matter. They added it in an update after more that two years of using the car and I cannot get rid of it.

Filed Oct 8, 2026 · Acceleration, Driver assistance · CA

On XXX at approximately 1:18 PM Pacific Time in [XXX], my Tesla Model Y collided with a stationary metal post/barrier while operating under Full Self-Driving (Supervised). FSD was controlling the vehicle during a low-speed maneuver. The vehicle moved forward and struck the stationary obstacle. I did not intentionally press the accelerator, apply the brakes, or override the steering before impact. I applied the brakes only AFTER the collision. This was not a collision caused by my manually steering or accelerating the vehicle into the obstacle. I have preserved the original Tesla-recorded accident video, which displays the blue "Self-Driving" indicator during the relevant maneuver. Tesla's official vehicle data also records: 13:17:50.255 - ACTIVE_FSD 13:18:17.661 - Significant acceleration anomaly, approximately -7.29 m/s², consistent with a possible impact 13:18:18.268 - DRIVER_APPLYING_BRAKES 13:18:18.285 - FSD state UNAVAILABLE The suspected impact event occurred approximately 0.607 seconds before the recorded manual braking event. This supports my account that I braked in response to the collision, not before it. I am concerned that FSD failed to avoid a stationary obstacle while controlling the vehicle. I request that the federal safety agency investigate FSD obstacle detection, path planning, steering, propulsion and braking behavior, and whether adequate collision warnings were provided. I request preservation and examination of Tesla's complete FSD logs and an assessment of whether the automated system contributed to this collision. I dispute any assumption that this incident was caused solely by manual driver operation. I have the original video, Tesla CSV data and damage photographs available as evidence. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)