AMCA, HAL, and the Hard Work of Building an Indian Aerospace Ecosystem

In an earlier column for The Print, I argued that India’s Advanced Medium Combat Aircraft (AMCA) programme would succeed or fail not on engineering competence alone, but on whether India could finally build a viable aerospace ecosystem rather than relying on a single institutional champion. The argument was not about defending or attacking Hindustan Aeronautics Limited (HAL). It was about structure, risk, and delivery.

The recent reports that HAL has not been shortlisted as the Development-cum-Production Partner (DcPP) for AMCA prototypes, while a small set of private players and consortia have cleared the initial filters, make that argument newly relevant. Predictably, the debate has polarised. For some, this is long-overdue disruption. For others, it is an inexplicable sidelining of India’s most capable aircraft manufacturer.

Both reactions miss the point.

This decision is neither a verdict on HAL’s engineering capability nor proof that private industry will magically do better. It is the downstream consequence of a system decision taken years ago to end structural dependence on a single prime integrator. Whether that decision improves outcomes will depend on what the state does next.

What the AMCA decision actually means

To make sense of the present moment, three questions need to be separated.

First, is HAL technically capable of building AMCA prototypes?

Yes. HAL remains the only Indian entity with decades of experience in fighter aircraft manufacture, integration, flight test support, certification workflows, and sustainment. Nothing in the current process negates that reality.

This naturally raises the question of the National Flight Test Centre (NFTC). HAL remains the only Indian aircraft manufacturer with embedded, end-to-end industrial flight-test capability. NFTC provides national flight-test and certification expertise, but it does not replace an integrator’s in-house test-modify-produce loop.

Second, did the system deliberately remove HAL’s automatic claim to be the integrator?

Yes. That shift occurred when AMCA was structured around a Special Purpose Vehicle (SPV) model. Design authority was vested in the Aeronautical Development Agency (ADA), while the development-cum-production role was no longer automatic but made explicitly contestable through competition.

This marked a clear departure from earlier programmes where integration defaulted to HAL by institutional convention rather than by comparative assessment. That choice was not about engineering quality. It was about risk and capacity management.

Third, did the SPV predetermine HAL’s exclusion?

No. This is where much commentary overreaches. An SPV creates contestability. It does not mandate replacement. HAL could still have emerged as Development-cum-Production Partner (DcPP) if capacity, bandwidth, and delivery confidence stacked up convincingly against the competition.

The present outcome should therefore be read neither as a humiliation nor as a triumph. It is the intersection of an earlier structural choice with today’s capacity realities.

Why the state chose contestability

Five years ago, policymakers had already internalised three risks that had little to do with engineering competence.

One, capacity saturation. HAL carries an enormous and politically non-negotiable workload across fighters, trainers, helicopters, upgrades, and sustainment. At some point, experience stops being an asset and becomes a bottleneck.

Two, timeline slippage history. Not all delays are managerial failures. Many are systemic, driven by funding uncertainty, changing requirements, and fractured accountability. But from the user’s perspective, the effect is the same.

Three, the single-point-of-failure problem. A country that depends on one institution for combat aircraft production is exposed, irrespective of how competent that institution is.

The SPV was therefore a risk-governance instrument, not an engineering judgment. It signalled that future combat aircraft programmes would not automatically default to a single prime, however accomplished.

That signal matters. But signalling is the easy part.

Why private entry alone does not create an ecosystem

There is a temptation to read the AMCA shortlisting as proof that private industry is finally “taking over” aerospace. That is a comforting narrative. It is also misleading.

Combat aircraft programmes do not fail because someone cannot machine parts or assemble structures. They fail because of weaknesses in systems integration, configuration control, flight-test discipline, certification processes, and learning loops that stretch over decades. These are not skills you acquire by winning a tender. They are institutional capabilities built through repeated exposure to risk.

India’s private sector brings genuine strengths: capital, manufacturing discipline, supply-chain management, and, in some cases, world-class niche capabilities. What it does not yet have is an end-to-end experience of taking a fighter aircraft from prototype to squadron service under Indian military and regulatory conditions.

That gap is not a moral failing. It is the predictable result of a system that, until recently, did not allow private firms to own such programmes.

Which brings us to the uncomfortable truth: opening competition is necessary but not sufficient. Without changes in how programmes are governed, funded, and de-risked, private primes will inherit the same structural constraints that burdened HAL, and the cycle of disappointment will repeat under new ownership. By “primes” (prime integrator), I mean the lead entity responsible for end-to-end integration, supplier management, and delivery against time, cost, and performance.

The missing layer: programme governance

If there is one lesson aerospace powers have absorbed, it is that ownership models matter less than programme discipline.

A credible AMCA ecosystem requires, at minimum:

– Clear separation of roles: design authority, user authority, and integrator authority must be distinct and empowered.

– Milestone-linked accountability: payments and penalties tied to tangible progress, not paper compliance.

– Configuration control: ruthless resistance to requirement creep during development.

– Risk-sharing: the state must explicitly own developmental risk rather than pushing it downstream and then penalising delays.

– Long-term demand signalling: industry cannot invest in skills and tooling on episodic orders and annual budgets.

None of these are solved by choosing a private firm over a public one. They are solved by how the state behaves as a customer and market-maker.

This was the core argument of my earlier article, and it remains unresolved.

HAL’s paradoxical position

HAL today occupies an uncomfortable dual role. It is simultaneously indispensable and structurally constrained.

On the one hand, it holds institutional memory that India cannot afford to lose. On the other, it is expected to carry national capability without the autonomy, financial flexibility, or workload rationalisation that such responsibility requires.

Treating HAL’s non-shortlisting as either punishment or liberation misunderstands this paradox. If HAL is not restructured, re-prioritised, and allowed to compete on equal terms with clear capacity commitments, it will remain trapped between expectation and blame.

Equally, if private primes are brought in without a serious effort to absorb, share, and institutionalise the knowledge HAL has accumulated, India risks fragmenting rather than strengthening its aerospace base.

The fiscal question that refuses to go away

There is another issue that tends to be discussed last, if at all: money.

The prototype phase of AMCA, however large it appears, is modest compared to the cost of series production and sustainment. That burden will fall overwhelmingly on the Indian Air Force’s (and maybe the Indian Navy’s) capital budget over many years.

If funding remains uncertain, back-loaded, or hostage to annual cycles, no integrator, public or private, will deliver at the pace rhetoric demands. Aerospace ecosystems are built on credible, long-term fiscal commitments, not on announcements.

Without this, we will continue to celebrate roll-outs and first flights while squadrons remain elusive.

What this moment should prompt us to ask

The AMCA shortlisting is an inflection point. Not because HAL has been kept out of one stage, but because India has reached the limits of what incremental change can achieve.

The real questions are not about which firm won or lost.

They are about whether India is finally willing to:

– Behave as a patient market-maker rather than an episodic buyer

– Absorb developmental risk rather than outsourcing it and then expressing surprise

– Invest in programme governance with the same seriousness it invests in platforms, and

– Accept that aerospace capability is measured in decades, not news cycles.

If the answer is yes, then contestability will strengthen the ecosystem. If not, we will simply rotate responsibility and repeat old arguments under new names.

A closing thought

India does not lack engineers. It does not lack firms. It does not even lack ambition.

What it has lacked, so far, is the institutional willingness to align risk, responsibility, and reward over the full life of an aerospace programme.

AMCA offers another chance to correct that. Whether we take it will matter far more than who builds the first prototypes.

Whether the Indian government has truly learnt from past failures and will get the next steps right is the question that now matters. Some of those next decisions, particularly how selection is approached in programmes of this complexity, will deserve closer scrutiny.

If you would like to follow this line of inquiry as it develops, you may consider subscribing and looking out for the next post.