Civil Law and Virtual Reality Training System Failure Injury Claims in Europe

1. Introduction

Virtual Reality (VR) training systems are increasingly used in Europe for aviation, military training, healthcare, manufacturing, construction, logistics, transport, emergency response, workplace safety and professional education.

A VR training system may combine:

a VR headset;

motion controllers;

haptic devices;

motion platforms;

treadmills;

sensors and cameras;

computers and graphics processors;

software;

artificial-intelligence systems;

cloud services;

biometric or physiological monitoring;

physical barriers and safety equipment.

When such a system fails, the resulting injury may be physical even though the immediate cause appears to be “digital.”

Examples include:

a trainee falls because the virtual environment fails to correspond to the physical environment;

a motion platform moves unexpectedly;

a headset displays incorrect spatial information;

tracking software loses the user's position;

a haptic device applies excessive force;

an AI-controlled training simulation gives an unsafe instruction;

a software update disables a safety function;

a trainee experiences severe disorientation and falls;

a defective headset causes burns or electrical injury;

the training provider fails to warn about foreseeable risks;

the employer fails to supervise or stop unsafe use.

European law therefore potentially engages product liability, contractual liability, tort/delict, occupational-safety law, consumer protection, software liability, AI regulation and evidentiary rules.

An important qualification is necessary at the outset: there is still comparatively little reported European appellate case law specifically involving an injured person and a failed VR training simulator. Accordingly, the most useful authorities are European product-liability and safety cases involving technologically complex products and equipment. They provide principles that can be applied by analogy to VR systems.

2. The Basic Legal Problem

A VR injury claim can be represented as:

VR hardware

VR software

training provider

employer/institution

trainer/operator

user

↓

injury

The central question is:

Who legally caused the injury, and under which liability regime?

There may be several potentially responsible parties.

The injured person may therefore have parallel or alternative causes of action.

3. European Product-Liability Framework

The traditional European framework has been Council Directive 85/374/EEC on liability for defective products.

However, Europe is now transitioning to the much more technologically relevant Directive (EU) 2024/2853 on liability for defective products.

The new Directive expressly treats software as a product, including software supplied through cloud technologies and software-as-a-service arrangements. It also recognises digital manufacturing files as products in appropriate circumstances. (EUR-Lex)

The new Directive applies to products placed on the market or put into service after 8 December 2026, following the 2026 corrigendum. Products placed on the market before that date remain subject to the transitional regime under the earlier Directive. (EUR-Lex)

This is particularly important for VR systems because a VR training product is rarely just hardware.

It can consist of:

hardware + firmware + software + cloud services + AI + sensors + safety controls.

4. What Constitutes a "Defective" VR Training System?

Under the traditional product-liability approach, a product is defective when it does not provide the safety that a person is entitled to expect, taking account of circumstances such as:

presentation;

reasonably foreseeable use;

time of circulation.

The new Directive retains and modernises this safety-based approach.

For VR training, the question becomes:

What level of safety could the trainee reasonably expect from the complete VR training system?

This may include expectations concerning:

spatial accuracy;

tracking accuracy;

collision warnings;

emergency stop functions;

motion limits;

software stability;

headset temperature;

electrical safety;

warnings concerning motion sickness;

physical-space warnings;

foreseeable misuse;

software updates.

5. Case Law 1 — Henning Veedfald v Århus Amtskommune, C-203/99

Facts

In Henning Veedfald v Århus Amtskommune, Case C-203/99, a medical procedure involved a defective solution prepared and used within a hospital.

The producer attempted to rely upon the fact that the product had been manufactured and used within a public healthcare environment.

Decision

The CJEU interpreted the product-liability regime broadly and held that the circumstances in which a product is manufactured and used do not automatically remove it from product liability. The Court also emphasised the strict nature of producer liability and narrowly interpreted the exemptions. (EUR-Lex)

Relevance to VR training

The analogy is important where a VR system is:

developed internally by a training institution;

assembled specifically for the institution;

used only within a training centre;

not sold directly to the injured trainee.

A manufacturer cannot necessarily argue:

“This system was only used internally, therefore product liability cannot apply.”

Principle

The circumstances of internal or specialised use do not automatically eliminate product liability.

6. Case Law 2 — Boston Scientific Medizintechnik, Joined Cases C-503/13 and C-504/13

Facts

The case concerned pacemakers and implantable cardioverter-defibrillators that presented a risk of failure.

The devices did not necessarily fail in every individual case, but a particular product group presented an increased safety risk.

Judgment

The CJEU held that where a group of products presents an abnormal potential for damage, the safety expectations applicable to the product can be assessed at the group level. The Court also considered recovery of costs associated with preventive removal and replacement of potentially defective devices. (EUR-Lex)

Importance for VR systems

This principle could be highly significant if a VR manufacturer discovers that:

“Version 4.2 of the motion-control system can unexpectedly accelerate the training platform.”

Even if only a small percentage of systems have actually malfunctioned, the existence of an abnormal safety risk may become relevant.

Potential consequences include:

recall;

software patch;

withdrawal;

replacement;

preventive inspection;

compensation.

VR example

Suppose 1,000 training systems contain identical motion-control software.

Ten systems unexpectedly move trainees without warning.

The manufacturer cannot necessarily wait until every system causes injury.

The Boston Scientific reasoning demonstrates why abnormal safety risk can be legally significant before an individual system actually injures someone. (EUR-Lex)

7. Case Law 3 — W and Others v Sanofi Pasteur MSD, C-621/15

Facts

The case involved alleged injury following vaccination and concerned the evidentiary requirements for proving:

defect; and

causal connection between defect and damage.

Judgment

The CJEU held that national courts may use serious, specific and consistent evidence to establish defect and causation, provided that the evidentiary approach does not effectively reverse the burden of proof. (EUR-Lex)

Relevance to VR injury

This is particularly important because VR injuries may have complicated causation.

For example:

A trainee uses a VR simulator, becomes severely disoriented, falls and suffers a spinal injury.

The manufacturer argues:

“The fall was caused by the trainee's own balance problem.”

The claimant may need to establish:

malfunction;

abnormal visual output;

tracking failure;

latency;

defective warning;

causal connection with disorientation;

resulting injury.

Scientific certainty may be difficult.

The Sanofi Pasteur approach demonstrates the importance of coherent circumstantial evidence.

8. Case Law 4 — O'Byrne v Sanofi Pasteur, C-127/04

Facts

In O'Byrne v Sanofi Pasteur, the claimant suffered injury allegedly caused by a defective vaccine.

A major issue concerned when the product was put into circulation and by whom, including transactions between a producer and its wholly owned subsidiary/distributor. (EUR-Lex)

Importance

The case illustrates that identifying the correct defendant can become a major issue in product-liability litigation.

Application to VR

A VR system may have:

headset manufacturer A;

software developer B;

distributor C;

integrator D;

training provider E.

Suppose the accident is caused by an integration failure.

Who is the "producer"?

Under the new Product Liability Directive, software developers and manufacturers are specifically incorporated into the modern product-liability architecture. (EUR-Lex)

Thus:

The identity and legal role of each economic operator may determine whether the claimant can pursue strict product liability.

9. Case Law 5 — Centre hospitalier universitaire de Besançon v Dutrueux, C-495/10

Facts

A patient suffered harm because of defective equipment used during medical treatment.

The question was whether the hospital's liability fell within the EU product-liability regime when the hospital was not itself the producer.

Judgment

The CJEU held that liability of a service provider using defective equipment that it did not produce does not fall within the scope of the Product Liability Directive merely because the defective equipment caused harm during the service.

However, national law could impose liability on the service provider, including potentially no-fault liability, while preserving the possibility of a product-liability claim against the producer. (EUR-Lex)

Importance for VR training

This is one of the most useful authorities for VR training providers.

Suppose:

Manufacturer A produces the headset;

Training company B operates the VR course;

trainee C is injured.

B may argue:

“The headset was manufactured by A, so I cannot be liable under product liability.”

That does not necessarily mean B escapes liability.

B could independently be liable under national law for:

negligent supervision;

inadequate training;

failure to inspect;

failure to maintain equipment;

failure to establish a safe training environment;

failure to stop the simulation after detecting abnormal behaviour.

Principle

Producer liability and service-provider liability can coexist.

10. Case Law 6 — Commission v United Kingdom, C-300/95

Facts

The case concerned implementation of the "development risks" defence under the old Product Liability Directive.

The issue was whether a producer could escape liability where scientific and technical knowledge at the time of circulation was insufficient to discover the defect.

Judgment

The CJEU confirmed the availability of the development-risks defence under Article 7(e), subject to the Directive's requirements. (EUR-Lex)

VR relevance

Consider an early-generation VR system.

At the time it was released:

a particular neurological interaction was not scientifically recognised;

available testing did not identify it;

the manufacturer complied with then-current standards.

Years later, evidence demonstrates that prolonged exposure creates a previously unknown risk.

The manufacturer may attempt to invoke a development-risk defence under the applicable product-liability regime.

However, the issue becomes much more complicated if:

the manufacturer knew of complaints;

safety incidents had occurred;

internal testing revealed the problem;

later software updates identified the defect;

warnings were not issued.

Principle

Scientific uncertainty does not automatically excuse a producer where the applicable legal conditions for the development-risk defence are not satisfied.

11. Case Law 7 — Commission v France, C-52/00

Facts

The case concerned France's implementation of the Product Liability Directive.

The CJEU considered whether national legislation had correctly implemented the harmonised European product-liability regime. (EUR-Lex)

Significance

This case is important because it demonstrates the extent to which European product-liability rules constrain national legal variations.

VR relevance

VR manufacturers often operate throughout Europe.

A claimant may argue:

“French law provides X.”

The manufacturer may respond:

“The EU product-liability regime establishes the applicable framework.”

Courts therefore need to distinguish:

harmonised product liability;

national tort law;

contract law;

occupational liability;

special statutory regimes.

12. Case Law 8 — LF v Sanofi Pasteur SA, C-338/24

This is particularly important because it is a 2026 CJEU judgment and therefore reflects the current state of EU product-liability law.

Facts

The case concerned a defective-product claim involving progressive injury and the relationship between EU product liability and national fault-based liability.

Judgment

On 26 March 2026, the CJEU held that Article 13 of the former Product Liability Directive does not prevent an injured person from pursuing compensation under a general fault-based liability regime where the alleged fault is distinct from the defect itself—for example, keeping a defective product in circulation despite knowledge of the defect or failing to comply with a duty of care concerning its risks. (FRA)

The Court also addressed limitation periods for progressive damage. (Court of Justice of the European Union)

Importance for VR injury claims

This is potentially highly significant.

Suppose a VR manufacturer knows that:

a software update causes abnormal visual tracking,

but does not withdraw or patch the system.

A claimant might have:

Route A — product liability

The VR system was defective.

Route B — fault-based liability

The manufacturer knew of the danger but negligently failed to act.

The 2026 LF v Sanofi Pasteur judgment confirms the conceptual possibility of such parallel reasoning where the fault-based claim rests on a different legal basis. (FRA)

13. The New EU Product Liability Directive and VR Systems

The most important development for future VR claims is Directive (EU) 2024/2853.

It expressly provides that software is a product for product-liability purposes, irrespective of whether it is:

installed on hardware;

supplied through a network;

delivered through cloud technology;

provided through software-as-a-service. (EUR-Lex)

This is exceptionally relevant to VR.

A VR training system may contain:

headset + firmware + simulation software + cloud platform + AI module.

A claimant therefore does not necessarily need to argue that only the physical headset is defective.

The defect could exist in the software itself.

14. Software Defect

Examples include:

incorrect collision detection;

failure of spatial tracking;

incorrect rendering;

excessive latency;

incorrect depth perception;

failure of emergency warnings;

software crash;

corrupted training scenario;

incorrect haptic command;

incorrect motion-platform command.

The new Directive expressly recognises software as capable of causing damage through its execution. (EUR-Lex)

Therefore, a VR software provider can become a central defendant.

15. AI-Enabled VR Training

Modern VR systems increasingly use AI for:

adaptive training;

automated scenario generation;

real-time feedback;

behavioural analysis;

voice interaction;

biometric monitoring;

automated movement instructions;

dynamic hazard simulation.

The EU AI Act is therefore potentially relevant.

The AI Act's risk framework treats certain AI systems that operate as safety components of regulated products as high-risk. It also requires risk-management processes for high-risk systems. (EUR-Lex)

A VR system used in training could therefore have an additional regulatory dimension where AI functionality performs a safety-related function.

16. Reasonably Foreseeable Misuse

One of the most important issues is whether the injury arose from:

Intended use

The user followed instructions exactly.

Foreseeable misuse

The user used the system in a way the manufacturer could reasonably anticipate.

Abnormal misuse

The user did something genuinely unforeseeable.

For example:

A manufacturer says:

“Use only while standing in a clear 2 × 2 metre area.”

A trainee moves into an area containing equipment.

The legal question becomes:

Was this behaviour reasonably foreseeable?

The answer can affect defect, causation and liability.

17. Training Provider's Independent Duty of Care

The training provider is not merely a passive recipient of the VR system.

It may have duties concerning:

risk assessment;

user screening;

supervision;

equipment inspection;

emergency procedures;

physical environment;

instructor competence;

maintenance;

software updates;

training duration;

user warnings.

Suppose the manufacturer provides a warning:

“Users susceptible to severe motion sickness should not participate.”

The training provider ignores the warning and requires participation.

Even if the VR hardware is not defective, the training provider may face a fault-based civil claim.

18. Employer Liability

Where VR is used for occupational training, an injured trainee may also be an employee.

The employer may have duties under:

national occupational-safety legislation;

workplace risk-assessment requirements;

employment law;

health-and-safety law;

general tort/delict principles.

A worker may therefore have a claim even if:

the VR equipment itself was perfectly manufactured.

The employer might be liable because it:

failed to conduct a risk assessment;

ignored previous incidents;

failed to maintain the equipment;

used untrained instructors;

placed the system in an unsafe room.

19. Physical-Space Liability

VR creates a distinctive legal problem:

The virtual environment may differ from the physical environment.

Example:

The simulation shows a virtual open floor.

The actual room contains:

a table;

cable;

wall;

step;

machine;

another trainee.

The user walks forward and collides with the physical object.

The manufacturer may argue:

“The software performed exactly as designed.”

But the training provider may have failed to ensure a safe physical environment.

Thus:

virtual safety ≠ physical safety.

20. Motion-Platform Failure

Advanced VR training may involve:

flight simulators;

vehicle simulators;

motion seats;

motion platforms;

industrial machinery simulators.

Suppose a motion platform suddenly tilts 30 degrees instead of 3 degrees.

The trainee falls.

Potential causes include:

hardware defect;

software defect;

sensor defect;

calibration failure;

maintenance failure;

incorrect operator instruction;

cybersecurity attack.

Expert evidence will be critical.

21. Haptic-Device Injury

Haptic systems can generate physical force.

For example:

gloves;

exoskeletons;

force-feedback controllers;

robotic arms;

resistance devices.

If a haptic device applies excessive force, the claim may concern:

defective hardware;

incorrect software;

inadequate safety limits;

insufficient warnings;

defective design;

inadequate emergency stop.

The Boston Scientific principle concerning abnormal safety risks can be particularly useful by analogy when a class of devices presents an unusual danger. (EUR-Lex)

22. Headset-Related Injuries

Potential injuries include:

overheating;

electrical shock;

burns;

allergic reactions;

visual injury;

headaches;

disorientation;

falls.

The claimant may need to prove:

Damage + defect + causal relationship.

Under the traditional EU framework, these are central elements of the product-liability claim. The CJEU's jurisprudence confirms the importance of these elements and the permissible methods of proving them. (EUR-Lex)

23. Motion Sickness and Neurological Injury

VR can produce:

nausea;

vertigo;

dizziness;

disorientation;

balance problems;

headaches.

A more difficult case arises when the claimant suffers a secondary injury:

VR → severe disorientation → fall → fractured hip.

The legal issue is not merely whether VR caused dizziness.

It is whether the dizziness and resulting fall were:

foreseeable;

attributable to a defect;

adequately warned against;

caused by defective design or operation.

24. Causation in VR Litigation

Causation can be divided into three stages.

Stage 1 — System malfunction

Example:

Tracking error = 500 milliseconds.

Stage 2 — Human consequence

The trainee perceives a virtual object incorrectly.

Stage 3 — Physical injury

The trainee falls.

The claimant therefore needs to establish a causal chain:

defect → abnormal system behaviour → human reaction → accident → injury.

This may require:

system logs;

video recordings;

telemetry;

software version records;

headset data;

sensor data;

expert reconstruction;

medical evidence.

25. Evidence and Digital Logs

VR litigation is likely to be heavily evidence-driven.

Important evidence may include:

headset logs;

server logs;

software versions;

firmware versions;

crash reports;

telemetry;

eye-tracking data;

motion data;

controller inputs;

training-session recordings;

maintenance records;

incident reports;

cybersecurity records.

A claimant may argue that the manufacturer possesses the relevant technical evidence.

The new Product Liability Directive is designed to facilitate evidence-related mechanisms in complex product-liability disputes, reflecting the increasing technological complexity of modern products.

26. The Problem of Software Updates

Suppose:

Version 3.1 — safe

Version 3.2 — defective

Version 3.3 — corrected

The accident occurs during version 3.2.

Questions include:

Who installed the update?

Was automatic updating enabled?

Was the training provider notified?

Did the manufacturer know about the defect?

Was version 3.2 withdrawn?

Were warnings provided?

Was the training provider obliged to install the patch?

The answer may determine liability.

27. Cybersecurity Attacks

Imagine a hacker compromises the VR training system.

The attacker causes:

false visual information;

uncontrolled motion;

disabling of safety warnings;

abnormal haptic feedback.

The injured person sues the manufacturer.

The manufacturer argues:

“The accident was caused by an external hacker.”

This raises difficult questions concerning:

foreseeability;

cybersecurity duties;

security-by-design;

product defect;

force majeure;

intervening cause.

The mere existence of third-party hacking does not automatically answer the liability question.

28. Contractual Liability

Where the injured person is a customer or employee receiving contractual training, contractual duties may also arise.

For example:

A professional pilot purchases a VR training programme from a training company.

The company promises:

certified equipment;

safe operation;

qualified instructors;

compliant software.

If the system fails, the claimant may have contractual claims for breach of:

express terms;

implied safety obligations;

professional standards;

reasonable-care obligations.

29. Product Liability vs Contract vs Tort

The Dutrueux judgment is particularly useful because it demonstrates that product liability does not necessarily eliminate separate liability of the service provider. (EUR-Lex)

30. Damage Recoverable

A successful claimant may seek compensation for:

Personal injury

fractures;

neurological injury;

burns;

visual injury;

psychological injury.

Medical costs

hospitalisation;

rehabilitation;

medication;

future treatment.

Loss of earnings

Particularly significant for professional trainees.

Reduced earning capacity

Relevant where injury permanently affects employment.

Pain and suffering

Recognised differently across European jurisdictions.

Property damage

For example, damage to personal equipment.

Other consequential losses

Subject to the applicable national law.

31. Comparative European Perspective

Germany

German claims may involve:

Bürgerliches Gesetzbuch (BGB);

Product Liability Act;

occupational-safety principles;

contractual duties;

Verkehrssicherungspflichten.

The concept of Verkehrssicherungspflicht can be particularly important where an operator creates or controls a potentially dangerous training environment.

France

French law may involve:

Code civil;

product-defect liability;

contractual liability;

tort liability;

employer duties.

The French origin of Sanofi Pasteur and Dutrueux makes the French jurisprudential contribution especially important to European product-liability analysis.

Italy

Italian claims may involve:

Codice civile;

product-liability provisions;

contractual liability;

general tort liability;

workplace safety legislation.

Spain

Spanish law provides product-liability and consumer-protection mechanisms alongside general civil liability.

Netherlands

Dutch law contains a structured product-liability regime and general tort principles, including duties arising from dangerous situations.

United Kingdom

The UK is geographically European but is no longer governed by EU law in the same way following Brexit. Its product-liability and negligence principles remain valuable comparative authorities, but should not be confused with current EU law.

32. The Significance of the 2026 Product-Liability Transition

This point is particularly important for a contemporary European legal analysis.

Directive (EU) 2024/2853 applies to products placed on the market or put into service after 8 December 2026. (EUR-Lex)

Therefore, in October 2026:

Older VR systems

Generally remain within the transitional framework of Directive 85/374 and national implementing laws.

New VR systems after the transition date

Will increasingly fall under the modernised product-liability regime.

The difference is important because the new regime expressly accommodates software, interconnected products and modern digital technology. (EUR-Lex)

33. AI and VR Training Systems

Suppose a VR training system contains AI that dynamically changes the training environment.

The AI decides:

“The trainee should now face a simulated emergency.”

But the algorithm generates an unsafe scenario.

If the AI system is a safety component of a regulated product, the EU AI Act may become relevant.

The AI Act requires risk-management measures for high-risk AI systems, including identification and evaluation of risks arising from intended use and reasonably foreseeable misuse. (EUR-Lex)

The future litigation could therefore examine:

AI risk assessment;

training data;

system limitations;

human oversight;

monitoring;

post-market incidents;

software updates.

34. Failure to Warn

Warning defects can be just as important as mechanical defects.

Suppose the manufacturer knows that:

rapid head movement combined with the simulation may cause severe disorientation.

But the instructions merely say:

“Some users may experience discomfort.”

The claimant could argue that the warning did not adequately communicate the seriousness of the risk.

The legal analysis would consider:

seriousness of injury;

probability of occurrence;

sophistication of users;

professional nature of training;

age of users;

foreseeable use;

adequacy of warnings.

35. Failure to Update

A particularly modern issue is post-market software knowledge.

Suppose:

manufacturer launches VR system;

10 incidents are reported;

manufacturer discovers tracking failure;

manufacturer develops a patch;

training provider does not install the patch;

trainee is injured.

Potential liability may be divided between:

manufacturer for failure to warn/update;

training provider for failure to install the update;

employer for inadequate safety monitoring.

The 2026 LF v Sanofi Pasteur judgment is important here because it confirms that a fault-based claim may coexist with product liability where the alleged fault consists of conduct such as knowingly keeping a defective product in circulation or failing to observe a duty of care. (FRA)

36. Development Risks and VR Technology

VR technology develops rapidly.

A manufacturer may argue:

“The specific danger was scientifically unknown when the product was released.”

The development-risk defence recognised under the older Directive can become relevant.

The Commission v United Kingdom judgment confirms the importance of the state of scientific and technical knowledge when evaluating that defence. (EUR-Lex)

But the argument becomes weaker if evidence shows that the producer:

knew of complaints;

ignored internal testing;

failed to monitor incidents;

failed to issue warnings;

failed to correct a known software defect.

37. Multi-Defendant Litigation

A serious VR accident can produce a multi-party action.

Example

A trainee is injured when:

the headset tracking system fails;

the motion platform moves unexpectedly;

the software was improperly updated;

the training provider ignored a maintenance warning.

Potential defendants:

Manufacturer A

→ defective headset.

Software Company B

→ defective tracking software.

Integrator C

→ defective installation.

Training Company D

→ inadequate supervision.

Employer E

→ inadequate risk assessment.

The court may need to determine:

causation;

contribution;

joint liability;

contractual indemnities;

apportionment.

38. Hypothetical Case

Consider EuroSim Training Ltd.

It operates VR systems for industrial-worker training.

A trainee enters a virtual factory.

The software incorrectly represents a virtual machine as being three metres away when it is actually immediately in front of the trainee.

The trainee steps forward, collides with a physical barrier and suffers a serious injury.

Investigation reveals:

headset tracking was inaccurate;

software had a known bug;

the manufacturer issued a patch;

EuroSim failed to install the patch;

the instructor was not informed about the risk;

the physical room lacked adequate clearance.

Possible claims

Against manufacturer

defective product;

inadequate warning;

failure to update;

software defect.

Against software provider

defective software;

contractual breach;

negligence.

Against training provider

inadequate supervision;

failure to maintain;

unsafe training environment.

Against employer

failure to provide a safe workplace.

This is precisely why VR injury litigation cannot be analysed solely as a conventional "defective headset" claim.

39. Burden of Proof

A claimant generally needs to establish:

1. Damage

Actual personal injury.

2. Defect

The system failed to provide the legally expected level of safety.

3. Causation

The defect caused the injury.

The Sanofi Pasteur jurisprudence is important because it permits appropriate evidentiary techniques under national law while maintaining the claimant's responsibility to establish defect and causation. (EUR-Lex)

For VR systems, this may involve expert evidence rather than eyewitness testimony alone.

40. Expert Evidence

A VR injury case may require several experts.

Software expert

Determines whether software behaved correctly.

Human-factors expert

Examines foreseeable human interaction.

Electrical engineer

Examines electrical safety.

Mechanical engineer

Examines motion-platform failure.

Medical expert

Establishes injury and causation.

Occupational-safety expert

Examines training-provider procedures.

Cybersecurity expert

Determines whether external interference caused the failure.

This makes VR litigation particularly technically intensive.

41. Key Case-Law Principles

42. Most Important Legal Questions for Courts

A European court dealing with a serious VR-training injury would probably need to answer the following sequence:

Question 1

Was the VR system a "product" for the applicable legal regime?

Question 2

Was the problem located in:

hardware;

software;

AI;

cloud service;

integration;

maintenance?

Question 3

Was there a safety defect?

Question 4

What safety could the trainee reasonably expect?

Question 5

Was the use foreseeable?

Question 6

Did the defect cause the injury?

Question 7

Did the training provider independently breach its duty of care?

Question 8

Did the employer breach workplace-safety obligations?

Question 9

Did warnings adequately disclose the risk?

Question 10

Did the manufacturer know about the problem?

Question 11

Was a software update available?

Question 12

Who failed to install it?

Question 13

Does a development-risk defence apply?

Question 14

Are contractual exclusions legally effective?

Question 15

How should damages be apportioned among defendants?

43. Practical Contract-Drafting Recommendations

VR training agreements should expressly address:

hardware specifications;

software specifications;

maximum latency;

tracking accuracy;

physical-space requirements;

emergency-stop mechanisms;

cybersecurity;

software updates;

maintenance;

incident reporting;

user warnings;

operator qualifications;

training duration;

foreseeable misuse;

data logging;

audit rights;

insurance;

indemnification;

liability caps;

product recalls;

regulatory changes;

termination following safety failures.

These provisions can significantly affect subsequent civil litigation.

44. Overall Legal Assessment

Virtual reality training system injury claims represent a particularly interesting development in European civil law because the physical injury may originate from an intangible software malfunction.

The traditional division between:

"defective product"

and

"defective service"

is becoming increasingly difficult to maintain.

A modern VR system may be:

physical hardware + software + AI + cloud services + sensors + human supervision.

The new Product Liability Directive recognises precisely this technological reality by expressly treating software as a product and accommodating interconnected digital products. (EUR-Lex)

The 2026 LF v Sanofi Pasteur judgment further demonstrates the continuing importance of distinguishing strict product liability from independent fault-based liability. (FRA)

45. Conclusion

Civil liability for VR training system failures in Europe is likely to develop through the interaction of product liability, tort/delict, contract, occupational safety and digital-technology regulation.

The principal European authorities—Veedfald, Boston Scientific, Sanofi Pasteur, O'Byrne, Dutrueux, Commission v United Kingdom, Commission v France and LF v Sanofi Pasteur—provide an important doctrinal foundation even though most arose from other technological or medical contexts.

The most important lessons are:

A VR system can potentially constitute a product even where software is central to the defect.

Software defects can increasingly generate product-liability claims.

Training providers may have independent liability even where they did not manufacture the VR equipment.

Employers may remain liable for failures in workplace safety.

Warnings and instructions are central to assessing defectiveness.

Foreseeable misuse can be legally significant.

Technical evidence and system logs may determine causation.

Known defects followed by failure to warn or update can create fault-based liability in addition to product liability.

AI-enabled VR systems may create additional regulatory obligations where AI performs a safety function.

The EU's new Product Liability Directive marks a major shift toward treating software and interconnected digital technologies as part of modern product-safety law.

The central legal proposition can therefore be stated as follows:

Where a VR training system causes physical injury, European civil law will increasingly look beyond the physical headset and examine the entire technological ecosystem—hardware, software, AI, updates, warnings, maintenance, training procedures and human supervision—to determine whether a defective product, negligent service, breach of contract, or combination of these caused the injury.

The transition to Directive (EU) 2024/2853 is especially significant because software is expressly included within the modern EU concept of a product, with the new regime applying to products placed on the market or put into service after 8 December 2026. (EUR-Lex)