EU type-approval of the automated driving system of fully automated vehicles (Implementing Regulation (EU) 2022/1426, as amended by Implementing Regulation (EU) 2026/481)
The automated driving system of a fully automated vehicle must perform the entire driving task within its operational design domain, detect when it leaves that domain, diagnose its own faults and stop the vehicle in a minimal risk condition, record defined occurrences in a data storage system, and be protected from unauthorised access under UN Regulation No. 155. The manufacturer needs a certified safety management system, an assessment with tests witnessed by a technical service, and in-service monitoring with reporting of occurrences to type-approval authorities, market surveillance authorities and the Commission.
Scope. Reaches a US developer of a fully automated vehicle of category M or N (Article 1) that seeks EU type-approval to sell or deploy it in the EU.
Draft mapping. Drafted by the Register's agents from the rule's text and not yet confirmed by a person. It is the Register's reading, not legal advice: whether and how the rule applies to you is a question for counsel.
Controls this rule maps to
Required by the text The rule's text requires a measure that is this control, or plainly includes it. Implied A binding rule whose purpose needs this control, but whose text does not name it. The Register's reading. Recommended A voluntary standard or guidance recommends it; nothing binds you to it. Proposed Appears in a proposed rule or proposed provision that is not yet in force.
| Control | Strength | Where in the rule, and why | Confidence | Missing or failed in |
|---|---|---|---|---|
| Hard domain restriction C-E2 | Required by the text | Annex II point 3.1.2: 'The ADS shall detect and respond when one or more ODD conditions are not fulfilled or no longer fulfilled'. | high | 4 cases |
| Degraded-input detection C-I3 | Required by the text | Annex II point 4.1.1: 'The ADS shall self-diagnose faults and failures'. | high | 3 cases |
| Automated fail-safe C-R2 | Required by the text | Annex II point 4.1.2.2: 'The ADS shall execute a MRM to achieve a MRC in the event of a failure of the ADS and/or other vehicle system that prevents the ADS from performing the DDT'. | high | 2 cases |
| Independent audit log C-V1 | Implied | Annex II point 9.1: the ADS 'shall record' listed occurrences (activation, remote operator requests, detected collision, MRM engagement, ADS failures); 9.6.2 first-in-first-out overwriting; 9.6.3 retrievable after a crash for M1/N1. No requirement that the record be protected from the ADS or the manufacturer. | high | 1 case |
| Reporting integrity C-V2 | Required by the text | Annex III Part 2 point 5.4: 'The manufacturer shall report to type-approval authorities, market surveillance authorities and the Commission the relevant occurrences in accordance with Part 5'; Part 5 point 2.1: 'The manufacturer shall notify without delay any safety critical occurrences'; 2.2: short-term occurrences 'within one month'; 2.3: annual report. | high | 1 case |
| Independent assurance before deployment C-O2 | Required by the text | Annex III Part 2 point 4.3: 'The manufacturer shall have a valid certificate of compliance for the safety management system (SMS)'; point 4: tests 'performed or witnessed by the Technical Service'; point 1.1: verification 'through targeted spot checks and tests'. | high | 1 case |
| Organizational recovery process C-R4 | Required by the text | Annex III Part 2 point 5.5: 'The manufacturer shall have processes to manage potential safety-relevant gaps post-registration and to update the vehicles if necessary'. | medium | 1 case |
| Actor identity verification C-A1 | Implied | Annex II point 8.1: 'The ADS shall be protected from unauthorised access in accordance with UN Regulation No 155'. | medium | 8 cases |