Proposal to clarify the EDR trigger input in the case of vehicles approved to UN R169 (M₂, M₃, N₂, N₃) equipped with airbags (Supplemental Restraint Systems).

Event data recorders shall record critical crash-related parameters shortly before, during and immediately after a collision, including vehicle speed, braking, position, tilt, and state of safety systems. Data shall be anonymised, protected against manipulation, operate on a closed-loop system, and be made available to national authorities only for accident research and analysis. Automated vehicles and fully automated vehicles shall comply with technical specifications for event data recorders. Discussion topics include whether recording requirements should be adapted for ADS-driven vehicles, whether ADS-specific data elements such as timestamp data should be recorded, and related issues.

Proposal concerning “detected objects” and data element precision.

Proposal concerning “detected objects” and data element precision for the ADS regulation provisions on DSSAD.

The EDR-DSSAD informal group approved definitions for detected objects and recording parameters, established language for power and communication failures, and agreed to a -2.5-second to 300-millisecond recording interval for rollover events. Discussions on fire-resistant data storage and automated emergency braking recording intervals remain unresolved. The group deferred decisions on EDR requirements for automated driving systems pending further analysis of overlap with DSSAD regulations.

The previous session report was approved with a note on post-crash recording intervals. A DSSAD Guidance Document feedback deadline was set for month-end. Phase 2 discussions on near-miss events require clarification of concepts and their safety contributions. For EDR Step 2, a 10 Hz sampling rate was adopted over 2 Hz following opposition from industry regarding implementation burden and support from regulatory bodies for accident reconstruction needs. Outstanding discussion items will be consolidated into a working document. Terms of Reference discussions on maintaining current structure versus integrating DSSAD into the ADS Informal Working Group will continue. The May 12 meeting was rescheduled due to conflict with ESV Toronto.

This document provides recommendations for DSSAD, a vehicle capability that monitors Automated Driving System (ADS) performance. It defines key terms including ADS, Dynamic Driving Task (DDT), Operational Design Domain (ODD), and Mitigated Risk Condition (MRC). The document specifies requirements for data storage, security, format, and accessibility. DSSAD must record time-stamped events such as feature activation/deactivation, ODD exits, and fallback responses, plus time-series data during triggering events like collisions, including vehicle dynamics and sensor information.

Comments on the proposal for a03 series of amendments to UN Regulation No. 160. Modifications include renumbering paragraph 2.2 as paragraph 2.25, deleting paragraph 2.25, and amending definitions for “End of event time,” “Engine throttle, percent full,” “Non-volatile memory,” and other terms. New paragraphs 2.71–2.82 introduce definitions for rollover protection system, advanced emergency braking system, blind spot monitoring system, and driver assistance systems. Paragraphs 5.3.1, 5.3.2, and 5.3.3 are amended to clarify triggering and locking conditions for rollover events and vulnerable road user events, and to establish time zero. Paragraph 5.4.3 clarifies crash test requirements.

The agenda includes discussion of DSSAD regulatory text guidance, EDR Step 2 proposals comments, and EDR for ADS. The next meeting is scheduled for September 15-17, 2026, as a hybrid event in Europe.

Systems with ACSF B2, D and E functionality cannot be approved to UN R79 unless incorporated within a DCAS complying with UN R171. However, these functionalities may exist independently of DCAS, requiring clear distinction. Where not part of DCAS, this must be specified in the EDR regulation. A new EDR data element, “DCAS status”, could encompass ACSF B2, D and E functionalities. These functionalities are now treated either as individual functions or as components of DCAS.