FSD v14.3.2 Is Out and It Finally Fixes That Annoying Double-Stop
Tesla started pushing FSD v14.3.2 the week of April 21st. Not a massive overhaul, but there are some things worth paying attention to, including one fix I've wanted for a while and one limitation that's still not resolved.
The Unified Model Is the Actual News
The biggest change in v14.3.2 isn't something you'll immediately notice. Tesla unified the model across Actually Smart Summon, FSD, and Robotaxi. One model powering all three instead of separate systems, with the stated goal of more capable and reliable behavior across all of them.
This makes sense from an engineering standpoint. Running three separate models means three separate maintenance paths and three ways for behavior to diverge. Consolidating them is the right long-term move, assuming the unified model generalizes well. And improvements in one mode should now carry over to the others instead of being siloed.
The Disengagement Menu
There's a new disengagement reason menu. When you take over from FSD, you can categorize why: Critical, Comfort, Preference, or Other.
This is clearly data collection. Tesla wants to know whether you grabbed the wheel because the car was about to do something genuinely dangerous versus you just didn't like how it handled a merge. That's useful signal for training. And having to consciously categorize the intervention might actually make you a more useful tester. Instinct-grabbing the wheel without thinking about why doesn't give Tesla much to work with.
Double-Stopping at Stop Signs: Fixed
FSD v14.3.2 fixes double-stopping at stop signs with painted lines. The car would stop at the line, then creep forward and stop again before proceeding. Not dangerous. But jarring, and not exactly confidence-inspiring for anyone watching from the cross street.
This kind of thing matters more than it sounds. Edge cases that make FSD feel hesitant and mechanical erode trust in the system even when they're not safety issues. Smooth, predictable behavior at intersections is table stakes.
Actually Smart Summon Keeps Getting Better
Responsiveness, speed, and navigation confidence in parking lots all improved in v14.3.2. This continues work that started in v14.3.
Actually Smart Summon is one of those features that looked impressive in demos and then consistently disappointed in real parking lots. Weird layouts, tight turns, pedestrians who don't expect a car moving without a driver. If these improvements hold up in actual use, it's a genuinely useful feature. Low-speed parking lot navigation is exactly where a working summon saves real hassle.
What's Still Not Working
Region-specific signage remains inconsistent. Specifically, signs like "Except Right Turn" under stop signs. These are common enough in parts of the U.S. that it's not a rare edge case. FSD v14.3.2 still doesn't handle them reliably.
Signage variation across states and counties is genuinely hard to solve at scale. That's not an excuse, just context. But "hard" and "acceptable" aren't the same thing, and this one's been lingering.
Unsupervised FSD: Geography First, Timeline Unclear
On the Q1 2026 earnings call, Elon Musk said unsupervised FSD would roll out gradually by geography, possibly state by state in the U.S. No specific dates attached to specific places.
The geographic approach makes regulatory sense. Autonomous vehicle approvals don't transfer across state lines, and some states move faster than others on this. This could mean certain states see unsupervised FSD well before others. But "gradually" and "possibly" aren't commitments. I'll take it seriously when there's an actual location and date on the calendar.
Bottom Line
v14.3.2 is a solid incremental update. The unified model is the most structurally significant change. The double-stop fix is the most immediately noticeable improvement for anyone who drives through intersections with painted lines (which is everyone). The disengagement categorization is worth using honestly if you're a regular FSD user.
The region-specific signage issue is a reminder that consistent and almost-consistent are different things. Check NotATeslaApp for version rollout tracking.
Source: Teslarati