The Engine Problem: Why India Still Can't Build Its Own Fighter Jet Engine — And What It Will Take to Fix ItFor a country that builds nuclear submarines, flies its own sata tie-up.

AMCA Round Neck Tee

₹999.00

Buy Now

For a country that builds nuclear submarines, flies its own satellites to Mars, and is developing a fifth-generation stealth fighter, there is one piece of hardware that has consistently eluded India: a fighter-class jet engine. It is, by common consensus among defence planners, the single toughest technology gap left in India's quest for military self-reliance — tougher than missiles, tougher than radars, arguably tougher than the atom bomb.

The story of that gap has a name: Kaveri.

A 37-Year Journey That Still Hasn't Landed

The GTRE GTX-35VS Kaveri programme was sanctioned in 1986 to power the Tejas Light Combat Aircraft. Four decades, thousands of crores of rupees, and several redesigns later, Kaveri has never powered an operational fighter. It was officially delinked from the Tejas programme in 2008 after failing to deliver the thrust and reliability a frontline jet needs, forcing India to rely on the American GE F404 (and now F414) engines instead.

That's not the end of the story, though — it's the mid-point. The knowledge, metallurgy, and test infrastructure built over those years didn't disappear; they've been repurposed. The Kaveri Derivative Engine (KDE), a "dry" (non-afterburning) 48–52 kN variant, is now being certified to power the DRDO Ghatak stealth UCAV, with certification targeted for 2026. Godrej Aerospace has already delivered the first production-standard unit. Meanwhile, GTRE is chasing a more ambitious "Kaveri 2.0" — an afterburning derivative in the 80–90 kN range — with a maiden flight test hoped for 2026–27 and production clearance eyed for around 2031.

In February 2026, Defence Minister personally watched a full afterburner test of the upgraded Kaveri configuration at GTRE in Bengaluru — a genuine milestone, and one that used afterburner components developed with help from BrahMos Aerospace. But even Singh was candid about the scale of the challenge, reportedly telling scientists that India has only "five to seven years" to develop a truly sovereign engine, and that the country cannot stop at fifth-generation propulsion — it needs to start thinking about the sixth generation now.

Why an Engine Is So Much Harder Than an Airframe

People outside the aerospace world are often surprised that India can design a fairly capable airframe (Tejas) but can't design the engine that powers it. The reasons are structural, not just budgetary:

1. Metallurgy at the edge of physics. A modern fighter engine's turbine blades spin at tens of thousands of RPM inside gas temperatures that exceed the melting point of the alloys they're made from. This is only possible because of single-crystal casting and directionally solidified superalloys — materials science so specialised that only a handful of countries (the US, UK, France, Russia) have fully mastered it end-to-end. India's Defence Metallurgical Research Laboratory made a real breakthrough here in 2021 with single-crystal casting and near-isothermal forging for compressor discs, but scaling this from lab success to reliable mass production is a different order of difficulty.

2. Thrust-to-weight ratio. It isn't enough to generate thrust — an engine has to generate it while staying light. The current Kaveri sits around 1,180 kg, heavier than competing engines in its thrust class, which eats directly into a fighter's payload and performance. Shedding that weight without compromising structural integrity is one of GTRE's most persistent headaches.

3. Test infrastructure. Altitude testing, flying test-beds, and high-cycle fatigue trials require facilities India historically didn't have in-house — Kaveri's altitude testing was done in Russia (Gromov Flight Research Institute) and later at Russia's CIAM in Moscow. Not owning this infrastructure means every test cycle involves geopolitics, cost, and delay layered on top of engineering.

4. Technology-denial regimes. Post-1998 Pokhran sanctions cut India off from critical alloys and test access exactly when the Kaveri programme needed them most. Even friendly technology transfers from foreign OEMs have historically been shallow — GTRE's collaboration with France's Snecma (now Safran) in the 2000s collapsed after India accused the French side of transferring only non-critical technology.

5. Institutional and industrial fragmentation. GTRE (design), HAL (production/integration), private players like Godrej Aerospace and Azad Engineering (manufacturing), and the DRDO metallurgy labs all have to move in lockstep over a 15–20 year development cycle — a coordination problem as much as a technical one. Critics have long argued that HAL's monopoly position as India's sole state aircraft-maker has slowed the broader ecosystem, and that private industry has been under-utilised.

6. The funding-versus-patience mismatch. Engine programmes elsewhere routinely take 20–30 years and tens of billions of dollars (the US F135 programme, for instance). India has historically funded Kaveri in fits and starts, with each funding gap costing years of momentum — and each delay adds pressure on the IAF, which needs engines now, not in the 2030s.

The Immediate Cost: An Air Force Running Short of Engines

This isn't an abstract technology debate for the IAF — it's an operational crisis. GE has repeatedly delayed deliveries of F404-IN20 engines for the Tejas Mk1A, forcing India to impose penalties and pushing squadron induction timelines further into 2026. With IAF squadron strength already well below its sanctioned 42-squadron requirement, every delayed engine delivery translates directly into fewer jets in service. The Tejas Mk2 and the twin-engine AMCA depend on the GE F414, whose delivery and technology-transfer terms remain a live negotiating issue. In short: India's fighter fleet modernisation is currently hostage to a supply chain it doesn't control.

What the Solution Actually Looks Like

Nobody serious in India's defence establishment believes Kaveri alone will produce a 110–120 kN engine for the AMCA on its own steam within a useful timeframe. The emerging consensus, reflected in recent GTRE moves, is a three-track strategy:

Track 1 — Finish what Kaveri can realistically finish. Certify the KDE for the Ghatak UCAV and push Kaveri 2.0 as a mid-thrust option, potentially for Tejas Mk1A life-extension. This keeps the domestic knowledge base alive and gives India a fallback that isn't hostage to any foreign supplier.

Track 2 — Co-develop the big-thrust engine with a foreign partner, but insist on real technology transfer and IP ownership. This is the track that matters most for the AMCA and any future sixth-generation fighter, and it's where the "which country can help" question gets answered.

Track 3 — Build sovereign industrial capacity in parallel, not after the fact: a full-scale altitude test facility on Indian soil, a domestic titanium/superalloy supply chain (India's new titanium and superalloy plant in Lucknow, commissioned in October 2025, is a step in this direction), and private-sector production partners like Godrej Aerospace and Azad Engineering so GTRE isn't the sole bottleneck.

Which Country Can Actually Help?

This is where things have moved fastest in the last two years, and there are essentially three live options on the table.

France (Safran) — the frontrunner

Safran has been India's most consistent engine partner discussion since 2023, when talks began during President Macron's visit. India has reportedly secured IP rights for a 120 kN engine class built on M88-derived technology, and Safran is actively supporting GTRE's afterburner and hot-section work on Kaveri 2.0. The France option has momentum, an existing relationship, and lower geopolitical friction than the US route — but past experience (the Snecma technology-transfer dispute) means India is negotiating this round with much sharper eyes on what counts as "critical" technology.

The United Kingdom (Rolls-Royce) — the boldest offer

Rolls-Royce has put the most aggressive proposal on the table: a fully joint-designed, India-based 120kN+ engine programme with 100% technology transfer and all IP resting with the Indian government, positioning India as Rolls-Royce's fourth global propulsion hub after the UK, US, and Germany. If signed by end-2026, Rolls-Royce projects core testing by 2030, first flight by 2034, and series production by 2036. It's a compelling offer precisely because it addresses India's historic complaint — shallow tech transfer — head-on.

The United States (GE Aerospace) — the incumbent, but pricier and slower

GE remains the IAF's current engine supplier (F404/F414) and has a formal partnership including some F414 co-production for India, but recent cost escalations on GE's offer have reportedly strengthened the hand of the French and British bids. GE also carries the baggage of past supply-chain delays that have already hurt the IAF.

Russia — a quieter, longer-standing option

Russia's CIAM facility has supported Indian altitude testing for years, and Russia has offered engine cooperation in the past, but it isn't currently positioned as the lead partner for the AMCA-class engine — more a testing and legacy-support relationship than a co-development one.

GTRE's own January 2026 Expression of Interest for an indigenous Advanced High Thrust Class Aero Engine (AHTCE) — a 120 kN engine with FADEC, to be delivered as 18 units over ten years — explicitly allows Safran, Rolls-Royce, GE, or Japan's IHI to bid as design consultants, while insisting that design control stays with the Indian partner. That single clause is probably the most important sentence in India's engine strategy right now: after 40 years, India has learned that the deal that matters isn't "buy an engine" or even "assemble an engine" — it's "own the IP and the design authority," with a foreign partner brought in specifically to compress the learning curve.

The Bottom Line

India doesn't have an engine problem because its engineers can't do the science — DRDO's metallurgy breakthroughs and the KDE's progress toward certification prove otherwise. It has an engine problem because building a fighter-class turbofan from a standing start, without decades of institutional experience, foreign co-development, or a mature domestic supply chain, is genuinely one of the hardest sustained engineering efforts a nation can undertake — harder, in real terms, than building a nuclear weapon.

The realistic path forward isn't "Kaveri succeeds and replaces everything." It's a hybrid: Kaveri and its derivatives quietly power UCAVs and mid-thrust roles while a genuine, IP-respecting co-development deal — most likely with France or the UK — delivers the 110–120 kN engine the AMCA needs, backed by an Indian industrial base (private manufacturers, a domestic superalloy supply chain, and full-scale test infrastructure) sturdy enough that the next engine after that one can be built substantially at home.

If India signs and executes that deal well this time — with real technology transfer, not the token version it got from Snecma two decades ago — the 2030s could be the decade India finally closes its oldest defence-technology gap.

This piece reflects the publicly reported state of India's aero-engine programmes as of mid-2026. Programme timelines in this sector have historically slipped and should be read as current official projections rather than certainties.