Introduction

The Defence Acquisition Council’s clearance of 114 additional Rafale fighters is being discussed as a procurement milestone. It is that. But it is also something larger.

When a fleet crosses a certain scale, it stops being a transaction and becomes infrastructure. It reshapes training pipelines, industrial partnerships, maintenance budgets and doctrinal assumptions. It creates comfort. And comfort changes incentives.

This three-part series argues that the Rafale expansion should not be framed as a debate over aircraft quality or price. The deeper issue is structural. What does this moment mean for AMCA? For India’s engine ambitions? For integration authority over software, sensors and weapons? For the long-term direction of the aerospace ecosystem?

Part I examines how fleet mass alters timelines and why delay, not cancellation, is the real strategic risk for AMCA.

Part II moves beneath localisation percentages to the harder question of configuration control and integration authority.

Part III turns to propulsion — the Safran partnership, the Rolls-Royce alternative, and the revival of Kaveri — and asks whether engines are finally being treated as a national mission rather than a platform add-on.

The series asks a simple but uncomfortable question: Is Rafale a bridge to sovereign aerospace capability — or another comfort zone?

In aerospace, delays compound. So does dependence. This decade will decide whether India breaks out — or drifts back into delay and dependence

Thanks for reading Sudhir Pillai's Notes on Strategy, Policy and Operations! This post is public so feel free to share it.

Part 1

From Procurement Event to Ecosystem Decision

The Defence Acquisition Council’s (DAC) clearance of 114 additional Rafale fighters is being discussed as a procurement milestone. It is that. But it is also something larger.

Some see it primarily through an operational lens — a necessary step to rebuild squadron strength and restore credible air power. Others read it as a quiet retreat from the indigenous aerospace path India has championed over the past decade. This essay examines both tracks to ask whether they lead to a common destination.

This decision, coupled with the 36 Rafales already in service and 26 Rafale-M on order for the Indian Navy, pushes the Rafale family toward a 150‑plus fleet that will shape India’s air combat architecture well into the 2040s. French and Indian reporting suggest that the Navy is even considering an additional 31 Rafale‑M beyond the 26 already contracted, though that has not been formally approved. At this scale, Rafale stops being a deal and becomes infrastructure.

Official language reflects this shift. The Acceptance of Necessity (AON) note describes the Multi‑Role Fighter Aircraft (MRFA) package as central to securing “air superiority across the full spectrum of conflict” and enhancing long‑range strike capability, while emphasising that most aircraft will be built in India under a high‑value manufacturing programme. The headline number — ₹3.6 lakh crore for jets, missiles and associated systems — is dramatic. But it still understates the real weight of the decision.

The revenue tail of a fleet this size will run for decades. What has been cleared is not only a capital purchase; it is a commitment to an industrial and logistical spine.

This essay does not revisit whether Rafale is a good aircraft or whether India should have chosen something else. Rafale is combat‑credible and has repeatedly prevailed in Indian evaluations. Nor is this a simple cost critique. Modern multi‑role fighters are expensive everywhere. Sticker prices may shock, but strategy ultimately sits above sticker shock.

The real question is institutional: does this Rafale expansion become a bridge to sovereign design depth, or does it quietly become the destination?

If Rafale settles in as the comfortable endpoint, the Advanced Medium Combat Aircraft (AMCA) risks becoming a perpetual laboratory — worthy, ambitious, but always one budget cycle away from full priority.

If Rafale is deliberately structured as a bridge, the same decision can accelerate India’s aerospace ecosystem — engines, sensors, software and integration capacity.

The answer lies not in the aircraft itself but in the ecosystem wrapped around it. Fleet size creates strategic gravity. Integration authority over avionics, weapons and software is national power. Engine design and life‑cycle structures determine whether revenue budgets strengthen foreign balance sheets or indigenous capability. How Kaveri’s revival and the AMCA–Safran engine partnership are handled will reveal whether India is content to assemble imported cores or intends to own propulsion design.

Rafale MRFA reshapes the AMCA timeline less by replacing it than by narrowing the window in which AMCA must move from paper to production before it is quietly deprioritised.

How Rafale MRFA Impacts the AMCA Development Timeline

The first hard constraint is arithmetic. As of the mid‑2020s, the IAF fields around 29–31 fighter squadrons against a sanctioned strength of 42, with official and semi‑official projections that even if Tejas Mk1A, Tejas Mk2 and MRFA acquisitions all run broadly on schedule, India will reach only about 35–36 squadrons by 2035. Over this same period, multiple legacy fleets—MiG‑21, Jaguars, MiG‑29UPG and eventually Mirage‑2000—will retire in phases, creating a rolling deficit that Rafale MRFA is explicitly meant to stabilise rather than fully close. That means Rafale is structurally locked in as the principal 4.5‑generation workhorse of the 2030s, not a short‑term patch.

AMCA’s declared schedule now sits directly inside this Rafale‑dominated decade. The Defence Ministry’s AMCA execution model and DRDO leadership statements put prototype roll‑out around 2028–29, first flight in 2029, and induction and series production beginning roughly 2033–35. The Air Chief has publicly echoed this, stating that AMCA’s first flight is expected in 2028 and that induction is targeted for 2035, aligning the programme’s trajectory with the IAF’s long‑term modernisation plans. In other words, AMCA must make the transition from prototype to production precisely as Rafale numbers ramp up and Tejas Mk1A/Mk2 production lines are at full stretch, delivering over 200 indigenous 4+/4.5‑generation fighters by the early‑mid 2030s.

This overlap cuts both ways. On the positive side, a stabilised Rafale‑Tejas force mix gives the IAF operational breathing space to accept the inevitable teething troubles of a first‑generation stealth design, much as Su‑30MKI and Mirage‑2000 fleets bought time for Tejas. Combined with Tejas Mk2’s planned entry around 2029 and its 120‑aircraft tranche by 2034, Rafale MRFA can help prevent AMCA from being burdened with the impossible task of repairing squadron strength and closing the technology gap simultaneously. But the same comfort is also the core risk. Once the Rafale pipeline is flowing and Tejas Mk1A/Mk2 are in bulk production, there will be strong bureaucratic and financial incentives to slip AMCA milestones “just a little” to ease cash‑flow and avoid operational disruption.

The danger is not that AMCA will be cancelled. It is that it becomes the default shock absorber. When MRFA overruns, when Tejas production slips, when some other capital priority demands accommodation, AMCA will be the programme that is easiest to “adjust”. A year here. Two years there. A milestone quietly deferred to smooth cash flow or reduce risk. In aerospace, that is not harmless.

Every year AMCA’s first flight moves beyond the 2028–29 window, and every year induction slips beyond the mid-2030s target, India could fall further behind the 5th-generation curve. Meanwhile, the PLAAF is not pausing. It is expanding stealth fleets and maturing the ISR and electronic warfare (EW) architecture that makes those aircraft effective.

Rafale MRFA, by stabilising squadron numbers through the 2030s, creates comfort. Comfort creates temptation. If operational pressure is eased, delay becomes politically manageable.

The real danger is not cancellation. It is drift.

AMCA will not vanish. It will stay in official slides and public statements. What changes is pace. A year added here. A milestone quietly moved there. Funds adjusted to ease pressure elsewhere. In aerospace, those small shifts add up. Lost time is lost capability.

Rafale MRFA gives India breathing room. That breathing room can be used to build the future, or it can make delay feel acceptable.

Which way this goes depends on decisions taken now. Protected funding. Clear milestones. Engine and subsystem contracts that cannot be dipped into whenever Rafale bills come due.

That is where the real story sits.

In the next part, I step away from timelines and look at structure: what “Make in India” really means in this deal, why assembly alone is not capability, and why integration authority will determine whether Rafale becomes a bridge to AMCA or a comfortable destination.