Launch Vehicle Third-Party Liability Insurance in India 2026: Outer Space Treaty, IN-SPACe Indemnity and the Liability Cap

For an Indian launch vehicle operator, the property and launch covers protect the operator's own balance sheet. Third-party liability is different in kind. It is the cover that the state requires before it will authorise a launch at all, and it is the cover that sits between a private startup and a potentially uncapped international claim against the Republic of India. By 2026, with Skyroot and Agnikul moving from demonstrator flights toward commercial orbital launches, third-party liability has become the single most regulated and most negotiated line in the launch insurance programme.

This post is a focused treatment of the liability layer alone. It does not repeat the full phase-by-phase programme (pre-launch property, hull, in-orbit cover, and pricing anchors), which is covered in detail in our Space Launch Startup Insurance guide and, for satellite operators specifically, in Insurance for Space Tech and Satellite Startups. Here the subject is narrower and deeper: who is liable when a launch causes third-party damage, how that liability flows from the international treaty system down to a private Indian startup, what IN-SPACe actually requires, and how brokers structure and place the resulting cover.

The reason liability dominates the regulatory conversation is structural. A launch failure that destroys the vehicle and payload is a large loss, but it is a known and bounded loss that the operator and its insurers price. A launch failure that drops debris on inhabited territory, damages a foreign aircraft, or generates a collision in orbit creates a claim whose size the operator does not control and whose ultimate counterparty may be a foreign state. The liability framework exists precisely to allocate that open-ended exposure, and insurance is the instrument the state uses to keep private operators solvent against it.

International space liability rests on two instruments India has ratified. The Outer Space Treaty 1967 establishes in Article VI that states bear international responsibility for national space activities, including those carried out by non-governmental entities, and that such activities require authorisation and continuing supervision by the appropriate state. Article VII makes the launching state internationally liable for damage caused by its space objects. The Liability Convention 1972 then operationalises that liability.

The Liability Convention draws a distinction that is central to how the risk is priced and placed:

• Absolute liability for surface damage. Under Article II, a launching state is absolutely liable to pay compensation for damage caused by its space object on the surface of the Earth or to aircraft in flight. Absolute means no fault needs to be shown. The mere fact of the damage triggers the obligation.
• Fault liability for damage in space. Under Article III, for damage caused elsewhere than on the surface (for example, one space object colliding with another in orbit), liability arises only where fault is established.

The term launching state is itself broad. It covers the state that launches, the state that procures the launch, and the state from whose territory or facility the launch takes place. For an Indian private launch from Indian soil carrying a foreign payload, India is squarely a launching state. Where more than one state qualifies, they are jointly and severally liable internationally, which is why launch services agreements between operators in different countries contain detailed allocation and cross-waiver clauses.

Because the treaty makes India internationally liable, the domestic question is how the state passes that exposure to the private operator whose activity created it. India has historically managed space liability entirely within the government, since space activity was an ISRO and Department of Space monopoly. The opening of the sector under the Indian Space Policy 2023 created the need for a formal recourse mechanism against private operators, and that mechanism is being built through IN-SPACe authorisation conditions and the long-consulted Space Activities legislation.

The structure that has emerged in practice works in three layers:

1. State faces the international claim. If a third-party claim is presented against India under the Liability Convention, the state is the respondent on the international plane.
2. State recovers from the operator by indemnity. As a condition of authorisation, the operator signs an indemnity in favour of the government, agreeing to reimburse the state for claims arising from the operator's activity. This indemnity is the legal hinge of the whole system.
3. Operator backs the indemnity with insurance. The operator must hold third-party liability insurance up to the limit IN-SPACe specifies, so that the indemnity to the state is funded rather than merely promised.

This mirrors the architecture used by other launching states. The United States runs a three-tier system under its Commercial Space Launch Act in which the operator insures up to a maximum probable loss figure, the federal government indemnifies a defined band above that, and the operator is again exposed above the government band. France, the United Kingdom, and Japan operate comparable insure-then-indemnify structures, several of which include a statutory cap on the operator's exposure. India's framework is converging toward the same shape, and the open policy question that most affects operators is whether and at what level a cap on operator liability will be fixed.

IN-SPACe, established under the Indian Space Policy 2023 as the single-window authorising body for private space activity, sets the insurance conditions that an operator must satisfy before launch. The liability requirement is not a single fixed number across the sector. It is calibrated to the activity, and brokers need to understand the inputs because they drive the limit the programme must reach.

The principal factors IN-SPACe weighs in setting a third-party liability limit are:

• Activity type. Launch operations carry a far higher third-party damage potential than satellite operations or ground-station activity, and attract correspondingly higher limits.
• Maximum probable loss. The limit is typically anchored to a maximum probable loss assessment of the specific mission, considering the launch trajectory, overflight of populated areas, the debris-fall footprint, and the range safety regime, rather than to the value of the vehicle.
• Launch site and trajectory. A launch from Sriharikota over the Bay of Bengal presents a different surface-damage and overflight profile than other trajectories, and the assessment reflects it.
• Payload and mission. Foreign payloads, sensitive missions, and orbits with heavy debris populations can raise the assessed exposure.

In 2025-26 the limits seen on Indian launch authorisations have ranged from tens of crores to several hundred crores, expressed or placed in USD-equivalent terms commonly between USD 50 million and USD 500 million depending on mission scale. These figures should be read as the regulator's calibration of probable loss, not a ceiling on what a catastrophic event could cost. The broker's task is to confirm the exact authorisation figure for each mission rather than carry a standing assumption, because the requirement is set application by application.

The documentation discipline matters as much as the limit. IN-SPACe expects to see policy certificates, cover summaries, evidence that the cover period brackets the authorised activity, and confirmation that the cover stays in force for the authorisation validity. A programme that meets the limit on paper but mistimes its inception or termination against the authorised launch window does not satisfy the condition.

Two features of launch liability practice decide how much residual exposure actually reaches the operator's balance sheet: whether there is a cap on operator liability, and how liability is waived among the parties to a launch.

On the cap, the position in India in 2026 is unsettled in statute but addressed in contract. Mature launching jurisdictions cap the operator's liability at the insured maximum probable loss figure and have the state absorb the excess, on the policy logic that no private launch industry can survive uncapped exposure to a catastrophic third-party event. India's draft Space Activities framework has been expected to introduce a comparable cap, but until it is law the operator's protection above the insured layer depends on the indemnity terms agreed with the government in the authorisation. Brokers should flag this gap explicitly to operators and their boards, because it is the part of the exposure that insurance does not reach.

On waivers, the launch industry relies heavily on inter-party cross-waivers of liability. In a typical launch services agreement, the launch provider, the payload customer, and their respective contractors and sub-contractors each waive claims against the others for damage to their own property and personnel arising from the launch, regardless of fault. The effect is to confine each party's first-party losses to its own insurance and to remove cross-claims between the participants. This is why a satellite operator and a launch vehicle operator each carry their own hull and pre-launch covers rather than suing one another after a failure. Cross-waivers do not, however, reach genuine third parties who are not part of the launch. Claims by uninvolved third parties on the ground, by other satellite operators in orbit, or by foreign states remain live, and that is exactly the exposure the mandatory third-party liability cover is built for.

Third-party liability is not a single moment of risk. The exposure changes character across the mission, and a well-drafted policy responds across all of it rather than only at launch.

• Pre-launch ground phase. While the vehicle is being integrated and fuelled at the range, third parties (range personnel outside the operator's own waivered group, neighbouring facilities, the public near the site) can be harmed by fuel handling, ordnance, or ground-equipment incidents. This is conventional liability territory but at a hazardous facility.
• Launch and ascent phase. This is the period of absolute liability for surface damage under the Liability Convention. A failure during ascent can scatter debris across the range safety footprint, with exposure to populated areas, maritime traffic, and aircraft in the overflight corridor. The range safety and flight termination regime is designed to contain this, and underwriters scrutinise it closely.
• In-orbit phase. Once on orbit, the liability shifts to the fault-based regime of Article III of the Liability Convention. The realistic exposure is a collision with another operator's satellite or the generation of debris that later causes damage. Conjunction analysis discipline and collision-avoidance capability are increasingly underwriting conditions, not optional extras.
• Re-entry phase. Spent stages and end-of-life objects that re-enter the atmosphere can cause surface damage, returning the exposure to the absolute liability regime. Controlled de-orbit and disposal planning bear directly on this tail.

The practical drafting point is that the third-party liability cover should follow the space object through all four phases with a single consistent limit and clear definitions of where one phase ends and the next begins, rather than leaving the in-orbit or re-entry tail to a different cover or to chance.

Once the required limit is fixed, the programme has to be built and placed, and the third-party liability layer for a launch is a specialty placement rather than a domestic commercial one. The structure that is workable for an Indian launch operator in 2026 typically has the following shape.

A primary layer, often the first USD 50 million to USD 100 million equivalent, is placed through an Indian insurer that fronts the risk, supported by foreign reinsurance. The major Indian commercial insurers (ICICI Lombard, HDFC Ergo, Bajaj Allianz, TATA AIG and peers) can front and retain a measured share, but the technical capacity sits in reinsurance. Excess layers above the primary are placed in the global specialty market, principally Lloyd's syndicates with space appetite and specialty reinsurers such as Munich Re and Swiss Re space teams, accessed through specialist space brokers. The capacity available to Indian programmes is improving as the specialty market grows familiar with the IN-SPACe regime, but the global launch market remains small in absolute terms, which is the deeper constraint on how programmes are built. For the broader question of how Indian risks reach Lloyd's and the Singapore market, see our note on Lloyd's Asia Singapore capacity for Indian commercial risks.

Three placement details repeatedly decide whether a launch liability programme works:

• Currency. IN-SPACe limits and customer requirements may be stated in INR while the specialty capacity prices and pays in USD. The programme has to reconcile the denomination so that the placed limit genuinely meets the authorisation in the regulator's currency, and so that a claim settles without a currency shortfall. The FEMA interface on premium and claims flows needs to be cleared in advance.
• Fronting economics. The fronting insurer charges a fee for lending its paper and retaining a sliver of risk, and the reinsurance back-to-back has to be tight so that no gap opens between what the operator is told it has and what the reinsurers actually owe.
• Pricing. Third-party liability for launch operations is commonly placed in the order of 1 to 3 percent of the limit per annum, moving with the operator's track record and the mission profile. It is a smaller line than the hull and launch covers but the one the regulator will not let the operator skip.

Third-party liability claims in space are rare and potentially catastrophic, which is the worst combination for preparation, because operators rarely have lived experience to fall back on. A realistic claim would involve the affected third party or its government, the operator, the fronting insurer and reinsurers, IN-SPACe and the Department of Space where state recourse is engaged, and technical investigators reconstructing the failure. The settlement path runs through the treaty and the domestic indemnity at the same time, which is why the wording of both must be coherent before launch, not reconciled after a loss.

A broker building or reviewing a launch liability programme should work through a consistent checklist:

• Confirm the exact IN-SPACe limit and currency for the specific mission, in writing, and place to it precisely.
• Read the government indemnity in the authorisation and identify the residual exposure above the insured layer, including whether any cap applies.
• Reconcile the cross-waiver in the launch services agreement against the third-party policy so that first-party and third-party exposures are cleanly separated with no gap.
• Bracket the cover period to the full mission, from ground processing through ascent, in-orbit operations and the re-entry tail, with no lapse between layers.
• Verify the fronting and reinsurance back-to-back so the placed limit is genuinely available on a claim.
• Assemble a submission that evidences range safety, flight termination, conjunction analysis and disposal planning, because these are what the specialty market underwrites.

Platforms that support structured programme analysis and counterparty review are beginning to help brokers carry this discipline at scale for deep-tech buyers. Sarvada supports brokers in building and comparing structured liability programmes for space-tech and similar specialty risks. Request Access to evaluate it for launch liability programme design and authorisation-condition reconciliation.

Through FY2026-27, as Indian operators move toward recurring commercial launches and the Space Activities framework matures, the liability layer is where regulatory change will land first. Brokers who understand the treaty-to-operator chain, the IN-SPACe conditions, and the cap question are positioned to advise on the part of the space programme that the operator cannot launch without.