Civil Law and Autonomous Spacecraft Navigation Error Claims in Europe

1. Introduction

Autonomous spacecraft navigation error claims arise when a spacecraft, satellite, space probe, orbital vehicle, or other space object uses autonomous or AI-assisted systems for navigation and an incorrect decision causes loss or damage.

Examples include:

incorrect orbital manoeuvres;

collision-avoidance errors;

wrong attitude or orientation;

incorrect rendezvous calculations;

autonomous docking failure;

GNSS/Galileo positioning errors;

erroneous trajectory calculations;

failure to avoid space debris;

autonomous re-entry errors;

incorrect station-keeping;

software-update-induced navigation failure;

AI misinterpretation of sensor data;

communication-loss-induced autonomous manoeuvres.

This is an especially difficult area of European civil law because space activities are primarily regulated through international space law, while many compensation claims between private parties are governed by national civil law and European private-international-law rules.

There is presently no single European civil-law statute specifically governing every autonomous spacecraft navigation error. The legal analysis therefore combines international space law, national tort/contract law, EU non-contractual liability, product liability, private international law, insurance, and space-licensing regimes.

The problem is becoming more important because European GNSS and autonomous systems can interact: academic research specifically identifies the question of who should bear liability when an AI-enabled autonomous system causes an accident because of an inaccurate or absent GNSS signal. (Vrije Universiteit Amsterdam)

2. What Is an Autonomous Spacecraft Navigation Error?

An autonomous navigation error occurs when a spacecraft's automated system makes, recommends, or executes an incorrect navigation decision.

Typical chain

Sensor/GNSS data → navigation software → AI/autonomous decision → command → spacecraft manoeuvre → damage

For example:

An autonomous satellite incorrectly calculates another spacecraft's trajectory, performs an avoidance manoeuvre, collides with a third satellite, and creates debris.

Potential consequences include:

destruction of spacecraft;

loss of satellite services;

damage to another space object;

creation of orbital debris;

interruption of communications;

interruption of navigation services;

damage during uncontrolled re-entry;

personal injury or property damage on Earth;

commercial losses.

3. Why the Legal Problem Is Different From Ordinary Civil Liability

Ordinary civil liability usually asks:

Who caused the accident?

Space law first asks:

Which launching State is internationally responsible for the space object?

The international framework is based principally on:

Outer Space Treaty 1967;

Liability Convention 1972;

Registration Convention 1975;

relevant national space legislation.

The Liability Convention establishes:

absolute liability for damage caused by a space object on the surface of the Earth or to aircraft in flight;

a fault-based regime for certain damage occurring elsewhere than on the surface of the Earth.

The distinction is extremely important for autonomous spacecraft.

For an in-orbit collision, Article III of the Liability Convention requires proof of fault of the launching State or persons for whom it is responsible. (OUP Academic)

4. Meaning of "Fault" in Autonomous Navigation

The Liability Convention does not provide a detailed modern definition of technological fault.

This creates a difficult question:

If an AI system makes a navigation error without a human operator directly instructing it to do so, whose fault is it?

Possible sources of fault include:

defective software;

poor algorithm design;

insufficient training;

inadequate testing;

defective sensors;

failure to update software;

inadequate collision avoidance;

poor mission planning;

inadequate supervision;

failure to react to warnings;

inadequate debris tracking;

negligent spacecraft design.

Academic analysis has identified the absence of a precise standard of care for "fault" in Article III as a major difficulty in applying the Liability Convention to space-object collisions. (OUP Academic)

5. Important European Legal Framework

A. International Space Law

The starting point is:

Outer Space Treaty

Article VI is particularly important because States bear international responsibility for national activities in outer space, including activities carried out by non-governmental entities.

Therefore, private European space companies do not simply operate outside the international legal framework.

B. Liability Convention

The Convention distinguishes between:

Damage on Earth

The launching State is generally subject to absolute liability.

Damage in outer space

Where damage is caused elsewhere than on Earth's surface, liability is generally based on fault.

This creates an important distinction:

6. European Civil Law and Rome II

Private claims can raise difficult questions concerning:

applicable national law;

jurisdiction;

place of damage;

place of conduct;

contractual law;

insurance law.

The Rome II Regulation can potentially become relevant to non-contractual obligations where its territorial and substantive conditions are satisfied.

Space-law scholarship has specifically examined the possibility that Rome II could provide an interface for private third-party claims arising from space activities, while recognising the difficulties created by the international character of space liability. (ScienceDirect)

7. Case Law

A major qualification is necessary:

There are very few reported European judgments directly deciding civil liability for an autonomous spacecraft navigation error.

Accordingly, the following cases are divided into:

directly space-related European cases; and

closely analogous European civil-liability authorities.

That distinction is important to avoid presenting ordinary satellite or administrative cases as if they were autonomous-spacecraft accident cases.

8. Case 1 — Galileo International Technology LLC and Others v Commission

General Court, Case T-279/03, 10 May 2006

This is one of the most directly relevant European cases because it concerned the EU's Galileo satellite-navigation programme.

The applicants alleged damage arising from the Commission's use of the name "Galileo" for the Community satellite navigation project. The action was brought as an action for non-contractual liability against the Community.

The General Court rejected the claim. It considered, among other things, the requirements governing Community non-contractual liability and the relationship between the alleged conduct and the claimed damage. (Eur-Lex)

Importance

Although the case did not concern a navigation malfunction, it demonstrates that European courts have already considered:

Galileo;

satellite navigation;

EU institutional responsibility;

non-contractual liability;

causation;

compensable damage.

Application to autonomous spacecraft

If an autonomous spacecraft relies on a European navigation infrastructure and an alleged failure is attributed to an EU institution or agency, a claimant would have to establish the relevant legal basis for EU non-contractual liability and a sufficiently direct causal connection.

Principle

The existence of a European satellite-navigation programme does not automatically establish EU civil liability for every loss associated with that system.

9. Case 2 — Airbus Defence and Space SAS and Marlink Events SAS v European Defence Agency

General Court, Case T-105/24, judgment 1 July 2026

This is a particularly recent space-related European case.

The dispute concerned a procurement procedure involving satellite communications, equipment and related services. The General Court considered issues including:

procurement criteria;

equal treatment;

manifest error of assessment;

non-contractual liability;

loss of opportunity;

compensation. (Curia)

Relevance

It does not concern a spacecraft navigation accident.

Nevertheless, it is useful for autonomous-spacecraft litigation because it demonstrates how European courts approach:

complex space-related technical services;

public-sector contracting;

causation;

economic loss;

compensation;

non-contractual responsibility.

Application

If an EU body contracts for an autonomous spacecraft navigation system and the procurement or contractual administration itself causes legally compensable loss, this line of jurisprudence can become relevant.

Principle

Space-related commercial disputes can fall within ordinary European contractual and non-contractual liability frameworks even when the underlying technology is highly specialised.

10. Case 3 — Brasserie du Pêcheur and Factortame III

CJEU, Joined Cases C-46/93 and C-48/93, 1996

This is a foundational EU State-liability case.

The CJEU established important conditions for Member State liability arising from breaches of EU law.

The basic framework includes:

the EU rule must confer rights on individuals;

the breach must be sufficiently serious;

there must be a direct causal connection between the breach and the damage.

Relevance to autonomous spacecraft

Suppose a Member State:

fails to properly implement an applicable EU obligation;

seriously breaches an EU requirement governing a relevant activity;

and that breach contributes directly to damage caused by an autonomous spacecraft.

A State-liability claim could potentially arise if the relevant conditions are satisfied.

Principle

Autonomous technology does not prevent State liability where an independent EU-law breach satisfies the established requirements for compensation.

11. Case 4 — Francovich and Others v Italy

CJEU, Joined Cases C-6/90 and C-9/90, 1991

Francovich established the fundamental principle of Member State liability for damage caused by sufficiently serious breaches of EU law.

Relevance

Spacecraft navigation may depend upon:

EU space programmes;

telecommunications;

GNSS;

cybersecurity;

aviation or transport systems;

regulatory frameworks.

Where a relevant EU obligation is breached by a Member State, Francovich principles may become relevant to a compensation claim.

Limitation

Francovich does not mean that every spacecraft malfunction attributable to a State creates State liability.

The claimant still has to satisfy the applicable requirements.

Principle

State liability depends upon breach, legal rights, seriousness and causation—not merely the occurrence of damage.

12. Case 5 — Boston Scientific Medizintechnik GmbH v AOK

CJEU, Joined Cases C-503/13 and C-504/13, 2015

This case concerned defective medical devices and the safety risks associated with products belonging to a particular series.

Principle

The CJEU developed important principles concerning:

defective products;

safety expectations;

systemic product risk;

products belonging to the same series.

Application to spacecraft

Consider a manufacturer that produces 100 autonomous satellites using the same navigation computer.

Satellite No. 1 suffers:

software-controlled navigation failure.

Investigation reveals that the same architectural defect exists in the other 99 satellites.

The reasoning of Boston Scientific can provide an analogy for analysing systemic safety defects.

Possible claims

product defect;

design defect;

inadequate warning;

inadequate testing;

recall-related loss.

Principle

A recurring safety risk within a product series may be legally significant even if every individual unit has not yet failed.

13. Case 6 — W and Others v Sanofi Pasteur

CJEU, Case C-621/15, 2017

The CJEU considered evidentiary questions in complex product-liability litigation.

Importance

Technology-intensive disputes often involve situations where scientific evidence cannot provide a simple causal explanation.

This is highly relevant to autonomous spacecraft.

Suppose:

Satellite navigation software malfunctioned → spacecraft changed orbit → collision occurred.

The claimant may need to prove:

the software was defective;

the defect existed at the relevant time;

the defect caused the navigation error;

the navigation error caused the collision.

Evidence

Possible evidence includes:

telemetry;

source-code records;

system logs;

sensor data;

orbital data;

software-version history;

testing documentation;

communications records;

expert reconstruction.

Principle

Complex technical causation requires careful evidentiary analysis rather than assuming that scientific uncertainty automatically defeats a claim.

14. Case 7 — Commission v United Kingdom

CJEU, Case C-300/95, 1997

This case is important for the concept of the development-risk defence under European product-liability law.

Application to spacecraft

A spacecraft manufacturer may argue:

“The navigation defect could not reasonably have been discovered using the scientific and technical knowledge available at the relevant time.”

The claimant may argue that:

adequate simulation would have detected it;

similar failures were already known;

industry standards identified the risk;

previous missions provided warning;

the manufacturer failed to conduct sufficient testing.

Principle

The technological state of knowledge may become relevant when determining the legal consequences of an allegedly unknown product risk.

15. Case 8 — O'Byrne v Sanofi Pasteur MSD

CJEU, Case C-127/04, 2006

This case concerned the concept of when a product is put into circulation for product-liability purposes and the relationship between manufacturer and distribution arrangements.

Relevance to spacecraft

Spacecraft have unusual production and deployment structures.

A satellite may pass through:

Manufacturer → systems integrator → launch provider → operator → mission-control contractor.

Determining who legally supplied or controlled the relevant component can therefore be critical.

Autonomous spacecraft example

Suppose:

satellite hardware was manufactured by Company A;

navigation software was supplied by Company B;

integration was performed by Company C;

operation was controlled by Company D.

A court may need to determine which actor's conduct legally caused the defect.

Principle

Identifying the legally responsible producer or actor is fundamental in complex technological supply chains.

16. International Space-Law Liability and the Private Claim Problem

One of the most important difficulties is that the Liability Convention is primarily State-to-State.

Suppose a French company's satellite is damaged by an autonomous satellite launched by another State.

The private company does not simply invoke Article III in the same way it would invoke a domestic tort statute.

Instead, the international framework may involve:

injured State → launching State → international claim → domestic/private compensation mechanisms.

This State-centric structure creates a gap between:

international responsibility

and

private civil compensation.

Academic analysis has specifically identified the limitations of the international space-liability system for modern private commercial activities and GNSS-dependent autonomous systems. (OUP Academic)

17. GNSS/Galileo Navigation Error

This is one of the most important areas.

An autonomous spacecraft may rely on:

Galileo;

GPS;

GLONASS;

BeiDou;

onboard sensors;

star trackers;

ground-based navigation.

Suppose Galileo provides an incorrect signal.

The spacecraft then:

calculates an incorrect position;

makes an incorrect orbital manoeuvre;

enters another spacecraft's path;

causes a collision.

Possible defendants

Potential responsibility could be examined in relation to:

spacecraft operator;

spacecraft manufacturer;

navigation-software provider;

GNSS service provider;

system integrator;

ground-control operator;

potentially a public authority or programme operator.

But liability does not automatically attach to whichever actor supplied the navigation signal.

18. EU Galileo Liability

The EU has specifically contemplated liability arrangements concerning Galileo satellites.

For example, an EU-US agreement concerning Galileo satellite launches contains provisions addressing liability where a Galileo satellite or component causes damage that gives rise to claims against the United States under international law. (Eur-Lex)

This demonstrates an important principle:

Galileo-related liability is not purely an ordinary consumer-services issue; it can engage international State responsibility and intergovernmental allocation mechanisms.

19. Autonomous Collision in Outer Space

Consider:

Satellite A uses AI collision avoidance.

The AI predicts incorrectly.

It performs an emergency manoeuvre.

Satellite A collides with Satellite B.

Satellite B is destroyed.

Article III issue

Because the damage occurs in outer space, the fault-based part of the Liability Convention becomes particularly relevant.

The claimant may need to establish:

damage;

causation;

connection to the relevant space object;

fault of the launching State or persons for whom it is responsible.

The major legal question becomes:

What constitutes reasonable care for autonomous spacecraft navigation?

20. Standard of Care for Autonomous Spacecraft

There is no universally detailed European judicial standard.

A court or claims body may examine:

1. Industry practice

Was the navigation system consistent with established spacecraft practices?

2. Mission standards

Were accepted mission-safety procedures followed?

3. Collision avoidance

Was the spacecraft capable of detecting known risks?

4. Testing

Was the AI adequately tested?

5. Simulation

Were abnormal orbital situations simulated?

6. Human supervision

Was human intervention possible?

7. Redundancy

Were backup systems available?

8. Software updates

Was the system maintained?

9. Debris monitoring

Was relevant orbital data considered?

21. AI and Autonomous Decision-Making

Traditional negligence assumes:

Human observes → Human decides → Human acts.

Autonomous spacecraft change this:

Sensors → AI → autonomous decision → spacecraft action.

This creates an agency gap.

The AI itself generally cannot simply be treated as the legal defendant.

Responsibility instead must normally be allocated among the human and corporate actors who:

designed the system;

trained it;

integrated it;

deployed it;

controlled it;

maintained it;

updated it.

22. Software Defect

Suppose an autonomous spacecraft's navigation software contains a coding error.

Possible legal questions:

Was the software defective?

Was the defect present when supplied?

Was the defect introduced by an update?

Did the operator install the update?

Was the update mandatory?

Did the developer issue a warning?

Was the software tested sufficiently?

European product-liability principles become increasingly relevant as software becomes an integral part of physical products.

23. Cyberattack and Navigation

Another scenario:

Cyberattack → false orbital data → autonomous navigation decision → collision.

Possible legal theories include:

negligent cybersecurity;

defective software;

breach of contract;

inadequate warning;

failure to maintain;

failure to implement appropriate safeguards.

The existence of a cyberattack does not automatically determine liability.

The court may ask whether the attack was:

foreseeable;

preventable;

reasonably mitigable;

enabled by an existing vulnerability.

24. Space Debris

Autonomous spacecraft must increasingly operate in an environment containing:

inactive satellites;

rocket bodies;

fragments;

collision debris;

operational constellations.

Suppose the navigation system fails to recognise an approaching object.

Potential issues include:

adequacy of debris tracking;

quality of orbital data;

collision-warning systems;

reaction time;

autonomous decision thresholds;

responsibility for the original debris.

This creates potentially multi-causal liability.

25. Multiple-Cause Accidents

Example:

Old debris → inadequate tracking → AI prediction error → incorrect manoeuvre → collision.

Four actors may potentially be relevant:

original debris-producing operator;

tracking-data provider;

autonomous navigation developer;

current spacecraft operator.

The court must distinguish:

factual causation;

legal causation;

concurrent causes;

intervening causes.

26. Contractual Liability

Many spacecraft navigation disputes will arise under contracts.

Important agreements include:

satellite manufacturing contracts;

launch contracts;

satellite-operation contracts;

software licences;

GNSS service agreements;

insurance contracts;

ground-station agreements;

mission-management agreements.

Important contractual clauses include:

Warranty

Was the navigation system guaranteed to satisfy specified accuracy?

Service level

Was continuous navigation support promised?

Indemnity

Which party bears third-party claims?

Limitation of liability

Are consequential losses excluded?

Force majeure

Does a GNSS outage qualify?

Cybersecurity

Who bears responsibility for security breaches?

27. Insurance

Spacecraft operators commonly depend heavily upon insurance arrangements.

Relevant insurance issues may include:

launch insurance;

in-orbit insurance;

third-party liability insurance;

satellite-service interruption insurance;

cyber insurance.

An autonomous navigation error may therefore produce disputes not only between operator and manufacturer but also between:

operator ↔ insurer ↔ manufacturer ↔ software provider.

28. Damage Categories

Potential claims may include:

Physical damage

destroyed satellite;

damaged spacecraft;

damaged ground infrastructure.

Economic loss

loss of communications;

loss of navigation services;

loss of satellite capacity;

replacement costs.

Business interruption

A navigation failure may interrupt:

telecommunications;

transport;

logistics;

financial timing systems;

emergency services.

Personal injury

Particularly relevant where a spacecraft or fragment causes damage during re-entry.

Environmental damage

Space debris can create long-term orbital risks, although compensation mechanisms for such harm remain legally complex.

29. Damage on Earth Versus Damage in Space

This distinction is fundamental.

30. Causation

Autonomous spacecraft cases may involve extraordinary causal chains.

Example:

Galileo signal anomaly → navigation calculation error → autonomous manoeuvre → collision → satellite destruction → communications outage → commercial losses.

The claimant must identify the legally relevant causal connection.

Possible evidence includes:

telemetry;

navigation logs;

GNSS signal records;

orbital trajectories;

source code;

AI model documentation;

sensor records;

mission-control records;

software updates;

cybersecurity logs;

expert testimony.

31. Black-Box Problem

AI navigation systems may be difficult to explain.

Suppose:

The spacecraft suddenly performs an unexpected orbital manoeuvre.

The operator may not immediately know why.

The system could have:

interpreted sensor data incorrectly;

detected a false collision;

weighted an incorrect input;

suffered model drift;

malfunctioned after an update.

This creates an evidentiary problem similar to other complex AI-liability disputes.

32. Human Oversight

A central question will be:

Could a human reasonably have prevented the autonomous error?

The court may examine:

ground-control staffing;

monitoring frequency;

warning systems;

emergency override;

operator training;

response time;

mission protocols.

If the system was specifically designed to operate autonomously, the claimant may argue that responsibility lies further upstream with the designers and integrators.

33. Manufacturer Liability

A manufacturer may potentially be responsible for:

defective navigation hardware;

defective sensors;

inadequate collision-avoidance mechanisms;

insufficient redundancy;

defective firmware;

inadequate warnings.

The traditional product-liability framework can therefore complement international space law.

34. Software Developer Liability

A software developer may potentially face claims where:

code contains a defect;

navigation logic is unsafe;

update introduces a defect;

cybersecurity vulnerability was inadequately addressed;

documentation fails to disclose a critical limitation.

The legal classification of standalone software and the applicable temporal scope of EU product-liability reforms must be examined carefully in each case.

35. Spacecraft Operator Liability

The operator may be responsible for:

mission planning;

navigation parameters;

maintenance;

updates;

collision-avoidance decisions;

supervision;

communication with ground control.

An operator cannot necessarily avoid all responsibility simply by saying:

“The AI decided.”

36. State Responsibility for Private Space Activities

European private space companies operate within national licensing systems.

A State may therefore have international responsibility for ensuring that non-governmental space activities are appropriately authorised and supervised.

This produces two distinct questions:

International responsibility

Is the State responsible under international space law?

Private civil liability

Can an injured private party obtain compensation from:

operator;

manufacturer;

insurer;

contractor;

State?

These questions should not be confused.

37. Public-Authority Liability

A public authority may face liability if it independently violates a legal duty.

Possible situations include:

negligent regulatory approval;

failure to enforce applicable safety rules;

unlawful administrative decision;

failure to supervise a licensed activity.

The Francovich/Brasserie principles may become relevant when an actionable EU-law breach is established.

38. Autonomous Spacecraft and Product Liability

A useful conceptual model is:

Spacecraft = hardware + software + sensors + AI + communications + navigation system.

If a defect in one integrated component creates an unreasonable safety risk, product-liability principles may become relevant.

But space law remains special because:

product liability does not simply replace the international State-liability regime.

Both regimes may operate at different levels.

39. Important Legal Distinction

International space law

Primarily asks:

Which State is internationally responsible?

Civil law

Asks:

Which private or public actor owes compensation?

Contract law

Asks:

Which contractual obligation was breached?

Product liability

Asks:

Was the product defective?

Tort/delict

Asks:

Was there a wrongful/negligent act causing damage?

Insurance law

Asks:

Who bears the insured loss?

A single autonomous spacecraft accident can therefore generate all five levels simultaneously.

40. Hypothetical Example

Facts

A European company operates an autonomous Earth-observation satellite.

The satellite uses:

Galileo;

onboard AI;

optical sensors;

autonomous collision avoidance.

A software update changes the collision-prediction algorithm.

The AI incorrectly determines that another satellite is on a collision course.

It performs an emergency manoeuvre.

The manoeuvre places it directly into the other satellite's trajectory.

A collision occurs.

Damage

Satellite B is destroyed.

The collision creates debris.

A third satellite subsequently becomes damaged.

The operator of Satellite B claims €200 million.

41. Legal Analysis of the Hypothetical

Issue 1 — Fault

Was the navigation error attributable to:

software developer;

operator;

manufacturer;

AI provider?

Issue 2 — Article III

Because the collision occurred in outer space, the fault-based regime becomes central.

The claimant must establish the relevant fault and causal connection.

Issue 3 — Product defect

Was the software update defective?

Issue 4 — Operator negligence

Did the operator properly test the update before deployment?

Issue 5 — Human supervision

Was a warning available but ignored?

Issue 6 — GNSS

Was the Galileo signal itself inaccurate?

Issue 7 — Causation

Would the collision have occurred without the software update?

Issue 8 — Concurrent causes

Could both:

software defect; and

operator negligence

have contributed?

42. Possible Defences

Defendants may argue:

No defect

The system performed according to its specifications.

No fault

The navigation error could not reasonably have been predicted.

Intervening cause

Another spacecraft acted unpredictably.

Force majeure

An extraordinary solar or space-weather event caused the navigation failure.

Operator fault

The spacecraft operator incorrectly configured the system.

Third-party fault

A separate satellite or debris object caused the accident.

Scientific uncertainty

The failure could not reasonably have been detected using available technical knowledge.

43. Evidence

A successful claim may depend heavily on technical evidence.

Spacecraft evidence

telemetry;

command history;

orbital data;

attitude-control records.

Software evidence

source code;

version history;

update records;

testing results.

AI evidence

training information;

decision logs;

model validation;

anomaly detection.

GNSS evidence

Galileo signal records;

positioning data;

timing information.

Operational evidence

mission-control instructions;

operator communications;

emergency procedures.

44. Expert Evidence

Courts are likely to require experts in:

orbital mechanics;

spacecraft engineering;

AI;

software engineering;

GNSS;

cybersecurity;

space debris;

insurance;

international space law.

An expert may reconstruct the accident:

Input → Algorithm → Decision → Command → Manoeuvre → Collision.

45. Compensation

Possible compensation may include:

spacecraft replacement;

repair;

launch of replacement satellite;

loss of satellite capacity;

lost commercial revenue;

emergency mission costs;

debris-removal expenses;

investigation costs.

Whether consequential economic losses are recoverable depends heavily on the applicable legal regime and contractual arrangements.

46. Case-Law Principles — Revision Table

47. Major Legal Problems

1. AI autonomy

Who is responsible for an independent AI decision?

2. State-centric space law

International liability primarily operates through States.

3. Private victims

Private companies may require domestic mechanisms to obtain compensation.

4. Causation

Navigation errors may involve multiple technological causes.

5. Black-box AI

The operator may not understand why the AI made the decision.

6. GNSS dependence

Autonomous spacecraft may depend on external navigation systems.

7. Space debris

Previous accidents may become contributing causes.

8. Cross-border jurisdiction

Manufacturer, operator, launching State and injured party may all be located in different countries.

9. Insurance

Insurance may determine practical recovery even where legal responsibility is disputed.

10. Lack of direct precedent

European courts have not yet developed a comprehensive body of case law specifically concerning AI-controlled spacecraft navigation errors.

48. Future European Legal Development

The most important future issue is the transition from traditional:

human-controlled spacecraft

to:

autonomous spacecraft capable of making real-time navigation decisions without human approval.

The legal standard may increasingly focus on the entire technological system:

Designer → Manufacturer → Software Developer → AI Provider → Integrator → Operator → Ground Controller → GNSS Provider.

A navigation error may therefore be treated as a systemic liability problem, rather than simply an error committed by a machine.

49. Simple Exam Formula

For an examination answer, use:

Autonomous Navigation Error → Applicable Space Treaty → Launching State → Fault → Causation → Product Defect → Operator Negligence → Contract → EU/National Law → Damage → Compensation.

50. Conclusion

Autonomous spacecraft navigation error claims in Europe occupy the intersection of international space law and civil liability. The central difficulty is that the traditional space-liability system was designed around human and State-controlled space activities, while modern spacecraft increasingly rely upon autonomous software, AI, GNSS, automated collision avoidance and machine-to-machine decision-making.

The Liability Convention remains fundamental: damage on Earth is treated differently from damage occurring in outer space, where fault becomes particularly important. At the European level, cases such as Galileo International Technology v Commission, Airbus Defence and Space v EDA, Francovich, Brasserie du Pêcheur, Boston Scientific, W v Sanofi Pasteur, Commission v United Kingdom, and O'Byrne provide useful principles concerning EU institutional liability, causation, technical products, evidentiary problems, technological risks and complex supply chains. (Eur-Lex)

The most difficult future question will be:

When an autonomous spacecraft makes a navigation decision that no human directly instructed it to make, should the legal responsibility be attributed to the spacecraft operator, manufacturer, software developer, AI provider, navigation-signal provider, launching State, or several of them?

European space-law scholarship already identifies the potential liability gap created when AI-enabled autonomous systems depend upon inaccurate or unavailable GNSS signals, making this a significant emerging field of civil and space liability. (UNIDROIT)