Last updated: August 24, 2026
By: LA Injury Lawyers Editorial Team
Determining liability following a robotaxi crash in Los Angeles depends on the root cause of the accident rather than the mere lack of a human operator. Responsibility may lie with the autonomous vehicle operator, another motorist or road user, the manufacturer, the vehicle owner, a maintenance contractor, or an alternative entity. To establish fault, critical forms of evidence must be analyzed, including sensor logs, trip details, automated driving system status, video recordings, physical vehicle inspection data, and remote assistance transcripts.
Such collisions present a distinct challenge regarding evidence preservation: while the driverless vehicle itself holds the most comprehensive record of the crash, this crucial data remains outside the control of the injured individual. Furthermore, these incidents can involve a variety of affected parties—including robotaxi occupants, pedestrians, bicycle riders, motorcyclists, or operators of other vehicles—each presenting a unique perspective and navigating distinct insurance frameworks.
To prevent the alteration or loss of camera files, electronic logs, and physical vehicle evidence, a Los Angeles electric vehicle and scooter accident lawyer can issue targeted data preservation demands immediately following the incident.
Regulatory Approval Does Not Decide Civil Fault
To regulate autonomous-vehicle operations and passenger services, California relies on distinct oversight frameworks. The California DMV issues testing and deployment permits to manufacturers under specific operational conditions, whereas the California Public Utilities Commission oversees autonomous passenger-service initiatives.
For example, the Waymo authorization history maintained by the DMV details geographic and platform expansions, including its rollout in Los Angeles in January 2024. While these records provide necessary regulatory context, they do not establish or disprove liability for any specific crash involving Waymo or other providers.
Ultimately, determining civil fault in a collision hinges on standard legal principles, including duty, conduct, causation, and damages, alongside relevant agency, product liability, or ownership regulations.
The Autonomous-Vehicle Evidence Stack
A complete investigation should preserve information at six layers:
| Evidence layer | Questions it can help answer | Examples to request or document |
|---|---|---|
| Street scene | What could each road user see and do? | Signals, lanes, crosswalks, signs, lighting, weather, construction, debris and final positions. |
| Physical vehicles | What contact occurred and were components damaged? | Crush patterns, tire marks, lights, steering, braking, sensor surfaces, restraint systems and downloads. |
| Passenger and trip record | Who requested the ride and what did the passenger experience? | App receipt, pickup and destination, route, timestamps, support contacts, in-cabin messages and audio. |
| Automated-driving system | What system was engaged and what did it detect or command? | Mode and state, perception objects, path plan, speed, braking, steering, alerts, disengagements and fault codes. |
| Remote operations | Did a remote assistant or operator communicate with or support the vehicle? | Requests for assistance, response time, instructions, communications and escalation logs. |
| Corporate and regulatory record | What policies, maintenance and required reports relate to the event? | Vehicle ownership, permit, maintenance, software version, prior issue reports and crash submissions. |
Not every requested item exists or is discoverable in every case. The point is to define the evidence categories before a generic request is sent.
Who May Be Responsible?
Another Driver or Road User
A human driver may have run a light, turned unsafely, opened a door, followed too closely or entered the robotaxi’s path. A pedestrian or cyclist can also be accused of contributing to the event. Ordinary traffic and comparative-fault principles remain relevant.
The Robotaxi Operator or Vehicle Owner
An operator may be investigated for fleet deployment, maintenance, monitoring, route or operational decisions. Ownership and insurance must be confirmed. The absence of a person in the driver’s seat does not mean there is no operating entity.
The Vehicle or System Manufacturer
A product theory requires evidence of a defect in design, manufacture or warnings and proof that the defect caused the collision or injury. A surprising maneuver is not, by itself, proof of a defect. Technical inspection, system records and expert analysis are usually necessary.
Maintenance, Mapping or Component Providers
Maintenance providers, fleet contractors or component suppliers may be relevant if their work caused the problem. A map or software vendor should not be named merely because its technology was used; the investigation must connect a specific act or defect to the crash.
A Public Entity or Road Contractor
Construction, signal failure, road design, or a dangerous property condition can create a separate claim. Public-entity claims require exact ownership, legal elements, and shorter claim deadlines.
An experienced Los Angeles car accident lawyer should build the party map from evidence rather than assuming the robotaxi company is the only defendant.
What to Do at the Scene
- Call 911 when appropriate and obtain medical care. Report that an autonomous vehicle was involved.
- Identify the robotaxi. Photograph the vehicle number, plate, make, model, and exterior from safe positions.
- Capture the full scene. Record traffic controls, lanes, approach paths, crosswalks, lighting and vehicle positions.
- Save the trip. A passenger should screenshot the app, receipt, route, pickup, destination, support chat and any on-screen message.
- Find cameras and witnesses. Nearby vehicles, businesses, homes and transportation infrastructure may hold video.
- Avoid technical speculation. Describe observations such as movement, sounds and signals. Do not guess about software failure.
- Preserve the vehicle and data. Send a request identifying the precise event, data layers and time window.
Passenger, Pedestrian and Other-Driver Claims Differ
Injured Robotaxi Passenger
A passenger is often not responsible for operating either vehicle. The claim may involve the robotaxi’s passenger-service coverage, another driver’s policy or both. Preserve seat position, restraint use, in-cabin messages and every insurer contact.
Pedestrian or Cyclist
Visibility, crossing location, signal phase, detection and planned path can become central. Preserve clothing, bicycle or device damage, helmet, phone data and witness observations.
Driver of Another Vehicle
The defense may compare the driver’s testimony with video and system logs. Preserve dashcam, vehicle data, phone records, damage, and the first statements made at the scene.
Government Reports Are Leads, Not Verdicts
The NHTSA Standing General Order requires identified manufacturers and operators to report certain crashes involving automated driving systems. NHTSA warns that the public data has limitations and should not be used by itself to compare safety or assign fault.
California DMV also maintains manufacturer collision reports for certain autonomous-vehicle operations. A report can provide identifiers and an initial narrative, but it may be preliminary, incomplete or prepared by an interested party. Compare it with physical, digital and witness evidence.
Insurance and Damages
Potential coverage may include a robotaxi operator’s commercial or passenger-service policy, another driver’s auto policy, uninsured or underinsured motorist coverage and other policies tied to responsible entities. Coverage depends on the policy, regulatory program and facts.
A supported injury claim can include medical care, lost income, reduced earning capacity and other economic losses. Non-economic damages can address pain, suffering and loss of enjoyment of life. No responsible evaluation can estimate value from the brand or technology alone.
Deadlines and Public-Entity Issues
California commonly uses a two-year deadline for personal-injury lawsuits, but exceptions apply. A public-entity claim generally requires presentation within six months under Government Code §911.2. Contractual or policy notice requirements may also demand earlier action.
Data can disappear before any legal deadline. Preservation should begin as soon as the vehicle and operator are identified.
Why Institutional Evidence Matters to LA Injury Lawyers
LA Injury Lawyers approaches robotaxi claims as complex evidence matters involving corporate systems, insurance, and multiple technical custodians. The firm can preserve data, identify operators and policies, coordinate vehicle inspection, obtain regulatory materials and build the medical-damages record.
Managing Attorney Ashton Cohen started in securities and class-action litigation and later represented major corporations and insurance carriers in business disputes. He also served as General Counsel and strategist for a major media organization. The State Bar of California lists license #312255 as active.
His biography notes commentary appearances on Fox News, NPR, and ABC. Legal-review attribution should be added only after he reviews this article.
Start With the Data Custodians
If you were injured in a Los Angeles crash involving a robotaxi or driverless vehicle, preserve the vehicle identity, trip record, scene, witnesses and medical evidence now. Call LA Injury Lawyers at (818) 721-9333 or contact LA Injury Lawyers for a free case review. Hablamos español.
Frequently Asked Questions :
1. Is the robotaxi company automatically at fault because no driver was inside?
No. Fault depends on the conduct and cause of the collision. Another driver, road condition, operator, owner, manufacturer or contractor may be involved.
2. Can I bring a claim as a robotaxi passenger?
Potentially. Passenger claims can involve the robotaxi’s coverage, another driver’s insurance or multiple sources. Save the trip and support records.
3. Does a DMV permit prove the vehicle was safe in my crash?
No. A permit authorizes operation under regulatory conditions. It does not decide the facts or liability of a specific collision.
4. What data should be preserved?
Request trip, ADS state, sensor, video, remote-support, maintenance, software-version and regulatory-report evidence tied to the precise event.
5. Are NHTSA crash reports proof of negligence?
No. They are investigative leads with stated data limitations. Fault requires case-specific evidence.
6. How is a driverless crash different from an assisted-driving crash?
A driverless ADS may perform the driving task within its operational domain, while Level 2 assistance still requires a human driver to remain engaged. Identifying the system and mode is essential.
Legal Disclaimer
This article is for general informational purposes only and does not constitute legal, technical, safety or medical advice. Mentioning Waymo or another company does not allege fault, defect or unsafe operation. Reading this article or contacting LA Injury Lawyers does not create an attorney-client relationship. Every case depends on the evidence, law, coverage and facts.