Current Affairs Topics Archive
International Relations Economics Polity & Governance Environment & Ecology Science & Technology Internal Security Geography Social Issues Art & Culture Modern History

On India’s fighter jet acquisitions

March 03, 2026 5 min read Internal Security Science & Technology International Relations GS Paper 2 (International Relations) GS Paper 3 (Internal Security Science & Technology)
On This Page ▼

What Happened

  • India's Defence Acquisition Council (DAC) on February 12, 2026 accorded an Acceptance of Necessity (AoN) for 114 additional Rafale jets under the Multi-Role Fighter Aircraft (MRFA) program — India's largest ever defence acquisition worth approximately ₹3.25 lakh crore ($39–43 billion).
  • Of the 114 jets, 18 will be delivered in flyaway condition and 96 will be assembled in India, with significant indigenous content requirements.
  • The proposal now moves to the Cabinet Committee on Security (CCS), headed by the Prime Minister, for final approval.
  • India's Defence Secretary Rajesh Kumar Singh confirmed that India will push for access to Interface Control Documents (ICDs) — or, as an alternative, API-level access to mission software — so Indian weapons such as the Astra BVR missile and Rudram anti-radiation missile can be integrated on the Rafale platform.
  • Full access to proprietary source code (for radar and electronic warfare systems) is understood to be off the table; India's negotiated fallback position is API/ICD access that allows independent development and integration of mission software components.
  • The deal was announced ahead of French President Emmanuel Macron's visit to India on February 17, 2026.
  • The Indian Air Force currently operates 36 Rafale jets (F3R variant) acquired in 2016; the new fleet will be the more advanced F4 variant, with contractual options to upgrade to F5 standards.
  • Tata Advanced Systems and Dassault Aviation have already agreed to produce Rafale fuselage components in Hyderabad — the first Rafale production outside France.

Static Topic Bridges

India's Defence Procurement Process: DAC → CCS

Defence acquisitions in India follow a multi-stage approval architecture set out under the Defence Acquisition Procedure (DAP 2020), which replaced the Defence Procurement Procedure (DPP 2016). The process moves from the Defence Acquisition Council (DAC) — chaired by the Defence Minister — issuing an Acceptance of Necessity (AoN), through categorization (Make in India vs. foreign procurement), to final approval by the Cabinet Committee on Security (CCS) chaired by the Prime Minister. The DAC includes the Chiefs of Staff of all three services, the Chief of Defence Staff, and senior secretaries.

  • DAC issues AoN: gateway for any procurement project to move to tendering/negotiations
  • CCS is the apex body for national security decisions; it approves proposals above a threshold value
  • DAP 2020 introduced new categories: "Make-I" (government-funded indigenization), "Make-II" (industry-funded), and "IDDM" (Indigenously Designed, Developed and Manufactured) to prioritize Atmanirbhar Bharat
  • For strategic assets above a certain value, inter-governmental agreements (IGA) between states can bypass standard tendering (as with the original 2016 Rafale deal)
  • The MRFA program, being India's largest acquisition, required CCS-level sanction after DAC AoN

Connection to this news: The DAC's AoN on February 12, 2026 is the formal entry point into the procurement chain; the proposal now awaits CCS approval before government-to-government negotiations with France begin in earnest.

Make in India in Defence: Strategic Autonomy and Technology Transfer

The "Make in India" initiative, launched in 2014, has a specific defence manufacturing track aimed at reducing India's position as the world's largest arms importer. The Defence Acquisition Procedure 2020 mandated minimum indigenization thresholds, created a Positive Indigenization List (PIL) restricting import of 310+ defence items, and promoted strategic partnerships with global OEMs for technology transfer. India's defence exports grew from ₹686 crore in 2013-14 to over ₹21,000 crore in 2023-24, and the government targets ₹50,000 crore in defence exports by 2028-29.

  • iDEX (Innovations for Defence Excellence), launched in 2018, funds startups working on defence technologies
  • Defence Industrial Corridors announced in Uttar Pradesh and Tamil Nadu for manufacturing clusters
  • The MRFA deal structure — 18 flyaway, 96 assembled in India — mirrors the "strategic partnership" model outlined in DAP 2020
  • For the Rafale deal, Dassault and Tata Advanced Systems have agreed to manufacture fuselage components in Hyderabad — first Rafale production outside France
  • Minimum Indian content thresholds in the contract are a key negotiating condition alongside ICD access

Connection to this news: The demand for weapons integration autonomy (Astra, Rudram on Rafale) represents the qualitative leap beyond "screwdriver assembly" — India seeks mission software sovereignty, not just hardware production.

Mission Software Sovereignty and the Source Code Debate

Mission software in a fourth-generation-plus fighter jet controls radar management, electronic warfare, weapons release, sensor fusion, and communications. The source code to this software is among the most closely guarded national security assets of any arms-exporting country. The tension between arms sellers (who protect IP) and buyers (who need operational flexibility) is a recurring feature of modern defence procurement. India's experience with earlier platforms — the Su-30MKI, for instance — shows the risk of vendor lock-in when integration capabilities are not transferred.

  • Interface Control Documents (ICDs) define the software interfaces and data protocols needed to plug external systems (weapons, sensors) into the platform — a middle-ground solution short of full source code
  • API-level access allows India to develop its own software modules compatible with Rafale systems without accessing the core source code
  • Astra Mk-1 BVR missile (DRDO-developed, range ~100 km) and Rudram anti-radiation missiles are high-priority for Rafale integration
  • France's position: full source code unlikely; ICD access under negotiation
  • Historical parallel: In the original 36-jet Rafale deal (2016), India secured maintenance and logistical independence but not full software integration rights

Connection to this news: The article's core argument is that access to mission software and weapons integration autonomy is the true measure of whether this deal advances India's defense indigenization goals or merely expands the fleet under continued strategic dependence.

Key Facts & Data

  • Deal size: ₹3.25–3.6 lakh crore (~$39–43 billion); India's largest-ever defence acquisition
  • Composition: 18 flyaway (F4 variant) + 96 assembled in India; option to upgrade to F5
  • Existing fleet: 36 Rafale F3R jets delivered under the 2016 inter-governmental agreement
  • DAC AoN: February 12, 2026; next stage — CCS approval
  • Macron visit: February 17, 2026 (coincided with deal announcement)
  • Indian weapons sought for integration: Astra BVR (DRDO), Rudram anti-radiation missile (DRDO)
  • India's negotiating ask: Interface Control Documents (ICDs) or API-level mission software access
  • Co-production: Tata Advanced Systems + Dassault — fuselage components in Hyderabad
  • India's current IAF squadron strength is below the sanctioned 42 squadrons (operating ~30)
  • Defence exports grew from ₹686 crore (2013-14) to ₹21,083 crore (2023-24)
  • DAP 2020 Positive Indigenization List: 310+ items banned from import