The Indian Air Force (IAF) is actively working to integrate the Meteor beyond-visual-range air-to-air missile (BVRAAM) onto the upcoming Tejas Mk2, as part of its broader objective to standardize advanced air combat capabilities. However, the effort faces both technological and policy-related challenges, largely due to the indigenous architecture of the Tejas Mk2 and integration restrictions imposed by missile manufacturer MBDA.
The Tejas Mk2 reflects a significant shift in India’s fighter development approach, prioritizing sovereignty and high levels of indigenization. Unlike earlier Tejas variants that relied on foreign radar systems such as Israel’s EL/M-2032 and EL/M-2052, the Mk2 is being designed around the indigenous Uttam AESA radar. With an estimated 980 transmit/receive modules, the radar is expected to deliver improved detection range, enhanced tracking, and superior multi-target engagement capability.
While this indigenous sensor framework strengthens self-reliance and pushes indigenization levels beyond 80 percent, it complicates the integration of foreign-origin weapons like the Meteor missile. MBDA has traditionally enforced strict controls over integration with non-European radar systems due to the sensitive nature of its data links, guidance algorithms, and radar-missile interface protocols.
Effective operation of the Meteor requires deep integration with the aircraft’s fire control system, including access to source codes that enable communication between the radar and the missile’s mid-course guidance system. With the Uttam AESA being fully indigenous, MBDA has reportedly been hesitant to provide such access, creating a key bottleneck.
Despite these constraints, the IAF continues discussions with MBDA to explore possible solutions. One option under consideration is a “black box” integration model, where critical software elements remain proprietary while still enabling operational compatibility. Another potential pathway involves localized production or expanded industrial collaboration to ease technology transfer concerns. However, no definitive agreement has been reached, particularly regarding timelines for integration with the Tejas Mk2 prototype.
At the same time, HAL is planning to integrate the Meteor missile into a second batch of 97 Tejas Mk1A aircraft, indicating that integration may be feasible under specific configurations. This aligns with the IAF’s broader strategy to deploy the Meteor across multiple platforms, including the Rafale fleet, where it already serves as a primary long-range air-to-air weapon.
Parallel to this, India’s indigenous missile development programs are advancing rapidly to reduce dependence on foreign systems. The Astra Mk1, with a range of approximately 110 km, is already operational, while the Astra Mk2—featuring dual-pulse propulsion—is expected to extend engagement ranges to around 160 km. Looking ahead, the Astra Mk3 is being developed as a potential game-changing solution, possibly incorporating ramjet propulsion to rival or exceed Meteor-class performance, thereby ensuring greater strategic autonomy.
