AB 3061: Vehicles: autonomous vehicle incident reporting.
- Session Year: 2023-2024
- House: Assembly
- Latest Version Date: 2024-08-31
Current Status:
Failed
(2024-09-27: Vetoed by Governor.)
Introduced
In Committee
First Chamber
In Committee
Second Chamber
Enacted
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV a vehicle collision or disengagement, as defined, that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted, at minimum, on an annual basis, as specified. The bill would require these reports to be submitted on timelines adopted by the DMV that do not exceed reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would additionally, commencing July 31, 2025, require a manufacturer to submit quarterly reports to the department that summarize the vehicle miles traveled, vehicle immobilizations, and certain traffic violations, as specified. The bill would, commencing July 1, 2025, require the DMV to maintain all reports submitted pursuant to the above-described provisions and make the reports available to local and state transportation authorities upon request. The bill would, commencing January 1, 2028, require the department to publish reports in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt, but would require the department to redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing these reports. The bill would authorize the department to establish additional reporting requirements for purposes of these provisions by regulation. The bill would also authorize the department to establish and assess fees to recover costs reasonably incurred by the department for implementing these provisions by regulation.
This bill would incorporate additional conforming changes and references to Section 38752 of the Vehicle Code as proposed to be added by AB 1777, to be operative only if this bill and AB 1777 are both enacted.
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV a vehicle collision or disengagement, as defined, that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted submitted, at minimum, on an annual basis, as specified. The bill would require these reports to be submitted on timelines adopted by the DMV that do not exceed reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would additionally, commencing July 31, 2025, require a manufacturer that is testing or deploying autonomous vehicles, as specified, to submit quarterly reports to the department that summarize the vehicle miles traveled, vehicle immobilizations, and certain traffic violations, as specified. The bill would, commencing July 1, 2025, require the DMV to maintain all reports submitted pursuant to the above-described provisions in an electronic format and make the reports available to local and state transportation authorities upon request. The bill would, commencing January 1, 2028, require the department to publish reports in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt, but would require the department to redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing these reports. The bill would authorize the department to establish additional reporting requirements for purposes of these provisions by regulation. The bill would also authorize the department to establish and assess fees to recover costs reasonably incurred by the department for implementing these provisions by regulation.
This bill would incorporate additional conforming changes and references to Section 38752 of the Vehicle Code as proposed to be added by AB 1777, to be operative only if this bill and AB 1777 are both enacted.
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV a vehicle collision, traffic citation, collision or disengagement, as defined, that occurs when a manufacturers vehicle is operating in autonomous mode in California on California public roads regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted at the time the incident is identified by the manufacturer. on an annual basis, as specified. The bill would require these reports to be submitted on timelines adopted by the DMV that do not exceed reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would additionally additionally, commencing July 31, 2025, require a manufacturer that is testing or deploying autonomous vehicles, as specified, to submit quarterly reports to the department that summarize the above-mentioned reports, vehicle miles traveled, unplanned stops, vehicle immobilizations, and certain traffic violations, and wheelchair-accessible services, violations, as specified. The bill would would, commencing July 1, 2025, require the DMV to publish maintain all reports submitted pursuant to these the above-described provisions in an electronic, open, and machine-readable format electronic format and make the reports available to local and state transportation authorities upon request. The bill would, commencing January 1, 2028, require the department to publish reports in an electronic, open, and machine-readable format on the departments internet website within 30 90 days of receipt, as specified. The bill would authorize the DMV to suspend or revoke the testing and deployment permit of any manufacturer while an investigation of any violations is pending. but would require the department to redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing these reports.
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV a vehicle collision, traffic violation, citation, or disengagement, as defined, or a barrier to access or incident of discrimination for a passenger with a disability, that involves occurs when a manufacturers vehicle is operating in autonomous mode in California regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted at the time the incident is identified by the manufacturer. The bill would require these reports to be submitted on a timeline timelines adopted by the DMV that does do not exceed reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would additionally require a manufacturer to submit quarterly reports to the department that summarize the above-mentioned reports, vehicle miles traveled, unplanned stops, certain traffic violations, and wheelchair-accessible services, as specified. The bill would require the DMV, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, to create and publish an autonomous vehicle incident form and a form to report data required by these provisions by no later than July 1, 2025. The bill would require the DMV to publish all reports submitted pursuant to these provisions in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt, as specified. The bill would authorize the DMV to impose specified fines for violations of the reporting provisions and to suspend or revoke the testing and deployment permit of any manufacturer while an investigation of any violations is pending. The bill would also authorize members of the public or public entities with direct evidence of an incident to submit an autonomous vehicle incident report, as specified.
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV any vehicle collision, traffic violation, or disengagement, as defined, or the assault or harassment of any passenger or safety driver, that involves a manufacturers vehicle in California regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted at the time the incident is identified by the manufacturer. The bill would require these reports to be submitted on a timeline adopted by the DMV that is required to be equal to or shorter than the reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would require the DMV, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, to create and publish an autonomous vehicle incident form and a form to allow for the aggregate analysis of autonomous vehicle safety by no later than July 1, 2025. The bill would require the DMV to publish all reports submitted pursuant to these provisions in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The bill would require the DMV to impose specified fines for violations of the reporting provisions and to suspend or revoke the testing and deployment permit of any manufacturer while an investigation of any violations is pending. The bill would also authorize members of the public or public entities with direct evidence of an incident to submit an autonomous vehicle incident report, as specified.The bill would make related findings and declarations.Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV a vehicle collision, traffic violation, or disengagement, as defined, or a barrier to access or incident of discrimination for a passenger with a disability, that involves a manufacturers vehicle in California regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted at the time the incident is identified by the manufacturer. The bill would require these reports to be submitted on a timeline adopted by the DMV that does not exceed reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would additionally require a manufacturer to submit quarterly reports to the department that summarize the above-mentioned reports, vehicle miles traveled, unplanned stops, and wheelchair-accessible services, as specified. The bill would require the DMV, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, to create and publish an autonomous vehicle incident form and a form to report data required by these provisions by no later than July 1, 2025. The bill would require the DMV to publish all reports submitted pursuant to these provisions in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt, as specified. The bill would authorize the DMV to impose specified fines for violations of the reporting provisions and to suspend or revoke the testing and deployment permit of any manufacturer while an investigation of any violations is pending. The bill would also authorize members of the public or public entities with direct evidence of an incident to submit an autonomous vehicle incident report, as specified.
Existing law authorizes the operation of an autonomous vehicle on public roads for testing purposes by a driver who possesses the proper class of license for the type of vehicle operated if specified requirements are satisfied. Existing law prohibits the operation of an autonomous vehicle on public roads until the manufacturer, as defined, submits an application to the Department of Motor Vehicles (DMV), as specified, and that application is approved. Existing law requires the department to adopt various specified regulations relating to autonomous vehicles, including, among others, testing, equipment, and performance standards that the department concludes are necessary to ensure the safe operation of autonomous vehicle on public roads.
Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles to report to the DMV any vehicle collision, traffic violation, or disengagement, as defined, or the assault or harassment of any passenger or safety driver, that involves a manufacturers vehicle in California regardless of whether the vehicle is in the testing or deployment phase. The bill would require these reports to contain specified information and to be submitted at the time the incident is identified by the manufacturer. The bill would require these reports to be submitted on a timeline adopted by the DMV that is required to be equal to or shorter than the reporting deadlines required by the federal National Highway Traffic Safety Administration. The bill would require the DMV, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, to create and publish an autonomous vehicle incident form and a form to allow for the aggregate analysis of autonomous vehicle safety by no later than July 1, 2025. The bill would require the DMV to publish all reports submitted pursuant to these provisions in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The bill would require the DMV to impose specified fines for violations of the reporting provisions and to suspend or revoke the testing and deployment permit of any manufacturer while an investigation of any violations is pending. The bill would also authorize members of the public or public entities with direct evidence of an incident to submit an autonomous vehicle incident report, as specified.
The bill would make related findings and declarations.
The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(3)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(4)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement occurs when the deactivation of a vehicles autonomous mode is needed, a human intervention is needed, or when the autonomous technology is not able to continue performing the dynamic driving task.
(2)Traffic citation means a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section, except for tickets issued for double parking that obstructs public transportation.
(3)Vehicle immobilization means a stop on a public road when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. A significant amount of time means at least 180 seconds, unless a shorter period of time is determined to be appropriate by the department.
(4)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision or disengagement that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is operating under a testing or deployment permit.
(c)An incident report related to a vehicle collision submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 30 seconds before a collision through the conclusion of the collision.
(2)The total number of passengers.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)The latitude and longitude coordinates of the collision with five decimal precision.
(9)The date and time of the collision in coordinated universal time format.
(10)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
(d)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall be, at minimum, submitted on an annual basis, unless the department establishes a more frequent timeline, and contain, at minimum, all of the following information:
(1)The latitude and longitude coordinates of the disengagement with five decimal precision.
(2)Whether the vehicle was operating with or without a test driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle safety driver, the remote operator, or a passenger.
(e)All collision reports submitted pursuant to subdivision (b) shall be submitted on the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(f)Commencing July 31, 2025, a manufacturer shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, vehicle immobilizations, and any traffic citations that have not been dismissed at the time of submission of the report.
(g)A summary report of vehicle miles traveled submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The county.
(5)The municipality.
(6)The month and year.
(7)The total vehicle miles traveled on public roads, broken down by county.
(8)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(9)The vehicle miles traveled on public roads when the vehicle was operated in autonomous mode and a test driver was present.
(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(h)A summary report of vehicle immobilizations submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The number of passengers.
(5)Road and weather conditions at the time of the vehicle immobilization.
(6)The latitude and longitude coordinates of the vehicle immobilization with five decimal precision.
(7)The date and time of the vehicle immobilization in coordinated universal time format.
(8)The total duration of the vehicle immobilization measured in seconds from the beginning of the vehicle immobilization to when the stop is resolved and the autonomous vehicle is no longer blocking the active travel lane.
(9)Whether the vehicle immobilization obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(10)A narrative description of the vehicle immobilization, including how the stop was resolved.
(i)A summary report of traffic violations that resulted in a citation and have not been dismissed, submitted pursuant to subdivision (f), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was the basis of the citation.
(2)The circumstances that led to the issuance of the citation.
(3)Any actions taken by the autonomous vehicle manufacturer to contest or accept the citation.
(4)Any justification offered for the citation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time of the violation.
(j)(1)Commencing July 1, 2025, the department shall maintain all reports submitted pursuant to this section and make the reports available upon request by local and state transportation authorities.
(2)Commencing January 1, 2028, the department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt.
(k)(1)Commencing January 1, 2028, the department shall redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing any report.
(2)The department may redact information on vehicles not owned or operated by a manufacturer.
(3)The department shall provide the relevant autonomous vehicle manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted pursuant to paragraph (1). A manufacturer bears the burden of proving the reasons why the department shall withhold any information, or any portion thereof, from the public. To request confidential treatment of information submitted to the department, a manufacturer must designate each page, section, or field, or any portion thereof, as confidential. If only a certain portion of information is claimed to be confidential, then only that portion rather than the entire submission should be designated as confidential.
(l)The department may establish additional reporting requirements for manufacturers for purposes of this section by regulation.
(m)The department may establish and assess fees to recover costs reasonably incurred by the department for implementing this section by regulation.
SEC. 2.5.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement occurs when the deactivation of a vehicles autonomous mode is needed, a human intervention is needed, or when the autonomous technology is not able to continue performing the dynamic driving task.
(2)Vehicle immobilization means a stop on a public road when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. A significant amount of time means at least 180 seconds, unless a shorter period of time is determined to be appropriate by the department.
(3)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision or disengagement that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is operating under a testing or deployment permit.
(c)An incident report related to a vehicle collision submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 30 seconds before a collision through the conclusion of the collision.
(2)The total number of passengers.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)The latitude and longitude coordinates of the collision with five decimal precision.
(9)The date and time of the collision in coordinated universal time format.
(10)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
(d)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall be, at minimum, submitted on an annual basis, unless the department establishes a more frequent timeline, and contain, at minimum, all of the following information:
(1)The latitude and longitude coordinates of the disengagement with five decimal precision.
(2)Whether the vehicle was operating with or without a test driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle safety driver, the remote operator, or a passenger.
(e)All collision reports submitted pursuant to subdivision (b) shall be submitted on the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(f)Commencing July 31, 2025, a manufacturer shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, vehicle immobilizations, and any notices of autonomous vehicle noncompliance, as defined in Section 38752, issued.
(g)A summary report of vehicle miles traveled submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The county.
(5)The municipality.
(6)The month and year.
(7)The total vehicle miles traveled on public roads, broken down by county.
(8)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(9)The vehicle miles traveled on public roads when the vehicle was operated in autonomous mode and a test driver was present.
(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(h)A summary report of vehicle immobilizations submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The number of passengers.
(5)Road and weather conditions at the time of the vehicle immobilization.
(6)The latitude and longitude coordinates of the vehicle immobilization with five decimal precision.
(7)The date and time of the vehicle immobilization in coordinated universal time format.
(8)The total duration of the vehicle immobilization measured in seconds from the beginning of the vehicle immobilization to when the stop is resolved and the autonomous vehicle is no longer blocking the active travel lane.
(9)Whether the vehicle immobilization obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(10)A narrative description of the vehicle immobilization, including how the stop was resolved.
(i)A summary report of notices of autonomous vehicle noncompliance issued, submitted pursuant to subdivision (f), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was the basis for the issuance of the notice.
(2)The circumstances that led to the issuance of the notice.
(3)Any actions taken by the autonomous vehicle manufacturer to contest or accept the notice.
(4)Any justification offered for the actions that resulted in the issuance of the notice.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time the notice was issued.
(j)(1)Commencing July 1, 2025, the department shall maintain all reports submitted pursuant to this section and make the reports available upon request by local and state transportation authorities.
(2)Commencing January 1, 2028, the department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt.
(k)(1)Commencing January 1, 2028, the department shall redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing any report.
(2)The department may redact information on vehicles not owned or operated by a manufacturer.
(3)The department shall provide the relevant autonomous vehicle manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted pursuant to paragraph (1). A manufacturer bears the burden of proving the reasons why the department shall withhold any information, or any portion thereof, from the public. To request confidential treatment of information submitted to the department, a manufacturer must designate each page, section, or field, or any portion thereof, as confidential. If only a certain portion of information is claimed to be confidential, then only that portion rather than the entire submission should be designated as confidential.
(l)The department may establish additional reporting requirements for manufacturers for purposes of this section by regulation.
(m)The department may establish and assess fees to recover costs reasonably incurred by the department for implementing this section by regulation.
SEC. 3.Section 2.5 of this bill incorporates additional conforming changes and references to Section 38752 of the Vehicle Code as proposed to be added by Assembly Bill 1777. That section of this bill shall only become operative if both bills are enacted and become effective on or before January 1, 2025, in which case Section 2 of this bill shall not become operative.
The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(3)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(4)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement means occurs when the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated. is needed, a human intervention is needed, or when the autonomous technology is not able to continue performing the dynamic driving task.
(2)Traffic citation means a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section, except for tickets issued for double parking that obstructs public transportation.
(3)Vehicle immobilization means a stop in an active traffic lane on a public road when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. The department shall have the discretion to define what qualifies as a significant amount of time up to a maximum of 180 seconds. A significant amount of time means at least 180 seconds, unless a shorter period of time is determined to be appropriate by the department.
(4)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision or disengagement that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is operating under a testing or deployment permit.
(c)An incident report related to a vehicle collision submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 30 seconds before a collision through the conclusion of the collision.
(2)The total number of passengers and any passenger interactions, if known by the manufacturer. passengers.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)The latitude and longitude coordinates of the collision with five decimal precision.
(9)The date and time of the collision in coordinated universal time format.
(10)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
(d)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall be be, at minimum, submitted on an annual basis and shall occur the period of December 1 of the current year to November 30, inclusive, of the following year basis, unless the department establishes a more frequent timeline, and contain, at minimum, all of the following information:
(1)The latitude and longitude coordinates of the disengagement with five decimal precision.
(2)Whether the vehicle was operating with or without a test driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test safety driver, the remote operator, or a passenger.
(e)All collision reports submitted pursuant to subdivision (b) shall be submitted on the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(f)Commencing July 31, 2025, a manufacturer that is testing autonomous vehicles pursuant to Article 3.7, or deploying autonomous vehicles pursuant to Article 3.8, of Chapter 1 of Division 1 of Title 13 of the California Code of Regulations, shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, vehicle immobilizations, and any traffic citations that have not been dismissed at the time of submission of the report.
(g)A summary report of vehicle miles traveled submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The county.
(5)The municipality.
(6)The month and year.
(7)The total vehicle miles traveled on public roads, broken down by county.
(8)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(9)The vehicle miles traveled on public roads when the vehicle was operated in autonomous mode and a test driver was present.
(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(h)A summary report of vehicle immobilizations submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The number of passengers.
(5)Road and weather conditions at the time of the vehicle immobilization.
(6)The latitude and longitude coordinates of the vehicle immobilization with five decimal precision.
(7)The date and time of the vehicle immobilization in coordinated universal time format.
(8)The total duration of the vehicle immobilization measured in seconds from the beginning of the vehicle immobilization to when the stop is resolved and the autonomous vehicle is no longer blocking the active travel lane.
(9)Whether the vehicle immobilization obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(10)A narrative description of the vehicle immobilization, including how the stop was resolved.
(i)A summary report of traffic violations that resulted in a citation and have not been dismissed, submitted pursuant to subdivision (f), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was the basis of the citation.
(2)The circumstances that led to the issuance of the citation.
(3)Any actions taken by the autonomous vehicle manufacturer to contest or accept the citation.
(4)Any justification offered for the citation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time of the violation.
(j)(1)Commencing July 1, 2025, the department shall maintain all reports submitted pursuant to this section in an electronic format as received by the manufacturer and make the reports available upon request by local and state transportation authorities.
(2)Commencing January 1, 2028, the department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt.
(k)(1)Commencing January 1, 2028, the department shall redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing any report.
(2)The department may redact information on vehicles not owned or operated by a manufacturer.
(3)The department shall provide the relevant autonomous vehicle manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted pursuant to paragraph (1). A manufacturer bears the burden of proving the reasons why the department shall withhold any information, or any portion thereof, from the public. To request confidential treatment of information submitted to the department, a manufacturer must designate each page, section, or field, or any portion thereof, as confidential. If only a certain portion of information is claimed to be confidential, then only that portion rather than the entire submission should be designated as confidential.
(l)The department may establish additional reporting requirements for manufacturers for purposes of this section by regulation.
(m)The department may establish and assess fees to recover costs reasonably incurred by the department for implementing this section by regulation.
SEC. 2.5.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement occurs when the deactivation of a vehicles autonomous mode is needed, a human intervention is needed, or when the autonomous technology is not able to continue performing the dynamic driving task.
(2)Vehicle immobilization means a stop on a public road when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. A significant amount of time means at least 180 seconds, unless a shorter period of time is determined to be appropriate by the department.
(3)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision or disengagement that occurs when a manufacturers vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is operating under a testing or deployment permit.
(c)An incident report related to a vehicle collision submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 30 seconds before a collision through the conclusion of the collision.
(2)The total number of passengers.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)The latitude and longitude coordinates of the collision with five decimal precision.
(9)The date and time of the collision in coordinated universal time format.
(10)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
(d)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall be, at minimum, submitted on an annual basis, unless the department establishes a more frequent timeline, and contain, at minimum, all of the following information:
(1)The latitude and longitude coordinates of the disengagement with five decimal precision.
(2)Whether the vehicle was operating with or without a test driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle safety driver, the remote operator, or a passenger.
(e)All collision reports submitted pursuant to subdivision (b) shall be submitted on the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(f)Commencing July 31, 2025, a manufacturer shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, vehicle immobilizations, and any notices of autonomous vehicle noncompliance, as defined in Section 38752, issued.
(g)A summary report of vehicle miles traveled submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The county.
(5)The municipality.
(6)The month and year.
(7)The total vehicle miles traveled on public roads, broken down by county.
(8)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(9)The vehicle miles traveled on public roads when the vehicle was operated in autonomous mode and a test driver was present.
(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(h)A summary report of vehicle immobilizations submitted pursuant to subdivision (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The number of passengers.
(5)Road and weather conditions at the time of the vehicle immobilization.
(6)The latitude and longitude coordinates of the vehicle immobilization with five decimal precision.
(7)The date and time of the vehicle immobilization in coordinated universal time format.
(8)The total duration of the vehicle immobilization measured in seconds from the beginning of the vehicle immobilization to when the stop is resolved and the autonomous vehicle is no longer blocking the active travel lane.
(9)Whether the vehicle immobilization obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(10)A narrative description of the vehicle immobilization, including how the stop was resolved.
(i)A summary report of notices of autonomous vehicle noncompliance issued, submitted pursuant to subdivision (f), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was the basis for the issuance of the notice.
(2)The circumstances that led to the issuance of the notice.
(3)Any actions taken by the autonomous vehicle manufacturer to contest or accept the notice.
(4)Any justification offered for the actions that resulted in the issuance of the notice.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)Whether a safety driver was present.
(8)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time the notice was issued.
(j)(1)Commencing July 1, 2025, the department shall maintain all reports submitted pursuant to this section and make the reports available upon request by local and state transportation authorities.
(2)Commencing January 1, 2028, the department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 90 days of receipt.
(k)(1)Commencing January 1, 2028, the department shall redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing any report.
(2)The department may redact information on vehicles not owned or operated by a manufacturer.
(3)The department shall provide the relevant autonomous vehicle manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted pursuant to paragraph (1). A manufacturer bears the burden of proving the reasons why the department shall withhold any information, or any portion thereof, from the public. To request confidential treatment of information submitted to the department, a manufacturer must designate each page, section, or field, or any portion thereof, as confidential. If only a certain portion of information is claimed to be confidential, then only that portion rather than the entire submission should be designated as confidential.
(l)The department may establish additional reporting requirements for manufacturers for purposes of this section by regulation.
(m)The department may establish and assess fees to recover costs reasonably incurred by the department for implementing this section by regulation.
SEC. 3.Section 2.5 of this bill incorporates additional conforming changes and references to Section 38752 of the Vehicle Code as proposed to be added by Assembly Bill 1777. That section of this bill shall only become operative if both bills are enacted and become effective on or before January 1, 2025, in which case Section 2 of this bill shall not become operative.
The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)The data collected by the DMV is inconsistent with the data provided to the federal National Highway Traffic Safety Administration by autonomous vehicle companies operating in California.(3)(2)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(4)(3)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(5)(4)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement means the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
(2)Traffic citation includes, but is not limited to, means a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section. section, except for tickets issued for double parking that obstructs public transportation.
(3)Unplanned stop Vehicle immobilization means a stop in a roadway for a minimum of 90 seconds when the conditions on the road require traffic flow. an active traffic lane when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger. passenger or goods. The department shall have the discretion to define what qualifies as a significant amount of time up to a maximum of 180 seconds.
(4)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision, traffic citation, or disengagement, collision or disengagement that occurs when a manufacturers vehicle is operating in autonomous mode in California. on California public roads. These reports shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is in the testing or deployment phase. operating under a testing or deployment permit.
(c)An incident report related to a vehicle collisions collision submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 90 30 seconds before a collision to when the involved vehicles leave the scene or first responders arrive on scene. through the conclusion of the collision.
(2)The total number of passengers and any passenger interactions. interactions, if known by the manufacturer.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)Information related to the performance of the autonomous vehicle system, including whether the autonomous technology was engaged within 30 seconds of the collision, precollision movement and speed, and narrative description.(6)Injury and property damage details.(7)(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(8)(6)The vehicle identification number, or other identifying information if the vehicle identification number is not available, number of the autonomous vehicle.
(9)The license plate number of the autonomous vehicle.(10)(7)Whether a test safety driver was present.
(11)(8)The latitude and longitude coordinates of the collision with five decimal precision.
(12)(9)The date and time of the collision in coordinated universal time format.
(13)(10)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personally identifiable personal information.
(d)An incident report related to a traffic citation submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:(1)The specific state or local traffic law or regulation that was violated.(2)The circumstances that led to the violation.(3)Any actions taken by the autonomous vehicle or other involved parties to contest or accept the violation.(4)Any justification offered for the violation.(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.(6)The vehicle identification number of the autonomous vehicle.(7)The license plate number of the autonomous vehicle.(8)Whether a safety driver was present.(9)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time of the violation.(e)(d)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall be submitted on an annual basis and shall occur the period of December 1 of the current year to November 30, inclusive, of the following year and contain, but is not limited to, at minimum, all of the following information:
(1)The location at which the disengagement occurred, including whether the location was an interstate, freeway, highway, rural road, or street. latitude and longitude coordinates of the disengagement with five decimal precision.
(2)Whether the vehicle was operating with or without a test driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test driver, the remote operator, or a passenger.
(f)(1)(e)All collision reports submitted pursuant to subdivision (b) shall be submitted on the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(2)If an incident related to a vehicle collision results in a fatality or any individual being transported to a hospital from the scene for medical treatment, or involves a vulnerable road user, the report shall be submitted within one calendar day.(3)If an incident related to a vehicle collision results in a vehicle being towed or air bag deployment, the report shall be submitted within five calendar days.(4)If the autonomous technology was engaged 30 seconds before a collision, the report shall be submitted within 45 calendar days.(g)(f)Commencing July 31, 2025, a manufacturer of autonomous vehicles that is testing autonomous vehicles pursuant to Article 3.7, or deploying autonomous vehicles pursuant to Article 3.8, of Chapter 1 of Division 1 of Title 13 of the California Code of Regulations, shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, unplanned stops, wheelchair-accessible services, and traffic violations that resulted in a traffic citation and vehicle immobilizations, and any traffic citations that have not been dismissed at the time of submission of the report.
(h)(g)A summary report of vehicle miles traveled submitted pursuant to subdivision (g) (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle. number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The license plate number of the autonomous vehicle.(5)(4)The county.
(6)(5)The municipality.
(7)(6)The month and year.
(8)(7)The total vehicle miles traveled on public roads. roads, broken down by county.
(9)(8)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(10)(9)The vehicle miles traveled on public roads when the vehicle was controlled by the autonomous technology and a safety operated in autonomous mode and a test driver was present.
(11)(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(i)(h)A summary report of unplanned stops vehicle immobilizations submitted pursuant to subdivision (g) (f) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle. number of the autonomous vehicle operating on California public roads during the reporting period.
(4)The license plate number of the autonomous vehicle.(5)Whether the automated technology was engaged 30 seconds before the unplanned stop.(6)(4)The number of passengers.
(7)Whether a test driver was present at the time of the unplanned stop.(8)(5)Road and weather conditions at the time of the unplanned stop. vehicle immobilization.
(9)The type of location where the unplanned stop occurred, including, but not limited to, an interstate, freeway, highway, rural road, or street.(6)The latitude and longitude coordinates of the vehicle immobilization with five decimal precision.
(10)(7)The date and time of the unplanned stop vehicle immobilization in coordinated universal time format.
(11)(8)The total duration of the unplanned stop vehicle immobilization measured in seconds from the beginning of the stop vehicle immobilization to when the stop is resolved and the autonomous vehicle is no longer blocking the public right-of-way. active travel lane.
(12)(9)Whether the unplanned stop vehicle immobilization obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(13)A description of the cause of the unplanned stop.(14)A description of how the unplanned stop was resolved, including whether the vehicle drove away or was removed by the autonomous technology, a remote operator, or a tow truck.(15)The unplanned stop identification number.(16)(10)A narrative description of the unplanned stop, vehicle immobilization, including how the unplanned stop was resolved.
(j)(i)A summary report of traffic violations that resulted in a citation and have not been dismissed, submitted pursuant to subdivision (g), (f), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was violated. the basis of the citation.
(2)The circumstances that led to the violation. issuance of the citation.
(3)Any actions taken by the autonomous vehicle or other involved parties manufacturer to contest or accept the violation. citation.
(4)Any justification offered for the violation. citation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number, or other identifying information if the vehicle identification number is not available, number of the autonomous vehicle.
(7)The license plate number of the autonomous vehicle.(8)(7)Whether a test safety driver was present.
(9)Whether a test driver, remote operator, or the automated driving system was in control of the vehicle at the time of the violation.(k)The(j)(1)Commencing July 1, 2025, the department shall maintain all reports submitted pursuant to this section in an electronic format as received by the manufacturer and make the reports available upon request by local and state transportation authorities.
(2)Commencing January 1, 2028, the department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 30 90 days of receipt. The reports published pursuant to this subdivision shall not be redacted in any capacity except to remove identifiable personal information of any passengers or drivers.
(l)The department may suspend or revoke the manufacturers testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.(k)(1)Commencing January 1, 2028, the department shall redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the autonomous vehicle manufacturer prior to releasing any report.
(2)The department may redact information on vehicles not owned or operated by a manufacturer.
(3)The department shall provide the relevant autonomous vehicle manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted pursuant to paragraph (1). A manufacturer bears the burden of proving the reasons why the department shall withhold any information, or any portion thereof, from the public. To request confidential treatment of information submitted to the department, a manufacturer must designate each page, section, or field, or any portion thereof, as confidential. If only a certain portion of information is claimed to be confidential, then only that portion rather than the entire submission should be designated as confidential.
The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)The data collected by the DMV is inconsistent with the data provided to the federal National Highway Traffic Safety Administration by autonomous vehicle companies operating in California.
(3)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(4)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(5)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement means the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
(2)Traffic violation citation includes, but is not limited to, a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section.
(3)Unplanned stop means a stop in a roadway for a minimum of 90 seconds when the conditions on the road require traffic flow. It does not include a stop intended to pick up or drop off a passenger.
(4)Vulnerable road user includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders or occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision, traffic violation, citation, or disengagement, or a barrier to access or incident of discrimination for a passenger with a disability, that involves occurs when a manufacturers vehicle is operating in autonomous mode in California. These reports shall be submitted by the manufacturer using the forms described in subdivision (l) and shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is in the testing or deployment phase.
(c)An incident report related to vehicle collisions submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 90 seconds before a collision to when the involved vehicles leave the scene or first responders arrive on scene.
(2)The total number of passengers and any passenger interactions.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)Information related to the performance of the autonomous vehicle system, including whether the autonomous technology was engaged within 30 seconds of the collision, precollision movement and speed, telematics data, and narrative description.
(6)Injury and property damage details.
(7)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(8)The vehicle identification number number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle.
(9)The license plate number of the autonomous vehicle.
(10)Whether a safety test driver was present.
(11)The latitude and longitude coordinates of the collision with five decimal precision.
(12)A timestamp The time of the collision in coordinated universal time format.
(13)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personally identifiable information.
(d)An incident report related to a traffic violation citation submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was violated.
(2)The circumstances that led to the violation.
(3)Any actions taken by the autonomous vehicle or other involved parties to contest or accept the violation.
(4)Any justification offered for the violation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)The license plate number of the autonomous vehicle.
(8)Whether a safety driver was present.
(9)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time of the violation.
(e)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:
(1)The location at which the disengagement occurred, including whether the location was an interstate, freeway, highway, rural road, street, or parking facility. or street.
(2)Whether the vehicle was operating with or without a driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test driver, the remote operator, or a passenger.
(f)An incident report related to an incident of discrimination or a barrier to access for a passenger with a disability submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:(1)The date, time, and location of the incident and the vehicle identification number or license plate of the autonomous vehicle.(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.(3)Anonymized information about the passengers disability and any accommodations requested by the passenger, whether the requested accommodation was provided, and whether the passenger completed the trip requested.(4)Any complaints or grievances, with the passengers name redacted, filed by the passenger about the autonomous vehicle service and the outcome of the complaint or grievance.(g)(f)(1)All reports submitted pursuant to subdivision (b) shall be submitted on a timeline the timelines adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(2)If an incident related to a vehicle collision results in a fatality or serious injury, any individual being transported to a hospital from the scene for medical treatment, or involves a vulnerable road user, the report shall be submitted within one calendar day.
(3)If an incident related to a vehicle collision results in a vehicle being towed or air bag deployment, the report shall be submitted within five calendar days.
(4)If the autonomous technology was engaged 30 seconds before a collision, the report shall be submitted within 30 45 calendar days.
(h)(g)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, unplanned stops, and wheelchair-accessible services. services, and traffic violations that resulted in a traffic citation and have not been dismissed at the time of submission of the report.
(i)(h)A summary report of vehicle miles traveled submitted pursuant to subdivision (h) (g) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle.
(4)The license plate number of the autonomous vehicle.
(5)The county.
(6)The municipality.
(7)The month and year.
(8)The total vehicle miles traveled. traveled on public roads.
(9)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(10)The vehicle miles traveled on public roads when the vehicle was controlled by the autonomous technology and a safety driver was present.
(11)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(j)(i)A summary report of unplanned stops submitted pursuant to subdivision (h) (g) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle.
(4)The license plate number of the autonomous vehicle.
(5)Whether the automated technology was engaged 30 seconds before the unplanned stop.
(6)The number of passengers.
(7)Whether a safety test driver was present at the time of the unplanned stop.
(8)Road and weather conditions at the time of the unplanned stop.
(9)The type of location where the unplanned stop occurred, including, but not limited to, an interstate, freeway, highway, rural road, or parking facility. street.
(10)A timestamp The time of the unplanned stop in coordinated universal time format.
(11)The total duration of the unplanned stop measured in seconds from the beginning of the stop to when the stop is resolved and the autonomous vehicle is no longer blocking the public right-of-way.
(12)Whether the unplanned stop obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(13)A description of the cause of the unplanned stop.
(14)A description of how the unplanned stop was resolved, including whether the vehicle drove away or was removed by the autonomous technology, a remote operator, or a tow truck.
(15)The unplanned stop identification number.
(16)A narrative description of the unplanned stop. stop, including how the unplanned stop was resolved.
(k)A summary report of wheelchair-accessible services submitted pursuant to subdivision (h) shall include, but is not limited to, all of the following information:(1)The number of wheelchair-accessible autonomous vehicles in operation and the number of nonwheelchair-accessible autonomous vehicles in operation.(2)The number of wheelchair-accessible autonomous vehicle trips requested by the public and the number of nonwheelchair-accessible autonomous vehicle trips requested by the public.(3)The number of wheelchair-accessible autonomous vehicle trips accepted, canceled, and completed, and the number of nonwheelchair-accessible autonomous vehicle trips accepted, canceled, and completed.(4)The average wait time for a wheelchair-accessible autonomous vehicle and the average wait time for a nonwheelchair-accessible autonomous vehicle.(5)The service area for wheelchair-accessible autonomous vehicles and the service area for nonwheelchair-accessible autonomous vehicles.(l)The department, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, shall create and publish the following forms by no later than July 1, 2025:(1)An autonomous vehicle incident form for the reporting of autonomous vehicle incidents required by subdivision (b).(2)A form for the reporting of data required by subdivision (h).(j)A summary report of traffic violations that resulted in a citation and have not been dismissed, submitted pursuant to subdivision (g), shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was violated.
(2)The circumstances that led to the violation.
(3)Any actions taken by the autonomous vehicle or other involved parties to contest or accept the violation.
(4)Any justification offered for the violation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number, or other identifying information if the vehicle identification number is not available, of the autonomous vehicle.
(7)The license plate number of the autonomous vehicle.
(8)Whether a test driver was present.
(9)Whether a test driver, remote operator, or the automated driving system was in control of the vehicle at the time of the violation.
(m)(k)The department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The reports published pursuant to this subdivision shall not be redacted in any capacity except to remove identifiable personal information of any passengers or drivers.
(n)The department and the Public Utilities Commission shall post on their respective internet websites all relevant information about autonomous vehicle permit applications and approvals, including, but not limited to, the geographic extent of the operational design domain, the hours of operation, fleet size, permitted weather conditions, facility types, and operating speeds. If a permit is suspended or altered in any way, the department and the Public Utilities Commission shall post the new permit conditions and cause or basis for the change.(o)(1)The department may impose a fine of up to twenty-six thousand three hundred fifteen dollars ($26,315) per day for a violation of this section and may impose a fine of up to one hundred thirty-one million five hundred sixty-four thousand one hundred eighty-three dollars ($131,564,183) for a related series of violations, consistent with the Second Amended Standing General Order 202101 of the federal NHTSA. A false report submitted under this section shall constitute a violation of this section.(2)The department shall establish a fine structure with a multiplier for subsequent violations.(3)(l)The department may suspend or revoke the manufacturers testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
(p)(1)Members of the public or public entities with direct evidence of an incident may submit a true and accurate autonomous vehicle incident report covering an autonomous vehicle.(2)The department shall determine if the submission is credible and notify the submitting party of the departments determination within 30 days of receiving the report.(3)If the submission is deemed credible, the department shall give the manufacturer of the autonomous vehicle identified in the report 30 days to investigate and respond. The manufacturer shall either inform the department that it disputes the veracity of the report, with evidence to support its determination, or provide the manufacturers own incident report.(4)The department shall notify the submitting party of any response by the manufacturer.(5)Notwithstanding subdivision (m), a report submitted pursuant to this subdivision shall only be published after the department receives a response by the manufacturer pursuant to paragraph (3). Disputed reports shall be published in a separate manner that clearly notes the dispute.(6)Reports that are not deemed credible by the department shall not be published.The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)The data collected by the DMV is inconsistent with the data provided to the federal National Highway Traffic Safety Administration by autonomous vehicle companies operating in California.
(3)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(4)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(5)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver, that involves a manufacturers vehicle in California. These reports shall be submitted at the time the incident is identified by the manufacturer using the forms described in subdivision (g) and shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is in the testing or deployment phase.(b)An incident report related to vehicle collisions submitted pursuant to this section shall include, but is not limited to, all of the following information:(1)A detailed narrative of the collision, including any relevant precollision and postcollision information.(2)The cause of the collision.(3)Any passenger interactions.(4)The road and traffic conditions at the time of the collision.(5)Any interactions with road users or obstacles on the road.(6)Vehicle performance data.(7)Injury and property damage details.(8)The status of the autonomous vehicles technology at the time of the collision.(9)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA).(c)An incident report related to a traffic violation submitted pursuant to this section shall contain, but is not limited to, all of the following information:(1)The specific traffic law or regulation that was violated, including any official record of an issued traffic violation or citation.(2)The circumstances that led to the violation.(3)Any actions taken by the autonomous vehicle or other involved parties in response to the violation.(4)Any justification offered for the violation.(d)An incident report related to autonomous vehicle disengagements submitted pursuant to this section shall contain, but is not limited to, all of the following information:(1)The location at which the disengagement occurred, including whether the location was an interstate, freeway, highway, rural road, street, or parking facility.(2)Whether the vehicle was operating with or without a driver at the time of the disengagement.(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test driver, the remote operator, or a passenger.(e)(1)An incident report related to assault and harassment, both sexual and nonsexual, that involved passengers or safety drivers.(2)Disclosures under this subdivision shall include a detailed description of the incident, including the nature of the assault or harassment, the approximate ages and gender identities of the parties to the incident, how the manufacturer addressed the incident, and any changes to company policies or protocol that will be made in response to the incident.(3)Disclosures under this subdivision shall be made without compromising the privacy and confidentiality of the individuals involved. All such disclosures shall comply with applicable privacy laws and regulations.(f)All reports submitted pursuant to this section shall be submitted on a timeline adopted by the department that shall be equal to or shorter than the reporting deadlines required by the federal NHTSA.(g)The department, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, shall create and publish the following forms by no later than July 1, 2025:(1)An autonomous vehicle incident form for the reporting of autonomous vehicle incidents required by subdivisions (b) to (e), inclusive.(2)A form to collect data for the aggregate analysis of autonomous vehicle safety.(h)The department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The reports published pursuant to this subdivision shall be anonymized to remove identifiable personal information of any passengers or drivers.(i)(1)The department shall impose a fine of no less than twenty-six thousand three hundred fifteen dollars ($26,315) per day for a violation of this section and shall impose a fine of up to one hundred thirty-one million five hundred sixty-four thousand one hundred eighty-three dollars ($131,564,183) for a related series of violations, consistent with the Second Amended Standing General Order 202101 of the federal NHTSA. A false report submitted under this section shall constitute a violation of this section.(2)The department shall establish a fine structure with a multiplier for subsequent violations.(3)The department shall suspend or revoke the manufacturers testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.(j)(1)Members of the public or public entities with direct evidence of an incident may submit a true and accurate autonomous vehicle incident report covering an autonomous vehicle.(2)The department shall determine if the submission is credible and notify the submitting party of the departments determination within 30 days of receiving the report.(3)If the submission is deemed credible, the department shall give the manufacturer of the autonomous vehicle identified in the report 30 days to investigate and respond. The manufacturer shall either inform the department that it disputes the veracity of the report, with evidence to support its determination, or provide the manufacturers own incident report.(4)The department shall notify the submitting party of any response by the manufacturer.(5)Notwithstanding subdivision (h), a report submitted pursuant to this subdivision shall only be published after the department receives a response by the manufacturer pursuant to paragraph (3). Disputed reports shall be published in a separate manner that clearly notes the dispute.(6)Reports that are not deemed credible by the department shall not be published.(k)For the purposes of this section, disengagement means the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)For purposes of this section, the following definitions apply:
(1)Disengagement means the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
(2)Traffic violation includes, but is not limited to, a violation of this code and a violation of a local ordinance adopted pursuant to this code.
(3)Unplanned stop means a stop in a roadway for a minimum of 90 seconds when the conditions on the road require traffic flow. It does not include a stop intended to pick up or drop off a passenger.
(b)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision, traffic violation, or disengagement, or a barrier to access or incident of discrimination for a passenger with a disability, that involves a manufacturers vehicle in California. These reports shall be submitted by the manufacturer using the forms described in subdivision (l) and shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is in the testing or deployment phase.
(c)An incident report related to vehicle collisions submitted pursuant to subdivision (b) shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information. Relevant precollision and postcollision information includes activity from 90 seconds before a collision to when the involved vehicles leave the scene or first responders arrive on scene.
(2)The total number of passengers and any passenger interactions.
(3)The road and traffic conditions at the time of the collision.
(4)Any interactions with road users or obstacles on the road.
(5)Information related to the performance of the autonomous vehicle system, including whether the autonomous technology was engaged within 30 seconds of the collision, precollision movement and speed, telematics data, and narrative description.
(6)Injury and property damage details.
(7)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(8)The vehicle identification number of the autonomous vehicle.
(9)The license plate number of the autonomous vehicle.
(10)Whether a safety driver was present.
(11)The latitude and longitude coordinates of the collision with five decimal precision.
(12)A timestamp of the collision in coordinated universal time format.
(13)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personally identifiable information.
(d)An incident report related to a traffic violation submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:
(1)The specific state or local traffic law or regulation that was violated.
(2)The circumstances that led to the violation.
(3)Any actions taken by the autonomous vehicle or other involved parties to contest or accept the violation.
(4)Any justification offered for the violation.
(5)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(6)The vehicle identification number of the autonomous vehicle.
(7)The license plate number of the autonomous vehicle.
(8)Whether a safety driver was present.
(9)Whether a safety driver, remote operator, or the automated technology was in control of the vehicle at the time of the violation.
(e)An incident report related to autonomous vehicle disengagements submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:
(1)The location at which the disengagement occurred, including whether the location was an interstate, freeway, highway, rural road, street, or parking facility.
(2)Whether the vehicle was operating with or without a driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test driver, the remote operator, or a passenger.
(f)An incident report related to an incident of discrimination or a barrier to access for a passenger with a disability submitted pursuant to subdivision (b) shall contain, but is not limited to, all of the following information:
(1)The date, time, and location of the incident and the vehicle identification number or license plate of the autonomous vehicle.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)Anonymized information about the passengers disability and any accommodations requested by the passenger, whether the requested accommodation was provided, and whether the passenger completed the trip requested.
(4)Any complaints or grievances, with the passengers name redacted, filed by the passenger about the autonomous vehicle service and the outcome of the complaint or grievance.
(g)(1)All reports submitted pursuant to subdivision (b) shall be submitted on a timeline adopted by the department that shall not exceed the reporting deadlines required by the federal NHTSA.
(2)If an incident results in a fatality or serious injury, or involves a vulnerable road user, the report shall be submitted within one calendar day.
(3)If an incident results in a vehicle being towed or air bag deployment, the report shall be submitted within five calendar days.
(4)If the autonomous technology was engaged 30 seconds before a collision, the report shall be submitted within 30 calendar days.
(h)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall submit to the department quarterly reports summarizing in tabular format all reports that were submitted pursuant to subdivision (b) in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled, unplanned stops, and wheelchair-accessible services.
(i)A summary report of vehicle miles traveled submitted pursuant to subdivision (h) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle.
(4)The license plate number of the autonomous vehicle.
(5)The county.
(6)The municipality.
(7)The month and year.
(8)The total vehicle miles traveled.
(9)The vehicle miles traveled when the vehicle was controlled by a safety driver or remote operator.
(10)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was present.
(11)The vehicle miles traveled when the vehicle was controlled by the autonomous technology and a safety driver was not present.
(j)A summary report of unplanned stops submitted pursuant to subdivision (h) shall include, but is not limited to, all of the following information:
(1)The manufacturer.
(2)The permit number for the testing or deployment permit issued by the department and the Public Utilities Commission for the autonomous vehicle, if applicable.
(3)The vehicle identification number of the autonomous vehicle.
(4)The license plate number of the autonomous vehicle.
(5)Whether the automated technology was engaged 30 seconds before the unplanned stop.
(6)The number of passengers.
(7)Whether a safety driver was present at the time of the unplanned stop.
(8)Road and weather conditions at the time of the unplanned stop.
(9)The type of location where the unplanned stop occurred, including, but not limited to, an interstate, freeway, highway, rural road, or parking facility.
(10)A timestamp of the unplanned stop in coordinated universal time format.
(11)The duration of the unplanned stop measured in seconds from the beginning of the stop to when the stop is resolved and the autonomous vehicle is no longer blocking the public right-of-way.
(12)Whether the unplanned stop obstructed a general-purpose lane, transit-only lane, bike lane, intersection, rail track, an emergency response vehicle, or an emergency response scene.
(13)A description of the cause of the unplanned stop.
(14)A description of how the unplanned stop was resolved, including whether the vehicle drove away or was removed by the autonomous technology, a remote operator, or a tow truck.
(15)The unplanned stop identification number.
(16)A narrative description of the unplanned stop.
(k)A summary report of wheelchair-accessible services submitted pursuant to subdivision (h) shall include, but is not limited to, all of the following information:
(1)The number of wheelchair-accessible autonomous vehicles in operation and the number of nonwheelchair-accessible autonomous vehicles in operation.
(2)The number of wheelchair-accessible autonomous vehicle trips requested by the public and the number of nonwheelchair-accessible autonomous vehicle trips requested by the public.
(3)The number of wheelchair-accessible autonomous vehicle trips accepted, canceled, and completed, and the number of nonwheelchair-accessible autonomous vehicle trips accepted, canceled, and completed.
(4)The average wait time for a wheelchair-accessible autonomous vehicle and the average wait time for a nonwheelchair-accessible autonomous vehicle.
(5)The service area for wheelchair-accessible autonomous vehicles and the service area for nonwheelchair-accessible autonomous vehicles.
(l)The department, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, shall create and publish the following forms by no later than July 1, 2025:
(1)An autonomous vehicle incident form for the reporting of autonomous vehicle incidents required by subdivision (b).
(2)A form for the reporting of data required by subdivision (h).
(m)The department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The reports published pursuant to this subdivision shall not be redacted in any capacity except to remove identifiable personal information of any passengers or drivers.
(n)The department and the Public Utilities Commission shall post on their respective internet websites all relevant information about autonomous vehicle permit applications and approvals, including, but not limited to, the geographic extent of the operational design domain, the hours of operation, fleet size, permitted weather conditions, facility types, and operating speeds. If a permit is suspended or altered in any way, the department and the Public Utilities Commission shall post the new permit conditions and cause or basis for the change.
(o)(1)The department may impose a fine of up to twenty-six thousand three hundred fifteen dollars ($26,315) per day for a violation of this section and may impose a fine of up to one hundred thirty-one million five hundred sixty-four thousand one hundred eighty-three dollars ($131,564,183) for a related series of violations, consistent with the Second Amended Standing General Order 202101 of the federal NHTSA. A false report submitted under this section shall constitute a violation of this section.
(2)The department shall establish a fine structure with a multiplier for subsequent violations.
(3)The department may suspend or revoke the manufacturers testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
(p)(1)Members of the public or public entities with direct evidence of an incident may submit a true and accurate autonomous vehicle incident report covering an autonomous vehicle.
(2)The department shall determine if the submission is credible and notify the submitting party of the departments determination within 30 days of receiving the report.
(3)If the submission is deemed credible, the department shall give the manufacturer of the autonomous vehicle identified in the report 30 days to investigate and respond. The manufacturer shall either inform the department that it disputes the veracity of the report, with evidence to support its determination, or provide the manufacturers own incident report.
(4)The department shall notify the submitting party of any response by the manufacturer.
(5)Notwithstanding subdivision (m), a report submitted pursuant to this subdivision shall only be published after the department receives a response by the manufacturer pursuant to paragraph (3). Disputed reports shall be published in a separate manner that clearly notes the dispute.
(6)Reports that are not deemed credible by the department shall not be published.
The Legislature finds and declares all of the following:
(a)Since 2013, the Department of Motor Vehicles (DMV) has been considering the implications of testing and deploying autonomous vehicles on California roads.
(b)The DMV convened workshops, public hearings, and ultimately adopted regulations in 2018.
(c)These regulations served as a starting point for data collection during the testing of autonomous vehicles. However, updates to the law are necessary to ensure that critical data is collected by the state for all of the following reasons:
(1)During the workshops, public hearings, and regulation drafting process, the DMV primarily considered autonomous vehicle deployment for personal vehicle use. In more recent years, the autonomous vehicle industry has pivoted rapidly toward the ride hailing industry and other autonomous vehicle services.
(2)The data collected by the DMV is inconsistent with the data provided to the federal National Highway Traffic Safety Administration by autonomous vehicle companies operating in California.
(3)Currently, the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.
(4)In recent months, driverless vehicles have shut down and blocked intersections or have caused gridlock and obstructed emergency vehicles.
(5)There is a public interest in the highest level of transparency as the state determines the level and extent of the deployment of autonomous vehicles.
(d)Thus, a statutory minimum is essential to ensure that the need for innovation is met with public transparency and safety.
SEC. 2.Section 38760 is added to the Vehicle Code, immediately following Section 38755, to read:38760.(a)Commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver, that involves a manufacturers vehicle in California. These reports shall be submitted at the time the incident is identified by the manufacturer using the forms described in subdivision (g) and shall apply to all autonomous vehicles permitted by the department, regardless of whether the vehicle is in the testing or deployment phase.
(b)An incident report related to vehicle collisions submitted pursuant to this section shall include, but is not limited to, all of the following information:
(1)A detailed narrative of the collision, including any relevant precollision and postcollision information.
(2)The cause of the collision.
(3)Any passenger interactions.
(4)The road and traffic conditions at the time of the collision.
(5)Any interactions with road users or obstacles on the road.
(6)Vehicle performance data.
(7)Injury and property damage details.
(8)The status of the autonomous vehicles technology at the time of the collision.
(9)Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA).
(c)An incident report related to a traffic violation submitted pursuant to this section shall contain, but is not limited to, all of the following information:
(1)The specific traffic law or regulation that was violated, including any official record of an issued traffic violation or citation.
(2)The circumstances that led to the violation.
(3)Any actions taken by the autonomous vehicle or other involved parties in response to the violation.
(4)Any justification offered for the violation.
(d)An incident report related to autonomous vehicle disengagements submitted pursuant to this section shall contain, but is not limited to, all of the following information:
(1)The location at which the disengagement occurred, including whether the location was an interstate, freeway, highway, rural road, street, or parking facility.
(2)Whether the vehicle was operating with or without a driver at the time of the disengagement.
(3)A description of the facts and circumstances of the disengagement, including weather conditions, road surface conditions, traffic conditions, construction, emergencies, or collisions. The description shall be written in plain language with enough detail that a nontechnical person can understand the circumstances triggering the disengagement. The report shall identify the party that initiated the vehicles disengagement, including the vehicles autonomous technology, the autonomous vehicle test driver, the remote operator, or a passenger.
(e)(1)An incident report related to assault and harassment, both sexual and nonsexual, that involved passengers or safety drivers.
(2)Disclosures under this subdivision shall include a detailed description of the incident, including the nature of the assault or harassment, the approximate ages and gender identities of the parties to the incident, how the manufacturer addressed the incident, and any changes to company policies or protocol that will be made in response to the incident.
(3)Disclosures under this subdivision shall be made without compromising the privacy and confidentiality of the individuals involved. All such disclosures shall comply with applicable privacy laws and regulations.
(f)All reports submitted pursuant to this section shall be submitted on a timeline adopted by the department that shall be equal to or shorter than the reporting deadlines required by the federal NHTSA.
(g)The department, in consultation with the Department of the California Highway Patrol, the Public Utilities Commission, and any other public entity it deems necessary, shall create and publish the following forms by no later than July 1, 2025:
(1)An autonomous vehicle incident form for the reporting of autonomous vehicle incidents required by subdivisions (b) to (e), inclusive.
(2)A form to collect data for the aggregate analysis of autonomous vehicle safety.
(h)The department shall publish all reports submitted pursuant to this section in an electronic, open, and machine-readable format on the departments internet website within 30 days of receipt. The reports published pursuant to this subdivision shall be anonymized to remove identifiable personal information of any passengers or drivers.
(i)(1)The department shall impose a fine of no less than twenty-six thousand three hundred fifteen dollars ($26,315) per day for a violation of this section and shall impose a fine of up to one hundred thirty-one million five hundred sixty-four thousand one hundred eighty-three dollars ($131,564,183) for a related series of violations, consistent with the Second Amended Standing General Order 202101 of the federal NHTSA. A false report submitted under this section shall constitute a violation of this section.
(2)The department shall establish a fine structure with a multiplier for subsequent violations.
(3)The department shall suspend or revoke the manufacturers testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
(j)(1)Members of the public or public entities with direct evidence of an incident may submit a true and accurate autonomous vehicle incident report covering an autonomous vehicle.
(2)The department shall determine if the submission is credible and notify the submitting party of the departments determination within 30 days of receiving the report.
(3)If the submission is deemed credible, the department shall give the manufacturer of the autonomous vehicle identified in the report 30 days to investigate and respond. The manufacturer shall either inform the department that it disputes the veracity of the report, with evidence to support its determination, or provide the manufacturers own incident report.
(4)The department shall notify the submitting party of any response by the manufacturer.
(5)Notwithstanding subdivision (h), a report submitted pursuant to this subdivision shall only be published after the department receives a response by the manufacturer pursuant to paragraph (3). Disputed reports shall be published in a separate manner that clearly notes the dispute.
(6)Reports that are not deemed credible by the department shall not be published.
(k)For the purposes of this section, disengagement means the deactivation of a vehicles autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
|
Date
|
Status
|
|---|---|
| Sep 27, 2024 | Vetoed by Governor. |
| Sep 6, 2024 | Enrolled and presented to the Governor at 4 p.m. |
| Aug 28, 2024 | Senate amendments concurred in. To Engrossing and Enrolling. (Ayes 65. Noes 4.). |
| Aug 28, 2024 | Assembly Rule 77 suspended. |
| Aug 28, 2024 | In Assembly. Concurrence in Senate amendments pending. May be considered on or after August 30 pursuant to Assembly Rule 77. |
| Aug 27, 2024 | Read third time. Passed. Ordered to the Assembly. (Ayes 30. Noes 7.). |
| Aug 26, 2024 | Read second time. Ordered to third reading. |
| Aug 23, 2024 | Read third time and amended. Ordered to second reading. |
| Aug 19, 2024 | Read second time. Ordered to third reading. |
| Aug 15, 2024 | Read second time and amended. Ordered returned to second reading. |
| Aug 15, 2024 | From committee: Amend, and do pass as amended. (Ayes 5. Noes 2.) (August 15). |
| Aug 12, 2024 | In committee: Referred to APPR suspense file. |
| Aug 5, 2024 | In committee: Hearing postponed by committee. |
| Jun 26, 2024 | Re-referred to Com. on APPR. |
| Jun 26, 2024 | Withdrawn from committee. |
| Jun 26, 2024 | From committee: Do pass and re-refer to Com. on E., U. & C. (Ayes 11. Noes 2.) (June 25). Re-referred to Com. on E., U. & C. |
| Jun 12, 2024 | From committee chair, with author's amendments: Amend, and re-refer to committee. Read second time, amended, and re-referred to Com. on TRANS. |
| Jun 5, 2024 | In committee: Set, first hearing. Hearing canceled at the request of author. |
| Jun 5, 2024 | Referred to Coms. on TRANS. and E., U. & C. |
| May 23, 2024 | In Senate. Read first time. To Com. on RLS. for assignment. |
| May 22, 2024 | Read third time. Passed. Ordered to the Senate. (Ayes 61. Noes 3. Page 5525.) |
| May 20, 2024 | Read second time. Ordered to third reading. |
| May 16, 2024 | From committee: Do pass. (Ayes 12. Noes 3.) (May 16). |
| May 16, 2024 | Joint Rule 62(a), file notice suspended. (Page 5215.) |
| May 15, 2024 | In committee: Set, first hearing. Referred to APPR. suspense file. |
| Apr 25, 2024 | From committee: Do pass and re-refer to Com. on APPR. (Ayes 10. Noes 1.) (April 24). Re-referred to Com. on APPR. |
| Apr 17, 2024 | Re-referred to Com. on C. & C. |
| Apr 16, 2024 | From committee chair, with author's amendments: Amend, and re-refer to Com. on C. & C. Read second time and amended. |
| Apr 16, 2024 | From committee: Do pass and re-refer to Com. on C. & C. (Ayes 12. Noes 1.) (April 15). Re-referred to Com. on C. & C. |
| Mar 18, 2024 | Referred to Coms. on TRANS. and C. & C. |
| Feb 17, 2024 | From printer. May be heard in committee March 18. |
| Feb 16, 2024 | Read first time. To print. |
|
Date
|
Description
|
Location
|
Votes
|
|
|---|---|---|---|---|
| Aug 28, 2024 | AB 3061 Haney Concurrence in Senate Amendments | Assembly Floor |
Passed |
|
| Aug 27, 2024 | Assembly 3rd Reading AB3061 Haney et al. By Cortese | Senate Floor |
Passed |
|
| Aug 15, 2024 | Do pass as amended | Senate Standing Committee on Appropriations |
Passed |
|
| Aug 12, 2024 | Placed on suspense file | Senate Standing Committee on Appropriations |
Passed |
|
| Jun 25, 2024 | Do pass, but first be re-referred to the Committee on [Energy, Utilities and Communications] | Senate Standing Committee on Transportation |
Passed |
|
| May 22, 2024 | AB 3061 Haney Assembly Third Reading | Assembly Floor |
Passed |
|
| May 16, 2024 | Do pass. | Assembly Standing Committee on Appropriations |
Passed |
|
| Apr 24, 2024 | Do pass and be re-referred to the Committee on [Appropriations] | Assembly Standing Committee on Communications and Conveyance |
Passed |
|
| Apr 15, 2024 | Do pass and be re-referred to the Committee on [Communications and Conveyance] | Assembly Standing Committee on Transportation |
Passed |
This list shows positions taken on this bill by organizations on the date displayed, which is linked to the original source.
Positions by individuals are not included.
|
Organization
|
Position
|
Date
|
|---|---|---|
| Alliance For Automotive Innovation | ** Against | |
| Autonomous Vehicle Industry Association | ** Against | |
| California Conference Board Of The Amalgamated Transit Union | ** Support | |
| California Conference Of Machinists | ** Support | |
| California Labor Federation, Afl-Cio | ** Support | |
| California Low-Income Consumer Coalition | ** Support | |
| California Manufacturers & Technology Association | ** Against | |
| California Professional Firefighters | ** Support | |
| California School Employees Association | ** Support | |
| California Teamsters Public Affairs Council | ** Support | |
| Chamber Of Progress | ** Against | |
| Consumer Attorneys Of California | ** Support | |
| Consumer Federation Of California | ** Support | |
| Consumers For Auto Reliability & Safety | ** Support | |
| Consumer Watchdog | ** Support | |
| Cupertino Chamber of Commerce | ** Against | |
| Engineers and Scientists of California, IFPTE Local 20, AFL-CIO | ** Support | |
| Mission Street Neighbors | ** Support | |
| Mountain View Chamber of Commerce | ** Against | |
| Public Law Center | ** Support | |
| San Francisco County Transportation Authority | ** Support | |
| San Francisco Taxi Workers Alliance | ** Support | |
| SMART - Transportation Division | ** Support | |
| Technet | ** Against | |
| Tesla Inc. | ** Against | |
| UNITE-HERE, AFL-CIO | ** Support | |
| Utility Workers Union of America, AFL-CIO | ** Support | |
| volvo group north america | ** Against |
GOVERNOR'S VETO
GV Bill Id:AB 3061
Author:(Haney)
As Enrolled Ver:August 31, 2024
2/3 vote
SUMMARY
Requires the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California starting July 31, 2025.
Senate Amendments
- Remove the requirement for AV manufacturers to report barrier to access or incidents of discrimination for passengers with disabilities.
- Remove the requirement for DMV and the California Public Utilities Commission (CPUC) to post all relevant information about AV permit applications and approvals on their websites.
- Remove the authority for DMV to impose a fine for failure to report data to DMV.
- Remove the authority for members of the public to submit incident reports to DMV and require DMV to investigate such reports.
- Remove reporting requirements for disengagements that occur on parking facilities.
- Remove the requirement for all traffic citations to be reported to DMV and instead requires reporting on traffic citations that have not been dismissed by the court by the time the quarterly report to DMV is due.
- Remove the requirement for a fatality collision to be reported in a single day and collisions that result in air bag deployment or a tow within five days and instead align the reporting requirements with reporting deadlines established by the National Highway Traffic Safety Administration (NHTSA).
- Authorize DMV to establish and assess fees to recover costs reasonably incurred by the department to implement this bill.
- Clarify that DMV may establish additional reporting requirements for manufacturers beyond what is permitted by this bill.
- Incorporate chaptering out amendments for AB 1777 (Ting).
- Make other, technical, clarifying changes.
Governor's Veto Message
Beginning July 31, 2025, this bill would require autonomous vehicle manufacturers to report specific data related to collisions and disengagements to the Department of Motor Vehicles (DMV). Additionally, manufacturers would need to submit quarterly summaries on vehicle miles traveled, vehicle immobilizations, and traffic citations. The bill also mandates that the DMV publish these reports online within 90 days of receipt.
While I support the intent of this bill to enhance the safety and transparency of autonomous vehicle operations, the timeline it imposes is infeasible for the DMV to implement these new requirements and address the associated operational challenges involved. The DMV recently released a new set of draft regulations, which are open for public input until October 14, 2024, to address many of the concerns raised in this bill. Stakeholders will be able to provide input and contribute to the rulemaking process informally and through the notice and comment processes outlined in the Administrative Procedures Act.
My Administration remains open to working with the Legislature on future legislation that complements and builds upon existing and proposed regulatory requirements. It is essential that such proposals are practical, enhance clarity, and do not duplicate existing efforts, which will ultimately further compliance and public safety.
COMMENTS
DMV actions under this bill: DMV currently has limited tools to penalize AV companies violating its AV regulations, and is limited to suspending operation. DMV can suspend permits for failure to report data to DMV. This year an AV company lost its testing permit for failure to report disengagement data to DMV.
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and better mirrors existing NHSTA reporting requirements.
This includes data regarding crashes during the testing and deployment phases, not just the testing phase as required by existing DMV regulations.
Unclear if AVs are safer than humans. According to a RAND Corporation report Driving to Safety: How Many Miles of Driving Would it Take to Demonstrate Autonomous Vehicle Reliability, it may take decades before we know if AVs are safer than human drivers. Despite tens of thousands of deaths on the road every year, humans are capable of driving a remarkable number of miles without collisions. Americans drive 3 trillion miles every year. In 2013, there were 2.3 million injuries reported, a rate of 77 injuries per 100 million miles driven. The 32,719 deaths from car crashes that year correspond to a rate of about one fatality per 100 million miles driven. AVs have not driven anywhere near that many miles, and already at least one person has been killed by an AV in Tempe, Arizona.
AV companies often cite a report from the National Transportation Safety Board (NTSB) that concluded that 94% of all collisions are because of human error, and because of that AVs have the potential to save tens of thousands of lives. According to the Insurance Institute for Highway Safety (IIHS), "It is likely that fully self-driving cars will eventually identify hazards better than people, but we found that this alone would not prevent the bulk of crashes." IIHS estimates that only a third of the collisions caused by human error would be expected to be avoided because AVs will potentially have more accurate perceptions than human drivers and are not vulnerable to incapacitation. Avoiding the other two-thirds would require AVs that are programmed to prioritize safety over speed and convenience."
AVs performance and reporting in California. Most AV testing and deployment in California has occurred in San Francisco. In January 2023, the San Francisco County Transportation Authority asked the California Public Utilities Commission to reject Waymo's request to allow commercial deployment throughout the city. The letter notes a series of 9-1-1 calls that the city had received. The letter states "Managers in the City's Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or a Cruise AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours. Additional incidents were posted on social media or reported by the media. The number of reported incidents is likely a fraction of the total unplanned stops because most are reported during late night hours when few people are on the streets to notice them and because many people would not think to call 9-1-1 in these circumstances….Unfortunately, the AV failure incidents reported by the public have been significantly concentrated on streets of great importance in the City's transportation network: downtown streets, streets with transit service, streets on the bike network, intersections, and streets on the City's High Injury Network (the 12% of San Francisco streets that account for more than 68% of severe or fatal injury crashes)."
The incidents described by San Francisco were only known to them because of 9-1-1 calls and were not reported to DMV because DMV only requires disengagement reports for vehicles with a testing permit, but not a deployment permit. Companies also do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations, allowing AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
The Cruise LLC vehicles involved in these incidents had a DMV deployment permit at the time of the incidents. To get this permit, a company must self-certify that the "autonomous technology is designed to detect and respond to roadway situations in compliance with all provisions of the California Vehicle Code and local regulation applicable to the performance of the dynamic driving task in the vehicle's operational design domain, except when necessary to enhance the safety of the vehicle's occupants and/ or other road users." Despite the incidents of Cruise LLC vehicles documented by San Francisco above, Cruise LLC had received approval from DMV to expand their hours of service operation, increase their allowable speed, and test a vehicle incapable of being operated by a human operator. In addition, Cruise still has a pending application for approval for use by the NHSTA.
CPUC later approved Cruise LLC to operate for profit in San Francisco on August 10, 2023. Within a week a Cruise LLC vehicle crashed into a San Francisco Fire Department truck. A day later Cruise voluntarily reduced its fleet by 50% in the city. On October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Under DMV regulations, Cruise was not required to report this collision to DMV because it was operating on a deployment permit. DMV however, did follow up with Cruise based on media reports of the incident. DMV suspended Cruise's permit 24 days after an incident when they discovered Cruise had not shared with them the entirety of the video of the incident. The video showed the Cruise vehicle had come to a complete stop after the crash but then proceeded to drive over and drag the pedestrian. Cruise had stopped the video after the vehicle had come to a stop, but before the vehicle resumed to run over the pedestrian.
According to the Author
"AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe."
Arguments in Support
The California Teamsters, the co-sponsor of this bill, argue "Our union represents workers across the supply chain that frequently interact with AVs. Teamster members have seen firsthand how this technology is often imperfect, glitches, or fails to work appropriately. Likewise, driverless vehicles have made headlines for inuring pedestrians, shutting down and blocking intersections, causing gridlock, and obstructing emergency vehicles. There is a strong public interest in transparency.
Updates to the law are necessary to ensure that critical data is collected by the state as there are holes in the current regulations for data collection. Under AB 3061, a manufacturer of an autonomous vehicle must report to the DMV any collision, traffic violation, disengagement, assault, or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California. All reports must be published online in an accessible readable format within 30 days of receipt. AB 3061 imposes fines for failure to report or false reporting, in addition to suspension or revocation of the manufacturer testing or deployment permit."
Arguments in Opposition
According to the Autonomous Vehicle Industry Association, "The proposed reporting structure would create significant costs for industry and for the DMV. As the bill analysis states, AB 3061 will create "significant one-time and ongoing costs for the DMV, likely in the millions of dollars one-time and, to a lesser extent, millions of dollars ongoing." The bill would therefore exacerbate the fiscal pressures on the Motor Vehicle Account, which, according to the Legislative Analyst's Office (LAO), is expected to fully exhaust its reserves and become insolvent in fiscal year 2025-26. The LAO further warns that the MVA, absent corrective action, such as revenue increases or spending reductions, will experience a negative fund balance of $1.4 billion in fiscal year 2028-29.
We believe that AV technology will dramatically increase safety on California roads, and that California should continue to support safety-enhancing policies and competition.
FISCAL COMMENTS
According to Senate Appropriations Committee:
"DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department's website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])"
VOTES
ASM TRANSPORTATION: 12-1-2
YES: Wilson, Davies, Aguiar-Curry, Juan Carrillo, Hart, Jackson, Lowenthal, Papan, Ting, Wallis, Ward, Wicks
NO: Hoover
ABS, ABST OR NV: Berman, Sanchez
ASM COMMUNICATIONS AND CONVEYANCE: 10-1-0
YES: Boerner, Jim Patterson, Bonta, Davies, Garcia, Holden, Maienschein, Stephanie Nguyen, Luz Rivas, Rodriguez
NO: Hoover
ASM APPROPRIATIONS: 12-3-0
YES: Wicks, Arambula, Bryan, Calderon, Wendy Carrillo, Mike Fong, Grayson, Haney, Hart, Jim Patterson, Pellerin, Villapudua
NO: Sanchez, Dixon, Ta
ASSEMBLY FLOOR: 61-3-16
YES: Addis, Aguiar-Curry, Alanis, Alvarez, Arambula, Bauer-Kahan, Bennett, Boerner, Bonta, Bryan, Juan Carrillo, Wendy Carrillo, Chen, Connolly, Davies, Mike Fong, Gabriel, Garcia, Gipson, Grayson, Haney, Hart, Irwin, Jackson, Jones-Sawyer, Kalra, Lackey, Lee, Low, Lowenthal, Maienschein, McCarty, McKinnor, Muratsuchi, Stephanie Nguyen, Ortega, Pacheco, Papan, Jim Patterson, Pellerin, Petrie-Norris, Quirk-Silva, Ramos, Rendon, Reyes, Rodriguez, Blanca Rubio, Santiago, Schiavo, Soria, Ting, Valencia, Waldron, Wallis, Ward, Weber, Wicks, Wilson, Wood, Zbur, Robert Rivas
NO: Dixon, Vince Fong, Hoover
ABS, ABST OR NV: Bains, Berman, Calderon, Cervantes, Megan Dahle, Essayli, Flora, Friedman, Gallagher, Holden, Mathis, Joe Patterson, Luz Rivas, Sanchez, Ta, Villapudua
SENATE FLOOR: 31-7-2
YES: Allen, Archuleta, Ashby, Atkins, Becker, Blakespear, Bradford, Caballero, Cortese, Dodd, Durazo, Eggman, Glazer, Gonzalez, Hurtado, Laird, Limón, McGuire, Menjivar, Min, Newman, Padilla, Portantino, Roth, Rubio, Skinner, Smallwood-Cuevas, Stern, Umberg, Wahab, Wiener
NO: Alvarado-Gil, Dahle, Grove, Jones, Niello, Seyarto, Wilk
ABS, ABST OR NV: Nguyen, Ochoa Bogh
ASSEMBLY FLOOR: 65-4-10
YES: Addis, Aguiar-Curry, Alanis, Alvarez, Arambula, Bauer-Kahan, Bennett, Berman, Boerner, Bonta, Bryan, Calderon, Juan Carrillo, Wendy Carrillo, Chen, Connolly, Davies, Mike Fong, Friedman, Gabriel, Garcia, Gipson, Grayson, Haney, Hart, Holden, Irwin, Jackson, Jones-Sawyer, Kalra, Lackey, Lee, Low, Lowenthal, Maienschein, McCarty, McKinnor, Muratsuchi, Stephanie Nguyen, Pacheco, Papan, Jim Patterson, Pellerin, Petrie-Norris, Quirk-Silva, Ramos, Rendon, Reyes, Luz Rivas, Rodriguez, Blanca Rubio, Santiago, Schiavo, Soria, Ting, Valencia, Waldron, Wallis, Ward, Weber, Wicks, Wilson, Wood, Zbur, Robert Rivas
NO: Megan Dahle, Dixon, Essayli, Hoover
ABS, ABST OR NV: Bains, Cervantes, Flora, Gallagher, Mathis, Ortega, Joe Patterson, Sanchez, Ta, Villapudua
UPDATED
VERSION: August 31, 2024
CONSULTANT: David Sforza / TRANS. / (916) 319-2093 FN: 0005153
CONCURRENCE IN SENATE AMENDMENTS
CSA1 Bill Id:AB 3061
Author:(Haney)
As Amended Ver:August 23, 2024
Majority vote
SUMMARY
Requires the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California starting July 31, 2025.
Senate Amendments
- Remove the requirement for AV manufacturers to report barrier to access or incidents of discrimination for passengers with disabilities.
- Remove the requirement for DMV and the California Public Utilities Commission (CPUC) to post all relevant information about AV permit applications and approvals on their websites.
- Remove the authority for DMV to impose a fine for failure to report data to DMV.
- Remove the authority for members of the public to submit incident reports to DMV and require DMV to investigate such reports.
- Remove reporting requirements for disengagements that occur on parking facilities.
- Remove the requirement for all traffic citations to be reported to DMV and instead requires reporting on traffic citations that have not been dismissed by the court by the time the quarterly report to DMV is due.
- Remove the requirement for a fatality collision to be reported in a single day and collisions that result in air bag deployment or a tow within five days and instead align the reporting requirements with reporting deadlines established by the National Highway Traffic Safety Administration (NHTSA).
- Authorize DMV to establish and assess fees to recover costs reasonably incurred by the department to implement this bill.
- Clarify that DMV may establish additional reporting requirements for manufacturers beyond what is permitted by this bill.
- Incorporate chaptering out amendments for AB 1777 (Ting).
- Make other, technical, clarifying changes.
COMMENTS
DMV actions under this bill: DMV currently has limited tools to penalize AV companies violating its AV regulations, and is limited to suspending operation. DMV can suspend permits for failure to report data to DMV. This year an AV company lost its testing permit for failure to report disengagement data to DMV.
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and better mirrors existing NHSTA reporting requirements.
This includes data regarding crashes during the testing and deployment phases, not just the testing phase as required by existing DMV regulations.
Unclear if AVs are safer than humans. According to a RAND Corporation report Driving to Safety: How Many Miles of Driving Would it Take to Demonstrate Autonomous Vehicle Reliability, it may take decades before we know if AVs are safer than human drivers. Despite tens of thousands of deaths on the road every year, humans are capable of driving a remarkable number of miles without collisions. Americans drive 3 trillion miles every year. In 2013, there were 2.3 million injuries reported, a rate of 77 injuries per 100 million miles driven. The 32,719 deaths from car crashes that year correspond to a rate of about one fatality per 100 million miles driven. AVs have not driven anywhere near that many miles, and already at least one person has been killed by an AV in Tempe, Arizona.
AV companies often cite a report from the National Transportation Safety Board (NTSB) that concluded that 94% of all collisions are because of human error, and because of that AVs have the potential to save tens of thousands of lives. According to the Insurance Institute for Highway Safety (IIHS), "It is likely that fully self-driving cars will eventually identify hazards better than people, but we found that this alone would not prevent the bulk of crashes." IIHS estimates that only a third of the collisions caused by human error would be expected to be avoided because AVs will potentially have more accurate perceptions than human drivers and are not vulnerable to incapacitation. Avoiding the other two-thirds would require AVs that are programmed to prioritize safety over speed and convenience."
AVs performance and reporting in California. Most AV testing and deployment in California has occurred in San Francisco. In January 2023, the San Francisco County Transportation Authority asked the California Public Utilities Commission to reject Waymo's request to allow commercial deployment throughout the city. The letter notes a series of 9-1-1 calls that the city had received. The letter states "Managers in the City's Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or a Cruise AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours. Additional incidents were posted on social media or reported by the media. The number of reported incidents is likely a fraction of the total unplanned stops because most are reported during late night hours when few people are on the streets to notice them and because many people would not think to call 9-1-1 in these circumstances….Unfortunately, the AV failure incidents reported by the public have been significantly concentrated on streets of great importance in the City's transportation network: downtown streets, streets with transit service, streets on the bike network, intersections, and streets on the City's High Injury Network (the 12% of San Francisco streets that account for more than 68% of severe or fatal injury crashes)."
The incidents described by San Francisco were only known to them because of 9-1-1 calls and were not reported to DMV because DMV only requires disengagement reports for vehicles with a testing permit, but not a deployment permit. Companies also do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations, allowing AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
The Cruise LLC vehicles involved in these incidents had a DMV deployment permit at the time of the incidents. To get this permit, a company must self-certify that the "autonomous technology is designed to detect and respond to roadway situations in compliance with all provisions of the California Vehicle Code and local regulation applicable to the performance of the dynamic driving task in the vehicle's operational design domain, except when necessary to enhance the safety of the vehicle's occupants and/ or other road users." Despite the incidents of Cruise LLC vehicles documented by San Francisco above, Cruise LLC had received approval from DMV to expand their hours of service operation, increase their allowable speed, and test a vehicle incapable of being operated by a human operator. In addition, Cruise still has a pending application for approval for use by the NHSTA.
CPUC later approved Cruise LLC to operate for profit in San Francisco on August 10, 2023. Within a week a Cruise LLC vehicle crashed into a San Francisco Fire Department truck. A day later Cruise voluntarily reduced its fleet by 50% in the city. On October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Under DMV regulations, Cruise was not required to report this collision to DMV because it was operating on a deployment permit. DMV however, did follow up with Cruise based on media reports of the incident. DMV suspended Cruise's permit 24 days after an incident when they discovered Cruise had not shared with them the entirety of the video of the incident. The video showed the Cruise vehicle had come to a complete stop after the crash but then proceeded to drive over and drag the pedestrian. Cruise had stopped the video after the vehicle had come to a stop, but before the vehicle resumed to run over the pedestrian.
According to the Author
"AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe."
Arguments in Support
The California Teamsters, the co-sponsor of this bill, argue "Our union represents workers across the supply chain that frequently interact with AVs. Teamster members have seen firsthand how this technology is often imperfect, glitches, or fails to work appropriately. Likewise, driverless vehicles have made headlines for inuring pedestrians, shutting down and blocking intersections, causing gridlock, and obstructing emergency vehicles. There is a strong public interest in transparency.
Updates to the law are necessary to ensure that critical data is collected by the state as there are holes in the current regulations for data collection. Under AB 3061, a manufacturer of an autonomous vehicle must report to the DMV any collision, traffic violation, disengagement, assault, or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California. All reports must be published online in an accessible readable format within 30 days of receipt. AB 3061 imposes fines for failure to report or false reporting, in addition to suspension or revocation of the manufacturer testing or deployment permit."
Arguments in Opposition
According to the Autonomous Vehicle Industry Association, "The proposed reporting structure would create significant costs for industry and for the DMV. As the bill analysis states, AB 3061 will create "significant one-time and ongoing costs for the DMV, likely in the millions of dollars one-time and, to a lesser extent, millions of dollars ongoing." The bill would therefore exacerbate the fiscal pressures on the Motor Vehicle Account, which, according to the Legislative Analyst's Office (LAO), is expected to fully exhaust its reserves and become insolvent in fiscal year 2025-26. The LAO further warns that the MVA, absent corrective action, such as revenue increases or spending reductions, will experience a negative fund balance of $1.4 billion in fiscal year 2028-29.
We believe that AV technology will dramatically increase safety on California roads, and that California should continue to support safety-enhancing policies and competition.
FISCAL COMMENTS
According to Senate Appropriations Committee:
"DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department's website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])"
VOTES:
ASM TRANSPORTATION: 12-1-2
YES: Wilson, Davies, Aguiar-Curry, Juan Carrillo, Hart, Jackson, Lowenthal, Papan, Ting, Wallis, Ward, Wicks
NO: Hoover
ABS, ABST OR NV: Berman, Sanchez
ASM COMMUNICATIONS AND CONVEYANCE: 10-1-0
YES: Boerner, Jim Patterson, Bonta, Davies, Garcia, Holden, Maienschein, Stephanie Nguyen, Luz Rivas, Rodriguez
NO: Hoover
ASM APPROPRIATIONS: 12-3-0
YES: Wicks, Arambula, Bryan, Calderon, Wendy Carrillo, Mike Fong, Grayson, Haney, Hart, Jim Patterson, Pellerin, Villapudua
NO: Sanchez, Dixon, Ta
ASSEMBLY FLOOR: 61-3-16
YES: Addis, Aguiar-Curry, Alanis, Alvarez, Arambula, Bauer-Kahan, Bennett, Boerner, Bonta, Bryan, Juan Carrillo, Wendy Carrillo, Chen, Connolly, Davies, Mike Fong, Gabriel, Garcia, Gipson, Grayson, Haney, Hart, Irwin, Jackson, Jones-Sawyer, Kalra, Lackey, Lee, Low, Lowenthal, Maienschein, McCarty, McKinnor, Muratsuchi, Stephanie Nguyen, Ortega, Pacheco, Papan, Jim Patterson, Pellerin, Petrie-Norris, Quirk-Silva, Ramos, Rendon, Reyes, Rodriguez, Blanca Rubio, Santiago, Schiavo, Soria, Ting, Valencia, Waldron, Wallis, Ward, Weber, Wicks, Wilson, Wood, Zbur, Robert Rivas
NO: Dixon, Vince Fong, Hoover
ABS, ABST OR NV: Bains, Berman, Calderon, Cervantes, Megan Dahle, Essayli, Flora, Friedman, Gallagher, Holden, Mathis, Joe Patterson, Luz Rivas, Sanchez, Ta, Villapudua
SENATE FLOOR: 31-7-2
YES: Allen, Archuleta, Ashby, Atkins, Becker, Blakespear, Bradford, Caballero, Cortese, Dodd, Durazo, Eggman, Glazer, Gonzalez, Hurtado, Laird, Limón, McGuire, Menjivar, Min, Newman, Padilla, Portantino, Roth, Rubio, Skinner, Smallwood-Cuevas, Stern, Umberg, Wahab, Wiener
NO: Alvarado-Gil, Dahle, Grove, Jones, Niello, Seyarto, Wilk
ABS, ABST OR NV: Nguyen, Ochoa Bogh
UPDATED
VERSION: August 23, 2024
CONSULTANT: David Sforza / TRANS. / (916) 319-2093 FN: 0004829
SENATE RULES COMMITTEE Office of Senate Floor Analyses (916) 651-1520 Fax: (916) 327-4478 | AB 3061 |
THIRD READING
Bill No: AB 3061
Author: Haney (D), et al.
Amended: 8/23/24 in Senate
Vote: 21
SENATE TRANSPORTATION COMMITTEE: 11-2, 6/25/24
AYES: Cortese, Allen, Archuleta, Becker, Blakespear, Dodd, Gonzalez, Laird, Limón, Newman, Umberg
NOES: Niello, Seyarto
NO VOTE RECORDED: Dahle, Nguyen
SENATE APPROPRIATIONS COMMITTEE: 5-2, 8/15/24
AYES: Caballero, Ashby, Becker, Bradford, Wahab
NOES: Jones, Seyarto
ASSEMBLY FLOOR: 61-3, 5/22/24 - See last page for vote
SUBJECT: Vehicles: autonomous vehicle incident reporting
SOURCE: Author
DIGEST:
This bill requires, commencing July 31, 2025, a manufacturer of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) a vehicle collision, traffic citation, or disengagement, as defined, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California. It also requires quarterly reports on vehicle miles traveled (VMT), vehicle immobilizations, and traffic citations, as specified, and allows DMV to establish additional reporting requirements via regulation and assess fees for implementation costs.
Senate Floor Amendments of 8/23/24 (1) make technical changes to improve definitions; (2) specify information and timelines for inclusion in reports; (3) authorize the establishment of additional reporting requirements and fees; and (4) incorporate chaptering out language to avoid issues with AB 1777 (Ting, 2024).
ANALYSIS:
Existing law:
- Authorizes the operation of AVs on public roads for testing purposes under certain circumstances specified in DMV regulations (Vehicle Code Section (VEH) 38750).
- Defines “autonomous vehicle” to mean vehicle equipped with technology that makes it capable of operation that meets the definition of Levels 3, 4, or 5 of the Society of Automotive Engineers (SAE) International's Taxonomy and Testing of Autonomous Vehicles Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (APR 2021).
- Defines “autonomous technology” to mean technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator.
- States that an AV does not include a vehicle that is equipped with one or more collision avoidance systems, including, but not limited to, electronic blind spot assistance, automated emergency braking systems, park assist, adaptive cruise control, lane keep assist, lane departure warning, traffic jam and queuing assist, or other similar systems that enhance safety or provide driver assistance, but are not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator.
- Prohibits the operation of AVs on public roads for non-testing purposes unless the manufacturer of the vehicles submits an application to DMV that is approved pursuant to DMV regulations.
- Requires DMV to approve an application submitted by a manufacturer for the operation of AVs for non-testing purposes if DMV finds that the applicant has submitted all information and completed testing necessary to satisfy that the AVs are safe to operate on public roads and the applicant has complied with all requirements specified in DMV regulations.
- Authorizes DMV to impose additional requirements it deems necessary to ensure the safe operation of AVs if those vehicles are capable of operating without the presence of a driver inside the vehicle.
- Requires AV manufacturers to have a testing or deployment permit to operate an autonomous vehicle in California.
- Restricts the testing and deployment of autonomous vehicles to vehicles under 10,001 pounds and excludes motorcycles.
- Authorizes both the testing and deployment of AVs without a human operator inside the vehicle.
- Requires an AV with a testing permit (but not a deployment permit) to report collisions to DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if they have a testing permit.
- Requires AVs with a testing permit (but not a deployment permit) to report disengagements on an annual basis.
- Requires AVs or level 2 advanced driver assistance systems to report crashes within five calendar days.
This bill:
- The Legislature makes findings and declarations as specified.
- Establishes definitions:
- “Disengagement” occurs when the deactivation of a vehicle’s autonomous mode is needed, a human intervention is needed, or when the autonomous technology is not able to continue performing the dynamic driving task.
- “Traffic citation” means a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section, except for tickets issued for double parking that obstructs public transportation.
- “Vehicle Immobilization” means a stop on a public road when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. “A significant amount of time” means at least 180 seconds, unless a shorter period of time is determined to be appropriate by the department.
- “Vulnerable road user” includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders of occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
- Requires, commencing July 31, 2025, that a manufacturer of autonomous vehicles shall report to the DMV a vehicle collision or disengagement that occurs when a manufacturer’s vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the DMV, regardless of whether the vehicle is operating under a testing or deployment permit.
- Requires that an incident report related to a vehicle collision submitted under this bill to include, but is not limited to, all of the following information:
- A detailed narrative of the collision, including any relevant precollision and postcollision information, as specified.
- The total number of passengers.
- The road and traffic conditions at the time of the collision.
- Any interactions with road users or obstacles in the road.
- The permit number for the testing or deployment permit issued by the DMV and the California Public Utilities Commission (CPUC) for the AV, if applicable.
- The vehicle identification number.
- Whether a safety driver was present.
- The latitude and longitude coordinates of the collision, as specified.
- The date and time of the collision, as specified.
- Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
- Requires that an incident report related to AV disengagements under this bill be submitted on an annual basis, unless the department establishes a more frequent timeline, and contain, at minimum, all of the following information:
- The latitude and longitude coordinates of the disengagement, as specified.
- Whether the vehicle was operating with or without a test driver at the time of the disengagement.
- A description of the facts and circumstances of the disengagement, as specified.
- Requires all collision reports submitted pursuant to this bill be submitted on the timelines adopted by the DMV that do not exceed the reporting deadlines required by NHTSA.
- Requires, commencing July 31, 2025, a manufacturer of AVs to submit quarterly reports to the DMV summarizing in tabular format of all reports that were submitted pursuant to this bill in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled (VMT), vehicle immobilizations, and any traffic citations that have not been dismissed at the time of submission of the report.
- Requires that a summary report of VMT pursuant to this bill be submitted to DMV, including information as specified.
- Requires that a summary report of vehicle immobilizations pursuant to this bill be submitted to DMV, including information as specified.
- Requires that a summary report of traffic violations that resulted in a citation and have not been dismissed pursuant to this bill be submitted to DMV, including information as specified.
- Requires, commencing July 1, 2025, the DMV to maintain all reports submitted pursuant to this bill and make the reports available upon request by local and state transportation authorities.
- Requires, commencing January 1, 2028, the DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine readable format on the DMV’s internet website within 90 days of receipt.
- Requires, commencing January 1, 2028, the department to redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the AV manufacturer prior to releasing any report.
- The DMV may redact information on vehicles not owned or operated by the manufacturer.
- The DMV shall provide the relevant AV manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted, as specified.
- Allows the department to establish additional reporting requirement for manufacturers of AVs by regulation.
- Allows the department to establish and assess fees to recover costs reasonably incurred by the department for implementation.
- Contains provisions to avoid chaptering out issues under the circumstance that both this bill and AB 1777 (Ting, 2024) are enacted.
Comments
- Purpose of the bill. According to the author, “AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.”
- DMV and AVs. In 2012, the Legislature passed SB 1298 (Padilla), which permitted AVs to operate on public roads for testing by a driver under certain conditions. In 2014, the DMV established regulations to authorize the testing of AVs with gross vehicle weights (GVWs) of less than 10,001 pounds (e.g. light duty AVs) with safety drivers. In 2018, the DMV established regulations to authorize testing of light-duty AVs without safety drivers. In 2022, the DMV established regulations to authorize the deployment of light-duty AVs without safety drivers. Layered on top of the DMV process is approval by the CPUC. Though not required as part of the 2012 legislation, the CPUC has been involved as a second layer of approval for light-duty AVs. This is because the AVs are carrying fare-paying passengers and the CPUC has the duty to ensure passenger safety. Unless specified in a new statute, the CPUC would have no role in the approval of AV trucks.
The DMV testing process appears relatively thorough though reliant on reporting and self-assessment. Before an AV is allowed on a public road with a safety driver, the manufacturer must apply for a permit where they demonstrate that they have validated the technology. The safety driver must be properly trained and enrolled in the DMV’s commercial driver program that tracks driver safety and revokes the license of unsafe drivers (pull-notice program). Evidence of financial responsibility (e.g. insurance) by the manufacturer is required. Extensive reporting by the AV manufacturer is required including all collisions and disengagements of the AV system. As of April 2024, 35 companies are authorized to test with a safety driver.
To test an AV without a safety driver the DMV looks at the performance of the manufacturer when testing with a safety driver. A real-time communication link between the AV and a remote operator must be maintained. A plan for interacting with law enforcement must be created, which is reviewed by the California Highway Patrol. As of April 2024, six companies are authorized to test without a safety driver.
To obtain final approval to deploy, the AV the manufacturer must identify the geographic location and conditions under which the AV will operate, certify compliance with all applicable Federal Motor Vehicle Safety standards, equip the vehicle with data recorders, which capture all vehicle functions, and provide other safety-related certifications. As of January 2024, three companies are authorized to operate autonomously without a driver in specified locations and conditions: Mercedes-Benz, Nuro, and Waymo.
- Deployment and reporting. Most AV testing and deployment in California has occurred in San Francisco. In a January 2023 letter, the San Francisco County Transportation Authority asked the CPUC to reject Waymo’s request to allow commercial deployment throughout the city. The letter highlights a series of 9-1-1 calls that the city had received stating, “Managers in the City’s Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or an AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours.”
The incidents described above were only known to San Francisco officials because of these 9-1-1 calls. These incidents were not reported to DMV because it only requires disengagement reports for vehicles with a testing permit. Reporting to DMV is further limited because AV companies do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations. This allows AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
In addition to these incidents not being reported to DMV, on October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Cruise was not required to report this collision to DMV because it was operating on a deployment permit.
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and more closely follows existing NHSTA reporting requirements. This includes data regarding crashes and traffic citations during the testing and deployment phases, not just the testing phase as required by existing DMV regulations. It also requires AV companies in the deployment and testing phase to report to DMV on unplanned stops and disengagements which have been noted as points of concern by San Francisco officials. This bill further gives the DMV the authority to suspend or revoke the testing or deployment permit of a manufacturer if an investigation is pending for a violation of the new reporting requirements.
- AV safety, promises versus realities. According to the Bureau of Transportation Statistics over 32,000 people are killed in crashes on United States roads every year. The National Transportation Safety Board (NTSB) reports that more than 90% of crashes are caused by human errors. AVs have the potential to significantly mitigate this public health crisis, as AVs are never drunk, distracted, or tired. Their performance should also be better than human drivers because of their better perception (ie. no blind spots), better decision making (ie. more-accurate planning of driving maneuvers), and better execution (ie. faster and more precise control of acceleration, braking, and steering). However, AVs are not perfect. For instance, inclement weather and complex driving environments pose challenges for AVs and human drivers, and a study of Google’s AVs found they performed worse than human drivers in some of these cases. There is also the potential for AVs to pose new crash risks like crashes resulting from cyber-attacks.
In short, AVs can be safer than vehicles operated by humans, but additional engineering is needed to prevent specific blind spots that may currently lead to roadway incidents, accidents, and fatalities. The data reporting requirements in this bill can positively contribute to a smoother and safer implementation of this technology while ensuring public transparency.
FISCAL EFFECT: Appropriation: No Fiscal Com.: Yes Local: No
According to the Senate Appropriations Committee, “The DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department’s website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])”
SUPPORT: (Verified 8/26/2024)
California Conference Board of The Amalgamated Transit Union
California Conference of Machinists
California Labor Federation, Afl-cio
California Low-income Consumer Coalition
California Professional Firefighters
California School Employees Association
California Teamsters Public Affairs Council
Consumer Attorneys of California
Consumer Federation of California
Consumer Watchdog
Consumers for Auto Reliability & Safety
Engineers and Scientists of California, Ifpte Local 20, Afl-cio
Mission Street Neighbors
Public Law Center
San Francisco County Transportation Authority
San Francisco Taxi Workers Alliance
Smart - Transportation Division
Unite-here, Afl-cio
Utility Workers Union of America, Afl-cio
OPPOSITION: (Verified 8/26/2024)
Alliance for Automotive Innovation
Autonomous Vehicle Industry Association
California Manufacturers & Technology Association
Chamber of Progress
Cupertino Chamber of Commerce
Mountain View Chamber of Commerce
Technet
Tesla INC.
Volvo Group North America
ASSEMBLY FLOOR: 61-3, 5/22/24
AYES: Addis, Aguiar-Curry, Alanis, Alvarez, Arambula, Bauer-Kahan, Bennett, Boerner, Bonta, Bryan, Juan Carrillo, Wendy Carrillo, Chen, Connolly, Davies, Mike Fong, Gabriel, Garcia, Gipson, Grayson, Haney, Hart, Irwin, Jackson, Jones-Sawyer, Kalra, Lackey, Lee, Low, Lowenthal, Maienschein, McCarty, McKinnor, Muratsuchi, Stephanie Nguyen, Ortega, Pacheco, Papan, Jim Patterson, Pellerin, Petrie-Norris, Quirk-Silva, Ramos, Rendon, Reyes, Rodriguez, Blanca Rubio, Santiago, Schiavo, Soria, Ting, Valencia, Waldron, Wallis, Ward, Weber, Wicks, Wilson, Wood, Zbur, Robert Rivas
NOES: Dixon, Vince Fong, Hoover
NO VOTE RECORDED: Bains, Berman, Calderon, Cervantes, Megan Dahle, Essayli, Flora, Friedman, Gallagher, Holden, Mathis, Joe Patterson, Luz Rivas, Sanchez, Ta, Villapudua
Prepared by: Benjamin O'Brien-Hokanson / TRANS. / (916) 651-4121
8/26/24 21:34:20
**** END ****
SENATE RULES COMMITTEE Office of Senate Floor Analyses (916) 651-1520 Fax: (916) 327-4478 | AB 3061 |
THIRD READING
Bill No: AB 3061
Author: Haney (D), et al.
Amended: 8/15/24 in Senate
Vote: 21
SENATE TRANSPORTATION COMMITTEE: 11-2, 6/25/24
AYES: Cortese, Allen, Archuleta, Becker, Blakespear, Dodd, Gonzalez, Laird, Limón, Newman, Umberg
NOES: Niello, Seyarto
NO VOTE RECORDED: Dahle, Nguyen
SENATE APPROPRIATIONS COMMITTEE: 5-2, 8/15/24
AYES: Caballero, Ashby, Becker, Bradford, Wahab
NOES: Jones, Seyarto
ASSEMBLY FLOOR: 61-3, 5/22/24 - See last page for vote
SUBJECT: Vehicles: autonomous vehicle incident reporting
SOURCE: Author
DIGEST:
This bill requires, commencing July 31, 2025, a manufacturer of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) a vehicle collision, traffic citation, or disengagement, as defined, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California.
ANALYSIS:
Existing federal regulations require AVs or level 2 advanced driver assistance systems to report crashes within five calendar days.
Existing state law:
- Authorizes the operation of AVs on public roads for testing purposes under certain circumstances specified in DMV regulations (Vehicle Code Section (VEH) 38750).
- Defines “autonomous vehicle” to mean vehicle equipped with technology that makes it capable of operation that meets the definition of Levels 3, 4, or 5 of the Society of Automotive Engineers (SAE) International's Taxonomy and Testing of Autonomous Vehicles Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (April 2021).
- Defines “autonomous technology” to mean technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator.
- States that an AV does not include a vehicle that is equipped with one or more collision avoidance systems, including, but not limited to, electronic blind spot assistance, automated emergency braking systems, park assist, adaptive cruise control, lane keep assist, lane departure warning, traffic jam and queuing assist, or other similar systems that enhance safety or provide driver assistance, but are not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator.
- Prohibits the operation of AVs on public roads for non-testing purposes unless the manufacturer of the vehicles submits an application to DMV that is approved pursuant to DMV regulations.
- Requires DMV to approve an application submitted by a manufacturer for the operation of AVs for non-testing purposes if DMV finds that the applicant has submitted all information and completed testing necessary to satisfy that the AVs are safe to operate on public roads and the applicant has complied with all requirements specified in DMV regulations.
- Authorizes DMV to impose additional requirements it deems necessary to ensure the safe operation of AVs if those vehicles are capable of operating without the presence of a driver inside the vehicle.
Existing DMV regulations:
- Requires AV manufacturers to have a testing or deployment permit to operate an autonomous vehicle in California.
- Restricts the testing and deployment of autonomous vehicles to vehicles under 10,001 pounds and excludes motorcycles.
- Authorizes both the testing and deployment of AVs without a human operator inside the vehicle.
- Requires an AV with a testing permit (but not a deployment permit) to report collisions to DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if they have a testing permit.
- Requires AVs with a testing permit (but not a deployment permit) to report disengagements on an annual basis.
This bill:
- The Legislature makes findings and declarations as specified.
- Establishes definitions:
- “Disengagement” means the deactivation of a vehicle’s autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
- “Traffic citation” means a cited violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section, except for tickets issued for double parking that obstructs public transportation.
- “Vehicle Immobilization” means a stop in an active traffic lane when the autonomous vehicle is not able to continue the dynamic driving task for a significant amount of time. It does not include a stop intended to pick up or drop off a passenger or goods. The department shall have the discretion to define what qualifies as a significant amount of time up to a maximum of 180 seconds.
- “Vulnerable road user” includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders of occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
- Requires, commencing July 31, 2025, that a manufacturer of autonomous vehicles shall report to the DMV a vehicle collision or disengagement that occurs when a manufacturer’s vehicle is operating in autonomous mode on California public roads. These reports shall apply to all autonomous vehicles permitted by the DMV, regardless of whether the vehicle is operating under a testing or deployment permit.
- Requires that an incident report related to a vehicle collision submitted under this bill to include, but is not limited to, all of the following information:
- A detailed narrative of the collision, including any relevant precollision and postcollision information, as specified.
- The total number of passengers and any passenger interactions, if known by the manufacturer.
- The road and traffic conditions at the time of the collision.
- Any interactions with road users or obstacles in the road.
- The permit number for the testing or deployment permit issued by the DMV and the CPUC for the AV, if applicable.
- The vehicle identification number.
- Whether a safety driver was present.
- The latitude and longitude coordinates of the collision, as specified.
- The date and time of the collision, as specified.
- Any additional information reported to the federal National Highway Traffic Safety Administration (NHTSA) that does not contain personal information.
- Requires that an incident report related to AV disengagements under this bill be submitted on an annual basis and cover the period of December 1 of any current year to November 30, inclusive of the following year and contain at minimum, all of the following information:
- The latitude and longitude coordinates of the disengagement, as specified.
- Whether the vehicle was operating with or without a test driver at the time of the disengagement.
- A description of the facts and circumstances of the disengagement, as specified.
- Requires all collision reports submitted pursuant to this bill be submitted on the timelines adopted by the DMV that do not exceed the reporting deadlines required by NHTSA.
- Requires, commencing July 31, 2025, a manufacturer that is testing or deploying AVs to submit quarterly reports to the DMV summarizing in tabular format all reports that were submitted pursuant to this bill in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled (VMT), vehicle immobilizations, and any traffic citations that have not been dismissed at the time of submission of the report.
- Requires that a summary report of VMT be submitted to DMV, as specified.
- Requires that a summary report of vehicle immobilizations be submitted to DMV, as specified.
- Requires that a summary report of traffic violations that resulted in a citation and have not been dismissed be submitted to DMV, as specified.
- Requires, commencing July 1, 2025, the DMV to maintain all reports submitted pursuant to this bill in an electronic format as received by the manufacturer and make the reports available upon request by local and state transportation authorities.
- Requires, commencing January 1, 2028, the DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine readable format on the DMV’s internet website within 90 days of receipt.
- Requires, commencing January 1, 2028, the department to redact the personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the AV manufacturer prior to releasing any report.
- The DMV may redact information on vehicles not owned or operated by the manufacturer.
- The DMV shall provide the relevant AV manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted, as specified.
Comments
- Purpose of the bill. According to the author, “AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.”
- DMV and AVs. In 2012, the Legislature passed SB 1298 (Padilla), which permitted AVs to operate on public roads for testing by a driver under certain conditions. In 2014, the DMV established regulations to authorize the testing of AVs with gross vehicle weights (GVWs) of less than 10,001 pounds (e.g. light duty AVs) with safety drivers. In 2018, the DMV established regulations to authorize testing of light-duty AVs without safety drivers. In 2022, the DMV established regulations to authorize the deployment of light-duty AVs without safety drivers. Layered on top of the DMV process is approval by the California Public Utilities Commission (CPUC). Though not required as part of the 2012 legislation, the CPUC has been involved as a second layer of approval for light-duty AVs. This is because the AVs are carrying fare-paying passengers and the CPUC has the duty to ensure passenger safety. Unless specified in a new statute, the CPUC would have no role in the approval of AV trucks.
The DMV testing process appears relatively thorough though reliant on reporting and self-assessment. Before an AV is allowed on a public road with a safety driver, the manufacturer must apply for a permit where they demonstrate that they have validated the technology. The safety driver must be properly trained and enrolled in the DMV’s commercial driver program that tracks driver safety and revokes the license of unsafe drivers (pull-notice program). Evidence of financial responsibility (e.g. insurance) by the manufacturer is required. Extensive reporting by the AV manufacturer is required including all collisions and disengagements of the AV system. As of April 2024, 35 companies are authorized to test with a safety driver.
To test an AV without a safety driver the DMV looks at the performance of the manufacturer when testing with a safety driver. A real-time communication link between the AV and a remote operator must be maintained. A plan for interacting with law enforcement must be created, which is reviewed by the California Highway Patrol. As of April 2024, six companies are authorized to test without a safety driver.
To obtain final approval to deploy, the AV the manufacturer must identify the geographic location and conditions under which the AV will operate, certify compliance with all applicable Federal Motor Vehicle Safety standards, equip the vehicle with data recorders, which capture all vehicle functions, and provide other safety-related certifications. As of January 2024, three companies are authorized to operate autonomously without a driver in specified locations and conditions: Mercedes-Benz, Nuro, and Waymo.
- Deployment and reporting. Most AV testing and deployment in California has occurred in San Francisco. In a January 2023 letter, the San Francisco County Transportation Authority asked the CPUC to reject Waymo’s request to allow commercial deployment throughout the city. The letter highlights a series of 9-1-1 calls that the city had received stating, “Managers in the City’s Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or an AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours.”
The incidents described above were only known to San Francisco officials because of these 9-1-1 calls. These incidents were not reported to DMV because it only requires disengagement reports for vehicles with a testing permit. Reporting to DMV is further limited because AV companies do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations. This allows AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
In addition to these incidents not being reported to DMV, on October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Cruise was not required to report this collision to DMV because it was operating on a deployment permit. This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and more closely follows existing NHSTA reporting requirements. This includes data regarding crashes and traffic citations during the testing and deployment phases, not just the testing phase as required by existing DMV regulations. It also requires AV companies in the deployment and testing phase to report to DMV on unplanned stops and disengagements which have been noted as points of concern by San Francisco officials. This bill further gives the DMV the authority to suspend or revoke the testing or deployment permit of a manufacturer if an investigation is pending for a violation of the new reporting requirements.
- AV safety, promises versus realities. According to the Bureau of Transportation Statistics over 32,000 people are killed in crashes on United States roads every year. The National Transportation Safety Board (NTSB) reports that more than 90% of crashes are caused by human errors. AVs have the potential to significantly mitigate this public health crisis, as AVs are never drunk, distracted, or tired. Their performance should also be better than human drivers because of their better perception (ie. no blind spots), better decision making (ie. more-accurate planning of driving maneuvers), and better execution (ie. faster and more precise control of acceleration, braking, and steering). However, AVs are not perfect. For instance, inclement weather and complex driving environments pose challenges for AVs and human drivers, and a study of Google’s AVs found they performed worse than human drivers in some of these cases. There is also the potential for AVs to pose new crash risks like crashes resulting from cyber-attacks. In short, AVs can be safer than vehicles operated by humans, but additional engineering is needed to prevent specific blind spots that may currently lead to roadway incidents, accidents, and fatalities. The data reporting requirements in this bill can positively contribute to a smoother and safer implementation of this technology while ensuring public transparency.
FISCAL EFFECT: Appropriation: No Fiscal Com.: Yes Local: No
According to the Senate Appropriations Committee: “The DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department’s website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])”
SUPPORT: (Verified 8/16/24)
California Conference Board of the Amalgamated Transit Union
California Conference of Machinists
California Labor Federation, Afl-cio
California Low-income Consumer Coalition
California Professional Firefighters
California School Employees Association
California Teamsters Public Affairs Council
Consumer Attorneys of California
Consumer Federation of California
Consumer Watchdog
Consumers for Auto Reliability & Safety
Engineers and Scientists of California, Ifpte Local 20, Afl-cio
Mission Street Neighbors
Public Law Center
San Francisco County Transportation Authority
San Francisco Taxi Workers Alliance
Smart - Transportation Division
Unite-here, Afl-cio
Utility Workers Union of America
Utility Workers Union of America, Afl-cio
OPPOSITION: (Verified 8/16/24)
Alliance for Automotive Innovation
Autonomous Vehicle Industry Association
California Manufacturers & Technology Association
Chamber of Progress
Cupertino Chamber of Commerce
Mountain View Chamber of Commerce
Technet
Tesla INC.
Volvo Group North America
ASSEMBLY FLOOR: 61-3, 5/22/24
AYES: Addis, Aguiar-Curry, Alanis, Alvarez, Arambula, Bauer-Kahan, Bennett, Boerner, Bonta, Bryan, Juan Carrillo, Wendy Carrillo, Chen, Connolly, Davies, Mike Fong, Gabriel, Garcia, Gipson, Grayson, Haney, Hart, Irwin, Jackson, Jones-Sawyer, Kalra, Lackey, Lee, Low, Lowenthal, Maienschein, McCarty, McKinnor, Muratsuchi, Stephanie Nguyen, Ortega, Pacheco, Papan, Jim Patterson, Pellerin, Petrie-Norris, Quirk-Silva, Ramos, Rendon, Reyes, Rodriguez, Blanca Rubio, Santiago, Schiavo, Soria, Ting, Valencia, Waldron, Wallis, Ward, Weber, Wicks, Wilson, Wood, Zbur, Robert Rivas
NOES: Dixon, Vince Fong, Hoover
NO VOTE RECORDED: Bains, Berman, Calderon, Cervantes, Megan Dahle, Essayli, Flora, Friedman, Gallagher, Holden, Mathis, Joe Patterson, Luz Rivas, Sanchez, Ta, Villapudua
Prepared by: Benjamin O'Brien-Hokanson / TRANS. / (916) 651-4121
8/19/24 12:46:41
**** END ****
SENATE COMMITTEE ON APPROPRIATIONS
Senator Anna Caballero, Chair
2023 - 2024 Regular Session
AB 3061 (Haney) - Vehicles: autonomous vehicle incident reporting
Version: June 12, 2024 | Policy Vote: TRANS. 11 - 2 |
Urgency: No | Mandate: No |
Hearing Date: August 15, 2024 | Consultant: Mark McKenzie |
Bill Summary:
AB 3061 would, commencing July 31, 2025, require a manufacturer of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) a vehicle collision, traffic citation, or disengagement, as defined, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California.
*********** ANALYSIS ADDENDUM – SUSPENSE FILE ***********
The following information is revised to reflect amendments
adopted by the committee on August 15, 2024
Fiscal Impact:
- The DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department’s website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])
Author Amendments:
- Delete the requirement for AV manufacturers to report traffic citation data to the DMV, and clarify that data for AV collisions and disengagements must be reported when operating in autonomous mode on California public roads, as specified.
- Delete a legislative finding and declaration stating that data collected by DMV is inconsistent with data provided by AV companies operating in California to the federal National Highway Traffic Safety Administration.
- Clarify the definitions of “traffic citation” and “vehicle immobilization,” as specified.
- Delete the requirement that a collision incident report provided to DMV must include information related to the performance of the AV system, injury and property damage details, and the AVs license plate number, and clarify other information that must be reported, as specified.
- Require incident reports regarding AV disengagements to be submitted annually, as specified, and require the location of any such incidents to be reported by latitude and longitude coordinates of the incident with five decimal precision.
- Delete a requirement for vehicle collisions resulting in a fatality, involving a vulnerable road user, or resulting in any individual being transported to a hospital to be reported within one calendar day.
- Delete a requirement for vehicle collisions resulting in a vehicle being towed or air bag deployment to be reported within five calendar days.
- Delete a requirement to report whether autonomous technology was engaged 30 seconds before a collision within 45 calendar days.
- Require the summary report of vehicle miles traveled (VMT) to include the number of AVs operating on California public roads during the reporting period, and the VMT broken down by county.
- Delete the requirement that a summary report of vehicle immobilizations must include the license plate number of an AV, whether the automated technology was engaged 30 seconds prior to an unplanned stop, whether a test driver was present at the time of the unplanned stop, the type of location where the unplanned stop occurred, a description of the cause of the unplanned stop, a description of how the unplanned stop was resolved, and the unplanned stop identification number.
- Clarify other information that must be included in a summary report of vehicle immobilizations, as specified.
- Delete the requirement that a summary report of traffic violations that resulted in a citation and have not been dismissed to include the license plate number of the AV, and whether a test driver, remote operator, or the automated driving system was in control of the vehicle at the time of the collision.
- Require DMV to maintain all reports submitted pursuant to the bill in an electronic format, as specified, and make the reports available upon request by local and state transportation authorities.
- Require DMV to publish the reports on its website within 90 days of receipt, commencing on January 1, 2028, as specified.
- Require DMV to redact any personal information of any passengers, drivers, or other road users, and any information that divulges trade secrets identified by the AV manufacturer prior to releasing any report.
- Require DMV to provide the relevant AV manufacturer an opportunity to identify any information that divulges trade secrets that should potentially be redacted, and require the manufacturer to bear the burden of proving why the department should withhold any information, as specified.
- Make other technical, clarifying, and conforming changes.
-- END --
SENATE COMMITTEE ON APPROPRIATIONS
Senator Anna Caballero, Chair
2023 - 2024 Regular Session
AB 3061 (Haney) - Vehicles: autonomous vehicle incident reporting
Version: June 12, 2024 | Policy Vote: TRANS. 11 - 2 |
Urgency: No | Mandate: No |
Hearing Date: August 12, 2024 | Consultant: Mark McKenzie |
Bill Summary:
AB 3061 would, commencing July 31, 2025, require a manufacturer of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) a vehicle collision, traffic citation, or disengagement, as defined, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California.
Fiscal Impact:
- The DMV estimates costs of $16 million in 2025-26, $7.6 million in 2026-27, and $4.4 million annually thereafter to adopt regulations, develop, build, and maintain a new separate IT system to receive and manage the reports and post them on the department’s website. DMV would need to contract with technical consultants and hire additional staff to operate and maintain the IT systems, coordinate with AV manufacturers, perform technical analysis, review and evaluate data, track incidents, and take permitting actions, as necessary. (Motor Vehicle Account [MVA])
Background:
Existing law establishes the statutory framework for the DMV to test and approve the operation of all AVs within the state. In 2014, DMV adopted regulations to authorize the testing of light duty AVs (with a gross weight of 10,000 lbs or less) with a safety driver. The DMV established regulations to authorize the testing of light-duty AVs without a safety driver in 2018, and adopted additional regulations in 2022 to authorize the full deployment of light-duty AVs without a safety driver. In order to receive DMV’s approval to operate, an AV service must do all of the following:
- Identify the Operational Design Domain, or geographic location and conditions, in which the AVs are designed to operate.
- Establish that their technology can detect and respond to roadway situations.
- Establish that their vehicles meet federal motor vehicle safety standards.
- Certify the manufacturer has conducted tests to ensure the AVs are safe for deployment.
- Develop a law enforcement interaction plan to help first responders interact with the AVs.
- Meet specified insurance requirements.
The DMV’s website indicates that there are currently 35 companies authorized to test AVs with a safety driver, six companies authorized to test AVs without a safety driver, and three companies currently authorized to deploy AVs without a safety driver.
An AV company that conducts commercial passenger service must also receive approval from the California Public Utilities Commission (CPUC) to operate as a charter-party carrier that uses public highways for the transportation of passengers for compensation. To receive CPUC approval, the AVS must submit a specified Passenger Safety Plan (PSP) describing its policies and procedures to minimize risk for AV passengers. After the CPUC approves the initial plan, Commission staff can approve many subsequent changes, including expanding where an AVS can operate. To date, the CPUC has approved permits for seven companies to provide AV service with passengers, although some remain limited to piloting and testing their service, and one has since had their permit suspended.
Current DMV regulations require an AV testing permittee to report a collision within 10 days, if the collision resulted in damage of property or in bodily injury or death if the permittee has a testing permit. This requirement does not apply to AVs that are under a deployment permit. Existing federal regulations require AV operators to report any collisions involving AVs to the National Highway Traffic Safety Administration (NHTSA) within five or ten calendar days, depending on the circumstances of the collision.
Driverless AVs provide passenger service in California cities, and have reportedly caused numerous highly reported disruptions in San Francisco. In October 2023, a driverless AV operated by Cruise, a unit within General Motors, was struck by another vehicle, which sent the AV into a collision with a pedestrian. The AV dragged the pedestrian about 20 feet, causing critical injuries. Cruise did not properly report the incident to DMV, which in response revoked Cruise’s AV deployment license. In January of this year, the City and County of San Francisco sued the State over the CPUC’s permitting of driverless AVs.
Proposed Law:
This bill would, among other things, do the following:
- Require, commencing July 31, 2025, a manufacturer of AVs to report to DMV a vehicle collision, traffic citation, or disengagement, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California. These reports shall apply to all AVs permitted by DMV, regardless of whether the vehicle is in the testing or deployment phase.
- Prescribe the information that must be contained in an incident report related to a vehicle collision, traffic citation, and disengagement, respectively.
- Require all reports pursuant to this bill to be submitted on the timelines adopted by DMV, and specify that the timelines must not exceed the reporting deadlines required by NHTSA.
- Require a report to be issued within one calendar day if an incident related to a vehicle collision results in a fatality, any individual being transported to a hospital from the scene for medical treatment, or involves a specified vulnerable road user. If an incident related to a vehicle collision results in a vehicle being towed or air bag deployment, the report must be submitted within five calendar days. If the autonomous technology was engaged 30 seconds before a collision, the report must submitted within 45 calendar days.
- Require, commencing July 31, 2025, a manufacturer of AVs to submit quarterly reports to DMV summarizing in tabular format all reports that were submitted pursuant to this bill in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled (VMT), unplanned stops, wheelchair-accessible services, and traffic violations that resulted in a traffic citation and have not been dismissed at the time of submission of the report.
- Prescribe the information that must be contained in quarterly summary reports of VMT, unplanned stops, and traffic violations resulting in a citation that have not been dismissed, as specified.
- Require DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine-readable format on the department’s internet website within 30 days of receipt. The reports published shall not be redacted in any capacity except to remove identifiable personal information of any passengers or drivers.
- Authorize DMV to suspend or revoke an AV manufacturer’s testing and deployment permit while an investigation is pending for a violation of this section.
Related Legislation:
AB 1777 (Ting), which is currently pending in this Committee, would make an AV manufacturer responsible for traffic citations for violations that occur when autonomous technology is engaged. The bill would also require manufacturers that operate driverless AVs to maintain a dedicated emergency response telephone line and equip AVs with two-way voice communication, as specified.
AB 2286 (Aguiar-Curry), which is currently pending in this Committee, would prohibit the operation of an AV with a gross vehicle weight of over 10,000 pounds on public roads without a human safety operator physically present in the AV, and require the manufacturers of these vehicles operating under a testing permit to report collision and disengagement date to the DMV.
SB 1298 (Padilla), Chap. 570/2012, established conditions for the operation of AVs on public roadways, and required DMV to develop AV regulations.
Staff Comments:
The Legislative Analyst’s Office (LAO) recently published a report as part of its analysis of the Governor’s proposed 2024-25 Budget entitled “Insolvency Risks for Environmental and Transportation Special Funds” that includes an evaluation of the MVA. The report notes that between 2018-19 and 2023-24, MVA revenues have increased by $714 million while expenditures have increased by about $1 billion, and since 2021-22, annual expenditures have exceeded yearly revenues, resulting in a structural imbalance. The MVA is expected to fully exhaust its reserves and become insolvent in 2025-26 (Budget Year +1). Specifically, the administration projects expenditures will exceed available resources by roughly $140 million in 2025-26. Absent actions to address the MVA fund condition, approving any new proposals that would increase MVA expenditures would exacerbate the structural imbalance and hasten the insolvency timeline. The LAO recommends that “the Legislature set a high bar for considering approval of any proposals that create additional MVA cost pressures and accelerate the risk of insolvency.” This bill would result in increases in MVA expenditures that would exacerbate the fund’s structural imbalance.
-- END --
SENATE COMMITTEE ON TRANSPORTATION
Senator Dave Cortese, Chair
2023 - 2024 Regular
Bill No: Hearing Date: 6/25/2024
Author: | Haney | ||
Version: | 6/12/2024 Amended | ||
Urgency: | No | Fiscal: | Yes |
Consultant: | Benjamin O'Brien-Hokanson | ||
SUBJECT:
DIGEST: Commencing July 31, 2025, this bill would require a manufacturer of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) a vehicle collision, traffic citation, or disengagement, as defined, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California.
ANALYSIS:
Existing law:
- Authorizes the operation of AVs on public roads for testing purposes under certain circumstances specified in DMV regulations (Vehicle Code Section (VEH) 38750).
- Defines “autonomous vehicle” to mean vehicle equipped with technology that makes it capable of operation that meets the definition of Levels 3, 4, or 5 of the Society of Automotive Engineers (SAE) International's Taxonomy and Testing of Autonomous Vehicles Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (APR 2021).
- Defines “autonomous technology” to mean technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator.
- States that an AV does not include a vehicle that is equipped with one or more collision avoidance systems, including, but not limited to, electronic blind spot assistance, automated emergency braking systems, park assist, adaptive cruise control, lane keep assist, lane departure warning, traffic jam and queuing assist, or other similar systems that enhance safety or provide driver assistance, but are not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator.
- Prohibits the operation of AVs on public roads for non-testing purposes unless the manufacturer of the vehicles submits an application to DMV that is approved pursuant to DMV regulations.
- Requires DMV to approve an application submitted by a manufacturer for the operation of AVs for non-testing purposes if DMV finds that the applicant has submitted all information and completed testing necessary to satisfy that the AVs are safe to operate on public roads and the applicant has complied with all requirements specified in DMV regulations.
- Authorizes DMV to impose additional requirements it deems necessary to ensure the safe operation of AVs if those vehicles are capable of operating without the presence of a driver inside the vehicle.
Existing DMV regulations:
- Requires AV manufacturers to have a testing or deployment permit to operate an autonomous vehicle in California.
- Restricts the testing and deployment of autonomous vehicles to vehicles under 10,001 pounds and excludes motorcycles.
- Authorizes both the testing and deployment of AVs without a human operator inside the vehicle.
- Requires an AV with a testing permit (but not a deployment permit) to report collisions to DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if they have a testing permit.
- Requires AVs with a testing permit (but not a deployment permit) to report disengagements on an annual basis.
Existing federal regulations:
- Requires AVs or level 2 advanced driver assistance systems to report crashes within five calendar days.
This bill:
- The Legislature makes findings and declarations as specified.
- Establishes definitions:
- “Disengagement” means the deactivation of a vehicle’s autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated.
- “Traffic citation” includes, but is not limited to, a violation of this code and a violation of a local ordinance adopted pursuant to this code. Parking tickets shall not be included as a traffic citation pursuant to this section.
- “Unplanned stop” means a stop in a roadway for a minimum of 90 seconds when the conditions on the road require traffic flow. It does not include a stop intended to pick up or drop off a passenger.
- “Vulnerable road user” includes any person who is not an occupant of a motor vehicle with more than three wheels. This definition includes, but is not limited to, pedestrians, people traveling in wheelchairs, bicyclists, motorcyclists, and riders of occupants of other transport vehicles that are not motor vehicles, including all-terrain vehicles and tractors.
- Requires, commencing July 31, 2025, that a manufacturer of autonomous vehicles shall report to the DMV a vehicle collision, traffic citation, or disengagement, that occurs when a manufacturer’s vehicle is operating in autonomous mode in California. These reports shall apply to all autonomous vehicles permitted by the DMV, regardless of whether the vehicle is in the testing or deployment phase.
- Requires all reports pursuant to this bill to be submitted on the timelines adopted by the DMV that shall not exceed the reporting deadlines required by the National Highway Traffic Safety Administration (NHTSA).
- Requires that if an incident related to a vehicle collision results in a fatality or, any individual being transported to a hospital from the scene for medical treatment, or involves a vulnerable road user, the report shall be submitted within one calendar day.
- Requires that if an incident related to a vehicle collision results in a vehicle being towed or air bag deployment, the report shall be submitted within five calendar days.
- Requires that if the autonomous technology was engaged 30 seconds before a collision, that report shall be submitted within 45 calendar days.
- Requires, commencing July 31, 2025, that a manufacturer of AVs shall submit to the DMV quarterly reports summarizing in tabular format all reports that were submitted pursuant to this bill in the previous three months. The quarterly reports shall include a summary of vehicle miles traveled (VMT), unplanned stops, wheelchair-accessible services, and traffic violations that resulted in a traffic citation and have not been dismissed at the time of submission of the report.
- Requires that a summary report of VMT be submitted to DMV as specified.
- Requires that a summary report of unplanned stops be submitted to DMV, as specified.
- Requires that a summary report of traffic violations that resulted in a citation and have not been dismissed be submitted to DMV, as specified.
- Requires DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine-readable format on the department’s internet website within 30 days of receipt. The reports published shall not be redacted in any capacity except to remove identifiable personal information of any passengers or drivers.
- Authorizes DMV to suspend or revoke the manufacturer’s testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
COMMENTS:
- Purpose of the bill. According to the author, “AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.”
- DMV and AVs. In 2012, the Legislature passed SB 1298 (Padilla), which permitted AVs to operate on public roads for testing by a driver under certain conditions. In 2014, the DMV established regulations to authorize the testing of AVs with gross vehicle weights (GVWs) of less than 10,001 pounds (e.g. light duty AVs) with safety drivers. In 2018, the DMV established regulations to authorize testing of light-duty AVs without safety drivers. In 2022, the DMV established regulations to authorize the deployment of light-duty AVs without safety drivers. Layered on top of the DMV process is approval by the California Public Utilities Commission (CPUC). Though not required as part of the 2012 legislation, the CPUC has been involved as a second layer of approval for light-duty AVs. This is because the AVs are carrying fare-paying passengers and the CPUC has the duty to ensure passenger safety. Unless specified in a new statute, the CPUC would have no role in the approval of AV trucks.
The DMV testing process appears relatively thorough though reliant on reporting and self-assessment. Before an AV is allowed on a public road with a safety driver, the manufacturer must apply for a permit where they demonstrate that they have validated the technology. The safety driver must be properly trained and enrolled in the DMV’s commercial driver program that tracks driver safety and revokes the license of unsafe drivers (pull-notice program). Evidence of financial responsibility (e.g. insurance) by the manufacturer is required. Extensive reporting by the AV manufacturer is required including all collisions and disengagements of the AV system. As of April 2024, 35 companies are authorized to test with a safety driver.
To test an AV without a safety driver the DMV looks at the performance of the manufacturer when testing with a safety driver. A real-time communication link between the AV and a remote operator must be maintained. A plan for interacting with law enforcement must be created, which is reviewed by the California Highway Patrol. As of April 2024, six companies are authorized to test without a safety driver.
To obtain final approval to deploy, the AV the manufacturer must identify the geographic location and conditions under which the AV will operate, certify compliance with all applicable Federal Motor Vehicle Safety standards, equip the vehicle with data recorders, which capture all vehicle functions, and provide other safety-related certifications. As of January 2024, three companies are authorized to operate autonomously without a driver in specified locations and conditions: Mercedes-Benz, Nuro, and Waymo.
- Deployment and reporting. Most AV testing and deployment in California has occurred in San Francisco. In a January 2023 letter, the San Francisco County Transportation Authority asked the CPUC to reject Waymo’s request to allow commercial deployment throughout the city. The letter highlights a series of 9-1-1 calls that the city had received stating, “Managers in the City’s Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or an AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours.”
The incidents described above were only known to San Francisco officials because of these 9-1-1 calls. These incidents were not reported to DMV because it only requires disengagement reports for vehicles with a testing permit. Reporting to DMV is further limited because AV companies do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations. This allows AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
In addition to these incidents not being reported to DMV, on October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Cruise was not required to report this collision to DMV because it was operating on a deployment permit.
The Chamber of Progress and others in opposition argue that, “AB 3061 would implement duplicative reporting standards… Current federal law already requires autonomous vehicle operators to report any collisions involving autonomous vehicles to the NHTSA within 5 or 10 days, depending on the circumstances of the collision. The data NHTSA collects is made publicly available. NHTSA also reserves the right to open investigations into AV operators following any incident reports, and can request additional information regarding the performance of the autonomous systems throughout the course of the investigation.”
Supporters including the California Professional Firefighters express a different perspective, “AB 3061 (Haney) will address regulatory gaps in California’s governance and oversight of driverless ride hail services in California by ensuring jurisdictions have the information they need to understand the impacts of autonomous vehicles and how they are performing on public roadways. It would also allow the Department of Motor Vehicles to enforce compliance of the reporting provisions.”
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and more closely follows existing NHSTA reporting requirements. This includes data regarding crashes and traffic citations during the testing and deployment phases, not just the testing phase as required by existing DMV regulations. It also requires AV companies in the deployment and testing phase to report to DMV on unplanned stops and disengagements which have been noted as points of concern by San Francisco officials. This bill further gives the DMV the authority to suspend or revoke the testing or deployment permit of a manufacturer if an investigation is pending for a violation of the new reporting requirements.
- AV safety, promises versus realities. According to the Bureau of Transportation Statistics over 32,000 people are killed in crashes on United States roads every year. The National Transportation Safety Board (NTSB) reports that more than 90% of crashes are caused by human errors. AVs have the potential to significantly mitigate this public health crisis, as AVs are never drunk, distracted, or tired. Their performance should also be better than human drivers because of their better perception (ie. no blind spots), better decision making (ie. more-accurate planning of driving maneuvers), and better execution (ie. faster and more precise control of acceleration, braking, and steering). However, AVs are not perfect. For instance, inclement weather and complex driving environments pose challenges for AVs and human drivers, and a study of Google’s AVs found they performed worse than human drivers in some of these cases. There is also the potential for AVs to pose new crash risks like crashes resulting from cyber-attacks.
In short, AVs can be safer than vehicles operated by humans, but additional engineering is needed to prevent specific blind spots that may currently lead to roadway incidents, accidents, and fatalities. The data reporting requirements in this bill can positively contribute to a smoother and safer implementation of this technology while ensuring public transparency.
- Ongoing negotiations. The AV industry has expressed concern regarding these new data reporting requirements and whether they could result in the disclosure of confidential business information (CBI). NHTSA has exceptions, for which they will permit an AV company to claim that information submitted in an incident report constitutes CBI. The committee is aware that the author and industry stakeholders’ are in active negotiations to address this concern.
- Double referral. This bill is double referred to the Senate Energy, Utilities, and Communications Committee.
Related Legislation:
AB 1777 (Ting, 2024) - Places various requirements on AVs, holds AV companies liable for vehicle code infractions and authorizes DMV to take incremental enforcement measures against AVs, including restrictions on their operating domain. This bill is pending before this committee.
AB 2286 (Aguiar-Curry, 2024) - Restricts an AV with a GVW of 10,001 pounds or more from being operated on public roads for testing purposes, transporting goods, or transporting passengers without a human safety operator physically present. This bill is pending before this committee.
SB 915 (Cortese, 2024) - Requires local authorization for an AV commercial passenger service to operate within its limits. This bill is pending before the Assembly Transportation Committee.
AB 96 (Kalra, Chapter 419, Statutes of 2023) - Requires a public transit employer to provide written notice to an exclusive representative of the workforce affected by autonomous transit vehicle technology, and that collective bargaining commence within a certain timeframe.
AB 316 (Aguiar-Curry, 2023) - Was substantially similar to AB 2286. This bill was vetoed by the Governor.
AB 2441 (Kalra, 2022) - Would have required a public transit district to provide written notice to an exclusive representative of the workforce affected by autonomous transit vehicle technology. This bill was vetoed by the Governor.
SB 336 (Dodd, 2019) - Would have required a transit operator on every fully-automated transit vehicle until January 1, 2025. This bill died in this committee.
AB 1141 (Berman, 2017) - Would have required DMV to adopt regulations setting standards for AVs operating freight by September 30, 2018. This bill died in Assembly Communications and Conveyance Committee.
SB 1298 (Padilla, Chapter 570, Statutes of 2012) - Established conditions for the operation of AVs upon public roadways.
FISCAL EFFECT: Appropriation: No Fiscal Com.: Yes Local: No
According to the Assembly Appropriations Committee:
This bill requires AV manufacturers to regularly report substantial new amounts of data to the DMV, and authorizes members of the public or a public entity to also submit evidence to the DMV, all of which the DMV will need to receive, store and organize. And the bill requires the DMV to create and publish forms for AV reporting. In addition, the bill requires the DMV to publish certain AV manufacturer reports within 30 days of receipt and to post AV permit applications and approvals online. This will create significant one-time and ongoing costs for the DMV, likely in the millions of dollars one-time and, to a lesser extent, millions of dollars ongoing. (Motor Vehicle Account (MVA)).
The DMV estimates it will need $1.25 million one-time, in fiscal year 2025-26, to develop the information technology (IT) system to store and organize the reports, which, presumably, will include creation of forms, and $350,000 annually ongoing to maintain and manage the IT system. In addition, the DMV concludes it will need $3 million for AV consultant contracts and additional internal data and engineering staff to perform technical and data analysis, track incidents and promulgate regulations. The bill does not provide additional fee authority to DMV to pay for these costs.
The DMV may see an increase in revenue to the MVA, to the extent AV manufacturer violations of the law lead DMV to issue fines, pursuant to this bill.
According to the Legislative Analyst's Office (LAO), the MVA—the DMV's main funding source—is expected to fully exhaust its reserves and become insolvent in fiscal year 2025‑26. The LAO further warns that the MVA, absent corrective action, such as revenue increases or spending reductions, will experience a negative fund balance of $1.4 billion in fiscal year 2028‑29.
POSITIONS: (Communicated to the committee before noon on Wednesday, June 19, 2024.)
SUPPORT:
California Conference Board of The Amalgamated Transit Union
California Conference of Machinists
California Labor Federation, Afl-cio
California Low-income Consumer Coalition
California Professional Firefighters
California School Employees Association
California Teamsters Public Affairs Council
Consumer Attorneys of California
Consumer Federation of California
Consumer Watchdog
Consumers for Auto Reliability & Safety
Engineers and Scientists of California, Ifpte Local 20, Afl-cio
Mission Street Neighbors
Public Law Center
San Francisco County Transportation Authority
San Francisco Taxi Workers Alliance (SFTWA)
Smart - Transportation Division (SMART-TD)
Unite-here, Afl-cio
Utility Workers Union of America
Utility Workers Union of America, Afl-cio
OPPOSITION:
Alliance for Automotive Innovation
Autonomous Vehicle Industry Association
California Manufacturers & Technology Association
Chamber of Progress
Cupertino Chamber of Commerce
Mountain View Chamber of Commerce
Technet
Tesla INC. (oppose unless amended)
Volvo Group North America
-- END --
ASSEMBLY THIRD READING
ATR Bill Id:AB 3061
Author:(Haney)
As Amended Ver:April 16, 2024
Majority vote
SUMMARY
Requires the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California starting July 31, 2025.
Major Provisions
- Requires the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement of any passenger or safety driver that involves a manufacturer’s vehicle in California starting July 31, 2025.
- Authorizes DMV to impose a fine of up to $26,315 per day for a violation of this section and to impose a fine up to $131,546,183 for a related series of violations, consistent with requirements of the federal National Highway Traffic Safety Administration (NHTSA). A false report submitted under this section constitutes a violation.
- Requires DMV to establish a fine structure with a multiplier for subsequent violations.
- Authorizes DMV to suspend or revoke the manufacturer's testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
- Requires DMV, in consultation with the California Highway Patrol (CHP) the California Public Utilities Commission (CPUC), and any other public entity DMV deems necessary to create and public forms no later than January 1, 2025 that capture the above information and create a form to collect data for the aggregate analysis of AV safety.
- Requires DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine-readable format on the department's internet website within 30 days of receipt.
- Proves that the above described reports shall be anonymized to remove identifiable personal information of any passengers or drivers.
- Authorizes a member of the public or public entities with direct evidence of an incident to submit a true and accurate AV incident report covering an AV. Requires DMV to determine if the submission is credible and notify the submitting party of the department's determination within 30 days of receiving the report.
COMMENTS
DMV actions under this bill: DMV currently has limited tools to penalize AV companies violating its AV regulations, and is limited to suspending operation. DMV can suspend permits for failure to report data to DMV. This year an AV company lost its testing permit for failure to report disengagement data to DMV.
In addition to suspensions and revocations, this bill authorizes DMV to issue fines against AV companies for failure to report data. The fines permitted in this bill mirror NHTSA's fine structure. The Autonomous Vehicle Industry Association opposes these fines, arguing they are draconian and would detrimentally impact competition in California.
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and better mirrors existing NHSTA reporting requirements.
This includes data regarding crashes during the testing and deployment phases, not just the testing phase as required by existing DMV regulations. It also requires the DMV to collect harassment data on AVs, something already collected by CPUC.
The bill also creates a process for individuals to submit complaints about AVs to the DMV and requires the DMV to suspend a permit as it investigates the incident.
Additionally, AB 3061 does not establish a process for how the DMV should evaluate the veracity of public reports and disputes of such reports, nor the circumstances under which it should issue fines or permit suspensions or revocations. At a minimum, such a process must clarify how manufacturers could dispute claims and provide supporting evidence, as well as clarify the result of a manufacturer responding to a claim by providing their incident report."
Unclear if AVs are safer than humans. According to a RAND Corporation report Driving to Safety: How Many Miles of Driving Would it Take to Demonstrate Autonomous Vehicle Reliability, it may take decades before we know if AVs are safer than human drivers. Despite tens of thousands of deaths on the road every year, humans are capable of driving a remarkable number of miles without collisions. Americans drive 3 trillion miles every year. In 2013, there were 2.3 million injuries reported, a rate of 77 injuries per 100 million miles driven. The 32,719 deaths from car crashes that year correspond to a rate of about one fatality per 100 million miles driven. AVs have not driven anywhere near that many miles, and already at least one person has been killed by an AV in Tempe, Arizona.
AV companies often cite a report from the National Transportation Safety Board (NTSB) that concluded that 94% of all collisions are because of human error, and because of that AVs have the potential to save tens of thousands of lives. According to the Insurance Institute for Highway Safety (IIHS), "It is likely that fully self-driving cars will eventually identify hazards better than people, but we found that this alone would not prevent the bulk of crashes." IIHS estimates that only a third of the collisions caused by human error would be expected to be avoided because AVs will potentially have more accurate perceptions than human drivers and are not vulnerable to incapacitation. Avoiding the other two-thirds would require AVs that are programmed to prioritize safety over speed and convenience."
AVs performance and reporting in California. Most AV testing and deployment in California has occurred in San Francisco. In January 2023, the San Francisco County Transportation Authority asked the California Public Utilities Commission to reject Waymo's request to allow commercial deployment throughout the city. The letter notes a series of 9-1-1 calls that the city had received. The letter states "Managers in the City's Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or a Cruise AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours. Additional incidents were posted on social media or reported by the media. The number of reported incidents is likely a fraction of the total unplanned stops because most are reported during late night hours when few people are on the streets to notice them and because many people would not think to call 9-1-1 in these circumstances….Unfortunately, the AV failure incidents reported by the public have been significantly concentrated on streets of great importance in the City's transportation network: downtown streets, streets with transit service, streets on the bike network, intersections, and streets on the City's High Injury Network (the 12% of San Francisco streets that account for more than 68% of severe or fatal injury crashes)."
The incidents described by San Francisco were only known to them because of 9-1-1 calls and were not reported to DMV because DMV only requires disengagement reports for vehicles with a testing permit, but not a deployment permit. Companies also do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations, allowing AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
The Cruise LLC vehicles involved in these incidents had a DMV deployment permit at the time of the incidents. To get this permit, a company must self-certify that the "autonomous technology is designed to detect and respond to roadway situations in compliance with all provisions of the California Vehicle Code and local regulation applicable to the performance of the dynamic driving task in the vehicle's operational design domain, except when necessary to enhance the safety of the vehicle's occupants and/ or other road users." Despite the incidents of Cruise LLC vehicles documented by San Francisco above, Cruise LLC had received approval from DMV to expand their hours of service operation, increase their allowable speed, and test a vehicle incapable of being operated by a human operator. In addition, Cruise still has a pending application for approval for use by the NHSTA.
CPUC later approved Cruise LLC to operate for profit in San Francisco on August 10, 2023. Within a week a Cruise LLC vehicle crashed into a San Francisco Fire Department truck. A day later Cruise voluntarily reduced its fleet by 50% in the city. On October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Under DMV regulations, Cruise was not required to report this collision to DMV because it was operating on a deployment permit. DMV however, did follow up with Cruise based on media reports of the incident. DMV suspended Cruise's permit 24 days after an incident when they discovered Cruise had not shared with them the entirety of the video of the incident. The video showed the Cruise vehicle had come to a complete stop after the crash but then proceeded to drive over and drag the pedestrian. Cruise had stopped the video after the vehicle had come to a stop, but before the vehicle resumed to run over the pedestrian.
According to the Author
"AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe."
Arguments in Support
The California Teamsters, the co-sponsor of this bill, argue "Our union represents workers across the supply chain that frequently interact with AVs. Teamster members have seen firsthand how this technology is often imperfect, glitches, or fails to work appropriately. Likewise, driverless vehicles have made headlines for inuring pedestrians, shutting down and blocking intersections, causing gridlock, and obstructing emergency vehicles. There is a strong public interest in transparency.
Updates to the law are necessary to ensure that critical data is collected by the state as there are holes in the current regulations for data collection. Under AB 3061, a manufacturer of an autonomous vehicle must report to the DMV any collision, traffic violation, disengagement, assault, or harassment of any passenger or safety driver that involves a manufacturer's vehicle in California. All reports must be published online in an accessible readable format within 30 days of receipt. AB 3061 imposes fines for failure to report or false reporting, in addition to suspension or revocation of the manufacturer testing or deployment permit."
Arguments in Opposition
The Autonomous Vehicle Industry Association, writing in opposition to this bill, argues "AB 3061 would permit members of the public to submit evidence of an incident, and then require the DMV to suspend or revoke the AV company's testing or deployment permit while an investigation occurs to determine whether or not the report is credible. As drafted, this process could take up to 30 days. Only if the submission is determined to be credible by the DMV is a manufacturer then provided an opportunity to respond to the report. Moreover, the term "investigation" is undefined and thus any inquiry into an incident report could require the DMV to pause AV operations. As a result, any member of the public can report a potential incident to the DMV, and–even if the report is not accurate or credible–the DMV would need to suspend the manufacturer's permit while it investigates. This proposed process would neither be workable nor would it enhance safety or transparency; instead, it would allow members of the public to effectively halt AV operations in California.
FISCAL COMMENTS
According to Assembly Appropriations Committee:
This bill requires AV manufacturers to regularly report substantial new amounts of data to the DMV, and authorizes members of the public or a public entity to also submit evidence to the DMV, all of which the DMV will need to receive, store and organize. And the bill requires the DMV to create and publish forms for AV reporting. In addition, the bill requires the DMV to publish certain AV manufacturer reports within 30 days of receipt and to post AV permit applications and approvals online. This will create significant one-time and ongoing costs for the DMV, likely in the millions of dollars one-time and, to a lesser extent, millions of dollars ongoing. (Motor Vehicle Account (MVA)).
The DMV estimates it will need $1.25 million one-time, in fiscal year 2025-26, to develop the information technology (IT) system to store and organize the reports, which, presumably, will include creation of forms, and $350,000 annually ongoing to maintain and manage the IT system. In addition, the DMV concludes it will need $3 million for AV consultant contracts and additional internal data and engineering staff to perform technical and data analysis, track incidents and promulgate regulations. The bill does not provide additional fee authority to DMV to pay for these costs.
The DMV may see an increase in revenue to the MVA, to the extent AV manufacturer violations of the law lead DMV to issue fines, pursuant to this bill.
According to the Legislative Analyst's Office (LAO), the MVA—the DMV's main funding source—is expected to fully exhaust its reserves and become insolvent in fiscal year 2025‑26. The LAO further warns that the MVA, absent corrective action, such as revenue increases or spending reductions, will experience a negative fund balance of $1.4 billion in fiscal year 2028‑29.
VOTES
ASM TRANSPORTATION: 12-1-2
YES: Wilson, Davies, Aguiar-Curry, Juan Carrillo, Hart, Jackson, Lowenthal, Papan, Ting, Wallis, Ward, Wicks
NO: Hoover
ABS, ABST OR NV: Berman, Sanchez
ASM COMMUNICATIONS AND CONVEYANCE: 10-1-0
YES: Boerner, Jim Patterson, Bonta, Davies, Garcia, Holden, Maienschein, Stephanie Nguyen, Luz Rivas, Rodriguez
NO: Hoover
ASM APPROPRIATIONS: 12-3-0
YES: Wicks, Arambula, Bryan, Calderon, Wendy Carrillo, Mike Fong, Grayson, Haney, Hart, Jim Patterson, Pellerin, Villapudua
NO: Sanchez, Dixon, Ta
UPDATED
VERSION: April 16, 2024
CONSULTANT: David Sforza / TRANS. / (916) 319-2093 FN: 0003019
Date of Hearing: May 15, 2024
ASSEMBLY COMMITTEE ON APPROPRIATIONS
Buffy Wicks, Chair
ABPCA Bill Id:AB 3061
Author:(Haney) – As Amended Ver:April 16, 2024
Policy Committee: | Transportation | Vote: | 12 - 1 |
Communications and Conveyance | 10 - 1 | ||
|
|
Urgency: No State Mandated Local Program: No Reimbursable: No
SUMMARY:
This bill creates a process by which autonomous vehicle (AV) manufacturers must report to the Department of Motor Vehicles (DMV) incidents regarding their AVs and provides DMV substantial new penalty authority to use against an AV manufacturer that does not comply with the requirements of this bill.
Specifically, this bill, among other things:
- Requires an AV manufacturer, effective July 31, 2025, to report to the DMV any collision, traffic violation, disengagement of a vehicle’s AV mode when a failure of the autonomous technology is detected or barrier to access or incident of discrimination against a passenger with a disability, and directs DMV to adopt reporting timelines that do not to exceed reporting deadlines required by the National Highway Traffic Safety Administration (NHTSA).
- Requires an AV manufacturer to submit quarterly reports to DMV summarizing all reports submitted in the previous three months and requires DMV to publish the manufacturer’s report within 30 days of receipt.
- Authorizes a member of public or public entity with direct evidence to submit an AV incident report to DMV, which DMV is to determine as credible, or not credible, within 30 days and, if credible, gives the AV manufacturer 30 days to investigate and respond. Requires DMV to publish incident reports it deems credible and to notify the reporting party of the AV manufacturer’s response.
- Provides DMV significant new mechanisms to punish violations of the requirements of this bill, including submitting a false report, as follows: a fine of no less than $26,315 per day for a singular violation; a of fine up to $131,546,183 for a related series of violations, consistent with NHTSA requirements; and a fine structure, to be established by DMV, with a multiplier for subsequent violations. In addition, the bill requires DMV to suspend or revoke an AV manufacturer’s testing and deployment permit while an investigation of a violation of this section is pending against the manufacturer.
- Requires DMV—by July 1, 2025, and in consultation with the California Highway Patrol (CHP), the California Public Utilities Commission (CPUC) and any other public entity DMV deems necessary—to create and publish forms for the reporting of information described above and requires DMV and CPUC to post online all relevant info about AV permit applications and approvals.
FISCAL EFFECT:
This bill requires AV manufacturers to regularly report substantial new amounts of data to the DMV, and authorizes members of the public or a public entity to also submit evidence to the DMV, all of which the DMV will need to receive, store and organize. And the bill requires the DMV to create and publish forms for AV reporting. In addition, the bill requires the DMV to publish certain AV manufacturer reports within 30 days of receipt and to post AV permit applications and approvals online. This will create significant one-time and ongoing costs for the DMV, likely in the millions of dollars one-time and, to a lesser extent, millions of dollars ongoing. (Motor Vehicle Account (MVA)).
The DMV estimates it will need $1.25 million one-time, in fiscal year 2025-26, to develop the information technology (IT) system to store and organize the reports, which, presumably, will include creation of forms, and $350,000 annually ongoing to maintain and manage the IT system. In addition, the DMV concludes it will need $3 million for AV consultant contracts and additional internal data and engineering staff to perform technical and data analysis, track incidents and promulgate regulations. The bill does not provide additional fee authority to DMV to pay for these costs.
The DMV may see an increase in revenue to the MVA, to the extent AV manufacturer violations of the law lead DMV to issue fines, pursuant to this bill.
According to the Legislative Analyst’s Office (LAO), the MVA—the DMV’s main funding source—is expected to fully exhaust its reserves and become insolvent in fiscal year 2025‑26. The LAO further warns that the MVA, absent corrective action, such as revenue increases or spending reductions, will experience a negative fund balance of $1.4 billion in fiscal year 2028‑29.
COMMENTS:
- Purpose. The author describes this bill as “all about safety.” As the author states:
AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state…AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.
- Background. State law allows for the operation of driverless AVs on the state’s roadways, subject to regulation and permitting by the DMV. Currently, the DMV issues two types of AV permits to light-duty passenger vehicles: testing permits and deployment permits. An AV permittee may operate a driverless AV pursuant to a testing permit or a deployment permit. DMV subjects such a permittee to various requirements that, in some cases differ by the type of AV permit. Most notably, for this bill, DMV regulations require an AV testing permittee to report a collision to the DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if the permittee has a testing permit.
The CPUC allows an AV, including a driverless AV, to offer passenger service for hire, subject to a Transportation Charter Party (TCP) permit issued by the CPUC. A TCP permittee must comply with the DMV’s AV permit requirements.
Driverless AVs provide passenger service in California cities. Such vehicles have caused numerous highly reported disruptions in San Francisco. Most notably, perhaps, in October of last year, a driverless AV operated by Cruise—a unit within General Motors—was struck by another vehicle, which sent the AV into a collision with a pedestrian. The AV dragged the pedestrian about 20 feet, critically injuring the person. Cruise did not properly report the incident to the DMV. In response, the DMV revoked Cruise’s AV deployment license. In January of this year, the City and County of San Francisco sued the state over the CPUC’s permitting of driverless AVs.
- Related Legislation.
AB 1777 (Ting) creates requirements of the operation of AVs on public roadways regarding communications between an AV and emergency response officials and control of AVs in emergency situations. AB 1777 is pending before this committee.
AB 2286 (Aguiar-Curry) restricts an AV with a gross vehicle weight of 10,001 pounds or more from operating on public roads for testing purposes, transporting goods or transporting passengers without a human safety operator physically present in the AV at the time of operation. AB 2286 is pending before this committee.
Analysis Prepared by: Jay Dickenson / APPR. / (916) 319-2081
Date of Hearing: April 24, 2024
ASSEMBLY COMMITTEE ON COMMUNICATIONS AND CONVEYANCE
Tasha Boerner, Chair
ABPCA Bill Id:AB 3061 (
Author:Haney) – As Amended Ver:April 16, 2024
SUBJECT: Vehicles: autonomous vehicle incident reporting
SUMMARY: Requires, starting July 31, 2025, the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) on any vehicle collision, traffic violation, disengagement, or barrier to access or incident of discrimination for a passenger with a disability that involves a manufacturer’s vehicle in California.
Specifically, this bill:
- Establishes findings and declarations of the Legislature.
- Establishes definitions:
- “Disengagement” means the deactivation of a vehicle’s autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated
- “Traffic violation” includes, but is not limited to, a violation of this code and a violation of a local ordinance adopted pursuant to this code.
- “Unplanned stop” means a stop in a roadway for a minimum of 90 seconds when the conditions on the road require traffic flow. It does not include a stop intended to pick up or drop off a passenger.
- Requires, commencing July 31, 2025, a manufacturer of autonomous vehicles shall report to the Department of Motor Vehicles a vehicle collision, traffic violation, or disengagement, or a barrier to access or incident of discrimination for a passenger with a disability, that involves a manufacturer’s vehicle in California. Additionally, a manufacturer is required to submit quarterly reports summarizing in tabular format al reports that were submitted.
- Requires the specific report submitted by the manufacturer to the DMV to use specified forms required to be published by the DMV by no later than July 1, 2025.
- Specifies 13 specific criteria, at a minimum, that must be reported to the DMV related to a vehicle collision.
- Specifies 9 criteria, at a minimum, that must be reported to the DMV related to a traffic violation.
- Specifies 3 criteria, at a minimum, that must be reported to the DMV related to a vehicle disengagement.
- Specifies 4 criteria, at a minimum, that must be reported to the DMV related to an incident of discrimination or barrier to access for a passenger with a disability.
- Requires all the reports submitted to the DMV to be submitted on a timeline adopted by the Department, which shall not exceed the reporting deadline required by the federal National Highway Traffic Safety Administration (NHTSA).
- Requires the DMV to post all reports publicly on the department’s website within 30 days of receipt. Requires the report not be redacted, except to remove identifiable personal information of passengers or drivers.
- Authorizes the DMV to impose a fine of up to $26,315 per day for a violation of this section, and may impose a fine of up to $131,564,183 for a related series of violations. Additionally, requires the department to establish a fine structure with a multiplier for subsequent violations. Authorizes the department to suspend or revoke a manufacturer’s permit during an investigation.
- Authorizes members of the public or public entities with direct evidence of an incident to submit a true and accurate vehicle incident reporting covering an autonomous vehicle. Requires the department to determine if the submission is credible and notify the submitting party of the determination within 30 days of receiving this report. Additionally, requires the manufacturer to investigate and respond within 30 days if the submission is deemed credible by the DMV.
EXISTING LAW:
- Authorizes the operation of AVs on public roads for testing purposes under certain circumstances specified in DMV regulations (Vehicle Code Section (VEH) 38750).
- Defines “autonomous vehicle” to mean vehicle equipped with technology that makes it capable of operation that meets the definition of Levels 3, 4, or 5 of the Society of Automotive Engineers (SAE) International's Taxonomy and Testing of Autonomous Vehicles Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (APR 2021). (VEH 38750)
- Defines “autonomous technology” to mean technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator. (VEH 38750)
- States that an AV does not include a vehicle that is equipped with one or more collision avoidance systems, including, but not limited to, electronic blind spot assistance, automated emergency braking systems, park assist, adaptive cruise control, lane keep assist, lane departure warning, traffic jam and queuing assist, or other similar systems that enhance safety or provide driver assistance, but are not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator. (VEH 38750)
- Prohibits the operation of AVs on public roads for non-testing purposes unless the manufacturer of the vehicles submits an application to DMV that is approved pursuant to DMV regulations. (VEH 38750)
- Requires DMV to approve an application submitted by a manufacturer for the operation of AVs for non-testing purposes if DMV finds that the applicant has submitted all information and completed testing necessary to satisfy that the AVs are safe to operate on public roads and the applicant has complied with all requirements specified in DMV regulations. (VEH 38750)
- Authorizes DMV to impose additional requirements it deems necessary to ensure the safe operation of AVs if those vehicles are capable of operating without the presence of a driver inside the vehicle. (VEH 38750)
Existing DMV regulations:
- Requires AV manufacturers to have a testing or deployment permit to operate an autonomous vehicle in California.
- Restricts the testing and deployment of autonomous vehicles to vehicles under 10,001 pounds and excludes motorcycles.
- Authorizes both the testing and deployment of AVs without a human operator inside the vehicle.
- Requires an AV with a testing permit (but not a deployment permit) to report collisions to DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if they have a testing permit.
- Requires AVs with a testing permit (but not a deployment permit) to report disengagements on an annual basis.
Existing federal regulations:
- Requires AVs or level 2 advanced driver assistance systems to report crashes within five calendar days.
FISCAL EFFECT: Unknown. This bill is keyed fiscal by the Legislative Counsel.
COMMENTS:
- Author’s Statement. According to the author: “AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.”
- Committee Jurisdiction. The policy jurisdiction of the Communications & Conveyance Committee includes for-hire passenger transportation, including transportation network companies and autonomous vehicles engaged in the transportation of passengers. When an AV is used on a commercial basis, the passenger safety aspect of AVs passenger service is regulated by the CPUC, under the authority of the Charter Party Carrier of Passengers Act. Other aspects of autonomous vehicle regulation, including a manufacturer’s authority to operate on public roads and highways, are under the authority of the DMV and policy jurisdiction of the Transportation Committee. Accordingly, this analysis will primarily focus on the passenger safety aspect of autonomous vehicle service. Notably, most of the full driverless deployment and testing of AVs has happened under the CPUC’s program.
- AV Testing and Deployment in California. In 2012, the Legislature passed SB 1298 (Padilla), Chapter 570 which permitted AVs to operate on public roads for testing by a driver under certain conditions. In 2014, DMV released regulations to allow for testing AVs with a test driver, and in April 2018, DMV finalized regulations for the testing and deployment of AVs on public roads without a driver. About 35 companies currently have a testing permit with a driver and six companies have received a permit for testing without a driver[1]. Only three companies currently have a valid driverless deployment permit. While this bill would apply to all autonomous vehicle manufactures broadly – in testing with a driver, driverless testing, and full driverless deployment - most of the recent public attention has been focused on a limited number of companies that have fully deployed their driverless vehicles for commercial service under CPUC programs.
In 2018 the CPUC initially authorized[2] two pilot programs for the private prearranged transportation of passengers in test autonomous vehicles (AVs):
- The "Drivered AV Passenger Service" pilot program allows for the provision of passenger service in test AVs with a driver in the vehicle. Under this pilot program, a safety driver is available to assist with operations if needed.
- The "Driverless AV Passenger Service" pilot program allows for the provision of passenger service in test AVs without a driver in the vehicle. Under this pilot program, a communication link between passengers and "remote operators" of the vehicle must be available and maintained at all times during passenger service.
To be eligible to participate in the Commission's AV Passenger Service pilot programs, participants must possess the appropriate corresponding Autonomous Vehicle Tester Program Manufacturer's Testing Permit from the California Department of Motor Vehicles (DMV) for AV testing with a driver or testing without a driver and comply fully with DMV's AV testing regulations (California Code of Regulations, Title 13, Article 3.7). Under the AV Passenger Service pilot programs, monetary compensation may not be charged for any rides in test AVs. Currently, only one company (Waymo LLC), is authorized for full driverless deployment under the CPUC’s program. One other company (Zoox, Inc.), is authorized for driverless testing from the CPUC. Again, while there are other companies that currently have DMV testing permits with and without a driver, most of the vehicle miles traveled in AVs in California is happening under the CPUC’s passenger service pilot. To the extent that AVs in California will continue to primarily be deployed on a commercial basis, the impact of AV policy in California is almost intractable from its relationship to the CPUC programs and jurisdiction. However, this bill primarily focuses on the relationship between a manufacturer and the DMV.
- Data collection. Proponents of this bill, the academic community, local governments, and other members of the public have raised concerns with the state’s current data collection for autonomous vehicles. The primary concerns with the state’s AV data collection are that it is not comprehensive enough to capture the public safety impact of the technology and that the data is not shared publicly or in a format that is suitable for interested parties (academics, planners, etc;) to analyze. Consumer Watchdog, in their letter of support, points out that “currently the DMV neither collects nor reports data once an autonomous vehicle permit holder shifts from testing to a full deployment permit.”
In addition to the data the DMV collects for permit holders in their testing phases, the CPUC also collects its own data from companies permitted under its programs. The data collection scheme at the CPUC covers a broader field of data than the DMV testing data, which only covers disengagements and collisions[3] in the testing phase. On a quarterly basis, AVs in the CPUC’s programs are required to report on a breadth of data that covers information such as trip times, location by zip code, miles traveled, wheelchair accessibility information, the number of passengers per trip, whether the ride was shared, the time a customer waited, complaints, and other incidents that required the attention of the permit holder[4].
While some of the data that would be required to be reported to the DMV under this bill is similar to the data that is collected by the CPUC, this bill requires information that is much more granular and varied. For example, the CPUC already collects data on the total number of passengers per trip, trip times, and collisions generally (for the companies in their program). This bill would require additional information to be reported to the DMV such as a detailed narrative, a description of the injury and property damage, and other information related specifically to disengagements and incidents of discrimination of access for passengers with disabilities. While proponents of this bill underscore the importance of ensuring a minimum level of data is reported back to the DMV by autonomous vehicle manufactures, the opponents would argue the requirements are “unworkable and duplicative”. It is true that the CPUC does collect similar data than what is proposed by this bill, however it is only for the testing phase and there is no indication that the DMV reviews the reports submitted to the CPUC. As a result, there is a data gap of information that ought to be available to the public that this bill may help resolve.
- Monetary penalties for violations. This bill would make manufactures liable for significant monetary fines for violations of this bill’s provisions. Specifically, a manufacturer could be fined by the DMV in the amount of $26,315 per day for a violation of this bill’s provisions, and a fine of up to $131,564,183 for a related series of violations. The Assembly Transportation Committee analysis points out that the level of fines are severe and significant, and “mirror NHTSA’s fine structure.”
In addition to any fines imposed by DMV, under existing law and regulations the CPUC also has significant authority to levy fines or other punishment on AV operators under the commission’s jurisdiction. The CPUC’s authority to fine or penalize a regulated entity not in compliance with the law or regulatory requirement is set forth in Public Utilities Code §2107 (penalties range from $500 to $100,000) and §2108 (which provides that every violation is a separate offense, and that each day’s continuance shall be a separate and distinct offense). Additionally, pursuant to Rule 1.1 of the CPUC’s Rules of Practice and Procedure, one need not act with a specific intent to violate Pub. Util. Code § 2107.20. In addition the general fine authority, there are separate fine or penalty ranges for charter-party carriers (TCPs), which would include an AV operator. Pursuant to Pub. Util. Code § 5411, TCPs can be fined between $1,000 and $5,000 each day’s continuance thereof is a separate and distinct offense pursuant to Pub. Util. Code § 5415. Finally, Pub. Util. Code § 5378(b) also provides that a TCP can be fined up to $7,500 for a violation of the provisions set forth in Pub. Util. Code § 5378(a).
Notably, the CPUC’s regulations require a manufacturer to simultaneously transmit to the CPUC all reports required by DMV regulations. As such, the CPUC has interpreted omissions of information reported to the DMV to be omissions of information reported to the CPUC. For example, after an incident with Cruise, LLC in which a member of the public was killed and Cruise subsequently withheld information, the CPUC initiated an enforcement action[5] against Cruise ordering the company to show cause of why it should not be fined or penalized. The final decision is still pending, but Cruise initially offered a settlement payment of $75,000.
- Monitoring accessibility for persons with disabilities. This bill would require a manufacturer to report to the DMV on incidents related to discrimination or a barrier to access for a passenger with a disability. The accessibility of transportation services for persons with disabilities, especially autonomous vehicles, has consistently been an issue raised by disability rights advocates and regulators. Disability rights advocates have also advocated to secure the privacy of persons with disabilities, and for policies that prevent persons with disabilities from being required to disclose their status or medical history. For example, the evidentiary record for the CPUC’s decision to authorize autonomous vehicle deployment included comments from the California Council for the Blind and the Disability Rights Education and Defense Fund. Both organizations underscored the importance ensuring accessibility for persons with disabilities with the need to protect the privacy of those persons.
Analyzing this bill’s requirements pertaining to disabled persons through the lens of safety, this bill does provide some safeguards to ensure privacy and anonymity. For example, reports of barriers to access or discrimination for a passenger with a disability are to be reported anonymously with the passengers name redacted. Nonetheless, in order for a manufacturer to comply with the provisions of this bill related to discrimination or access for a person with a disability, the manufacturer would seemingly need to be made aware of that passenger’s disability status. If the manufacturer fails to report those incidents, even unknowingly, this bill would make them liable for significant fines. Given the sensitivity of disclosure of a disability to a private company or a government regulator, this bill’s provisions related to disability access may put manufacturers in a particularly precarious situation balancing privacy and accurate reporting.
It should be noted that the CPUC already collects data on the availability of wheelchair accessible vehicle (WAV) on AV platforms, which reflected a balance ensuring privacy with accessibility for persons with disabilities. While the CPUC has not established any specific targets or regulations regarding the availability of WAVs on AV platforms, the data is important to collect to understand where gaps exists. Lastly, pursuant to existing law[6], the CPUC also administers the Transportation Network Company (TNC) Access for All Program, which provides accessibility options for riders using TNC platforms. However, because AVs are a distinct regulatory category from TNCs, AVs are not currently covered by the program. In the future, the Legislature may wish to consider whether extending AV participation in the program would be reasonable. Perhaps, when equipped with more data relating to disability access, the evidence may show that an AV-inclusive approach is needed.
- Similar/related bills:
- AB 1777 (Ting) of 2024 places various requirements on AVs, holds AV companies liable for vehicle code infractions and authorizes DMV to take incremental enforcement measures against AVs, including restrictions on their operating domain. That bill is pending in the Assembly Transportation Committee.
- AB 2286 (Aguiar-Curry) of 2024 restricts an AV with a gross vehicle weight (GVW) of 10,001 pounds or more from being operated on public roads for testing purposes, transporting goods, or transporting passengers without a human safety operator physically present in the AV at the time of operation. That bill is pending in this committee.
- SB 915 (Cortese) of 2024 requires local authorization for an AV commercial passenger service to operate within its limits. That bill is pending before Senate Local Government Committee.
- AB 316 (Aguiar-Curry) of 2023 was substantially similar to AB 2286. That bill was vetoed by Governor Newsom.
- AB 1141 (Berman) of 2017 would have required DMV to adopt regulations setting standards for AVs operating freight by September 30, 2018. That bill died in Assembly Communications and Conveyance Committee.
- SB 1298 (Padilla), Chapter 570, Statutes of 2012 established conditions for the operation of AVs upon public roadways.
REGISTERED SUPPORT / OPPOSITION:
Support
California Low-income Consumer Coalition
California Professional Firefighters
California School Employees Association
Consumer Attorneys of California
Consumer Federation of California
Consumer Watchdog
Mission Street Neighbors
Public Law Center
San Francisco County Transportation Authority
San Francisco Taxi Workers Alliance (SFTWA)
Teamsters
Opposition
Autonomous Vehicle Industry Association
Analysis Prepared by: Emilio Perez / C. & C. / (916) 319-2637
A list of Autonomous Vehicle Testing Permit Holders can be found on the DMV website. https://www.dmv.ca.gov/portal/vehicle-industry-services/autonomous-vehicles/autonomous-vehicle-testing-permit-holders/ ↑
Decision D. 18-05-043. http://docs.cpuc.ca.gov/PublishedDocs/Published/G000/M215/K279/215279920.PDF ↑
§227.48 and §227.50 of Title 13 of the California Code of Regulations. https://www.dmv.ca.gov/portal/file/adopted-regulatory-text-pdf/ ↑
The CPUC data reporting requirements were adopted in Decision D. 20-11-046. https://docs.cpuc.ca.gov/PublishedDocs/Published/G000/M352/K185/352185092.PDF ↑
CPUC “Order to Show Cause” - https://docs.cpuc.ca.gov/PublishedDocs/Efile/G000/M521/K133/521133499.PDF ↑
SB 1376 (Hill): TNC Access for All Act. Chapter 701, Statutes of 2018. ↑
Date of Hearing: April 15, 2024
ASSEMBLY COMMITTEE ON TRANSPORTATION
Lori D. Wilson, Chair
ABPCA Bill Id:AB 3061 (
Author:Haney) – As Introduced Ver:February 16, 2024
SUBJECT: Vehicles: autonomous vehicle incident reporting
SUMMARY: Requires the manufacturers of autonomous vehicles (AVs) to report to the Department of Motor Vehicles (DMV) any vehicle collision, traffic violation, or disengagement, or the assault or harassment of any passenger or safety driver that involves a manufacturer’s vehicle in California starting July 31, 2025. Specifically, this bill:
- Requires DMV to impose a fine of no less than $26,315 per day for a violation of this section and to impose a fine up to $131,546,183 for a related series of violations, consistent with requirements of the federal National Highway Traffic Safety Administration (NHTSA). A false report submitted under this section constitutes a violation.
- Requires DMV to establish a fine structure with a multiplier for subsequent violations.
- Requires DMV to suspend or revoke the manufacturer’s testing and deployment permit of any manufacturer while an investigation is pending for a violation of this section.
- Requires a vehicle collision report to DMV to include the cause of the collision, any passenger interactions, the road and traffic conditions at the time of the collision, any interactions with road users or obstacles on the road, vehicle performance data, injury and property damage details, the states of the AV’s technology at the time of the collision and any additional information reported to NHSTA.
- Requires a traffic violation report to include the specific traffic law or regulation that was violated, including the traffic violation or citation; the circumstances that led to the violation, any actions taken by the AV or other involved parties in response to the violation, and any justification for the violation.
- Requires disengagement reports to include the location at which the disengagement occurred, whether the vehicle was operating with or without a driver at the time of the disengagement, and a description of the facts and any circumstances of the disengagement, including weather, road and traffic conditions.
- Requires harassment and assault reports to include disclosures of the nature of the incident, including the nature of assault or harassment, the approximate ages and gender identities, how the manufacturer addressed the incident, and any changes to company policies or protocol that will be made in response to the incident. Provides that any such reports shall be made without compromising the privacy and confidentiality of the individuals involved.
- Requires the information to be submitted to DMV on a timeline established by DMV.
- Requires DMV, in consultation with the California Highway Patrol (CHP) the California Public Utilities Commission (CPUC), and any other public entity DMV deems necessary to create and public forms no later than January 1, 2025 that capture the above information and create a form to collect data for the aggregate analysis of AV safety.
- Requires DMV to publish all reports submitted pursuant to this bill in an electronic, open, and machine-readable format on the department’s internet website within 30 days of receipt.
- Proves that the above described reports shall be anonymized to remove identifiable personal information of any passengers or drivers.
- Authorizes a member of the public or public entities with direct evidence of an incident to submit a true and accurate AV incident report covering an AV. Requires DMV to determine if the submission is credible and notify the submitting party of the department’s determination within 30 days of receiving the report.
- Requires DMV to give the manufacturer of the AV in the report 30 days to investigate and respond. The manufacturer is required either to inform DMV that it disputes the veracity of the report, with evidence to support its determination, or provide the manufacturer’s own incident report.
- Requires disputed reports to be published unless DMV determines they are not credible.
- Defines “disengagement” as the deactivation of a vehicle’s autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires a test driver or remote operator to disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated. (Consistent with DMV regulations.)
EXISTING LAW:
- Authorizes the operation of AVs on public roads for testing purposes under certain circumstances specified in DMV regulations (Vehicle Code Section (VEH) 38750).
- Defines “autonomous vehicle” to mean vehicle equipped with technology that makes it capable of operation that meets the definition of Levels 3, 4, or 5 of the Society of Automotive Engineers (SAE) International's Taxonomy and Testing of Autonomous Vehicles Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, standard J3016 (APR 2021). (VEH 38750)
- Defines “autonomous technology” to mean technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator. (VEH 38750)
- States that an AV does not include a vehicle that is equipped with one or more collision avoidance systems, including, but not limited to, electronic blind spot assistance, automated emergency braking systems, park assist, adaptive cruise control, lane keep assist, lane departure warning, traffic jam and queuing assist, or other similar systems that enhance safety or provide driver assistance, but are not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator. (VEH 38750)
- Prohibits the operation of AVs on public roads for non-testing purposes unless the manufacturer of the vehicles submits an application to DMV that is approved pursuant to DMV regulations. (VEH 38750)
- Requires DMV to approve an application submitted by a manufacturer for the operation of AVs for non-testing purposes if DMV finds that the applicant has submitted all information and completed testing necessary to satisfy that the AVs are safe to operate on public roads and the applicant has complied with all requirements specified in DMV regulations. (VEH 38750)
- Authorizes DMV to impose additional requirements it deems necessary to ensure the safe operation of AVs if those vehicles are capable of operating without the presence of a driver inside the vehicle. (VEH 38750)
Existing DMV regulations:
- Requires AV manufacturers to have a testing or deployment permit to operate an autonomous vehicle in California.
- Restricts the testing and deployment of autonomous vehicles to vehicles under 10,001 pounds and excludes motorcycles.
- Authorizes both the testing and deployment of AVs without a human operator inside the vehicle.
- Requires an AV with a testing permit (but not a deployment permit) to report collisions to DMV within 10 days of the collision if the collision resulted in damage of property or in bodily injury or death if they have a testing permit
- Requires AVs with a testing permit (but not a deployment permit) to report disengagements on an annual basis.
Existing federal regulations:
- Requires AVs or level 2 advanced driver assistance systems to report crashes within five calendar days.
FISCAL EFFECT: Unknown
COMMENTS: In 2012, the Legislature passed SB 1298 (Padilla), Chapter 570 which permitted AVs to operate on public roads for testing by a driver under certain conditions. In 2014, DMV released regulations to allow for testing AVs with a test driver, and in April 2018, DMV finalized regulations for the testing and deployment of AVs on public roads without a driver. 36 companies currently have a testing permit with a driver (down from a high of 58), and six companies have received a permit for testing without a driver. Three companies have received a deployment permit without a human driver. One company has a deployment permit for a level three AV, which requires a human operator. One or two companies currently have a deployment permit. One company, Cruise, has lost both its deployment permit and its permit to test without a human operator. Waymo is currently the only autonomous vehicle company authorized to charge fares for its services. Waymo is operating both in the Bay Area and Los Angeles.
DMV regulations prohibit the testing or deployment of AVs with a GVW of 10,001 pounds or more. This was initially done for safety reasons, as vehicles with heavier weights are capable of causing significantly more damage in a collision. DMV held a public workshop on January 27, 2023, to receive public comment to potentially start a new regulatory process to consider authorizing the testing and deployment of AVs over 10,000 pounds after years of lobbying efforts to expand testing and deployment permits for heavier vehicles.
According to the author, “AB 3061, the Self-Driving Cars Safety Act is in response to increased concerns about deployed self-driving cars — also called autonomous vehicles (AVs) — that are currently not required to report data on collisions, accidents, and vehicle malfunctions to the state. This is all about safety. AV companies are preparing to roll out in nearly every city in California, but data on which companies are safe and law-abiding and which aren't is being kept from the public and the state. As families may choose to rely on self-driving cars for daily activities like getting to school, work, and the grocery store, we have a responsibility to make sure they are safe.”
DMV actions under this bill: DMV currently has limited tools to penalize AV companies violating its AV regulations, and is limited to suspending operation. DMV can suspend permits for failure to report data to DMV. This year an AV company lost its testing permit for failure to report disengagement data to DMV.
In addition to suspensions and revocations, this bill authorizes DMV to issue fines against AV companies for failure to report data. The fines permitted in this bill mirror NHTSA’s fine structure. The Autonomous Vehicle Industry Association opposes these fines, arguing they are draconian and would detrimentally impact competition in California.
This bill creates a more structured format for collecting data than DMV is currently collecting under its existing regulations and better mirrors existing NHSTA reporting requirements.
This includes data regarding crashes during the testing and deployment phases, not just the testing phase as required by existing DMV regulations. It also requires the DMV to collect harassment data on AVs, something already collected by CPUC.
The bill also creates a process for individuals to submit complaints about AVs to the DMV and requires the DMV to suspend a permit as it investigates the incident.
The Autonomous Vehicle Industry Association, writing in opposition to this bill, argues “AB 3061 would permit members of the public to submit evidence of an incident, and then require the DMV to suspend or revoke the AV company’s testing or deployment permit while an investigation occurs to determine whether or not the report is credible. As drafted, this process could take up to 30 days. Only if the submission is determined to be credible by the DMV is a manufacturer then provided an opportunity to respond to the report. Moreover, the term “investigation” is undefined and thus any inquiry into an incident report could require the DMV to pause AV operations. As a result, any member of the public can report a potential incident to the DMV, and–even if the report is not accurate or credible–the DMV would need to suspend the manufacturer’s permit while it investigates. This proposed process would neither be workable nor would it enhance safety or transparency; instead, it would allow members of the public to effectively halt AV operations in California.
Additionally, AB 3061 does not establish a process for how the DMV should evaluate the veracity of public reports and disputes of such reports, nor the circumstances under which it should issue fines or permit suspensions or revocations. At a minimum, such a process must clarify how manufacturers could dispute claims and provide supporting evidence, as well as clarify the result of a manufacturer responding to a claim by providing their incident report.”
Unclear if AVs are safer than humans. According to a RAND Corporation report Driving to Safety: How Many Miles of Driving Would it Take to Demonstrate Autonomous Vehicle Reliability, it may take decades before we know if AVs are safer than human drivers. Despite tens of thousands of deaths on the road every year, humans are capable of driving a remarkable number of miles without collisions. Americans drive 3 trillion miles every year. In 2013, there were 2.3 million injuries reported, a rate of 77 injuries per 100 million miles driven. The 32,719 deaths from car crashes that year correspond to a rate of about one fatality per 100 million miles driven. AVs have not driven anywhere near that many miles, and already at least one person has been killed by an AV in Tempe, Arizona.
AV companies often cite a report from the National Transportation Safety Board (NTSB) that concluded that 94% of all collisions are because of human error, and because of that AVs have the potential to save tens of thousands of lives. According to the Insurance Institute for Highway Safety (IIHS), “It is likely that fully self-driving cars will eventually identify hazards better than people, but we found that this alone would not prevent the bulk of crashes.” IIHS estimates that only a third of the collisions caused by human error would be expected to be avoided because AVs will potentially have more accurate perceptions than human drivers and are not vulnerable to incapacitation. Avoiding the other two-thirds would require AVs that are programmed to prioritize safety over speed and convenience.”
AVs performance and reporting in California. Most AV testing and deployment in California has occurred in San Francisco. In January 2023, the San Francisco County Transportation Authority asked the California Public Utilities Commission to reject Waymo’s request to allow commercial deployment throughout the city. The letter notes a series of 9-1-1 calls that the city had received. The letter states “Managers in the City’s Department of Emergency Management began to notice several calls to 9-1-1 from people who witnessed or were affected by driverless AVs obstructing travel lanes. Sometimes these AVs caused extended traffic backups. Callers also complained of erratic driving (including signaling in one direction while moving in the other direction) or a Cruise AV blocking a transit vehicle. In other cases, callers reported evasive maneuvers by other road users such as driving on a sidewalk to get around a blockage caused by a disabled AV. The duration of these unplanned AV stops obstructing travel lanes appeared to range from minutes (extending through many traffic light cycles) to hours. Additional incidents were posted on social media or reported by the media. The number of reported incidents is likely a fraction of the total unplanned stops because most are reported during late night hours when few people are on the streets to notice them and because many people would not think to call 9-1-1 in these circumstances….Unfortunately, the AV failure incidents reported by the public have been significantly concentrated on streets of great importance in the City’s transportation network: downtown streets, streets with transit service, streets on the bike network, intersections, and streets on the City’s High Injury Network (the 12% of San Francisco streets that account for more than 68% of severe or fatal injury crashes).”
The incidents described by San Francisco were only known to them because of 9-1-1 calls and were not reported to DMV because DMV only requires disengagement reports for vehicles with a testing permit, but not a deployment permit. Companies also do not consider disengagements where a human operator is not present in the vehicle as a reportable disengagement under DMV regulations, allowing AV companies using remote operators to take over driverless vehicles to avoid reports to the DMV about disengagements.
The Cruise LLC vehicles involved in these incidents had a DMV deployment permit at the time of the incidents. To get this permit, a company must self-certify that the “autonomous technology is designed to detect and respond to roadway situations in compliance with all provisions of the California Vehicle Code and local regulation applicable to the performance of the dynamic driving task in the vehicle’s operational design domain, except when necessary to enhance the safety of the vehicle’s occupants and/ or other road users.” Despite the incidents of Cruise LLC vehicles documented by San Francisco above, Cruise LLC had received approval from DMV to expand their hours of service operation, increase their allowable speed, and test a vehicle incapable of being operated by a human operator. In addition, Cruise still has a pending application for approval for use by the NHSTA.
CPUC later approved Cruise LLC to operate for profit in San Francisco on August 10, 2023. Within a week a Cruise LLC vehicle crashed into a San Francisco Fire Department truck. A day later Cruise voluntarily reduced its fleet by 50% in the city. On October 2nd, 2023 a Cruise vehicle struck a pedestrian that was first struck by a human-operated vehicle. Under DMV regulations, Cruise was not required to report this collision to DMV because it was operating on a deployment permit. DMV however, did follow up with Cruise based on media reports of the incident. DMV suspended Cruise's permit 24 days after an incident when they discovered Cruise had not shared with them the entirety of the video of the incident. The video showed the Cruise vehicle had come to a complete stop after the crash but then proceeded to drive over and drag the pedestrian. Cruise had stopped the video after the vehicle had come to a stop, but before the vehicle resumed to run over the pedestrian.
The California Teamsters, the co-sponsor of this bill, argue “Our union represents workers across the supply chain that frequently interact with AVs. Teamster members have seen firsthand how this technology is often imperfect, glitches, or fails to work appropriately. Likewise, driverless vehicles have made headlines for inuring pedestrians, shutting down and blocking intersections, causing gridlock, and obstructing emergency vehicles. There is a strong public interest in transparency.
Updates to the law are necessary to ensure that critical data is collected by the state as there are holes in the current regulations for data collection. Under AB 3061, a manufacturer of an autonomous vehicle must report to the DMV any collision, traffic violation, disengagement, assault, or harassment of any passenger or safety driver that involves a manufacturer’s vehicle in California. All reports must be published online in an accessible readable format within 30 days of receipt. AB 3061 imposes fines for failure to report or false reporting, in addition to suspension or revocation of the manufacturer testing or deployment permit.”
Committee concerns: When DMV developed its AV regulations in 2018 it indicated to the Committee that they had personal use vehicles, not fleet-operated taxi-like vehicles in mind. DMV, through self-attestation, has authorized multiple companies now to fully deploy, not just test AVs. Deployment permits require a vehicle to be able to follow all the rules of the road. However, based on the experiences in San Francisco, it is clear that even deployed vehicles are still in testing mode and making significant mistakes.
While DMV has decided it no longer needs to collect collision and disengagement reporting after a deployment permit has been issued, NHTSA still treats AVs as nascent technology and requires crash reports to be submitted. DMV has also recognized the importance of monitoring AVs in the deployment stage and is currently relying on media reports to conduct investigations, as it did regarding the various Cruise violations that ultimately led to their permit being suspended.
Certain provisions of this bill are vague, as pointed out in the Autonomous Vehicle Industry Association letter. As this bill moves through the process, the author may want to provide further clarity. For example, it is unclear what an AV company may need to report for “vehicle performance data” and “The status of the autonomous vehicle’s technology” as required under the bill. Requiring AV companies to report the “cause of the collision” also may force them to make an admission of guilt.
This bill requires DMV to collect harassment information from AV companies. That provision may be more appropriate for CPUC, not DMV, which is in charge of licensing AVs for passengers for hire purposes. Otherwise, AV manufacturers could become responsible for having to report harassment data for personal use AVs should they ever become available. Moreover, CPUC already requires this data to be reported.
In this bill it is also unclear as to what constitutes a violation, but it has severe consequences for a violation, including a temporary loss of a permit to operate and significant fines. The bill requires that reporting occur “at the time the incident is identified” while also providing DMV flexibility to set timelines for when the data needs to be reported. As the bill moves forward the author should make it clear if a violation is for failure to report data to DMV.
The requirement to investigate consumer complaints and suspend AV operations while conducting the investigation could create a process where AV companies are never able to operate, and place a large administrative burden on AVs. According to the Legislative Analyst Office (LAO), the Motor Vehicle Account (MVA), the primary funding source for DMV, is expected to fully exhaust its reserves and become insolvent in 2025-26. The LAO recommends the Legislature should consider MVA cost pressures when evaluating new proposals. LAO argues that “Until a plan is put in place to address MVA’s structural deficit, we recommend the Legislature set a high bar for considering approval of any proposals that create additional MVA cost pressures and accelerate the risk of insolvency.”
Related Legislation: AB 1777 (Ting) of 2024 places various requirements on AVs, holds AV companies liable for vehicle code infractions and authorizes DMV to take incremental enforcement measures against AVs, including restrictions on their operating domain. That bill is pending before this committee.
AB 2286 (Aguiar-Curry) of 2024 restricts an AV with a gross vehicle weight (GVW) of 10,001 pounds or more from being operated on public roads for testing purposes, transporting goods, or transporting passengers without a human safety operator physically present in the AV at the time of operation.
SB 915 (Cortese) of 2024 requires local authorization for an AV commercial passenger service to operate within its limits. That bill is pending before Senate Local Government Committee.
AB 96 (Kalra), Chapter 419, Statutes of 2023 requires a public transit employer to provide written notice to an exclusive representative of the workforce affected by autonomous transit vehicle technology, and that collective bargaining commence within a certain timeframe, among other provisions.
AB 316 (Aguiar-Curry) of 2023 was substantially similar to AB 2286. That bill was vetoed by Governor Newsom.
AB 2441 (Kalra) of 2022 would have required a public transit district to provide written notice to an exclusive representative of the workforce affected by autonomous transit vehicle technology, among other provisions. That bill was vetoed by the Governor.
SB 336 (Dodd) of 2019 would have required a transit operator on every fully-automated transit vehicle until January 1, 2025. That bill died in this committee.
AB 1141 (Berman) of 2017 would have required DMV to adopt regulations setting standards for AVs operating freight by September 30, 2018. That bill died in Assembly Communications and Conveyance Committee.
SB 1298 (Padilla), Chapter 570, Statutes of 2012 established conditions for the operation of AVs upon public roadways.
REGISTERED SUPPORT / OPPOSITION:
Support
California Conference Board of The Amalgamated Transit Union
California Conference of Machinists
California Labor Federation, AFL-CIO
California Professional Firefighters
California School Employees Association
California Teamsters Public Affairs Council
Consumer Attorneys of California
Engineers and Scientists of California, IFPTE Local 20, AFL-CIO
Mission Street Neighbors
Public Law Center
San Francisco Taxi Workers Alliance (SFTWA)
Smart Transportation Division
Unite-Here, AFL-CIO
Utility Workers Union of America
Two Individuals
Oppose
Alliance for Automotive Innovation
Autonomous Vehicle Industry Association
California Manufacturers & Technology Association
Chamber of Progress
Cupertino Chamber of Commerce
Mountain View Chamber of Commerce
Technet
Volvo Group North America
Analysis Prepared by: David Sforza / TRANS. / (916) 319-2093
Discussed in Hearing
Assembly Floor
Senate Floor
Senate Standing Committee on Transportation
Assembly Floor
Assembly Standing Committee on Communications and Conveyance
Assembly Standing Committee on Transportation
Bill Author
Bill Co-Author(s):