California AB 3061 (Vehicles: Autonomous Vehicle Incident Reporting 2024)

Adds Section 38760 to California's Vehicle Code, requiring autonomous vehicle manufacturers to report collisions, disengagements, and traffic violations from July 31, 2025. Mandates quarterly reports on vehicle miles and incidents. Requires data publication and redaction by the DMV starting January 1, 2028.

  • Authority: California
  • Parent authority: State governments
  • Jurisdiction: United States
  • Collections: U.S. state and local documents
  • Most recent activity: Defunct
  • Most recent activity date: 2024-09-27

Risk subdomain coverage

Good coverage — Comprehensive governance measures or mitigations with clear procedures relating to the risk subdomain are explicitly described.

  • Governance failure
  • Lack of capability or robustness
  • Lack of transparency or interpretability

Minimal coverage — Brief mention but no specific mitigations, recommendations or governance measures relating to the risk subdomain are described.

  • Compromise of privacy
  • Overreliance and unsafe use
  • Competitive dynamics

All other risk subdomains had no coverage in this document.

Risk Coverage Summary

The document has minimal to good coverage of approximately 5-7 subdomains, with primary focus on AI system safety failures (7.3 Lack of robustness), governance mechanisms (6.5 Governance failure - through transparency requirements), and human-computer interaction risks (5.1 Overreliance). Coverage is concentrated in system safety, transparency, and operational monitoring domains specific to autonomous vehicles.

Sector coverage

Good coverage — Comprehensive governance measures or mitigations with clear procedures relating to the sector are explicitly described.

  • Trade, Transportation & Utilities

Minimal coverage — Brief mention but no specific mitigations, recommendations or governance measures relating to the sector are described.

  • Agriculture, Mining, Construction & Manufacturing
  • Information
  • Public Administration (excl. National Security)

All other sectors had no coverage in this document.

Sectors Summary

The document primarily governs the Trade, Transportation and Utilities sector, specifically autonomous vehicle transportation services. It also has secondary coverage of the Information sector through ride-hailing technology platforms that deploy autonomous vehicles.

Legislative Status

Hard Law

Legislative Status Summary

This is a binding California state statute (AB 3061) that adds Section 38760 to the Vehicle Code with mandatory reporting requirements, specific enforcement timelines, and regulatory authority granted to the DMV to establish fees and additional requirements.

Actors

Proposer

  • Entity Types: AI_Governance_Actor
  • Summary: The document is a legislative act enacted by the California State Legislature, as indicated by the formal enactment clause and legislative findings.

Target

  • Entity Types: AI_Developer, AI_Deployer
  • Summary: The legislation explicitly targets manufacturers of autonomous vehicles who test or deploy vehicles on California public roads, requiring them to submit various reports and comply with data collection requirements.

Enforcer

  • Entity Types: AI_Governance_Actor
  • Summary: The DMV is granted explicit authority to collect reports, establish additional requirements, assess fees, maintain and publish data, and enforce compliance with the reporting requirements.

Monitor

  • Entity Types: AI_Governance_Actor
  • Summary: The DMV is responsible for maintaining, reviewing, and publishing all incident reports, while local and state transportation authorities are granted access to these reports for monitoring purposes.

AI Lifecycle Stages

Lifecycle stages covered by the documents, as defined in the OECD Framework for the Classification of AI Systems

  • Verify and Validate
  • Deploy
  • Operate and Monitor

AI Lifecycle Summary

The document primarily focuses on the Deploy and Operate and Monitor lifecycle stages, with comprehensive requirements for post-deployment incident reporting, ongoing monitoring of autonomous vehicle performance, and public transparency. There is minimal coverage of earlier lifecycle stages.

Technical Scope

Terms relating to technical scope that are mentioned or implicitly referenced in the document

  • AI Systems
  • Task-specific AI

Technical Scope Summary

The document explicitly mentions autonomous vehicles and autonomous technology/mode throughout, but does not use AI-specific terminology such as AI models, AI systems, frontier AI, general purpose AI, foundation models, or compute thresholds. The focus is on autonomous vehicle systems as a specific application domain rather than AI systems broadly.

https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202320240AB3061
https://agora.eto.tech/instrument/4052
Explore in the Document View

Document data from AGORA, CSET Emerging Technology Observatory.