Table 1 shows one common vehicle speed control related problems of the 2024 Tesla Model 3.
| Problem Category | Number of Problems |
|---|---|
| Vehicle Speed Control problems |
Component/system that failed: Tesla full self-driving (supervised) software version 14. X (2025. 38. X and later). The issue is software-only and remains installed on any vehicle updated to v14. Description of safety defect: fsd v14 deliberately removes the driver’s ability to set or adjust maximum speed offset using the right scroll wheel (feature present in all prior versions including my current v13. 2. 9). As a result, the system routinely exceeds posted speed limits by 5–20 mph with no way for the supervised driver to correct it short of fully disengaging fsd. The vehicle ignores speed-limit signs, relies on inaccurate map data, and follows surrounding traffic speed instead of the legal limit, even in school zones, construction zones, residential areas, and adverse weather. This significantly increases risk of collision, injury, and traffic citations. Reproduced/confirmed: widely reproduced by thousands of owners on Tesla forums, reddit, and x immediately after v14 rollout in late 2025. I have chosen to remain on v13. 2. 9 to avoid this exact defect. Inspected by manufacturer or others: no in-person inspection required; Tesla has full remote log access. Multiple owners have submitted in-car bug reports. Warning lamps/messages: none. The speed-offset control is simply grayed out and non-functional by design in v14. Vehicle available for inspection upon request.
Full self drive 14. 1 removes the max speed setting that allows drivers to control the speed of the vehicle while under computer control, leaving no way to prevent the car from speeding when the speed profiles choose to drive over 28+ mph over the speed limit. The lack of ability to control the speed of the system is fundamentally unsafe by design.
I am filing an urgent complaint regarding multiple incidents involving my 2024 Tesla Model 3 (VIN: [xxx] ) that caused major safety risks, personal property loss, and serious disruption to my life. [xxx] – while in a left-turn lane with autopilot engaged, the car attempted to go straight. When I took over, the system malfunctioned severely. (photo evidence available) [xxx] – remote support failed; car towed to Tesla upland service center. June 27, 2025 – issued loaner vehicle. July 1, 2025 – Tesla claimed I must pay for repairs. I requested a written evaluation report, but to date it has not been provided. July 20, 2025 – without consent, Tesla remotely locked my vehicle with my personal belongings inside, violating my property rights. Aug 1, 2025 – Tesla promised review and report but refused to unlock my car. Aug 12, 2025 – after 10+ days, still no report. Upland “options” included threats that my locked car in my garage could be deemed stolen, causing severe mental distress. Demands: 1. Full investigation into autopilot failure and handling delays. 2. Immediate delivery of written evaluation report. 3. Accountability for delays, threats, and property rights violations. 4. Compensation for all losses and disruptions caused. Contact: [xxx] I request a written response within 24 hours. Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).
I was in a drive thru of a fast food restaurant and the car rapidly accelerated on its own and crashed into a wall. The air bags deployed and we were injured. We also narrowly missed hitting a pedestrian. The car hasn’t been inspected by anyone yet, however it is available if someone wants to inspect it.
This is the 3rd or 4th time I have observed sudden unexpected acceleration when at a full stop at a light while using fsd supervised (v13. 2. 7 just updated). It first happened 2 or 3 times on fsd v13. 2. 6 when mine was the lead car at stop lights. This time I was at a stop light but obviously not the lead car. The truck in front of me was blocking view of the traffic lights. Each time, I have hit the brakes immediately, so I don't know if the vehicle would stop on its own during these situations, but I have no issues with it safely braking at any other time. Other than this intermittent glitch, fsd has been flawless on the hw4 next generation computer, which may lead to driver complacency not expecting this. I am reporting for awareness & hopefully correction. I have mp4 video files of the incident, but I cannot upload them here.
The car consistently has phantom braking. The speed will drop around 15 miles of speed immediately. It also will slow on rolling hills and random long turns on cruise control. Most recent date listed.
Traveling with cruise control with the flow of traffic at 75mph and the setting dropped to 60mph. I thought fsd/beta programming was not allowed as regular vehicle settings so why does this continue?.
I reduced my set standard cruise control speed when traveling on a road curve and the speed drastically reduced by over 15mph lower than my setting on it's own. If I was traveling in a group then this would have created a dangerous situation for the following vehicles. This is another fsd/beta programming in regular cruise control. Why are you still allowing this to exist???.
Traveling with cruise control at 80mph with the flow of traffic and the speed setting dropped to 60mph. Why do you still allow this?.
Cruising at 75 and speed dropped to 55. There are at least 3 fsd/beta features in the driver set cruise control, did Tesla get approval to add those features to the cruise control?.
Cruising at 75 the speed suddenly drops to 55, the worst I had was changed from 75 to 40. This is dangerous and needs to be changed. It drops speeds every day and before I can correct it the car usually drops a minimum of 5mph. If allowed I will start to report this every day until it is corrected as it is a huge safety issue for other drivers and potentially a deadly crash or road rage incident.
See attached document for complaint.
Using cruise control to go with the flow of traffic the vehicle will slow down for any random flashing lights far away or vehicle in next lane causing all vehicles to slow down unnecessarily. Fsd and beta programming does not belong in driver set cruise control.
While using traffic aware cruise control the vehicle would rapidly decelerate with no warnings of potential collision and with no actual emergency situation existing on the road. In a single trip that spanned both day and night there were three rapid declaration events occurring both when light or dark outside. Vehicle display wouldn't show any messages as to the reason for declaration.
Driver set cruise control has fsd imbedded that causes the vehicle to slow down drastically on its own. The car has brake tested several following vehicles so far. I’ve seen this before many times of other Teslas but thought it was the driver and now I know it was not. This causes a chain reaction of braking and smoking tires. I am positive this has created accidents but the ones involved have no idea how it started many vehicles ahead. The lane keep assist pillar cameras do not work in the dark, this has taken me by surprise already. The phantom braking on highways is awful, it is so bad that I am afraid to drive in the winter. The torque of the wheel sensor is not safe, when auto steer disables it can take you by surprise causing you to swerve into on coming traffic. The car accused me of using a cheat device one time so I decided to try it and surprisingly I found that it is actually much safer than using my body weight. These are extremely unsafe for busy traffic and slippery roads. I have videos showing it and will get more.
See attached document for complaint.
There is a a very dangerous software issue with new Tesla models where there is a 1-2 second lag between when cruise control is disengaged and when it actually disengages. Especially, at high speeds this is dangerous because the car can continue maintaining acceleration for several hundred feet against driver controls. I’ve had to slam on the breaks several times because of this. This is not a glitch, and this is not unique to my Tesla. It’s a known issue reported by the community that needs Tesla’s attention.
I have my phone mounted to the back of the computer screen, and I also have the phone power cord running from the center console 12v plug up to my phone. I have found that if the power cord comes in contact with the computer screen, it can inadvertently put the car in neutral (it acts like a finger touch). This could be extremely dangerous if, for example, the car is making a left turn in front of oncoming traffic and the car unexpectedly goes into neutral. I think consumers should be aware that a phone power cord can cause changes on the computer screen if there is contact, especially if it switches the car to neutral.