Tejas Mk1A Hits Fresh Engine Trouble as Defence Ministry Orders September Review

Every road in India’s flagship fighter programme now leads to September. That is the month Hindustan Aeronautics Limited says it will hand over the first batch of Tejas Mk1A jets to the Indian Air Force. It is the month the Defence Ministry has chosen for a comprehensive review of the entire programme, one meant to end with a new and avowedly realistic delivery timeline. It is also the month by which HAL expects visible progress on radar integration. The trouble is that the path to September just got narrower.

The sixth GE Aerospace F404-IN20 engine delivered to HAL — it arrived only in May — developed a defect during quality assurance checks. Around the same time, an engine failed its acceptance parameters, a fresh hurdle first reported in late June. HAL has notified GE Aerospace, and a technical team from the United States is expected to examine the defective engine in India before deciding whether it can be repaired on site or must be replaced outright. The early assessment is reassuring, as far as it goes: the defect is described as relatively minor and possibly the result of a routine transit issue rather than any structural flaw. The other five delivered engines remain cleared for aircraft assembly.

But the arithmetic is what makes even a minor snag consequential. India contracted 99 F404 engines in 2021 under a deal worth Rs 5,375 crore — about $716 million — and GE Aerospace has not kept to the agreed delivery schedule. Six engines in five years leaves 93 still to come, while roughly 30 brand-new Mk1A airframes sit finished and grounded, waiting for powerplants. The Indian Air Force ordered 83 of these fighters in February 2021 for roughly Rs 48,000 crore, and the programme is now running more than two years behind schedule. When the margin for error is a single-digit engine inventory, one engine in quarantine matters.

What September Must Settle

The review will have to resolve three questions. The first is whether the delivery target for the opening Mk1A batch — still officially September — survives contact with the engine ledger. Five cleared engines are enough to begin assembly, but a first handover is only credible if the pipeline behind it accelerates, and GE Aerospace’s record against its own contract so far argues for caution.

The second is what the inspection of the defective engine reveals. If the visiting team confirms the transit theory, the fix is largely procedural — tighter handling for the 93 engines still to make the journey — and the sixth engine returns to the line quickly. If the defect turns out to be something else, the questions become harder and the timeline consequences larger. The engine that failed acceptance parameters will face the same scrutiny.

The third is what “realistic” will mean. The Defence Ministry has committed the September review to producing an updated delivery schedule. After more than two years of slippage, the programme’s credibility rests less on the original promises than on whether the next timeline is one everyone involved can actually keep.

The markers to watch between now and then are already defined: a verdict on the snagged engine, an engine tempo from GE Aerospace that finally matches its contract, radar integration progress at HAL, and jets moving from the grounded rows toward the air force’s squadrons. September was always going to be a milestone month for the Tejas Mk1A. It is now shaping up as a verdict.