Adaptive Cruise Control problems of the 2026 Tesla Model Y - part 1

We have owned a 2026 Model Y Tesla for one week and have encountered these dangerous behaviors while in full self drive mode, even in “sloth” mode: 1. Tailgating, repeatedly, while at highway speeds. Controls did not allow me to increase trailing distance while in fsd. 2. Dangerous merging, cutting off other cars. 3. Failure to read surface directions and driving wrong way against oncoming traffic. And this is with only one week of casual driving!.

Using Tesla fsd 14. 3. 3. It began raining hard, causing standing water to pool on the road. The standing water was making the car lose traction and started sliding within the lane, it did change its speed or driving to account for the rain. Fsd was doing over the speed limit and would not slow down slower than the speed limit. Changing the Tesla speed profile from standard to sloth slowed it down to exactly the speed limit but no lower. At this point the car could not maintain its lane, I feared for our safety, so I had to disengage fsd to regain control of the car. Tesla have removed all methods of allowing the driver to maintain accurate speed control of the car and it often ignores speed limit signs, which means it is traveling too slow or too fast for the currently posted speed limit.

Tesla recently pushed a software update that introduces a major, unavoidable driver distraction right at the most critical moment of driving: the exact second you take manual control back from full self-driving (fsd).   whenever you disengage fsd, a mandatory, multiple-choice survey pops up on the center touchscreen asking why you took over. Unlike previous versions where this would disappear after a few seconds, it now stays on the screen permanently. There is no close button, and it does not time out.   this causes two clear safety hazards while driving: 1 it blocks the screen: the popup actively covers up part of the navigation map and basic screen controls. If you are trying to navigate a tricky intersection or see your route right after taking over, you can't see the map clearly because this giant survey is blocking it. 2 it forces you to look away from the road: because the prompt never goes away on its own, it forces the driver to physically look down, read the small text options, and tap the screen to clear it. Forcing a driver to do a multiple-choice survey while actively managing a manual takeover in traffic is incredibly dangerous. Tesla should not be allowed to use a mandatory, permanent ui popup to collect data while a vehicle is actively moving. It is a severe visual and cognitive distraction at the exact moment a driver needs to be 100% focused on the road. Please investigate this software design and require Tesla to add an automatic timeout or a quick-dismiss button that doesn't require driver interaction.

Adaptive cruise control slams on the brakes at highway speed alleging “curvature assist” on flat, straight roads. Dealer replaced firmware and problem persists. Defect appears to be inherent to adaptive cruise control.

At about 2:16 pm on Monday, 5/18/2026, I was driving southeast in the right lane of amaya drive from fletcher parkway in la mesa, CA, planning to turn right across the trolly tracks onto severin drive. There is an intermittent led sign indicating no right turn in the southeast corner of the intersection, just below and to the right of the ground-level stoplight, that illuminates when the trolley is passing so traffic going straight on amaya can still proceed. In the first street view pdf I uploaded, it is not illuminated. I had fsd engaged, and as I approached the intersection the no right turn led was illuminated. If I recall correctly, I assumed fsd would stop for the no right turn led; but instead, it continued to make the right turn. Luckily my son was in the right seat and yelled several times for me to stop, which I did—just a few feet from the crossing arm, which can been seen elevated in the middle of the second street view pdf I uploaded, and which was just coming down for the approaching trolley. By the time I got stopped, the crossing arm was fully down, and as noted above I ended up just a few feet from it, and would clearly and unequivocally have driven under and through it if I hadn’t braked suddenly. It’s clear that this was completely the fault of fsd either not reading or not being aware of the intermittent no right turn led sign. Since fsd clearly doesn’t read no right turn signs, particularly intermittent led signs, the solution seems to make this intersection no right turn whenever the light is green to pass through the intersection on amaya, although this will hold up the cars who would like to turn right when there’s no trolley approaching.

The latest Tesla autopilot software forces users to engage in an autopilot product survey after disengaging autopilot while driving in order to gain access to audio/radio controls. The survey is not dismissible without reading a complicated prompt and choosing a response, and it completely obstructs audio controls until you participate in the survey. The driver therefore cannot turn off music to listen for emergency sirens, pedestrians, or other potential safety cues while driving at any speed, unless the driver also takes eyes off the road to participate in the forced product survey. This is by design and affects all Tesla drivers who use the autopilot feature.

I have been a user of Tesla's "full self driving" technology for four years. In one of the last major updates, the company removed the ability of the driver to manually set a "cruise control set point" to maintain a safe speed. Instead, they employed a new system with five "drive profiles," which included "sloth," "chill," "standard," "hurry," and "mad max. " the problem is that only two of those stay anywhere near the speed limit. "sloth" will go the speed limit, "chill" is about 2 mph over the speed limit, "standard" is about 7 mph over the speed limit, "hurry" is 12 mph over the speed limit, and "mad max" is probably 15-17 mph over. Sloth and chill will remain in the right lane, rarely passing another vehicle, but all the others will include lane changes. And all of these profiles do not maintain a safe following distance. Users have been complaining about the cars tailgating, sometimes as close as 3 car lengths at 70 mph. However, sometimes conditions necessitate slower speeds. . . Like work zones. I live near denver, and I-70 has a work zone that will be in existence until 2029. The car doesn't recognize the 45 mph speed limit, bouncing back and forth between 45 and 65. Fsd must be disengaged completely to follow the 45 mph speed limit. Which brings up the other problem. In many areas, the speed limits are wrong. In texas, there are areas where the speed limit is 70, and the car thinks it's 55. In new mexico, the speed limit is 70, but the car thinks it's 60. There is no speed profile that will maintain the legal limit. Tesla also has a mechanism that's supposed to allow users to report problems, but some of these I've been reporting for over three years. They refuse to tell us where we can update the information (grok says "here," tom tom, open street maps), and they are not fixing the speeds on the maps.

The standard cruise control is extremely dangerous. The problem is what I hear is called ghosting. When driving using cruise, and there are no other vehicles nor any other objects such as animals or humans. The car will suddenly decelerate almost to the point of a complete if not overridden by manual takeover. I am under the impression that this is intentionally be done by Tesla, so that you will subscribe to their full self driving service. This can and will cause accidents in traffic.

Running full service driving (fsd) v14. 2. 2. 5 on hw4. At skillman st & I-635 dallas TX, fsd attempted a wrong way turn into oncoming traffic instead of taking the correct leftmost lane. In the image attached instead of following the blue path Tesla took the wrong lane highlighted in red.

Driving using autosteer feature at 65mph on expressway, attempted to change lanes which caused the cruise control to suddenly turn off causing the car to begin braking hard with traffic behind it. Tesla’s new Model Y has combined the lane keeping and cruise control so if the lane keeping turns off the car suddenly brakes hard from the regenitive brakes. Lane keeping and cruise control should be two separate controls to prevent this issue.

Subject: Tesla self-driving / autopilot incorrect maneuver at intersection vehicle: Tesla (model: **)?software: full self-driving / autopilot (specify which was active)?date: __[xxx]__?time: _[xxx]___?location: _** carlos, [xxx] ____ (city, intersection or street) description of incident: while the vehicle was operating with Tesla’s driver-assistance system engaged, the navigation indicated the car would turn right at an intersection. As the vehicle approached the intersection and began the maneuver, it unexpectedly continued straight instead of completing the right turn. This caused the vehicle to enter the intersection in front of other vehicles that were stopped at another traffic light. I had to intervene to ensure safety. There was no clear reason for the incorrect maneuver, and the system behavior was unexpected and potentially dangerous. Additional information: •weather conditions: ___good weather _clear__ •traffic conditions: ___lot of traffic people getting off work___ •driver intervention: yes / no (explain briefly)yes heading straight to cars if I had not made a quick maneuver and turn the steering wheel. I would have crash hitting at least one or two cars. •dashcam footage available: yes / no no I am submitting this report so the event can be reviewed for possible software or safety issues with the driver-assistance system. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

I am writing to formally report a serious safety failure involving Tesla’s full self-driving (supervised) feature, which resulted in property damage and a severe safety hazard. While fsd (supervised) was fully engaged, the vehicle failed to detect a large block of wood in the roadway. The vehicle struck the object, causing significant damage to the brand-new car's left-side tire and body, t touched two other cars hence I called 911 and reported it to ensure they remove the wood. Because I did not know how to manually trigger the dashcam save at the exact moment of the crash, video footage was not captured locally. However, the vehicle’s internal sensors, and event data recorder (edr) should have logged the active fsd status and sensor data at the time of impact and potentially save it. Immediately following the incident, I contacted emergency services via 911 to report the roadway hazard. I have since visited a Tesla service center, where staff informed me that I must wait for the formal complaint process to proceed. Due to recent publicly reported fatalities involving fsd, I strongly believe this software is not safe for public roads, and I have chosen not to renew the feature. I am requesting a comprehensive corporate review of my case. I expect Tesla to pull the vehicle's internal logs, take accountability for this hardware and software failure, provide a full repair of the vehicle, costs about $2000 as estimated by their collision center and issue a complete reimbursement for the damages.

On full self driving, there is no way to change the follow distance and it follows way too close very often. This generates incidents that the car reports to Tesla insurance and we are penalized for something we can't always control. We also can't change our speed but I'm more concerned about the follow distance on highways. Last incident at 7:46pm on 1/25/2026.

On January 20, around 9:35 am, phoenix time, I had the car in self-driving mode for a left-hand turn at the intercession of camino real and river road in tucson, arizona. A real-time view shows that it’s a tricky and dangerous left-hand turn. For the past 3 weeks, the car navigated it well, waiting until it was perfectly safe to do so. Today, however, the car moved quickly and unexpectedly into the center of river road, narrowly escaping a head on collision with a west-bound car, and then paused, squeezed in between west and east-bound lanes when I tapped the brake and took the wheel. Everything happened so quickly. I made the left turn into the east-bound lane, but, looking back, I don’t know how an accident didn’t occur, as traffic was still moving in east-bound lanes rapidly. There must have been enough distance between two cars at just the right time, that nothing hit me.

I was driving in full self driving mode on my Tesla Model Y. The car stopped at the left turn stoplight as it does normally. And then while the light was still red and the cross traffic was green (traffic flowing), the Tesla released the brake, accelerating into the intersection. I stomped on the brake and kept the car from fully entering the intersection, then continue home without using full self driving mode any further. If I hadn’t intervened, the Tesla would have caused an accident, injury, or even death.

Vehicle equipped with Tesla full self-driving (supervised v 14. 2) software exhibits unsafe automated following behavior. The system maintains following distances that are too short at steady speeds, including behind stable lead vehicles with no braking or traffic disturbances. Tesla’s own safety score system flags this behavior as “following too closely,” indicating elevated collision risk. However, the driver has no available control to adjust minimum following distance or impose safer headway while using fsd this represents unsafe autonomous tailgating behavior with loss of driver control authority over safe following distance, creating increased risk of rear-end collision and hazardous automated driving conditions. Tesla offers several controls (sloth, chill, standard, hurry, and madmax) modes, none of which solve the issue if the driver in front is driving the speed limit. My car under fsd will crowd (or tailgate) the front car regardless of the mode. In one instance, I was following a car under fsd in sloth mode and it made the car in front of me pull over just to get me off their tail. . . . This is certainly now how I wish to drive, and don't want my car driving this way. Failure mode: automated headway policy dominance, lack of driver override, unsafe autonomous following distance.

Vehicle equipped with Tesla full self-driving (supervised v 14. 2) software exhibits unsafe automated behavior due to removal of driver speed control. The system infers speed limits and driving speed without allowing the driver to set a safe maximum speed. In residential neighborhoods with children, pedestrians, and shared social spaces, the vehicle drives at model-inferred speeds that are socially and physically unsafe. Driver is unable to impose a lower safe speed limit without disengaging. Tesla removed previous option for driver to adjust speed. In a state park campground, the system failed to detect a posted 15 mph speed limit and inferred a 55 mph limit. The vehicle accelerated to unsafe speeds on narrow, pedestrian-heavy roads, with no driver ability to cap speed while under fsd. This represents a loss of human override authority and unsafe autonomous system behavior, creating pedestrian hazard and safety risk. Failure mode: automated speed inference dominance, map prior misclassification, lack of driver override, unsafe autonomous acceleration in pedestrian environments.

There is a serious safety-related fsd (full self driving) fundamental design flaw with stop sign behavior. On previous versions and on the latest and best version of fsd (currently that is v14. 2. 1. 25) when fsd approaches a stop sign and there is no white painted stopping line, fsd will make its full initial stop (also called the zero-speed stop) directly at or behind the stop sign instead of making the initial full stop beyond the stop sign at a location where the driver can see cross traffic. Sometimes the fsd initial full stop is 20, 30, 40, even 50+ feet back away from the edge of the road. At these distances from the edge of the road, most of the time, there is no visual of cross traffic left and right. The fsd stop then turns into the fsd "creep" where fsd, after stopping 30 feet back will then commit to the turn from 30 feet back giving drivers little to no time to see cross traffic. If I am the supervisor of fsd who is liable for my safety and my vehicle's safety, I need to be able to see cross traffic before my car (with fsd engaged) decides to commit to the turn, but fsd does not care if the driver can see. The "creep" is perhaps the least human-like manuever that fsd performs. From the stopped location directly at the stop sign, they creep may inch up and stop again, it may inch up a couple times and stop again, it may pull up to the edge of the road and stop again, or it may just pull out into oncoming traffic in one swift motion. Bc of this behavior, fsd has almost got rear ended countless times at stop signs. Also, cross traffic see's the creep and thinks I'm about to pull out in front of them drivers go beyond the stop sign to a location where they can see to make their one and only full stop. To avoid this issue, fsd needs to do this too (I. E. Make initial full stop at the edge of the road) this is legal in mostly every state (I live in PA) Tesla has not provided a single response to these reports and nothing seems to be getting done about it.

When in self driving mode, which activates the adaptive cruise control, it is not possible to set the following distance. The following distance automatically selected by Tesla self driving is much too close to the vehicle in front of me. Tesla has removed the ability to set the following distance. It follows at approximately 2 seconds behind the car in front of me, regardless of my vehicle speed . . . . At 80 mph 2 seconds is not enough time for a driver to react. Following distance should be controllable by the driver. Taking away this ability deprives a driver of driving within their own limitations.

On several occasions, my Tesla Model Y has braked for no reason while using traffic aware cruise control as well as when using autopilot. I can re-create this situation on the same parts of the highway. The sudden, uncommanded stopping creates a hazardous situation with the cars being me as I may get rear ended. At this point, I do not feel safe using autopilot or tacc. I submitted a ticket to Tesla but they declined to work on it.

Incident date 11/27/25 incident location: CA state highway 101between san luis obispo and los angeles. Driving conditions: daylight/dry roadway. Description of safety defect / complaint: during a single approximately 400-mile highway road trip, while using Tesla’s traffic-aware cruise control (tacc) feature enabled, the vehicle abruptly and forcefully applied the brakes on at least six (6) separate occasions without any apparent cause. On each occurrence: • no vehicle ahead was braking or decelerating, • no vehicle was merging or cutting in front of my vehicle, • no stationary or moving obstacles (including overpasses, road signs, or debris) were present in or near the travel lane, • the forward roadway was clear and unobstructed for a considerable distance. These sudden, un-commanded braking events were severe enough to cause significant deceleration, requiring me to immediately intervene by pressing the accelerator pedal to override the system. Due to the frequency and unpredictability of these phantom braking events, I no longer feel safe using traffic-aware cruise control or any Tesla advanced driver-assistance features that rely on the same sensor suite and software. I am filing this report because repeated uncommanded braking in highway traffic constitutes a serious safety hazard that could lead to rear-end collisions, particularly when closely followed by other vehicles or commercial trucks. Additional information (if applicable): • software version at time of incident: v12 (2025. 38. 9 fe 714a33a545) • full self-driving capability package: no. Enhanced autopilot: no. • any dashcam or sentry mode footage available: no I request that NHTSA investigate this recurring phantom braking issue in Tesla vehicles equipped with traffic-aware cruise control and autopilot systems.

My car installed update v12 (2025. 38. 8. 7) last night. This morning I was driving to work using autopilot when alarms sounded, the hazard lights turned on, and the screen flashed a warning that I had to take over immediately. The message included a note that autopilot had failed due to a "systems error. " the navigation and visualization screen froze, went blank, and took 10 minutes to come back on. I asked Tesla to roll back the update and they have told me that they cannot do that. I came very close to crashing into a concrete guard rail as the car was going around a turn when the system failed.

Very scary! heading west on [xxx] , my 2026 Tesla Model Y ran 2 red lights! it stopped at the first red light that sits back about 100 feet from [xxx] , and then just sped ahead, went through that light and the one directly on [xxx] and made a right turn. Crazy! information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

The latest version of Tesla fsd software does not let me fully control my speed. You can switch profiles or stop using full self-driving, but you cannot set the speed to what you want. In the last version, you could use the right scroll wheel to increase or decrease the speed. Now that shifts profiles but even that does not give you control over what exact speed you are driving.

While driving in rain at night, the vehicle’s automated driving system attempted to make a turn at an intersection near active train tracks. Instead of remaining on the roadway, the system steered the vehicle directly onto the train tracks, where the vehicle became stuck between the tracks and the paved road surface. All four tires were damaged, and the vehicle could not return to the travel lane under its own control. If a train had been approaching, this situation could have resulted in a severe or fatal collision. I had to manually reverse the vehicle a significant distance to return to the roadway. The malfunction appeared to result from the automated driving system misidentifying the roadway under rain and low-visibility conditions. This suggests a recurring risk for any vehicle using the system at this location in similar conditions. The safety issue has not yet been inspected or confirmed by the manufacturer. No warning lights or alerts were displayed prior to the incident. The affected components and system are available for inspection upon request. I also have dash-cam video of the incident documenting the event.

Fsd was unable to avoid object in road, may be due to how the adaptive headlights work as I was unable to see the object as well fsd/adaptive headlights may may it hard or impossible to see objects on road at night no in the process of a insurance claim no.

Tesla fsd v14. 1. 3 feels unsafe for the typical “average” driver because it no longer allows users to set a maximum speed limit offset when using the standard driving profile. In fsd v13, drivers could specify a max speed offset—such as 10% or 15% above the posted limit—when fsd was enabled. However, this option is no longer available in fsd v14. As a result, fsd v14 in the standard profile often speeds on highways and makes aggressive lane changes to pass slower vehicles. This behavior feels unsafe and stressful for most everyday drivers. Tesla should restore the ability for each driver to set their own comfortable max speed limit and reduce the aggressiveness of lane changes.

Tesla fsd issues: 1. Phantom braking sudden to a full stop for no known reason in the middle of the road, throwing my dogs into the floor and the car stopped completely on the highway. If an infant had been in the car ina car seat, their neck could have been broken 2. Sudden jerkiness when making turns 3. In one case the car suddenly changed lanes and was a close encounter. 4. Fsd system is now completely non-functioning. 5. These issues started about about 1 month ago and worsened in the past 1 week after the latest software update. Tesla premium connectivity navigation issue 1. Instead of taking me on main roads to my destination, it has been taking me down rural, isolated dirt roads. In one case I was directed to a dirt, logging road, isolated and dangerous terrain. I had to turn around in a secluded area and the navigation system kept directing me to dirt roads, although main roads were close by once I opened my iphone for directions. 2. In lynchburg, va the navigation directed me towards an exceptionally steep downgrade to the river and would have been a catastrophe 3. These issues started this weekend 10/24 - 10/26/25 door locks 1. Door locks respond occasionally and there have been times I left the car assuming it would lock but it had not. There is no rhyme or reason to this. 2. This issue started 10/25/25 I am following up with Tesla next but thought you should be made aware. I did the recent Tesla software update and things just got worst.

Upon purchase of the vehicle, unlike previous models and versions of the software - the vehicle’s speed limit control was incapable of being set - instead, using fsd, you had to select from percentage based offsets - which were frequently ignored and would still go much higher or much lower than the percentage value set. The owner of the vehicle was unable to say limit to only 10 over the speed limit; instead it was percent based and not reliable. In addition, more than a third of the time - the speed limits in the infotainment system did not match the posted speed limits. Sometimes, in the middle of a highway - it would randomly go from 55 to 25, posing a significant threat hazard when using the fsd or cruise control system (which is something Tesla charges extra for access to) causing the vehicle to immediately decrease speed when other vehicles behind are getting up to speed and not expecting a vehicle to randomly slow down excessively. Additionally, when you manually override the speed limit control, or the system does, the user interface hides this limit so the driver is unaware of what limit of speed it is set to. These issues were already bad enough, but just yesterday my vehicle was pushed a software update that dramatically reduced the performance of fsd, and now I am unable to manually control the speed limit at all in fsd. This was a regression from purchase, when a scroll wheel at least allowed me to manually set the speed limit or correct it when it was wrong. Now, that feature has been removed and instead there’s a duplication of fsd profiles (left/right on the right scroll wheel does the same as scrolling up/down). And continuing this trend, the driver is incapable of seeing what the speed limit is set to because it’s hidden from the user interface. In addition, the driving behavior for fsd has significantly regressed from before the update. Cruise control’s most basic functionality should be to set a speed limit. Now this feature has been removed.

On the day of the incident, I drove my vehicle into the charging station and activated the Tesla fsd autonomous driving and automatic parking functions. During the automatic parking attempt by the vehicle, the system exhibited the following severe loss of control behaviors: 1. The vehicle automatically collided with the vehicle in front without any human operation. 2. It paused for about 1 second after the collision. 3. Then, the vehicle suddenly accelerated in reverse at high speed, again without any driver operation. 4. It directly hit another Tesla that was charging behind my vehicle. The entire process is fully executed automatically by the vehicle system. I cannot intervene or stop the system through the steering wheel or brakes. Ii. Severe security risks when the accident happened, my friend was sitting in the passenger seat. If the vehicle had moved a few more inches, it could have caused serious injury or even a life-threatening situation. This system failure is a combination of sudden unintended acceleration (sua) and the loss of control in autonomous driving decision-making, posing a significant systemic risk to public traffic safety. I immediately contacted Tesla and sent a complaint letter to the north carolina consumer center. They accepted my complaint and sent an email to Tesla, but it has been over twenty days and I have not received a response from Tesla.

Reporting fsd incident on 10/08/25 approx around 8. 15 pm I was going on I-90 towards western mass / u mass amherst using fsd on 10/08/25 on I-90 road work was ongoing and it was 2 lanes. All the vehicles started going in the right lane as left lane had cones . Left lanes cones were tapering on its way ahead. My Tesla fsd chose the left lane which I would not choose as I saw at the distance cones were tapering to form a single lane . Tesla fsd drove in left lane and as it noticed cones tapering into single lane fsd acutely cut into the right lane in front of the of the truck at a very very narrow margin . Once the right lane , fsd asked me to take control of the car. From there till u mass amherst I could not use fsd . This was scary experience. I wanted to report using voice command but I got busy . Please you must have recording of the event. No body was hurt no vehicle damage just wanted to make aware about fsd.

I would like to formally report several incidents I have experienced with my newly purchased Tesla Model Y. I acquired the vehicle on [xxx], collected it from washington d. C. , and drove it back to houston between September 20 and 21. Prior to my return journey, I conducted a test drive. During this drive, at dusk, I engaged full self-driving (fsd) mode. The vehicle stopped appropriately at a traffic light; however, once the light turned green, it moved forward but veered into the yellow safety buffer zone located between the lanes of opposing traffic. I intervened by manually steering the car back into the correct lane. A similar occurrence happened in washington d. C. While attempting a left turn under a highway overpass—the vehicle again crossed into the yellow lines. These incidents suggest that the fsd system did not reliably detect the yellow lane markers. On the weekend of [xxx], during my drive to houston, I primarily used fsd. While navigating a road construction zone, the system failed to recognize large safety cones (yellow columns) and nearly collided with them. Fortunately, I was attentive and promptly took control, braked, and changed lanes to avoid an accident. This demonstrated the fsd’s inability to identify these safety markers. On Tuesday, [xxx], I drove the vehicle to work and returned home using fsd. As I exited the highway onto a ramp merging with frontage lanes, I observed that fsd did not reduce speed appropriately and nearly made contact with vehicles on the frontage road. This indicates that the system was unable to interpret the ramp as a short section intended for deceleration and safe merging. On [xxx], while returning home in the evening after work, I used fsd due to light traffic. The vehicle navigated turns and stops satisfactorily and paused roadside before my house. When I resumed manual control to park, the vehicle suddenly became unresponsive, accelerated onto my front yard, struck the flower bed stones, information redacted pursuant to the freedom of information act (foia), 5.

Bought a brand new Model Y and I less than a week I received the below two error message warnings and the airbag light comes on. Cabin occupancy radar obstructed. Front passenger safety restraint system issue. Also to engage the fsd, I have to double tab 2-3 times in order for it to engage.

This happened after I installed the most recent software version. My wife was driving with fsd enabled when the car suddenly braked hard. A little while later, as it was supposed to make a left turn, it suddenly accelerated on its own, ignored a red light, and drove straight through the intersection. A warning light appeared on the screen, notifying her that fsd was inoperable, but it was already accelerating, so it was too late to intervene. Therefore, the car crashed with another car. My wife, mom, and my baby were in the car, and my wife got injury on her face. I have a recorded video, and Tesla should have the log for that moment.

The curvature assist function activates and applies the brakes automatically on straight and level sections of freeways with no observable obstacles or curves, requiring driver to resume acceleration to override the brakes.