- Federal agenciesCreates a centralized, machine-readable federal dataset that supporters would say improves transparency and enables NHT…
- Potential benefitStandardized reporting requirements could support development of jobs and business activity in compliance, data enginee…
- Federal agenciesFederal-level reporting reduces fragmentation across states by providing a single regulatory reporting standard, which…
AV Safety Data Act
Referred to the House Committee on Energy and Commerce.
This bill (AV Safety Data Act) directs NHTSA to promulgate regulations within 90 days requiring manufacturers and operators covered by NHTSA’s Third Amended Standing General Order 2021-01 to submit specified incident and usage data. Covered entities must provide monthly reports including miles traveled (disaggregated by make, model, software version, location, road type, and occupant presence), collisions injuring vulnerable road users or other-vehicle occupants, and detailed information about “unplanned stoppage events” (including VIN, license plate, location, timestamps, environmental conditions, and resolution).
Privacy vs. transparency: Liberals and centrists emphasize safety and public data; conservatives emphasize privacy and limiting public release of VIN/license plate and precise geolocation.
Relative to its intended legislative type, this bill clearly establishes new statutory reporting obligations for covered entities and prescribes specific data elements, timelines, and public disclosure requirements, while delegating regulatory and operational detail to NHTSA.
This bill (AV Safety Data Act) directs NHTSA to promulgate regulations within 90 days requiring manufacturers and operators covered by NHTSA’s Third Amended Standing General Order 2021-01 to submit specified incident and usage data.
Covered entities must provide monthly reports including miles traveled (disaggregated by make, model, software version, location, road type, and occupant presence), collisions injuring vulnerable road users or other-vehicle occupants, and detailed information about “unplanned stoppage events” (including VIN, license plate, location, timestamps, environmental conditions, and resolution).
Level 2 ADAS data may only be submitted if the system was engaged or within 30 seconds before an unplanned stoppage and must not contain personally identifiable information about a human driver.
On content alone, this is a targeted regulatory oversight bill with a safety and transparency rationale that can attract bipartisan interest; however, it creates nontrivial compliance burdens, public-release requirements tied to sensitive data (VINs, precise locations, software versions), and demands rapid agency rulemaking. Those elements invite industry pushback and privacy/trade-secret debate that could slow or alter the bill, making enactment plausible but not highly likely without negotiation and amendments.
Relative to its intended legislative type, this bill clearly establishes new statutory reporting obligations for covered entities and prescribes specific data elements, timelines, and public disclosure requirements, while delegating regulatory and operational detail to NHTSA.
Privacy vs. transparency: Liberals and centrists emphasize safety and public data; conservatives emphasize privacy and limiting public release of VIN/license plate and precise geolocation.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- ManufacturersImposes new regulatory and administrative burdens on manufacturers and operators—collecting, validating, storing, and t…
- Potential burdenPublic release of detailed event-level data including VINs, license plates, precise locations, and timestamps raises pr…
- Potential burdenMandated disclosure of detailed operational data could increase legal and liability exposure for covered entities (e.g.…
Why the argument around this bill splits.
Privacy vs. transparency: Liberals and centrists emphasize safety and public data; conservatives emphasize privacy and limiting public release of VIN/license plate and precise geolocation.
A mainstream liberal would likely view this bill positively as a transparency and safety measure that makes AV performance and incidents visible to regulators, researchers, and the public.
They would appreciate data disaggregation (including vulnerability to road users, software versions, and location) to identify patterns that could inform stronger safety rules and protect pedestrians and cyclists.
They would note some privacy and surveillance concerns—especially because the bill requires VINs and license plates in reports and mandates public release—so they would want stronger safeguards and anonymization for individuals.
A centrist/ moderate would generally view the bill as a reasonable, evidence-building regulatory measure that standardizes reporting and increases information available to regulators and the public.
They would like the bill’s emphasis on disaggregated metrics and on events that harm vulnerable road users, while being mindful of regulatory cost, administrative burden, and industry innovation.
They would seek clearer implementation details, cost estimates, protections for legitimate trade secrets, and resources for NHTSA to carry out the mandate.
A mainstream conservative would likely be skeptical of new federal reporting and public-disclosure mandates that impose regulatory burdens and potentially expose proprietary information and vehicle owners’ data.
They would be concerned that mandatory public release of VINs, license plates, and precise geolocation is intrusive, raises security and privacy issues, and could damage business competitiveness or deter innovation and investment in AV technology.
They might acknowledge the safety rationale for data collection, but would push for narrower scope, stronger protection of trade secrets, state primacy where appropriate, and reduced frequency or public release of sensitive data.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, this is a targeted regulatory oversight bill with a safety and transparency rationale that can attract bipartisan interest; however, it creates nontrivial compliance burdens, public-release requirements tied to sensitive data (VINs, precise locations, software versions), and demands rapid agency rulemaking. Those elements invite industry pushback and privacy/trade-secret debate that could slow or alter the bill, making enactment plausible but not highly likely without negotiation and amendments.
- No cost estimate or implementation detail for NHTSA or covered entities is provided in the text; fiscal impacts (agency staffing, data infrastructure, compliance costs) are therefore unknown.
- The bill references and depends on the external 'Third Amended Standing General Order 2021-01' (effective date specified) for key definitions and scope; how that Order is written and how it interacts with these statutory requirements is not in the bill text.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Privacy vs. transparency: Liberals and centrists emphasize safety and public data; conservatives emphasize privacy and limiting public rele…
On content alone, this is a targeted regulatory oversight bill with a safety and transparency rationale that can attract bipartisan interes…
Relative to its intended legislative type, this bill clearly establishes new statutory reporting obligations for covered entities and prescribes specific data elements, timelines, and public disclosure requirements, whi…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.