Who Is Liable When a Driverless Car Causes a Crash?
Self-driving and semi-autonomous vehicles are already sharing Utah roads, and they raise a question the law is still catching up to: when a car with no human at the wheel causes a crash, who is responsible? The short version is that liability does not disappear. It shifts.
When a driverless or automated vehicle causes a crash, liability can fall on the human operator, the vehicle or software manufacturer, the company operating the fleet, or a maintenance provider, often more than one at once. The key questions are whether the automation failed, whether a human was supposed to be supervising, and whether a defect was involved. These cases blend traditional negligence with product liability.
“Driverless” is not one thing
Automation comes in levels. Most vehicles on the road today offer driver-assistance features such as adaptive cruise control, lane keeping, automated braking that still require a human to pay attention and take over. A smaller number of vehicles operate with much higher automation in limited conditions. Where a crash falls on that spectrum matters enormously, because it changes who had the duty to prevent it.
- Driver-assist systems. The human is still responsible for supervising and can be at fault for over-relying on the technology.
- Conditional automation. The car drives itself in some settings but expects the human to resume control when prompted.
- High automation. The system handles driving within a defined area, shifting more responsibility to the maker or operator.
- Fleet vehicles. Robotaxis and delivery bots add a company operator into the liability picture.
Where responsibility can land
A crash involving automation can involve several potentially responsible parties. Untangling them usually requires the vehicle’s data, the software’s decision logs, and an understanding of what the human was doing at the time.
| Party | When they may be liable | Claim type |
|---|---|---|
| Human operator | Ignored a takeover prompt or misused driver-assist | Negligence |
| Vehicle or software maker | The automation malfunctioned or was defectively designed | Product liability |
| Fleet operator | Poor maintenance or unsafe deployment of the vehicle | Negligence |
| Component supplier | A faulty sensor or part caused the failure | Product liability |
Key point. Automation does not erase the right to be compensated for an injury someone else’s technology caused. It simply means the responsible party may be a corporation rather than a driver, and proving the case can require access to data most crash victims never see without a lawyer’s help.
Why these claims are different from an ordinary crash
An ordinary car crash usually comes down to what two drivers did. A driverless-car case can turn on software behavior, sensor readings, and internal design decisions. That means the evidence lives inside the vehicle and the manufacturer’s systems, and the opposing party is often a well-funded company with lawyers of its own. Product liability principles, which allow claims when a product is defective or unreasonably dangerous, frequently come into play alongside traditional negligence. Utah’s comparative fault rules still apply, so more than one party can share the blame.
What to do if a driverless car hits you
Call police and get medical care
Treat it like any serious crash: report it, get an official record, and see a doctor even if you feel okay.
Identify the vehicle and operator
Note the company name, any fleet markings, the vehicle identifiers, and whether a human was inside or supervising.
Preserve the evidence
Photograph the scene and the vehicle. The car’s data may be critical, and a lawyer can act quickly to keep it from being lost.
Get legal help early
Because a manufacturer or fleet operator may be involved, talk to an attorney before dealing with the company’s insurer or investigators.