News
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.
Tesla Full Self-Driving v14.2.2.5 hit my car back on Valentine’s Day, February 14, and since I’ve had it, it has become, in my opinion, the most confusing release I’ve ever had.
With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.
It has been about three weeks of driving on v14.2.2.5; I’ve used it for nearly every mile traveled since it hit my car. I’ve taken short trips of 10 minutes or less, I’ve taken medium trips of an hour or less, and I’ve taken longer trips that are over 100 miles per leg and are over two hours of driving time one way.
These are my thoughts on it thus far:
Speed Profiles Are a Mixed Bag
Speed Profiles are something Tesla seems to tinker with quite frequently, and each version tends to show a drastic difference in how each one behaves compared to the previous version.
I do a vast majority of my FSD travel using Standard and Hurry modes, although in bad weather, I will scale it back to Chill, and when it’s a congested city on a weekend or during rush hour, I’ll throw it into Mad Max so it takes what it needs.
Early on, Speed Profiles really felt great. This is one of those really subjective parts of the FSD where someone might think one mode travels too quickly, whereas another person might see the identical performance as too slow or just right.
To me, I would like to see more consistency from release to release on them, but overall, things are pretty good. There are no real complaints on my end, as I had with previous releases.
In a past release, Mad Max traveled under the speed limit quite frequently, and I only had that experience because Hurry was acting the same way. I’ve had no instances of that with v14.2.2.5.
Strange Turn Signal Behavior
This is the first Full Self-Driving version where I’ve had so many weird things happen with the turn signals.
Two things come to mind: Using a turn signal on a sharp turn, and ignoring the navigation while putting the wrong turn signal on. I’ve encountered both things on v14.2.2.5.
On my way to the Supercharger, I take a road that has one semi-sharp right-hand turn with a driveway entrance right at the beginning of the turn.
Only recently, with the introduction of v14.2.2.5, have I had FSD put on the right turn signal when going around this turn. It’s obviously a minor issue, but it still happens, and it’s not standard practice:
How can we get Full Self-Driving to stop these turn signals?
There’s no need to use one here; the straight path is a driveway, not a public road. The right turn signal here is unnecessary pic.twitter.com/7uLDHnqCfv
— TESLARATI (@Teslarati) February 28, 2026
When sharing this on X, I had Tesla fans (the ones who refuse to acknowledge that the company can make mistakes) tell me that it’s a “valid” behavior that would be taught to anyone who has been “professionally trained” to drive.
Apparently, if you complain about this turn signal, you are also claiming you know more than Tesla engineers…okay.
Nobody in their right mind has ever gone around a sharp turn when driving their car and put on a signal when continuing on the same road. You would put a left turn signal on to indicate you were turning into that driveway if that’s what your intention was.
Like I said, it’s a totally minor issue. However, it’s not really needed, and nor is it normal. If I were in the car with someone who was taking a simple turn on a road they were traveling, and they signaled because the turn was sharp, I’d be scratching my head.
I’ve also had three separate instances of the car completely ignoring the navigation and putting on a signal that is opposite to what the routing says. Really quite strange.
Parking Performance is Still Underwhelming
Parking has been a complaint of mine with FSD for a long time, so much so that it is pretty rare that I allow the vehicle to park itself. More often than not, it is because I want to pick a spot that is relatively isolated.
However, in the times I allow it to pull into a spot, it still does some pretty head-scratching things.
Recently, it tried to back into a spot that was ~60% covered in plowed snow. The snow was piled about six feet high in a Target parking lot.
A few days later, it tried backing into a spot where someone failed the universal litmus test of returning their shopping cart. Both choices were baffling and required me to manually move the car to a different portion of the lot.
I used Autopark on both occasions, and it did a great job of getting into the spot. I notice that the parking performance when I manually choose the spot is much better than when the car does the entire parking process, meaning choosing the spot and parking in it.
It’s Doing Things (For Me) It’s Never Done Before
Two things that FSD has never done before, at least for me, are slow down in School Zones and avoid deer. The first is something I usually take over manually, and the second I surprisingly have not had to deal with yet.
I had my Tesla slow down at a school zone yesterday for the first time, traveling at 20 MPH and not 15 MPH as the sign suggested, but at the speed of other cars in the School Zone. This was impressive and the first time I experienced it.
I would like to see this more consistently, and I think School Zones should be one of those areas where, no matter what, FSD will only travel the speed limit.
Last night, FSD v14.2.2.5 recognized a deer in a roadside field and slowed down for it:
🚨 Cruising home on a rainy, foggy evening and my Tesla on Full Self-Driving begins to slow down suddenly
FSD just wanted Mr. Deer to make it home to his deer family ❤️ pic.twitter.com/cAeqVDgXo5
— TESLARATI (@Teslarati) March 4, 2026
Navigation Still SUCKS
Navigation will be a complaint until Tesla proves it can fix it. For now, it’s just terrible.
It still has not figured out how to leave my neighborhood. I give it the opportunity to prove me wrong each time I leave my house, and it just can’t do it.
It always tries to go out of the primary entrance/exit of the neighborhood when the route needs to take me left, even though that exit is a right turn only. I always leave a voice prompt for Tesla about it.
It still picks incredibly baffling routes for simple navigation. It’s the one thing I still really want Tesla to fix.
A Texas man has been arrested and charged with manslaughter after his Tesla crashed into a home last month, striking a woman inside and killing her. The driver, Michael Butler, claimed the vehicle was in self-driving mode, but information from Tesla shows that Butler overrode the system.
Butler was arrested on Wednesday and booked at the Harris County, Texas, jail. He remained in custody through Thursday and Friday; he did not enter a plea, and his next court hearing is scheduled for Monday.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
There are a handful of new clues in the case that could clear Tesla of any wrongdoing, especially as the woman who was killed’s family, the Avilas, filed a wrongful death lawsuit against Tesla and Butler, seeking at least $1 million in damages.
Charging documents from the Harris County prosecutor now show that Butler, who was working DoorDash the evening of the accident, had been using Full Self-Driving mode without incident through the duration of multiple deliveries that evening.
In the moments leading up to the crash, while in FSD and approaching a left turn, Butler pressed the accelerator pedal, overriding FSD’s speed control, and continued to push it until it reached 100 percent. This caused rapid acceleration; the brake pedal was never pressed, and there is no data to show that Butler aimed to turn away from the curb or house.
The charging documents state:
“I noted that the brake pedal was never pressed in the final minute before the crash. I also did not see any data to indicate that the driver attempted to turn away from the curb that he eventually struck. Further, I observed that no mechanical error was detected or recorded by the vehicle before BUTLER and the Tesla struck the curb.”
Additionally, a forensic analysis of Butler’s phone showed that he searched Google around the time of the crash with queries questioning why FSD was “too timid,” “not aggressive enough,” and even searched, “FSD is not aggressive enough for city driving.”
The documents outlined this:
“Investigator Veal also informed me that he had received BUTLER’s cell phone from Deputy Amad and that HDAO digital forensics team had completed a data extraction and download of the phone. Multiple Google searches related to Tesla had been made from BUTLER’s phone in the months leading up the crash. I noted multiple searches in May of 2026 indicating an apparent frustration with Tesla’s FSD mode, including the following searches: “Tesla fsd not aggressive enough 2026 model,” “Tesla fsd not [sic) aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “tesla fsd too timid.”‘
Tesla had claimed just after the crash that its internal data showed Butler had overridden the system’s speed control and pressed the accelerator completely, causing the vehicle to travel at an excessive rate of speed. Eventually, the car slammed into Avila’s house, killing her.
Butler has now been formally charged with Manslaughter, a felony.
Tesla shocked with its quarterly delivery report yesterday by reporting it delivered 480,126 vehicles in the second quarter of 2026, a 25 percent year-over-year jump that crushed Wall Street estimates of roughly 400,000–408,000 units. Production reached 451,758, with Model 3 and Model Y accounting for the vast majority.
The result ended two years of annual delivery declines and drew down inventory, signaling demand that outpaced earlier production.
Tesla bears had long warned that the expiration of the U.S. federal EV tax credit would hammer demand. Without the $7,500 incentive, they argued, American buyers would balk at higher effective prices, leading to a sharp slowdown.
Will Tesla thrive without the EV tax credit? Five reasons why they might
That narrative has not played out as predicted. While U.S. EV sales faced broader headwinds, Tesla’s global numbers held firm, underscoring the company’s ability to offset domestic pressure through other levers.
There are several plausible factors that explain Tesla’s strength during this quarter. Let’s take a look at them:
Rising Gas Prices
Rising gas prices provided a powerful tailwind, especially in the U.S.
Geopolitical tensions tied to the Iran conflict pushed fuel costs higher earlier in the year, amplifying the lifetime savings of electric vehicles. Even as oil prices later moderated, the psychological and financial impact lingered, encouraging fleet operators and private buyers to accelerate EV purchases. European sales rebounded sharply, helping drive the quarter’s outperformance.
Full Self-Driving Adoption
Advances in Full Self-Driving (FSD) supervised software also appear to have boosted appeal. Tesla expanded FSD availability in select European markets and continued refining the system.
No complaints from me because I finally got to enjoy this drive on FSD; I usually like to manually drive down this mountain https://t.co/RBFniRPSR0 pic.twitter.com/XQ5sOpN1Yg
— TESLARATI (@Teslarati) June 26, 2026
For tech-oriented buyers, the promise of future autonomy and enhanced driver-assistance features adds perceived value beyond the car itself. This differentiation helps Tesla stand out in a crowded market where competitors focus primarily on hardware and basic range.
Pricing Strategy, Affordable Configurations
Tesla’s offerings and its pricing strategy during Q2 further stimulated demand. Tesla introduced lower-cost versions of the Model 3 and Model Y, widening accessibility without sacrificing core margins.
These moves countered affordability concerns and attracted buyers who had been waiting on the sidelines. Combined with attractive financing and leasing options, the pricing strategy converted interest into actual orders more effectively than many analysts expected.
Broad European Recovery
Supported by government incentives, corporate fleet electrification, and easing political headwinds around CEO Elon Musk, Tesla was supplied additional momentum through stronger registration numbers throughout Europe.
Strong exports from the Shanghai Gigafactory and a production ramp at Giga Berlin ensured supply met this resurgent demand. Corporate buyers, in particular, accelerated transitions to EVs to meet sustainability targets, providing a steady volume base.
These elements created a virtuous cycle that delivered the strong deliveries report. While bears correctly flagged the loss of the U.S. tax credit as a risk, Tesla’s diversified playbook demonstrated that it could remain resilient against those headwinds. The Q2 beat suggests the company remains adept at navigating shifting market conditions, even as competition intensifies.
A Tesla Semi was involved in a fatal collision on U.S. Highway 50 in Dayton, Nevada, on Sunday, June 28, 2026, marking the first known fatal crash involving the electric Class 8 truck. The incident occurred around 7:20 a.m. at the intersection with Traditions Parkway, approximately 40 miles east of Reno and close to Tesla’s Gigafactory Nevada.
According to the Lyon County Sheriff’s Office and the Nevada State Police Highway Patrol, a semi-truck struck two passenger vehicles stopped at a traffic signal. The truck hit the vehicles from behind. Two people were pronounced dead at the scene, and a third person suffered life-threatening injuries and was flown to a hospital, Forbes reported.
Preliminary statements gathered at the scene by the Lyon County Sheriff’s Office suggested the truck driver may have fallen asleep at the wheel. However, the Nevada Highway Patrol, which is leading the investigation, stated that the official cause has not yet been determined.
Additional information is expected to be released early the following week. The truck was seized for evidence as part of the ongoing probe.
Responders at the scene included deputies from the Lyon County Sheriff’s Office, personnel from the Nevada Highway Patrol, Central Lyon County Fire Department, and the Nevada Department of Transportation. The crash led to the temporary closure of U.S. 50 in both directions.
The Tesla Semi is Tesla’s battery-electric heavy-duty truck, produced at the nearby Gigafactory in Nevada. Authorities initially described the vehicle as a semi-truck; its make was subsequently confirmed through reporting and scene identification; an interesting bit of information here, as the Semi is not yet available publicly and many do not know that Tesla builds electric trucks.
The investigation remains active, with no further official details on contributing factors or vehicle systems released as of early July 2026.
This incident highlights ongoing scrutiny of commercial vehicle safety on Nevada highways, particularly involving fatigue. Law enforcement continues to gather evidence and witness statements.
Texas man charged in fatal Tesla crash where he blamed Autopilot
Tesla’s strong Q2 deliveries: Four key drivers behind the surprise
