Kaveri and Bharat’s Path to Aerospace Self-Reliance

If you are trying to decide whether the Kaveri programme deserves another serious national commitment, the usual yes-or-no question – did it deliver an operational engine? – is too crude. It collapses engine performance, testing capacity and funding policy into one verdict.

Bharat’s real choice is whether to sustain an indigenous engine-development loop: design, test under relevant conditions, diagnose, modify and test again. That loop, rather than any single prototype or announcement, is the capability you should look for in a credible claim of aerospace self-reliance.

Kaveri’s outcome cannot be reduced to one word

Calling Kaveri either a success or a failure conceals the information needed for a sound decision. At least three questions must be separated: What performance had the engine achieved? What remained below requirement? What prevented the development team from closing that gap?

Former Chief of Integrated Defence Staff Vice Admiral Raman Puri (Retd.) has argued that, during the final rounds of testing, Kaveri’s dry thrust was approaching expectations while its afterburning performance remained below target. GTRE believed it had identified the afterburning problems and needed continued development to refine the engine. This is an informed assessment, not a publicly presented test dossier, so it should not be turned into a claim that success on a particular schedule was guaranteed.

The distinction between dry and afterburning performance matters. Dry thrust is produced without the afterburner. Afterburning raises thrust by burning additional fuel in the exhaust stream. If afterburning remains below the required level, the complete engine has not met its intended performance. But that shortfall does not make the dry performance, test data or engineering knowledge worthless.

The defensible conclusion is narrower: Kaveri had not met its full objective, yet the available account indicates that some performance was nearing expectation and that the remaining shortfall was considered technically identifiable. That is the difference between an engine that is not ready and a programme from which nothing useful can emerge.

When you encounter the word “failure” in a discussion of Kaveri, ask what specifically failed. Was it dry thrust, afterburning thrust, reliability, the development schedule, access to testing, or the original plan for operational use? Unless those outcomes are separated, the label tells you almost nothing about the next decision.

The decisive capability is the test-and-redesign loop

A jet engine is not perfected through one uninterrupted act of design. Engineers run an instrumented test, inspect the results, identify a limitation, modify the engine and test it again. The speed and quality of that cycle determine how quickly uncertainty becomes usable knowledge.

Kaveri lacked a domestic high-altitude engine test facility. Major tests required sending the engine to Russia and waiting months for testing slots before it could return to Bharat for analysis and modification. A delay produced by that arrangement was not automatically proof that the engineering team had stopped progressing. Part of the calendar was being consumed by access and logistics rather than design work.

This changes how programme performance should be measured. Elapsed years alone are a poor diagnostic. The more useful measure is iteration time: how long does it take to move from a design change to a relevant test, obtain the data, make the next change and return to test?

A nation that can design an engine but cannot test it when needed does not control the development schedule. It also cannot easily distinguish a hard technical problem from a slow institutional process. The missing facility therefore represents more than an inconvenience for Kaveri. It is a strategic bottleneck for every programme that depends on the same kind of testing.

Before supporting any future engine allocation, you should expect clear answers to four questions. Is relevant high-altitude testing available domestically? How quickly can a modified engine return to test? Is access assured across the whole development sequence? Can Indian teams obtain the test data, diagnose the result and change the design without waiting for a foreign gatekeeper? These questions reveal more about real self-reliance than a ceremonial unveiling does.

Continuous funding must buy learning, not merely time

The judgement that halting Kaveri funding cost Bharat decades of technological progress is a strategic assessment, not a laboratory measurement. Its force comes from the nature of the capability being built. A prototype can be placed in storage; a living engineering ecosystem cannot simply be frozen and restarted on demand.

Engine capability accumulates through trained teams, facilities, manufacturing processes, test data and repeated experience with failure. When continuity breaks, the next programme may have to rediscover knowledge that the previous team was already learning. Money saved in one budget period can reappear later as lost time, renewed foreign dependence and another incomplete development cycle.

That does not justify an unlimited budget or the indefinite protection of missed targets. Strategic patience and accountability belong together. Funding should continue through explicit technical gates: state the engine configuration tested, distinguish dry from afterburning performance, identify the objective of the test, record the result and name the next corrective step. Infrastructure delay should be reported separately from an unresolved design defect.

This creates a better policy distinction. Procurement asks when a usable engine can be delivered for a platform. Technology development asks which capabilities must be retained even when that delivery date moves. Treating both questions as one contract encourages premature termination: if immediate integration slips, the country discards the learning mechanism along with the schedule.

A disciplined programme can therefore preserve the engine-development line without pretending that an unfinished engine is operationally ready. The standard should be continuous, measurable reduction of technical uncertainty – not patriotic rhetoric, but not the procurement of foreign hardware as a substitute for indigenous learning either.

Key takeaways: measure sovereignty by what Bharat controls

• Operational readiness and accumulated technological capability are different outcomes; Kaveri must be judged on both.
• The available account places dry thrust near expectations but afterburning performance below target, so neither total success nor total technical failure is an adequate description.
• Domestic high-altitude testing matters because control of the test calendar controls the speed of engineering iteration.
• Continuous funding should be tied to transparent technical gates, not granted as a blank cheque.
• Foreign collaboration is compatible with self-reliance when it accelerates Indian learning rather than controlling whether the next test, diagnosis or redesign can occur.

Strategic self-reliance does not require Bharat to reject every foreign component, facility or partnership. It requires the country to retain enough authority and capacity to keep developing when foreign access becomes slow, conditional or unavailable. A foreign relationship should expand the Indian learning loop, not become the switch that turns it on and off.

You can evaluate self-reliance at three levels. At the platform level, ask whether the armed forces can operate and support what they field. At the programme level, ask whether Indian teams can test, diagnose, modify and qualify the technology. At the national level, ask whether knowledge and infrastructure will remain available for the next engine even if the present design never enters service in its original form.

Kaveri’s deepest strategic value lies at the second and third levels. A platform deadline can be met through imports, but importing an engine does not by itself create the capacity to design the next one. Procurement can fill an operational gap; it cannot be allowed to erase the development path.

What Bharat should require from the next Kaveri decision

1. Establish a domestic high-altitude engine-testing loop with dependable access, so design changes are not separated from relevant tests by foreign queues lasting months.
2. Fund engine maturation through declared milestones that report dry and afterburning performance separately and connect every test result to the next engineering action.
3. Publish a legible programme scorecard that distinguishes technical shortfalls, infrastructure constraints, logistical delays and management decisions.
4. Preserve Indian design authority, test data and skilled teams even when an immediate platform schedule requires a different procurement choice.
5. Judge partnerships by whether they transfer learning and shorten future Indian iterations, not merely by whether they deliver one finished engine.

The next Kaveri decision should be framed as a national capability decision before it is framed as a verdict on one engine. Ask whether the budget merely funds another announcement or shortens the next design-test-redesign cycle on Indian soil. Back the latter with measurable gates. That is how one difficult programme becomes durable aerospace capacity rather than a cautionary tale repeated by its successor.

References

• Hindu Post – Vice Admiral Raman Puri: Stopping Kaveri Funding Was Bharat’s Biggest Jet Engine Mistake