California Vehicle Code 38750 is the backbone of the state's autonomous vehicle rules. It defines which vehicles qualify as autonomous, sets testing and deployment conditions, and creates insurance, data, and safety obligations that manufacturers and technology companies must meet. For companies operating in California's high-scrutiny environment, understanding California Vehicle Code 38750 is essential to avoid permit problems, regulatory enforcement, and unnecessary liability.

What California Vehicle Code 38750 covers

The statute applies to vehicles equipped with autonomous technology that meet SAE International Level 3, Level 4, or Level 5 automation. These levels describe how much of the driving task the system can perform and when a human must intervene. By contrast, common driver-assistance features such as collision avoidance, electronic blind-spot assistance, automated emergency braking, park assist, adaptive cruise control, and lane keeping are excluded. Correctly classifying your product avoids triggering requirements that do not apply to driver-assistance systems and focuses compliance efforts on the correct regulatory path.

The law also divides operations into two buckets: testing and deployment. Testing addresses how a manufacturer can operate vehicles on public roads during development. Deployment covers post-testing use in public settings, including when there is no human driver present. Each stage has distinct certifications, filings, and oversight, and a misstep at either stage can slow or stop a program.

Core definitions and elements under California Vehicle Code 38750

Autonomous technology. Technology capable of driving a vehicle without the operator's active physical control or monitoring. This definition is technology neutral but outcome focused.

Autonomous vehicle. Any vehicle with autonomous technology integrated into it that meets SAE Level 3, 4, or 5. Excluded systems are those that merely enhance safety or assist the driver but cannot drive the vehicle independently.

Manufacturer. Either the original vehicle manufacturer that equips autonomous technology on the OEM vehicle, or an entity that retrofits a completed vehicle to make it autonomous. This matters for who is responsible for certifications, collision reporting, and compliance filings.

Operator. For testing that uses a safety driver, the person seated in the driver's seat and able to take control immediately. For driverless operation, the “operator” is the person who causes the autonomous technology to engage.

Testing requirements under California Vehicle Code 38750

Who can test. Testing on public roads is limited to employees, contractors, or designated persons of the autonomous technology manufacturer. This limitation ties training, control, and oversight to the party most familiar with the system.

Driver presence and control. When testing with a safety driver, the driver must be licensed for the vehicle class, sit in the driver's seat, monitor the system, and be able to assume immediate manual control. Clear protocols and driver training records are key compliance artifacts.

Financial responsibility. Before testing begins, the manufacturer must maintain an instrument of insurance, a surety bond, or proof of self-insurance in the amount of five million dollars and provide evidence to the Department of Motor Vehicles in the manner the department requires.

Program documentation. The DMV's testing and driverless testing permits require detailed applications, recurring updates, and adherence to disengagement reporting, collision reporting, and other program-specific rules. Gaps in documentation can lead to permit delays or enforcement action.

Deployment approvals and ongoing obligations

Certification to deploy. Moving beyond testing requires DMV approval based on manufacturer certifications. Among other items, the manufacturer must certify that the vehicle has an accessible mechanism to engage and disengage autonomous mode, a visible status indicator, and a system that safely alerts operators when a failure is detected.

Operator control and alerts. The vehicle must allow an operator to take control via brake, accelerator, or steering inputs and must alert the operator when the system disengages. If the operator cannot take over after a failure alert, the vehicle must be capable of coming to a complete stop.

Federal safety compliance. Autonomous technology must meet applicable Federal Motor Vehicle Safety Standards for the vehicle's model year and cannot make any federal safety standard inoperative. Monitoring both federal and state rulemaking helps avoid conflicts, because federal rules supersede state provisions if there is a direct conflict.

Data recording and preservation: the litigation fulcrum

California requires an independent mechanism to capture and store autonomous technology sensor data for at least 30 seconds before a collision while the vehicle operates in autonomous mode. That data must be recorded in a read-only format and preserved for three years after the collision date. In practice, this data is often the most important evidence in civil litigation, regulatory inquiries, and internal incident reviews. Companies should implement clear data retention, access, and chain-of-custody policies that preserve privilege where appropriate.

Zero-emission rule for future deployment

Beginning January 1, 2030, autonomous vehicles with model year 2031 or later and a gross vehicle weight rating under 8,501 pounds must be zero emission to qualify for deployment permits, to the extent authorized by federal law. This requirement does not apply to testing, but it should influence long-range product planning, supplier selection, and infrastructure strategy.

Penalties, exposure, and where companies face risk under California Vehicle Code 38750

Most enforcement pressure comes through permits and program oversight rather than traditional criminal penalties. The DMV can impose additional requirements for driverless operations, suspend or revoke authorizations, and mandate a safety driver if necessary for safe operation. Parallel oversight by the CPUC may apply for commercial passenger service. Operationally, the biggest risks are unreported collisions, gaps in disengagement reporting, lapses in insurance or bond coverage, and failures in data preservation.

Civil exposure also intersects with traditional tort and product theories. Depending on the facts, litigation may involve negligence, design defect, and failure-to-warn allegations, along with regulatory noncompliance as evidence of breach. Companies should plan for coordinated defense of administrative actions and civil suits, particularly where plaintiff's counsel attempts to convert regulatory filings into admissions.

Defense strategies that work

Map the technology to the statute. Start by documenting whether your system qualifies as Level 3, 4, or 5. If a product is limited to driver-assistance, memorialize why it is excluded and build internal controls around marketing, owner's manuals, and disclosures to prevent overstatement of capabilities.

Prove driver readiness. For testing, build training curricula, maintain sign-in sheets, and make sure drivers rehearse takeovers and failure modes. Written testing protocols and simulator or closed-course records can be persuasive in regulatory reviews and litigation.

Harden HMI and failure-handling. Collect evidence that engagement, disengagement, and alert mechanisms function as required and that the vehicle will safely stop if human takeover does not occur. Track changes with engineering release notes and test reports.

Insurance, bond, or self-insurance selection. Choose the financial responsibility instrument that aligns with your risk profile and capital structure, and calendar renewals and financial triggers. Maintain an auditable trail of policy issuance, endorsements, and DMV submissions.

Data governance. Build a litigation-ready process for data recorder extraction, preservation, and analysis. Limit access, maintain hash values where appropriate, and document every touch. Consider privileged post-incident reviews to separate safety learnings from discoverable analyses.

Coordinate state and federal compliance. Track NHTSA and California DMV rulemakings. When conflicts arise, prepare a preemption analysis and adjust certification language, validation testing, and field operations accordingly.

Related compliance issues manufacturers should anticipate

Autonomous operations often intersect with other exposure areas. If a collision or system malfunction leads to consumer injury claims, counsel should be prepared to address product liability exposure in parallel with regulatory defenses. For events that draw prosecutorial scrutiny, develop internal protocols to assess and mitigate corporate criminal liability risks. Operational issues on public streets can also lead to local abatement or enforcement disputes, so teams should be ready for defending against nuisance actions where necessary. Finally, complex supplier relationships and fleet contracts should be reviewed for fairness; in the right case, unconscionable contract defenses can be a pressure valve in negotiations or litigation.

Process timeline: what to expect

Internal assessment. Classify the technology, map requirements, and identify gaps. Decide whether your next phase requires a drivered testing permit, a driverless testing permit, or a deployment permit.

Application assembly. Prepare the DMV application with required certifications and supporting evidence. Align insurance or bond instruments with the program's start date and keep copies in every test vehicle.

Pilot operations and reporting. Conduct public-road testing under documented protocols. Capture and retain disengagements and collision data. Submit required reports on time.

Scaling and deployment. Before expanding, verify that all certifications remain accurate and that software updates have not introduced new risks. For driverless service, incorporate any DMV-imposed conditions, including potential requirements to place a trained driver in the vehicle for designated scenarios.

Practical guidance for in-house teams

• Centralize AV compliance with a cross-functional committee spanning engineering, legal, safety, and public policy.
• Use a single source of truth for permits, training records, insurance or bond documents, and regulatory submissions.
• Run incident tabletop exercises that include data extraction, counsel notification, and media protocols.
• Update owner communications and manuals to precisely describe capabilities and limits consistent with California Vehicle Code 38750 and DMV regulations.
• Integrate the zero-emission deployment rule into product planning and supply-chain decisions now.

California Vehicle Code 38750 FAQs

Does the law cover driver-assistance features? No. Features like adaptive cruise control and lane keeping are specifically excluded, so long as they cannot drive the vehicle without human control or monitoring.

Is five million in coverage always required? For testing and deployment, the manufacturer must maintain five million dollars in financial responsibility through insurance, a surety bond, or self-insurance and provide evidence to DMV as required by regulation.

How long must collision data be saved? Three years after a collision, with at least 30 seconds of pre-collision sensor data captured by a separate, read-only recording mechanism.

What about federal rules? Vehicles must meet applicable Federal Motor Vehicle Safety Standards. If a direct conflict arises, federal rules supersede state provisions.

California Vehicle Code 38750 lawyers in California

If your company is developing, testing, or deploying autonomous vehicles in California, Bulldog Law can help. Our team understands California Vehicle Code 38750, DMV permitting, data-recording obligations, and the fast-changing regulatory landscape. We build proactive compliance frameworks, respond to investigations, and defend complex civil and regulatory matters so your program can keep moving.