A Satellite In Orbit Is Not Resilience

India can launch satellites.

That is not the question.

The harder question is whether India can keep flying, communicating, warning, navigating, and commanding when satellite-derived signals are jammed, spoofed, denied, degraded, or simply no longer trusted.

To be honest, this is the part of the space-security debate that feels under-discussed. We love talking about the visible part of space power. Launches are clean. They photograph well. GSAT, NavIC, GAGAN, military communication satellites, indigenous clocks, private space policy… all of that sounds like strategic progress.

And some of it genuinely is.

But a satellite in orbit is not resilience.

Resilience is what still works when the signal does not.

It is the aircraft that can still land when GPS is lying. It is the telecom network that still has trusted time when GNSS is unreliable. It is the emergency alert that still reaches people when networks are congested. It is the ship, aircraft, or military unit that has more than one communication path. It is the ground segment that is ready before the satellite’s useful life is half gone. It is the agency chain that does not lose time deciding who owns the incident.

The failure point may not be the satellite. It may be the clock, the tower, the runway, the ground station, the reporting chain, or the ministry handoff.

The 2025 ITU/ICAO/IMO warning on satellite-navigation interference is a good global frame here: GNSS disruption is not only a navigation issue; it also affects timing, synchronization, aviation, maritime operations, and wider critical services.[1]

A useful way to think about severity is this:

  • local interference -> inconvenience, reporting, short disruption
  • regional GNSS jamming or spoofing -> aviation, maritime, telecom timing, and logistics stress
  • SATCOM link denial -> ships, aircraft, remote regions, disaster response, and military units lose a path
  • ground-segment or terminal compromise -> the satellite may be fine, but the service cannot be trusted
  • targeted satellite loss -> capacity, coverage, and continuity planning get tested
  • all-satellite-denied scenario -> total-war planning construct, not the everyday baseline

The ladder matters because each step asks for a different fallback.

More satellites help some steps. They do not answer all of them. That is where the lazy answers start falling apart.

That is the real story.

The satellite may be alive. The signal may not be.

When people hear “satellite security”, the first image is often dramatic: anti-satellite missiles, space debris, lasers, maybe some co-orbital object doing suspicious things in orbit.

Those threats matter. India itself demonstrated a direct-ascent kinetic ASAT capability during Mission Shakti in 2019.[2] Global counterspace reports from groups like Secure World Foundation and CSIS track direct-ascent weapons, electronic warfare, cyber capabilities, directed energy, and co-orbital systems.[3][4]

But in day-to-day national resilience, the more likely failure is less cinematic. Less satisfying for headlines, but more dangerous in a very boring way.

The satellite is still there. The service is degraded.

The signal is jammed. Or spoofed. Or locally unreliable. Or the ground station has a cyber problem. Or the terminal cannot authenticate properly. Or the telecom network downstream loses timing. Or the fallback procedure exists on paper but was not exercised enough.

That is why this topic is not just about space. It is about dependency.

Satellite disruption can hit:

  • positioning
  • navigation
  • timing
  • aviation
  • maritime traffic
  • telecom synchronization
  • disaster response
  • military beyond-line-of-sight communication
  • public warning systems
  • financial and grid timestamping
  • ground-segment cyber operations

One weak satellite signal can be connected to a surprisingly large number of ordinary systems on Earth. And the uncomfortable part is that many of these systems do not look like “space” systems to the public at all.

That is probably why the risk is easy to miss.

India already has a warning sign in aviation.

This is not hypothetical. This is where the topic stops being abstract and starts becoming slightly annoying.

Indian aviation authorities already treat GNSS interference as a live safety and reporting problem. DGCA issued Advisory Circular ANSS AC 01/2023 on 24 November 2023, titled GNSS Interference in Airspace. A public copy is available through an IATA mirror, and DGCA/AAI material presented through ICAO also references India’s GNSS interference response.[5][6]

The circular matters because it does not treat GPS spoofing as some exotic internet panic. It treats it as an aviation safety-management issue. It talks about reporting, stakeholder roles, threat monitoring, operator risk assessment, crew awareness, and contingency planning.

Most importantly for this blog, it also tells aviation stakeholders to account for GNSS interference while rationalizing conventional navigation and surveillance infrastructure. In plain English: do not throw away too much of the old fallback world just because satellite navigation is convenient.

That is a very important point, and honestly, it should be one of the core lessons of the whole debate.

Modern aviation wants performance-based navigation. It wants RNAV/RNP procedures. It wants satellite-aided efficiency. Fair enough. But when GNSS is degraded, the boring old stuff suddenly matters again. AAI’s CNS services page lists conventional layers such as ILS, DVOR, DME, NDB, radar, ADS-B, HF/VHF communication, and ATM automation.[7] Those systems are not nostalgia. They are part of resilience.

And yes, India has official reporting data too. A Lok Sabha answer says GPS interference reporting started after the DGCA circular, and that 1,951 GPS interference issues were reported from November 2023 to November 2025.[8] Another Lok Sabha answer reports 465 GPS/GNSS interference and spoofing incidents near Amritsar and Jammu between November 2023 and February 2025.[9]

We have to be careful here. These numbers are not all the same scope. The 465 number is not “Delhi had 465 incidents.” The 1,951 number is a wider reporting figure after the DGCA circular. A separate Lok Sabha answer discusses GPS interference around Delhi airspace for other periods.[10] Mixing them together would be sloppy.

But the broad point is solid: official India is seeing enough GNSS interference to formalize reporting and contingency response.

There is also a 10 November 2025 DGCA SOP for real-time reporting of GPS spoofing/GNSS interference around IGI Airport, referenced in Lok Sabha AU893 and Rajya Sabha AS5.[11][12] I have not found the direct DGCA-hosted SOP PDF yet. So the clean wording is: Parliament confirms it exists; the public PDF has not been recovered.

That caveat matters. This whole topic requires discipline. If we exaggerate, we make the argument weaker.

”Just use NavIC” is not an answer.

NavIC is important.

India having its own regional navigation system is strategically meaningful. It reduces exclusive dependence on foreign GNSS. ISRO describes NavIC as an independent regional navigation satellite system designed to cover India and roughly 1,500 km beyond the Indian boundary, with civilian and restricted services. ISRO also discusses modernization through the NVS series and L1 signal support on its satellite navigation pages.[13]

So yes, NavIC matters.

But NavIC is not magic.

It is still a satellite radio-frequency system. If the issue is weak satellite signals being overwhelmed, misled, interfered with, or distrusted, then adding a sovereign constellation improves control and diversity. It does not make the receiver immune to physics.

This is where national-security writing often becomes cheesy. It is tempting to say: foreign GPS can be denied, therefore Indian NavIC solves the problem. That sounds neat. It is also too neat.

The better framing is:

NavIC improves India’s sovereign PNT options, but it is one layer in a resilient PNT stack, not a standalone answer to jamming or spoofing.

Same with GAGAN.

GAGAN is useful for aviation. ISRO describes it as GPS Aided Geo Augmented Navigation, and AAI says GAGAN is India’s SBAS developed with ISRO to improve the accuracy and integrity of GPS signals for civil aviation.[7][13] PIB also describes GAGAN as operational for aviation services and procedures.[14] But the phrase is right there: GPS aided. It is not a GPS-independent terrestrial fallback.

So if GNSS itself is degraded, GAGAN is not the same kind of fallback as ILS, DME, VOR, radar, or procedural control. It helps in the GNSS world. It does not replace the non-GNSS world.

That distinction is not academic. It is the difference between diversity and dependency. Confusing the two is how we get bad policy dressed up as confidence.

The quiet dependency is the clock.

Position gets all the attention. Timing is the quieter dependency.

GNSS is not just “where am I?” It is also “what time is it, precisely?” Modern telecom networks, logging systems, financial systems, power systems, and distributed infrastructure need synchronized time. If time becomes untrusted, the failure may look like a network problem, a logging problem, a billing problem, a traceability problem, or a coordination problem.

This is where India’s public resilience story is actually interesting. Maybe not exciting, but important.

TEC’s 49189:2022, the National Plan for Distribution of Indian Standard Time to Licensed Service Providers, explicitly recognizes dependence on GNSS timing as a vulnerability. It discusses distributing Indian Standard Time to licensed telecom providers, anchored to UTC(NPLI) / CSIR-NPL, through Time Source Centres and controlled timing distribution.[15]

That direction is also visible in PIB’s June 2025 “One Nation, One Time” release, which frames IST dissemination as strategic infrastructure across sectors such as financial markets, power grids, telecommunications, and transportation, while also warning about dependence on foreign time sources vulnerable to spoofing and jamming.[16]

That is a big deal. Not the kind of thing that gets hype, but still a big deal.

Not flashy, but important. Actually, maybe because it is not flashy, it matters more. Satellite resilience is not only about more satellites; it is also about whether the national network can still trust its clocks.

But again, caveat. A plan is not the same as complete deployment. The TEC document is strong evidence that India recognizes the timing vulnerability and has a national plan. It is not, by itself, proof that every operator and every critical node has already moved to a fully resilient timing architecture.

This should become one of the blog’s core questions:

India has a verified telecom timing plan. How far has the operational rollout gone?

That is not a gotcha. That is the right question. Plans are nice. Deployment is where reality starts.

Cell towers help. Cell towers also fail.

You asked earlier whether phone towers can be used. Short answer: yes, but not as some magical safe layer.

Cellular networks can be part of the fallback stack. They can carry voice, SMS, data, public alerts, coordination traffic, and local communications. India also has public-warning work through Cell Broadcast, the CAP-based SACHET ecosystem, and C-DOT’s CAP Integrated Alert System.[17][18][19] Cell Broadcast is especially important because it broadcasts alerts to devices in a target cell area rather than sending one individual SMS per person. During congestion, that difference matters.

But a cell tower is not automatically resilient. It is infrastructure, not a miracle.

It needs power. It needs backhaul. It needs spectrum that is not locally jammed. It needs a functioning core network. It needs timing. It needs operational staff. It needs cyber integrity. It needs interconnection with the alerting system. It needs handset support.

So the right answer is not “use cell towers instead of satellites.” That only replaces one lazy answer with another one.

The right answer is:

Use terrestrial telecom as one fallback layer, but design it assuming timing, backhaul, power, RF conditions, and cyber systems can fail too.

Same with fibre.

Fibre is resistant to RF jamming along the cable path. That is genuinely valuable. A satellite jammer does not jam glass in the ground. But fibre still has endpoints, repeaters, landing stations, power systems, routing systems, physical cuts, and cyber layers.

Nothing is invulnerable. The point is not to find the one perfect layer. The point is to ensure layers fail differently.

Protected SATCOM is not just “encrypted satellite internet.”

Sometimes satellite communication is unavoidable. No amount of “just use fibre” fixes a ship in the middle of the ocean.

Ships need it. Aircraft may need it. Remote regions need it. Military deployments need it. Disaster response may need it when terrestrial infrastructure is damaged. In those cases, the answer is not ordinary satellite communication. It is protected SATCOM.

At a high level, protected SATCOM can involve:

  • directional antennas
  • narrower beams
  • spread spectrum
  • frequency agility
  • beamforming and nulling
  • adaptive coding and modulation
  • multi-band terminals
  • encryption and authentication
  • interference detection
  • gateway diversity
  • multipath routing

But there is a trap here too. Encryption protects content. It does not stop someone from denying the RF link. Directional beams help, but they do not make a system immortal. Multi-band terminals help, but they still depend on terminals, gateways, ground networks, power, and operators.

India has public military SATCOM markers: GSAT-7, GSAT-7A, CMS-03 / GSAT-7R, GSAT-7B procurement, and GSAT-7C approval.[20][21][22][23] ISRO says CMS-03 launched on 2 November 2025 as a multiband communication satellite covering a wide oceanic region including the Indian landmass.[24] PIB sources verify GSAT-7B contract-level facts and GSAT-7C approval-level facts.[22][23]

But public sources do not reveal India’s classified protected waveforms, anti-jam implementation, terminal details, TRANSEC, hopping patterns, or adaptive nulling specifics. And we should not pretend they do.

That boundary is important. A public blog can explain the defensive concept without drifting into operational nonsense.

Policy exists. Readiness is the question.

The lazy critique would be: India has no policy.

That is not true.

India now has multiple policy and governance pieces:

  • Indian Space Policy 2023[25]
  • IN-SPACe authorization norms and guidelines[26]
  • DGCA GNSS interference circular and reporting process
  • TEC telecom timing plan
  • CERT-In / SIA-India space cybersecurity framework[27]
  • defence SATCOM procurement and launch milestones
  • AAI and DGCA involvement in aviation fallback response

The better critique is more uncomfortable, and in my opinion, more useful:

Are these layers connected, enforced, exercised, funded, and synchronized with procurement?

CERT-In’s 2026 space/SatCom cybersecurity framework is a good example. It is real. It covers ground segment, space segment, communication links, user terminals, incident reporting, access control, supply chain, monitoring, and secure operations. That is progress.

But PIB describes the guidelines as advisory.[28] So the right question is not “does India have a space cyber framework?” It does.

The right question is:

Which parts are actually enforceable, through which law, license, procurement contract, IN-SPACe authorization condition, or sectoral rule?

This is where political critique can be useful, if it stays evidence-first.

Similarly, IN-SPACe gives India a space authorization layer. That matters. It gives the state a way to regulate private space activities, ground stations, satellite control, high-resolution remote sensing data, and national-security conditions.

But if private satellites, telecom systems, aviation systems, and defence users overlap during a crisis, who leads? CERT-In? NCIIPC? IN-SPACe? DoT and spectrum-monitoring agencies? DGCA? AAI? ISRO? MoD?

That is not bureaucracy trivia. In a fast-moving signal or cyber incident, minutes matter. Confusion is also a failure mode.

GSAT-6 is the warning label.

If this still sounds abstract, GSAT-6 makes it concrete.

The CAG Report No. 21 of 2022 is brutal. It says GSAT-6 was launched at a cost of Rs 508 crore, but the Department of Space could not use the satellite as envisaged because the ground segment was not ready. The first phase of the ground segment was completed only in July 2020, though the satellite launched in August 2015. CAG also records that DoS used 20 percent capacity for societal applications and research projects and was not aware of utilization of the balance 80 percent.[29]

Needless to say, this is exactly the kind of thing that should make us careful with space-power headlines.

The issue is not only whether India can build or launch a satellite.

The issue is whether the user segment, ground segment, governance, ownership, utilization plan, and fallback architecture are ready when the satellite is ready.

Otherwise, we get strategic theatre instead of strategic resilience.

And yes, that sounds harsh. But this is where harshness is useful.

The answer is a stack, not a slogan.

So what should India actually aim for?

Not one perfect technology.

A stack.

The shortcut answers all fail for the same reason:

ShortcutWhy it is incomplete
”Just use NavIC.”Sovereignty helps, but NavIC is still satellite RF.
”Just use GAGAN.”GAGAN improves GNSS integrity, but it is GPS-aided.
”Just use towers.”Cellular networks need power, timing, backhaul, spectrum, core networks, and cyber.
”Just encrypt it.”Encryption protects content. It does not prevent RF denial.
”Launch more.”More satellites do not fix ground-segment readiness, incident command, or fallbacks.

A practical national resilience stack would include:

  • sovereign PNT through NavIC, with realistic caveats
  • aviation GNSS integrity through GAGAN, with GPS-aided caveats
  • conventional aviation navigation and surveillance fallback
  • independent timing from CSIR-NPL / IST through telecom timing architecture
  • protected SATCOM where satellite links are unavoidable
  • terrestrial fibre, microwave, cellular, radio, and Cell Broadcast where possible
  • INS/IRS for RF-independent navigation continuity, with drift caveats
  • cyber-secure ground stations, terminals, TT&C, firmware, supply chains, and SOC/NOC operations
  • clear incident command across DGCA, AAI, DoT, spectrum-monitoring agencies, CERT-In, NCIIPC, IN-SPACe, ISRO, and MoD
  • exercises that test combined failure, not just individual systems

This is less glamorous than a launch video. Ah well.

It is also the thing that matters when the signal is lying.

Do not bluff the gaps.

This argument gets weaker if it tries to sound more certain than the evidence allows.

So I would keep these claims out until better public evidence appears:

  • Do not claim that Delhi FIR was the “9th most affected hotspot.” OPSGROUP material supports concern around Delhi/Lahore FIRs, but the exact ranking needs careful handling.
  • Do not claim that GSAT-7B or GSAT-7C are operational. PIB verifies contract and approval-level facts, not operational status.
  • Do not claim that India has current operational eLoran or a public nationwide terrestrial PNT backup. Historical Loran-C infrastructure is not the same thing.
  • Do not claim that NavIC is impenetrable.
  • Do not claim that cell towers are safe from jamming.
  • Do not claim that CERT-In’s space framework is penalty-backed unless the legal route is proven.
  • Do not claim that Indian aviation spoofing can be attributed to a specific state actor without official or high-quality investigative evidence.

That caution is not timidity. It is how the piece stays credible. The facts already say enough. We do not need to add fake certainty on top.

Overall, the real test is underneath orbit.

Overall, India’s satellite-security conversation needs to grow up a bit.

Launches matter. Sovereign systems matter. NavIC matters. Defence SATCOM matters. CERT-In and IN-SPACe matter. The progress is real.

But if the debate stops there, it becomes shallow.

The real test is not whether India has satellites in orbit. The real test is whether India has a satellite-denied continuity plan that is layered enough to survive, public enough to trust, and exercised enough to matter.

That is a technical question. It is also a governance question: procurement discipline, ground-segment readiness, exercised fallback, and clear crisis ownership.

Because in a crisis, the satellite may still be alive.

The signal may not be.

References

  1. ITU, “UN agencies warn of satellite navigation jamming and spoofing”, 26 March 2025. https://www.itu.int/hub/2025/03/un-agencies-warn-of-satellite-navigation-jamming-and-spoofing/
  2. Press Information Bureau, “Mission Shakti”, 27 March 2019. https://www.pib.gov.in/Pressreleaseshare.aspx?PRID=1569563
  3. Secure World Foundation, “Global Counterspace Capabilities Report”. https://www.swfound.org/publications-and-reports/2026-global-counterspace-capabilities-report
  4. CSIS, “Space Threat Assessment 2025”. https://www.csis.org/analysis/space-threat-assessment-2025
  5. DGCA Advisory Circular ANSS AC 01/2023, “GNSS Interference in Airspace”, 24 November 2023, IATA mirror. https://ic.iata.org/sites/default/files/iata_sih_document_attachment/DGCA%20Circular%20on%20GNSS%20Spoofing.pdf
  6. DGCA/AAI presentation hosted by ICAO APAC PBNICG 12, “Presentation on GNSS Interference in India”, 2025. https://www.icao.int/sites/default/files/APAC/Meetings/2025/2025%20PBNICG%2012/WPs%20IPs%20Presentations/SP08-INDI_AI7_Presentation-on-GNSS-Interference-in-India.pdf
  7. Airports Authority of India, “Communication Navigation Surveillance”. https://www.aai.aero/en/services/communication-navigation-surveillance-planning
  8. Lok Sabha Unstarred Question AU1863, “GPS Interference Issues”. https://sansad.in/getFile/loksabhaquestions/annex/186/AU1863_MRrh9T.pdf?source=pqals
  9. Lok Sabha Unstarred Question AU3374, “GPS/GNSS Interference and Spoofing”. https://sansad.in/getFile/loksabhaquestions/annex/184/AU3374_oX22L3.pdf?source=pqals
  10. Lok Sabha Unstarred Question AU3233, “GPS Interference Around Delhi Airspace”. https://sansad.in/getFile/loksabhaquestions/annex/187/AU3233_OJcXSG.pdf?source=pqals
  11. Lok Sabha Unstarred Question AU893, “False GPS Signals”. https://sansad.in/getFile/loksabhaquestions/annex/186/AU893_rLPypo.pdf?source=pqals
  12. Rajya Sabha Starred Question AS5, “GPS Spoofing at IGI Airport”. https://sansad.in/getFile/annex/269/AS5_m5Q5jl.pdf?source=pqars
  13. ISRO, “Satellite Navigation Services”. https://www.isro.gov.in/SatelliteNavigationServices.html
  14. Press Information Bureau, GAGAN aviation services release. https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=1881866
  15. Telecommunication Engineering Centre, TEC 49189:2022, “National Plan for Distribution of Indian Standard Time to Licensed Service Providers”. https://www.tec.gov.in/pdf/GRs/TEC49189_2022.pdf
  16. Press Information Bureau, “One Nation, One Time”, June 2025. https://www.pib.gov.in/Pressreleaseshare.aspx?PRID=2137279
  17. Press Information Bureau, Cell Broadcast alerting release. https://www.pib.gov.in/PressReleasePage.aspx?PRID=2257499
  18. National Disaster Management Authority, SACHET portal. https://sachet.ndma.gov.in/
  19. C-DOT, “CAP Integrated Alert System”. https://deveservices.dot.gov.in/products/cap-integrated-alert-system
  20. ISRO, “GSAT-7”. https://www.isro.gov.in/GSAT_7.html
  21. ISRO, “GSAT-7A”. https://www.isro.gov.in/ISRO_EN/GSAT-7A.html
  22. Press Information Bureau, GSAT-7B NSIL contract release. https://www.pib.gov.in/PressReleasePage.aspx?PRID=1991574
  23. Press Information Bureau, GSAT-7C Acceptance of Necessity release. https://www.pib.gov.in/PressReleasePage.aspx?PRID=1774313
  24. ISRO, “LVM3-M5 / CMS-03 Mission”. https://www.isro.gov.in/LVM3_M5_CMS_03_MISSION.html
  25. Department of Space, “Indian Space Policy 2023”. https://www.isro.gov.in/media_isro/pdf/IndianSpacePolicy2023.pdf
  26. IN-SPACe, “Norms, Guidelines and Procedures for Implementation of Indian Space Policy-2023”. https://www.inspace.gov.in/sys_attachment.do?sys_id=5d532e37877102503b0f0d060cbb35cf
  27. CERT-In and SIA-India, “Cyber Security Framework Guidelines for Indian Space Industry”. https://www.cert-in.org.in/PDF/CyberSecurityFrameworkGuideline_for_space.pdf
  28. Press Information Bureau, CERT-In/SIA-India space cybersecurity guidelines release. https://www.pib.gov.in/PressReleasePage.aspx?PRID=2233122&lang=2&reg=3
  29. Comptroller and Auditor General of India, Report No. 21 of 2022, Union Government Scientific and Environmental Ministries/Departments. https://cag.gov.in/uploads/download_audit_report/2022/Report-No.-21-of-2022-Union-Government-Scientific-and-Environmental-Ministries-Departments-068b163a5db29a5.59690847.pdf