News
Five things that are keeping Tesla Full Self-Driving supervised
Tesla Full Self-Driving is really good. I have used it for over 10,000 of my 13,000 miles of driving since FSD v14 launched around this time last year, equating to about 76 percent of my miles using the suite. It’s truly the only way I prefer to travel, but admittedly I save some of the more fun drives for myself.
Even with all of the great things it has done for me, including saving me from being involved in an accident, there are still a handful of things that it needs to improve on. These issues recur from update to update, and while there have been some improvements, they still give me reasons to either soft or hard intervene.
A soft intervention means an adjustment that is needed without disengaging the suite, like manually using a turn signal to change lanes while the car still operates on FSD. What I’d consider to be a “hard intervention” is anything that requires me to disengage the suite altogether, like missing a turn or performing a maneuver I’m uncomfortable with. Of course, some hard interventions will be subjective.
Here are the five things I’d like to see Tesla really focus on through the final versions of v14 and hope to see completely improved with v15.
Speed Limit Recognition and Adjustment
There are entirely too many instances of FSD traveling at a speed that is just totally outrageous. While some of these events can occur on Hurry Mode, I’ve even had issues with it on Standard from time to time, and despite wanting more aggressive maneuvers or a slight bit of urgency, I don’t want to worry about getting a ticket while doing it.
The two areas I notice it the most are in school zones and on local roads. When a Speed Limit changes from 45 to 35, FSD does not always slow down in a way that would appease local law enforcement. On Hurry, 52-55 is pretty standard for a rate of travel in a 45 MPH zone. When it changes to 35, FSD shows zero urgency to slow down to an appropriate speed.
School Zones have been a true pain point, and as recently as last week, I had an issue with it:
Threw FSD into Sloth to see how it handled this school zone. You can see well before I enter it, the car is traveling 34 MPH, one MPH under the limit.
Still not slowing down nearly enough.
@Tesla_AI, not 25, not 30…15 MPH in School Zones https://t.co/YQuQ8ydhKh
— TESLARATI (@Teslarati) September 29, 2026
Realistically, most Speed Limit issues are a soft intervention, as I simply scroll into a slower Speed Profile to get the car to slow down. School Zones are a hard intervention, as they require me to completely take over and travel at the posted 15 MPH limit. Even on Sloth, it simply does not get down to a low enough speed.
Parking
Parking is one thing that has really improved over time, but there are still some pretty considerable hoops Tesla needs to jump through to get it to a point where it can be unsupervised.
Parking preferences seem to be where a lot of these issues will be resolved, as most of my complaints come from the fact that the place FSD chooses to park are usually not where I would personally choose to park. This morning, for example, when I arrived at the gym, FSD chose to park next to a vehicle that was parked with its two tires in the spot that FSD picked.
This is a big reason Parking Preferences with Supervised FSD will be so valuable.
If possible, parking a little further away and being distant from people like this is worth it. https://t.co/3Ac71KQiQ3
— TESLARATI (@Teslarati) June 7, 2026
There were three spots in between that car and the nearest car, so FSD could have chosen the spot that would have given a one-spot buffer between the two vehicles. In a parking lot full of empty spots, don’t be that guy who parks next to a car.
Generally, parking performance is vastly improved from where it was a year ago; I rarely am adjusting how it pulls or backs into a spot on v14.3.10, but in earlier versions, I definitely had my problems. It’s gotten really good since, and this version has been the best in terms of parking performance. It’s more about the places FSD choose to park, and not necessarily the parking itself.
There are also no options or map data to allow you to choose a charger at a place like a grocery store if it offers charging. These are things that are a bit more complex, but they will be needed for unsupervised FSD operation.
Navigation
Navigation was always going to be on this list, simply because it is one of the most inconsistent and mind-boggling things about FSD. Even after a year of intervening, sending voice notes, and overriding decisions, FSD still tries to take me out of my neighborhood the wrong way. You cannot turn left out of my neighborhood’s main entrance and exit, only right. Navigation still prompts a left turn out of my neighborhood’s main entrance and exit, instead of going around the neighborhood and exiting where a left turn is legal.
Tesla rolled out Preferred Routes with the Summer Update, and this has resolved some of the issues. I also found my own personal workaround:
🚨See if this cool Tesla Navigation Hack works for you!
I have used it to get out of my neighborhood legally with FSD, thus enabling completely hands-free drives! https://t.co/DlDsCQjxRI
— TESLARATI (@Teslarati) July 16, 2026
Some of the more mind-boggling things that FSD used to do with Navigation have been remedied, but it is still a frequent complaint for me and many other owners. I’d just like to see it adopt those preferred routes more frequently and maybe learn them a little faster.
Certain Highway Behaviors
Highway travel is the most consistent and perhaps FSD’s best use case. There is nothing better than having FSD handle busy highway traffic or just long, monotonous, and boring drives. I love to use it for my trips to the Flight 93 Memorial where I volunteer. When I drove manually, I chose to get a hotel and stay overnight because it’s about a 2.5 hour drive. FSD lets me make the drive, put in a volunteering shift, and drive home, without much fatigue. I have found that this is where FSD is most valuable for me, personally.
However, there are a few things FSD does on the highway that are just weird.
One thing I’ve had issues with as of late is that there will be times when I’m about a mile from my exit, the car is in the left lane and is traveling faster than the traffic in the cruising late. Instead of completing a pass and then getting over with no traffic ahead, the car will sometimes drastically and suddenly slow down, switch to the slow lane, and get behind a vehicle — all with a mile until the exit. On average, I’ll have around one minute from the time I get to my exit if it’s a mile away, because in most cases, I’m traveling somewhere around 60 MPH on the highway.
There is no reason to not complete that last pass, then get into the right lane, and have an unobstructed path to the exit. This is one of the more strange behaviors I’ve seen it do, and it really does feel like a bug. Here’s an example of it from FSD v14.3.7:
🚨 Tesla FSD v14.3.7 did nearly the exact opposite — nearly 2.5 miles before the exit it got over into the slow lane and got behind much slower traffic.
Now, v14.3.8, anecdotally, waited til the last minute to get off the highway https://t.co/Lc9vAKDyQC
— TESLARATI (@Teslarati) August 29, 2026
I ended up overriding the turn signal and using the accelerator to nudge the car to do what I wanted it to do. There was no reason to get in the left lane and add to the congestion in that lane.
Another thing that FSD does frequently is camps in the left lane, especially on Hurry. Cruising in the passing lane is illegal in Pennsylvania, and I know it is not a crime to do that everywhere. However, it is here, and I really wish the car was a little quicker to get over in the left lane when it’s cruising.
Here’s a pretty drastic example I had just a couple weeks back:
Recognizing Drastic Changes in Road Condition
I think anyone who has ever used FSD knows that potholes are a huge issue, but so are large bumps or sudden changes in road condition. At the intersection of Kreutz Creek Rd. and Rt. 462 in Hellam, PA the roads are nearly set up as a ramp, and going over it at a speed of over 35 MPH can send your head into the glass roof, your butt off your seat, and a brace for the sudden thud that is inevitably coming when you finally touch back down again.
You can see here I tried to change Speed Profiles quickly, but I did it a tad too late:
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
There are other roads in my area that should not be taken at even the posted Speed Limit because of the damage it could do to your car. Here’s another, where I disengaged FSD altogether:
🚨 I’ve talked in the past about my struggles with FSD when large bumps or sudden changes in sloping are approaching.
Today I tried switching down into Sloth from Standard but I did it a tad too late and I had to take over. You can see this isn’t a bump you take at 35 MPH https://t.co/f4tK13hsz1
— TESLARATI (@Teslarati) September 6, 2026
The recognition of these bumps is so crucial for two main reasons: they can cause injury, and they can cause damage to the car. These are reasons why the suite is supervised and drivers should remain attentive. I could not imagine going over that bump at an excessive speed if I had back issues, or if I were older.
Potholes are rarely recognized and usually require a lead car to avoid them. I had FSD use a lead car to avoid a pretty sizeable manhole cover a few weeks back:
🚨 Interesting observation on FSD v14.3.8 – Make note of the van in front of me as it swerves out of the way of a sewer cover
FSD followed this behavior, but interestingly did not swerve for the next sewer cover
What do we make of this? https://t.co/RO19941AIP
— TESLARATI (@Teslarati) September 2, 2026
Tesla says that there are improvements coming for potholes, so hopefully that means these bumps will also be recognized consistently.
SpaceX’s Raptor engine family has steadily increased sea-level thrust while simultaneously reducing mass, turning iterative engineering gains into substantially higher performance for the Super Heavy booster. CEO Elon Musk shed more light on how powerful Raptor 4 will be, and it’s pretty crazy.
Raptor 1 delivered 185 metric tons of thrust at roughly 2,080 kilograms, while Raptor 2 raised that to 230 tons while cutting mass to about 1,630 kilograms. SpaceX data for Raptor 3 lists a target of 280 tons at 1,525 kilograms (with further reductions in associated vehicle hardware), while operational flight ratings have been cited near 250 tons.
This morning, Elon Musk stated that Raptor 4 is expected to reach 300 tons of sea-level thrust at roughly the same mass as Raptor 3. Across these versions, thrust has risen by more than 60 percent from the first engines while engine mass has fallen, producing a sharp improvement in thrust-to-weight ratio. This is a true testament to how great SpaceX engineering has been:
🚀 Elon says Raptor 4 will make 300 tons of thrust at sea level at roughly the same mass as Raptor 3.
How far Raptor has come:
Raptor 1: 185 tf, 2,080 kg
Raptor 2: 230 tf, 1,630 kg
Raptor 3: 250 tf, 1,525 kg
Raptor 4: 300 tf33 on Super Heavy = ~9,900 tf, nearly 3x Saturn V https://t.co/HQDswZhyvL
— TESLARATI (@Teslarati) October 26, 2026
With 33 engines on SuperHeavy, the jump from earlier versions to a 300-ton Raptor 4 would produce roughly 9,900 metric tons of total liftoff thrust, nearly three times the Saturn V’s approximately 3,400 metric tons from its five F-1 engines.
This is not just a larger number on a data sheet, either, as sea-level thrust is the force available the moment the vehicle leaves the pad. This is when it is heaviest and still deep in Earth’s gravity well and dense atmosphere.
Higher levels of sea-level thrust directly improves the initial thrust-to-weight ratio of the full stack. A higher ratio produces faster acceleration off the pad, which shortens the time the rocket has to spend fighting gravity, and gravity losses during the first minute or two of the flight are a major drain on total available delta-v. Every second shaved off of that early climb preserves more propellant energy for reaching orbital velocity or for carrying extra payload.
Because Super Heavy’s engine count is constrained by vehicle diameter and packing density, increasing thrust per engine is the most straightforward way to raise total liftoff performance without redesigning the booster structure or design.
The same-mass target for Raptor 4 is equally important. Holding engine mass roughly constant while raising thrust improves the engine’s own thrust-to-weight ratio and reduces the structural and propellant mass fraction that must be carried solely to support the engines.
Earlier Raptor iterations also simplified or eliminated extensive vehicle-side hardware such as heat shields. These gains compound: more force for less installed mass leaves additional capacity for propellant, payload, or operational margins such as engine-out capability.
For Starship’s architecture, the practical effects are large. Greater liftoff thrust supports heavier vehicles, larger propellant loads, and higher payloads to low Earth orbit, figures SpaceX has targeted in the 100-plus-ton reusable range. That capacity underpins orbital refueling, lunar missions, and eventual Mars cargo and crew flights.
Continued growth in sea-level thrust therefore tightens the gap between theoretical rocket performance and the high flight rates and reusability needed to make large-scale space transport practical.
Tesla has expanded its Tesla Assisted Driving (TAD) suite to its tenth European country, as Latvia joined a growing list of European Union member states authorizing the company’s advanced driver assistance technology.
Tesla Europe announced this morning that the system is now approved in Latvia, with a software rollout to begin soon.
The approval and rollout follow recognition of a provisional European type approval originally granted by the Netherlands’ RDW authority on April 10.
🚨 Latvia has just received approval for Tesla Full Self-Driving (Supervised)
This is the 10th country in the EU to gain approval:
1. Netherlands — 10 April 2026 (original RDW approval)
2. Lithuania — 20 May 2026
3. Estonia — 29 May 2026
4. Denmark — 9 June 2026
5. Belgium — 10 June 2026
6. Slovenia — 7 September 2026
7. Czechia — 21 September 2026
8. Croatia — 29 September 2026
9. Slovakia — 16 October 2026— TESLARATI (@Teslarati) October 26, 2026
Latvia’s Road Traffic Safety Directorate (CSDD) evaluated the Dutch documentation, coordinated with the other national authorities, and reviewed updates from Tesla. These included tightened limits on speed offsets, automatic resets of any manual speed adjustments after each trip, and stronger driver monitoring.
In Europe, the feature is marketed as Tesla Assisted Driving after a recent rule change that labeled the name “Full Self-Driving” as misleading.
The system remains an SAE Level 2 driver assistance tool, not unsupervised autonomy. It can control speed, steering, braking, lane changes, and intersections while following a navigation route. Drivers need not keep their hands on the wheel at all times, yet they must continuously monitor the road and be prepared to intervene immediately.
The sequence of EU recognitions began with the Netherlands in April and continued through Lithuania, Estonia, Denmark, Belgium, Slovenia, Czechia, Croatia, and Slovakia. Most have relied on mutual recognition of the single Dutch provisional approval rather than independent national testing.
These national clearances do not yet constitute bloc-wide authorization. An EU-wide decision requires a qualified majority in the Technical Committee on Motor Vehicles: at least 15 of 27 member states representing 65 percent of the EU population. Larger markets, like Germany, France, and Italy, remain under review, and a vote is expected this December.
However, for Latvian Tesla owners with compatible vehicles and software, the imminent rollout expands access to the supervised system while underscoring that attentive human oversight remains essential.
Tesla expanded its Robotaxi geofence in Houston, Texas, today, enlarging the service area and drawing a new rocket-shaped boundary across the city’s northwestern and central parts.
Although CEO Elon Musk said it was just a coincidence, the expansion seems to be an ode to SpaceX and its potential merger with Tesla.
🚨 Tesla has just expanded its Robotaxi geofence in Houston
It looks a lot like a rocket — we all remember the shape in Austin 🤣 https://t.co/cFOPEuiJ4u
— TESLARATI (@Teslarati) October 26, 2026
The official Tesla Robotaxi account announced the change with the lines “Houston, we have liftoff” and “Bigger service area now live,” pairing them with a map overlay.
The prior white geofence, roughly 25 square miles covering Jersey Village, Harvest Bend, and the Willowbrook corridor along U.S. 290 and State Highway 249, now sits inside a larger blue zone that stretches southeast toward Bellair and closer to central Houston.
Houston’s Robotaxi service launched on April 18, 2026, the same day as Dallas, as Tesla’s first unsupervised public expansion beyond Austin. From the start, the vehicles were Model Ys running without anyone in the front seats, booked through the dedicated Tesla Robotaxi app and open to the public inside the geofence.
Trackers measured the initial zone at about 25 square miles; by late September it had not grown substantially. Community and registry data indicated a modest local fleet of unsupervised Model Ys, while dozens to nearly 200 Cybercabs, the purpose-built, steering-wheel-free two-seaters, have been spotted staging and testing in Houston lots, though public Cybercab rides remain limited to Austin for now.
Across the broader Robotaxi program, Tesla began public Robotaxi rides in Austin in June 2025, as a small geofence and vehicles with safety monitors became available for a ride-hailing service. Later on, Tesla removed the monitors and steadily expanded the service area until it covered most of the Austin metro area.
Unsupervised Robotaxi services now run in six cities: Austin, Dallas, Houston, Miami, Orlando, and Tampa. Cumulative driverless miles reported by the company have reached several million. The Cybercab entered public service in Austin in early September 2026 and has scaled rapidly there. The company has also said that Dallas is next for Cybercab rides in November, with further cities and 24/7 hours targeted by year-end, plus fleet-operator sales of the vehicle.
Waymo also operates a fully driverless service in Houston, which has been open to the public since August of this year.
The Houston expansion continues Tesla’s pattern of starting with tightly controlled validation zones before widening coverage as real-world data accumulates, while the rocket motif on the map underscores the company’s habit of injecting visual flair into its autonomy rollout.
Riders inside the new boundary can request unsupervised Model Y trips in the Robotaxi app; exact operating hours and further Cybercab availability remain subject to app updates and company statements.
How SpaceX Is raising Raptor’s sea-level thrust while holding engine mass steady
Tesla Assisted Driving expands to tenth EU country
