The legal classification begins with the automation level
If an automated vehicle physically injured you, the first question is what technology was actually controlling the vehicle. Vehicle Code § 38750 defines an autonomous vehicle using higher levels of driving automation and excludes many driver-assistance features that still require active human control or monitoring. Marketing terms such as self-driving, autopilot, or driverless do not by themselves establish the vehicle's legal classification.
A vehicle may have been operating manually, using partial assistance, testing autonomous technology with a safety driver, or providing a deployed driverless service. The answer affects whose decisions and records matter. Your photographs, ride receipt, fleet number, plate, witness observations, and any statement about automated mode can anchor the inquiry before the operator or manufacturer supplies technical information.
Responsibility may be divided between people and technology companies
A human driver may remain responsible for monitoring and taking control when the system requires it. A person who causes autonomous technology to engage may qualify as an operator under California law even without sitting in the driver's seat. A fleet company may control dispatch, remote assistance, maintenance, route restrictions, and operational policies, while a manufacturer or supplier may control software, sensors, braking, steering, or other components.
Another motorist, cyclist, pedestrian, road contractor, or public entity may also contribute to the event. The presence of autonomous technology does not automatically make the manufacturer responsible, and a traffic citation issued to another road user does not automatically eliminate a system-related claim. Each theory should connect specific conduct, data, or a product condition to the collision and your physical injury.
Automated driving can produce unusually detailed evidence
Autonomous systems may collect camera, lidar, radar, positioning, speed, braking, steering, mapping, object-classification, and remote-assistance information. Vehicle Code § 38750 requires specified autonomous technology to capture and store sensor data for at least 30 seconds before a collision in autonomous mode and preserve that data for three years. The statute's application depends on the vehicle and approved operation.
Other useful records may include software versions, update history, safety-driver actions, disengagement reports, maintenance, recalls, testing permits, passenger app data, and communications with a remote operations center. Those records are usually controlled by companies rather than the injured person. A focused preservation request should identify the correct vehicle, time, location, service, and potential data sources without assuming that every system stores the same information.
The law is developing, but your injury claim still needs clear proof
California's autonomous-vehicle statutes and DMV regulations continue to develop alongside federal safety standards and local operational concerns. New technology does not remove the need to prove duty, causation, physical injury, and legally recognized losses. It can, however, create several defendants, technical experts, insurance layers, and competing explanations involving human behavior, system limits, road conditions, or product performance.
A public road design or government-operated vehicle can add the claim-presentation period in Government Code § 911.2. Product-related and ordinary negligence paths may follow different evidence and deadline rules. Prompt review can identify the automation level, preserve sensor and fleet data, separate driver conduct from system performance, and evaluate coverage while keeping the claim centered on your medical needs and documented bodily injury losses.