Hindustan Aeronautics Limited’s public assurances that “engine issues” would
be resolved by the end of March 2026 have collided sharply with the
ground‑level reality that no additional F404‑IN20 engines were delivered to
the TEJAS MK-1A line by 31 March and, consequently, no MK-1A aircraft were
formally handed over to the Indian Air Force against the projected tranche of
five jets.
HAL’s own statements in February indicated that five MK-1A aircraft were ready
for delivery once engines arrived, another nine were built and flown but
awaiting engines, and several more airframes were in the pipeline, all of
which depended on a steady flow of GE‑supplied F404‑IN20s.
Reports from early 2026 show that HAL had received only a handful of
engines—five plus one additional unit up to January 2026—against an order of
99 F404‑IN20s for the initial batch of 83 MK-1A fighters, with a follow‑on
contract for 113 more engines to support the 97‑aircraft order placed in 2025.
Historical Vs Promised Milestones
| Milestone | Promised Timeline | Actual Status (Mar 2026) |
|---|---|---|
| Contract signed for 83 TEJAS MK-1A (₹48,000 crore) | 2021 | ✔ Signed, but deliveries lagging |
| First aircraft delivery | By Feb 2024 (original plan) | ❌ Slipped to 2026 |
| Initial batch (3 fighters) | 2024–25 | ❌ Still pending, pushed to Mar 2026 |
| 15 aircraft ready | End of 2025 | Only 5 delivered-ready, 9 awaiting engines |
| GE F404-IN20 engines (99 units) | 2024–2029 | ✔ 6 delivered so far (5 in 2025, 1 in Jan 2026) |
GE Aerospace committed to a “two‑per‑month” delivery rhythm from April 2025
onward, intended to carry through to March 2026, in order to clear the backlog
and allow HAL to deliver 12 TEJAS MK-1A jets by the close of FY2026.
On paper, the US government had promised uninterrupted F404 supply through
this period, and Indian officials had gone so far as to say that would “meet
HAL’s target to deliver 12 TEJAS MK-1A aircraft” by the fiscal‑year cut‑off.
However, by 31 March 2026, neither the engine‑delivery pipeline nor the actual
aircraft handover has kept pace with those commitments. Open‑source and
social‑media‑sourced tallies circulating among defence watchers indicate zero
new engine deliveries to the MK-1A line in the final month and, therefore,
zero MK-1A deliveries to the IAF versus the promised five.
This gap is particularly jarring because HAL’s CMD had publicly stated that
integration‑related engine issues—such as fit‑checks, software maturation, and
interface‑validation—had already been resolved, implying that the only
remaining bottleneck was physical engine availability.
If integration problems were in fact sorted, the remaining choke points are
almost certainly logistical, contractual, and/or internal to HAL’s execution
rather than external GE‑supply‑chain hurdles acting alone.
Closer inspection of the situation suggests that the bottleneck has shifted
from pure engine‑supply to a mix of HAL‑specific factors.
Even if GE sustains two engines per month in aggregate, the precise timing of
those shipments, the handling of customs and quality‑assurance procedures at
HAL facilities, and the sequencing of airframe‑engine mated testing can all
create localised blockages on the production line.
There are also reports that HAL’s own production‑rate planning and internal
logistics—such as final‑assembly line load, engine‑test‑bay capacity, and
manpower rosters—have not always been synchronised with the incoming
engine‑flow, leaving completed airframes stranded in the “awaiting engines”
queue rather than being rapidly mated and cleared.
In some cases, engines delivered to India may have been earmarked for other
TEJAS programs or test‑beds, or held in inspection and certification loops,
which further throttles the number that can actually be fitted to MK-1A
machines for IAF release.
Another layer of delay resides in the feedback loop between HAL, IAF
acceptance authorities, and the Directorate of Quality Assurance
(Aeronautics).
Even where airframes are fitted with engines, the IAF may insist on additional
flight‑test hours, mission‑scenario validation, or paperwork reconciliation
before accepting aircraft formally, which can stretch out the
“ready‑to‑deliver” period.
Some defence‑industry analysts have pointed out that HAL sometimes treats an
aircraft as “ready” once the factory‑acceptance checks are complete, whereas
the IAF counts “delivery” only after successful user‑trials and documentation
sign‑offs, creating a perceptual gap between the two sides.
This dichotomy can make HAL’s public statements about “five aircraft ready by
March 31” appear to be at odds with the IAF’s own records of zero physical
deliveries, even if engines are in place and ground tests are complete.
From a broader program‑management perspective, the TEJAS MK-1A timeline has
long been conditioned by the fact that the F404‑IN20 line was shut down after
2016 and then re‑started in 2021, compounded by pandemic‑era disruptions and a
fragmented global supply chain for precision components.
HAL’s own slower‑than‑expected ramp‑up of the production line, coupled with
serial‑change requests from the IAF and software updates for avionics and
radar, added further schedule pressure.
Although the latest US‑India coordination and the new $1 billion follow‑on
engine deal are meant to stabilise the flow from 2027 onward, the current
fiscal‑year gap demonstrates that shorter‑term sequencing and internal
execution discipline remain weak links.
Given that integration issues have been declared closed, the residual hold‑up
is increasingly difficult to outsource to external actors.
The fact that neither engines nor aircraft have materialised at the rate
promised by March 2026 points squarely to HAL’s responsibility for matching
engine‑arrival cadence with assembly‑line throughput, testing‑bay throughput,
and IAF‑acceptance preparations.
If the IAF had required extra validation or documentation, those requirements
should have been factored into the delivery calendar; if engine‑handling and
certification loops are digesting engines that could otherwise be mounted,
those processes must be streamlined.
In this light, the current situation is less about a looming technical crisis
and more about a failure of program governance, coordination, and transparent
communication—accountability for which rests logically with HAL’s top
management and the project‑execution machinery at the Nashik and Bengaluru
facilities.
IDN (With Agency Inputs)
