Beyond Launch: Why a Constellation Operator Is a Different Risk
India's space sector has opened to private companies, and one of the fastest-moving segments is private Earth-observation (EO) operators: companies that own and run constellations of small satellites, capture imagery and other sensing data of the Earth, and sell the data and the analytics derived from it as a service to customers in agriculture, infrastructure, insurance, defence-adjacent, environmental and other markets. India's space economy is growing as the regulatory framework, the launch capability and private investment come together, and EO is a segment where Indian companies are building real, revenue-generating operations rather than one-off missions.
For insurance, the important point is that an EO constellation operator's risk is fundamentally different from the launch risk that dominates the popular understanding of space insurance. Launch insurance covers the rocket and the satellite through the launch and the early orbit phase, and it is a well-defined, if specialised, line. A constellation operator's risk is overwhelmingly about everything that happens after a successful launch and over the years the business runs: keeping many satellites alive and working in orbit, running the ground segment that commands the satellites and receives the data, earning revenue from a continuous data-as-a-service stream, and carrying the liabilities and professional responsibilities that come with operating spacecraft and selling data products. This is an operating-business risk profile, closer to that of a technology and infrastructure operator than to a single-launch insured.
The constellation difference
The word constellation matters. A single large satellite is one expensive asset whose loss is catastrophic to a mission. A constellation is many smaller, often individually less expensive satellites whose value and function are distributed and partly redundant: the loss of one satellite degrades the service but does not end it, and satellites are replenished over time as they reach end of life or fail. This changes the risk shape from a single large binary loss to a portfolio of in-orbit assets with attrition, replenishment and a service that depends on the constellation as a whole. The insurance question becomes less about a single total loss and more about the health, attrition and replenishment of the fleet and the continuity of the service it provides.
This post works through the EO constellation operator's risk beyond launch: the in-orbit life of the satellites and how it is insured, the ground-segment property and operations, the data-as-a-service revenue and the business interruption of that revenue stream, the third-party space liability under India's IN-SPACe authorisation regime, and the professional indemnity that attaches to selling data and analytics. It is written for the operator, the broker and the underwriter trying to build a programme for a real operating space business in the Indian regulatory context.
In-Orbit Life: Insuring a Fleet, Not a Single Satellite
Once satellites are launched and operating, they face the in-orbit environment for their service life, and the in-orbit risk is the space-specific core of a constellation operator's exposure. In-orbit insurance, distinct from launch insurance, covers a satellite against failure or loss during its operational life in orbit, and for a constellation it has to be thought about as covering a fleet with attrition rather than a single asset.
A satellite in orbit faces several hazards over its life. Component and system failures are the most common: the satellite's electronics, power system (solar arrays and batteries), propulsion, attitude control and payload can fail, and small satellites built to shorter lifetimes and tighter budgets carry real failure rates. The space environment degrades and damages satellites: radiation, thermal cycling, atomic oxygen at low orbits, and the gradual decay of components. Space debris and micrometeoroids are a growing physical hazard, especially in the congested low-Earth orbits where EO constellations operate, and a debris impact can damage or destroy a satellite. Collision risk with other objects, requiring conjunction monitoring and avoidance manoeuvres, is a real and increasing operational burden in crowded orbits.
How in-orbit cover is structured for a constellation
For a single large satellite, in-orbit cover is a high-value cover on one asset. For a constellation, the cover has to reflect the fleet structure: the operator may insure the constellation on a basis that responds to the loss of individual satellites against the fleet, with the economics built around the expected attrition and the replenishment plan rather than around a single total loss. Because individual small satellites are less expensive and some attrition is expected and planned for, an operator may choose to self-insure the expected attrition and buy cover for the loss beyond the expected, or for events that take out multiple satellites at once (a common-cause failure across a batch, or a debris event affecting several). The structure, what is insured, the deductible or attachment relative to expected attrition, and the treatment of multiple-satellite losses, has to be designed around the constellation's economics and the operator's risk appetite.
The accumulation and common-cause question
The distinctive underwriting concern for a constellation is accumulation and common-cause risk. Many satellites of the same design, built in a batch and operating in similar orbits, share design and manufacturing characteristics, so a design defect or a manufacturing fault can manifest across multiple satellites, and a single environmental event can affect many at once. This correlated-loss potential is the constellation analogue of the single-satellite total loss, and it is what an in-orbit underwriter of a constellation has to weigh: not just the probability of one satellite failing, but the probability of a systematic or common-cause loss across a large part of the fleet. The operator's design diversity, batch testing, orbital distribution and the maturity of the satellite platform all bear on this, and they are the inputs the underwriter examines.
The Ground Segment: Property and Operations
A constellation is useless without the ground segment: the ground stations that command the satellites and downlink their data, the mission-control and operations facilities, and the data-processing infrastructure that turns raw downlinked data into usable products. The ground segment is a terrestrial property and operations risk, and it is often underweighted in thinking about a space business because attention fixes on the satellites, but it is a single point of failure for the whole operation.
The ground stations, antennas, the radio-frequency equipment, the servers and the facilities, are physical assets exposed to the conventional property perils: fire, electrical fault, equipment breakdown, and the natural perils of their locations. The mission-control and data-processing facilities house high-value computing and networking equipment dependent on reliable power and cooling, much like a data centre. These are insured on property and machinery breakdown or electronic equipment bases, and the underwriting captures the resilience of the critical infrastructure, the power and cooling redundancy, the fire protection, and the protection of the high-value RF and computing equipment.
The operational dependency
The ground segment is where a constellation's operation can be interrupted by something other than a satellite failure. If a primary ground station or the mission-control facility goes down, the operator may lose the ability to command the satellites or to downlink and process their data, interrupting the service even though every satellite is healthy. The resilience of the ground segment, the use of multiple ground stations (including third-party ground-station-as-a-service networks), the redundancy of mission control, the diversity of data-processing and connectivity, is therefore both an operational resilience question and an insurance one. An operator dependent on a single ground station or a single processing site carries a single-point-of-failure exposure that an operator with a distributed ground segment does not.
Cyber and the digital dimension
A space operation is heavily digital: the satellites are commanded over communication links, the data flows through networks, and the whole operation depends on software and IT. This brings a cyber exposure, an attack that disrupts the ground systems, the command links or the data infrastructure can interrupt the operation or compromise the data, and the cyber cover has to be read together with the property and business-interruption cover because a cyber event at the ground segment can produce a business interruption and a data-integrity loss. The ground segment is, in this sense, as much an IT and cyber risk as a property one, and the programme should treat it that way.
Data-as-a-Service Revenue and Business Interruption
An EO constellation operator's revenue comes not from selling satellites but from selling data and analytics as a service: continuous or repeat imagery of areas of interest, monitoring products, change detection, and analytics built on the data, delivered to customers under subscriptions and contracts. This data-as-a-service (DaaS) revenue model shapes the business interruption exposure, and it is a different BI profile from a manufacturer's or a project's.
The DaaS revenue depends on the operator being able to capture, downlink, process and deliver the data the customers are paying for, and that capability can be interrupted at several points: a loss of satellites that degrades the constellation's coverage or revisit capability below what customers contracted for, a ground-segment failure that stops the operator commanding the satellites or processing the data, or a cyber or IT failure that disrupts the delivery pipeline. Any of these can reduce or stop the deliverable service and therefore the revenue, and the BI exposure is the loss of that revenue while the capability is impaired, plus the continuing costs and the risk of customers leaving.
Constructing the BI cover
Business interruption cover for a DaaS operator has to respond to the right triggers, which is where it gets difficult, because the revenue interruption can flow from an in-orbit loss, a ground-segment property loss, a machinery breakdown, or a cyber event, and conventional BI is triggered by physical damage to the insured's own property. The programme has to be assembled so that the BI follows the property and machinery damage at the ground segment, so that the in-orbit cover addresses the revenue consequence of losing satellites where that is the cover's intent, and so that the cyber cover addresses the business-interruption consequence of a cyber event, with the pieces fitting together rather than leaving the revenue interruption uncovered between them. The interruption from a loss of satellites is particularly awkward: the financial consequence of a degraded constellation is a revenue loss, but it flows from the in-orbit risk rather than from terrestrial property damage, and how the in-orbit and BI covers interact on a service-degradation loss has to be defined.
The customer and contract dimension
The DaaS model means the operator's exposure is tied to its customer contracts: service-level commitments, the consequences of failing to deliver, and the risk of customers terminating or claiming for non-delivery. A serious interruption can lose customers who do not return and can trigger contractual liabilities for failure to meet service levels, so the loss-of-custom and the contractual-liability dimensions extend the exposure beyond the simple lost revenue during the interruption. The operator's contracts, the service-level terms and the liability they create, should be understood when sizing the BI and the liability cover, because the contractual exposure is part of the picture.
Third-Party Space Liability and the IN-SPACe Authorisation Regime
Operating spacecraft carries third-party liability, and in India that liability sits within a specific regulatory and authorisation framework that shapes what an operator must carry. The liability exposure and the regulatory context together make this a distinctive part of the operator's programme.
A satellite operator can be liable for damage caused by its spacecraft: damage on the surface or to aircraft (the international liability framework imposes a strict standard for damage caused by space objects on the surface and to aircraft in flight), and damage caused in space to other space objects. For an EO operator in congested low-Earth orbit, the realistic concern is collision with another operator's satellite or with debris and the liability and responsibility that flow from it, and the re-entry of a decommissioned or failed satellite. The liability is potentially large and is governed by an international and national framework that ultimately engages the launching state's responsibility, which is why national regulators require operators to carry liability cover and to manage their orbital activities responsibly.
The IN-SPACe authorisation regime
India's framework for private space activity runs through IN-SPACe (the Indian National Space Promotion and Authorisation Centre), the body that authorises and supervises private space activities under the national space policy. A private operator running an EO constellation operates under IN-SPACe authorisation, and that authorisation regime is the channel through which obligations, including liability and insurance expectations, indemnification of the government, and responsible-operations requirements (collision avoidance, debris mitigation, end-of-life disposal), are imposed on the operator. The operator's third-party liability insurance has to be sized and structured to meet the authorisation requirements and to cover the realistic liability exposure, and the broker has to understand the IN-SPACe authorisation terms because they drive what cover the operator must carry. As India's space activity and its regulatory framework mature, the liability and insurance expectations attaching to authorisation are an area operators and their brokers must track.
Responsible operations as a risk control
The operator's responsible-operations practices are both a regulatory obligation and a risk control that bears on the liability exposure: conjunction monitoring and collision-avoidance manoeuvring, debris-mitigation design, and credible end-of-life disposal (de-orbiting or moving satellites to a disposal orbit) reduce the probability of a collision or a harmful re-entry and therefore the liability exposure. An operator that runs a disciplined space-traffic-management and disposal regime presents a lower liability risk than one that does not, and these practices are inputs the liability underwriter and the regulator both weigh. The growth of constellations and the congestion of low-Earth orbit make these practices increasingly central to the liability picture.
Professional Indemnity on the Data and Assembling the Programme
An EO operator does not just operate satellites; it sells data and analytics that customers rely on to make decisions, and that creates a professional indemnity exposure distinct from the physical and liability risks of operating the spacecraft. This is the part of the risk that most resembles a technology and data business, and it completes the operator's exposure picture.
When a customer uses an operator's imagery or analytics, monitoring an asset, assessing a crop, detecting a change, informing an insurance or infrastructure decision, and the data or analysis is wrong, late or misleading, the customer may suffer a loss and look to the operator. This is a professional-services and product exposure: errors or omissions in the data or the analytics, failure to deliver to specification, and the consequences of a customer relying on a flawed output. Professional indemnity cover responds to claims arising from the operator's professional services and the data products, and for a data-driven space business it is a core cover, not an afterthought, because the operator's whole value proposition is that customers can rely on its data. The cover has to be matched to the nature of the data products and the way customers use them, and the operator's contractual terms (limitations of liability, disclaimers about the use of the data) interact with the PI cover and should be aligned with it.
Data, privacy and the regulatory dimension
EO data can raise data, privacy and regulatory sensitivities, depending on what is imaged and how the data is used, and the handling of the data sits within the applicable data-protection and any sector-specific or security regulation. The operator's data-governance and the associated liability, including any cyber and data-breach exposure on the data it holds and processes, connect the professional-indemnity, cyber and liability covers, and the programme should treat the data as both an asset and a source of liability.
Assembling the programme
The EO constellation operator's programme spans an unusually wide set of covers because the business spans space operations, terrestrial infrastructure and a data service:
- In-orbit cover for the satellites, structured around the fleet, the expected attrition and the common-cause exposure.
- Property and machinery breakdown or electronic equipment for the ground segment and the data infrastructure.
- Business interruption assembled to follow the property, machinery, in-orbit and cyber triggers around the data-as-a-service revenue.
- Cyber for the digital ground segment, the command links and the data.
- Third-party space liability sized and structured to the IN-SPACe authorisation requirements and the orbital exposure.
- Professional indemnity for the data and analytics service.
The work is to make these fit together so the operator's real exposures, a satellite loss that degrades the service, a ground-segment failure, a cyber attack, a collision liability, a data error, are each answered by the right cover and the revenue interruption does not fall between them. This is a young and specialised area, and the cover is assembled across the space, property, liability, cyber and professional lines with terms that have to be defined carefully because the precedents are still developing.
For brokers building programmes for Earth-observation and other new-space operators, the difficulty is exactly this assembly across space, terrestrial and data lines, and the careful definition of where each cover responds. Sarvada gives commercial insurance brokers structured, searchable access to insurer policy wordings so they can compare the property, machinery, business-interruption, liability and professional-indemnity grants, triggers, sub-limits and exclusions across the lines a space-data operator's programme spans, and assemble a constellation-operator programme that matches the in-orbit, ground-segment, data-service and liability realities. Request Access to evaluate the platform for space-economy and new-economy risks.
