Powering India's Fifth-Generation Ambition: AMCA, the Private Sector Gamble, and the Long Road to an Indigenous Engine

India's Advanced Medium Combat Aircraft (AMCA) programme is, without exaggeration, the most consequential aerospace project the country has ever attempted. It is also a project standing on two legs that have never been tested together before: a private sector that has never built a fighter jet, and an engine industry that has never fielded one. Understanding whether AMCA succeeds on schedule means understanding both problems — and why they are, in fact, the same problem viewed from two angles.

1. The AMCA Bet: Why HAL Was Sidelined

For over four decades, Hindustan Aeronautics Limited (HAL) was the only game in town for Indian fighter production — from licence-built MiG-21s and Su-30MKIs to the Tejas. That monopoly has now been broken, deliberately.

In February 2026, HAL was formally excluded from the race to build AMCA prototypes after its bid, submitted through a consortium with smaller private partners, failed to clear technical thresholds. Part of the disqualifying arithmetic was structural: the Defence Ministry's Expression of Interest stipulated that a bidder's existing order book could not exceed three times its annual turnover — and HAL's order book runs to roughly eight times its turnover. In other words, HAL is drowning in Tejas Mk1A, Su-30MKI upgrade, and overhaul work, and the government decided it could not also be trusted with the country's most complex fighter programme on top of that backlog.

Three consortia now remain in serious contention for the ₹15,000 crore prototype-development contract, which covers five flying prototypes and one structural test airframe:

- Tata Advanced Systems Limited, bidding independently

- L&T, teamed with defence PSU Bharat Electronics and aerospace parts maker Dynamatic Technologies

- Bharat Forge (Kalyani Group), teamed with BEML and Data Patterns

The winning consortium won't just build prototypes — it stands to become the anchor for series production of a fifth-generation stealth jet, a contract likely to dwarf even the ₹98,000 crore Tejas Mk1A order. A new 650-acre greenfield aerospace facility in Andhra Pradesh has been earmarked to host this work, with projections of roughly 7,500 direct jobs and downstream demand across metallurgy, composites, avionics and precision manufacturing.

2. The Private Sector's Real Challenge: Components vs. Systems Integration

This is where the optimism needs a dose of realism. Indian private firms have genuine and growing capability — Tata, L&T, Bharat Forge, Adani and others have built airframe sections, missile bodies, artillery systems, and precision components for both Indian and global primes for years. What none of them has done is act as the prime systems integrator on a manned, stealth, fifth-generation combat aircraft — a discipline that involves reconciling airframe, propulsion, sensor fusion, avionics, electronic warfare suites and software into a single flyable, certifiable, maintainable weapons system.

The gap isn't ambition or capital — India's private groups have both. It's **institutional experience with the failure modes unique to fighter development**: schedule slippage cascading from a single subsystem, weight-growth management across a stealth airframe, software integration testing at the scale a modern fighter requires, and the multi-decade sustainment and overhaul ecosystem that a fighter fleet demands long after rollout. HAL's own Tejas journey — repeated Final Operational Clearance delays, weapons-integration bottlenecks — illustrates how unforgiving this domain is even for an organisation with 80 years of aircraft-building history.

The government's implicit theory of the case is that competitive tension between three well-capitalised private consortia, working directly with the Aeronautical Development Agency (ADA) as design authority rather than through HAL as an intermediary, will produce better discipline than a single PSU monopoly ever did. That's a reasonable hypothesis. It is still a hypothesis, being tested for the first time on the country's most expensive and technically demanding aircraft programme.

3. The Engine Problem: Where Self-Reliance Actually Gets Hard

If systems integration is AMCA's private-sector risk, propulsion is its sovereignty risk — and it is the harder of the two problems by an order of magnitude. Jet engine design is widely considered among the most difficult engineering disciplines on Earth; fewer countries can build a competitive military turbofan than can build nuclear weapons.

Where Kaveri actually stands

The original Kaveri engine, under development by DRDO's Gas Turbine Research Establishment (GTRE) since the late 1980s, never reached the thrust or reliability levels needed for a manned fighter — it topped out around 49 kN dry thrust, well short of what even the Tejas Mk1 required, and a technology-transfer collaboration with France's Snecma collapsed decades ago over what GTRE viewed as minimal transfer of meaningful technology.

Rather than abandon the programme, GTRE pivoted it toward more achievable near-term goals:

- Kaveri Derivative Engine (KDE)— a dry (no afterburner) variant, in the 46–51 kN thrust class, aimed squarely at unmanned platforms like DRDO's Ghatak stealth UCAV rather than manned fighters. Godrej Aerospace delivered the first production-standard unit in September 2025, with further units and high-altitude trials (including tests on a Russian Il-76 flying testbed) targeting full certification later in 2026.

- Kaveri 2.0 — a more ambitious, lighter afterburning variant now being pursued with an eye toward roughly 55–59 kN dry and 95–98 kN wet thrust, potentially relevant to Tejas Mk1A's mid-life re-engining in the 2030s. A February 2026 afterburner test, using hardware developed with BrahMos Aerospace, demonstrated meaningful progress in the hot-section and afterburner design.

- A new high-thrust engine test facility at Rajanukunte is nearing completion (not built in a day obviously its decades of hard work), giving GTRE, for the first time, the domestic ground infrastructure to rub it

serious endurance and altitude trials without relying entirely on foreign test benches.

This is real, incremental progress — arguably the most credible phase the Kaveri lineage has had in 30 years. But it needs to be stated plainly: nothing in the current Kaveri family is close to the 110–130 kN thrust class that a twin-engine AMCA actually needs.** Kaveri's realistic near-term destiny is powering the Ghatak UCAV and eventually replacing the GE F404 in upgraded Tejas Mk1A jets — not powering AMCA.

What will actually power AMCA

For AMCA Mk1 — the initial production version — the decision has already been made: the GE F414-INS6, roughly 98 kN thrust, the same engine selected for Tejas Mk2/TEDBF. Negotiations between HAL, ADA and GE for co-production with roughly 80% indigenisation of manufacturing, assembly, testing and overhaul are well advanced, with first locally-built engines targeted for the late 2020s. Recent cost escalation from GE has complicated this picture and strengthened the hand of European competitors, but F414 remains the baseline engine for AMCA Mk1 prototypes and early production.

AMCA Mk2 is where indigenous ambition and hard engineering reality collide. This variant requires a clean-sheet 120 kN-plus class engine, and both Rolls-Royce and Safran have made serious, competing offers to co-develop it with GTRE — full technology transfer, Indian IP ownership, and joint design and manufacture on Indian soil, not licensed production of an existing foreign design. As of mid-2026, Safran's proposal was seen as the frontrunner for formal government clearance, though Rolls-Royce's more recent pitch — including a proposal to test the engine core by 2030 and target first flight by the mid-2030s if contracted before end-2026 — has reopened the competition given GE's cost pressure on the wider AMCA programme.

Even under the most optimistic of these timelines, industry sources and DRDO's own past experience point to 12–15 years as a realistic gestation period for a clean-sheet high-performance military turbofan. That timeline is why AMCA Mk2's induction, once pencilled in for the mid-2030s, is now more realistically being discussed for around 2040.

4. Can Kaveri Ever Power AMCA? An Honest Answer

Not in its current form, and not within any timeframe that matters for AMCA Mk1 or even Mk2's first squadrons. What Kaveri can do — and is plausibly on track to do — is:

1. Power the Ghatak UCAV via the KDE, giving India its first fully indigenous, certified gas-turbine aircraft engine, even if in an unmanned/dry-thrust role.

2. Re-engine Tejas Mk1A in the 2030s via Kaveri 2.0, displacing dependence on the GE F404 for at least one fighter type.

3. Seed the metallurgy, single-crystal blade casting, and hot-section technology base that any future high-thrust engine — indigenous or co-developed — will draw on. DRDO's Defence Metallurgical Research Laboratory has already transferred near-isothermal forging and single-crystal casting technology to Mishra Dhatu Nigam for production, which is a genuine sovereign capability gain regardless of which airframe eventually benefits.

Kaveri's real value to AMCA, in other words, is not as AMCA's engine — it's as the industrial and human-capital foundation that makes the next indigenous engine (post-Safran/Rolls-Royce collaboration) achievable on India's own terms rather than as a permanently license-dependent programme.

5. Which Country Can Actually Help — and On What Terms

The choice, as it stands in mid-2026, is essentially between two serious offers:

France (Safran): Deepest existing footprint in India already, through helicopter-engine manufacturing and the M88 engine used on Rafale, where Safran has separately signalled willingness to localise 40–60% of production to meet India's Rafale-order indigenous-content requirements. Safran's AMCA pitch centres on a 120–140 kN class engine, co-developed with GTRE, with full technology transfer including critical hot-section know-how and Indian ownership of the resulting IP. As of the most recent reporting, this partnership was closest to formal government clearance.

United Kingdom (Rolls-Royce): A more recently sharpened pitch, explicitly framed as a joint-design, joint-manufacture programme entirely on Indian soil for a 120 kN-plus engine, with an aggressive (if optimistic) schedule promising core testing by 2030. Rolls-Royce has also signalled interest in involving India directly in sixth-generation, variable-cycle engine technology — a further-out but strategically attractive proposition if India wants to avoid falling a full generation behind on adaptive-cycle propulsion.

Russia remains a background option — mainly discussed informally around the Su-57's Product 30 (izdeliye 177S) engine — but has not produced a comparable formal technology-transfer offer for AMCA and carries its own geopolitical and sanctions-exposure baggage for a programme India wants to keep export-market-friendly.

The United States (GE) remains the incumbent supplier for AMCA Mk1 via the F414, but is not seriously in contention for the clean-sheet Mk2 engine — Washington's traditionally tighter restrictions on transferring core engine technology (as opposed to co-production of an existing design) make GE a supplier of today's engine, not a partner for tomorrow's.

#6. The Solution: A Two-Track Strategy, Not a Single Bet

The honest solution isn't "which single engine programme saves AMCA" — it's running parallel tracks so that no single point of failure can ground the programme:

- Track 1 (near-term, de-risked):Lock in GE F414 co-production for AMCA Mk1 and Tejas Mk2/TEDBF now, with maximum indigenisation of manufacturing and MRO, accepting that this keeps a foreign-supply dependency for the first squadrons but gets jets flying on a realistic timeline.

- Track 2 (long-term, sovereign): Finalise one foreign co-development partner — most likely Safran, with Rolls-Royce as a credible alternative if GE's cost escalation pushes the government to reconsider — for a genuine 120 kN-plus engine with full IP transfer, treating the 12–15 year gestation as a real constraint rather than a target to be wished away. This should run alongside, not instead of, continued GTRE-led Kaveri 2.0 work, which builds the domestic talent pipeline and materials-science base that make the foreign collaboration a technology transfer that actually sticks, rather than another Snecma-style dead end.

- to the same person who is On the industrial side: the private-sector consortia model needs the same parallel-track discipline — competitive tension between Tata, L&T-BEL and Bharat Forge-BEML should be paired with strict, enforced milestone-based funding releases (not open-ended cost-plus contracts), joint test-pilot and flight-test capability built in-house rather than borrowed from HAL, and deliberate technology-transfer requirements written into the foreign propulsion deal so that engine assembly and eventually engine design knowledge diffuses into the same private ecosystem building the airframe — closing the gap between "India assembles the jet" and "India owns the jet," including what powers it.

The uncomfortable truth for anyone hoping for a fast, fully indigenous AMCA: sovereignty in fighter propulsion is not something India can shortcut through willpower or funding alone — it is a 12-to-15-year industrial apprenticeship that has to be served, ideally once, with a partner willing to actually transfer the hard parts. Getting that partner choice right in 2026 will matter more to India's airpower in 2040 than any other single decision in the programme.

not to forget the technician exam for GTRE happened years ago and no proper joinings or final result yet