06 March 2026
Automated vehicles are revolutionizing our mobility, presenting insurers and vehicle manufacturers with a pivotal question: Who will be held liable in the event of a claim?
Under current law, the keeper of an automated vehicle remains the central liable party. Their liability stems from Art. 58 of the Road Traffic Act (RTA). According to this provision, the vehicle keeper is strictly liable for personal injury and property damage caused by the operation of the motor vehicle.
Pursuant to the RTA, there is a compulsory insurance requirement for motor vehicles used in public traffic (Art. 63 para. 1 RTA). An injured third party (e.g., a road traffic victim) can bring a claim against the vehicle keeper or directly against their insurer (Art. 65 para. 1 RTA). Typically, the road traffic victim (or their own property damage insurer) will proceed against the keeper's solvent liability insurer.
The vehicle keeper's liability insurer is jointly and severally liable with third parties who are liable to the injured party under contract, law, or tort (Art. 51 Code of Obligations [CO]). Once the insurer has settled the claim, it has two recourse options:
Driverless vehicles, as defined by the Ordinance on Automated Driving (OAD), are, as the name suggests, designed for operation without a driver. The vehicle occupant is not required to take control. They are therefore not liable for damage caused by the vehicle. If they suffer damage themselves, they can submit their claims directly to the keeper's liability insurer. If the automated vehicle is operated by a transport company, the vehicle occupant may be able to assert claims under a contract of carriage.
With increasing automation and the growing control of vehicles by automation systems, the liability of drivers will increasingly fade into the background, while the liability of manufacturers is likely to gain importance (cf. Dispatch on the amendment of the RTA, BBl 2021 3026, p. 40). In the future, other parties such as importers and garages could be interposed between the vehicle keeper and the manufacturer. For the sake of clarity, these are not considered in this article. The future development, particularly in the private use of driverless vehicles, remains to be seen.
The manufacturer's liability is primarily based on the PrLA. The manufacturer is liable for damage caused by a defective product (Art. 1 in conjunction with Art. 4 para. 1 PrLA). A product is considered defective if it does not provide the safety that a person is entitled to expect. Under the PrLA, the vehicle manufacturer, its suppliers (manufacturers of a component part), and importers are to be qualified as manufacturers.
However, product liability law does not grant claims for damage to the defective vehicle itself. Furthermore, the vehicle manufacturer is not liable under the PrLA for damage to commercially used property or for pure financial losses. The vehicle keeper or other injured parties must therefore assert such claims on other grounds:
If suppliers are also responsible for damage alongside the vehicle manufacturer, they are jointly and severally liable to the injured party (Art. 2 para. 1 lit. a in conjunction with Art. 7 PrLA). The Product Liability Act does not provide specific rules for recourse between the manufacturer of the final product and the manufacturer of a component part. The general provisions of the Code of Obligations apply (Art. 50 para. 2 and Art. 51 CO).
A supplier's liability is established if a component supplied by them has a defect within the final product and this defect causes personal injury or property damage.
In the context of automated vehicles, manufacturers of cameras, sensors, radar-, and lidar-systems, for example, are to be classified as classic suppliers within the meaning of the PrLA. According to the revised EU Product Liability Directive (Art. 4 No. 1) and the prevailing doctrine in Switzerland, software is also considered a product, meaning its manufacturers fall under the PrLA.
If a software becomes defective after market launch due to an over-the-air update deployed by the software supplier, the software supplier is responsible under the PrLA for any resulting property damage and personal injury.
The extent to which liability for software errors or for errors during the installation of updates is regulated between the vehicle manufacturer and the software supplier depends primarily on their contractual agreements (quality assurance agreement, exclusion and limitation of liability, assumption of risk).
The operator is a new figure in road traffic law. They monitor driverless vehicles, interact with them, and communicate with the vehicle occupants if necessary (Art. 34 para. 2 OAD). Since the law does not provide for special civil liability for the operator and they will often be in an employment relationship with the keeper, their culpable conduct could be attributed to the keeper as an associate.
Injured parties typically turn directly to the vehicle keeper's liability insurer. The insurer, in turn, examines recourse against the keeper or the manufacturer. The manufacturer, in turn, can take recourse against its suppliers.

When an automation system takes over the driving task, the criminal responsibility of the driver is eliminated. Instead, the keeper, the operator, the manufacturer, and its suppliers come into focus.
For assessing criminal and civil liability, it is crucial that specific events in the automated vehicle can be reconstructed after an accident. Consequently, it is prescribed that vehicles equipped with an automated driving system must have a data storage system for automated driving (DSSAD). The requirements for this data storage system are detailed in Art. 25e and 25f RTA and in Art. 7 OAD.
Click here for the fictional case study.
You will learn about the data protection regulations applicable to automated driving and their impact on the fictional case study in the next post of our blog series.
You can find out more about this at our event "Autonomous driving – navigating the legal complexities":
https://lunchandlearn2026.events.vischer.com/