AMCA: Why L1 Approaches Can Fail Combat Aircraft Development

As the AMCA debate enters its decisive phase, one procurement idea now deserves closer scrutiny. Not the technical evaluation that has already produced a shortlist, but what follows it.

Once the technically qualified bidders submit their commercial proposals after receiving the RFP, reports suggest that the final selection may be made on a lowest-cost (L1) basis. If that is indeed the approach, technical credibility becomes little more than an entry ticket, not a way to judge who is actually better placed to deliver. At precisely the stage where integration depth, learning discipline, and execution risk matter most, cost would become the deciding factor. In that scenario, the risks involved are no longer abstract. They sit at the heart of the next decisions the Ministry of Defence (MOD) must take.

In routine procurement, L1 (the lowest commercial bidder) has a role. When designs are frozen, risks are known, and outcomes are predictable, price competition can be a useful discipline. It keeps suppliers honest and protects public money.

Combat aircraft prototypes do not fit that model.

They are not early production items, and they are not “build-to-drawing” contracts. Their purpose is to uncover what is not yet understood, expose integration problems, and absorb failures early, before they multiply at scale.

When prototypes are treated like commodities, programmes do not become cheaper. The approach introduces fragility. And this is no longer a hypothetical concern. If the lowest cost is allowed to dominate the final AMCA Development-cum-Production Partner (DcPP) selection, price will be placed at the centre of a decision whose success depends far more on learning, discipline, and long-term execution.

That is why this moment matters and needs to be debated.

False Economy: How “Saving Money” Quietly Destroys Capability

Every major national programme is sold as a triumph of efficiency. Costs are controlled. Timelines are compressed. Minimum requirements are met. And yet, again and again, the programmes that look cheapest at the start turn out to be the most expensive in the end.

This is not mismanagement by accident. It is “false economy by design”.

A false economy occurs when early savings are achieved by cutting learning, testing, or capability, on the assumption that shortcomings can be fixed later. They rarely are. Once production lines are running and political capital is committed, every correction becomes slower, costlier, and more painful.

Global experience is unforgiving. Deferred testing leads to retrofits. Under-scoped capability leads to upgrades that never quite deliver. “Minimum acceptable” designs create maximum downstream cost. What looks prudent in year one quietly compounds risk for the next twenty.

This lesson is directly relevant to India’s Advanced Medium Combat Aircraft (AMCA) programme. The real danger to AMCA is not ambition. It is the temptation to appear economical by compressing development, limiting prototypes, or treating early production as proof of success. Fighter aircraft do not mature through spreadsheets; they mature through hard, expensive learning.

If AMCA is pushed too quickly toward numbers, low unit cost, or early induction optics, India risks repeating the global pattern—cheap aircraft today that demand costly fixes tomorrow, and capabilities that arrive years after they are needed.

The hardest truth for policymakers is this: the most economical decision often lead from overspending at the start. Programmes that invest early in realism, testing, and design discipline almost always cost less, perform better, and survive contact with reality.

False economy is not about spending too much. It is about spending badly—and calling it discipline.

Why lowest price and learning pull in opposite directions

Lowest-bidder logic holds when three conditions are met: the design must be stable, the technical risk must be low, and the learning must be marginal rather than central. None of these applies to a fifth-generation fighter.

Stealth shaping, materials, avionics software, sensor fusion, electronic warfare, propulsion growth, flight-control laws, and certification boundaries all evolve through testing, redesign, and iteration. Uncertainty is not a flaw in the process. It is the process.

When L1 logic enters this space, it changes behaviour in predictable ways. Firms under-price risk. Learning is compressed. Problems are assumed to be solvable later. And “later” is exactly when costs return: in the form of delays, retrofits, and capability gaps.

The counter-argument is familiar: once the technical qualification is complete, all surviving bidders are deemed equally capable, so price should decide. But “equally qualified on paper” is not the same as “equally capable of managing developmental risk.” In a prototype programme, the gap between minimum technical compliance and genuine integration depth is where programmes live or die.

This is not a philosophical objection. It is borne out repeatedly in practice.

What global experience actually shows

The international record on this question is remarkably consistent.

The F-35 Joint Strike Fighter is the most cited example. The Pentagon’s concurrency strategy — producing aircraft before development was complete in order to contain early costs — led to extensive retrofits once testing exposed design flaws. The Pentagon estimated that concurrency-related retrofit costs alone exceeded $1.4 billion across early production lots. Senior US officials later described concurrency as a miscalculation. Early affordability translated into long-term cost escalation and delayed capability.

The Eurofighter Typhoon followed a different but related path. Early tranches were deliberately under-scoped to meet affordability pressures. Capability was deferred to later phases. The aircraft entered service only after multiple enhancement programmes to close gaps that had been known but postponed.

The A400M Atlas shows the limits of contractual risk transfer. Fixed-price development was meant to cap government exposure. Integration complexity overwhelmed the contract. Delays mounted, costs rose anyway, and governments ultimately had to renegotiate and absorb the risk they had tried to price away.

India’s own Tejas Mk1 experience follows the same pattern, though in a quieter way. Learning was stretched over time because funding and parallel development were constrained. Early aircraft entered service with limitations that later variants had to address. This was not incompetence. It was what happens when learning is rationed.

Across these cases, the lesson is consistent: when learning is squeezed to protect near-term price optics, cost returns later through time, redesign, and retrofit.

When learning was allowed to come first

There are contrary examples, and they are instructive.

The F-22 Raptor underwent a long and expensive prototype and test phase. Design maturity was prioritised before production. The aircraft was costly, but it entered service largely without the concurrency-driven retrofit chaos seen elsewhere. Capability evolution continued after the Initial Operational Clearances (IOC), but the core design remained stable.

The Gripen E demonstrates a different path. Cost discipline was maintained, but not through lowest-bid competition. Strong configuration control, model-based development, and clear design authority enabled early learning. Delays occurred, but escalation remained contained.

The difference in these cases was not ownership or ideology. It was how the programmes were optimised.

Why the AMCA decision window is unusually consequential

This brings us back to AMCA.

Three private consortia are now expected to receive the Request for Proposal for the prototype phase. Under the current plan, the selected partner will work with the Aeronautical Development Agency (ADA) to build five flying prototypes and one structural test article under a ₹15,000 crore allocation. Target dates for first flight, certification, and production are already circulating.

On paper, this looks like forward momentum. In reality, this is the point at which programmes quietly succeed or quietly break.

Between contract award and first flight lie the hardest parts of any combat aircraft programme: systems integration, flight-test discovery, envelope expansion, configuration freezes, and certification convergence. These processes do not accelerate because bids are cheaper. They mature when learning is protected and governed.

This is why the evaluation method matters so much now.

There is an additional institutional wrinkle worth noting. The pre-qualification stage reportedly used a quality-cum-cost scoring approach that accounted for capacity constraints, such as order-book saturation. If the programme now defaults to pure L1 at the RFP stage, it would represent a step backwards in an otherwise sophisticated evaluation, precisely at the point where judgement matters most.

That paradox should make decision-makers pause and make them think.

What treating this seriously would actually mean

If AMCA is to be treated as a learning programme rather than a price contest, some implications follow naturally.

The lowest bidder cannot be the sole discriminator. Technical credibility must come first. Payments should follow learning milestones, not paper compliance. Configuration control must be enforced, not negotiated. And developmental risk must be acknowledged and owned, not hidden in contract language.

None of this weakens accountability. It makes accountability real.

A closing thought

L1 was designed to buy certainty at the lowest price. Combat aircraft prototypes exist to confront uncertainty honestly. Confusing the two is not fiscal prudence. It is deferred responsibility.

As political stakes and public expectations build around AMCA, the real test is whether India can keep its intellectual discipline, not about who wins the contract, but about how learning is valued. If that lesson is absorbed now, AMCA will have already done something important, even before the first aircraft ever flies.

There are deeper layers to the AMCA debate that go beyond timelines, bids, and contracting models. One such layer concerns Intellectual Property (IP). Not as a commercial entitlement, but as a question of sovereignty. Who controls design decisions, who authorises modifications, who can integrate new sensors or weapons without external permission, and who retains the freedom to adapt the aircraft over its lifetime are not secondary issues. They determine whether a combat aircraft remains a national capability or slowly slips into being a licensed one.

As India moves toward partnering with private integrators and consortia on AMCA, the protection, custody, and governance of intellectual property will matter as much as who builds the prototypes.

I will take this up next, looking at how IP in programmes like AMCA must be protected not merely as a commercial asset, but as a sovereign one. If you would like to follow that line of thinking as it develops, do consider subscribing and staying with the argument.