AB 2502 adds Section 23152.1 to the California Vehicle Code to declare that, for specified criminal statutes, the legal term “drive” includes any volitional movement of a vehicle that has driving automation at SAE Levels 0, 1, 2, or 3. The covered statutes include gross vehicular manslaughter while intoxicated (Penal Code §191.5) and several Vehicle Code offenses related to reckless driving and driving under the influence.
This is a targeted, doctrinal clarification that expands criminal liability to situations where a person exerts volitional control while a vehicle has partial or conditional automation. It matters for prosecutors, defense counsel, law enforcement training, insurers, and vehicle manufacturers because it shifts where responsibility for movement lies when driver-assist features are present and relies explicitly on SAE level definitions rather than a vehicle maker’s label or mode indicator.
At a Glance
What It Does
The bill declares that, for certain criminal statutes, a person “drives” when they cause volitional movement in a vehicle equipped with SAE Level 0–3 automation. It therefore makes the presence of partial or conditional automation irrelevant to whether an intoxicated or reckless operator can be criminally charged for movement they initiated or controlled.
Who It Affects
Drivers who operate vehicles with Level 0–3 driver assistance (common lane‑keeping, adaptive cruise, and partial automation systems), prosecutors and defense attorneys handling DUI and vehicular manslaughter cases, law enforcement officers responsible for charging and field investigation, and insurers who underwrite risk for crashes involving assisted‑driving systems.
Why It Matters
By codifying a definition keyed to SAE automation levels, the bill closes a potential defense based on automation and gives prosecutors a clearer statutory hook. It also creates legal uncertainty because SAE definitions are industry standards that can change and because proving a driver’s 'volitional' movement in partially automated contexts is fact‑intensive.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 2502 inserts a new statutory definition into the Vehicle Code saying that, for a set of criminal provisions, “drive” covers volitional movement in vehicles that have driving automation at SAE Levels 0 through 3. In practice that means commonly available driver‑assist features — from basic lane‑keeping and adaptive cruise to more advanced partial automation that still requires human supervision — do not defeat criminal liability if a person intoxicated or otherwise culpable exerts volitional control and the vehicle moves.
The bill ties its definition to the Society of Automotive Engineers’ level framework rather than to manufacturer labels or to an on‑vehicle ‘‘autonomous’’ mode. That creates a mechanical rule: courts, prosecutors, and investigators will look to whether a vehicle’s automation falls within Levels 0–3 and whether the movement was volitional.
The statute specifically reaches offenses under Penal Code §191.5 (gross vehicular manslaughter while intoxicated) and several Vehicle Code offenses related to reckless driving and DUI (23103, 23152, 23153), as cross‑referenced in the new text.Operationalizing the law will require factual findings at arrest and at trial: whether the vehicle was in a mode consistent with SAE Level 0–3, what human inputs (steering, braking, throttle, mode selection) occurred, and whether those inputs qualify as 'volitional' under the statute and existing case law. Prosecutors can rely on this statutory definition to charge cases where drivers were using common assistance features; defendants will likely litigate whether a particular system truly operated at the stated SAE level, whether the driver intended movement, and whether the system’s behavior, not the driver’s, caused the movement.The bill also notes this change creates a state‑mandated local program (because it expands criminal liability) and includes a constitutional provision stating no reimbursement to local agencies is required under Article XIII B, on the ground that the change pertains to crimes and penalties.
Practically, local agencies and courts will still face implementation tasks — evidence collection training, updated charging guidance, and possibly more contested trials over system classification and driver interaction.Finally, the law’s reliance on SAE levels imports technical standards into criminal law. That linkage can speed adjudication in many cases by pointing to an established taxonomy, but it also transfers interpretive questions — which system corresponds to which SAE level, and which edition of SAE guidance controls — into the courtroom and into administrative practice.
The Five Things You Need to Know
The bill adds a new Vehicle Code section (23152.1) declaring that for certain criminal statutes, 'drive' includes volitional movement of a vehicle with SAE Level 0, 1, 2, or 3 driving automation.
It expressly applies this definition for purposes of Penal Code §191.5 (gross vehicular manslaughter while intoxicated) and Vehicle Code offenses cited (23103 via 23103.5, 23152, and 23153).
The statute uses SAE (Society of Automotive Engineers) level definitions as the controlling taxonomy rather than manufacturer labels or proprietary system names.
By expanding the definition of 'drive' the bill is treated as creating a state‑mandated local program; the text separately states no constitutional reimbursement is required because it changes the definition of a crime.
Notably, the bill stops at SAE Level 3 — it does not mention Level 4 or Level 5 automation, leaving higher‑level, no‑human‑driver scenarios outside this specific definition.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Defines 'drive' to include volitional movement in SAE Levels 0–3
This provision is the substantive core: it amends the Vehicle Code so that, for listed criminal statutes, the term 'drive' covers any volitional movement when the vehicle has driving automation at SAE Levels 0, 1, 2, or 3. Practically, that means human inputs that cause movement while commonly available driver‑assist features are present count as driving for purposes of DUI, reckless driving, and related prosecutions. The section makes the SAE taxonomy the touchstone for classification rather than relying on how a manufacturer markets or labels a system.
Targets DUI, vehicular manslaughter, and reckless driving statutes
The new definition is expressly tied to gross vehicular manslaughter while intoxicated (Penal Code §191.5) and Vehicle Code offenses (23103, 23152, 23153). That linkage gives prosecutors a clear statutory basis to charge intoxication‑related crimes even when partial automation is present. Because each of those offenses carries distinct mens rea and penalty schemes, the practical effect varies: a simple DUI (23152) may be handled differently than gross vehicular manslaughter (§191.5) even if the same underlying evidence of volitional movement exists.
Imports industry standard definitions into criminal analysis
The bill delegates the technical classification of automation to SAE levels. This has two consequences: it introduces a widely used technical taxonomy that courts and investigators can reference, and it creates a moving target because SAE standards are updated over time. Disputes will likely arise over which edition applies, whether an installed feature truly meets a Level designation, and how aftermarket or partially implemented systems fit within the schema.
Declares no state reimbursement required under the California Constitution
Section 2 states that, although the bill creates or changes a crime (triggering local costs), the state need not reimburse local agencies under Article XIII B because the change concerns crimes and penalties. That is a standard drafting tack used to address constitutional reimbursement rules; it does not eliminate implementation work for local law enforcement and courts, but it signals that the state is not promising to cover those additional costs.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Prosecutors and district attorneys — the statutory definition removes a legal gap prosecutors might otherwise face when charging DUI and related offenses involving partial automation, giving them a clearer basis to allege criminal responsibility for volitional movement.
- Victims and plaintiffs in criminal prosecutions — the bill makes it easier to hold a human operator criminally accountable when movement contributed to injury or death even if driver‑assist features were active.
- Insurers and civil plaintiffs — clearer criminal attribution can strengthen subrogation claims and civil liability theories where driver conduct is at issue, simplifying parallel civil disputes.
Who Bears the Cost
- Drivers using Level 0–3 assisted‑driving systems — ordinary drivers could face criminal exposure for actions that interact with partial automation, increasing legal risk for common driving behavior assisted by technology.
- Local law enforcement and prosecutors — agencies must develop training, investigation protocols, and technical capacity to document automation modes and human inputs, imposing time and resource costs.
- Vehicle manufacturers and dealers — while the bill does not create direct regulatory duties, manufacturers may face reputational and litigation risk as consumers and prosecutors scrutinize how systems operate and are advertised.
Key Issues
The Core Tension
The central dilemma is accountability versus technological attribution: the bill strengthens the ability to hold humans criminally responsible for movement when driver assistance is present, protecting public safety and victims, but it risks misallocating blame where system behavior — not human intent — primarily caused movement, and it forces courts to translate a technical standard (SAE levels) into legal fault without settled rules for doing so.
The bill resolves an evidentiary opening — tying criminal responsibility to human‑initiated movement in partially automated vehicles — but it pushes several practical and doctrinal questions into implementation. First, proving 'volitional movement' will often be a fact-intensive task: prosecutors must show what human inputs occurred, whether the driver intended movement, and how the automation responded.
Current vehicle data recorders, telematics, and ADAS logs will become key evidence, but access, standardization, and admissibility of that data vary. Second, the statute adopts SAE levels as the determinative taxonomy.
That simplifies classification in theory but imports an industry standard that evolves; courts will face disputes over which SAE edition applies and whether an OEM feature matches a level on paper versus in field operation.
Third, the bill’s explicit cutoff at Level 3 leaves a legal gap for Level 4 and 5 systems. That may be intentional — distinguishing partial automation (where human responsibility remains plausible) from high‑automation systems — but it also creates edge cases for vehicles that intermittently operate across levels or for software updates that change a vehicle’s capabilities.
Finally, the provision increases prosecutorial clarity but risks criminalizing borderline conduct where the human contribution to movement is minimal; courts will need to calibrate 'volitional' so the statute does not sweep in accidental or reflexive inputs.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.