·The Hindu·15 marks·250–350 wordsS&T

Discuss the governance and data-integrity concerns that arise when AI models decide which satellite data reaches the ground.

New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →
In this answer
  1. Data-integrity concerns
  2. Governance concerns
  3. Way forward

In-orbit (edge) computing analyses data on board a satellite and sends down only "the most relevant information". This avoids waiting for ground-station pass windows [1]. NASA's Dynamic Targeting test showed onboard AI screening and choosing targets in under 90 seconds with no human input [2]. But once a machine decides what never reaches Earth, faster delivery puts both data integrity and accountability at risk.

Data-integrity concerns

  • Irreversible loss: a frame deleted in orbit can never be processed again. Errors made on the ground can be fixed later.
  • Model drift: models trained before launch meet floods and terrain they have never seen. Hardware already in orbit is hard to upgrade.
  • Correlated blind spots: the onboard task proven in flight is cloud avoidance [2]. Floods usually come with heavy cloud, so optical filters may drop the very frames taken during the disaster.
  • Overstated capability: so far the evidence covers screening and pointing the instrument. Detecting fires, volcanic plumes and storms is still a future goal [2].

Governance concerns

  • Accountability: if an AI omission delays flood relief, it is unclear who answers for it: the operator, the model vendor or the user agency.
  • Auditability: without logs of discarded frames, NRSC cannot check the model's choices.
  • Data sovereignty: as private firms enter the space economy, models trained abroad may decide what Indian users receive.
  • Misaligned priorities: low latency is valuable for emergency response, but how fast data is needed differs by user [3]. A vendor's idea of "relevance" may not match NDMA's.
  • Regulatory vacuum: there is no dedicated statute or nodal framework for onboard processing.

Way forward

  • Latency targets first: NDMA and NRSC should set a delivery time for each use, following NASA's latency-study approach [3].
  • Screen, don't delete: send urgent summaries at once and keep raw frames on the onboard recorder until the next pass. Polar stations such as AGEOS in Antarctica add downlink chances [4].
  • Audit mandate: IN-SPACe authorisations could require discard logs and model validation.
  • Radar priority: ISRO lists onboard SAR processing as a research area [5]. Radar sees through cloud, so it suits monsoon floods.

Onboard AI can speed up disaster response, but data deleted in orbit is gone for good. Used as a fast summary layer above a preserved raw archive, with audit trails and latency standards set by users, it can be both fast and accountable. That would advance resilient, transparent disaster governance in line with SDGs 11 and 13.

Sources

  1. 1The Hindu, "When orbit processing makes sense — and when it doesn't" (17 Nov 2026), explainerdefinition of in-orbit computing; pass-window delay
  2. 2NASA JPL, "How NASA Is Testing AI to Make Earth-Observing Satellites Smarter"onboard decisions in under 90 seconds; cloud avoidance proven on CogniSAT-6; event hunting still a future goal
  3. 3NASA GSFC Applied Sciences, Study on Data Latency Needs and Requirementsvalue of low latency for emergency response; latency needs differ by user
  4. 4ISRO, Space India (July–December 2016)IRS onboard solid-state recorder; AGEOS Antarctic ground station
  5. 5ISRO, Research Areas in Space 2023 (RESPOND)onboard SAR processing as a research area
Practice
7 questions on this article
Check the answer for each question, or reveal all at once.
Practice MCQs →

More from this note

More on S&T