India’s ambitious push toward technical sovereignty in defense production is increasingly facing roadblocks with the limits of Transfer of Technology (ToT) agreements, as supplier states are reluctant to negotiate sensitive technologies. Recently, despite the proposed acquisition plans for 114 multirole fighter aircraft for the Indian Air Force and another purchase order of 26 Dassault Rafale Marine Jets for the Indian Navy in 2025, France has reportedly refused to grant access to the critical Interface Control Document (ICD) for the Rafale jets, citing security concerns. The issue has escalated to the point that India has indicated to walk away from the proposed $43 billion deal.
The ICD is considered indispensable to operating an aircraft, as the interface controls communication and data exchange between radars, sensors, avionics, and mission systems. Without access to the ICD, India’s ability to tailor and integrate electronic warfare (EW) systems, indigenous weapons, and mission-specific upgrades remain constrained, limiting its ability to operate the aircraft only within original equipment manufacturer (OEM), approved parameters.
India has relied on ToT agreements to boost its defense production capabilities since the 1960s and 1970s. New Delhi is aware of the inherently restrictive nature of such agreements. They typically are accompanied by constraints on the type and duration of use, and on research and development (R&D), often obligating the buyer to procure materials and parts exclusively from the seller, and sometimes imposing price controls.
Additionally, many ToT agreements include a grant-back provision requiring the buyer to transfer any further improvements and inventions to the seller. Critical technologies – such as source code, mission-systems architecture, radar algorithms, EW databases, and advanced command and control architecture – are usually excluded from ToT agreements.
So why is India still pressuring for the ICD of the Rafale aircraft?
The ICD governs interoperability, exchange, and communication of data between components in an aircraft. It is sensitive but different from core critical technologies. If the layers of technological levels of a modern combat aircraft are to be analyzed, the ICD can then be categorized as moderately sensitive. Layer 1 is user operation and training; Layer 2 includes maintenance and repair; Layer 3 involves interface integration and interoperability mechanisms (such as the ICD); Layer 4 is subsystem modifications and customization; and Layer 5 is the very core technologies, such as source code, radar algorithms, EW database, and propulsion technology. They constitute some of the aircraft’s most sensitive intellectual property and remain highly restricted.
ICDs are by no means trivial, as access to them might allow buyers to infer integration logic, system engineering, and subsystem relationships. It is precisely why they are so selectively released and controlled with strict contracts. But that does not make the ICD itself a core critical technology.
India does not expect Rafale’s core intellectual property, source code, or software designs. It rather seeks limited interface-level access that would allow it more autonomy in indigenous weapon integration, upgradation, and mission customization. Modern weapon systems are incomplete without access to software controls. The mere import of hardware platforms does not add anything without some degree of control over software architecture, interoperability, and indigenous systems integration.
There have been instances in which suppliers have provided sufficient interface-level access, enabling buyers to exercise autonomy over interoperability and customization. India has previously managed to negotiate substantial interface-level access in the Sukhoi Su-30MKI, allowing it to integrate Israeli avionics, the BrahMos and Astra missiles, and indigenously developed EW systems and mission computers onto the aircraft. Similarly, South Korea, under the KF-16 program, was able to incorporate substantial indigenous weapons, mission systems, and avionics into the customized domestic production of F-16s – in practical terms, connoting ICD-level access – while the United States continued to protect sensitive radar codes, EW databases, and advanced engine technologies.
As France seeks to establish itself as a more flexible strategic partner, its willingness to negotiate on sensitive topics like ICDs could give it a stronger edge, enabling it to compete more successfully in the global market. Reportedly, the United Arab Emirates has also sought greater flexibility on software access and integration rights in its defense engagement with France.
But even with success in ICD-related negotiations over the Rafale aircraft, India needs to ramp up its technological absorption capability, in which it still lags far behind. Access to the Rafale’s ICD will imbue India with deeper technological know-how in avionics, sensors, weapon systems and integration, mission computers, and communication systems. It will further build indigenous expertise in system integration, software adaptation, platform updates, and modifications, paving the way for the design of more sophisticated indigenous platforms in the future.
But as the record shows, India has struggled to gain an edge in system design or innovation and has been constrained in manufacturing, maintenance, and assembly. Its failure to build the indigenous powerful aircraft engine Kaveri is a case in point. Despite experience with such advanced propulsion technologies, India failed to emulate them. The program encountered significant problems in perfecting “hot section” technologies, which include single-crystal turbine blades, thermal barrier coatings, and advanced cooling systems – factors that decide an engine’s life cycle, its performance, and longevity.
India’s experience with the Sukhoi Su-30MKI has also been somewhat similar. India possessed an initial license to assemble, manufacture, and maintain the Su-30MKI domestically, to grasp the technical know-how, design, and achieve autonomy in upgrades and maintenance in the long run. But despite the existing agreement, India could not access the full design and technological know-how.
Russia’s UEC NPO Saturn supplied engines, while India had to face persistent issues with short life and frequent replacements of parts. With no authority to redesign or update the engines, India continues to rely on Russia for spare parts and components. Integrating major new systems like radars, avionics, or weapons also requires prior Russian cooperation, limiting operational autonomy.
The lack of investment in R&D, emphasis on and over-reliance on licensed production rather than innovation, a focus on self-reliance over export competitiveness, and the deferred entry of private players into its defense ecosystem have plagued India’s technology absorption capability. The much-wanted ICD access for the Rafale should be seen as an important learning point toward achieving genuine technological know-how and eventual self-reliance.
