---
title: Autonomous vehicle regulatory update
author: Jean Booth
url: https://www.plaintiffmagazine.com/issues/2026-july/autonomous-vehicle-regulatory-update
---

# [Autonomous vehicle regulatory update](https://www.plaintiffmagazine.com/issues/2026-july/autonomous-vehicle-regulatory-update "Autonomous vehicle regulatory update")

## California is moving in the right direction, but injured plaintiffs still need ready access to the digital evidence

[Jack Bollier](https://www.plaintiffmagazine.com/authors/jack-bollier "Jack Bollier")

[2026 July](https://www.plaintiffmagazine.com/issues/2026-july)

Autonomous vehicles (“AVs”) are no longer just an interesting concept. They are an everyday occurrence that we are almost guaranteed to encounter when we leave our homes. As AVs continue to proliferate, they will become increasingly involved in traffic collisions. This increased frequency will force plaintiffs’ attorneys to address the important evidence collected by AVs that has bearing on issues of fault and causation in vehicle cases.

Historically, law enforcement has been tasked with collecting the primary foundational evidence to vehicle collisions. This comes from familiar sources: party/witness statements, tire marks, vehicle damage, debris, roadway conditions, weather, amongst other relevant evidence. More recently and in more catastrophic cases, law enforcement may download data from a vehicle’s Event Data Recorder, a “black box” now equipped on most vehicles, which saves vehicle information in the moments leading up to an “event” – a sufficiently significant change in velocity caused by a collision. This data can vary from car to car but at a minimum will usually include vehicle speed, steering, braking, and throttle percentage, broken down every 10 milliseconds. 

In the traditional vehicle case, law enforcement synthesizes their investigation into a Traffic Collision Report (“TCR”), which “victims” are entitled to a copy of by statute. Plaintiffs and their attorneys can use the TCR as a starting point in evaluating the existence of a civil claim against any responsible party, which could include another driver, defective product, or dangerous condition of the roadway.

AVs can frustrate this paradigm. When there is no human driver, there is no conventional “statement” to be taken. Rather, the AVs “statement” must instead be derived from the software driving the AV. This could include whether the AV was operating in autonomous mode or remotely controlled, what the AV sensors perceived, how it classified surrounding objects, what it predicted other road users would do, AV planning, or its intended actions. 

California has recognized the importance of AV data generated contemporaneous to vehicle collisions. Vehicle Code section 38750 has long required AV manufacturers to preserve certain sensor data following a collision. More recently, AB 1777 amended California’s AV framework by adding emergency-response and enforcement provisions now codified in Vehicle Code sections 38751 and 38752. AVs can now be cited by law enforcement for violating the Vehicle Code. DMV regulations have also evolved, empowering the DMV to demand that AV manufacturers disclose “technical information, images, video and depictions about the status and operation of the vehicle’s sensors recorded 30 seconds prior to the time of the collision . . . .” (Cal. Code Regs., tit. 13, § 228.34.) Clearly, California takes seriously the role of ensuring the safe operation of AVs on its roadways.

But one piece remains missing. California has not yet created a clear, streamlined, and cost-effective mechanism allowing injured people and their attorneys to access crash-relevant AV data in the same practical way that injured parties may obtain a Traffic Collision Report. That gap matters because AV data may be relevant not only to the fault of the autonomous vehicle, manufacturer, or operator, but also to the fault of third-party *human*drivers, other driverless vehicles, roadway contractors, public entities, or others.

The civil justice system cannot evaluate fault if the best evidence of fault is inaccessible.

**California’s traditional auto-liability model depends on accessible evidence**

California’s tort system has long been built around the principle that those who fail to use ordinary care are responsible for the harm they cause. This standard is nowhere more prevalent than on the roadways and is intended to serve as a deterrent by holding negligent drivers accountable for their actions. California’s financial-responsibility laws complement civil liability by ensuring a minimum source of compensation to victims. 

Achieving the stated goals of compensation and deterrence in the context of vehicle injuries depends on the accessibility of foundational evidence. California recognizes that victims of a traffic collision are entitled to this evidence. While Traffic Collision Reports are confidential, the Vehicle Code permits disclosure to persons with a proper interest, including those involved in the collision and others with a legitimate connection to the matter. (Veh. Code, § 20012.) In practice, injured persons, vehicle owners, insurers, and attorneys representing those parties may obtain the report. The framework balances confidentiality against the practical need for evidence.

AVs can disrupt this balance. In a driverless crash, the Traffic Collision Report may still exist, but it may be missing key evidence. Law enforcement may document the scene, the damage, the roadway, and identities of those involved. But if an AV is involved, the officer may not be able to obtain the equivalent of a driver statement. Such evidence is contained in the AV data.

**Vehicle Code section 38750: Preservation is already part of California law**

California recognized early that autonomous vehicles would generate unique collision evidence. The Vehicle Code defines “autonomous technology” as “technology that has the capability to drive a vehicle without the active physical control or monitoring by a human operator.” (Veh. Code, § 38750, subd. (a)(1).) Put simply, an “autonomous vehicle” is a vehicle that is equipped with “autonomous technology” but excludes ordinary driver-assistance features such as automated emergency braking, lane-keeping assistance, adaptive cruise control, blind-spot assistance, and similar systems that are not capable of driving the vehicle without active human control or monitoring. (Veh. Code, § 38750, subd. (a)(2).)

Section 38750 requires AV manufacturers to certify that an autonomous vehicle has a separate mechanism to capture and store autonomous-technology sensor data for at least 30 seconds before a collision while the vehicle is operating in autonomous mode. The data must be captured and stored in read-only format and preserved for three years after the collision. (Veh. Code, § 38750, subd. (c)(1)(G).)

That requirement is not new. Section 38750 was originally added in 2012 as part of California’s early autonomous-vehicle legislation. (Stats. 2012, ch. 570, § 2.) But its significance has grown. As autonomous vehicles become more common, the statutory preservation requirement becomes more important to civil practice. California has already accepted the premise that AV collision data matters enough to preserve. The next questions are, who can access it, when, and at what cost?

**AB 1777: California is building out emergency-response and enforcement rules**

The more recent legislative update is AB 1777. That bill amended section 38750 and added Vehicle Code sections 38751 and 38752. (Stats. 2024, ch. 682 § 1.) These provisions do not create a plaintiff-access mechanism, but they are important because they show California is continuing to adapt its vehicle laws to the reality of AVs.

Vehicle Code section 38751 addresses emergency response. Effective July 1, 2026, it requires manufacturers operating driverless AVs under a testing or deployment permit to maintain a dedicated emergency-response telephone line whenever an AV is on a public road. The line must be available to emergency-response officials at no cost to public agencies. (Veh. Code, § 38751, subd. (b)(1)(A).)

Manufacturers must continuously monitor the status of each AV on public roads, and the telephone line must be staffed so calls are answered within 30 seconds by a remote human operator with “situational awareness” of the vehicles. (Veh. Code, § 38751, subd. (b)(1)(B).) The remote human operator must be able to immobilize the vehicle, allow an emergency official to move it, or cause it to move as directed. (Veh. Code, § 38751, subd. (b)(1)(C).) There are also requirements that the AV be equipped with two-way voice communications devices for emergency-response officials to achieve the same objectives. (Veh. Code, § 38751, subd. (b)(2).) Section 38751 authorizes emergency-response officials to issue emergency “geofencing messages” directing a manufacturer to have its fleet leave or avoid an emergency area. (Veh. Code, § 38751, subd. (d).)

These requirements reflect a practical legislative insight: When there is no human driver, public officials need a new way to interact with the AV in order to protect public safety.

Vehicle Code section 38752 addresses enforcement. It creates a “notice of autonomous vehicle noncompliance,” which a peace officer may issue after observing an alleged Vehicle Code violation or local traffic-ordinance violation by an AV while autonomous technology is engaged. (Veh. Code, § 38752, subds. (a), (b).) The notice must identify the alleged violation, the date, time, location, and license plate number. (Veh. Code, § 38752, subd. (a).) The manufacturer must provide the notice to DMV within 72 hours, or another timeframe determined by DMV. (Veh. Code, § 38752, subd. (c).) The issuance of the notice does not create a presumption that the AV is unsafe and does not prevent the manufacturer from contesting the alleged violation. (Veh. Code, § 38752, subd. (d).)

Again, the plaintiff-side significance is not that these provisions address the evidence-access problem. The significance is that California recognizes the need for law enforcement to interact with AVs in a manner that promotes public safety.

**DMV regulations show that the technical data exists and matters**

DMV regulations govern both the “testing” and “deployment” of AVs. (Cal. Code Regs., tit. 13, §§ 227.00 et seq., 228.00 et seq.) AVs that are “deployed” are those which are essentially available for fared passenger service. (See*City and County of San Francisco v. Public Utilities Com.* (2025) 108 Cal.App.5th 22, 31.) In either scenario, whether tested or deployed, AV manufacturers are subject to reporting obligations to the DMV when their AVs are involved in collisions. (Cal. Code Regs., tit. 13, §§ 227.54, 228.34.) AV manufacturers are subject to heightened scrutiny by the DMV relative to AV collisions effective April 28, 2026.

When an AV is involved in a collision, the DMV can demand:

technical information, images, video and depictions about the status and operation of the vehicle’s sensors recorded 30 seconds prior to the time of the collision, including, but not limited to, plots of the distance and the speed difference relative to the relevant targets in the collision path, the speed and acceleration of the subject vehicle and the acceleration, braking and steering commands that were issued by the automated driving system, and camera footage with target tracking representations.

(Cal. Code Regs., tit. 13, § 228.34(a)).)

Separate from the DMV right to technical information, AV manufacturers must certify that the AV has a “separate mechanism” to 

capture and store the autonomous technology sensor data for at least 30 seconds before a collision occurs between the autonomous vehicle and another vehicle, object, or natural person while the vehicle is operating in autonomous mode. The autonomous technology sensor data shall be captured and stored in a read-only format by the mechanism so that the data is retained until extracted from the mechanism by an external device capable of downloading and storing the data. The data shall be preserved for three years after the date of the collision.

(Cal. Code Regs., tit. 13, § 228.34(b).)

If the DMV can require technical information to evaluate AV safety and regulatory compliance, the next policy question is whether injured parties should have a parallel civil-access pathway to obtain crash-relevant information under appropriate protections.

**The current gap: Getting AV data without filing suit**

California now has several important pieces of an AV framework. Section 38750 requires preservation of autonomous-technology sensor data. Section 38751 gives emergency officials tools to interact with driverless vehicles. Section 38752 gives peace officers a way to document observed AV traffic-law violations. DMV regulations give the agency tools to require technical information from AV manufacturers relative to AV-involved collisions. But none of these provisions enable an injured party to gain access to relevant AV data needed to evaluate issues of third-party liability. 

This creates a practical access problem. The injured person may need the AV data to know whether a claim exists, against whom, and what legal theories apply. But without a clear mechanism to access AV data, the plaintiff may need to file suit before obtaining the very data needed to determine whether suit is justified. A practical, cost-effective framework that grants victims access to collision-related AV data is needed to address this absence of evidence.

**The next legislative step: An AV collision-data access report**

California should create a statutory AV collision-data access process modeled on the Traffic Collision Report framework.

The mechanism should be available to injured persons, vehicle owners, property owners, persons who may incur civil liability, insurers, and attorneys representing those persons. Like Traffic Collision Reports, the information need not be available to the general public. The access right can be limited to proper parties with a legitimate interest in evaluating the collision.

The trigger should be any AV-involved collision causing bodily injury, death, or significant property damage. The AV data may show that the AV caused the collision, but it may also show that the AV did not cause the collision, or that another party caused or contributed to the crash.

The production should include standardized, non-proprietary AV collision data sufficient to evaluate issues of fault and causation. At minimum, the report should identify whether autonomous technology was engaged, the relevant time window, vehicle speed and acceleration, braking and steering commands, detected objects, relevant object classification and tracking, autonomous-mode disengagements, remote-assistance or remote-driving involvement, and camera or sensor-derived images. Raw data should be preserved for later discovery if litigation follows. 

Costs for gaining access to AV data should be limited so that investigation is not dependent on whether the damages are large enough to justify expensive technical extraction and analysis. 

**Practice points for plaintiffs’ attorneys now**

Until California creates a plaintiff-access mechanism, attorneys should treat every AV or possible AV case as a digital-evidence case from day one.

Preservation letters should be sent immediately to the AV owner, manufacturer, operator, or insurer. The letters should request preservation of EDR data and AV data contemplated by DMV regulations. Plaintiffs’ attorneys should also look for DMV reports, NHTSA reports, public permit materials, noncompliance notices issued by law enforcement, and public regulatory filings. Early discovery, where litigation follows, should focus on what the AV perceived, classified, predicted, and did. Counsel should ask whether autonomous technology was engaged, what the vehicle detected, what objects were tracked, how those objects were classified, what path the vehicle selected, what braking or steering commands were issued, whether there were system failures or disengagements, whether remote assistance was involved, and whether the vehicle was operating within its approved operational design domain.

Most importantly, attorneys should remember that AV data may help prove fault against someone other than the AV company. The AV may be the best witness against a human driver, another driverless vehicle, a roadway contractor, a public entity, or some other third party.

**Conclusion**

California’s recent autonomous-vehicle updates are important. Changes to the Vehicle Code and DMV regulations demonstrate stepped-up enforcement against AV manufacturers on issues of public safety.

These developments show that California is moving in the right direction. But for injured plaintiffs, the next step is to share in the new forms of evidence historically contained in Traffic Collision Reports. California’s tort system requires access to this data to deter unsafe conduct, allocate responsibility, and compensate injured victims on California roads.

*Jack Bollier is a partner in the Rains Lucia Stern St. Phalle & Silver, PC Personal Injury Group. Jack has handled a variety of cases to successful resolution including auto, pedestrian, bicycle, motorcycle, and bus claims; various industrial and construction site accident claims; premises liability and worksite safety claims; and products liability actions.*

### [Jack Bollier](https://www.plaintiffmagazine.com/authors/jack-bollier "Jack Bollier")

[![Jack Bollier](https://www.plaintiffmagazine.com/media/zoo/images/Bollier-Jack-web_29cd92bbe5c76d92679f9d8955130774.jpg)](https://www.plaintiffmagazine.com/authors/jack-bollier "Jack Bollier")

Jack Bollier is a partner in the Rains Lucia Stern St. Phalle & Silver, PC Personal Injury Group. Jack has handled a variety of cases to successful resolution including auto, pedestrian, bicycle, motorcycle, and bus claims; various industrial and construction site accident claims; premises liability and worksite safety claims; and products liability actions.

### Subject Matter Index

[Evidence (see also Discovery)](https://www.plaintiffmagazine.com/tag/Evidence%20(see%20also%20Discovery))
