A technological comparison of American, Chinese and European capabilities in satellite inspection, servicing and protection

Scope: This assessment compares publicly documented rendezvous, proximity operations and orbital servicing capabilities in the United States, China and Europe, distinguishing demonstrated performance from development programmes and assessing their strategic implications through 2031.

Executive assessment

The decisive competition in space increasingly concerns the ability to reach, understand and influence another spacecraft, while retaining sufficient mobility and operational endurance to continue the mission.

The United States combines operational geosynchronous inspection with demonstrated commercial satellite life extension. China has advanced into orbital logistics: US Space Command’s 2026 assessment states that Shijian-25 likely extended Shijian-21’s life through docking and refuelling. Europe has demonstrated exceptional autonomous formation accuracy, but its civilian servicing projects, military patrol initiatives and surveillance services remain distinct capabilities at different stages of development. ussf-cfc.spaceforce.mil

The most consequential technical distinctions are between cooperative formation flying, inspection of an unprepared spacecraft, physical capture and sustained servicing. Success in one does not establish mastery of the others.

The procurement implication is direct: governments should assess complete mission performance—navigation, manoeuvre, safety, availability and recovery—rather than satellite numbers or isolated precision claims.

Plesetsk 2026: Russia’s Satellite Power Contest

Europe’s Space Sovereignty Will Be Decided in Its Contracts

Europe’s space spending will buy strategic autonomy only if governments acquire enforceable control over services, recovery and evidence alongside the hardware. That is the contradiction running through programmes from IRIS² to orbital servicing: public money can strengthen domestic industry while leaving the state dependent on someone else’s permission, software or infrastructure when a mission fails. The fiscal stakes are therefore inseparable from the security stakes. A satellite that remains operational but cannot be commanded, a commercial network whose capacity cannot be reassigned, or an inspection service that produces evidence unavailable to government can all satisfy an industrial objective while failing an operational one. Europe’s immediate choice is whether procurement will pay primarily for assets delivered or for authority that remains usable under pressure.

The spending figures measure ambition, not freedom of action

The financial commitments assembled across Europe are substantial, but they measure different things. France’s civil and dual-use commitment exceeds €16 billion through 2030. Germany’s future space-security commitment exceeds €35 billion. The United Kingdom’s commitment amounts to £7.8 billion through 2030. ESA’s 2025 ministerial subscriptions reached €22.3 billion. These figures cannot be added into a defensible European annual budget: they differ in currency, scope, time horizon and institutional treatment. Their common significance is the scale of public exposure before operational independence has been demonstrated.

Italy’s orbital-servicing procurement makes the distinction concrete. The ASI industrial contract amounts to €234.807921 million, with 61% under fixed-price treatment and 39% reimbursable. That allocation determines how part of the financial risk is distributed; it does not establish whether the resulting service can recover a government mission, operate without indispensable external support or provide evidence that the customer can independently assess. Contract value records an obligation to spend. Acceptance conditions determine what the state receives.

The environmental figures also change the economics of procurement. ESA’s Space Environment Report 2026, drawing on data through the end of 2025, records more than 300 launches and more than 4,000 newly deployed payloads during 2025. More than three intact satellites or rocket bodies re-entered daily on average. Each additional fleet therefore enters an operating environment that requires continuing identification, coordination and disposal. Purchasing launch and production capacity without funding those functions transfers costs into the operational years.

IRIS² exposes a further accounting problem. Its revised architecture comprises 348 satellites, an increase of 66, while the original €10.6 billion financing figure belongs to the earlier configuration. Until the revised architecture and its financial treatment are reconciled, the earlier figure cannot be treated as a validated price for the expanded system. The strategic issue is whether governments know which service obligations, operating costs and dependencies their stated commitment actually covers.

Industrial delivery must become an operational obligation

IRIS² and Europe’s orbital-servicing programmes should be judged by the same procurement sequence: delivery, customer acceptance, repeated service and verified performance under disruption. Those stages answer different questions. A successful demonstration establishes that a capability worked under particular conditions. Repeated acceptance establishes that a customer can use it consistently. A disruption exercise establishes whether the service survives the conditions for which governments are paying a security premium.

Italy’s ASI orbital-servicing programme should therefore carry an obligation to demonstrate a usable customer outcome, with access to mission records and an explicit allocation of recovery responsibilities. France should connect its protection concepts to exercises involving operators and political authorities. Germany should make tasking rights and trusted delivery central to acceptance. The United Kingdom should connect authorization, commercial provision and allied information exchange through executable incident procedures. These are proposed procurement conditions; industrial participation alone does not establish that they have been met.

NIST’s satellite command-and-control and hybrid-network frameworks identify why this transmission mechanism matters. Space services depend on interconnected systems, often under different ownership. Two apparently competing providers may depend on the same identity service, ground operator, software supplier or terminal manufacturer. Procurement that counts suppliers without examining shared dependencies can purchase the appearance of redundancy while retaining a common point of failure.

The commercial consequence follows directly from NIST’s system-wide approach: recovery rights must be priced before a contract is signed. Government access to relevant telemetry, support-transfer provisions, configuration records and participation in exercises impose costs on suppliers. Omitting them may reduce the acquisition price while increasing the cost of failure. The buyer then discovers during an incident that the information or authority required for recovery belongs to another organization.

KA-SAT showed why the satellite is the wrong unit of protection

The KA-SAT disruption of February 2022 remains a decisive procurement example because the satellite itself was unaffected, according to Viasat’s incident account. A ground-based intrusion disrupted users, and recovery included the physical replacement of modems. Protecting the spacecraft did not preserve the service. Restoring central infrastructure did not automatically restore every endpoint.

The EU’s attribution of the KA-SAT activity to the Russian Federation in May 2022 also separates two decision clocks. Operators had to restore service before governments completed their public attribution. A protection architecture that makes technical recovery dependent on a political conclusion therefore builds delay into the response. Conversely, rapid recovery does not require an operator to claim knowledge of an attacker’s intent that the evidence cannot support.

For IRIS² and other government-purchased networks, the contractual consequence is to measure recovery where the mission consumes the service. An annual availability percentage can conceal the loss of a critical location or user group. Acceptance should establish the longest continuous outage, the time required to restore trusted control, the activation time of an alternative provider and the ability to reject misleading information. These measures reveal whether redundancy reaches the user or stops at the provider’s network boundary.

NIST’s frameworks support this broader risk assessment, but they do not certify a constellation’s resilience. Governments must still require witnessed exercises across the delivery chain. Otherwise, each contractor can demonstrate that its component behaved as specified while the public service remains unavailable. The resulting dispute concerns contractual boundaries precisely when the customer needs a functioning mission.

Legal obligations cap the freedom that technology appears to offer

The Outer Space Treaty prevents governments from treating orbital intervention as an unrestricted technical option. Article VI requires authorization and continuing supervision of non-governmental activities. Article VIII preserves jurisdiction, control and ownership. Article IX establishes due-regard and consultation provisions. An inactive object is consequently not an ownerless industrial opportunity, and proximity alone does not settle whether an operation is unlawful.

For inspection and servicing programmes, those provisions make authorization part of the delivery schedule. A vehicle capable of approaching an object is not automatically a service that a customer can lawfully task. Procurement must establish who consents, who commands, who receives evidence and who bears responsibility if the operation changes another object’s condition. Leaving those questions unresolved can strand an otherwise functional capability.

ESA’s debris-mitigation requirements add a separate constraint: disposal must be designed and verified within the applicable mission framework. Propellant, reliability, end-of-life procedures and disposal capability cannot be treated as resources available without restriction for other purposes. Protection decisions that consume those resources can alter the mission’s remaining options and obligations.

NATO’s space policy places another limit on automatic reasoning. Space-related attacks may lead to an Article 5 decision, but the assessment is case by case. An unexplained approach is not itself a collective-defence trigger. Europe therefore needs contracts that preserve evidence as carefully as they preserve service: synchronized records, retention rights and procedures for sharing an incident account can affect the credibility of a subsequent political response.

Cooperation works only when access survives the crisis

NATO’s HALO, STARLIFT and APSS initiatives address different parts of the cooperation problem: integrating sovereign capabilities, improving launch access and supporting space-based surveillance information. Their procurement value will depend on what participating governments can actually obtain through them. Membership cannot substitute for an exercised arrangement that delivers information, capacity or access within the operational deadline.

IRIS² faces the same test inside Europe. Shared infrastructure does not eliminate the need to decide whose traffic takes priority when capacity is constrained, which authority can redirect service and what information national users may receive. Those rules determine the distribution of scarcity. If governments postpone them until a crisis, the architecture will encounter a political negotiation at the point where it requires an operational instruction.

Comparison with the United States and China should consequently use an identical evidence ladder: funded development, hardware delivery, orbital demonstration, customer acceptance, repeated service and performance under disruption. A capability demonstrated in one function cannot establish maturity in another. Nor should incomplete public evidence be converted into certainty about either superiority or weakness.

For Europe, NATO cooperation and national control can reinforce one another when responsibilities are explicit. Shared observations can strengthen attribution; qualified alternatives can reduce dependence; common acceptance criteria can widen the supplier base. NATO’s preservation of national sovereignty nevertheless leaves governments responsible for defining the authority they retain. Cooperation becomes usable when that authority has a procedure, an authenticated decision-maker and a tested route to execution.

The next procurement cycle will allocate the cost of dependence

Over the next 12–24 months, the consequential choice for IRIS², ASI’s orbital-servicing programme and national protection procurements will be whether contracts secure evidence access, recovery authority, crisis allocation and support transfer before dependencies become embedded. These provisions are easier to negotiate while suppliers are competing for an award. After integration, changing them can require additional engineering, qualification and commercial concessions.

ASI’s programme should release acceptance payments against demonstrated customer outcomes. IRIS² should reconcile its expanded architecture with financing and service obligations. National protection contracts should require exercises that remove a primary control facility, interrupt vendor support or constrain available capacity. These are proposed decisions with identifiable costs; each would make a claim of autonomy testable before an operational emergency.

If those decisions are deferred, the cost will fall first on public users whose missions depend on inaccessible capacity or unavailable support. Contractors may still have delivered their specified hardware, and governments may still report industrial expenditure. The unresolved obligation will return to the state as emergency purchases, recovery work or a renewed dependence on allied and commercial assistance.

Europe’s spending on IRIS², orbital servicing and national space security will therefore have two possible contractual legacies: assets accompanied by usable authority, or assets whose critical conditions of use remain elsewhere. The next procurement cycle will determine which obligations taxpayers finance now—and which failures they will be asked to finance again.

Starlink – MULTI-DOMAIN INTELLIGENCE SYNTHESIS: DE-ANONYMIZATION OF LEO SATELLITE ARCHITECTURES VIA ADINT CONVERGENCE

---

Navigational index

Pillar I — The engineering of orbital access

• Chapter 1 — Relative navigation, autonomy and the physics of proximity.
• Chapter 2 — Inspection, docking, manipulation and orbital logistics.
• Chapter 3 — American, Chinese and European systems: comparative performance and maturity.

Pillar II — Industrial capacity and European sovereignty

• Chapter 4 — Production, launch, ground infrastructure and service economics.
• Chapter 5 — Italy, France, Germany, the United Kingdom and the European institutional architecture.

Pillar III — Protection, escalation and strategic choice

• Chapter 6 — Satellite vulnerability, attribution and operational resilience.
• Chapter 7 — Development pathways and observable indicators to 2031.
• Chapter 8 — Procurement priorities, cooperation options and final assessment.

---

Italian Space Sovereignty Strengthened: Digital Twin Integration Enables 100+ Satellites/Year Capacity at PNRR-Funded Facility

Master abstract

The critical capability is controlled access to another spacecraft

An inspector, a servicing vehicle and a protective patrol satellite share important engineering foundations. Each must acquire a target, estimate its relative motion, navigate safely and execute controlled manoeuvres. Their missions diverge after that point. An inspector needs useful observations; a servicer must establish a mechanically and operationally compatible connection; a protective vehicle must contribute to an authorised response without endangering the spacecraft it is intended to protect.

These distinctions make a single international ranking misleading. NASA’s technical assessment identifies relative position, velocity and attitude estimation, onboard navigation filters, constrained guidance and suitable actuators as essential elements of autonomous proximity operations. A capable sensor does not compensate for unreliable propulsion, and sophisticated guidance software cannot overcome inadequate power or failed control hardware. NASA

The appropriate comparison is therefore between mission chains. Can the system find the object, approach it, maintain useful relative geometry, complete its task and leave safely? Can it repeat that sequence under realistic illumination, communications and propellant constraints? Can its operator sustain the service rather than demonstrate it once?

On the evidence examined, American programmes offer the clearest combination of operational inspection and commercially delivered life extension. China’s progress makes sustained orbital mobility an increasingly important competitive variable. Europe possesses substantial enabling technology, but the practical value of that technology depends on its integration into available spacecraft, launch arrangements and operational organisations. This is an assessment of the disclosed record, rather than a claim about the full extent of classified capabilities.

United States: inspection, servicing and responsive deployment

The Geosynchronous Space Situational Awareness Program, GSSAP, provides a documented military inspection capability. The US Space Force describes spacecraft operating near the geosynchronous belt and conducting rendezvous and proximity operations to characterise objects, resolve anomalies and improve surveillance. Its published mission establishes operational inspection; it does not establish physical capture, refuelling or a particular offensive payload. ussf-cfc.spaceforce.mil

Commercial servicing provides a separate and more tangible benchmark. Northrop Grumman reports that MEV-1 docked with Intelsat 901 on 25 February 2020, completed its five-year assignment in April 2025 and docked with another client in May 2025. MEV-2 docked with Intelsat 10-02 in April 2021. The vehicle supplies propulsion using its own thrusters and propellant while attached to the client. This demonstrates delivered life extension and, for MEV-1, reuse across successive assignments. It is distinct from transferring fuel into the client’s tanks. Northrop Grumman

The 2026 VICTUS HAZE mission adds a different capability: rapid deployment of a manoeuvrable spacecraft. Rocket Lab records an Electron launch on 19 June, 16 hours and 42 minutes after notice to launch, followed by spacecraft commissioning in 37 hours and 36 minutes. The company reports subsequent low Earth orbit proximity operations in a simulated threat-response scenario. These are separate milestones; launch responsiveness alone does not measure the time required to complete an orbital inspection or protective mission. Rocket Lab

Together, these programmes show why American capability should be understood as an ecosystem. Surveillance, close inspection, attached propulsion support and responsive launch address different operational problems. Their strategic value grows when they can exchange information and support a common decision process, although the public evidence does not establish that every component already functions as one seamless service.

China: orbital logistics changes the endurance calculation

China’s official announcement identifies Shijian-25 as a spacecraft for verifying satellite fuel replenishment and life-extension technologies. It launched from Xichang on 7 January 2025, Beijing time. The announcement establishes the mission’s declared purpose and launch, rather than the successful completion of every intended experiment. english.www.gov.cn

The more consequential subsequent assessment appears in US Space Command’s 2026 congressional posture statement. It states that Shijian-25 likely extended Shijian-21’s operational life through docking and refuelling in geosynchronous orbit. That qualification matters: the statement supports an assessment of probable success, but does not disclose transferred propellant mass, interface characteristics, transfer efficiency or the recipient’s resulting manoeuvre budget. The same document identifies complex Chinese close-approach activity involving multiple spacecraft in low Earth orbit during 2024. armedservices.house.gov

The strategic mechanism is nevertheless significant. A spacecraft that depends entirely on its launch-loaded propellant faces a finite lifetime allocation between stationkeeping, mission manoeuvres, contingency actions and disposal. Replenishment could relax that constraint and support repeated assignments. The magnitude of the advantage depends on reliable transfers, compatible clients, available servicing vehicles and an economically sustainable replenishment chain.

This does not justify treating every Chinese servicing technology as a demonstrated weapon. It does justify evaluating orbital logistics alongside inspection and manoeuvre. A vehicle’s ability to reach another satellite and its ability to remain useful after repeated encounters are different measures of power.

The Geopolitical Weaponization of Commercial Low Earth Orbit Satellites: OSINT Signal Analysis of Global Starlink Deployments

Europe: precision is demonstrated; operational integration remains decisive

Europe’s strongest disclosed precision benchmark is Proba-3. ESA reported in May 2025 that its two spacecraft maintained autonomous formation at a separation of approximately 150 metres, achieving millimetric longitudinal and sub-millimetric lateral accuracy. The system combines cameras observing cooperative visual references, laser metrology and a shadow-position sensor. Crucially, formation flying occurs above 50,000 kilometres, where the mission’s geometry reduces the propellant needed to maintain the formation. These conditions prevent a direct comparison with an uncooperative low Earth orbit encounter. Proba-3 achieves precise formation flying

Proba-3 demonstrates European mastery of a demanding cooperative control problem. It does not independently demonstrate capture of an unfamiliar spacecraft, persistent low Earth orbit pursuit or military protection. ESA’s June 2026 update reported that the Coronagraph spacecraft and its principal scientific instrument were healthy and ready to resume routine formation operations, adding operational context beyond the initial precision achievement. Proba-3 blog

European servicing is advancing through a different route. ESA’s RISE agreement with Italy’s D-Orbit provides a €119 million contract, supplemented by company co-funding, for a vehicle intended to dock with a geostationary client, manoeuvre it and release it. ESA’s published baseline anticipates launch in 2028 and an approximately eight-year mission. The design uses the client’s launch-adapter ring and takes over attitude and orbit control while the client retains its own power, communications and payload functions. These are contracted mission objectives, not completed servicing results. esa.int

Europe therefore has meaningful technological assets without a uniform level of operational maturity. Its central challenge is to connect precision navigation, robotics, spacecraft production, surveillance and national military requirements into services with explicit availability and mission responsibilities.

Key evidence table

The figures below describe different engineering or programme variables. They are not interchangeable measures of superiority.

Indicator	Value/status	Reference date	Definition/scope	Issuer	Exact source
GSSAP proximity operations	Operational mission publicly documented	Fact sheet current to October 2021	Near-geosynchronous inspection and characterisation; not a current fleet count	US Space Force	Geosynchronous Space Situational Awareness Program. ussf-cfc.spaceforce.mil
MEV-1 service and reuse	Five-year assignment completed; subsequent client docking reported	April–May 2025	Attached propulsion support; distinct from fuel transfer	Northrop Grumman	SpaceLogistics. Northrop Grumman
VICTUS HAZE notice to launch	16 h 42 min	19 June 2026	Notice-to-liftoff interval; excludes later commissioning	Rocket Lab	VICTUS HAZE. Rocket Lab
Shijian-25 mission purpose	Fuel-replenishment and life-extension verification	7 January 2025	Officially declared experimental purpose	Chinese government/SAST	China launches test satellite for orbital refueling. english.www.gov.cn
Shijian-25 servicing outcome	Docking/refuelling assessed as likely to have extended Shijian-21’s life	2026 testimony	Attributed US military assessment; no disclosed transfer quantity	US Space Command	2026 Posture Statement, pp. 5–6. armedservices.house.gov
Proba-3 formation	Approximately 150 m separation; millimetric range accuracy	8 May 2025	Cooperative autonomous formation above 50,000 km	ESA	Proba-3 achieves precise formation flying. Proba-3 achieves precise formation flying
RISE	€119 million contract; 2028 launch baseline	Agreement announced October 2024	Planned geostationary docking, manoeuvre and release	ESA/D-Orbit	ESA to build first in-orbit servicing mission with D-Orbit. esa.int
Orpheus	Critical Design Review completed; launch planned for 2027	8 April 2026	Two-spacecraft formation mission; design milestone	Astroscale UK	Astroscale UK Completes Critical Design Review for Orpheus Mission. astroscale.com

The engineering distinctions that determine a fair comparison

A technically non-cooperative target does not necessarily mean an unwilling operator. An authorised servicing mission may approach a client that lacks navigation beacons, docking fixtures or functioning attitude control. Conversely, an active spacecraft can possess cooperative hardware while its operator declines an encounter. Physical preparation, operational cooperation and legal consent are separate variables.

The navigation problem becomes more demanding when the approaching spacecraft cannot rely on known markers or a shared navigation solution. NASA’s FlashPose illustrates one relevant approach: it processes three-dimensional range and intensity measurements, matches the resulting point cloud against a target model and estimates relative position and orientation. This demonstrates a concrete method for estimating a target’s pose; it does not remove dependence on sensor visibility, model suitability or validated control behaviour. T2 Portal

Capability	What must be established	What success alone does not establish
Cooperative formation flying	Accurate relative navigation and controlled separation under agreed conditions	Approach to an unfamiliar, tumbling or evasive target
Close inspection	Useful observations at a controlled distance and geometry	Docking compatibility or physical manipulation
Docking and capture	Stable contact, load management and control of the combined system	Fluid transfer or component replacement
Attached life extension	Reliable propulsion and attitude support for the client	Replenishment of the client’s own tanks
Refuelling	Compatible interfaces and successful propellant transfer	Repair, rearming or unlimited operational endurance
Satellite protection	Detection, attribution, authorised action and preservation of service	Guaranteed protection merely because a patrol vehicle is nearby

The last row is particularly important for procurement. A patrol spacecraft can improve observation or response options, but protection must be evaluated through the survival and continued utility of the supported mission. An inspection vehicle, a spare imaging satellite and a servicing spacecraft can each improve resilience through different mechanisms.

Europe’s national positions

Italy: a potential operating position in the servicing market

RISE gives Italy a concrete industrial route into geostationary life extension through D-Orbit. The relevant strategic opportunity is to build an enduring service business around the spacecraft: flight operations, client qualification, mission assurance and successive servicing assignments.

The principal decision is how much public value should depend on a single demonstration. A technically successful mission would establish an important foundation, but commercial continuity would require customers, reliable operations and financing for subsequent vehicles. Italy’s strongest position would arise from retaining the ability to operate the service and evolve its technology across missions, rather than capturing development expenditure alone.

France: military ambition requires demonstrated delivery

French parliamentary records distinguish several initiatives. In May 2026, the Senate’s defence proceedings described an incremental approach under Egide, involving Yoda and Paladin in geostationary orbit and Toutatis in low Earth orbit. These references establish the intended programme architecture; they do not establish that all vehicles were deployed or operational. senat.fr

The National Assembly’s 7 May 2026 debate provides a material warning about schedule interpretation. Members stated that Yoda’s demonstration had not occurred, while the debate contained competing explanations concerning industrial readiness and launcher availability. A parliamentary allegation should not be treated as a settled technical diagnosis. The defensible conclusion is that the record documents delivery concerns and a disputed explanation for delay. Assemblée nationale

France’s decisive milestone is consequently an evidenced orbital mission, followed by repeatable operations under military authority. Programme names, strategic intent and technology demonstrations must remain distinct from an available protection service.

Germany: robotics and qualification infrastructure

Germany’s contribution extends beyond the production of complete spacecraft. DLR identifies CAESAR robotic technology, the EPOS 2.0 proximity-operations simulator and OOS-SIM as elements of its servicing and orbital robotics work. Its description of EROSS includes preparation for a mission involving rendezvous and robotic tasks such as capture, refuelling and component exchange. The source describes development and preparation, rather than a completed orbital service. dlr.de

This creates an industrial opportunity in systems that several European missions may need: navigation validation, capture mechanisms, robotic control and contact-dynamics testing. The policy challenge is to make successful qualification translate into flight hardware and sustained orders. Test facilities reduce development risk; their strategic return depends on the missions that use them.

United Kingdom: operations, formation missions and regulatory coordination

Astroscale UK reported completion of Orpheus’s Critical Design Review in April 2026. Its published description envisages two Open Cosmos-built spacecraft operating in close formation, with a planned 2027 launch. The disclosed £5.15 million contract concerns the stated Dstl procurement arrangement; it should not be read as the cost of an entire sovereign orbital-protection capability. astroscale.com

The UK’s September 2026 Space Strategy also records completion of an RPO regulatory sandbox in March and arrangements with New Zealand concerning multijurisdictional proximity missions. This addresses a practical constraint on commercial servicing: the spacecraft operator, launch provider, client and responsible authorities may sit in different jurisdictions. Regulatory coordination can make a mission executable, although it remains separate from flight performance. GOV.UK

European Union: surveillance must connect to operational decisions

EU Space Surveillance and Tracking provides an existing coordination layer. Its current description lists 19 participating member states, more than 400 receiving organisations and more than 700 satellites supported against collision risk. It assigns collision-avoidance services to French and Spanish operations centres, re-entry and fragmentation services to the Italian centre, and responsibility for the common database and future catalogue to Germany. These are service roles and coverage figures, rather than a count of European military inspection spacecraft. EU SST

The strategic requirement is to connect such surveillance information to the organisations empowered to decide and act. Civil collision assessment, military attribution and spacecraft command serve related but different purposes. Europe’s effectiveness will depend on timely coordination between them.

Operational relationship: a shared foundation, different mission requirements

Competing development pathways

The evidence supports three potentially overlapping pathways. They are conditional assessments, not probability forecasts.

Pathway	Mechanism	Evidence supporting the pathway	Decisive indicator
Inspection remains the principal operational use	Navigation and sensing deliver value without the added complexity of contact	Operational GSSAP mission; responsive inspection demonstration architecture	Repeatable inspection missions with documented availability
Servicing makes orbital mobility more sustainable	Attached propulsion or replenishment extends useful service	MEV service history; assessed Shijian-25 demonstration; contracted RISE objectives	Repeated servicing across clients with disclosed operational results
Europe integrates complementary national capabilities	Robotics, formation control, surveillance and operations support shared missions	Proba-3 results, national programmes and EU SST service architecture	Joint missions with named authority, committed spacecraft and sustained operating arrangements

These pathways are supported by the programme records examined; their relative importance will depend on repeatability, reliability and deployment rather than announcement volume. ussf-cfc.spaceforce.mil

Principal gaps and watch indicators

Operational endurance. Public descriptions rarely provide directly comparable usable propellant, manoeuvre budgets or remaining service life. Consequential evidence would include disclosed propulsion performance, repeated manoeuvre histories and verified servicing results. Vehicle mass or advertised mission duration cannot substitute for these measures.

Refuelling repeatability. For China, the major unresolved technical questions concern transferred quantity, recipient performance after the encounter and the ability to repeat servicing. Additional official mission results or sustained subsequent recipient manoeuvring would strengthen the assessment of an operational logistics capability.

European delivery. RISE’s flight qualification, launch and completed docking sequence would materially change Europe’s servicing position. For military patrol programmes, the relevant evidence is a documented orbital demonstration followed by operational acceptance—not a revised target date alone.

Autonomy under failure. Procurement should require evidence of safe behaviour during sensor loss, navigation divergence, actuator anomalies and interrupted communications. NASA’s review records missions whose proximity objectives were constrained by propulsion and control failures, demonstrating why navigation performance must be assessed alongside hardware reliability. NASA

Mission continuity. Resilience should be measured through delivered service. For a radar-imaging architecture, relevant contractual measures include successful tasking, acquisition timeliness, processing and delivery latency, replacement capacity and ground-system availability. ICEYE’s July 2026 announcement reports 76 cumulative satellite launches and Gen4 imagery specifications of up to 16-centimetre resolution with a 400-kilometre high-resolution field of regard. Cumulative launches do not establish the active fleet, and field of regard must not be read as a single continuous image swath. iceye.com

Comparable cost. Development contracts, experimental procurements and commercial service payments cover different activities. The available figures do not support a defensible international cost-per-protected-satellite ranking.

The governing strategic judgment is that orbital mobility becomes durable power when it is repeatable, supportable and connected to a useful mission outcome. The United States has documented strengths in operational inspection and delivered servicing; China’s assessed refuelling progress raises the importance of endurance; Europe’s opportunity lies in converting substantial enabling technology into sustained operational services.

---

Pillar I — The engineering of orbital access

Technical assessment as of 20 October 2026. Calculated examples are explicitly distinguished from spacecraft specifications and reported mission results.

Chapter 1 — Relative navigation, autonomy and the physics of proximity

The principal constraint on orbital access is the integration of geometry, navigation and propulsion into a system that can reach the required relative state and remain safe when its estimates or hardware fail. A spacecraft can possess excellent cameras and still lack the manoeuvre capacity to reach a target. It can possess substantial propellant and still lack the relative navigation needed for a controlled approach. These limitations must be assessed together.

Orbital position is only one part of the access problem

A meaningful rendezvous requires control of relative velocity as well as relative position. Two spacecraft can pass close to one another while following substantially different trajectories; their short encounter does not establish the ability to maintain a useful inspection geometry. Conversely, a deliberate rendezvous can culminate in a relatively stable separation without immediate physical contact.

The cost of reaching that condition depends strongly on orbital-plane alignment. Changes within an existing plane can exploit differences in orbital period to accumulate separation or close a gap over time. Changing the plane itself requires redirecting the velocity vector and can impose a much larger propellant burden. NASA’s orbital-design primer illustrates both the relationship between drift time and manoeuvre cost and the expense of plane changes in low Earth orbit. GDC Orbit Primer — NASA Goddard Space Flight Center — October 2018, slides 18–21.

For an ideal impulsive change between planes with the same orbital speed:

Δv = 2v × sin(Δα/2)

Here, Δα is the angle between the two orbital planes. It is not necessarily equal to the difference between their listed inclinations: the orientation of their ascending nodes also matters.

The following calculations use circular two-body orbits, an Earth equatorial radius of 6,378.137 kilometres and a rounded gravitational parameter of 398,600 km³/s². They exclude atmospheric drag, Earth’s nonspherical gravity, finite-burn losses and other perturbations. The constants follow NASA’s Earth Fact Sheet.

Illustrative circular orbit	Orbital speed	Orbital period	Ideal Δv for 1° plane change	Ideal Δv for 5° plane change
500 km altitude	7.613 km/s	94.62 minutes	132.9 m/s	664.1 m/s
1,000 km altitude	7.350 km/s	105.12 minutes	128.3 m/s	641.2 m/s
35,786 km altitude	3.075 km/s	1,436.07 minutes	53.7 m/s	268.2 m/s

Calculated values, rounded as displayed. The GEO-altitude example is an ideal circular equatorial case; the table does not represent the manoeuvre budget of any named spacecraft.

The operational implication is that nominally global reach does not mean rapid access to every satellite. A vehicle may be well positioned to inspect several objects sharing a compatible orbital region while being poorly positioned for a nearby object in a different plane. Initial deployment geometry, available waiting time and remaining manoeuvre capacity can therefore matter more than physical distance at a particular moment.

This also changes the interpretation of responsive launch. A short notice-to-liftoff interval is valuable, but launch must place the vehicle into an orbit from which it can complete the intended task. Readiness on the ground and accessibility in orbit are separate requirements.

Navigation must estimate a changing state, not produce a single distance

Close operations require an estimate of relative position, relative velocity, target orientation and, where relevant, target rotation. Navigation must also characterise uncertainty: a plausible best estimate is insufficient when the error distribution could place the vehicle inside an unsafe approach corridor.

NASA’s spacecraft tracking assessment distinguishes routinely distributed orbital elements from precision state information accompanied by covariance. Its conjunction-assessment research explicitly states that Two-Line Elements are insufficient for collision-avoidance mitigation decisions. A highly precise-looking separation calculated from public elements therefore should not automatically be treated as a verified close-approach measurement. Identification and Tracking Systems — NASA and CARA Research and Development — NASA. NASA

The important distinction is between locating both spacecraft in a common reference frame and measuring one spacecraft directly relative to the other. The first supports acquisition and broad trajectory planning. The second becomes increasingly important as the permitted separation and uncertainty decrease.

Navigation element	Principal contribution	Important limitation	Evidence required for qualification
Ground-derived orbit determination	Establishes absolute trajectory and supports initial acquisition	Update latency and manoeuvre uncertainty can degrade predictions	Residual statistics, update frequency and covariance realism
GNSS-based navigation	Provides onboard position and timing where signal geometry permits	Absolute position accuracy does not automatically equal relative-navigation accuracy	Performance across the actual orbit and antenna configuration
Optical bearing measurements	Establish target direction and track visible features	A bearing alone does not directly provide complete range and velocity information	Acquisition reliability and estimator convergence
Cooperative visual markers	Improve identification and pose estimation	Require a prepared, visible client configuration	Performance under changing illumination and partial obstruction
Laser ranging or imaging lidar	Adds range or three-dimensional target information	Return quality and usable geometry depend on target and sensor characteristics	Range, reflectivity and interference test envelopes
Target-model matching	Estimates position and orientation from observed structure	Depends on model adequacy and identifiable geometry	Robustness to occlusion, configuration changes and ambiguous features
Sensor fusion	Combines complementary measurements and propagates state estimates	Inconsistent timing or biased measurements can undermine the combined solution	End-to-end testing with realistic faults and uncertainties

This table is an engineering synthesis. It defines assessment functions rather than asserting that every listed method is present on each national system.

A concrete example is NASA’s FlashPose technology. It converts three-dimensional measurements into a point cloud and iteratively aligns that cloud with a target model to estimate relative translation and rotation. The underlying method illustrates why onboard processing matters: measurements must become a sufficiently reliable state estimate before they can support guidance and control. It also shows why “autonomous navigation” is too broad a label to compare without specifying the target assumptions. FlashPose: Range and intensity image-based terrain and vehicle relative pose estimation algorithm — NASA Technology Transfer.

Angular accuracy and spatial accuracy must remain distinct

Sensor specifications are often expressed as angular errors, while mission requirements concern physical displacement. Under a small-angle approximation, the transverse error associated with a bearing error is:

Transverse error ≈ range × angular error

For an assumed angular error of 10 microradians:

Target range	Assumed angular error	Corresponding transverse error
100 m	10 μrad	1 mm
1,000 m	10 μrad	10 mm
10,000 m	10 μrad	100 mm

Calculated geometry only. These are not specifications for a particular sensor and do not include calibration, attitude, timing, structural or estimation errors.

The same angular specification produces different physical errors at different ranges. Moreover, transverse precision does not establish range precision. A system can track a target’s direction accurately while retaining a less certain estimate of distance along the line of sight.

A useful technical comparison must consequently state the coordinate component, measurement range, confidence convention and operating conditions associated with an accuracy claim. “Centimetre navigation” without those definitions is inadequate for assessing docking readiness.

Precision control depends on the smallest usable impulse

An actuator must provide both sufficient control authority and sufficiently fine control increments. The minimum impulse bit—the smallest reliably delivered thrust impulse—helps determine how gently the spacecraft can correct its motion. The resulting velocity increment depends on spacecraft mass:

Δv = impulse / mass

An illustrative impulse of 0.001 newton-seconds changes the velocity of a 100-kilogram spacecraft by 0.00001 m/s, or 10 micrometres per second. The same impulse applied to a 500-kilogram vehicle produces one-fifth of that increment. These calculated values show why thruster specifications cannot be assessed independently of the spacecraft.

NASA’s propulsion assessment identifies small impulse bits as an advantage of cold-gas systems, while noting that their low specific impulse constrains large orbital corrections. Fine control and long-range mobility therefore need not favour the same propulsion architecture. In-Space Propulsion — NASA, Small Spacecraft Technology State of the Art.

Proba-3 makes this division tangible. ESA’s technical description assigns approximately 10-millinewton cold-gas propulsion to the Occulter for precision formation maintenance, while the Coronagraph uses a one-newton-scale monopropellant system for other manoeuvres, including collision avoidance. Its navigation architecture also changes with orbital location and separation: GNSS is used in the lower orbital segment, visual sensing supplements closer operations, and laser metrology supports fine positioning. Proba-3 Technologies — ESA — November 2024.

Autonomy must include the authority to stop

The most important autonomous action during a difficult encounter may be to suspend the planned sequence. A navigation algorithm that continues approaching after losing confidence in its target estimate is less operationally useful than one that recognises its limits and transitions safely.

Qualification should therefore distinguish several functions:

Autonomy function	Decision performed onboard	Appropriate verification question
Measurement validation	Accept, reject or down-weight sensor observations	Can corrupted or inconsistent data be detected?
State estimation	Update relative position, velocity and orientation estimates	Does uncertainty remain consistent with actual errors?
Guidance	Select a trajectory satisfying mission constraints	Are separation and actuator limits respected?
Control	Translate guidance into actuator commands	Is performance retained under realistic disturbances?
Fault management	Isolate or accommodate failed equipment	Can the vehicle remain controllable after specified faults?
Mission supervision	Continue, hold, retreat or terminate a phase	Are transitions safe and understandable to operators?
Ground coordination	Exchange status and accept authorised changes	Can the mission tolerate communications interruptions?

NASA’s guidance-and-control review records proximity missions constrained by propulsion and actuator problems, including incomplete docking objectives. These cases establish that algorithmic progress and mission completion are separate measures. Hardware reliability, operational recovery and safe degradation belong inside the autonomy assessment. Guidance, Navigation, and Control — NASA.

Key judgments

Orbital accessibility should be specified as a combination of reachable orbital geometry, time to task, navigation performance and remaining manoeuvre capacity. No single distance, launch interval or sensor-accuracy figure captures that combination.

The strongest evidence of autonomy is successful operation across nominal and faulted conditions with explicit limits. Demonstrations against prepared targets remain valuable, but their results must retain the conditions under which they were achieved.

What would change the assessment: published end-to-end results showing repeatable acquisition, controlled approach and safe withdrawal across different target configurations, together with uncertainty estimates and degraded-mode performance.

Open official record: comparable operational envelopes for military inspection vehicles—including usable manoeuvre budgets, target-acquisition limits and fault-response performance—remain insufficiently disclosed for a numerical international ranking.

Chapter 2 — Inspection, docking, manipulation and orbital logistics

Physical servicing introduces a different engineering problem from close observation: the servicer must interact with the client’s structure, dynamics and systems without creating an unacceptable failure. The most consequential technologies are therefore interfaces, force-controlled robotics, fluid management and the ability to verify that the client remains usable after intervention.

Servicing difficulty begins with the client’s design

A satellite can be authorised for servicing while lacking the hardware needed to make that servicing straightforward. A stable client with accurate engineering documentation, visible reference features and an accessible docking point presents a different problem from an aged spacecraft with uncertain geometry, damaged appendages or uncontrolled rotation.

Three distinct questions determine the intervention:

Client characteristic	Lower-complexity condition	More demanding condition	Consequence for servicing
Navigation preparation	Cooperative markers or relative-navigation aids	Unprepared external structure	Greater dependence on natural-feature identification and target modelling
Attitude state	Stable and commanded	Uncontrolled or rotating	More complex approach, contact and stabilisation
Structural interface	Qualified capture fixture	Legacy structure requiring characterisation	Greater uncertainty about load paths and contact limits
Fluid interface	Robotic service valve	Ground-only valve, caps and protective features	More tools, operations and verification steps
Documentation	Current configuration and material data	Incomplete or outdated records	Additional inspection and conservative operating constraints
System health	Known power, thermal and propulsion condition	Partially failed or uncertain system	Reduced tolerance for intervention and harder outcome verification

These distinctions also explain why the servicing market is unlikely to be uniform. The technically reachable fleet and the economically serviceable fleet are different populations. A satellite may be physically accessible but offer too little remaining payload value to justify a complex intervention.

Contact creates a coupled mechanical system

Before capture, the servicer and client are separate vehicles. During contact, forces pass through the end effector, robot arm and spacecraft structure. After capture, attitude control must account for the combined mass distribution and inertia.

The engineering challenge is not merely to close a gripper. A stiff contact against a moving structure can produce unwanted loads. A manipulator moving relative to a free-flying base also influences that base’s motion. Force and torque sensing, compliance and coordinated control help manage these interactions.

DLR’s CAESAR specification provides a useful European reference. It describes a seven-degree-of-freedom arm with torque sensing in every joint, impedance control and configuration-dependent dimensions. The published figures are component characteristics, not a demonstrated operational envelope for capturing every class of satellite. CAESAR — DLR Institute of Robotics and Mechatronics.

CAESAR parameter	Published characteristic	Interpretation
Degrees of freedom	7	Provides kinematic redundancy for positioning and orientation
Extended-arm length	Minimum approximately 2.4 m; up to 5 m depending on configuration	Mission configuration changes the working envelope
Mass reference	Approximately 60 kg for a 3 m arm	Component figure, excluding the complete servicing spacecraft
Maximum joint torque	80 N·m per joint	Does not directly establish allowable client contact loads
Maximum joint speed	Up to 10°/s	Upper component capability, not a recommended capture speed
Operational temperature	−20°C to +60°C	Thermal control must preserve functionality within the stated range
Published GEO mission-time objective	Up to 10 years	Design characteristic rather than completed service duration

A long arm also creates thermal and structural challenges. DLR’s July 2026 CAESAR study examines changing illumination, arm postures, heaters, radiators and insulation for the EROSS servicing application. It identifies configuration-dependent heat rejection and self-shadowing as material design issues, while reserving further work for proximity operations and coupled interactions with the client. Thermal Design of the CAESAR Multi-Degree-of-Freedom Robotic Arm for On-Orbit Servicing — DLR — July 2026.

The procurement consequence is that a qualified joint or manipulator is only one level of evidence. The complete vehicle must also demonstrate coordinated navigation, contact control, thermal management and post-capture stabilisation.

Refuelling requires a complete fluid-transfer chain

Successful physical connection does not establish successful replenishment. The transfer system must deliver the correct substance, maintain compatible pressure and temperature conditions, measure the delivered amount and avoid unacceptable leakage or contamination.

NASA’s propellant-transfer work identifies pumps, metering devices, tubing, deployable hoses and specialised nozzle tools as parts of that chain. Its descriptions also distinguish station-based experiments using a safer substitute fluid from ground testing with actual hazardous oxidiser. These are different demonstrations and should retain their respective environments and materials. Propellant Transfer Technologies — NASA.

Transfer function	Engineering requirement	Consequence of failure
Commodity identification	Match the transferred medium to the recipient system	Chemical incompatibility or unusable replenishment
Mechanical coupling	Establish a stable, qualified connection	Leakage or loss of interface control
Pressure management	Maintain acceptable conditions across source, line and receiver	Transfer interruption or hardware damage
Thermal management	Keep fluid and components inside operating limits	Degraded transfer or equipment malfunction
Flow control	Regulate delivery and shutoff	Overfill, underfill or unstable operation
Quantity measurement	Establish usable delivered mass	Uncertain remaining mission capability
Contamination control	Preserve fluid and system cleanliness	Valve, feed-system or thruster degradation
Isolation and disconnect	Close the system and separate safely	Persistent leakage or failure to release

The interface can remove much of this complexity before launch. NASA’s Cooperative Service Valve replaces a conventional fill-and-drain valve with a robot-accessible design. Its documented features include three individually actuated seals, mechanical keying to prevent mixing of media and provisions for carrying robotic loads into the mounting structure. Cooperative Service Valve for In-orbit Cooperative Satellite Fueling — NASA Technology Transfer. NASA

This changes the economics of servicing. A prepared valve reduces the number of tools and operations needed at the client. Across a fleet, common interfaces can make repeated servicing less dependent on bespoke procedures. The commercial value arises from reducing operational complexity as well as enabling the initial connection.

Orbital logistics has a longer experimental history than recent announcements imply

Satellite propellant transfer did not originate with the latest geosynchronous experiments. NASA’s Jet Propulsion Laboratory records that the 2007 Orbital Express mission demonstrated rendezvous, propellant transfer and replacement of battery and computer modules. Its planning system also had to account for thermal, power, sensor-pointing and collision constraints. Orbital Express — NASA Jet Propulsion Laboratory.

China’s space agency separately reported that the Tianyuan-1 experimental payload completed nine on-orbit tests in 2016, including microgravity fluid management and replenishment-related measurements. The announcement described data from three tank-filling processes. This establishes a Chinese experimental fluid-management lineage; it does not by itself establish a freely manoeuvring commercial servicing service. 我国首次卫星在轨加注试验取得圆满成功 — China National Space Administration — July 2016.

The frontier is therefore moving from whether individual servicing functions can work toward whether they can be delivered reliably, repeatedly and economically across useful client populations.

Propellant efficiency and response time pull design in different directions

Electric propulsion can achieve high exhaust velocities and conserve propellant, but its performance is constrained by available electrical power and thrust. ESA consequently describes it as well suited to low-thrust, long-duration applications and stresses mission-level trade-offs between thrust, power and other characteristics. What is Electric Propulsion? — ESA.

The rocket equation illustrates the mass advantage. For an ideal manoeuvre:

Propellant fraction = 1 − exp[−Δv/(g₀ × Isp)]

The table uses standard gravity g₀ = 9.80665 m/s² and three illustrative specific impulses. The 220-second and 310-second examples correspond to values used in NASA’s orbital primer; 1,500 seconds is an explicitly assumed electric-propulsion comparison case.

Required ideal Δv	Propellant fraction at Isp = 220 s	At Isp = 310 s	At assumed Isp = 1,500 s
100 m/s	4.53%	3.24%	0.68%
500 m/s	20.69%	15.17%	3.34%
1,000 m/s	37.09%	28.03%	6.57%

Calculated fractions of initial mass consumed as propellant. They exclude tanks, power systems, thruster mass, reserves, operational losses and finite-burn effects. Equation and chemical-propulsion reference values: GDC Orbit Primer — NASA, slide 21.

The mass savings do not establish rapid response. Under a deliberately simplified constant-mass calculation, the time required to deliver a velocity increment is:

Time = spacecraft mass × Δv / thrust

For an assumed 100-kilogram vehicle delivering 100 m/s:

Assumed continuous thrust	Ideal thrusting duration
0.01 N	11.57 days
0.1 N	27.78 hours
1 N	2.78 hours
10 N	16.67 minutes

Illustrative impulse-delivery calculation. It is not an orbital-transfer solution and excludes changing mass, eclipse restrictions, attitude interruptions and trajectory constraints.

A mission requiring economical repositioning over weeks and one requiring a prompt manoeuvre may therefore favour different propulsion choices. Hybrid architectures can be attractive because they separate efficient transport from higher-authority manoeuvres, but they add integration, mass and qualification burdens.

The service architecture determines how many clients one vehicle can support

Attached life extension, module installation and fluid transfer have different consequences for fleet capacity.

Architecture	What remains with the client	Servicer occupancy	Principal scaling constraint
Attached propulsion support	The servicing vehicle	Potentially much of the service interval	Number of available servicers
Installed propulsion module	A dedicated module	Servicer can depart after installation and verification	Module inventory, installation rate and compatible clients
Propellant replenishment	Transferred propellant	Servicer departs after transfer and checks	Commodity inventory, interfaces and replenishment logistics
Component replacement	New or refurbished hardware	Task-dependent	Standardised interfaces, spare parts and verification
Inspection-only visit	No installed hardware	Observation interval	Access geometry, sensing quality and manoeuvre budget

A system that leaves a propulsion module with the client can potentially support more assignments than one that remains attached for years. It must, however, transport or access replacement modules and verify their installation. A refuelling vehicle can also depart, but only after completing a more demanding fluid-transfer process.

These architectures should consequently be compared through completed useful assignments, time occupied per client and resource consumption per assignment—not solely through the number of robotic arms or the amount of onboard propellant.

Key judgments

Servicing scalability begins with the client interface. Fleet-wide preparation can reduce recurring operational complexity more effectively than designing an increasingly dexterous robot to accommodate every legacy configuration.

Orbital logistics must be assessed as a chain of compatible spacecraft, commodities, tools, replenishment opportunities and verified outcomes. A successful transfer is an important milestone; a sustainable service requires repeated delivery.

What would change the assessment: repeated servicing across multiple clients, disclosed delivered quantities or installed-module performance, and evidence that the servicing vehicle remains available for subsequent assignments.

Open official record: comparable service throughput, intervention duration, customer-specific compatibility and complete operating costs remain insufficiently disclosed to calculate a defensible international cost per completed servicing mission.

Chapter 3 — American, Chinese and European systems: comparative performance and maturity

The strongest comparison now concerns how each industrial and institutional system converts enabling technologies into completed missions. American programmes offer a substantial record of delivered servicing and a newly launched robotic platform. China’s disclosed evidence points toward increasingly capable orbital sustainment, while retaining important uncertainty about interfaces and repeatability. Europe’s latest results show progress in integrated ground demonstrations and flight preparation, with clear differences between those milestones and an available servicing service.

The American transition from attached support to robotic intervention

The major new American development is the launch of the Mission Robotic Vehicle carrying DARPA’s Robotic Servicing of Geosynchronous Satellites payload on 21 July 2026. DARPA’s launch record describes an approximately year-long journey to GEO. The correct status at the assessment cut-off is therefore launched and transferring toward the operating region; it should not be presented as a completed sequence of robotic servicing assignments. Robotic Servicing of Geosynchronous Satellites lifts off — DARPA — July 2026.

DARPA describes two manipulator arms, each with seven joints, interchangeable tools, cameras and lighting. Intended tasks include installation of Mission Extension Pods designed to provide six or more years of additional client operation. That duration remains a programme performance objective rather than an accumulated flight result for the newly launched vehicle. Robotic Servicing of Geosynchronous Satellites lifts off — DARPA — July 2026.

NASA’s separate account confirms the launch and identifies its contributions in dynamic simulation, software performance analysis and flight robot operations. This is significant because the mission combines commercially operated hardware with government-developed robotics and specialist operational expertise. Robotic Servicing Mission Launches with NASA Support — NASA — July 2026, updated September 2026. DARPA

American capability layer	Established contribution	Remaining verification boundary
Operational inspection	Characterisation of resident space objects	Public records do not disclose a complete target-access envelope
Attached commercial life extension	Sustained propulsion support to a client	Does not demonstrate every form of repair or replenishment
MRV robotic architecture	Launched spacecraft carrying dual-arm servicing hardware	GEO arrival, checkout and completed interventions remain separate milestones
Mission Extension Pods	Intended distributed propulsion support	Installed performance and repeated deployment must be established
Civil-government support	Simulation, software analysis and specialist robot operators	Supporting expertise is distinct from service availability

American development also provides evidence against technological inevitability. NASA’s OSAM-1 programme was cancelled after reviews identified technical, cost and schedule difficulties, substantial remaining integration work and a lack of a transition partner. NASA’s mission page retains older descriptive material, but its explicit cancellation announcement governs the status assessment. On-orbit Servicing, Assembly, and Manufacturing 1 — NASA, announcement from NASA Headquarters.

The lesson is substantive. A technically ambitious legacy-refuelling mission can fail to reach deployment even within a mature national ecosystem. Commercial transition, client demand and an executable operations model are part of capability development.

China’s progress must be assessed through mission outcomes rather than labels

China’s orbital-logistics position contains several different evidentiary levels. The Tianyuan experimental record establishes fluid-management development. Shijian-25’s official launch announcement establishes its declared replenishment and life-extension purpose. US Space Command’s 2026 posture statement adds an assessment of likely docking and refuelling success involving Shijian-21.

Those records support a more developed logistics picture than a launch announcement alone. They still do not provide a common set of engineering measurements with which to compare the Chinese system against American or European servicing vehicles. China launches test satellite for orbital refueling — Government of China — January 2025 and 2026 Posture Statement — US Space Command, pp. 5–6.

Chinese assessment question	What the examined record supports	What it does not establish
Is replenishment a declared mission?	Yes, in the official Shijian-25 announcement	Full interface design or transfer architecture
Is there experimental fluid-management heritage?	Yes, in the CNSA Tianyuan announcement	A commercial multi-client service
Was Shijian-21’s life extended?	US Space Command assesses this as likely	Disclosed transferred mass or independently measurable lifetime extension
Is repeated servicing established?	Not by the cited records	Routine throughput or fleet-wide compatibility
Are manoeuvre and logistics strategically relevant?	Yes, through their effect on endurance and repeat assignments	A disclosed universal advantage over every comparator

The distinction between likely successful replenishment and routine logistical support is the central boundary. A single recipient may be highly compatible with a particular servicer. A broader operational architecture would require repeated assignments, resource replenishment and reliable support across a larger client population.

Public opacity does not establish technical inferiority. It does prevent confident numerical comparisons of manoeuvre endurance, transfer rate, operating cost or service reliability.

Europe’s most useful new evidence is integrated qualification

The February 2026 EROSS-IOD result provides more decision-relevant evidence than generic claims about European robotics. GMV reports that four technology elements reached TRL 6: ERGO autonomy, the ESROCOS robotic-control environment, ROB_DFF data fusion and model-based visual tracking.

The same report describes a July 2025 vision-system demonstration using life-sized models and representative materials during the final ten metres of approach, followed by a December robotic demonstration involving prepared and unprepared satellite models and orbital-replaceable-unit assembly. These were integrated ground demonstrations at DLR, rather than completed orbital capture and assembly. With the EROSS-IOD project, GMV achieves TRL 6 for key space robotics technologies — GMV — February 2026. GMV

EROSS-IOD element	Reported function	Reported maturity/result	Correct interpretation
ERGO	Supervisory autonomy	TRL 6; orchestration of autonomous capture in the demonstration	Integrated technology validation
ESROCOS	Robotic-control software environment	TRL 6	Supporting execution platform
ROB_DFF	Sensor-data fusion	TRL 6	Navigation and control information integration
Model-Based Tracking	Autonomous computer vision	TRL 6	Target-relative perception capability
Servicer Vision System	Approach-phase perception	Ground demonstration over the final 10 m	Representative test result, not an orbital approach
CAESAR integration	Capture and unit manipulation	Demonstrated with representative satellite hardware	Important system integration evidence

The implication is that Europe’s gap cannot be described simply as a lack of algorithms or robotic components. The more immediate challenge is the transition from qualified subsystems and integrated test facilities to available flight services.

RISE’s schedule and design maturity require an updated baseline

ESA’s September 2025 RISE publications state a planned launch in 2029, superseding the 2028 date in its October 2024 announcement and in the earlier overview. The same update records successful completion of the System Requirements Review on 11 July 2025. That review validates the requirements baseline and readiness to enter the next development phase; it does not constitute final qualification or orbital acceptance. Europe advances in-orbit servicing: RISE mission passes milestone review — ESA — September 2025.

The revised date changes the timing comparison with the American robotic vehicle already launched in July 2026. It does not justify a simplistic claim that the American service is fully available while the European mission is absent: MRV’s transfer and checkout must also be completed before its intended robotic services can be demonstrated.

Programme milestone	What it establishes	What it leaves open
Requirements review	Mission requirements and design direction are sufficiently defined for progression	Detailed design closure and qualification
Representative subsystem demonstration	Performance under specified test conditions	Full flight-environment behaviour
Integrated spacecraft testing	Compatibility of major hardware and software elements	Actual orbital commissioning and client interaction
Launch	Successful departure and deployment, as documented	Arrival, checkout and service performance
Completed orbital intervention	Achievement of a defined mission task	Repeatability and long-term availability
Repeated customer service	Evidence of operational delivery across assignments	Fleet-scale economics and sustained capacity

Italy’s industrial opportunity lies in moving RISE through those gates while retaining operating knowledge and a credible customer service model. Germany’s robotics infrastructure and the wider European software contribution can support that transition, but neither should be counted as a substitute for flight acceptance.

British operating heritage and Japanese achievements must be attributed correctly

Astroscale illustrates why national comparisons require care. The group operates across jurisdictions; expertise acquired within the corporate group does not automatically become a sovereign capability of every country hosting one of its subsidiaries.

ELSA-d nevertheless provides important evidence of operating experience. In its January 2024 mission conclusion, Astroscale reported navigation from approximately 1,600 kilometres to within 160 metres using absolute-navigation methods, transition to relative navigation and more than two years of operations. It also disclosed the loss of four of eight thrusters and the decision not to continue an autonomous capture attempt after anomalous conditions were detected. Astroscale’s ELSA-d Finalizes De-Orbit Operations Marking Successful Mission Conclusion — Astroscale — January 2024.

That record is valuable precisely because it includes limitations. It demonstrates operations, transitions between navigation modes and recovery under degraded conditions without supporting a claim that every intended autonomous capture objective was completed.

ADRAS-J offers a separate external benchmark. Astroscale Japan’s March 2026 completion report describes approach and inspection of an actual unprepared rocket stage approximately 11 metres long, four metres wide and three tonnes in mass, including an approach within 15 metres and validation of autonomous collision avoidance. Capture and removal are assigned to the subsequent mission. These achievements belong to the Japanese programme and should not be relabelled as completed European debris removal. Astroscale’s ADRAS-J Mission Completes Operations, Begins Deorbit — Astroscale Japan — March 2026.

Benchmark	Target preparation	Established mission result	Boundary
ELSA-d	Purpose-built client	Capture-system demonstration, rendezvous and navigation transitions	Not every planned autonomous capture completed
ADRAS-J	Actual unprepared rocket stage	Inspection, close approach and collision-avoidance validation	No completed debris capture/removal in this mission
EROSS-IOD	Representative ground hardware	Integrated autonomous capture and manipulation demonstrations	Ground qualification
MRV/RSGS	Intended GEO servicing clients	Launch of integrated robotic vehicle	Servicing demonstrations follow transfer and checkout
RISE	Intended legacy GEO client	Requirements review and continuing development	Planned launch and later orbital demonstration
Shijian-25	Interface details not established in the cited record	Likely servicing success assessed by US Space Command	Transfer quantity and repeated service remain undisclosed

France’s contribution must be judged by mission acceptance

France’s military programme architecture addresses a different customer requirement from commercial life extension. The relevant question is whether a system can support national observation, decision-making and authorised action in the required orbital environment.

The May 2026 parliamentary record identifies Yoda, Paladin and Toutatis within the incremental Egide approach. It supplies programme intent, but does not establish an operational acceptance date or a common set of flight-performance measurements. For comparison purposes, France’s military patrol development must therefore remain separate from ESA cooperative formation achievements, EROSS ground robotics and commercial servicing objectives. Commission des affaires étrangères, de la défense et des forces armées: proceedings for the week of 4 May 2026 — French Senate.

The meaningful acceptance evidence would include the responsible operating organisation, completed mission tasks, available spacecraft, supported orbital regions and sustained readiness. Without those elements, assigning a numerical readiness score would add precision without adding knowledge.

The comparative verdict must follow the mission

The evidence supports different judgments for different tasks.

Assessment dimension	United States	China	Europe
Inspection	Operational military mission record	Manoeuvring and close-approach capability identified in official US assessments	National programmes and enabling technologies with differing maturity
Attached life extension	Demonstrated commercial delivery	No directly equivalent commercial service established by the cited record	RISE in development
Robotic intervention	MRV launched; orbital servicing sequence still to be demonstrated	Detailed comparable specifications remain limited in the examined record	Integrated ground validation and flight hardware development
Propellant replenishment	Historical experimental demonstrations; legacy-refuelling programme also encountered cancellation	Likely GEO replenishment success assessed by US Space Command	Component and mission development; no equivalent completed service established here
Target preparation	Varies by programme	Insufficient disclosure for some comparisons	Clear distinction between cooperative formation, prepared interfaces and legacy clients
Repeatability	Successive commercial life-extension assignments documented	Multi-assignment servicing not established in the cited records	Sustained commercial servicing remains to be demonstrated
Numerical ranking	Unsupported across all mission types	Unsupported across all mission types	Unsupported across all mission types

Assessment based on the mission records cited throughout this chapter. “Not established” describes the evidentiary boundary, rather than proving that a capability does not exist.

The United States’ strongest disclosed advantage is the breadth of completed and progressing mission architectures. China’s most consequential development is the prospect of replenishable mobility, whose magnitude cannot yet be quantified from the available record. Europe’s most credible route is to convert integrated technical competence into repeatable flight operations, with explicit recognition of national ownership, programme maturity and service responsibility.

Key judgments

Mission maturity must be measured through completed operational gates. Ground validation, launch, orbital checkout, first intervention and repeated customer service are different achievements.

The latest evidence narrows some technological gaps while making delivery gaps more visible. European robotics and autonomy results are substantive; the next decisive step is integrated flight performance. American deployment is advancing, but newly launched systems still require mission validation. Chinese sustainment progress warrants close attention without treating undisclosed engineering characteristics as known quantities.

What would change the assessment: MRV’s completed GEO commissioning and first verified robotic assignments; repeated Chinese servicing outcomes; RISE’s progression through qualification and launch; and European military mission acceptance supported by disclosed operational results.

Open official record: the central unresolved comparisons concern useful service throughput, reliability across multiple clients, remaining manoeuvre capacity, degraded-mode performance and full mission cost. Until those variables are documented on compatible terms, the defensible comparison remains multidimensional.

---

Pillar II — Industrial capacity and European sovereignty

Chapter 4 — Production, launch, ground infrastructure and service economics

Industrial strength in orbital services depends on the ability to manufacture, deploy, operate and finance a continuing service. A technically successful spacecraft can remain commercially isolated if its manufacturer cannot secure repeat orders, its launch arrangements introduce excessive delay or its operator lacks the infrastructure to support simultaneous assignments. The relevant unit of analysis is therefore the complete delivery system.

Production capacity must be measured at the acceptance gate

Satellite manufacturing announcements commonly describe buildings, assembly positions or intended annual capacity. These are useful indicators of investment, but they do not establish how many flight-ready spacecraft a production system can deliver consistently.

The decisive industrial measures are accepted output, production lead time, first-pass test performance, supplier delivery reliability and the time needed to incorporate corrective changes. Increasing assembly speed produces little benefit if environmental testing, propulsion acceptance or flight-software verification becomes the controlling bottleneck.

ICEYE’s July 2026 announcement provides a concrete European manufacturing reference. The company reported a production rate of 50 satellites annually, with a target of 100 annually by 2027 and beyond, supported by matching launch activity. This is a manufacturer’s statement of current rate and future ambition; it is not an independently audited annual delivery series. ICEYE launches four new satellites aboard Transporter-17 — ICEYE — July 2026.

On an evenly distributed calendar basis, those rates correspond to one spacecraft every 7.3 days and 3.65 days, respectively. These calculated intervals describe equivalent factory output, not the assembly duration of an individual satellite: multiple spacecraft can move through production and testing concurrently.

Industrial measure	What it establishes	Evidence needed to assess sustained capacity
Installed assembly capacity	Physical ability to accommodate work	Staffing, equipment availability and supplier readiness
Annualised production rate	Claimed or demonstrated output pace	Definition of completion and underlying reporting period
Accepted spacecraft output	Units passing the specified acceptance process	Signed acceptance records and unresolved deviations
First-pass test performance	Manufacturing consistency	Rework frequency and repeat-test burden
Order backlog	Contracted demand	Cancellation provisions, delivery dates and customer concentration
Inventory of qualified components	Protection against selected supply interruptions	Shelf life, configuration compatibility and replenishment arrangements
Delivered operational capacity	Output that has become usable in orbit	Launch, commissioning and customer acceptance
Replacement lead time	Ability to restore lost capacity	Reserved components, manufacturing slots, launch access and trained operators

The industrial distinction is especially important for servicing vehicles. An imaging satellite produced repeatedly around a stable architecture and a robotic servicer carrying specialised interfaces have different manufacturing and qualification requirements. Output rates from one category cannot be transferred mechanically to the other.

For orbital servicing, the more useful production objective is a repeatable family of vehicles sharing qualified avionics, propulsion, operations software and interface modules. Commonality can reduce recurring engineering work. Excessive customisation for each customer can erase that advantage even when the underlying platform remains nominally unchanged.

Launch demand can support industrial scale while creating customer concentration

A credible launch industry needs a sufficiently predictable flow of missions to maintain suppliers, production personnel and launch-site operations. Institutional demand can provide continuity, while commercial constellations can supply additional volume. The difficulty is ensuring that a large order book translates into delivered missions without making the industrial system excessively dependent on a small number of customers.

Arianespace’s September 2026 commercial update records six additional Ariane 64 launches for Amazon Leo, increasing the agreement from 18 to 24 launches by 2031. It also records two Ariane 64 launches for Eutelsat’s OneWeb renewal, scheduled for 2027 and 2028. The same statement distinguishes these launch orders from memoranda signed with ICEYE, EnduroSat and AgenaSpace. Ariane 6 builds on commercial success at the International Space Summit with its largest order intake since entering service — Arianespace — September 2026.

That distinction matters economically. A launch order contributes a different level of demand visibility from an agreement to explore future cooperation. Neither should be counted as realised revenue before the applicable contractual and accounting conditions are met.

Launch-market development	Documentary status	Industrial significance	Remaining exposure
Amazon Leo expansion to 24 Ariane 64 launches	Announced launch order	Extends demand visibility for production and operations	Delivery concentration and schedule execution
Two additional OneWeb renewal launches	Announced launch orders for 2027–2028	Adds European constellation demand	Customer and spacecraft readiness
Cooperation with ICEYE, EnduroSat and AgenaSpace	Memoranda of understanding	Opens potential future demand channels	Conversion into binding orders
European Launcher Challenge contracts	Milestone-linked programme commitments	Supports additional launch suppliers	Technical qualification and financial execution

Commercial demand and strategic autonomy can reinforce one another, but their incentives are not identical. A high-volume commercial customer may value schedule and price differently from a government requiring a specific orbital deployment window. European procurement should therefore define which missions need reserved access, which can use scheduled commercial capacity and which justify paying for an alternative launch route.

Europe is funding additional launch supply, not merely additional designs

ESA’s 27 August 2026 European Launcher Challenge announcement records contracts of €186.9 million for Rocket Factory Augsburg, €158.9 million for PLD Space and €197.8 million for Isar Aerospace. Their combined announced value is €543.6 million, calculated from those three contracts. ESA states that funding is unlocked as milestones are met and that providers must achieve an orbital launch before 2028. First contracts kick off European Launcher Challenge — ESA — August 2026.

Provider	Announced contract	Deployment arrangement described by ESA	Status boundary
Rocket Factory Augsburg	€186.9 million	German vehicle; launch from SaxaVord, United Kingdom	Contract does not establish routine launch availability
PLD Space	€158.9 million	Spanish vehicle; launch from French Guiana	Development and demonstration remain consequential
Isar Aerospace	€197.8 million	German vehicle; launch from Andøya, Norway	Qualification and subsequent service reliability remain separate
Three-contract total	€543.6 million	Cross-border European supply architecture	Announced values, not certified expenditure

The funding structure addresses a central industrial problem: additional providers require capital before they can establish reliable revenue. Milestone-linked support can reduce that financing gap while retaining a relationship between payment and delivery.

However, several European companies do not automatically create several fully independent launch chains. Providers may still share suppliers, testing infrastructure, financing sources or regulatory dependencies. Diversity should be assessed through the underlying production and operating arrangements, rather than corporate names alone.

China provides a different indicator of launch-system scale. In April 2026, CNSA reported that China conducted 92 space launch missions during 2025, a 35% increase from 2024. This national mission count demonstrates industrial activity; it does not measure launch capacity commercially available to European customers or the availability of particular orbital services. China to carry out intensive space missions in 2026: CNSA — Government of China — April 2026.

The comparison illustrates why national launch totals and mission-access guarantees must remain separate. A country can possess substantial aggregate launch activity while access to a specific orbit, payload class or priority window remains constrained.

Ground infrastructure can become the limiting production resource

A spacecraft entering service creates continuing demand for tracking, communications, mission planning, software maintenance and anomaly response. Increasing the fleet without expanding those functions can reduce the operational value of each additional spacecraft.

ESA’s invitation to expand Estrack states that projected annual demand will exceed existing capacity over the coming years, potentially causing mission data loss. Its response is to integrate additional European institutional and commercial stations into an augmented network. This is direct evidence that ground capacity is a strategic resource rather than an administrative support function. Expanding Estrack: Opportunities for European Ground Stations — ESA Commercialisation Gateway.

For servicing operators, antenna access is only part of the requirement. A useful operating system must also support flight-dynamics analysis, customer coordination, mission authorisation, configuration management and recovery from unexpected behaviour. Some functions can be shared across missions; others require dedicated teams during sensitive operations.

Ground-service layer	Resource that can constrain growth	Procurement measure
Telemetry, tracking and command	Antenna time and compatible equipment	Guaranteed access windows and tested alternatives
Mission planning	Qualified personnel and validated planning tools	Planning turnaround and independent checking capacity
Flight dynamics	Timely observations and specialist analysis	Orbit-update performance and manoeuvre reconstruction
Mission control	Trained operators and resilient facilities	Staffing coverage, recovery exercises and backup-site readiness
Software maintenance	Access to source code, build systems and expertise	Reproducible releases and verified rollback procedures
Customer integration	Compatible interfaces and clear responsibilities	Time from contract signature to operational integration
Security management	Trusted identities, keys and controlled access	Tested authority transfer and continuity procedures

Analytical procurement framework. The table assigns no unsupported numerical performance thresholds.

Antenna ownership alone does not establish operational independence. A European operator may depend on an external software supplier, foreign-hosted processing or an unavailable specialist team. Conversely, commercial infrastructure can contribute to sovereignty when access rights, security controls and continuity arrangements are sufficiently robust.

The appropriate objective is reliable control over the service chain, including the ability to continue operating when an individual supplier becomes unavailable.

American procurement is creating identifiable service demand

The American market offers useful evidence of government demand moving beyond exploratory studies. Starfish Space announced a $54.5 million Space Systems Command contract in February 2026 for a second Otter vehicle, with delivery scheduled for 2028. The company identifies the APFIT programme as the funding route. Starfish Space Awarded $54.5 Million Space Force Contract for Dedicated Otter Satellite Servicing Vehicle — Starfish Space — February 2026.

A separate January announcement records a $52.5 million Space Development Agency contract covering construction, launch and operation of an Otter for end-of-life disposal. It describes an initial disposal with options for additional assignments and a target launch in 2027. Starfish Space Awarded First Ever End-of-Life Disposal Contract for a LEO Constellation — Starfish Space — January 2026. Starfish Space

Award	Announced value	Purchased scope	Commercial interpretation
SSC second Otter vehicle	$54.5 million	Dedicated vehicle; planned 2028 delivery	Demand for additional operational capacity
SDA disposal mission	$52.5 million	Build, launch and operate; initial disposal plus options	Demand for an outcome delivered as a service

These values should not be converted into an international “price per servicing satellite.” Their scopes, delivery conditions and optional work differ. Their significance is the emergence of identifiable customers purchasing defined capacity or outcomes.

For a developing industry, such contracts can be more consequential than a larger research grant without a subsequent buyer. They help suppliers make decisions about staffing, production commitments and financing. They also expose the purchaser to execution risk, which must remain visible until delivery and acceptance.

Service economics depend on utilisation and the customer’s remaining asset value

A servicing business has two economic tests. The customer must obtain sufficient value from the intervention, and the supplier must recover the cost of maintaining the capability.

For the customer, the relevant comparison includes the remaining useful value of the existing payload, the cost and timing of replacement, transition costs, expected service interruption and the consequences of intervention failure. Extending an old spacecraft is not automatically preferable to replacing it. Replacement may provide better performance, lower operating cost or a more suitable architecture.

For the supplier, the critical question is how many useful assignments can be completed before the servicing system requires replacement or replenishment.

A simplified accounting relationship is:

Average cost per completed assignment = allocated fixed costs per assignment + variable mission costs + allocated contingency costs.

This is an analytical identity, not a numerical model. Its practical value is to identify what contracts must disclose or control.

Economic variable	Why it matters	Information required
Development expenditure	Determines the investment that must be recovered or publicly absorbed	Separation of non-recurring development from recurring service cost
Launch and commissioning	Establishes the cost of placing usable capacity in orbit	Full deployment scope and acceptance conditions
Customer integration	Can require substantial engineering before intervention	Interface documentation and qualification responsibility
Vehicle utilisation	Determines fixed-cost recovery	Availability, transit time and occupancy per assignment
Consumable use	Constrains later assignments	Mission-level resource accounting
Operating expenditure	Continues between customer tasks	Staffing, infrastructure, software and security costs
Failure exposure	Can affect both servicer and client value	Contractual allocation and available financial protection
Residual vehicle value	Influences later pricing and reinvestment	Remaining capability after each assignment

The resulting market may support several business models. A government can purchase a dedicated vehicle, reserve access to a shared capability or buy a specific outcome. Each allocates risk differently.

Procurement model	Public purchaser gains	Principal burden	Main contractual safeguard
Dedicated spacecraft purchase	Greater control over assignment priorities	Capital and operational responsibility	Acceptance criteria, documentation and sustainment rights
Reserved service capacity	Access without owning the complete system	Dependence on provider availability	Enforceable priority and substitution provisions
Payment for completed intervention	Stronger link between payment and outcome	Potentially higher supplier risk premium	Precise completion and verification rules
Development co-funding	Influence over emerging technology	No automatic guarantee of future service	Defined transition plan and follow-on procurement route
Multi-year service agreement	Demand stability and operational continuity	Long-term supplier dependence	Performance remedies, portability and exit arrangements

An effective industrial policy should select the model according to the public requirement. Buying hardware to preserve national engineering knowledge serves a different purpose from purchasing timely imagery or the removal of a failed satellite. Combining those objectives without specifying their relative importance makes cost and performance difficult to evaluate.

Key judgments

The most important industrial indicator is accepted operational capacity delivered over time. Factory investment, annualised production claims and launch orders provide evidence of progress, but each leaves different execution risks unresolved.

Europe’s challenge is to connect manufacturing growth with launch availability, ground capacity and recurring customer demand. Public procurement can support that connection when it purchases explicit outcomes and preserves the knowledge needed to sustain or replace suppliers.

What would change the assessment: documented production acceptance rates, repeated service delivery, reserved launch arrangements, demonstrated ground-network continuity and evidence that follow-on demand supports recurring production.

Open official record: comparable utilisation, recurring operating cost, customer-specific integration expenditure and profitably completed servicing assignments remain insufficiently disclosed for a defensible international service-cost ranking.

Chapter 5 — Italy, France, Germany, the United Kingdom and the European institutional architecture

European sovereignty depends on the allocation of decision rights across national governments, European institutions and private operators. Manufacturing location matters, but so do authority over tasking, access to engineering knowledge, rights to modify software, control of operational data and the ability to sustain the service when commercial circumstances change.

Financial scale must be compared without adding incompatible commitments

Europe’s public commitments demonstrate substantial political demand, but they belong to different accounting categories.

ESA’s final CM25 announcement records €22.3 billion in subscriptions, updated on 2 December 2025. ESA describes the increase over the 2022 ministerial as 31% in nominal terms and 17% after inflation adjustment. These are programme subscriptions, not a single annual budget or a dedicated orbital-servicing appropriation. ESA Member States commit to largest contributions at Ministerial — ESA — November 2025, updated December 2025.

Public commitment	Reported amount	Scope	Comparison boundary
ESA CM25	€22.3 billion	Ministerial programme subscriptions	Not annual expenditure
France	More than €16 billion through 2030	Civil and dual-use space trajectory	Excludes purely military activity in the cited statement
Germany	More than €35 billion over the coming years	Announced space-security architecture investment	Commitment trajectory, not completed expenditure
United Kingdom	£7.8 billion through 2030	Government space strategy investment framework	Different currency, programme coverage and accounting basis

Sources: French Council of Ministers communication — Élysée — December 2025; Weltraumsicherheit: Kanzler Merz bei BST — German Federal Government — December 2025; New space strategy will bolster UK defences against threats from space — UK Government — September 2026.

These amounts cannot be added to produce a clean European total. National spending can include contributions to European programmes, while the time horizons and civil–military boundaries differ. Their decision value lies in identifying demand, priorities and implementation obligations.

Italy: connect public investment to recurring industrial output

Italy’s national in-orbit-servicing procurement offers unusually detailed evidence of how development risk is allocated. ASI’s March 2023 award decree specifies an industrial contract of €234,807,921.23, divided between fixed-price and cost-reimbursement work.

ASI national IOS award component	Amount	Calculated share of industrial contract
Fixed-price component	€143,206,209.38	60.99%
Cost-reimbursement component	€91,601,711.85	39.01%
Industrial contract	€234,807,921.23	100%
Acceleration/programmatic contingency provision	€497,793.05	Outside the industrial contract subtotal
Technical-function incentive provision	€458,000.00	Outside the industrial contract subtotal
Overall initiative framework	€235,763,714.28	Includes the additional provisions

Shares calculated from the decree. Amounts are stated as VAT non-taxable in the record. These are award-framework figures, not a certification of expenditure. Decreto D.G. n. 334/2023 — ASI, pp. 6–7.

The split has an important industrial implication. Fixed-price work places more cost-control responsibility on the contractor, subject to the contract’s conditions. Reimbursable work retains greater expenditure exposure for the purchaser. The division therefore provides a more informative view of development-risk allocation than the rounded headline of €235 million.

ASI’s transparency record also identifies a 2026 non-onerous addendum to the same contract. That confirms continuing contractual administration; it does not, by itself, establish mission acceptance, launch or completion of the original performance objectives. Atto aggiuntivo n. 2023-15-I.1-2026 — ASI transparency record. asi.it

Italy’s production infrastructure adds another layer. ASI’s October 2025 Space Factory statement describes a network financed 49% by ASI through PNRR resources and 51% privately, with approximately 21,000 square metres in total, including 5,000 reconfigurable square metres. It identifies interconnected manufacturing, integration, solar-cell and testing facilities. These are infrastructure and financing measures, rather than an audited annual spacecraft output figure. Space Factory 4.0 al completo: inaugurata la Space Smart Factory di Thales Alenia Space a Roma — ASI — October 2025.

Italy’s policy task is to make those investments reinforce one another. A demonstration programme should generate reusable engineering knowledge, qualified suppliers and operating procedures. Production facilities should then support subsequent vehicles and other programmes without requiring the entire development effort to be repeated.

Italian industrial asset	Strategic opportunity	Evidence needed to establish durable value
National IOS procurement	Retain integrated mission-development competence	Acceptance results and follow-on use of the developed architecture
Distributed Space Factory infrastructure	Support recurring production and supplier development	Facility utilisation, accepted output and commercial order conversion
Launch-service capability	Link production to deployment	Reliable service delivery and sustainable demand
Ground operations	Retain mission knowledge and customer relationships	Operating contracts, trained teams and continuity arrangements
European programme participation	Access larger markets and shared qualification	Work packages carrying design responsibility and reusable intellectual property

Ground infrastructure is also receiving new investment. In February 2026, ASI and Telespazio announced RESPONSE, intended to modernise Fucino’s 27-metre FOC-1A antenna for near-Earth and deep-space communications, including future support to wider mission networks. The agreement establishes an upgrade programme, not completed availability of all intended services. Agenzia Spaziale Italiana e Telespazio insieme per potenziare le comunicazioni satellitari oltre l’orbita terrestre — ASI — February 2026.

The strategic return will be strongest where Italy retains operational responsibility and the capacity to adapt the system for future customers. Manufacturing participation without access to design changes or operational knowledge provides a narrower form of sovereignty.

France: reconcile European preference with delivery performance

France’s December 2025 policy communication explicitly links independent access to space, industrial competitiveness and European cooperation. It also advocates stronger European preference for institutional space capabilities. This is a French policy position; it should not be described as an already uniform European procurement rule. Compte rendu du Conseil des ministres du 2 décembre 2025 — Élysée.

The industrial rationale is clear. Predictable institutional purchasing can preserve engineering teams, supplier capacity and launch infrastructure that might otherwise face uneven demand. The corresponding risk is that preference becomes detached from delivery obligations.

A workable French approach would couple demand support with measurable acceptance, schedule transparency and the ability to introduce competing suppliers. European preference is more economically defensible when it purchases capabilities that can remain useful and competitive after the initial public order.

France also faces a coordination problem common to states with substantial established industrial capacity. Large programmes can sustain specialised suppliers, but emerging service companies need access to customers, test infrastructure and integration opportunities. Procurement should reward contributions that reduce operating cost or improve service delivery, rather than using consortium membership as the principal measure of inclusion.

The relevant sovereignty test is whether France and its partners can sustain the service chain under adverse conditions while continuing to improve it. Protecting an existing allocation of industrial work is not sufficient evidence of that outcome.

Germany: a service purchase can create capacity without transferring ownership

Germany’s SPOCK 1 programme provides a concrete example of purchasing controlled access rather than government ownership of every spacecraft. The December 2025 supplier announcement describes a contract of approximately €1.7 billion gross, running from the end of 2025 to the end of 2030, with extension options. The scope includes satellite operations, ground-station management and image evaluation; the constellation remains the joint venture’s property. ICEYE and Rheinmetall win major contract worth billions for space reconnaissance — ICEYE — December 2025.

A subsequent 6 October 2026 Rheinmetall announcement reports that the Bundeswehr has direct access to several dedicated SAR satellites and can task them independently. It also states that production has commenced in Neuss, with the objective of building and certifying several dozen satellites annually. The latter remains a capacity objective, rather than a completed annual output total. Major milestone achieved: Rheinmetall ICEYE Space Solutions provides the German Armed Forces with exclusive access to SAR satellites — Rheinmetall — October 2026. iceye.com

SPOCK 1 characteristic	Reported arrangement	Sovereignty implication
Asset ownership	Retained by the joint venture	Government access does not require direct ownership
Tasking	Independent tasking of dedicated satellites reported	Public user controls an important operational decision
Operations	Performed by the service provider	Continuity depends on the operating contract and provider capability
Ground segment	Included in the service scope	Security and availability must be assessed across the complete chain
Industrial production	Commenced in Neuss	Creates domestic integration, testing and quality-assurance activity
Expansion	Constellation growth and annual production objective	Future capacity still requires delivery and acceptance

The German model can strengthen demand visibility and industrial utilisation. It also makes contractual rights unusually important. Priority access, continuity during disputes, data retention, software dependence and termination arrangements determine how much practical control the purchaser retains.

Germany’s wider announced investment trajectory creates room for additional capacity, but procurement scale alone does not resolve those questions. The strongest industrial outcome would combine delivered service with domestic engineering competence and the ability to qualify alternatives.

United Kingdom: use procurement and regulation to make services financeable

The UK’s September 2026 Technical Delivery Annex specifies funding and delivery intentions that are more informative than the strategy headline alone. It identifies up to £77 million for a national active-debris-removal mission and places its planned launch in 2029, following design and readiness milestones. It also lists a £37 million Space Clusters Infrastructure Fund and £65 million for the National Space Innovation Programme over the stated spending-review framework. UK Space Strategy: Technical Delivery Annex — UK Government — September 2026.

UK instrument	Published amount or timing	Industrial function
National active-debris-removal mission	Up to £77 million	Government customer for an integrated mission
National mission launch	Planned 2029	Flight-demonstration objective
Space Clusters Infrastructure Fund	£37 million	Shared regional research and test infrastructure
National Space Innovation Programme	£65 million	Co-funded development with a target market

These entries should not be added indiscriminately to other announcements: programme totals, subprogrammes and spending periods can overlap.

The UK is also altering the financial environment for innovative missions. Its September policy package states that qualifying ISAM and lunar orbital-operation licences issued from 1 December 2026 will receive a £0 operator-liability limit, with the detailed measure covering planned launches before the end of 2030. The measure is prospective at this assessment’s cut-off. The package retains liability and insurance requirements for procuring the launch and schedules a policy review in 2029. Space regulatory financial tools package — UK Government — September 2026, “Measure 2”.

Economically, this can reduce a particular licensing-related burden on early missions. It does not eliminate technical risk, contractual exposure or the need to finance the spacecraft. Its value depends on whether companies can convert regulatory relief into insurable, investable and deliverable services.

The British opportunity is to combine mission operations, test infrastructure, commercial contracting and financial services. The implementation test is whether firms win recurring customer assignments and retain the personnel and knowledge required to deliver them.

ESA, the European Union and national governments hold different authorities

ESA has 23 member states, including the United Kingdom, Norway and Switzerland. Its membership is not identical to that of the European Union, and ESA is an independent intergovernmental organisation. That distinction determines programme participation and the routes through which countries can finance and influence activities. Member States & Cooperating States — ESA.

ESA’s industrial policy also links participation to contributions through geographical-return arrangements. Its published explanation describes return coefficients based on the relationship between contract shares and financial contributions, with technological weighting and programme-specific calculations. ESA, an intergovernmental customer — ESA.

The arrangement can sustain political support and distribute technical competence. It also requires industrial teams to account for national participation when allocating work. The analytical trade-off is between maintaining a broad industrial base and preserving clear technical responsibility.

Institutional layer	Principal role	What it does not automatically provide
National government or public customer	Defines national requirements and purchases capability	Authority over every European programme
ESA	Develops and implements subscribed programmes and technical activities	A single European military command
European Commission	Manages relevant EU programme and concession arrangements	Direct operation of every contributing asset
EUSPA	Performs assigned service, security and operational functions	Ownership of all pooled capacity
Industrial consortium	Designs, supplies or operates contracted systems	Unrestricted authority over government priorities
Satellite operator	Commands spacecraft within its responsibilities	Authority to redefine customer requirements

The practical weakness to avoid is a mission whose technical participants are identified but whose operational decision rights remain ambiguous. Each programme needs a clear answer to who prioritises users, approves changes, accepts performance, manages incidents and finances replacement.

Secure connectivity demonstrates how the European model is evolving

IRIS² provides an important institutional example even though it is a connectivity programme rather than a servicing fleet. ESA’s August 2026 update records an addition of 66 LEO satellites, bringing the main constellation to 348, and identifies progressive service deployment from 2029. The negotiations defining the revised governance, technical configuration and financing concluded on 6 August 2026. IRIS² reinforced and accelerated as implementation advances — ESA — August 2026.

The 66-satellite addition represents a calculated 23.4% increase over the preceding 282-satellite main-constellation figure. It does not establish an equal percentage increase in delivered capacity, because capacity depends on the architecture and payload allocation.

The original December 2024 concession announcement stated a €10.6 billion twelve-year cost framework, including €6 billion from the EU, €550 million from ESA and more than €4 billion from the private sector. Those are the original agreement’s financing figures; they should not be treated as a fully reconciled final cost of the subsequently revised architecture without an updated financial record. ESA to support the development of EU’s secure communication satellites system — ESA — December 2024.

IRIS² record	Verified figure or arrangement	Interpretation
Original concession	12 years; €10.6 billion framework	Historical contractual baseline
August 2026 architecture	348 satellites in the main constellation	Revised programme configuration
Additional LEO spacecraft	66	Architecture expansion
Progressive services	From 2029	Deployment objective
ESA role	Development, qualification and in-orbit validation oversight	Technical implementation responsibility
Industrial delivery	SpaceRISE and participating suppliers	Contracted space and ground infrastructure

The institutional lesson is that sovereignty is being organised through a long-term public–private service arrangement. Its success will depend on enforceable requirements, technical acceptance and control of government services, as well as the nationality of the participating companies.

Pooling existing capacity can produce benefits before a new constellation is complete

GOVSATCOM offers a nearer-term example. The European Commission’s June 2026 account states that services have operated since January 2026, pooling participating states’ satellite capacity for authorised public users. It describes an interim EUSPA-operated hub and its progressive replacement by permanent sites in Athens and Cologne. EU GOVSATCOM Hub Site in Cologne to further strengthen Europe’s Secure Satellite Communications — European Commission — June 2026. defence-industry-space.ec.europa.eu

Pooling can improve access for countries without equivalent national assets. Its effectiveness depends on allocation rules and the availability of contributed capacity during periods of simultaneous demand.

That is relevant to future orbital services. Europe could share inspection, servicing or disposal capacity without requiring every state to own a complete fleet. Such an arrangement would need explicit customer priorities, security conditions, operational responsibility and financial commitments. It would remain a proposed procurement architecture until those arrangements were agreed.

The decisive procurement question is which rights Europe retains

A European-built spacecraft can still leave its customer dependent on a single supplier. Conversely, a shared commercial service can provide substantial public control when its contractual and technical arrangements are designed accordingly.

Control requirement	Evidence a purchaser should obtain	Failure consequence
Tasking priority	Enforceable allocation and emergency-priority provisions	Capacity unavailable when most needed
Operational knowledge	Documentation, training and validated procedures	Inability to sustain or transfer operations
Software continuity	Appropriate maintenance, modification and recovery rights	Dependence on unavailable vendor support
Data control	Defined access, storage, retention and release rules	Loss of usable information or restricted exploitation
Supplier substitution	Qualified interfaces and transition arrangements	Long interruption after supplier failure
Replacement capacity	Manufacturing and launch provisions	Slow recovery from spacecraft loss
Acceptance authority	Named public or delegated technical responsibility	Payment without a clear performance determination
Lifecycle financing	Defined operations, refresh and disposal obligations	Capability erodes after development funding ends

These requirements should be applied proportionately. Full public ownership is justified for some missions; service purchasing is appropriate for others. The common requirement is that the public authority understands which dependencies it accepts and how it will manage them.

Key judgments

Italy’s opportunity is to turn funded development and manufacturing infrastructure into recurring missions with retained operating knowledge. France’s challenge is to connect institutional demand support with measurable delivery and industrial renewal. Germany’s service-purchasing model can accelerate capacity, provided contractual control remains strong. The UK’s combination of mission procurement and prospective financial relief can support commercialisation if it generates repeated assignments.

At European level, the most consequential task is to establish clear authority across funding, technical acceptance and service operation. ESA participation, EU programme access, national security authority and corporate ownership remain distinct.

What would change the assessment: recurring service contracts, accepted production output, tested supplier-transition arrangements, operational ground redundancy and published evidence that European demand supports financially sustainable delivery.

Open official record: implementation requires continued scrutiny of national contract amendments, actual payments, service acceptance, revised programme financing and the allocation of operational rights. Spending commitments establish intent; sovereignty emerges from the capabilities and decision rights delivered through them.

---

Pillar III — Protection, escalation and strategic choice

Chapter 6 — Satellite vulnerability, attribution and operational resilience

The decisive protection requirement is the survival of the service through disruption. Satellite survival matters, but it is only one component of that requirement. An operational spacecraft can become inaccessible through compromised ground infrastructure, unusable through corrupted data, or unavailable to a government customer because priority rights were never secured.

Protection must therefore encompass the complete chain from spacecraft command to the decisions made by the end user. This changes both the definition of vulnerability and the evidence required to claim resilience.

Vulnerability follows shared dependencies

Distributing a mission across many spacecraft reduces some consequences of individual failures. It provides less protection when those spacecraft share command credentials, software, gateways, update infrastructure or a single contractual access mechanism.

The relevant engineering question is: which functions can fail together, and which remain independently recoverable?

The following table is an analytical framework for answering that question.

Dependency	Potential operational consequence	Evidence needed to assess exposure	Protection priority
Spacecraft command authority	Loss of legitimate control or acceptance of unauthorized commands	Command authentication architecture, privilege separation and recovery procedures	Preserve a trusted route to command
Fleet software and updates	A defect or compromise propagates across multiple spacecraft	Software lineage, update authorization and rollback demonstrations	Limit common failures across the fleet
Ground control and gateways	Healthy spacecraft become inaccessible	Independent control facilities, network dependencies and tested failover	Maintain command and service access
Communications links	Intermittent or sustained service denial	Interference monitoring, link performance and alternative access paths	Preserve essential traffic under degradation
Navigation and timing inputs	Incorrect positioning, synchronization or downstream decisions	Independent checks, integrity warnings and fallback performance	Detect misleading information before use
Data processing and distribution	Delayed, altered or unauthenticated products reach users	Provenance, processing records and end-to-end integrity checks	Protect confidence in delivered information
Personnel and external support	Recovery depends on unavailable specialists or vendors	Staffing exercises, access rights and support obligations	Make recovery executable by the authorized operator
Commercial service rights	Capacity exists but cannot be assigned when required	Priority clauses, jurisdiction, termination provisions and allocation rules	Secure usable access during crisis

This approach is consistent with the system-wide treatment of command and control in NIST IR 8401 and the treatment of independently owned, interconnected components in NIST’s Hybrid Satellite Networks profile. These publications provide risk-management frameworks; they do not certify that a particular constellation can withstand an attack.

The operational lesson of KA-SAT

The February 2022 KA-SAT incident demonstrates why spacecraft protection and service protection require separate assessment.

According to Viasat’s incident account, a ground-based intrusion affected a consumer broadband partition, disrupting several thousand customers in Ukraine and tens of thousands elsewhere in Europe. The company reported that the satellite itself was unaffected. Recovery included shipping tens of thousands of replacement modems.

The incident therefore exposed a dependency extending from network management to equipment in users’ premises. Restoring central infrastructure did not automatically restore every affected user.

The EU subsequently attributed the malicious activity to the Russian Federation on 10 May 2022. That public attribution followed the incident of 24 February, illustrating the difference between the operational response clock and the public attribution clock. Viasat

Three procurement implications follow.

First, recovery must be measured at the user endpoint. Second, physical replacement logistics belong inside cyber-resilience planning. Third, an operator must be able to contain an incident before a government completes its public assessment of responsibility.

Attribution requires several separate judgments

A close approach, a communications outage and an unexpected manoeuvre are observations. Each requires explanation, but none establishes hostile intent by itself.

A disciplined attribution process should distinguish the following questions.

Judgment	Question to resolve	Stronger supporting evidence	Remaining limitation
Event detection	What changed?	Independent observations, telemetry and synchronized logs	Detection may be incomplete
Mechanism	How was the effect produced?	Consistent technical evidence across affected components	Several mechanisms may explain similar symptoms
Object or infrastructure identification	Which spacecraft, transmitter or network was involved?	Correlated tracking, communications and infrastructure records	Identification does not establish command responsibility
Actor attribution	Who directed or controlled the activity?	Corroborated technical, intelligence and organizational evidence	Public evidence may be narrower than classified evidence
Intent assessment	Was the effect deliberate, incidental or accidental?	Repeated behaviour, communications and operational context	Capability alone does not prove intent
Legal characterization	Which obligations or thresholds are relevant?	Established facts assessed against applicable law	Technical severity and legal classification are different questions
Political response	What action serves the national or allied objective?	Assessment of consequences, alternatives and escalation risks	A technically feasible response may be strategically undesirable

These stages should inform one another without being collapsed into a single confidence label.

An operator might have high confidence that interference caused an outage, moderate confidence about its geographic origin, and insufficient evidence to identify the directing authority. A government can still protect users while preserving those distinctions.

Evidence preservation is therefore an operational capability. Contracts should provide access to relevant logs, retention rules, time synchronization, chain-of-custody procedures and arrangements for releasing a sanitized account. Without these provisions, a government may acquire a sophisticated service while remaining unable to substantiate interference against it.

Resilience must be measured at mission level

Fleet availability is an incomplete performance measure. A system can report high average availability while failing the users, locations or time windows that matter most.

A protection programme should establish a minimum service floor for each essential mission.

Measure	Definition for acceptance testing	Why it matters
Essential-user coverage	Share of designated users receiving the minimum required service	Prevents aggregate capacity from hiding critical gaps
Maximum continuous outage	Longest uninterrupted loss of an essential function	Captures consequences that annual averages obscure
Detection delay	Time from disruption onset to a validated operational alert	Determines how long users may act without warning
Trusted-control recovery	Time needed to restore verified command authority	Distinguishes access restoration from secure restoration
Alternative-service activation	Time to deliver usable service through another provider or architecture	Tests whether diversification works in practice
Information integrity	Ability to detect or reject corrupted products	Addresses plausible but misleading outputs
Sustained degraded operation	Duration for which minimum service can be maintained	Tests endurance after the initial response
User restoration	Time until affected terminals and workflows are operational	Includes logistics and local support
Recovery independence	Recovery achievable without unavailable foreign or vendor intervention	Measures practical freedom of action

These are proposed evaluation measures, not universal numerical standards. Their thresholds should follow mission consequences.

A timing service supporting safety-critical infrastructure and an imagery service supporting periodic analysis should not receive identical outage limits. Nor should a provider receive full credit for a fallback that exists technically but cannot be activated under the customer’s contractual rights.

The same distinction applies to navigation interference. In their joint warning of 25 March 2025, ITU, ICAO and IMO highlighted harmful jamming and spoofing and called for protective measures, including conventional navigation alternatives. The strategic implication is that severe downstream disruption can occur without damage to any spacecraft.

Legal thresholds must remain distinct

Orbital proximity creates operational concern without automatically resolving questions of legality, responsibility or response.

The Outer Space Treaty establishes several relevant obligations, but it does not create a universal numerical separation distance between satellites.

Legal issue	Relevant provision	Consequence for operational policy
Private space activities	Article VI: authorization and continuing supervision	Commercial ownership does not remove state responsibilities
Registry and control	Article VIII: jurisdiction, control and continuing ownership	An apparently inactive object cannot simply be treated as ownerless
Potential interference	Article IX: due regard and consultation provisions	Consultation and evidence exchange belong in incident procedures
Weapons restrictions	Article IV: specified restrictions, including orbital nuclear and other weapons of mass destruction	Avoid describing all military satellites as prohibited

These provisions support structured assessment rather than automatic conclusions from proximity alone. treaties.un.org

Damage liability also requires care. The Liability Convention distinguishes absolute liability for specified damage on Earth or to aircraft in flight from fault-based liability for specified damage to another state’s space object elsewhere. An operational outage should not automatically be represented as a straightforward compensation claim under that convention.

Alliance response is another separate question. NATO’s overarching space policy states that attacks to, from or within space could lead to invocation of Article 5, with decisions taken case by case. It does not make an unexplained approach an automatic collective-defence trigger. The UN Charter’s Article 51 concerns self-defence in the event of an armed attack; applying that threshold requires assessment of the circumstances.

Protection and escalation should use different decision clocks

An incident procedure should permit rapid protective action while retaining deliberate control over public accusation and coercive responses.

Observed condition	Immediate operational objective	Separate strategic decision
Unexplained service degradation	Preserve essential service and collect evidence	Whether the event warrants governmental notification
Suspected command compromise	Establish trusted control and contain affected systems	Whether attribution supports public disclosure
Unexpected proximity	Improve tracking and reassess operational safety	Whether to request clarification or consultations
Corroborated harmful interference	Protect users and document consequences	Which diplomatic, regulatory or allied measures are justified
Persistent disruption across providers	Activate mission priorities and independent alternatives	Whether the event forms part of a wider campaign

The principal judgment is that resilience reduces the pressure to escalate on incomplete information. A government that retains essential service has more time to verify evidence and select a proportionate response.

The strongest indicator of improvement would be a witnessed recovery exercise involving the spacecraft operator, ground provider, terminal supplier and government user. The principal open question in most public programmes is whether recovery remains possible after several shared dependencies fail together.

Chapter 7 — Development pathways and observable indicators to 2031

Progress to 2031 should be judged by repeatable service, independent recovery and verified operational access. Launches, demonstrations and programme announcements remain relevant, but they provide incomplete evidence of protection.

A successful demonstration answers whether a capability can work under particular conditions. A mature service must also show that it can work repeatedly, with different customers, under adverse conditions and within an enforceable allocation of responsibilities.

The environmental baseline is already demanding

The ESA Space Environment Report 2026, using data through the end of 2025, reports more than 300 launches and more than 4,000 newly deployed payloads during 2025.

Published observation	Reference period	Strategic significance
More than 300 launches	2025	More deployments require identification, coordination and operational supervision
More than 4,000 new payloads	2025	Aggregate object growth increases the importance of reliable fleet operations
More than three intact satellites or rocket bodies re-entered daily on average	2025	Re-entry management is a continuing operational responsibility
Fragmentation can sustain debris growth even without new launches	Long-term modelling discussed in the report	Disposal and removal remain relevant alongside launch discipline

These observations establish a workload and sustainability problem. They do not establish a scientifically defensible date for an orbital “collapse” before 2031. ESA Space Environment Report 2026

The planning implication is to include environmental constraints in protection decisions. A defensive manoeuvre consumes resources; an abandoned spacecraft can create continuing exposure; a recovery mission introduces additional coordination requirements. Protection and sustainability share parts of the same operational infrastructure.

Numerical requirements need precise interpretation

ESA’s Space Debris Mitigation Requirements, Issue 1 Revision 1, dated 23 October 2025 provide useful examples of measurable obligations.

Requirement	Published threshold	Interpretation
Successful disposal in Earth orbit	Probability above 0.9 through end of life	Includes relevant reliability and collision contributions
Clearance for spacecraft operating in the LEO protected region	Orbital lifetime below five years, with the starting point determined by manoeuvring capability	A disposal constraint, not a universal mission lifetime
Relevant cumulative collision probability during clearance	Below \(10^{-3}\) for debris larger than 1 cm	Applies to the specified assessment interval and conditions
Re-entry consequences	Expected casualties below \(10^{-4}\) per re-entry	An expected-casualty measure, not a collision probability

These are requirements within ESA’s applicable framework. They should not be presented as globally binding law. Procurement must identify the applicable clauses and verification method. esamultimedia.esa.int

Three conditional pathways

The following pathways are analytical possibilities. They can coexist across countries, orbital regimes and service classes.

Pathway	Defining development	Evidence supporting it	Evidence weakening it
Repeatable orbital services	Inspection, servicing and protection become routinely purchased services	Repeated missions, returning customers, documented acceptance and sustained support	Demonstrations do not convert into recurring operations
Selective strategic dependence	Governments retain control of a few critical functions while purchasing substantial external capacity	Independent command, evidence access and tested provider substitution	External support remains indispensable during crisis
Fragmented operational blocs	Security restrictions and incompatible interfaces divide the market	Exclusive access arrangements, restricted data exchange and duplicated infrastructure	Cross-provider qualification and practical interoperability expand

The first pathway improves the economic basis for resilience, but can also concentrate dependence in a few service providers. The second can offer an affordable degree of autonomy if the retained functions are selected carefully. The third may improve control within each bloc while reducing the capacity to exchange evidence and manage ambiguous incidents.

No pathway guarantees strategic stability. More capable spacecraft can improve inspection and recovery while also making another operator uncertain about intentions. Stability depends partly on whether operational behaviour can be explained, verified and communicated.

Observable indicators with high analytical value

A useful indicator should identify a change in usable capability. It should also specify what evidence would establish that change.

Indicator	Observable evidence	What it would establish	What it would leave unresolved
Repeat mission delivery	Several completed operations with documented outcomes	Operational repeatability	Performance against substantially different targets
Independent customer acceptance	Acceptance by a customer outside the development consortium	External utility and accountability	Broader market demand
Secure control recovery	Witnessed restoration after a controlled loss of trust	Practical recovery capability	Resistance to every attack method
Provider substitution	Essential service transferred during an exercise	Usable interoperability	Equal performance in every location
Independent evidence access	Government receives usable tracking and incident records	Greater attribution autonomy	Complete knowledge of another actor’s intent
Interface qualification	Different suppliers pass a common test	Reduced integration dependence	Guaranteed commercial competition
Crisis allocation exercise	Priority users receive contracted service during constrained capacity	Enforceable access rights	Unlimited capacity during a major conflict
Sustained staffing	Qualified teams maintain operations across prolonged exercises	Endurance beyond an initial response	Performance under every simultaneous emergency
Verified disposal	Tracked completion of the approved disposal outcome	Execution of an end-of-life obligation	Sustainability of the entire orbital population
Supplier transition	Another authorized organization assumes defined support functions	Reduced dependence on one company	Complete independence from upstream components

These indicators are deliberately more demanding than a technology-readiness label. A spacecraft may be technically mature while its service agreement, recovery arrangements or evidence access remain immature.

A proposed evaluation sequence through 2031

The schedule below is a recommended assessment sequence, not a list of announced programme commitments.

Assessment window	Main question	Required evidence	Decision enabled
Late 2026–2027	Are dependencies and authorities understood?	Dependency register, access rights, incident procedures and baseline exercises	Correct foundational gaps before expansion
2028–2029	Can capability be repeated and exchanged?	Repeated operations, external acceptance and provider-transfer exercises	Expand services that demonstrate operational value
2030–2031	Can essential missions survive sustained disruption?	Extended exercises, secure recovery and independently verified service floors	Commit to enduring operational procurement

This sequence should remain sensitive to actual performance. An early demonstration should not accelerate a long-term commitment automatically. Equally, an unexpectedly strong service record should permit earlier procurement where the evidence supports it.

For the United States, China and Europe, comparison should use the same evidence ladder:

1. Announced objective.
2. Funded and contracted development.
3. Hardware delivered.
4. Orbital demonstration.
5. Customer acceptance.
6. Repeated service.
7. Verified performance under disruption.

Each programme should be placed at the highest stage supported by evidence for the specific function being assessed. Success in one function cannot establish maturity in another.

Transparency affects the comparison itself

Public evidence is uneven. A less transparent programme may possess capabilities that are difficult to verify externally. That uncertainty should remain visible.

Conversely, a highly publicized programme may disclose numerous milestones without demonstrating repeatable operational effect. Disclosure volume is not a performance metric.

A rigorous comparison therefore needs two separate conclusions:

• Capability assessment: what the evidence supports about performance.
• Evidence confidence: how complete, independent and reproducible that evidence is.

The principal judgment for 2031 is that the most consequential development may be institutional repeatability: the ability to buy, authorize, operate, recover and verify a service consistently.

The strongest changing indicator would be repeated customer acceptance combined with a credible disruption exercise. The main unresolved public question is whether emerging services will retain their performance when operating outside the carefully prepared conditions of their initial demonstrations.

Chapter 8 — Procurement priorities, cooperation options and final assessment

European procurement should secure control over essential decisions and continuity of essential services. The priority is to identify which dependencies would prevent Europe from acting during a crisis, then remove or govern those dependencies with verifiable measures.

This approach permits selective cooperation and selective national ownership. Its success depends on acceptance evidence and enforceable rights.

Procurement priorities in order of operational consequence

The following ordering is a recommendation derived from the preceding analysis.

Priority	Procurement objective	Required deliverable	Acceptance evidence	Main risk if neglected
1	Preserve trusted command	Controlled identities, protected credentials and recovery authority	Witnessed loss-of-trust and restoration exercise	A healthy fleet becomes uncontrollable
2	Maintain essential service	Independent alternatives and explicit service floors	Mission-level failover exercise	Capacity exists but critical users lose access
3	Preserve evidence and decision autonomy	Data rights, retention and incident records	Reconstruction of a test incident	Government cannot substantiate interference
4	Secure crisis access	Priority allocation and continuity provisions	Constrained-capacity exercise	Commercial allocation overrides national need
5	Enable support transfer	Documentation, tools and authorized substitute support	Partial transfer to another qualified organization	Supplier failure becomes mission failure
6	Purchase selective orbital intervention	A defined inspection, recovery or servicing outcome	Customer acceptance against a specific mission requirement	Expensive capability lacks a usable operational role

Orbital intervention belongs in the portfolio where it changes mission outcomes. Its value depends on whether it reaches the relevant object, acts within the required time, has the necessary authorization and produces a benefit greater than alternative measures.

A servicing mission that extends the life of an important asset may be highly valuable. It does not automatically resolve a compromised ground network or restore thousands of damaged terminals. Procurement should connect each capability to a defined failure mechanism.

Acceptance must test the complete service

The customer should retain responsibility for defining the operational consequence that must be avoided. Suppliers should demonstrate the corresponding outcome through controlled, authorized testing.

Proposed acceptance scenario	Required demonstration	Evidence retained
Primary control facility unavailable	Authorized personnel maintain or recover essential control through an independent arrangement	Timeline, command records and remaining dependencies
Credentials no longer trusted	Control is restored under verified identities without unsafe command ambiguity	Revocation, replacement and validation records
Primary service provider unavailable	Designated users receive the minimum service through an alternative	User-level performance and activation time
Misleading navigation or timing input	The system identifies loss of integrity and enters an approved fallback	Detection behaviour and downstream effects
Evidence sources disagree	Analysts preserve competing explanations and identify additional collection needs	Decision record and uncertainty assessment
Vendor support interrupted	Authorized teams perform agreed essential functions	Tasks completed, support required and unresolved limitations
Capacity sharply constrained	Priority allocation follows the contract and mission hierarchy	Allocation records and essential-user outcomes
Recovery requires local equipment	Replacement logistics restore affected users within the agreed envelope	Delivery, installation and service-restoration evidence

Passing these tests should support payment and acceptance. Failing them should trigger corrective work, revised claims or a narrower operational role.

The customer must also inspect hidden dependencies. Two providers may use the same cloud platform, ground-station operator, identity service or terminal manufacturer. The relevant diversity is diversity of failure mechanisms and recovery paths.

Contracts should purchase operational rights

A government can own spacecraft while lacking the practical rights needed to operate or recover them. A purchased service can provide substantial freedom of action if the contract secures the necessary authority.

Contract provision	Operational purpose	Verification question
Government access to relevant telemetry and incident data	Independent assessment	Can the customer obtain usable records during an incident?
Clearly defined command authority	Avoid conflicting instructions	Who can authorize action, and how is authority authenticated?
Priority and continuity clauses	Preserve essential users	What happens when aggregate demand exceeds capacity?
Support-transfer provisions	Reduce supplier dependence	Can another authorized team perform specified functions?
Configuration and dependency disclosure	Expose common failures	Which external components can disable the service?
Exercise participation	Test the actual delivery chain	Must subcontractors participate and provide evidence?
Exit and transition arrangements	Preserve continuity when a contract ends	Can the customer migrate without losing essential functions?
Outcome-based acceptance	Connect spending to usable capability	Which demonstrated result releases payment?

Requirements should remain proportionate. Extensive disclosure can increase cost and expose sensitive intellectual property. The appropriate solution is controlled access, independently witnessed verification and carefully scoped rights.

The government needs sufficient evidence to exercise its responsibilities. It does not necessarily need unrestricted ownership of every supplier’s design.

Cooperation should be judged by the dependency it removes

Cooperation can provide additional observations, alternative access and shared verification. It can also introduce delays if authority and information-release rules remain unresolved.

NATO’s 7 July 2026 announcement reported eight allies launching the HALO initiative, Canada becoming the fifteenth STARLIFT participant, and Spain becoming the nineteenth participant in APSS.

Initiative	Relevant cooperation function	Question for European procurement
HALO	Development of an architecture integrating sovereign satellite capabilities	Which information and operational functions will become usable across participants?
STARLIFT	Cooperation concerning access to launch	What arrangements become executable during an urgent national requirement?
APSS	Cooperation supporting space-based surveillance information	Can information reach authorized decision-makers within their operational timeline?

Participation figures indicate institutional engagement. They do not establish that every planned capability has been delivered or tested.

For procurement purposes, cooperation should produce a concrete result: an additional observation source, a qualified alternative, an exercised launch arrangement, a usable information product or a verified recovery option.

European cooperation needs explicit authority

The following division is proposed as an operating model rather than a description of uniform existing arrangements.

Function	Appropriate authority or arrangement	Required boundary
National mission priorities	Responsible national government	Final authority over national objectives
Technical qualification	Agreed European or multinational technical body	Common evidence and verification criteria
Shared service acquisition	Participating procurement organizations	Defined access and allocation rights
Operational tasking	Authorized national or agreed multinational command	Clear responsibility for consequential decisions
Incident evidence exchange	Accredited technical and intelligence channels	Protection of sources alongside usable shared findings
Public attribution	Competent political authorities	Separation from routine operator statements
Alliance response	Applicable collective decision process	No implied automatic transfer of national authority

NATO’s space policy explicitly preserves national sovereignty. European arrangements should make that principle operational through agreed procedures, rather than leaving each incident to improvised negotiation.

National choices within a shared architecture

The following recommendations assign priorities without assuming that industrial participation alone creates strategic autonomy.

Italy should connect investment in orbital services to independently witnessed mission acceptance, government access to operational evidence and clear customer demand. Its strongest contribution would be a service that other European operators can qualify and purchase repeatedly.

France should connect operational protection concepts to a graduated incident process: observation, technical assessment, consultation and political decision. Exercises should test how civilian operators, military users and national authorities share evidence under time pressure.

Germany should make service access and information exploitation central acceptance conditions. Greater production capacity becomes strategically useful when authorized users can task systems, receive trusted products and continue operating through disruption.

The United Kingdom should connect mission authorization, commercial service provision and allied information exchange through practical incident exercises. A successful regulatory framework should support timely decisions while retaining clear responsibility for operational consequences.

Across all four countries, the relevant common product is an interoperable evidence and acceptance framework. Industrial specialization can then support a shared architecture without requiring every participant to reproduce every capability.

Match each decision to its burden and reversibility

Protection programmes should disclose the operational consequences of their choices.

Proposed action	Intended benefit	Principal burden	Reversibility	Second-order risk
Add independent ground recovery	Preserve command and service access	Facilities, staffing and recurring exercises	High	Apparent independence may conceal shared infrastructure
Reserve alternative capacity	Maintain essential service	Reservation fees and integration work	High to medium	Multiple customers may depend on the same reserve
Improve evidence collection	Strengthen attribution and decision quality	Sensors, analysts and secure data handling	High	More observations may still leave intent uncertain
Retain operational reserves	Preserve future options	Reduced immediately usable resources	Limited once consumed	Overly conservative rules can restrict mission performance
Procure orbital inspection or servicing	Resolve a defined on-orbit problem	Mission cost, coordination and authorization	Mission-dependent	Other operators may misinterpret the activity
Publicly attribute harmful activity	Establish accountability and support collective action	Evidentiary and diplomatic commitments	Low	Premature certainty can undermine credibility

The purpose of this framework is to keep response choices connected to operational objectives. A more visible response is not necessarily a more effective one.

Final assessment

Europe’s strategic position through 2031 will depend on whether it can preserve essential services, establish trusted facts and exercise operational authority under pressure. Spacecraft numbers and technical demonstrations contribute to that position, but cannot establish it alone.

Comparison with American and Chinese capabilities should apply the same demanding questions: who can command, who can recover, who can verify, who has priority, and what has been demonstrated repeatedly? Where public evidence is incomplete, the assessment should retain that uncertainty.

The strongest European procurement portfolio would combine secure control, independent recovery, enforceable access, shared verification and selectively purchased orbital intervention. Its success would be demonstrated when essential users continue operating through disruption and decision-makers retain credible options.

The decisive test is whether Europe can sustain a mission, reconstruct an incident and choose its response without an indispensable dependency becoming unavailable at the moment of crisis.

---

Copyright of debuglies.com – Even partial reproduction of the contents is not permitted without prior authorization Reproduction reserved