Rafale MRFA will only deepen India’s aerospace base if the “Make in India” push is framed around design and integration rights, not just percentage localisation and a new assembly line.

Part 2
Rafale Assembly Is Not Capability Acquisition

What India Must Get Right for Her Aerospace Ecosystem

Public signalling on MRFA is dominated by localisation numbers. The Defence Secretary has said the “Made‑in‑India” Rafales will aim for roughly 40–50% indigenous content, with Dassault initially proposing about 40% and India pushing toward 50% or more. The broad contours now envisage around 18 aircraft in fly‑away condition, with the remaining ~90 to be built in India, with final assembly at the Dassault Reliance Aerospace Limited (DRAL) Nagpur facility and a wider supplier base including Tata, Mahindra, Dynamatic, and several dozen other firms. Local assembly of this scale does matter for jobs, supply‑chain resilience and some elements of industrial learning, especially if the Nagpur line eventually feeds global Rafale demand as a second production hub. But by itself, screwdriver work and structural fabrication do not turn India into an aerospace power; at best, they create a high‑value workshop for someone else’s design.

The real structural questions are harder, and they sit largely below the current public debate.

First, configuration control: who ultimately sets and modifies the Rafale baseline that India flies? The MRFA framework is being cast as a government‑to‑government deal, with New Delhi stressing “sovereign authority to integrate its own weapons and systems” as a cornerstone. That language is important, but configuration control goes beyond weapon hardpoints. It includes the right to alter mission software, avionics architectures, EW configuration and cockpit systems on Indian timelines, for Indian requirements, without waiting indefinitely on OEM priorities. If those rights are not clearly written into the contract, we risk a strange outcome: Rafales rolling out of Nagpur, but every meaningful change to their software, sensors or systems still needing a green light from Paris.

Second, weapons integration: The Defence Secretary has suggested that the MRFA structure will allow India to integrate its own weapons, clearly a response to past experiences where foreign OEMs controlled the pace and cost of adding Indian munitions. For Rafale to function as a bridge, India needs more than permission to bolt on a few indigenous missiles. It needs the authority and technical access to run full weapons integration campaigns—data packages, interface control documents, captive‑carry trials, separation tests, software updates—through an Indian‑led team, drawing on DRDO, IAF and industry. Without this, Rafale becomes another premium platform whose most critical combat parameters are effectively outsourced.

Third, engine sustainment and upgrade possibilities: MRFA will lock India into Safran’s M88 ecosystem for decades, just as Su‑30MKI tied the IAF to Russian engine and spares pipelines. Dassault and Safran are already moving to set up Rafale MRO in India, and there is talk of expanding local workshare over time. The question is whether this remains high‑end maintenance under French design authority, or whether India can progressively move into component‑level overhaul, hot‑section work, and eventually design input for life‑extension and performance upgrades. If the AMCA–Safran engine partnership and Kaveri derivative work are structurally linked to M88 sustainment in India, the Rafale engine line could become a live classroom feeding indigenous propulsion competence; if not, it risks being a parallel, fenced‑off revenue stream that does little for AMCA.

All of this is supposed to sit under India’s Strategic Partnership (SP) model, which, in theory, forges long‑term ties between the MoD, a foreign OEM and an Indian prime responsible for manufacture, life‑cycle support and upgrades. On paper, SP is meant to provide exactly what India has lacked: a clear allocation of responsibility, risk, and liability across design, production, and sustainment. In practice, the danger is “industrial ambiguity”: a situation where the foreign OEM quietly retains real design and integration authority, the Indian partner is treated as an advanced fabricator and assembler, and no one is clearly accountable when upgrades stall or availability suffers.

If the MRFA contract does not define configuration control, weapons‑integration rights and engine sustainment life cycles with precision and enforceable liability, India will once again have created a large, expensive fighter ecosystem without building the design authority that AMCA and Kaveri actually require.

Rafale MRFA will only serve as a bridge to sovereignty if India insists on real integration authority, learns from Vikramaditya and Vikrant, and deliberately uses Rafale upgrades as a test bed for Indian sensors and weapons.

Integration Authority as National Power

India’s carrier experience captures the difference between buying a package and owning a platform. INS Vikramaditya began life as the Soviet Baku (later renamed Admiral Gorshkov after the breakup of the USSR ) and was acquired as a largely Russian‑defined package, with an extensive refit at Sevmash that ran into major delays and cost escalation, and left India structurally dependent on Russian design houses and yards for many upgrades and deep refits.

Vikrant, by contrast, was designed by the Indian Navy’s own recently renamed Warship Design Bureau (earlier the Directorate of Naval Design) and built at Cochin Shipyard, with a very high share of indigenous equipment and a domestic design loop that now allows India to plan refits, modernisations and future carrier classes on its own terms. In both cases, foreign technology and components remain important, but the contrast is stark: in one, India is essentially a client of someone else’s architecture; in the other, it is the platform architect who chooses what to integrate, when, and at what risk.

The fighter ecosystem is now at a similar fork. Rafale comes as a tightly optimised “system of systems,” with the RBE2 radar, Spectra EW suite and French‑curated weapons and software forming an integrated package. Indian “India‑specific enhancements” on the first 36 aircraft did push the envelope—additional EW features, bespoke communications and some Indian elements were integrated, with HAL taking on local work for part of the upgrade kit. But recent reporting on attempts to integrate the indigenous Uttam AESA radar onto Rafale M and French reluctance to allow it on carrier-borne aircraft underscores the risk of remaining trapped in a closed architecture in which the OEM ultimately decides which Indian systems can be added. Without a shift in the contractual and technical balance of power, Rafale may repeat the Vikramaditya pattern: India operates and maintains an advanced foreign platform, but key upgrades remain hostage to external gatekeepers.

For Rafale to become a genuine bridge, India must structure MRFA and follow‑on contracts around explicit integration authority. After the Cabinet Committee of Security approval, the Cost & Contract Negotiation will follow. It is at this stage that India needs to hold its own as a buyer. That means writing into the baseline that a defined subset of Rafale mid‑life upgrades—especially for radar, EW and weapons—will be Indian‑led, with Dassault and Safran in supporting roles. It also means securing access to the data packages, interface control documents, and software hooks required for DRDO, IAF, and Indian industry to run full integration campaigns for systems such as Uttam derivatives, Indian EW pods, and indigenous stand‑off weapons. This is not about excluding foreign kit; it is about ensuring that when India wants to change the “nervous system” of its primary fighter in response to Chinese and Pakistani counters, it can do so on Indian timelines and budgets. Integration authority, in this sense, is national power: it determines whether Rafale’s evolution over the next 30 years serves as a ladder into AMCA‑class design and integration competence, or whether it locks India into another long‑term package dependency dressed in localisation rhetoric.

But even the integration authority is not the deepest layer. The heart of aerospace sovereignty sits elsewhere — in propulsion. And that is where the real strategic test now lies.

You can own the radar interface. You can lead weapons integration. You can negotiate software access and mid-life upgrades. And still remain dependent. Because the real centre of gravity in a modern combat aircraft is not only its sensors or its code. It is its engine.

Propulsion determines thrust margins, growth potential, range, payload, thermal signature and upgrade headroom. It dictates how far a design can evolve before it hits hard physical limits. It anchors the life-cycle cost curve for decades. And it is the one domain where genuine design ownership has historically been guarded most tightly by the handful of countries that possess it.

If Rafale integration authority concerns who controls the nervous system, propulsion concerns who controls the heart.

India’s aerospace story has long stumbled at this point. Licensed manufacturer without core design ownership. Assembly without hot-section mastery. Maintenance capability without materials science sovereignty.

That is why the AMCA–Safran partnership, the parallel Rolls-Royce offer, and the revival of Kaveri are not side stories. They are the story.

Because once a nation decides who designs, certifies and upgrades its fighter engine, it has effectively decided whether it is climbing the aerospace ladder — or renting space on someone else’s.

Part III turns to that question. Engines are not a procurement sub-clause, but a strategy.