Who Is Liable in a Self-Driving Car Accident? (2026)

Who is liable in a self-driving car accident depends on who, or what, was driving. If a human was supposed to be supervising a driver-assist system, that person usually stays the driver in the eyes of the law, and the maker can still face a product claim. If no human was driving, as in a robotaxi, claims generally run against the company that operates the vehicle and the companies that built it, and the state statute that calls the software the "driver" is mostly a traffic-law rule, not a rule about who pays.

Scope: This page covers civil liability for crashes involving driver-assist and automated driving systems under US state law and the federal court record as of September 2026. It does not cover criminal defense, workers' compensation, or countries outside the United States. It is general legal information, not legal advice.

Who is liable in a self-driving car accident? A decision path by automation level

"Self-driving" covers very different products. The industry sorts them into levels, and the level tells you where the human sits in the picture. Statutes rarely use marketing names; they use terms like "operator," "driver," or "automated driving system."

None of this is a substitute for the facts of a particular crash. It is a map of where the legal arguments start.

Level 2: the human stays the driver, and the maker can still be liable

A Level 2 system steers or brakes, but the person behind the wheel is expected to watch the road and take over. California's statute draws that line in its definition. It defines an "autonomous vehicle" as one that meets the definition of SAE Level 3, 4 or 5, and excludes vehicles with collision avoidance systems that are "not capable, collectively or singularly, of driving the vehicle without the active control or monitoring of a human operator." A Level 2 car falls outside the autonomous vehicle statute, so the ordinary rules for drivers apply.

That does not end the manufacturer's exposure. A leading example is Benavides v. Tesla, a 2019 Key Largo, Florida crash involving a Tesla Model S with Autopilot. The driver, George McGee, hit a parked Chevrolet Tahoe, which then struck Naibel Benavides Leon and Dillon Angulo, killing Benavides Leon and injuring Angulo. The plaintiffs' claims against Tesla included strict-liability design defect and failure to warn.

The jury found for the plaintiffs on both claims and found Tesla liable for punitive damages. It awarded $59 million and $70 million in compensatory damages, but found Tesla only 33 percent responsible; Tesla's own SEC filing describes the jury as finding the driver 67 percent at fault. The final judgment totaled $242,570,000: $19.47 million and $23.1 million in reduced compensatory damages plus $200 million in punitive damages.

Two cautions. First, that is one jury in one case, and a verdict is not a holding that binds other courts. Second, Tesla's appeal (Eleventh Circuit No. 26-10858) is pending; Tesla's SEC filing says it filed its opening brief on July 2, 2026, and no decision has been reported, so the amounts can change. Tesla's SEC filing says the company does not believe the facts and law justify the damages awarded.

Human backup drivers of automated test vehicles face exposure too. In 2023, the safety driver of an Uber self-driving test vehicle, which was being controlled by its automated driving system when it killed a pedestrian in Tempe, Arizona in 2018, pleaded guilty to endangerment and received three years of supervised probation. That prosecution was criminal, not a civil liability ruling. The county attorney said the defendant "was responsible for the operation of a vehicle on our city streets that ended with a woman being killed."

For more on Tesla cases, see Tesla Autopilot and FSD lawsuits.

Level 3: who is responsible at the handoff?

Level 3 is the murkiest category. The system may drive in limited conditions, but a human is expected to be ready to take over when it asks. Few state statutes address it directly.

Utah does. It allows a motor vehicle with a Level 3 automated driving system to operate on a highway if it is operated, "whether by the ADS or human driver with a valid driver license," in compliance with traffic laws, and if a system failure will lead the system to reach a minimal risk condition or "make a request to intervene." Utah's definitions call the human a "fallback-ready user," someone with a valid license who is ready to operate the vehicle if a system failure occurs or the system issues a request to intervene.

Those provisions govern when a Level 3 vehicle may operate and who must comply with traffic law. By their terms they do not say who pays after a crash. In California, where a Level 3 vehicle needs a DMV-approved deployment, the "operator" is still the person in the driver's seat, or, if nobody is seated there, the person who causes the technology to engage.

In practice, a Level 3 dispute often turns on timing: did the system request a takeover, how much warning did the human get, and what did the vehicle's logs record. Those are questions for the evidence, discussed below.

Fully driverless robotaxis: when there is no human driver

With no human in the driver's seat, the question shifts from "which driver was at fault" to "which company answers for the vehicle."

Statutes that make the software the driver

Several states say an engaged automated driving system is the driver or operator. These statutes are framed around traffic and motor vehicle law, and none of them says who pays for an injury:

• Arizona: the system is considered the driver or operator "for the purpose of assessing compliance with applicable traffic or motor vehicle laws." The same section says the operation of autonomous vehicles, with or without a human driver, "is subject to all applicable federal and state laws," and that the person who submitted the required statement for a fully autonomous vehicle may be issued a traffic citation.
• Florida: the system, when engaged, is deemed the operator for purposes of the traffic chapter (Chapter 316), whether or not a person is physically present.
• Michigan: a system allowing operation without a human operator is considered the driver "for purposes of determining conformance to any applicable traffic or motor vehicle laws." The statute adds that an automated vehicle roadway system provider is not an operator.
• Texas: under Transportation Code chapter 545 as amended by SB 2807 (2025), the system is the operator of the vehicle "including for purposes of assessing compliance with applicable traffic or motor vehicle laws," while a citation goes to the owner or, for a fleet operating under a TxDMV authorization, the authorization holder. After a collision, the vehicle, a person on its behalf, or any human driver must comply with the crash-duty rules in Chapter 550.

Read those texts closely. A rule that says who receives a ticket is not a rule that says who owes money to an injured person. The operator provisions quoted above do not themselves allocate fault for an injury claim, and Arizona's provision that autonomous vehicle operation "is subject to all applicable federal and state laws" leaves the rest of state law, which includes negligence and product liability law, in place.

Other states name different responsible parties. Pennsylvania's certificate holder of a highly automated vehicle is considered a driver for compliance with the vehicle code (75 Pa.C.S. 8510.1(a)(1)). Where a state has no autonomous vehicle statute, its silence on driverless operation answers none of these questions either way. The hub page, self-driving car laws by state, covers the state-by-state picture.

Michigan: a statute that makes the manufacturer assume liability

Michigan's SAVE project statute is a rare example of a state making a company assume liability. For each SAVE project in which it participates, a motor vehicle manufacturer, while the automated driving system is in control of a fleet vehicle, "shall assume liability for each incident in which the automated driving system is at fault," subject to the state's no-fault insurance chapter (MCL 500.3101 to 500.3179). The same statute requires the manufacturer to insure each fleet vehicle under the no-fault act.

That rule applies to SAVE projects, not to every automated vehicle in Michigan, and it is limited by the no-fault system. Some states allocate liability in a narrower way: Florida, for example, shields an original manufacturer from claims over defects created when a third party converts its vehicle into an autonomous vehicle, unless the defect was present as originally manufactured.

Negligence and product claims against the operator and maker

Without a statute that assigns liability to a particular party, an injured person's claims usually take two forms.

Negligence asks whether someone failed to use reasonable care: for example, a company that deploys a vehicle with known problems, maintains it poorly, or operates it in conditions outside its design limits. The defendants can include the fleet operator that owns and runs the vehicles.

Product liability asks whether the product itself was defective in design, manufacture or warnings. In Benavides, the claims that reached the jury were design defect and failure to warn, while manufacturing defect and negligent misrepresentation claims were dismissed before trial. Florida's comparative fault statute defines a negligence action to include actions based on negligence, strict liability or products liability, so fault is apportioned under the same statute whichever theory is pleaded.

In a driverless-fleet crash the operator and the manufacturer may be the same company, as with a company that builds and runs its own vehicles, or different companies. Elements and defenses vary by state.

What insurance stands behind a robotaxi

A claim is only as useful as the money behind it. Several states set financial requirements for driverless vehicles:

• California: a manufacturer testing autonomous vehicles must obtain insurance, a surety bond or proof of self-insurance of $5,000,000, and the deployment application certifies the manufacturer will maintain the same amount.
• Florida: a fully autonomous vehicle with the system engaged while logged on to an on-demand network or engaged in a prearranged ride must be covered by a policy with primary liability coverage of at least $1 million for death, bodily injury and property damage, plus personal injury protection and uninsured and underinsured coverage.
• Pennsylvania: a certificate holder must maintain the ability to respond in damages of at least $1,000,000 per accident for death, bodily injury and property damage to a third party (75 Pa.C.S. 8508(f)(1)).
• Arizona: the written statement for a fully autonomous vehicle acknowledges that the vehicle meets the state's existing insurance requirements, rather than setting an AV-specific dollar figure.

A state minimum is a floor, not a cap on what a court can award, and testing requirements differ from requirements for carrying passengers. Compare each state's statute for its trigger.

Comparative fault: why one crash can have several responsible parties

Most crashes involve more than one contributing cause. Under comparative fault rules, a jury assigns percentages of fault and the damages are divided accordingly. Florida's statute directs the court to enter judgment against each party on the basis of that party's percentage of fault, and, for cases filed after March 24, 2023, provides that a party found more than 50 percent at fault for his or her own harm may not recover any damages (medical negligence cases excepted). Benavides was filed in 2021 under the earlier pure comparative fault rule, and the plaintiffs there were not assigned fault.

That is how Benavides produced a compensatory award cut to a 33 percent share. The 67 percent belonged to the driver, not to the injured plaintiffs. The $200 million punitive award in the judgment was not scaled to that percentage. Other states use different comparative fault rules, so the same facts can produce a different split elsewhere.

For Level 2 crashes this often means the driver, the manufacturer and sometimes another motorist or a road owner each carry a share. For general crash rules in your state, see the car accident law hub.

If you were a robotaxi passenger: what the rider terms say

A rider who books through the app accepts the operator's terms. Waymo's terms also say a guest riding in a trip someone else requested agrees to be bound by using the service, and make the account holder responsible for getting guests to agree; whether that binds a guest who never saw the terms is a question for a court. Waymo's terms, last updated September 22, 2026, illustrate what to look for. These are the company's own statements, and terms change, so check the version you accepted.

• Arbitration: the terms provide that disputes will be resolved through confidential binding arbitration under the JAMS Streamlined Arbitration Rules and Procedures, on an individual basis and not as a class action.
• A one-year deadline: any demand for arbitration "MUST BE MADE WITHIN ONE YEAR OF DISCOVERY OF THE CLAIM; OTHERWISE, THE CLAIM IS PERMANENTLY BARRED." That is a contract deadline, and it can be shorter than the state statute of limitations for personal injury. See the statute of limitations by state for the statutory window.
• A 30-day opt-out: a rider may opt out of binding arbitration within thirty days of first accepting the terms, by emailing the address the terms specify. The clock starts at first acceptance, not at the crash.
• Cost and carve-outs: a rider who starts arbitration pays JAMS filing fees up to $250 and Waymo pays the other JAMS costs. Small claims, certain intellectual-property disputes, and individual claims arising from sexual assault or unwelcome sexual behavior by a Waymo agent or employee are carved out. A crash injury claim is not listed as a carve-out.
• The liability cap: the terms cap Waymo's liability at the amount paid for the ride, but state that the cap does not limit liability for gross negligence, or for personal injury or property damage to the extent caused by Waymo's negligence or a defect in its services.

Whether a court would enforce the arbitration clause or the one-year window against a passenger's injury claim, or against a family member bringing a wrongful death claim, is a legal question this page does not resolve. A lawyer licensed in the rider's state can assess it. Other operators, including Zoox and Tesla's Robotaxi service, have their own terms, and the description above should not be assumed to apply to them.

If you were not in the robotaxi: pedestrians, cyclists and other drivers

A pedestrian, cyclist or driver of another car who is hit by a robotaxi never opened the company's app or accepted its terms. Rider terms are an agreement between the company and the rider, so the arbitration clause, the one-year window and the ride-price cap are not agreements the injured outsider made.

That does not mean a claim is easy. The same negligence and product theories apply, the state deadline for personal injury still runs, and the operator's insurance and the state's financial requirements shape what can be collected. It only means the contract defenses that come from the rider agreement are different for someone outside the vehicle.

For Waymo-specific crash reports and claims, see Waymo and robotaxi accidents.

Evidence in an automated vehicle crash

Automated vehicles generate more data than a conventional car, and that data often decides fault.

Vehicle data. Under the Driver Privacy Act of 2015 (section 24302), data retained by an event data recorder is the property of the vehicle's owner, or the lessee of a leased vehicle. The Act says the data may not be accessed by anyone else unless a court or other authority authorizes retrieval, the owner or lessee consents, or another listed exception applies. For a personal car, that owner is you. For a fleet vehicle, it is the fleet's owner or lessee, which is often but not always the company operating the service, so an injured third party generally needs that company's cooperation or a legal process to reach it. The Act covers event data recorders as defined in federal regulations; cameras, sensor logs and software records are separate questions.

NHTSA crash reports. Under NHTSA's Standing General Order, the manufacturers and operators it names must report certain crashes involving an automated driving system or a Level 2 driver-assist system to NHTSA. Reportable crashes include those where any person is taken to a hospital, a fatality, an air bag deployment, or a strike of a vulnerable road user, and the system must have been engaged at or within 30 seconds of the crash. According to NHTSA's notice, the order imposes no reporting obligations on individual consumers. It is a reporting tool for the regulator, not a claims process, and a company's report is one piece of evidence rather than a finding of fault.

Camera and app records. Robotaxis carry cameras, and rideshare apps keep trip records. Whether those records exist, who holds them, and how long they are kept varies by operator. For the privacy side, see do robotaxis record you.

What to do after a self-driving car accident

The steps below are general information, not legal advice, and they apply whether the car was a driver-assist vehicle or a robotaxi.

1. Get safe and get medical care. Call 911 for injuries. Injuries that seem minor at the scene are easier to document if they are evaluated promptly.
2. Call the police and get a report number. Say that an automated or driver-assist system may have been involved, if you know it.
3. Identify the vehicle and the operator. Photograph the vehicle, its company name, any fleet or vehicle number, and the license plate. For a driver-assist crash, note the make, model and whether the system was on.
4. Document the scene. Take photos and video of vehicle positions, damage, traffic signals, road markings and injuries. Get names and contact details for witnesses.
5. Ask that data be preserved. A written preservation request to the vehicle owner or operator, which a lawyer can send, asks them to keep logs, video and other records. Records can be overwritten or deleted on a routine schedule.
6. Save the paperwork. If you were a passenger, keep the app receipt, trip details, and a copy or screenshot of the terms you accepted. Note the date you first accepted them, since some terms have opt-out windows.
7. Report to your insurer, and read before you sign. Notify your own insurer as your policy requires. Be careful with releases or recorded statements from another party's insurer before you understand your options.
8. Check the deadlines. State statutes of limitations differ, and a contract deadline in rider terms can be shorter. Read the statute of limitations page for your state's window.

Self-driving crashes involve overlapping product, negligence and contract questions, and the deadlines can be short. If you want your situation reviewed, you can request a case review.

Related topics

Liability for the ticket is a separate question from liability for the crash; see can a self-driving car get a ticket. For a driver charged with impaired driving in a car that was driving itself, see DUI in a self-driving car. The federal layer, including NHTSA's role, is covered in federal self-driving car laws.

Frequently Asked Questions

Who is at fault in a self-driving car accident?

It depends on the level of automation and the facts. In a Level 2 driver-assist car, the human is still the driver, and the manufacturer can also face a product claim. In a driverless robotaxi, claims generally run against the fleet operator and the companies that built the vehicle. Fault can be shared between several parties under comparative fault rules.

Can I sue Tesla if Autopilot or FSD was on during my crash?

A jury in Benavides v. Tesla found Tesla liable for design defect and failure to warn in an Autopilot crash, but assigned Tesla 33 percent of the responsibility and the driver the other 67 percent. That verdict is on appeal and does not bind other courts. Whether a claim works depends on the facts, the state and the evidence, and a lawyer can assess it.

If a Waymo hits me and I was not a passenger, do I have to arbitrate?

Waymo's arbitration clause and one-year window are in its rider terms, an agreement between the company and the rider who accepted it. Someone outside the vehicle never accepted those terms. The state's ordinary personal injury deadline still applies.

If I was a passenger in a robotaxi, can I still go to court?

Waymo's terms, as of September 22, 2026, require individual arbitration for most disputes, with a 30-day opt-out from the date you first accepted them, and a one-year deadline to demand arbitration. Whether a court would enforce those terms against an injury claim is a legal question. Do not assume either way; get advice for your state.

Does the law that calls the software the driver make the company liable?

Not by itself. Arizona, Florida and Michigan make an engaged automated driving system the driver or operator for traffic-law purposes. Texas, since SB 2807 (effective September 1, 2025), makes the system "the operator of the vehicle, including for purposes of" traffic-law compliance. None of these operator provisions says who pays for an injury. Michigan's SAVE project statute is a notable exception that has a participating manufacturer assume liability for incidents where the system is at fault.

Who pays for a robotaxi crash, the company or its insurer?

Claims against a robotaxi operator are typically backed by its insurance or self-insurance. Some states set minimums, such as $1 million in Florida and Pennsylvania for covered driverless operations and $5 million in California for manufacturers testing autonomous vehicles. The amount available depends on the state, the operator and the policy.

Who is liable when no human was driving?

A driverless vehicle is owned or operated by a company or an individual, and the owner or operator is commonly the first party a claim is directed to. Some statutes, such as Texas's, direct citations to the owner or authorization holder. For a personal Level 2 car, the owner and the driver are typically the same person.

Who has the vehicle's crash data?

Under the Driver Privacy Act of 2015, data retained by an event data recorder belongs to the vehicle's owner or lessee. Others generally need consent, a court or other authority's authorization, or another exception in the Act. For a fleet vehicle, the owner or lessee is often the company running the service, so a written preservation request early on can matter.

How long do I have to bring a self-driving car accident claim?

The statute of limitations for personal injury varies by state. If you were a robotaxi passenger, the rider terms may also set a shorter contractual deadline; Waymo's terms use one year from discovery of the claim for arbitration demands. Check both, and see the statute of limitations page for your state.