Tesla Model Y abs comes on

Filed Sep 24, 2026 · Acceleration, Airbags · CA · crash

On September 23, 2026, the vehicle was being driven at low speed when the driver experienced sudden and unexpected acceleration. The vehicle rapidly accelerated and a collision occurred. The driver reports that she did not intentionally accelerate the vehicle to this degree. Vehicle data and the Event Data Recorder (EDR) were subsequently obtained. The data records the vehicle accelerating from approximately 0 mph to approximately 35 mph in about four seconds, with the recorded accelerator-pedal-position signal reaching 100%. The EDR does not record brake application before the first crash trigger. Vehicle data records driver brake application shortly after the initial crash trigger, including ABS activity. The cause of the accelerator-pedal-position signal is UNKNOWN. It has not been determined whether the recorded signal resulted from driver pedal application, the accelerator pedal/sensor system, or another vehicle system. I am reporting this because of the sudden acceleration and severity of the resulting collision and would like the incident reviewed as a potential vehicle safety issue. The EDR also indicates that airbag and seat-belt pretensioner deployment was not commanded during either of the two recorded crash events. Given the severity of the collision, I am also reporting the lack of airbag deployment as a safety concern. I do not know whether the collision met the applicable deployment thresholds. The vehicle is available for inspection. The EDR report and complete raw vehicle-data CSV have been preserved. There were no known warning messages indicating an accelerator problem before the incident.

Filed Sep 17, 2026 · Driver assistance · NJ

On XXX at about 6:14 AM, my 2026 Tesla Model Y drove into a flooded railroad underpass on [XXX] near [XXX], with Full Self-Driving (Supervised) engaged and a navigation route active. It was raining heavily (Newark Airport measured 1.25 in from 5:51 to 6:51 AM), the light was poor around sunrise, and the underpass was dark. The water depth was not apparent to me. At 6:12 AM the National Weather Service had issued a Flash Flood Warning naming [XXX] and listing underpasses. Tesla's data log (my privacy export) records FSD active from 6:12:02, my third FSD session that morning. With FSD active, speed rose from 7 to 27.4 mph between 6:14:04 and 6:14:31, with no accelerator input recorded. Speed then fell sharply (up to about 0.3 g), which I believe is when the car hit the water. FSD stayed active about 8 seconds (200 ft) more; the state changed to ABORTING at 6:14:39, at about 6 mph. I saw no warning, and the export shows none during the approach. We could not drive out. Water rose to about window level and entered the cabin. From 6:17 the log shows restraint system, AEB, ABS, stability and traction control alerts. I lowered a window at about 6:19. At 6:25 the log shows both front door releases activated repeatedly; neither door opened. We climbed out the window onto the roof. Our videos show us there at 6:31 with the front of the hood and headlights under water, and the Elizabeth Fire Department rescued us by boat at about 6:51. The car is a total loss. UNKNOWN: exact water-entry speed, what FSD perceived, and why it disengaged. I ask the federal safety agency to investigate whether FSD detects and responds to flooded roads in heavy rain and poor light, to obtain Tesla's data for this event, and to review escape from a flooded vehicle whose doors did not open. A report with the data timeline is attached. The full Tesla data export and videos are available on request. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Aug 16, 2026 · Acceleration, Electrical · CA · crash

COMPONENT/SYSTEM THAT FAILED: The service brakes failed to stop the vehicle. While reverse-parking at low (parking) speed, I applied the brake pedal and the vehicle did not stop as expected, resulting in contact with an object and vehicle damage. The vehicle is available for inspection upon request; it has been preserved and driven only minimally since the event. HOW SAFETY WAS PUT AT RISK: The brakes failed with no warning. Had a person been behind the vehicle, the failure to stop could have caused injury. This is the only vehicle for a family with three children who are regularly transported in it, and I no longer feel safe driving them. REPRODUCED/CONFIRMED BY A DEALER OR SERVICE CENTER: Not yet. INSPECTED BY MANUFACTURER/POLICE/INSURANCE/OTHERS: The insurer opened and then denied the claim and stated that no vehicle telemetry/data was available to preserve. No independent forensic inspection has occurred yet. Police did not attend. WARNING LAMPS/MESSAGES/SYMPTOMS PRIOR TO FAILURE: NONE. There was no warning light, no alert message, and no audible signal before or during the event. The parking sensors did not beep as they normally do. No ABS or brake warning light appeared at any time before or after. ADDITIONAL RELEVANT DETAIL: Approximately one week earlier, the front lower control arms were replaced. It is UNKNOWN whether the ABS wheel-speed sensor or related wiring was affected; the vehicle displayed no related warning at any time. No injuries occurred.

Filed Aug 14, 2026 · Steering · TX · crash · 1 injury

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 the federal safety agency 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

Filed Jul 25, 2026 · Driver assistance, Steering · IL · crash · 1 injury

On June 7, 2026, I was driving westbound on I-290 in the leftmost lane in a 2024 Tesla Model Y. I recall FSD (Supervised) was engaged and making a lane change into the left lane. Instead of settling in the lane, the vehicle continued left and struck the divider/median. I braked. The vehicle then bounced back and moved right toward a large truck and collided. I did not receive a takeover warning before the event. The front bumper came off and the vehicle became inoperable. A fire truck traveling behind me blocked traffic after the crash. Tesla event data records a Crash Algorithm Wake-Up at about 9:49 a.m. Central and includes speed, steering, braking, acceleration, ABS, lane-assist, and cruise-control signals. I reported the safety concern to Tesla and asked for review of the FSD/software issue and data, but I have not received written findings. I do not have an expert determination that FSD caused the crash. I am asking the federal safety agency to review the incident and data for a possible driver-assistance, steering, or lane-control safety defect.

Filed Jun 4, 2026 · Driver assistance, Electrical · CA

The vehicle’s secondary Autopilot Processor / car computer is internally faulted and stuck in a continuous wake/shutdown loop. This causes severe standby battery drain (~20 miles of range lost per day while parked) and completely prevents all over-the-air software updates - including federally mandated safety recall remedies. On April 4, 2024, Tesla Service diagnosed the fault and linked it to the drain and inability to update. On the same visit, Tesla added two safety recalls (23V‑838 Autosteer controls and 24V‑051 Brake/Park/ABS indicators) to the work order. They then demanded ~$3,000 customer payment for computer replacement before the recalls could be performed. After I declined the paid repair, Tesla marked both recalls as “completed” via software update despite the same invoice stating the vehicle could not receive updates and remained on software version 2023.38.9 (which predates both remedy firmwares they claimed was installed). Tesla is effectively paywalling federally required safety recall remedies by requiring the customer to first pay for computer replacement first. Two additional recalls remain open (21V‑389 seat belt fasteners and 24V‑554 hood latch). The problem has been confirmed and documented multiple times by Tesla Service.

Filed Jun 4, 2026 · Driver assistance · CA · crash · 1 injury

I am reporting a safety defect in Tesla’s Full Self-Driving (Supervised) system. On XXX, while using FSD, my 2024 Tesla Model Y (VIN: [XXX]) failed to recognize that the road terminated into the desert after a roundabout on the [XXX] road near [XXX]. The vehicle accelerated straight instead of making the sharp 90-degree left turn, left the roadway, traveled down an embankment, and crashed. Airbags deployed and the vehicle was declared a total loss. Vehicle Data Recorder (VDR) data confirms that Autosteer was active and available during the critical braking sequence. I applied very strong sustained braking (brake master cylinder pressure exceeded 129 BAR with ABS activation). The tow truck driver, [XXX], stated at the scene that this was the fifth Tesla he had recovered from this exact same location due to similar crashes. This documented cluster of at least five identical Tesla crashes at one hazardous spot indicates that Tesla had actual notice of a dangerous defect in its FSD mapping and road geometry recognition but failed to correct it. This incident aligns with the federal safety agency’s ongoing investigations into FSD performance issues (including EA26002). I am also pursuing a private product liability claim for damages. I can provide supporting documents including VDR screenshots, the Wickenburg Fire Department report, and a witness statement. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Apr 14, 2026 · Driver assistance · FL

My Tesla Model Y 2020 (VIN: [XXX] ) is stuck on software version 2023.44.1 for more than 2 years and has four incomplete the federal safety agency safety recalls: • 23V838 – Autosteer driver monitoring improvements • 24V051 – Brake/Park/ABS warning font size too small • 24V153 – Muted Pedestrian Warning System • 24V554 – Hood not detected as unlatched
Tesla Service in the Baltic region and Tesla Service in Warsaw (Poland) both refused to deliver the required OTA safety recall updates. They classified the vehicle as “unsupported” because it is a US-market vehicle located in Latvia.
I am unable to bring the vehicle to any Tesla Service Center.
Tesla is not fulfilling its legal obligation to provide the free safety recall remedies. Please require Tesla to deliver the updates or provide a proper solution.
Attached: screenshots of refusals from Tesla Service (Baltic + Warsaw). INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Nov 2, 2025 · Brakes, Driver assistance · CA

On October 2, my Model Y battery was replaced with a defective cell. Tesla service center replaced the battery. The vehicle could not charge or operate, making it unable to be driven. Today, November 2, while driving my car, my Tesla ABS system and other battery components experienced total failure while driving. For a brief period of time, I was unable to brake completely and my vehicle felt like it was skidding. At the time this occurred, my 1 year old daughter and pregnant wife were in the vehicle. This could have been much worse.

Filed May 14, 2025 · Driver assistance · CA · crash

This incident happened on [XXX], I just got the Tesla data and police report. Here are the events as I remembered: - I was driving my 2023 Tesla Y with FSD supervised (v13.2.8) along [XXX] entered from [XXX] and driving close to north of [XXX] without any issue - Noticed a car in front of me braking hard (about 6secs from the recording dashcam footage) - Realized FSD was not braking hard enough (or at least it did not feel like it) - Slammed on the brake for what felt like an eternity (about 2 secs from the dashcam footage) - Rear end collision on the front car at ~25 mph, airbag deployed. I remembered feeling the brake pedal vibrating but did not stop the car at all. By analyzing the raw data provided by Tesla, it is found brake, accelerator, AEB, ABS and TSC were completely messed up after FSD failed, please refer to the attached analysis report. Note: The dashcam video file and the original Tesla data are available for reviewing if any need as I cannot upload along with this report. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)