NHTSA delays EDR expansion to 2028 phase-in

NHTSA delays expanded pre-crash data capture, kicking off a four-year phase-in starting September 1, 2028.

The final rule, published in the Federal Register, amends the agency’s regulation governing Event Data Recorders to push back the schedule for expanded pre-crash data capture after petitions for reconsideration of the December 18, 2024 rule. The four-year phase-in is designed to align the rollout with how vehicles are produced and with what manufacturers can practically implement, the agency says, rather than forcing a rapid, fleet-wide upgrade.

The rule clarifies how the data architecture will unfold as part of the broader push toward more comprehensive crash data. EDRs, by design, focus on time-series data used after a crash to reconstruct events and determine causation. The rule also notes the role of DSSADs, which are timestamped flags intended to distinguish between human and machine operation in vehicles equipped with automated driving systems. While EDRs capture post-crash information, DSSADs address near-crash and pre-crash contexts that become more relevant as automation levels rise. The agency points out that the FAST Act mandate historically emphasized pre-crash recording duration for crash causation studies but did not address ADS-specific data elements. In parallel, NHTSA remains an active participant in UNECE WP.29 efforts to develop a Global Technical Regulation that would harmonize data standards across borders.

For compliance officers and technology leaders, the rollout signals a staged path rather than a single compliance date. The four-year ramp means teams should begin mapping current data collection capabilities to the expanded pre-crash data set in a way that can be incrementally implemented. It also highlights the distinction between EDRs and DSSADs: EDRs will continue to serve post-crash reconstruction, while DSSADs will increasingly shape the pre-crash and near-crash data picture, especially for vehicles with Level 3 through Level 5 automated driving features. This matters for product roadmaps, as ADS hardware and software updates must be coordinated with both the timing of the phase-in and the evolving ADS data elements that DSSADs aim to capture.

From an enforcement perspective, the rule establishes a formal, time-bound path to compliance, with agencies watching for adherence to each phase as the fleet transitions. The phased approach lowers the immediate risk of penalties for not meeting an abrupt standard, but it also concentrates effort on getting the fleet aligned with the upcoming data requirements as the four-year period progresses. For operators, the key tension is balancing existing production schedules, supply-chain constraints, and the need to invest in data governance and telemetry infrastructure that can handle richer pre-crash and ADS-specific data streams.

Two to four practitioner-focused takeaways emerge. First, risk and compliance teams should start inventorying data elements currently captured by EDRs and identify gaps that DSSADs and ADS data elements will fill, so upgrades can be staged without disrupting production lines. Second, product and engineering leaders should align ADS feature rollouts with the anticipated data capture capabilities, ensuring that vehicle software updates do not outpace the corresponding data-collection and storage capabilities. Third, procurement and supplier management teams must factor in hardware and software changes that enable richer data capture, including potential sensor and telematics upgrades. Finally, watch for continued guidance from UNECE WP.29 and other global bodies as harmonization efforts unfold, since alignment with international standards will influence how U.S. automakers and component suppliers design future data capture capabilities.