What kills a satellite?

Satellites die when a vital part fails, when propellant or power runs out, or when the launch or an early manoeuvre goes wrong.

Space is harsh, and an uncrewed satellite cannot be repaired. A single small fault can end a mission. India's own satellites give clear examples of each way it happens.

Lost before it starts

IRNSS-1H was meant to replace a failing navigation satellite. Its PSLV launch on 31 August 2017 failed, and the satellite never reached a working orbit.

NVS-02 reached its transfer orbit safely on 29 January 2025, but a loose electrical connection stopped the pyro valve on its engine's oxidiser line from opening. Without its engine, it is stranded in a 170 × 37,785 km orbit instead of its planned one. ISRO said its other systems were healthy and that it was working out ways to use it for navigation from that orbit. ISRO's committee recommended changes to make the pyro system more reliable; these were applied to CMS-03, launched on 2 November 2025 by LVM3-M5, whose pyro systems worked.

A key part fails

Each first-generation IRNSS satellite carried three rubidium atomic clocks. All three on IRNSS-1A had failed by January 2017. The satellite kept flying, but a navigation satellite without a clock cannot do navigation. The same month, ESA reported clock failures on Europe's Galileo satellites too. In 2026 the problem reached IRNSS-1F: ISRO says its atomic clock stopped on 13 March 2026, three days after it completed its 10-year design life.

Radiation is a quieter threat. NASA notes that small MEMS gyros are prone to radiation damage and to single-event upsets, where one charged particle flips a bit in the electronics.

Running out

ISRO's Mars Orbiter Mission most likely ran out of propellant. Unable to hold the pointing needed for power, it went silent after a long eclipse in April 2022, after about eight years at Mars.

Solar panels also fade. NASA lists radiation, ageing and contamination as the causes of solar cell degradation over a mission.

See it live

Find NVS-02 in the list and compare its orbit with the circular ones of its neighbours — it is alive but in the wrong place. Open the NavIC tracker

Key facts

  • IRNSS-1H: launch failure on 31 August 2017.
  • NVS-02: stranded in a 170 × 37,785 km transfer orbit since January 2025.
  • IRNSS-1A: all three rubidium clocks had failed by January 2017.
  • Mars Orbiter Mission: contact lost in April 2022 after a long eclipse; propellant likely exhausted.

Go deeper

Engineers fight random failures with redundancy. If one unit survives the mission with probability r, and the satellite works as long as at least one of n identical units works, the probability of success is

R = 1 − (1 − r)ⁿ

Illustrative: r = 0.9.

  • n = 1: R = 0.90
  • n = 2: R = 1 − 0.01 = 0.99
  • n = 3: R = 1 − 0.001 = 0.999

This is why IRNSS satellites carried three clocks. But the formula assumes failures are independent. If all units share a design flaw, a manufacturing batch or an environment, they can fail together, and the real R is close to r. Losing all three clocks on IRNSS-1A is the signature of such a common cause.

NVS-02 shows the same trap in wiring. Its pyro valve had a main and a redundant firing path. ISRO's Apex Committee concluded that at least one connector contact disengaged in each path. Two paths through one kind of connector are not fully independent. ISRO's fix, flown on CMS-03 in November 2025, aimed to improve the redundancy and reliability of the pyro system.

A useful habit is to sort failures by phase:

  • Launch — rocket failures (IRNSS-1H).
  • Early orbit — deployments and first engine firings (NVS-02).
  • Operations — random part failures and radiation (IRNSS-1A clocks).
  • Wear-out — propellant, batteries, solar cells (Mars Orbiter Mission).

Designers attack each phase differently: testing for launch, careful checks of one-shot devices like pyro valves, redundancy for random failures, and margins for wear-out.

Check yourself

Why did NVS-02 fail to reach its intended orbit?

The firing signal did not reach the pyro valve on the oxidiser line of its orbit-raising engine, most likely because a connector contact disengaged in both the main and backup paths, so the engine could not fire.

Why does redundancy not always prevent failure?

Backups help only when failures are independent. If all units share a cause — a design flaw or the same connector type — they can all fail together.

Give one Indian example each of a launch failure and an in-orbit failure.

Launch: IRNSS-1H, lost when its PSLV launch failed in August 2017. In orbit: IRNSS-1A, whose three atomic clocks all failed.

Sources

  1. GSLV-F15 / NVS-02 Mission (status update) — ISRO
  2. NVS-02 Spacecraft: On-Orbit Observations and Apex Committee Recommendations — ISRO
  3. Three Atomic Clocks Have Failed Onboard India's 'Regional GPS' Constellation — The Wire Science
  4. IRNSS — Satellite Missions — International Laser Ranging Service (NASA GSFC)
  5. IRNSS-1F successfully completed its mission life of 10 years — ISRO
  6. Update on the Mars Orbiter Mission (MOM) — ISRO
  7. State-of-the-Art of Small Spacecraft Technology — 5.0 Guidance, Navigation and Control — NASA
  8. State-of-the-Art of Small Spacecraft Technology — 3.0 Power — NASA