For the Indian Air Force, the Medium Transport Aircraft (MTA) programme is not simply another aircraft acquisition. It addresses one of the most important gaps emerging in India’s military logistics architecture. India faces two nuclear-armed adversaries, while large parts of its borders run through terrain where conventional road-based logistics remain difficult, slow and vulnerable to disruption. In such an environment, the ability to move troops, ammunition, equipment and supplies quickly between major air bases, Advanced Landing Grounds and forward areas is not a luxury. It is a core operational requirement.
The problem is that India’s existing transport fleet is ageing. The An-32 has been the backbone of tactical airlift for decades, while the IAF’s HS-748 Avro fleet represents an even older generation of transport aircraft. The C-17 provides valuable heavy strategic airlift, but the fleet is relatively small, while the C-130J fulfils a different role with its emphasis on tactical airlift and special operations. The IL-76 remains an important platform as well, but its age and serviceability have increasingly become constraints. The C-295 programme is now addressing the lighter end of the transport requirement, but India still needs a modern aircraft in the medium category to replace the capability that the ageing An-32 fleet has provided for decades.
This is where the MTA becomes strategically important. It is expected to form a major part of the IAF’s future transport architecture alongside the C-295, C-130J and C-17. More importantly, the programme has now reached a stage where India’s private aerospace industry has already begun positioning itself around the requirement. Tata Advanced Systems has partnered with Lockheed Martin around the C-130J, while Mahindra Defence has partnered with Embraer around the C-390 Millennium. Both aircraft represent mature international platforms, and both have a clear industrial proposition for India. The presence of multiple serious contenders also means that the programme does not necessarily have to become another single-vendor procurement.
That makes the reported position emerging around HAL particularly interesting.
According to a source from within the IAF who spoke to Alpha Defense, HAL is seeking changes to the MTA requirement, including an increase in the maximum take-off weight of the aircraft towards the 40-tonne class. This information has not been publicly confirmed through an official HAL or IAF document, so it should be treated as a source-based claim rather than an established fact. However, if such a proposal is indeed being pursued, it raises an important question about the timing of HAL’s intervention.
The MTA requirement has not suddenly appeared on the table. The requirement has been known for years. Potential aircraft have been evaluated, foreign OEMs have been engaging with Indian companies, and Indian private-sector firms have already invested considerable effort in creating partnerships around the programme. The government has now moved the procurement into a formal phase, with the current process seeking 60 aircraft and requiring their manufacture in India through an Indian industrial partner and foreign OEM collaboration.
This is where HAL’s position becomes difficult to understand. If HAL wanted to participate in the programme, it had considerable time to identify an OEM, establish a partnership and prepare an industrial proposal. It could have approached Lockheed Martin, Embraer or another suitable manufacturer and developed a credible plan for production in India. It could have built the manufacturing, technology-transfer and supply-chain proposition required to compete with Tata and Mahindra. Yet, if the information being reported is correct, HAL is now attempting to influence the aircraft requirement itself while it has not even finalised the OEM partnership through which it would participate.
That is an unusual sequence.
There is nothing inherently wrong with HAL wanting to participate in the MTA programme. In fact, there is a strong strategic argument for India’s largest aerospace manufacturer to have a role in building transport aircraft in the country. The issue is how that participation is achieved. If HAL has a credible aircraft or a credible foreign partnership that meets the IAF’s operational requirements, it should compete. If it believes the existing requirement is technically inadequate, it should present evidence showing why the requirement needs to change. What becomes problematic is changing the customer’s requirement primarily because an industrial participant was late in preparing its own proposal.
The maximum take-off weight is particularly important in this context because it is not an isolated number on a specification sheet. Moving an aircraft into a higher weight category can have consequences for its structure, landing gear, engines, wing design, fuel capacity, payload-range characteristics, runway requirements and high-altitude performance. For the IAF, these characteristics matter because the aircraft will not simply operate from large metropolitan air bases. Its value lies precisely in its ability to support military operations across India’s difficult geographical environment, including forward and austere airfields.
The MTA requirement therefore has to be driven by the operational problem that the IAF is trying to solve. It should not be driven by which aircraft an industrial participant happens to be capable of assembling.
This distinction is important because the Indian defence industry has spent years discussing the difference between genuine indigenisation and what is often derisively called “screwdriver technology”. Importing a foreign design and assembling it in India can certainly create manufacturing capability, supply chains and jobs, but it does not automatically create indigenous design capability. India should therefore demand meaningful technology transfer and increasing domestic content wherever possible. However, even an assembly programme requires an OEM partnership, production planning, tooling, supply-chain development, trained manpower and contractual preparation.
In that sense, there is an uncomfortable irony to the present situation. The criticism of foreign-origin assembly is often that it represents a shortcut to indigenous capability. Yet if HAL is indeed trying to enter the MTA programme through a foreign OEM partnership, it appears to have reached even that stage late. The question then becomes why the requirement should be altered to accommodate an organisation that did not establish its position when the opportunity was available.
India’s defence procurement system has historically suffered from delays, shifting requirements and prolonged competition. Every change to a requirement can potentially push a programme further into the future. That is particularly dangerous for the MTA because the underlying capability gap is not getting younger. Every additional year of delay means another year in which the IAF has to maintain ageing transport aircraft while waiting for their replacement.
The irony is that India now appears to have the beginnings of exactly the kind of industrial competition it has been asking for. Tata has built a relationship with Lockheed Martin around the C-130J. Mahindra has established a relationship with Embraer around the C-390. These are not paper concepts. They involve established aircraft, established OEMs and established industrial partnerships. The two aircraft also offer different approaches to the IAF’s requirement, giving the customer an opportunity to evaluate competing solutions on performance, cost, technology transfer, manufacturing depth, availability and lifecycle support.
If HAL wants to enter this competition, there is no reason why it should not be allowed to do so. But it should enter the competition rather than attempt to redefine it.
This is ultimately not about HAL versus Tata, or HAL versus Mahindra. It is about who gets to define India’s military requirements. The requirement should emerge from the operational needs of the armed forces, and industrial players should then compete to satisfy it. The reverse approach, where the industrial ecosystem influences the requirement so that a particular participant can become eligible, risks turning the procurement process upside down.
HAL has a critical role to play in India’s aerospace ecosystem. Its experience, infrastructure and manufacturing base are national assets. But those advantages also come with a corresponding responsibility. When a programme is already moving forward, the answer to being late cannot be to ask the customer to slow down or change direction.
If HAL has a better aircraft, a better industrial proposition or a better technology-transfer package, it should put that proposition on the table and compete. If the existing MTA requirement genuinely fails to meet the IAF’s operational needs, HAL should demonstrate that through technical evidence. But if the requirement is being reconsidered simply because HAL has not yet prepared itself to participate, then India needs to ask a much bigger question about institutional accountability.
The country does not need another procurement cycle in which the requirement changes, the process resets and the capability gap continues.
The IAF needs transport aircraft.
It needs them while the An-32 fleet is ageing, while the IL-76 fleet continues to face serviceability challenges and while India’s logistical requirements along difficult borders continue to grow.
India should therefore welcome competition, technology transfer and domestic manufacturing. But the race should be decided by the aircraft and the industrial proposition that best meet the operational requirement established by the IAF.
If HAL wants to participate, it should compete on those terms.
