India’s indigenous Tejas Mk1A fighter jet program faces significant hurdles, with the Indian Air Force (IAF) expressing strong concerns over delays pushing initial deliveries beyond two years post-first flight. The primary culprit: Hindustan Aeronautics Limited (HAL) severely underestimated the complex software validation required for the advanced aircraft’s crucial systems. While the Mk1A’s physical structure and hardware are largely complete, integrating critical components like the EL/M-2052 AESA radar and the new Digital Flight Control Computer (DFCC) demands extensive software testing that has fallen drastically behind schedule.

This miscalculation means the IAF may not receive its first fully cleared Mk1A until after March 2026, a stark contrast to HAL’s initial projection of just three to four months after the jet’s maiden flight. These Tejas Mk1A software validation delays compound a critical shortage for the IAF, which operates with only 31 fighter squadrons against a required 42. The problem extends beyond basic integration; a March 2025 weapons trial saw the indigenous Astra Mk1 missile fail to “handshake” with the aircraft’s radar due to software interoperability issues, not hardware defects. Compounding the software challenges are global supply chain disruptions impacting General Electric F404-IN20 engine deliveries. HAL initially expected 30 engines by late 2025 but has received only five.

Despite inaugurating a third production line, the combination of software, radar, missile integration, and engine bottlenecks continues to stall Final Operational Clearance (FOC) and formal induction, leaving IAF leadership increasingly frustrated.