Follow your curiosity

What discovery has been shared with you?

Start with one fact. Explore it, go deeper, then follow whichever branch catches your imagination.

Choose subjects for a surprise

Exploring any topic

Begin your discovery

Your next discovery is one click away.

Choose one or more subjects above, or leave Any Topic selected and let curiosity decide.

Technology

The Legal Framework Governing Autonomous Vehicle Liability

Quick fact

In a 2020 legal analysis, scholars suggested that under current product liability law, the maker of an autonomous vehicle's sensor or software could be held strictly liable for a crash, even if the vehicle followed all safety protocols. This is because the car acts as a product that malfunctions.

Why this is interesting

Imagine a car with no driver. If it hits a pedestrian, who is to blame—the owner, the manufacturer, or the software developer? The law is grappling with this very question.

Read the full explanation

Understanding The Legal Framework Governing Autonomous Vehicle Liability

With self-driving cars, the legal question of 'who is at fault' changes because the human driver is no longer in control. Traditional car accidents are assigned to a human driver's negligence—failing to brake, speeding, etc. But an AV's actions are determined by its algorithms, sensors, and design. So, the liability shifts from driver to the parties that created the system. This means we need new legal rules to answer: should the manufacturer be responsible if a car crashes, or should the owner be, even though they didn't drive? The emerging framework borrows from product liability law, which holds manufacturers accountable for defective products, and tort law, which deals with civil wrongs. The core idea is that whoever is best positioned to prevent the accident—usually the manufacturer—should carry the responsibility. Yet, not all accidents are due to defects; some are inevitable. This is where no-fault insurance systems might come in, pooling risk across car owners or manufacturers.

A deeper explanation

The mechanism at work is the replacement of human driving judgment with coded decision-making. In law, fault is typically based on a breach of a duty of care. With AVs, we cannot ask 'did the driver act reasonably?' because there is no driver. Instead, we ask 'did the system act as a reasonable driver would, and was the design or operation defective?' This leads to two prevailing theories: strict product liability and negligence. Strict liability holds the manufacturer liable for any injury caused by a defective product, regardless of fault, if the product is sold in a defective condition. Negligence requires proving the manufacturer failed to meet a standard of care. AV law is adopting a hybrid: for known failure modes, strict liability; for novel scenarios, negligence based on data. Additionally, the 'driver' is now partially the software, so we face the challenge of proving what the system 'intended'—a task only possible with black-box data recorders. This framework matters because it influences safety incentives: if manufacturers face liability, they'll invest more in safety, but if too harsh, it could stifle innovation. That's why jurisdictions are experimenting with no-fault insurance pools and sovereign immunity for initial deployments.

Keep FACTREE close

Internet access is required. Updates arrive when you reopen or reload the app. You may need to sign in again in the installed app.