HAL Defers Uttam AESA Radar Integration to Second Tejas Mk1A Order, First 83 to Retain Israeli EL/M-2052 to Avoid Further Delays

HAL Defers Uttam AESA Radar Integration to Second Tejas Mk1A Order, First 83 to Retain Israeli EL/M-2052 to Avoid Further Delays


In a significant update to India's indigenous fighter program, Hindustan Aeronautics Limited (HAL) has revealed a change in the equipment timeline for the Tejas Mk1A.

The highly anticipated home-grown Uttam Active Electronically Scanned Array (AESA) radar will no longer feature on the initial order of 83 Tejas Mk1A jets. Instead, its introduction has been pushed to the upcoming second batch of 97 aircraft.

This development was confirmed by HAL Chairman and Managing Director Ravi Kota during the company’s recent financial conference call.

Previously, the plan was to introduce the Uttam radar starting with the 41st aircraft of the first production run. However, to maintain a steady manufacturing pace, the entire first batch of 83 fighters and trainers will now be equipped with the Israeli-designed EL/M-2052 AESA radar.

The EL/M-2052 radar is currently manufactured domestically by HAL under a technology transfer agreement with Israel's defence electronics industry.

It is a highly capable system, offering the Indian Air Force (IAF) advanced features such as multi-target tracking, beyond-visual-range missile guidance, and robust electronic counter-countermeasures.

By sticking to this established system, HAL aims to avoid the complex testing and certification processes that would inevitably accompany the integration of a new radar system mid-production.

Industry experts note that this decision is primarily driven by the need to stabilise the Tejas Mk1A delivery schedule.

The manufacturing line has already experienced considerable disruptions due to global supply chain issues, most notably the delayed delivery of F404 engines from the American aerospace firm General Electric (GE).

Introducing a new radar at this critical juncture could have further stalled the induction of these vital jets into the IAF, which urgently needs to bolster its declining fighter squadron numbers.

The Defence Acquisition Council (DAC) has already cleared the procurement of the additional 97 Tejas Mk1A jets, where the Uttam radar will finally make its operational debut.

The Uttam AESA radar, designed by the Defence Research and Development Organisation (DRDO), remains a cornerstone of India's push for self-reliance in aerospace technology.

It has already undergone rigorous flight testing on prototype aircraft and is also slated for integration into future platforms like the Tejas Mk2 and the upgraded Su-30MKI "Super Sukhoi" fleet.

HAL also clarified that it will not manufacture the Uttam radar in-house. Rather, DRDO will select a private industrial partner for mass production, from whom HAL will procure the units for the second batch of Tejas fighters.

This strategic deferment ultimately allows HAL to focus on immediate delivery targets while paving the way for complete radar indigenisation in the very near future.
 
Very sad....after spending so much of the publics money there is no accountability or ownership or more importantly planning...they mention near future and that timeline in actuality is 30 years or more...very sad
 
EL/M‑2052 Integration issues.


The EL/M‑2052 itself is not the problem — the integration of its software with Tejas Mk‑1A’s mission computer, EW suite, and DFCC is the real bottleneck. This has created multi‑year delays in Mk‑1A certification and delivery. The issues are software‑level, not hardware‑level, and they directly affect radar modes, weapon cueing, and BVR missile integration.

🛑 What exactly is going wrong with EL/M‑2052 integration?

1. Software handshake problems with Indian avionics

Multiple sources confirm that the radar hardware is solid, but getting the EL/M‑2052 to “talk” to the Indian EW suite and mission computer is the core challenge.

• HAL insiders state the radar is proven, but software integration is taking far longer than expected.
• The DFCC (Digital Flight Control Computer) and AESA radar both require extensive validation, and HAL underestimated the volume of testing.

This is not a wiring or power‑supply issue — it’s protocols, data formats, and multi‑mode radar logic needing deep integration.

2. Radar–weapon communication failures

During 2025 weapons trials, the Astra Mk‑1 missile failed to communicate correctly with the radar, demonstrating that radar–weapon interface software is still unstable.

This is critical because Mk‑1A’s main upgrade is BVR combat capability — and that depends entirely on radar–weapon synchronization.

3. Certification delays due to incomplete radar modes

The IAF refuses to induct aircraft until the radar is fully certified.

• The IAF has received zero Mk‑1A aircraft because the EL/M‑2052, EW suite, and weapons package are not yet cleared.

• HAL claims aircraft are structurally ready, but CEMILAC has not certified the radar‑EW‑weapons integration, blocking induction.

4. HAL underestimated the software validation timeline

HAL originally believed radar integration would take 3–4 months after first flight, but it has now stretched beyond two years.

This is the single biggest reason Mk‑1A deliveries slipped from 2024 → 2026+.

5. Undisclosed performance issues

IDRW reports that the EL/M‑2052 is facing unspecified performance issues on Tejas, despite working on Jaguar DARIN‑III.

This suggests the problem is not the radar itself, but how it behaves within Tejas’ unique avionics architecture (larger antenna, different power supply, different EW suite).

🧩 Why does EL/M‑2052 work on Jaguar but not smoothly on Tejas?

Jaguar DARIN‑III uses:

• Israeli radar
• Israeli/foreign avionics
• A simpler weapons suite
• A legacy architecture with fewer indigenous subsystems

Tejas Mk‑1A uses:
• Indian mission computer
• Indian EW suite
• Indian DFCC
• Indian weapons (Astra)
• A larger, more powerful radar antenna

This creates a complex multi‑vendor integration environment, which is always the hardest part of fighter development.

📌 Summary — The 4 core EL/M‑2052 integration issues on Tejas Mk‑1A

1779143457630.webp

🔮 What happens next?

• Mk‑1A deliveries are unlikely before mid‑2026 at the earliest.
• The first 83 aircraft will continue using EL/M‑2052, not Uttam, to avoid even more delays.
• Uttam AESA will likely appear only in the second batch of Mk‑1A.
 

Forum statistics

Threads
7,238
Messages
65,939
Members
5,393
Latest member
Apurva_Koli
Back
Top