I was using the Tesla FSD in stop and go traffic. At the moment I was moving with traffic at about 30 mph and then traffic started slowing down. The vehicle in front of me came to a complete stop. The FSD on my car started slowing down, but not fast enough. It rear-ended the vehicle at about 18 mph.
2024 Tesla Model Y driver assistance complaints
Page 2 of 7: complaints 11 to 40 of 177, newest first, as owners wrote them.
On August 25, 2025, I was in a crowded Trader Joe's parking lot using the vehicle's FSD parking feature. The vehicle was moving backward into a parking position. A stationary vehicle was in the area. Instead of detecting the other vehicle and stopping, the Tesla kept backing up and made contact with the stationary vehicle. The other vehicle was not moving, and there was enough room for the Tesla to park without contact. I do not remember the exact positioning or direction because of the time that has passed. I did not receive a warning that prevented the contact. I reported to Tesla that the vehicle appeared not to detect the stationary vehicle, but I did not receive an inspection result or written technical finding. I do not have an expert determination of the cause. I am asking the federal safety agency to review this as a possible FSD parking, parking-collision-warning, or automatic-emergency-braking safety defect.
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.
On 7/22/2026 between 6pm and 7pm PST, I was driving my Tesla Model Y on I-405 southbound in Orange County, CA, between the Westminster Blvd exit and Exit 73, with Full Self-Driving (Supervised) engaged. The incident occurred at an express lane ingress/egress transition zone where a physical barrier separates the express and general-purpose lanes. While in FSD mode, the vehicle initiated a lane change on its own. During the lane change, the FSD system misjudged the lane boundary and steered the vehicle into the lane divider/barrier. The vehicle struck the divider on the front right side. The failed system is the FSD/automated steering and lane change function. No forward collision warning sounded and no automatic emergency braking activated before impact with the fixed barrier. There were no warning lamps, alerts, or symptoms prior to the failure; the system initiated and executed the lane change without indicating any problem. The impact damaged the front right body panel, front right bumper area, and the right headlight. My safety and the safety of vehicles in adjacent lanes was put at risk, as the collision occurred at roadway speed during an automated maneuver I did not initiate. Had the divider been a vehicle or a pedestrian work zone, the outcome could have been far more severe. All FSD telemetry, camera footage, and vehicle data from the incident should be available from the manufacturer, and I have requested the vehicle data report from Tesla. The vehicle is available for inspection upon request and is being taken to a Tesla-certified collision center for repair. An insurance claim is being filed with my carrier. The vehicle has not yet been inspected by the manufacturer or police.
This vehicle is hacked along with app. it's unsafe to drive at this point. I have contacted Tesla they are no help. my tesla app is hacked and the vehicle
My car will randomly break while I’m driving straight on a road. It seems to happen when I’m going between 30 and 45 mph. It breaks so hard that if a car behind me was following, they could run into me. Whenever it breaks, I have to put my foot on the accelerator to get the car to go back forward.
Whenever I cancel FSD in this Tesla for any reason, a highly distracting ‘forced feedback’ panel pops up on the single information screen, obstruction critical information. It only disappears when I select one of 4 feedback options, blocking my information screen view all that time. I am a regular driver, not a trained beta tester.
SYSTEMIC POWERTRAIN SAFETY DEFECT: Catastrophic Loss of Propulsion & Failure of Dual-Motor Redundancy. 1. Incident & Safety Risk: While traveling in the far-left HOV lane of a 6-lane interstate highway, the vehicle experienced an uncommanded, unwarranted Automatic Emergency Braking (AEB) intervention during a controlled lane change. This sudden deceleration instantly triggered a complete powertrain collapse and total loss of propulsion. The vehicle came to a dead stop in a live highway lane. The driver (me), passenger, and our [XXX] infant were stranded in lane 3 of a 6 lane highway for ~35 minutes until Highway Patrol units arrived to manually push the vehicle across live traffic to the shoulder. This near-miss was an immediate, severe life-safety crisis not just for the occupants but also to others on the road. 2. Symptoms & Alert Codes: There were zero warning symptoms prior to the incident. Immediately upon the power collapse, the touchscreen displayed critical faults. Active diagnostic telemetry confirmed alert codes: DI_a137 (No Capable Drive Units) DI_a063 (System Graceful Power Off) 3. Manufacturer Confirmation & Inspection Status: The failure was confirmed in writing by the manufacturer’s service center. The diagnostic invoice explicitly states: "The rear drive inverter experienced an unintended reset due to an error. Sudden power reduction and shutdown while driving." The vehicle is currently held at the manufacturer's facility and is fully available for inspection. 4. Engineering Assessment: As a mechanical engineer, my assessment is the surge through the AEB event to the inverter’s DC-link was unable to damp this load, forcing a hardware logic reset. Crucially, the software logic failed to partition this fault. In a dual-motor architecture marketed as having built-in powertrain redundancy, a localized rear inverter reset should be isolated, leaving the front motor operational to safely navigate out of traffic, this did not happen. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (
While driving on the highway with Tesla FSD engaged, the vehicle activated the right turn signal and began steering right as if taking an exit. There was no exit ramp, gore area, or valid right-turn path at that location. I took manual control to prevent the vehicle from leaving the highway/entering the shoulder. I believe this could have caused a crash if I had not intervened. I have dashcam footage of the event.
Whenever the self driving feature is disengaged, a pop up menu is forced into the user asking for a reason for the disengagement. The user is forced to submit a response for the pop up menu to go away. This menu shifts sections of the screen around and can cause distractions due to the user looking for specific information that is typically there but is not due to the pop up menu.
• FSD received a software update earlier this same morning. • While navigating a parking garage under FSD, the vehicle initiated an unprompted reverse maneuver. • The reversal happened with no warning and no meaningful time for driver intervention before impact. • The vehicle struck a structural beam, causing damage to the vehicle above the rear driver side door, as well as shattering and causing splintering of the roof glass.
The Tesla Autosteer (equivalent of adaptive cruise control) failed to brake on seeing the car ahead braking. In the 5 seconds before impact, the car ahead had started braking. The autosteer did not brake for the first 3 seconds and then It asked me to take over 2 seconds before collision. It did not apply automatic emergency braking causing me to rear end the car ahead of me on the freeway at around 30mph This is supposed to be a safety driver assist feature which instead was the primary cause of the accident. The take control was too late to avoid collision. This is a serious safety issue.
Vehicle: 2024 Tesla Model Y Date of Incident: XXX Location: Southbound XXX Express Lanes near the [XXX]/[XXX] exit split in [XXX]. At the time of the incident, Tesla Full Self-Driving (FSD) Supervised was engaged. I was traveling in the Express Lanes and intended to remain in the Express Lanes. I was not attempting to take any exit. As the roadway approached a lane split/gore area, the vehicle began steering toward the striped boom barriers that prevent drivers from going into oncoming traffic, rather than remaining in the travel lane. There were not impending impact alerts or lane deviation alerts. There were no unusual weather conditions, and I did not observe any road conditions that would have made the lane path unclear to a human driver. As soon as I saw the vehicle veering into the boom barriers, I intervened by taking control of the steering wheel. The system disengagement alert/chime occurred only after I took over. Despite my intervention, the vehicle made contact with the boom barrier assembly. The impact caused significant damage to the windshield and driver's side door frame. Glass entered the passenger compartment. My infant child was in the vehicle at the time. Fortunately, no injuries were sustained. Tesla Dashcam footage of the incident was preserved and is available. A claim was opened with Tesla Insurance, and I was advised to submit a vehicle malfunction report for review of vehicle telemetry and FSD operation during the incident. After the collision I maneuvered the vehicle back into its lane, exited the toll highway and parked at a nearby shopping center to assess our injuries the vehicle. While there, another Tesla parked near me, and the driver had experience the same exact situation while his Tesla was in autodrive. I am requesting investigation into whether the vehicle's driver-assistance system improperly tracked toward the boom barriers rather than remaining within the intended travel lane. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(
On XXX, at approximately 8:01:49 AM Eastern Time, my 2024 Tesla Model Y (VIN: [XXX]) was operating under Full Self-Driving (FSD) software version 14.3.3 when the system directed the vehicle into the outer wall of my residential garage without driver input. FSD was actively engaged at the time of the incident. The vehicle sustained significant damage to the front bumper fascia and wheel well trim. Additional damage includes a cracked front fog light/corner lens assembly with surrounding fascia stress, also caused by the same incident. The incident also caused paint transfer damage to the garage wall trim. I have preserved dashcam footage documenting the incident, which is consistent with FSD-directed vehicle behavior. I am referencing the federal safety agency Preliminary Evaluation PE25012 as this incident is consistent with the pattern of uninstructed FSD-directed maneuvers currently under federal investigation. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
On the evening of June 3, 2026, while driving on the I-575 Express Lanes in Cobb County, Georgia, the vehicle’s autopilot/driver assistance system malfunctioned and steered the vehicle into the express lane boom barrier. The boom bar struck the windshield, causing catastrophic windshield failure with glass imploding into the cabin. Glass shards covered the driver’s seat, floor, and dashboard. The driver sustained glass puncture wounds to both forearms and forehead, as well as neck, back, and right arm soft tissue injuries. Component failed: Autopilot/ADAS system. Vehicle is available for inspection. Tesla was notified directly at time of incident. Insurance company has been notified. SR-13 filed with Cobb County. No warning lamps or messages appeared prior to the autopilot malfunction. The root cause of the windshield damage was the autopilot system failure, not driver error or external road debris. Photographic documentation of vehicle damage and driver injuries exists.
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)
I and others have noticed that once UNsubscribed from FSD, lane departure alerts and automatic corrections occur much more often than when subscribed to FSD, even if car is being driven by user. The alerts and corrections happen on almost every drive despite being within normal lane spacing. It feels like this is intentional to push users to subscribe back to FSD. Driving other makes of vehicles does not result in nearly this amount of warnings and corrections. Various online forum post corroborate this behavior. Even if there is an explained reason for it, Tesla does not notify the user of such changes that will happen once unsubscribing from FSD.
I am reporting a software-induced driver distraction defect in Tesla’s Full Self-Driving (Supervised) system, specifically the post-disengagement “Why did you intervene?” dialog introduced in software 2026.2.9.8 and modified in 2026.2.9.9 and 2026.2.9.10, running FSD v14.3.2. Every time the driver disengages FSD via steering, brake, or accelerator input, a modal dialog appears on the center touchscreen asking the driver to categorize the intervention. It presents four options (Navigation, Preference, Discomfort, Critical) plus a voice memo prompt. The dialog cannot be dismissed or deferred. It remains on screen indefinitely until the driver reads the prompt and taps a selection. This creates a serious safety hazard: The dialog appears the moment the driver has resumed manual control, often in response to an unsafe FSD action requiring immediate attention to the road. Forcing the driver to read text and make a multi-choice touchscreen selection during this high-cognitive-load transition directly conflicts with the federal safety agency’s Driver Distraction Guidelines for in-vehicle devices. The dialog occupies a large portion of the center display and obscures the navigation map and surrounding-vehicle visualization, removing situational awareness at the moment it is most needed. Because it cannot be dismissed, drivers are coerced into touchscreen interaction while driving, including in active traffic, intersections, merges, and lane changes. The forced-choice design also incentivizes drivers to tap any option to clear the screen, defeating the stated data-collection purpose and increasing eyes-off-road time. Tesla provides no setting to disable this dialog. I request the federal safety agency investigate this as a driver distraction defect and require Tesla to provide a dismiss option, defer the prompt until Park, or remove the forced-interaction requirement. I am the vehicle owner and experience this on every FSD disengagement.
Hello, I am not writing about a specific incident, but rather wanted to alert the federal safety agency to a potentially dangerous development with Tesla's Full Self-Driving (FSD) technology. In the latest software update being pushed to owners, Tesla now forces drivers to provide feedback if they disengage the FSD system for any reason. This feedback comes in the form of a box on the screen and it cannot be closed. You cannot interact with any part of the vehicle infotainment system until you complete the feedback. I believe that this can cause safety issues, especially in a stressful situation if someone is trying to access the car's map system, for example. Even in normal situations, the driver would be required to read the options and make a selection on the screen - while still driving. I would highly recommend the federal safety agency look into this, as I believe this is a very shortsighted policy that will needlessly endanger drivers, other drivers, pedestrians and everyone on the road. To be clear for form purposes: I am not writing about a specific incident, but I am submitting this information via this form because I do not see a general information form.
The contact owns a 2024 Tesla Model Y. The contact stated that while driving approximately 25 - 35 MPH, while driving near cones on the road, the contact manually turned the vehicle towards the right, and the steering wheel failed to perform as needed. The contact attempted to manually correct the steering wheel but was unable return the steering wheel to center because the steering wheel was independently turning to the left or the right. The contact believed that the vehicle was operating in self-driving mode; however, the vehicle was not equipped with the feature. The contact depressed the brake pedal to decelerate, almost stopping the vehicle, to regain control of the vehicle. The contact was able to drive to the destination. The contact stated that the failure had occurred while driving approximately 60 - 70 MPH, and the vehicle veered to the left and the right while the lane assist was activated. The contact depressed the brake pedal and decelerated almost to a stop to regain control of the vehicle. The manufacturer was informed of the failure, but the contact had not received a follow-up call. The failure mileage was unknown.
Full self driving did not detect pole. I press the fsd of tesla going out of the parking lot and the car turned to the side where the pole is located hitting the side where the camera part right next to driver side. The sensor of the car did not detect completely that there is a pole on side
the federal safety agency COMPLAINT NARRATIVE — Vehicle: 2024 Tesla Model Y Component/System: Full Self-Driving (Supervised) Software, Version 14.2.2.5 On March 14, 2026, at approximately 5:22 PM, a 2024 Tesla Model Y was traveling on U.S. Route 3 in Franconia, New Hampshire, at approximately 45 mph within the posted speed limit. The vehicle was operating with Full Self-Driving (Supervised) software version 14.2.2.5 actively engaged. Three occupants were present in the vehicle, including two minor passengers. All occupants were properly restrained with seat belts. Component/System That Failed: The Full Self-Driving (Supervised) system, version 14.2.2.5, failed to safely detect and respond to a snow-covered road surface. The system lost control of the vehicle upon encountering a snow patch on the roadway, causing the vehicle to strike a tree. The FSD system is the primary failed component. The vehicle has been towed and is available for inspection upon request. How Safety Was Put at Risk: The FSD system was in active control of the vehicle's steering, braking, and acceleration at the time of the failure. The system provided no auditory alert, no visual warning, and no driver takeover request prior to the loss of control event. The failure occurred without any warning whatsoever, leaving insufficient time for the driver to intervene and prevent the collision, despite the driver actively supervising the system in full compliance with Tesla's own supervision requirements. Three occupants were placed in immediate risk of serious injury or death. The vehicle struck a tree and was totaled. Emergency services responded and evaluated all occupants on scene. An official police report was filed. Prior Warning Lamps, Messages, or Symptoms: None. The FSD system issued zero warnings — no auditory alerts, no visual prompts, no haptic feedback, and no takeover requests — at any point prior to or during the loss of control event. The system was operating normally by all displayed indicato
Vehicle: 2023 Tesla Model Y VIN: [XXX] Mileage: Approximately 40,531 miles Software Version: 2025.45.9 FSD (Supervised) Version: v14.2.2.4 While driving on [XXX] near the [XXX] entrance in Mission Viejo, California, the vehicle was operating under Full Self-Driving (Supervised) mode. As the freeway lane ended/merged, the vehicle unexpectedly performed a sudden full stop at freeway speed. There was no visible obstruction in front of the vehicle. Multiple vehicles behind me had to brake abruptly to avoid a rear-end collision. The system did not provide any audible or visual warning before the sudden braking. This has created a serious safety risk due to the high-speed freeway environment. This issue appears to be related to lane-ending or merge interpretation by the FSD system. I am concerned that this behavior could result in a rear-end collision. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
When Adaptive cruise control is on random phantom braking occurs. It can be very severe and drops speeds of 20-30 miles within seconds. Occurs on highways and is random and occurs daily. ( multiple times in a day) Has been serviced 4 times and Tesla cleans the cameras and adjusts them. It has progressively gotten worse and Tesla said don't bring it in because they cannot fix it. They describe it as a software update.
On Saturday morning January 3, 2026 I was driving with my wife, daughter and dog. There was light rain at the time and I had my adaptive cruise set at approximately 72 mph. I was driving our 2024 Tesla Y. At approximately 10:21am the rear of car began to slide right as we entered gradual left curve, possibly because we hit water on road. I tried to slightly correct right and when I did that the steering wheel aggressively corrected back left which put us into a slide. Within a second we hit a tree on the passenger side. The impact was severe and on the passenger side door where my wife was sitting. At that time I theorize that my dog was ejected out of the back window and thrown across the freeway. We then rolled in the other direction (I dont know how many times) down a hill and settled upside down. I immediately smelled smoke and began to try get out of my seatbelt but I couldn’t. I carry a knife and I was able to cut myself out. I then tried to open door and could not so I began punching the glass and eventually got it moving and pushed on it and got it open. I slid myself out, turned around and saw car was on fire. I pulled my daughter out and then began extracting my wife. She was unconscious and had obvious orthopedic injuries. I am 100% confident that had I been driving my other vehicle (non Tesla) that this accident would have NOT occurred. The Tesla and its steering system caused this accident. On top of that, the batteries immediately caught fire, my seatbelt release button did not work, and the electric door button did not work. Had I not been carrying a knife and strong enough to punch door open this story would have ended up differently. The car completely burned. As far as I know, this was the first time this exact issue presented itself. However, when looking online its seems this issue is fairly common with Teslas in wet weather.
Tesla's full self-driving software continues to malfunction. On January 30th at 9:50 a.m. mountain standard Time I was parked at work and discovered my vehicle was left unlocked with a partial window unrolled. This was my first indicator of many faulty problems signaling the vehicle was not operating properly. The vehicle has a proximity sensor via Bluetooth that locks and unlocks the vehicle on the owners approach was not properly working. On January 31st I experience a catastrophic failure with the software of the vehicle as I was locked out of my vehicle after utilizing summons feature that stopped the vehicle in the middle of the intersection obstructing traffic. Police arrived on scene within 30 minutes and we were unable to put the car in any gear to either drive the vehicle or place it in neutral to roll it out of the way. I have detailed video of the incident which is a better accounting of the incident on both occasions, the 30th and 31st of January. This is roughly the third or fourth occasion of Tesla's system producing a catastrophic failure resulting in damage to the vehicle or property damage.
On [XXX], while operating my 2024 Tesla Model Y in Full Self-Driving (Supervised) mode, the vehicle experienced an Uncommanded Steering Input leading to a collision. The vehicle was traveling at a very low speed of approximately 5 mph in a clear, simple environment. Despite this walking pace, the FSD software failed to identify a visible concrete curb and initiated a sudden, sharp turn directly into the obstacle without any prior warning or driver input. The fact that the system executed such a violent and erroneous maneuver at 5 mph indicates a fundamental failure in the Neural Network's object detection and path planning logic. If this logic failure had occurred at higher speeds or near pedestrians, the results could have been catastrophic. The local Tesla Service Center (Watertown, MA) refused to conduct a physical inspection or a log review of the steering torque. They issued a Repair Estimate of $1,217.26 while claiming 'no hardware fault codes' were present, thus ignoring the documented software malfunction. As a leaseholder of this vehicle with only 15,489 miles, I am reporting this as a significant safety defect that the manufacturer refuses to investigate. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
Incident Description (in my own words): We were driving southbound on [XXX] from New Hampshire back to Boston in our Tesla Model Y. Traffic became increasingly congested and slowed to a crawl. My wife was driving, and I was in the front passenger seat working on my laptop. As traffic built up, my wife became momentarily distracted and did not apply the brakes in time. I noticed, in my peripheral vision, the vehicle ahead of us—a truck—suddenly filling the windshield. At that point, I heard the forward collision warning alert, but it activated extremely late, essentially at the moment of impact. The vehicle did not automatically brake or stop, despite the low speed, close proximity, and clear visibility of the truck ahead. We collided with the truck in front of us. Damage was minimal (license plate damage and a small dimple on the front of the vehicle), but the safety concern is significant. Both of our Teslas are configured with forward collision warning set to “Early.” Under normal circumstances, this alert triggers frequently, sometimes conservatively. In this incident, however, the warning activated far later than expected, and there was no automatic braking intervention prior to impact. The front camera appeared clean and unobstructed. I am filing this complaint because this behavior undermines my confidence in the vehicle’s collision avoidance and automatic emergency braking systems. I am also filing a similar complaint for our Tesla Model 3. I am now anxious about whether the software will perform as expected in situations where driver attention lapses briefly—precisely the scenario these safety systems are designed to mitigate. I am requesting that the federal safety agency review this issue, as the system did not behave in a manner consistent with its intended safety function. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
Autopilot was engaged and active at the time of the incident. The vehicle failed to detect a stationary piece of road debris (appearing to be a dropped vehicle part) located in the driving lane. The system did not provide any warning, slow the vehicle, or attempt an avoidance maneuver. The vehicle drove directly over the debris, resulting in damage to the lower exterior/body panel. Road and traffic conditions were normal. This raises concerns about Autopilot’s object detection and hazard response capabilities.
Date & Time: December 25, approximately 6:00 PM Location: Northbound I-880 between the Mowry Avenue and Thornton Avenue exits, Fremont, CA Weather & Road Conditions: Heavy rain at the time of the incident. Road surface was wet with reduced visibility. Vehicle & System State: Tesla Model Y. Driver assistance / self-driving functionality was active at the time of the incident (traffic-aware cruise control / Autopilot functionality). Description of the Incident: While driving northbound on I-880 in heavy rain, the vehicle had been operating normally. Without warning, the vehicle appeared to incorrectly detect that it was drifting out of its lane and attempted to correct this perceived drift. Instead of a minor lane correction, the vehicle abruptly applied heavy braking and initiated a sudden and aggressive left steering maneuver. The car crossed approximately four lanes of traffic in the same direction of travel and continued rotating, ultimately performing an unintended U-turn while remaining on the northbound side of the highway. As a result, the vehicle came to a stop oriented against the direction of travel, facing oncoming northbound traffic. Immediately afterward, the vehicle unexpectedly began reversing at high speed without driver input, creating an additional imminent risk of collision with the outer highway wall (noise barrier separating the highway from adjacent residential areas). During this entire sequence of events, I was unable to regain control of the vehicle despite attempting to intervene. There were no vehicles immediately surrounding us at that moment. Had there been nearby traffic, this incident would likely have resulted in a severe or fatal multi-vehicle collision. Occupants: My wife and two young children were in the vehicle. The children were asleep in the back seat, secured in car seats. Outcome: No physical collision occurred. However, the incident caused extreme fear and distress, and we remain shaken by the event.
VIN decoder
See the problems and recalls for an exact car
Buying a used 2024 Tesla Model Y?
Check the exact car before you pay: accidents, salvage or flood titles, odometer readings and previous owners.
Check its history