Research briefs · Mobility · Updated 2026-11-08

Automated-driving crash reports need reproducible data

NHTSA reporting turns crash triage, version history, and correction tracking into a standing engineering workflow.

Thesis

Automated-driving crash reporting is not mainly a connectivity or compliance-checkbox problem. NHTSA’s Standing General Order requires named manufacturers and operators to report specified crashes involving ADS or SAE Level 2 advanced driver assistance systems. turns the quality, lineage, and operational handling of crash notice, vehicle and software configuration, automation state, source evidence, review, submission, and correction into part of the product itself. The durable advantage belongs to teams that can show what happened, why it happened, who acted, and how an exception was resolved without erasing the original evidence.

Market context

Editorial analysis: Versioned reporting shows what was known at each deadline while allowing later investigation to improve factual accuracy. This product-design interpretation is not a finding established by the cited source.

Editorial analysis: teams applying this framework may need to consider data lineage, exception handling, and responsibility across the organizations involved.

Evidence

  • NHTSA’s Standing General Order requires named manufacturers and operators to report specified crashes involving ADS or SAE Level 2 advanced driver assistance systems.
  • NHTSA publishes the order, reporting criteria, data, and explicit cautions about interpreting incident totals.
  • NHTSA says the order was first issued in 2021 and amended in 2021, 2023, and 2025—four version events that require report-pipeline change control.
  • Editorial analysis: a product or implementation should be assessed against its own architecture, operating context, and applicable obligations; the cited source does not validate a particular vendor or deployment.

Competing viewpoints

Editorial analysis: a narrow implementation may reduce cost and complexity, but may leave operational edge cases unresolved.

Editorial analysis: Public report counts can be misleading as comparative safety measures because reporting exposure, fleet size, data availability, and operating domain differ. may be a relevant alternative to evaluate; the appropriate control level depends on context and risk.

Implications

  • Architecture must preserve both original evidence and current normalized state; overwriting either one sacrifices auditability or usability.
  • Operational metrics should separate transport success from substantive completion, exception age, correction frequency, and customer impact.
  • Vendor contracts become product dependencies when crash notice, vehicle and software configuration, automation state, source evidence, review, submission, and correction cannot be exported, interpreted, or supported after access ends.
  • Governance should assign decision rights across product, compliance, security, and operations before a live exception forces an improvised answer.

Actionable takeaways

  • Map the end-to-end journey for crash notice, vehicle and software configuration, automation state, source evidence, review, submission, and correction, naming every source system, transformation, decision owner, handoff, and externally visible status.
  • Create a field-level data dictionary that records provenance, permitted values, validation logic, retention, and the authority for each critical element.
  • Build an exception taxonomy with service targets, escalation ownership, customer communications, and a rule against silently rewriting source evidence.
  • Run tabletop tests for malformed input, partner outage, disputed facts, correction, and bulk export; retain the observed results and remediation owners.
  • Review the primary source and implementation assumptions on a scheduled cadence, and require legal or regulatory review when scope or claims change.

Limitations and risks

Reporting orders and criteria can change, and published data contain caveats and are not exposure-adjusted safety rankings. This analysis interprets one authoritative source as a product-design signal; it is not legal advice and does not resolve fact-specific applicability. The source may be amended, supplemented, delayed, or interpreted through additional guidance. Outcomes also depend on data supplied by counterparties and on organizational controls outside the software. Teams should confirm current requirements, jurisdiction, contracts, technical specifications, and effective dates before relying on any proposed control.

Sources and citations

  1. Standing General Order on Crash Reporting — National Highway Traffic Safety Administration, accessed 2026-09-06