Why Tesla Needs to Change FSD Supervised for Europe and Beyond
The UNECE regulations for supervised driving systems are coming into effect in January 2027 and are only one type approval away from allowing FSD Supervised on the roads in the UK, Europe and UNECE (DCAS) member countries.
However, Tesla FSD Supervised is not fully aligned with UN R171 Series 02. Software changes are still required before Tesla can seek a cleaner type approval under that series.
This is the second part of our Tesla FSD Regulations for UK and Europe series. Part 1 explained UNECE, DCAS and UN R171. This piece looks at the gap between today’s European FSD Supervised and the Series 02 text.
Why Series 02 is the next test
The Dutch type-approval authority RDW approved FSD Supervised in April 2026 under UN R171 Series 01, with Article 39 exemptions under EU Regulation 2018/858. Those exemptions exist because parts of FSD Supervised, especially urban use and more extensive system-initiated manoeuvres, sit outside the baseline Series 01 envelope. Official background on the regulation family is on the UNECE vehicle regulations pages.
Series 02 is meant to bring more of that capability into the standard rulebook. GRVA sent the draft 02 series to WP.29 as document WP.29/2026/86. The working document is on the UNECE Series 02 proposal page. The World Forum considered it at its June 2026 session. After the usual post-adoption period, the series is expected to enter into force in late January 2027, around 28 January if that clock runs cleanly and no objection blocks it.
That is the opening Tesla needs. It is also a constraint. Series 02 does not simply bless today’s software. It sets extra process rules around how the car may start a move, how fast it may go, how hard it may corner, and how it must check the driver first.
Basic Autopilot in Europe is a different problem. That system is still boxed in by older UN R79 steering rules: a lateral acceleration cap, driver-initiated lane changes, and a six-metre remote parking limit. We set that out in a separate thread on 10 August 2026. The way out of those Autopilot limits is FSD Supervised under R171. Series 02 is the next version of that R171 rulebook.
What still needs to be changed in FSD for regulatory compliance?
On 9 August 2026 we published a point-by-point breakdown of the remaining gaps. Tesla has not issued an official Series 02 compliance list. The comparison below is how current European FSD Supervised behaves against the Series 02 requirements that matter for a cleaner approval.
“Tesla FSD Supervised is not fully compliant with the new UN R171 Series 02 (DCAS) rules that take effect late January 2027. Software changes are required. Here’s exactly what needs to change:”
FSD Approval Tracker (@NotAnFSDTracker), 9 August 2026
System-initiated manoeuvres are the big one
This is the largest gap. Under Series 02, the car cannot simply start a lane change, a turn, or a move away from a traffic light the way FSD often does today. The system may still propose those moves. It has to do so in a more formal way.
The new process for a system-initiated manoeuvre looks like this:
- A clear visual announcement, generally at least about three seconds before the move starts.
- The cabin camera must confirm the driver is looking and engaged.
- The driver must be able to reject or abort the move easily before it begins.
- If the driver rejects it, the system cannot immediately retry the same manoeuvre.
That last point already exists in spirit in Series 01: if the driver rejects an announced manoeuvre, the system should not start the same one again unless the situation has changed or there is a risk of an imminent collision. Series 02 extends this logic into the urban and non-highway cases that today’s “FSD” actually uses, and it pairs it with a harder engagement check right before the move.
Today’s European FSD Supervised will change lanes, take junctions and pull away from lights without that full announce, confirm and reject sequence. That is exactly why Article 39 was needed in the Netherlands, and why a straight Series 02 path is not a simple approval. An exemption would be required to allow FSD to operate outside of the Series 02 regulation.
What about traffic lights and tight urban turns?
Two everyday FSD behaviours sit inside that manoeuvre rule.
Traffic light departure. The car should only move off if visual engagement is confirmed. If the camera cannot confirm the driver is attending, the car stays stopped. That is a change from a system that is ready to go when the light turns green and the path is clear.
Tight urban curves and turns. If the system does not have visual confirmation that the driver is engaged, it should escalate warnings and, if needed, bring the car to a safe stop. Highway-style nagging after the fact is not enough for these sharper, slower, more cluttered moves.
Owners who have used FSD in the United States will recognise the difference. There the car often just takes the junction. In a Series 02 Europe build, the same junction should come with a short, visible warning and a confirmed glance from the driver first.
Does the speed offset have to change?
Yes, if Tesla wants a cleaner Series 02 approval. Tesla currently lets drivers set a speed offset that routinely takes the car above the posted limit. Series 02 is written so the system does not default to travelling above that limit.
This is not a new political argument. Sweden has already flagged the offset at EU level. Our earlier piece on the Swedish TCMV speed-offset objection covers that debate. France has also been among the governments asking harder questions about how the European software behaves. Series 02 turns that concern into a type-approval requirement rather than a talking point.
Tesla can change this in software. A Europe-specific default that tracks the posted limit, or that only exceeds it after a clear driver action, would close the gap. Tesla has already shown it can ship region-specific speed behaviour. What it has not done yet is ship a Series 02-ready default.
Why the car may feel slower in corners
Series 02 also expects the car to stay inside a strict maximum lateral acceleration in curves, around 3 m/s² for passenger cars, with validation tests. That figure will be familiar to anyone who has used European Autopilot. UN R79 has used a similar cap for years.
FSD Supervised is a more capable system than Autopilot, but a Series 02 approval still has to show the car does not take corners harder than the approved envelope. The software will need a calmer driving style on tighter ramps and urban bends than a US build that is free of that test.
That does not mean FSD becomes useless in towns. It means Tesla has to prove the European profile stays inside the numbers. For an end-to-end model, those hard limits are awkward. You cannot only prompt the network to “drive nicer.” Some of this will need explicit constraints, extra training, or both.
Driver monitoring gets more specific
Tesla already runs a continuous attentiveness system with the cabin camera. That is a start, and it is one reason FSD Supervised could be approved as a DCAS product at all. Series 02 adds event-specific checks immediately before system-initiated moves in complex environments, especially urban ones.
The practical difference for owners is the timing of the nag. Today a lot of the prompting still feels like highway Autopilot: hands, eyes, a warning if you look away too long. Series 02 wants an extra confirmation right as the car is about to change lane, turn, or leave a stop line. More targeted prompts around city manoeuvres, not only a general “pay attention” loop.
The remaining Series 02 gaps
The table below compares what Series 02 expects with how US FSD works today, based on the 9 August breakdown.
| Requirement | What Series 02 expects | How US FSD Works | Likely change |
|---|---|---|---|
| System-initiated manoeuvres | Announce, confirm engagement, allow a reject, no instant retry | Often starts the move without that full sequence | New visual timing and reject logic |
| Traffic light departure | Move off only if the driver is visually engaged | Ready to go when the path is clear | Hold at the line until confirmed |
| Urban turns and tight curves | Escalating warnings, then a safe stop if engagement is missing | General attentiveness nags, not event-specific | City-specific confirmation and fallback |
| Speed behaviour | Do not default to running above the posted limit | Driver-set offset can sit above the limit | Europe default tied to the posted limit |
| Lateral acceleration | About 3 m/s² for passenger cars, with tests | Can take tighter lines | Calmer cornering envelope |
| Driver monitoring | Event-specific check before complex system-initiated moves | Continuous camera monitoring already exists | Extra pre-manoeuvre confirmation |
Are these changes realistic before late January?
They are software changes. Tesla does not need a new sensor suite to announce a lane change three seconds early, to hold at a red-to-green light until the driver looks, or to cap the default speed at the posted limit. The hard part is doing that inside an end-to-end driving model without breaking the rest of the stack.
Hard-coded values (a three-second announce window, a 3 m/s² cap, a no-retry rule) sit awkwardly on a network that was trained to take the next safe action. Tesla can wrap those rules around the model. It can also retrain. Either path is possible. Neither is a weekend patch, and Tesla has not published a Series 02 delivery date.
If a compliant build is ready when Series 02 enters into force, the remaining regulatory step is a type approval under that series. That is a much cleaner path than Series 01 plus Article 39. Other countries that apply R171 can then recognise it under the 1958 Agreement. Live country status is on the global map and the EU Tracker.
It is not automatic on the day the series starts. Tesla still has to apply. A national authority still has to grant the approval. The April 2026 RDW decision shows that can be done. It also shows how much of today’s approval still depends on exemptions that Series 02 is supposed to make less necessary.
What this means if you own a Tesla in Europe or the UK
If you already have FSD Supervised in a country that recognised the Dutch approval, nothing about Series 02 switches your car off in January. The new series is the rulebook for the next type approval, not a kill switch for the current one.
If you are still waiting, Series 02 is the more important date to watch after the current exemption path. A cleaner approval would make it easier for other EU states and the United Kingdom to recognise the same product without another round of Article 39 politics. That is why the Netherlands approval and Series 02 belong in the same conversation.
What you should not expect is a US-identical drive. The Series 02 car will announce more, wait for a look, refuse to default above the limit, and take some corners more gently. That is the price of a standard DCAS approval instead of an exemption.
What comes next in this series
The next part asks how soon FSD Supervised can be approved across UNECE member states, including the EU, the UK, Japan, Turkey, Germany, France, Italy, etc., once a fuller R171 path is in place.
For notifications when that article is published, or when a country status changes, join the newsletter: Get the newsletter.
