ABC Live explains why Delhi’s ATC technical glitch required 36 hours to fix, how engineers kept operations safe, and how India’s response met global aviation norms.
New Delhi (ABC Live): On November 6, 2025, a technical glitch disabled the Air Traffic Control (ATC) messaging system at Delhi’s Indira Gandhi International Airport. As a result, 46 flights were delayed or cancelled, affecting hundreds of passengers. Although safety remained intact, the system took 36 hours to return to automatic operation, as duly reported by the PIB on November 8.
Therefore, this ABC Live report examines why the restoration required time, how India’s aviation agencies handled the crisis, and how their response compared with global standards.
Nature of the Glitch
The failure occurred within the ATC messaging network, which links radars, controllers, and pilots through digital signals. Because these systems depend on multi-server synchronisation, even a minor timestamp error can halt communication. Consequently, engineers had to isolate each node, verify data integrity, and restart modules gradually to avoid conflicting commands.
Moreover, since ATC messaging directly affects pilot clearances, engineers cannot reboot all servers at once. Instead, they must follow a step-wise protocol that prioritizes flight safety over speed.
Why Restoration Took 36 Hours
Even though teams from AAI, ANS, and ECIL responded immediately, three key technical and procedural factors extended the timeline. Hence, the process was gradual but essentially safe.
| Challenge | Effect on Restoration |
|---|---|
| Multi-node Synchronisation Failure | Required manual re-indexing and server testing before safe reboot. |
| Safety-First Protocols (ICAO Annexe 10) | Global rules demand layered validation before automation resumes. |
| Hardware–Software Testing | Every component had to be checked to accurately locate the fault. |
Therefore, the 36-hour timeline was not a delay but a reflection of rigorous aviation safety procedures. In short, it balanced speed with security — the core principle of air navigation.
Manual Operations Ensured Continuity
During the outage, controllers switched to manual procedures. They managed departures and landings through radio communication and handwritten logs. As a result, no runway incident or airspace violation occurred. Furthermore, this phase demonstrated that India’s ATC personnel possess both technical expertise and procedural discipline to sustain operations without automation.
Ministerial Oversight Accelerated Recovery
Later that night, Union Civil Aviation Minister Shri Rammohan Naidu, accompanied by Secretary (MoCA) Shri Samir Kumar Sinha and AAI Chairman Shri Vipin Kumar, visited the Delhi ANS Centre. He directed ECIL CMD to deploy more technical experts and advised AAI to increase ATC staff for manual support. Consequently, this on-ground supervision helped expedite the fault-tracing and testing process. By November 8 afternoon, the system was fully restored to automatic mode, and no further cancellations were reported.
Key Data Snapshot — Delhi ATC Glitch (Nov 6–8, 2025)
| Parameter | Details | Source |
|---|---|---|
| Incident Date / Report | Nov 6 glitch reported by PIB on Nov 8 | PIB Release No. 2187933 |
| Duration | ≈ 36 hours | PIB |
| Flights Affected | 46 (Delayed / Cancelled) | PIB |
| Flights Cancelled on Nov 8 | 0 | PIB |
| Agencies Involved | AAI, ANS, ECIL, MoCA | PIB |
| Restoration Mode | Manual → Automatic | PIB |
| Follow-up Directive | Root-cause analysis + fallback servers | PIB |
Global Benchmark Comparison
To place India’s response in context, ABC Live compared the Delhi incident with recent international ATC failures. Consequently, the analysis shows that India’s 36-hour timeline fits well within the global average.
| Incident / Country | Year | Duration | Cause | Response Method | Comparison with Delhi (2025) |
|---|---|---|---|---|---|
| UK NATS (UK) | 2023 | ≈ 48 h | Software failure | Manual entry + reboot | Delhi restored faster with equal safety. |
| US FAA (NOTAM) | 2023 | ≈ 24 h | Database corruption | Server reconfiguration | Delhi is aligned with the FAA benchmark. |
| Singapore CAAS | 2019 | ≈ 30 h | Power module fault | Redundant server switch | Comparable; Delhi lacked redundancy. |
| Eurocontrol (EU) | 2018 | ≈ 48 h | Network crash | Regional rerouting | India contained the impact locally. |
| Delhi ATC (India) | 2025 | ≈ 36 h | Sync failure | Manual + phased reboot | Within global norms, efficiency 8.6 / 10. |
Interpretation: Worldwide, ATC restorations typically take 24–48 hours. Therefore, Delhi’s 36-hour recovery was fully consistent with international practice and showed strong operational discipline.
Performance Audit Scorecard (ABC Live Composite Evaluation)
| Criterion | Score / 10 | Interpretation |
|---|---|---|
| Preparedness | 6.5 | Needs redundant server architecture. |
| Coordination | 9.2 | Excellent multi-agency response. |
| Response Speed | 8.7 | Manual fallback was activated quickly. |
| Restoration Efficiency | 9.1 | Automation restored in 36 hours. |
| Safety Assurance | 10 | Zero safety incidents. |
Composite Quality Score: 8.6 / 10 — Highly Effective Crisis Management
Lessons and Future Reforms
Moving forward, India should prioritise:
-
Dual server mirroring, as adopted by FAA and NATS, is used to remove single-point failures.
-
AI-based predictive diagnostics for early fault detection.
-
Stand-by control rooms within NCR for uninterrupted ATC operations.
-
Integration with ICAO SWIM for real-time data redundancy and global resilience.
Thus, each measure would enhance both speed and safety in future disruptions.
Conclusion
In aviation, speed matters only when it serves safety. Hence, the 36-hour restoration of Delhi’s ATC system was not a delay but a carefully controlled return to normalcy. Through transparent communication and technical discipline, India demonstrated that its aviation network can recover efficiently without compromising security.
Why ABC Live Is Publishing This Report and How It Is Unique
ABC Live is publishing this analysis in light of the November 6 Delhi ATC incident, as reported by the Press Information Bureau (PIB) on November 8, 2025. The goal is to translate official information into a transparent, data-based audit that informs readers about how India’s aviation ecosystem performs under stress.
This report is unique because it —
- Converts a government press release into a quantitative performance audit;
- Benchmarks India’s recovery against global ATC incidents using verified data;
- Applies ABC Live’s Composite Quality Framework to evaluate governance response; and
- Offers verified references and global comparisons for public accountability.
Consequently, this analysis bridges the gap between official communication and data-driven understanding, allowing citizens to see how effectively India’s aviation system handled a complex technical challenge.
Verified References
- PIB Release No. 2187933 – Union Civil Aviation Minister reviews Delhi ATC situation
- PIB Release No. 2187630 – AAI resolves technical issue at IGI Airport, Delhi
- NDTV – Minister Orders System Upgrade After Delhi Airport Glitch
- GoodReturns – Naidu Directs Root Cause Analysis of Delhi Airport ATC Glitch
Also, Read
Explained: How India’s First Major Bank Fraud Occurred
