Publications
Analysis Series
Analysis//0017/May/2026/London-Dialogue. 05 May 2026
Introduction
Strategic surprise is rarely the product of a single technology. It is the product of an adversary doing something the targeted state has not theorised about, has not rehearsed against, and has not built its force structure to defeat. By that classical definition, the opening hours of Operation Sindoor on the night of 7 May 2025 produced a strategic surprise for the Indian Air Force (IAF) of the first order. Pakistan did not field a more capable individual aircraft, a more advanced missile, or a larger air fleet. It fielded a tightly drilled networked architecture that the IAF had not credited it with possessing, and it used that architecture to inflict losses on Indian frontline platforms within the first hours of combat. The episode is not yet fully understood in New Delhi, and the Indian institutional response, ranging from the Rafale source-code dispute with France to the accelerated push for IACCS–Akashteer integration, suggests it is being absorbed slowly and reluctantly. Yet the structural lesson is unambiguous. India walked into a trap whose architecture it had failed to read.
The Opening Night: What Actually Happened
Operation Sindoor was launched in retaliation for the 22 April Pahalgam attack, in which 26 civilians were killed. On the night of 6–7 May, Indian Rafale, Su-30MKI, MiG-29UPG and Mirage 2000 aircraft, operating from within Indian airspace, employed SCALP-EG, BrahMos and Rampage stand-off munitions against targets in Pakistan and Pakistan-administered Kashmir. The Pakistan Air Force (PAF) responded with a defensive counter-air operation. According to a comprehensive reconstruction by Switzerland’s Centre for Military History and Perspective Studies, PAF achieved a decisive tactical victory in the opening hours of 7 May before India recovered the initiative through deeper strikes on Pakistani airbases between 8 and 10 May. The Swiss assessment confirms visual evidence of at least one Rafale, one Mirage 2000, and either a MiG-29UPG or a Su-30MKI being lost. These figures align with what French Air Force Chief General Jérôme Bellanger told reporters in July 2025 and with the conclusions of the US-China Economicand Security Review Commission’s 2025 Annual Report, which independently put Indian losses at three aircraft.
The numerical losses, while symbolically significant, are not the analytical core of what occurred. What matters is how those losses were inflicted, because the manner of the engagement reveals an architectural mismatch that no future Indian inventory expansion can address through procurement alone. The Indian aircraft that were downed received little or no warning before the terminal phase of engagement. They were targeted by missiles whose effective envelope they had underestimated, launched from platforms that never radiated, guided by sensors operating from a different point in the battlespace, and cued by a tactical datalink that India had not assessed as operationally mature. This was not a fair fight that India lost on aircraft quality. It was a contest between two architectures, and the Indian architecture was the slower, more brittle, and less coherent of the two.
The Architecture of the Trap
The clearest open-source reconstruction of PAF’s combat sequence comes from Michael Dahm of the Mitchell Institute for Aerospace Studies, who described the engagement as “a kill chain … ‘A’ launched by ‘B’ and guided by ‘C'”. As reported by Air & Space Forces Magazine, a Pakistani ground-based radar or surface-to-air missile system performed initial target illumination; a J-10C fighter, operating in radar-silent mode, launched a PL-15E beyond-visual-range missile from standoff distance; and a Saab 2000 Erieye airborne early warning and control aircraft maintained midcourse guidance via tactical datalink until terminal homing. The forward shooter never radiated. The Indian pilots had no electronic-warfare warning of an active radar lock until the missile’s onboard seeker activated in the terminal phase, by which point evasion windows were measured in seconds rather than minutes.
Figure 1. The PAF networked kill chain on the night of 7 May 2025. The Indian target had no warning of active radar lock until the missile’s terminal seeker activated.
Three architectural features made this kill chain possible. First, the entire sensor-shooter network was bound together by a Pakistani-developed secure tactical datalink, LINK-17, which connected J-10C and JF-17 Block III fighters, the Erieye AEW&C platform, and ground-based air-defence nodes into a single battlespace picture. Second, the PL-15E reportedly engaged at distances exceeding 200 kilometres, well beyond the 145-kilometre envelope that Indian intelligence had attributed to its export configuration. A Reuters investigation subsequently confirmed that Indian planners had underestimated the missile’s effective reach. Third, the J-10CE was integrated with HQ-9 surface-to-air systems and AEW&C feeds in a manner that allowed cooperative engagement across platforms of different origin and vintage. As Dahm noted, the engagement said little about the relative merits of the J-10C and the Rafale and a great deal about the relative maturity of integration on the two sides.
This is the trap. The Indian Air Force entered the night of 7 May expecting a contest between platforms. Pakistan presented it with a contest between architectures. The Indian aircraft were optimised for that platform-centric contest, and they performed competently within it. They were not optimised for an environment in which a missile could appear without warning from a vector inconsistent with the location of any radar emission they could detect, guided by a sensor whose existence in the battlespace they could not verify. PAF did not outfight the IAF on opening night in any conventional sense. It outflanked the IAF’s entire operational logic.
What India Failed to Read
Strategic surprise is fundamentally an intelligence and assessment failure before it is an operational one. The May 2025 surprise was no exception. Indian intelligence and operational planning appear to have misread the PAF on at least four interconnected counts.
The first misreading concerned the operational maturity of LINK-17 and the depth of Sino-Pakistani interoperability. Indian assessments treated the J-10CE as a recently inducted platform whose integration with PAF’s existing AEW&C and ground-based air-defence assets remained immature. The May engagement demonstrated the opposite. PAF had clearly drilled cooperative engagement protocols across mixed-origin platforms, including Chinese fighters, Swedish AEW&C, and Chinese ground-based SAMs, to a level of operational fluency that Indian planning had not credited it with achieving. This was a failure of imagination as much as of intelligence collection. Indian assessments appear to have assumed that the integration challenges visible in their own multi-vendor inventory must logically apply to PAF as well. They did not.
The second misreading concerned the PL-15E. Indian planners assumed the export variant carried the limited 145-kilometre range officially advertised. The engagement profile observed during May suggests an effective envelope of at least 200 kilometres and possibly more. The implication is consequential. Indian beyond-visual-range tactics, formation geometry, and stand-off distances had been calibrated to the lower assumed envelope. Aircraft operating at what Indian doctrine treated as safe ranges were in fact within engagement range. The loss of at least one Rafale appears to have occurred under precisely these conditions.
Figure 2. The intelligence gap between assumed and observed PL-15E engagement envelopes left Indian aircraft operating at distances they believed were safe.
The third misreading concerned PAF doctrine. Indian operational planning had largely assumed that PAF, whose institutional culture remains rooted in a fighter-pilot tradition shaped by decades of US training and equipment, would prefer a platform-centric engagement style emphasising fighter-versus-fighter combat. The May engagement revealed a PAF that had quietly migrated toward a system-centric doctrine in which the individual fighter is a node in a networked kill chain rather than the principal actor in an aerial duel. This doctrinal shift, validated through years of joint exercises with the People’s Liberation Army Air Force, including the Shaheen series, had been visible in open-source literature for some time. Indian planning had failed to update its operational expectations accordingly.
The fourth misreading concerned the Pakistani electronic warfare environment. The Swiss reconstruction describes the PAF EW environment encountered by Indian aircraft as “intensive”, with at least one Rafale pilot reportedly forced to jettison a BrahMos missile to break a missile lock under EW pressure. Indian assessments had not anticipated the density and coordination of electronic attack that PAF was able to generate, again because the integration of EW assets into the broader sensor-shooter network had been underestimated. The cumulative effect of these four misreadings was an Indian force that entered a contested airspace believing it understood the threat envelope and discovered, in the opening hours, that the actual threat envelope was structurally different from the one its planning had assumed.
The Integration Deficit: Structural Causes
The Indian inability to detect, anticipate, or respond to the trap was not a contingent failure attributable to a single intelligence cell or operational commander. It was the surfacing of a structural problem that has been visible in Indian airpower for at least a decade. The IAF operates a fleet sourced from at least four distinct technological ecosystems, namely Russian, French, Israeli, Indian, and to a lesser extent American, with each subsystem carrying its own datalink protocols, mission-computer architecture, weapons-integration logic and electronic-warfare configuration. Integrating these into a single coherent kill chain is structurally harder than integrating a Chinese-Pakistani stack designed to interoperate from the outset. Table 1 sets out the comparative picture.
| Platform | Country of Origin | Primary Datalink | EW / Integration Notes |
| INDIAN AIR FORCE | |||
| Rafale | France | Proprietary (Dassault) | SPECTRA EW; source code withheld; no ICD access |
| Su-30MKI | Russia / India | Russian / Israeli mix | Hybrid Russian-Israeli avionics; partial integration with indigenous weapons |
| MiG-29UPG | Russia | Legacy Soviet | Limited interoperability with Western or indigenous systems |
| Mirage 2000 | France | Proprietary (Dassault) | Upgraded ICMS suite; constrained software access |
| Tejas Mk1A | India | Indigenous | Indian mission computer; integration with foreign weapons in progress |
| PAKISTAN AIR FORCE | |||
| J-10CE | China | LINK-17 (Pakistani) | Native interoperability with Erieye and HQ-9; cooperative engagement validated |
| JF-17 Block III | China / Pakistan | LINK-17 (Pakistani) | Co-developed; full integration with PAF kill chain and stand-off munitions |
| Saab 2000 Erieye | Sweden | LINK-17 integrated | AEW&C with midcourse missile guidance; networked into PAF battlespace |
Table 1. Comparative heterogeneity in IAF and PAF combat aircraft inventories. The IAF stack spans four vendor ecosystems with distinct datalinks; the PAF stack is bound together by the indigenous LINK-17 layer.
Dahm’s characterisation of the IAF as fielding “a hodgepodge” of Western, Israeli, Russian, and indigenous technology is not a rhetorical flourish but a structural diagnosis. When the Rafale’s SPECTRA electronic warfare suite, the Su-30MKI’s Russian-Israeli avionics, the MiG-29’s legacy Soviet datalink, and the Tejas’s indigenous mission computer must share a battlespace picture under fire, the seams in that architecture become exploitable. PAF’s networked kill chain was specifically designed to operate in the seams. Its J-10CE could engage targets cued by a sensor; the targeted aircraft could not correlate with any threat in its own datalink picture. That is not an accident of equipment selection. It is a deliberate exploitation of architectural heterogeneity by an adversary whose own architecture is comparatively coherent.
The Source-Code Dispute as Institutional Confession
Nowhere is the institutional acknowledgement of the integration trap more visible than in the unresolved Indo-French dispute over Rafale software access. As L’Essentiel de l’Éco first reported and The Wire confirmed, France has firmly refused to transfer source codes for the SPECTRA electronic warfare suite, the Thales RBE2 active electronically scanned array radar, and the Modular Data Processing Unit that constitute the Rafale’s combat brain. Indian negotiators have shifted their demand from full source-code transfer to the Interface Control Document, the technical blueprint specifying how weapons, sensors and electronic-warfare systems communicate across the airframe. As Defence Security Asia has reported, senior Indian Ministry of Defence officials have framed the negotiating position as “No ICD, no deal” in the prospective 114-aircraft Multi-Role Fighter Aircraft order valued at approximately USD 36–43 billion.
The strategic stakes are precisely the integration deficit that the May engagement exposed. Without ICD or source-code access, India cannot independently integrate indigenous weapons such as the Astra Mk-1 and Mk-2 beyond-visual-range missiles, the Rudram anti-radiation missile, BrahMos-NG, or future Defence Research and Development Organisation electronic-warfare suites onto the Rafale without recurring approval cycles from Dassault Aviation and Thales. Every wartime adaptation, from a new datalink protocol to an updated EW response, depends on French technical support that may be slow, conditional, or politically constrained during a crisis. US Air Force veteran Lieutenant General David Deptula, in an interview with The Wire, argued that this dependency directly contributed to the loss of at least one Rafale during Operation Sindoor because India was unable to rapidly reprogram the aircraft for indigenous munitions or optimise data-link interoperability under wartime conditions. France, as reported by Defence Security Asia in April 2026, continues to insist that source code is proprietary intellectual property that cannot be released, with French officials reportedly concerned that Indian integration of BrahMos-NG could create technological exposure to Russia.
That an Indian threat to walk away from a USD 43 billion procurement should hinge on integration access is itself the institutional confession. New Delhi now publicly recognises what the May engagement demonstrated operationally, namely that platform acquisition without integration sovereignty is no longer adequate to meet the threat environment. The dispute is not a procurement disagreement. It is the explicit surfacing of a strategic vulnerability that Pakistan exposed in a single night.
The Adaptive Response and Its Limits
India is not standing still. Operation Sindoor produced visible integration successes on the air-defence side. The IAF’s Integrated Air Command and Control System (IACCS) was fused with the Indian Army’s Akashteer air-defence network and the Navy’s Trigun maritime grid, producing what Defence Minister Rajnath Singh subsequently described as a single operational picture stretching from the Himalayan front to the Arabian Sea. As the Carnegie Endowment’s post-conflict assessment notes, Akashteer connected Akash, Israeli SPYDER, MRSAM, and S-400 batteries into a layered defensive architecture that successfully neutralised most of the small drones, kamikaze munitions, and missiles deployed in the later phase of the conflict. Approximately 400 Akashteer command nodes have been ordered, with full IACCS integration projected by end-2025.
This adaptive response, however, addresses the easier half of the integration problem. Defensive networks fuse sensors and shooters whose mission profiles are largely predefined and whose engagement parameters can be programmed in advance. Offensive air-superiority and strike kill chains, by contrast, require dynamic sensor-shooter coordination across platforms of different vintages, vendors, and software architectures, conducted under EW pressure and with engagement decisions taken at machine speed. The IAF has not yet demonstrated this capability, and the source-code dispute with France is the visible measure of how far it remains from achieving it. Defensive integration is necessary but not sufficient. The trap that Pakistan set on the night of 7 May exploited the offensive integration gap, not the defensive one, and that gap is structurally harder to close.
Implications for South Asian Deterrence
The May 2025 engagement should not be read as a verdict on the relative quality of Indian or Pakistani airpower. It should be read as evidence of a deeper shift in the deterrence calculus between the two states. For three decades, Indian planners have assumed that a quantitative and qualitative platform advantage, reinforced by access to advanced Western systems, would translate into conventional air superiority over Pakistan in any limited engagement. The May trap complicates that assumption. PAF demonstrated that a qualitatively asymmetric force, operating a smaller but tighter integration stack, can achieve tactical surprise and inflict disproportionate losses on a numerically and technologically superior adversary in the opening hours of a conflict. That window, even if subsequently closed by deeper Indian strikes, is precisely the window in which crisis decision-making takes place under nuclear-shadowed conditions.
For Pakistan, the engagement validates a long-standing strategy of qualitative asymmetry through Sino-Pakistani interoperability. For India, it should accelerate a reckoning long under way in New Delhi, namely that the era in which acquiring premium Western platforms substitutes for sovereign integration capability is closing. The trap that India walked into on 7 May was not a tactical accident. It was the operational expression of a structural condition that Indian procurement, doctrine, and inter-service organisation had not yet adapted to address. How quickly New Delhi closes that adaptation gap will determine whether the next crisis presents a similar trap or one that has evolved further still.
Conclusion
Strategic surprise occurs when an adversary changes the rules of the game in ways the targeted state has not theorised about. On the night of 7 May 2025, Pakistan changed the rules. It presented the IAF not with a better aircraft or a better missile but with a better-integrated combat ecosystem operating to a doctrine the IAF had not credited it with possessing. The trap consisted of a radar-silent J-10CE shooter cued by an offboard Erieye sensor over a Pakistani datalink, employing a missile whose true engagement envelope Indian intelligence had underestimated, in an EW environment whose density Indian planning had not anticipated. Each element was individually visible in open source. The trap lay in their combination and in the operational fluency with which PAF executed that combination under conditions of contested airspace. India entered the engagement expecting a platform contest and discovered, within hours, that it had walked into an architecture contest it was structurally unprepared for.
The institutional response now under way in New Delhi, from the Rafale source-code dispute to the IACCS–Akashteer integration push to the unresolved theatre-command debate, is the visible measure of how seriously the trap has been taken. Whether that response moves fast enough, and whether it addresses the offensive integration gap as well as the defensive one, will shape the South Asian deterrence environment for the next decade. The platforms India has acquired are world-class. The architecture in which they operate is not yet of the same standard. Until that gap closes, the trap will remain available to be walked into again.
Dr Tahir Mahmood Azad is Executive Director of London Dialogue, an independent UK-based research and policy institute. He can be reached at [email protected]
Tahir Azad
Related posts
The Maritime Blockade and the Strategic Calculus of the U.S., Iran, and Israel Toward a Renewed Armed Confrontation
Understanding Asim Munir’s Doctrine: Regime Security in Place of a National Goal
The Data Dilemma: Navigating the AI Systems Matrix
The Anatomy of a Shortfall: Europe’s Nine Capability Areas and the Lessons for Pakistan
From Quiet Diplomacy to Attempted Maritime Security Governance: Oman’s Role and Limits in the 2026 Strait of Hormuz Crisis
Anatomy of Asymmetry: How a Weaker State Converts Vulnerability into Leverage
Integration for Stability: The SDF’s Dissolution and Syria’s Security Order
The Western Flank Unravelled: Cross-Border Militancy, TTP Resurgence, and Afghan Taliban Governance
The Time of Guards Tank Divisions is Gone, or Maybe It is Not?
Re-pricing Israel’s Corridor: The Mecca Alliance and IMEC
The SCO at 25: From Regional Security Mechanism to Platform for a Multipolar Eurasia
Imran Khan: The Last Hope of a Nation
