Regulation · Safety standard
13 Cal. Code Regs. § 227.54: Reporting Collisions
Requires a manufacturer to report collisions involving a permitted autonomous vehicle. As amended (effective April 28, 2026, OAL File 2025-0415-04), crash reporting aligns with US DOT / NHTSA guidelines. Previously numbered § 227.48. Part of California's broader autonomous-vehicle framework (see california-av-regulations, the comprehensive DMV plus CPUC entity).
Jurisdiction: United States/California · Effective 2018-04-02
Machine-readable surfaces
- Markdown mirror: /regulations/ca-ccr-13-227-54.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/regulations/cd7b2634-f3e7-4877-a9b5-d2970077b341
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (3)
- OAL Notice Register 2025 No. 17-Z (Apr 25, 2025) — DMV Autonomous Vehicles, Notice of Proposed Action (OAL File Z2025-0415-04): Informative Digest noting crash reporting aligned with US DOT/NHTSA · https://oal.ca.gov/wp-content/uploads/sites/166/2025/04/2025-Notice-Register-No.-17-Z-April-25-2025.pdf · 2025-04-25
- California DMV adopted regulatory text — 13 CCR Article 3.7 (Testing of Autonomous Vehicles), OAL File 2025-0415-04, effective April 28, 2026 · https://www.dmv.ca.gov/portal/file/adopted-regulatory-text-article-3-7-2025-0415-04-pdf · 2026-04-28
- Cornell LII — 13 CCR § 227.48 (pre-amendment representation of the collision-reporting content, formerly numbered § 227.48) · https://www.law.cornell.edu/regulations/california/13-CCR-227.48
Status history
- In effect · 2018-04-02 · editor:DEPLOY content-agent (Sprint 1.5b status-event pass)
California AV regulation (Title 13 CCR); current canonical, in effect (framework effective Apr 2, 2018). Baseline status event.
Common questions
- What does 13 Cal. Code Regs. § 227.54: Reporting Collisions cover?
- Requires a manufacturer to report collisions involving a permitted autonomous vehicle. As amended (effective April 28, 2026, OAL File 2025-0415-04), crash reporting aligns with US DOT / NHTSA guidelines. Previously numbered § 227.48. Part of California's broader autonomous-vehicle framework (see california-av-regulations, the comprehensive DMV plus CPUC entity).
- Where does 13 Cal. Code Regs. § 227.54: Reporting Collisions apply?
- 13 Cal. Code Regs. § 227.54: Reporting Collisions is recorded as a safety_standard applying in California on the DEPLOY registry.
- When did 13 Cal. Code Regs. § 227.54: Reporting Collisions take effect?
- 13 Cal. Code Regs. § 227.54: Reporting Collisions is recorded as effective April 2, 2018 on the DEPLOY registry.
- Is 13 Cal. Code Regs. § 227.54: Reporting Collisions still in effect?
- 13 Cal. Code Regs. § 227.54: Reporting Collisions is currently in effect and applies to covered operators in the named jurisdiction.
- What types of robots does 13 Cal. Code Regs. § 227.54: Reporting Collisions apply to?
- 13 Cal. Code Regs. § 227.54: Reporting Collisions is recorded as applying to autonomous vehicles on the DEPLOY registry.
- Which robot models on the DEPLOY registry fall under 13 Cal. Code Regs. § 227.54: Reporting Collisions?
- 8 robot models on the DEPLOY registry match the form-factor scope of 13 Cal. Code Regs. § 227.54: Reporting Collisions: Apollo RT6, Argo AI Self-Driving System, Aurora Driver, AutoX RoboTaxi and 4 others. Form-factor scope match does not by itself establish compliance status; review the underlying primary sources for each operator.
Methodology: Verified · 3 sources (1 primary) · last reviewed 2026-05-31
Verification posture
Verified
High confidence
Review state
Stable
Last reviewed 2026-05-31
Architectural position
Cohort: av
Sources by quality tier
- 2
- unclassified
- Unclassified source
- 1
- primary-regulatory-filing
- Regulatory filing
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for 13 Cal. Code Regs. § 227.54: Reporting Collisions.Canonical ID cd7b2634-f3e7-4877-a9b5-d2970077b341