LCA Tejas: An Indian Fighter - With Foreign Help

India’s Light Combat Aircraft program is meant to boost its aviation industry, but it must also solve a pressing military problem. The IAF’s fighter strength has been declining as the MiG-21s that form the largest component of its fleet are lost in crashes, or retired due to age and wear. India’s other Cold War vintage aircraft will face similar problems in the near future.

In response, some MiG-21s have been modernized to MiG-21 ‘Bison’ configuration, and other current fighter types are undergoing modernization programs of their own. The IAF’s fading hope is that India can maintain their fighter numbers until the multi-billion dollar 126+ plane MMRCA sale delivers replacements. Which still leaves India without an affordable overall solution. MMRCA can replace some of India’s mid-range fighters, but what about the MiG-21s? The MiG-21bis program adds years of life to those airframes, but that extended lifespan is still quite finite. By 2020, they’re likely to be gone.

That’s why India’s own Tejas Light Combat Aircraft (LCA) project is so important to the Indian Air Force’s future prospects, and why India’s rigid domestic-only policies are gradually being relaxed, in order to field an operational and competitive aircraft. Even with that help, however, the program’s delays are a growing problem for India. Beyond India, the west’s near-abandonment of the global lightweight fighter market means that choices made in the LCA’s design will also affect its export potential. Which, in turn, feeds back into the overall program’s lifetime costs and viability…

• LCA Tejas: India’s Lightweight Fighter [updated]
  • Radar Love: Weapons & Fire Control
  • Engines & Alternatives
  • In the Navy… Naval LCA
• LCA Tejas: Program, Prospects, and Future [updated]
  • Industrial Team
  • Future Prospects
• Contracts & Key Events [updated]
• Appendix A: DID Analysis & Op/Ed (2006)
• Appendix B: The Kaveri Engine: Keystone, or Killer?
• Appendix C: Additional Readings & Sources

LCA Tejas: India’s Lightweight Fighter

Within India’s force structure, the LCA is largely expected to replace its 400 or so MiG-21 aircraft with a more versatile and capable performer. The MiGs are being retired as age claims them, and even India’s 125 or so upgraded MiG-21 ‘Bisons’ are only scheduled to remain in service until 2016. The LCA’s overall performance is expected to be somewhat similar to India’s Mirage 2000s, with lower top speed but more modern electronics.

The Tejas LCA design uses a tailless compound delta plan that is designed to be unstable, but controllable thanks to advanced flight software and quadruplex fly-by-wire technology. The aircraft is intended for a 9g / -3.5g flight range, and advanced composites, often using co-cured cobonded technology, make up more than 40% of the Tejas airframe including the wings, fin and fuselage. The radome is made of Kevlar.

Composites help to save weight, and can also lower the plane’s radar profile, depending on where they’re placed. Japan’s F-16-derived F-2 fighters also made heavy use of composite technologies, and found some issues with delamination and cracking that required repair and changes. Static and fatigue strength studies on finite element models, and aeroservoelastic studies, have been performed on the Tejas design; nevertheless, only testing and actual service will reveal how it fares.

Preliminary statistics indicate that the Tejas will have a thrust:weight ratio of close to 1:1 in “clean” (unarmed) configuration; the initial Mark I version’s F404-IN20 power plant is rated for 18,700 lb/ 83.18 kN. Maximum speed is expected be about Mach 1.8, though Tejas will not have Mach 1+ supercruise; like most fighters, it will spend the vast majority of its flight time at subsonic speeds. 7 pylons (3 on each wing, one centerline) will allow it to carry up to 4,000 kg/ 8,800 lbs. of weapons, electronics pods, and/or external fuel, up to the maximum takeoff weight of about 12,500 kg/ 27,500 lbs. Unrefueled range is reportedly 850 km/ 460 nm, though this will vary with weapons and fuel loads. Air-air refueling capability can be used to extend that range, if necessary.

Confirmed combat accoutrements will include:

• MIL-STD-1553B databuses
• IAI EL/M-2032 radar
• Elbit DASH helmet-mounted display
• RAFAEL Derby medium range air-to-air missile
• Vympel R-73/AA-11 “Archer” short range air-to-air missile
• RAFAEL LITENING surveillance & targeting pod

The following sub-section goes into more detail about their rationales and capabilities, and discusses other equipment in this area.

Radar Love: Weapons & Fire Control

The plane’s avionics architecture is configured around a 3 bus, distributed MIL-STD-1553B system, using a 32-bit Mission Computer (MC) and software written in Ada. A “glass cockpit” of display screens will provide pilot information, supplemented by Elbit’s DASH helmet-mounted display for commonality with other IAF aircraft.

Radar Failure & Replacement

The Tejas project’s original radar, like its original engine choice, very nearly sank the project entirely. The state-run Aeronautical Development Agency had originally intended to use Ericsson Microwave Systems’ PS-05/A, but decided to develop its own instead. India’s Multi Mode Radar (MMR) program was started in June 1991, with a “Probable Date of Completion” of 6.5 years. More than 15 years later, development was still ongoing as a joint effort by Hindustan Aeronautics Limited in Hyderabad, India’s Electronics and Radar Development Laboratory in Bangalore, and the Centre for Airborne Studies. Even worse, test results for the radar were poor.

By August 2007, even India’s MoD finally admitted that MMR faced serious problems. Radar co-development has now been initiated with Israel’s IAI Elta. Meanwhile, they have offered the EL/M-2032 as an interim solution for Tejas testing and initial fielding, and are discussing the more advanced EL/M-2052 AESA.

IAI’s EL/M-2032 multi-mode radar was originally developed for Israel’s Lavi fighter, and looks set to equip Indian Tejas fighters for the foreseeable future. It already equips India’s Sea Harrier fleet and Jaguar IM strike aircraft., and is popular around the world. It can also be found on some F-16s in Israel and elsewhere, Kfir C10s flown by some Latin American customers, Chile’s upgraded F-5s, Romania’s MiG-21 Lancer upgrades, and South Korea’s F/A-50 lightweight fighter. The radar features modular hardware design, with software control and flexible avionic interfaces, and a TWT coherent transmitter with a low-sidelobe planar antenna. The M-2032 functions in several air-to-air modes, as well as the air-to-ground, air-to-sea, ground-mapping in RBS, DBM, SAR with moving target tracking, and terrain avoidance modes.

Detection and classification ranges will vary depending on the aperture size. A radar adapted to fit in an F-5’s narrow nose will have lower performance than one that fits into a larger F-16. The Tejas’ dimensions suggest that performance may be near the radar’s claimed 80 nautical mile maximums for detection of fighter-sized objects.

Weapons

Unsurprisingly, RAFAEL’s Derby radar-guided fire-and-forget missile will serve as the Tejas’ initial medium range air-air armament. It lacks the range and datalink of Raytheon’s AMRAAM or Russia’s R-77/AA-12, but it has already been integrated with the EL/M-2032 on India’s own Sea Harriers, and equips India’s forthcoming SPYDER mobile anti-aircraft missile systems. Derby reportedly has good seeker cone coverage, which improves performance within its range. In practice, positive identification requirements have kept most aerial fights within that range, anyway. If India’s own Astra MRAAM continues to progress, it might be integrated later, and supplant Derby.

For shorter-range engagements, Derby will be complemented by Russia’s infrared-guided Vympel R-73/AA-11 “Archer,” giving Tejas partial weapon commonality with India’s large MiG fleets. In an area where radar compatibility isn’t critical, this was a decisive advantage. The R-73 is known for its exceptional maneuverability and “wide boresight” seeker cone, a combination that inaugurated the era of 4th generation missiles. There’s even a rear-facing version, which offers enemies a nasty surprise. Its main competitor was believed to have been RAFAEL’s Python 4/5, which doesn’t need to face backward in order to hit targets behind its fighter.

Tejas planes are expected to carry a range of ground attack weapons, from ordinary bombs and unguided Russian S-8 80mm rockets, to precision munitions. They will carry RAFAEL’s LITENING advanced surveillance and targeting pod, giving them long-range looks at ground targets, independent laser designation capability, and (rumored) fleet commonality with India’s Jaguars, MiG-27s, Mirage 2000s, and SU-30MKIs.

Tests for unspecified laser-guided bombs and cluster bombs are expected, though they’re expected to be Russian KAB-1500 and RBK-500 weapons, along with Russian Kh-31/35/39 anti-ship and precision strike missiles. Unfortunately, the MIL-STD-1553B data bus will be an obstacle to integrating GPS-guided weapons. That’s a significant and puzzling omission, given the expected future growth of GPS in weapon guidance.

Engines & Alternatives

With its radar issue solved by a foreign partnership, the fighter’s indigenous Kaveri engine (vid. Appendix B) was left as the project’s biggest unresolved issue. That was resolved with a stopgap, followed by a competition to field a working engine; even so, India’s DRDO continues to pour dollars and time into Kaveri development.

The removal of American arms trade sanctions allowed smooth incorporation of a slightly modified F404-GE-IN20 turbofan in initial Tejas Mk.I production models. The engine weighs about 1,000 kg/ 2,200 pounds, and has produced 19,000 pounds of thrust on afterburner during static tests.

Over the longer term, an international competition for the Tejas Mk.II’s engines had 2 shortlisted competitors.

Eurojet’s rival EJ200 equips the Eurofighter Typhoon. It weighs about 1,000 kg and produces 13,500 pounds of thrust in normal operation, or 20,000 pounds of thrust with afterburners. There were even rumors of a thrust-vectoring version to improve Tejas maneuverability.

GE’s F414 is that company’s more advanced alternative to the F404 family that equips the Tejas Mk.I; it currently equips Saab’s JAS-39NG Gripen and Boeing’s F/A-18 Super Hornet family. It weighs about 2,300 pounds, and can reportedly produce up to 22,000 pounds of thrust on afterburners, but GE has been remarkably coy about its thrust in normal operation. The figures it supplied to India were obviously good enough, however, because the F414 won.

If the Tejas Mk.II ends up with an alternate engine program, it will have to come from a successful Kaveri follow-on, which is under negotiation as a partnership with French engine maker Snecma. DRDO still hopes to offer this option, and convince India’s politicians to mandate it for Tejas Mk.II retrofits.

Unfortunately for the air force, new engines usually mean changes in size and weight distribution, which require changes to a fighter’s design in order to compensate. If an LCA MkII is produced with a different engine, it can also be expected to feature some design changes and additions in order to rebalance the aircraft, add newer technologies, etc. That can be expected to take at least a year, and usually take several years. Sweden’s JAS-39 Gripen, which made a similar shift from Volvo’s F404-derived RM12 in the JAS-39 A-D models, to GE’s F414 for its new JAS-39NG, offers an excellent example.

In the short term, this means that a successful Tejas program is likely to either produce more LCA Tejas Mk.I aircraft than just the initial production run of 48, or accept fielding delays and the risk of expensive rework to initial production Tejas Mk.II planes.

In the Navy… Naval LCA

Indian officials were interested in an improved engine for 2 reasons. One is simply better performance, thanks to an improved thrust:weight ratio. Another is the need for additional thrust, in order to operate the Tejas successfully as a naval aircraft.

India will induct the 40,000t INS Vikramaditya in 2012-2013, after extensive modifications are completed to Russia’s former Admiral Gorshkov carrier. The navy is also proceeding with construction of 2 more 35,000t “air defence ship” Vikrant Class carriers, designed in collaboration with Fincantieri and built in India. Orders have been signed for 46 Russian MiG-29Ks, but India also wants to operate its own planes.

The initial Naval LCA prototypes will be powered by the same GE F404 engine that powers the IAF variant, but production versions are expected to use an improved F414 engine. They’re also expected to have a different name than “Tejas.” Other changes to the Naval LCA are expected to include:

• Dropped nose, for better visibility in high angle-of-attack (nose pointed up) landings
• Leading edge vortex controls that can extend from the edges of the main wing. They help the aircraft sink faster while remaining safe, in order to land in smaller spaces, and can also improve takeoff response.
• Arrester hook to catch landing wires
• Strengthened spine and related systems, to absorb the high impact of carrier landings
• Longer, strengthened undercarriage
• Powered nose wheel steering for better maneuverability on deck
• Fuel dump system that can shed 1,000 kg of fuel from the fighter’s wing tanks, in case of an emergency just after take-off. Fuel weighs a lot, and that added weight can imperil the attempted emergency landing.

Variant paper designs have been produced to this end, and an initial order placed in 2009 began turning those designs into prototypes. April 2012 saw the 1st flight of NP-1, and a 2012 decision gave the go-ahead for initial production of 8 planes, but that isn’t a contract yet.

LCA Tejas: Program, Prospects, and Future

The Tejas Light Combat Aircraft program began in 1983, and is currently in Full-Scale Engineering Development (FSED) Phase-II, under which India’s DRDO was trying to deliver production fighters to the IAF by December 2010. Initial Operational Clearance wasn’t granted until January 2011, and then only with significant waivers. Limited Series Production aircraft in final configuration have arrived, but IOC issues aren’t expected to resolve until June 2011, most weapons haven’t been tested yet, and full operational clearance (FOC) as a day/night, all-weather platform isn’t expected until December 2012. Final Operational Clearance for induction, and formation of a Tejas squadron at Sulur Air Base in Tamil Nadu, isn’t expected until 2013. The first test-flight of the improved and re-engined Tejas Mark-II is currently scheduled for December 2014, with production beginning in June 2016.

When it was originally approved in 1983, the Tejas program’s cost was set at Rs 560 crore (5.6 billion rupees). The cost had risen to over 3,300 crore by the late 1980s, and has continued to rise since. The Times of India places the 2011 program total at 17,269 crore/ $3.77 billion for all variants. So far, 40 Tejas Mk.I fighters have been ordered. Current plans call for another 100 aircraft (mostly Mk.II) for the air force, and up to 60 naval variants for the Navy.

Industrial Team

The Tejas industrial team is weighted toward government participation, which is one of the reasons for its long development cycle. Instead of buying finished and tested equipment from abroad, new designs had to be invented by government research agencies, then tested by themselves until they were ready, followed by integration testing with other elements. These choices were driven by India’s desire for long-term self-sufficiency in many aircraft sub-systems, in order to reduce their dependence of foreign suppliers.

There have also been a wide variety of sub-contracts to Indian firms for Tier 3 or Tier 4 participation to supply tooling, testing equipment, software development, or sub-assemblies. They are not covered in our list above.

Tejas: Future Prospects

The Tejas Light Combat Aircraft’s exact per-plane flyaway price point is not known yet, but the goal is an inexpensive fighter in the $20-25 million range, with performance that compares well to early model F-16s and Mirage 2000s. That combination could make this aircraft a capable export contender around the 3rd World; likely competitors include the market for second-hand F-16s, the Chinese/Pakistani JF-17, and Korea’s T/A-50 Golden Eagle supersonic trainer and light fighter. The Russian MiG-29S/M multi-role fighter may also become a competitor, depending on Russia’s chosen pricing approach.

Before exports can become a reality, however, the Tejas must achieve success in India.

Press Trust of India reports Bangalore-based Aeronautics Development Agency (MoD ADA) R K Ramanathan as promising a 2010 in-service date, while touting a reduction from over 30,000 components to around 7,000. That didn’t come close to happening. The cranked-delta LCA has already undertaken about 1,500 test flights, and plans to field 40-48 aircraft into the first 2 air force squadrons remain on track, but the IAF’s longer term commitment is less certain. They are taking something of a “wait and see” approach, until the final aircraft is delivered with working systems and the “Tejas Mark II” design has shown what it can do.

One the one hand, the project’s long development period, and DRDO’s past performance on defense projects, tend to justify that wait-and-see approach. On the other hand, the project can easily run into danger without adequate military and political backing. On Feb 6/06, The Telegraph in Calcutta reported that:

“Though air headquarters has not said so in public, it is weighing whether it should commit funds because it is anticipating a resource crunch for the big ticket purchases of multi-role combat aircraft – that could cost the exchequer more than $5 billion over 10 years – and other equipment that it has projected as an immediate need.”

The rumored growth of the MRCA foreign fighter program to 170-200 aircraft, naval plans for 32 more ships in the next 10-15 years, and other planned capital purchases do indeed have the potential to squeeze the Tejas. In return, confidence in the Tejas, or the lack of it, will influence India’s choices in the MMRCA buy of 120-200 foreign fighters – an influence that will be reciprocal. The fewer MMRCA aircraft that India can afford at a flyaway price tag of $35 – 120 million, the more attractive a sub-$25 million Tejas looks in order to plus up numbers – as long as it can in fact be produced to that cost level, be delivered on time, and perform at an adequate level.

Every one of those variables is currently in play.

At present, the worst-case scenario for the Tejas program is truncated production at about 48 aircraft. The generally accepted goal is 7 squadrons, or about 168 planes. The best-case scenario would involve full production for the IAF; a serving STOBAR (Short Take Off via ramps, But Assisted Recovery via arrester gear and wires) naval variant in service by 2020; and export successes that drive up production totals and help to finance future updates.

Contracts and Key Events

March 21: Costs. Defence minister Antony answers a Parliamentary question, and provides cost and schedule slips for the LCA Tejas, LCA Naval, and Kaveri engine. Those are reproduced above along with other information. Antony also discusses what’s being done about these slips, which amounts to more oversight and monitoring. That won’t cure a system whose main problem is a lack of accountability or consequences for the state-run development agencies, and whose secondary problem is the system’s own red tape. On the other hand, the answer makes it sound like the government is doing something. Antony adds that:

“Tacit knowledge acquired by the DRDO scientists during this project will also be applied for further aerospace technology. Kaveri spin-off engine can be used as propulsion system for Indian Unmanned Strike Air Vehicle (USAV).”

Readers may note that he is not referring to the LCA Tejas program as a destination for Kaveri, despite DRDO’s wishes in the matter.

March 14/12: 6 squadrons. Indian minister of state for defence M M Pallam Raju tels the Rajya Sabha upper chamber that the IAF plans to induct 6 LCA squadrons over the next decade or so, including 4 squadrons of Tejas Mk.II fighters. Given current schedules, past performance, and the extent of the redesign and testing involved, India may be lucky to induct any Mk.II fighters by 2022. Deccan Herald.

March 11/12: Naval LCA. India’s Sunday Guardian reports that India’s Centre for Military Airworthiness and Certification (CEMILAC) has refused flight certification for the Naval LCA, until the new landing gear’s weight is reduced, and its wing leading-edge vortex controls are redesigned. The US Navy and EADS are reportedly being consulted to help fix the problems.

CEMILAC’s decision will add further delays to a program that is already late, and effectively ends hopes for a March 2012 flight. The naval variant’s initial flight was initially slated to happen by the end of 2010, following a July 2010 roll-out. As of Sept 26/11, it had managed only an Engine Ground Run.

March 10/12: While Tejas continues to make test flights, and has been granted initial certification, final certification and full production continues to face delays, and will not come until late 2013 or even 2014 now.

New test aircraft LSP-7 had a maiden flight, without a chase plane, “to test many indigenously-developed instruments,” as well as the M-2032 radar and DASH helmet. It’s close enough to the final standard that it will be one of the planes offered for IAF user-evaluation trials, but the final-configuration LSP-8 won’t be ready until later in 2012. LSP-8 will be the version presented to CEMILAC for full certification and flight clearance, a necessary step before full production can begin for the two 20-plane orders. The Hindu.

Feb 29/12: HAL, shape up. India’s MoD explains that changes are coming to HAL, and cites the Tejas program as one reason behind the push:

“The Defence Minister Shri AK Antony today asked the Hindustan Aeronautics Limited (HAL) to realign its business processes for strategic alliances and joint ventures, as also, to step up R&D efforts to remain globally competitive…. Keeping in mind the mammoth role that the HAL would assume in the coming years in the aerospace industry and the challenges that it would face, the government has set up an expert group under the chairmanship of Shri BK Chaturvedi, Member, Planning Commission to suggest measures to strengthen and restructure HAL…. the Group will suggest how best the spin offs from HAL order book can be earnest to ensure better involvement of the private industry in the defence sector. It will also suggest measures to enhance the synergies between HAL, the private defence sector and the civilian industry.

“Taking part in the discussion the Members of Parliament appreciated the role played by HAL in the defence arena of the country over the years. They, however, pointed out certain shortcomings such as the delay in the induction of the Light Combat Aircraft in the Indian Air Force, delay in the development of Kaveri Engine, delay in phasing out of Mig-21 aircraft and lack of an aggressive strategy to export HAL products.”

See also March 24/11 entry, The Pioneer | Flight International | IN FOCUS: India advances air force modernisation.

Feb 27/12: Naval LCA. The Indian Ministry of Defence’s Defence Acquisition Council (DAC) has sanctioned the building of 8 Naval LCA aircraft by Hindustan Aeronautics Limited (HAL), and reportedly allocated the necessary funds for a contract. That does not mean a contract has been signed yet.

The 8 planes will be built as a mix of single-seat test fighters and twin-seat trainers, and would begin to add production fighters on top of the ordered fleet of 6 test aircraft. The first flight is announced for sometime in March, though talks last year of a maiden flight in July did not pan out. Business Standard.

Dec 21/11: Kaveri. In response to Parliamentary questions, Defence Minister Antony explains the Kaveri engine’s current development status:

“So far 9 prototypes of Kaveri engines and 4 prototypes of Kabini (Core) engines have been developed. Total 2050 hours of testing have been conducted on various Kaveri and Kabini engines at ground and altitude conditions for various requirements including performance, operability, endurance, environmental, etc. Two major milestones viz. successful completion of Official Altitude Testing (OAT) and completion of first block of flights of Kaveri engine in Flying Test Bed (FTB) has demonstrated the technological capability and maturity of this indigenous effort. Kaveri engine prototype (K9) was integrated with IL-76 aircraft at Gromov Flight Research Institute (GFRI), Russia and flight tests have been successfully carried out up to 12 km maximum forward altitude and a maximum forward speed of 0.7 Mach No. Twenty seven flights for 55 hours duration have been completed on IL-76. Critical subsystems and its associated knowledge know-how and know-why has been acquired in association with Indian public & private sector industries, including certification methodologies.”

Nov 23/11: Kaveri. In response to Parliamentary questions, Defence Minister Antony says that nothing has changed with respect to the Kaveri engine’s successor. He doesn’t put it like that, but that’s the reality. India MoD.

Aug 8/11: Kaveri. In response to questions, the Indian MoD clarifies the status of the Kaveri engine project. There is no signed co-operation agreement with SNECMA, but the Air Force has reviewed the draft technical specification and approved it.

“The Defence Research and Development Organisation (DRDO) has made no agreement with a French firm to develop the Kaveria aero engine to be used for the Light Combat Aircraft, Tejas. However, DRDO is negotiating with M/s Snecma, France for co-development and co-production of Kaveri aero engine for the Light Combat Aircraft (LCA) Tejas MK-II. The project proposal will be put up for Cabinet Committee on Security (CCS) approval after the completion of price negotiation…. IAF has further suggested that the engine design should have minimal impact on the LCA Tejas airframe for future retrofitment.”

If it succeeds, India’s Tejas fleet would have an alternative engine option, much like the popular F-16. Several countries fly F-16s, and even F-15s, with 2 different types of engine (PW F100 or GE F101) in their fleet, as insurance that keeps their air force flying even if an engine type develops problems. First, however, an agreement must be signed. Then, the development project must succeed at a reasonable cost.

July 20/11: Naval LCA. The naval Tejas will probably get a different name. Meanwhile, an F404-IN20-powered naval variant is undergoing ground integration tests at HAL’s Bangalore facility, followed by engine runs and ground runs in the coming weeks. A 1st flight within 3 months is considered optimistic.

Meanwhile, India’s ADA has asked the US Navy to help it define carrier suitability plans, and the US Navy is assisting. Flight International.

May 23/11: Aviation Week reports that the Tejas Mk.I is due to undergo a 2nd phase of night trials. Aircraft LSP-5 reportedly made 6 night flights in April 2011, which tested avionics, the instrument landing system, and integration involving the IAI ELTA multimode radar, Elbit’s DASH helmet-mounted display, and RAFAEL’s LITENING pod. The push to finish night operations clearance will also include items waived for the IAF’s initial clearance (vid. Jan 10/11 entry) – waivers that the service does not intend to grant again.

The next 16 months will see assessments of Tejas’ angle of attack, g-forces and sustained turn rate, with limited series production aircraft #6 arriving to help speed things along. It will also see a greater focus on weapons integratiopn tests – so far, only R-73/AA-11 Archer short-range air-to-air missiles and standard bombs have been tested. Still to go: Laser-guided bombs, cluster bombs, and Russian 80mm S-8 rocket pods. RAFAEL’s Derby medium-range air-to-air missile isn’t set to test until mid-2012, and the IAF also expects Russian Kh-31/35/39 anti-ship and precision strike missiles as part of the Tejas Mk.I’s intended configuration.

March 24/11: HAL. India’s Business Standard reports that the Indian DRDO is pushing HAL to outsource some Tejas production or set up joint ventures, in order to meet required delivery schedules and keep the IAF’s fighter fleet at acceptable numbers. The current line can reportedly produce just 8 planes per year, and a high-level HAL team has reportedly toured Boeing, Lockheed Martin, and Eurofighter GmbH facilities.

That the DRDO should be making such a request is nothing short of revolutionary. HAL has 2 serious problems, however, which make such a different approach thinkable for India’s bureaucrats. One is low real orders for Tejas. As one HAL executive put it: ”...how much money could we have realistically invested in a production line?... So far, future Tejas orders of 100-120 more fighters are only plans.” The other problem is the load level on the state-owned firm’s Aircraft R&D Centre, which is is simultaneously trying to develop the Tejas Mark II; the Sitara Intermediate Jet Trainer (IJT); the Sukhoi-HAL Fifth Generation Fighter Aircraft (FGFA); and the Irkut-HAL Multi-Role Transport Aircraft (MRTA). The firm is also developing Dhruv helicopter variants, including a light attack helicopter. That’s a tremendous amount of competition for attention and resources, and HAL itself will face those strains if/when each project becomes a production demand.

Other likely candidates for partnerships wold have to include France’s Dassault Aviation, Sweden’s Saab, and Israel Aerospace Industries, as well as BAE and Northrop Grumman. The latter 3 firms have considerable experience as fighter program sub-contractors. Northrop Grumman is looking to sell its E-2D AWACS and Global Hawk UAVs to India; while IAI supplies a range of equipment to India already, and has industrial partnerships in place. So, too, does BAE, who is already working with HAL to produce its Hawk advanced trainer jets in India.

Feb 14/11: Tejas runs the Derby. Indian Aeronautical Development Agency director P.S. Subramanya says they have picked RAFAEL’s Derby as the Tejas’ initial beyond visual range air combat missile. He expects a contract by March 2011, with delivery expected in the second half of 2012, in time for the final phase of Tejas Mk.I testing.

Derby has range limitations, and was accepted on India’s Sea Harrier fleet despite not meeting the program’s original range goals. It also lacks a datalink. On the other hand, it offers a fire-and-forget weapon that’s already in India’s inventory, and integrated with Tejas’ EL/M-2032 radar, possessing what’s reported to be a wide boresight cone. It’s also true that given the need to avoid fratricide and positively identify targeted aircraft, most aerial engagements have taken place within Derby’s range, and future conflicts involving India are expected to feature that same limitation.

Long-term plans were to deploy the locally developed Astra missile as the Tejas BVRAAM, but in 2010 India decided to use a foreign missile and get Tejas into operational service. If Astra succeeds, it can always be integrated later. Meanwhile, Tejas gets ordnance commonality with India’s Sea Harriers, which also carry the EL/M-2032 radar, and with India’s SPYDER anti-aircraft systems. Defense Update | Livemint | RAFAEL on Derby | ACIG on Derby.

Feb 3/11: Kaveri. DRDO hasn’t given up trying to force the issue with its long-delayed Kaveri engine. After proposing it as a naval turbine, the newest gambit is to specify it for a proposed twin-engine Advanced Medium Combat Aircraft (A-MCA), which would be developed by 2020 and operational by 2025. The proposal is an aircraft somewhat comparable to America’s F-35 – not an encouraging comparison, given that plane’s development costs.

Government acceptance of that plan would buy the engine project another decade, but the question is whether the A-MCA project is even realistic. India’s M-MRCA medium fighter competition hopes to field an advanced 4+ generation plane by 2015, but deliveries will take years, and real operational capability isn’t likely until 2016 or later. Meanwhile, the 2020-2025 time frame is also the expected window for India’s FGFA 5th generation collaboration with Sukhoi. Both are very big budget programs, even as India looks to field a much larger Navy to counter Chinese ambitions in the Indian Ocean basin, and faces a growing need for expensive ballistic and cruise missile defenses. In that environment, MCA could easily find itself fighting hard to avoid becoming yet another sidelined Indian technology demonstrator project.

DRDO also hopes to muscle the Kaveri v2 engine into the Tejas, however, by getting the Indian government to swap the engines in when the initial 40 GE F404 equipped Tejas Mk.Is come in for their scheduled overhauls, during the 2015-2020 time period. Flight International | The Hindu | UPI.

Jan 31/11: Kaveri. Livemint reports that India’s DRDO expects to close price negotiations for a Kaveri joint venture (JV) with France’s Snecma by the end of February 2011, following over 2 decades and INR 28.8 billion spent on the project in India. DRDO declined to reveal the estimated cost of the Snecma-GTRE project, which reportedly aims to produce a viable competitor to the GE F414 that powers the F/A-18 Super Hornet family, Saab’s JAS-39 Gripen NG, and will almost certainly power the Tejas Mk.II.

Reports suggest that Snecma will bring in critical technology for the hot engine core, which is key to the 38% thrust gain sought over existing Kaveri models, while DRDO’s Gas Turbine Research Establishment (GTRE) will work on the “cold” sections around it. GTRE would be left with complete know-how and intellectual property rights for the engine,which will also need to become lighter.

Jan 10/11: Tejas IOC. The Tejas LCA is given Initial Operational Clearance by the Indian Air Force, marking their first induction of an Indian designed and built front line fighter. It has been a long road. The Hindustan Times reports that: “The government has so far pumped Rs 14,428 crore into the LCA programme which was pegged at Rs 560 crore when conceived in 1983.” The program cost was set at over 3,300 crore by the late 1980s, and has continued to rise. At today’s exchange rates, the INR 144.28 billion figure translates into about $3.15 billion. The Times of India places the program total even higher, at 17,269 crore/ $3.77 billion for all variants.

Note that India’s IOC designation is not the same as Initial Operational Capability for America’s military, which represents a combat-ready unit. India doesn’t have that yet, and Tejas receives this designation without all of its advertised capabilities, such as air-air engagements using radar-guided missiles. Indeed, subsequent reports reveal that key criteria for even minimal operations were waived, including wake penetration tests, lightning clearances, and some basic all-weather and day/night items. What India’s IOC does, is it allows IAF pilots to begin flying it.

Indian Air Force chief P.V. Naik says that Final Operational Clearance for induction and formation of a Tejas squadron isn’t expected until 2013 or 2014, an event that will take place at Sulur Air Base in Tamil Nadu. The first test-flight of the Tejas Mark-II version is currently scheduled for December 2014, with production beginning in June 2016. Indian Government | Economic Times of India | The Hindu | Hindustan Times | IBNLive | LiveMint | New Delhi TV | Sify | Times of India | Times of India op-ed || BBC.

Nov 21/10: Cost. The Times of India places the cost of India’s Tejas program at 17,269 crore, or over $3.7 billion. The report adds:

“Latest figures also show each of the first 40 Tejas fighters will cost around Rs 150 crore [DID: about $33 million], over and above the huge developmental cost…. Tejas, incidentally, has clocked around 1,420 flights with 10 prototypes till date. Its FSED (full-scale engineering development) Phase-I till March 2004 cost Rs 2,188 crore [DID: 1 crore = 10 million rupees]. The Phase-II, to be completed by December 2012, will cost another Rs 5,778 crore. To add to that, there is fabrication of two Tejas Mark-II, with alternate engines, to be completed by Dec 2018 for Rs 2,432 crore, along with development of indigenous technologies for Rs 396 crore. Naval Tejas FSED Phase-I, in turn, is to be completed by Dec 2014 for Rs 1,715 crore, with Phase-II slated for completion by December 2018 for another Rs 1,921 crore.

Tejas will, of course, also be powered by American GE engines, with its indigenous Kaveri engine floundering despite Rs 2,839 crore being spent on its development since 1989. Towards this, India recently finalised a $822-million deal for 99 GE F-414 engines.”

It is very normal for the first production sets of a fighter to cost far more than fighters at full-rate production, with figures of double or even triple the price common for aircraft with very long production runs. India’s goal of a $20-25 million fighter at full rate production may still be achievable, but it will bear close watching.

Nov 6/10: F414. During President Obama’s visit, the White House provides further details regarding the F414 engine order, which it places at 107 engines:

”...Upon finalizing the contract, General Electric’s facility in Lynn, Massachusetts, and other sites across the United States will be positioned to export almost one billion dollars in high technology aerospace products. This transaction is tentatively valued at approximately $822 million, all of which is U.S. export content, supporting an estimated 4,440 jobs.”

This is strictly true, since any contract with GE would be 100% export content, but the deal itself may still contain provisos for technology transfer and related contracts in India. UK Financial Times Beyond BRICs blog | Hindu Business Line | Indo-Asian News Service (IANS) | NDTV | Sify | WSJ India Real Time blog.

Nov 3/10: At the end of the India-UK “Indra Dhanush 2010” exercise, Indian Air Chief Marshal P V Naik tells the media that LCA Mark-I will be inducted into operational squadrons by the middle of 2011, while the LCA Tejas Mark-II should be operational in the next 2-3 years, as “the process of selection of engine for LCA Mark-II is nearing completion.” It doesn’t happen that way.Deccan Herald.

Nov 1/10: Aviation Week reports that LSP-5, the 11th test jet and 1st final configuration Tejas Mk I aircraft, is readying for flight trials as the ADA tries to meer a Dec 27/10 deadline for release-to-service certification. Changes include internal cockpit lighting for night flying, a revised internal communication set similar to HAL’s Druhv helicopter, and National Aerospace Laboratories’ auto-pilot mode. Aviation week adds that:

“If the delivery schedules are met, then the Indian Air Force will have LSP-7 and LSP-8 for user evaluation trials by March 2011. LSP-6 will be a test vehicle for high angle of attack. The Tejas squadron is expected to be in Bengaluru by mid-2011 and the first two series production aircraft (SP-1, SP-2) also should be ready by then.”

Oct 25-28/10: Engine II. Report, and denial. After NewsX’s Vishal Thapar broadcasts a reports that a Eurojet consultant has been expelled from India for illegally obtaining information on GE’s bid, trying to substitute a new Eurojet bid by offering a monetary inducement, and then planting media reports that Eurojet was ahead on price. Thapar also claims that this is why the Indian MoD took the unusual step of announcing GE as its low-cost bidder, before a contract was signed.

The follow-on effects could be very severe if true, making it very difficult for India to pick the Eurofighter as its M-MRCA medium fighter. Eurojet’s communication agency subsequently issues the following denial. See Milplex | India Defence:

“Eurojet Turbo GmbH categorically denies unfounded allegations made in the NewsX report titled ” India expels arms dealer”, authored by Vishal Thapar and released on 23 October 2010. The report lacks any factual base and is a work of fiction.”

Oct 1/10: Engine II – F414. India’s Business Standard may want a word with its sources. GE announces that its F414 engine has been picked to power the Tejas Mk.II fighter. India’s Aeronautical Development Agency (ADA) will order 99 jet engines, with GE Aviation supplying the initial batch of F414-GE-INS6, engines and the rest manufactured in India under transfer of technology arrangements. When questioned by DID, GE sources confirmed that this is not a contract yet, merely preferred bidder status.

The selection of GE’s F414 deepens a relationship that has supplied 41 earlier model GE F404 engines so far, in order to power initial Tejas LCA Mk.I fighters and LCA Naval prototypes. GE describes the F414-GE-INS6 as “the highest-thrust F414 model,” without offering specifics, but is has been working on an F414 Enhanced Performance Engine. The INS6 will add single-engine safety features in its digital controls, something GE also installed in the F414 variant powering one M-MRCA candidate, the JAS-39 Gripen NG.

Sept 20/10: Engine II. India’s Business Standard reports that the European EJ200 engine may have the edge in the competition to supply the Tejas Mk.II fleet’s powerplants:

“Informed sources have told Business Standard that when the bids were opened last week, European consortium Eurojet bid $666 million for 99 EJ200 engines, against US rival General Electric, which quoted $822 million.”

Both engines have been ruled technically suitable, so the lower priced bid will win, but the bidding process isn’t 100% final yet. The paper also quotes Air Vice Marshall Kapil Kak (ret.) of the Indian Air Force’s Centre for Air Power Studies, who draws the obvious conclusion:

“It is as clear as daylight. Selecting the EJ200 for the Tejas would boost the Eurofighter’s prospects in the MMRCA contest. Its engines, which form about 15-20 per cent of the cost of a modern fighter, would be already manufactured in India for the Tejas [after the 1st 10 were built abroad]. For the same reason, rejecting the GE F-414 would diminish the chances of the two fighters [F/A-18 E/F Super Hornet and JAS-39NG/IN] that fly with that engine.”

Aug 25/10: Kaveri. Defence Minister Shri AK Antony updates progress in the Kaveri engine in a written reply to Shri N Balaganga of India’s Rajya Sabha (upper house of parliament). It’s phrased in terms of what DRDO is doing as development and testing continues, and gives various reasons why the engine is so late. It does not mention that the IAF isn’t interested, except to note at the end that “LCAs are, meanwhile, as decided by user, being fitted with imported engines.” Unlike some Indian programs, the Kaveri program has managed to spend most of its yearly budgets; over the last 3 years, these expenditures have been:

2007-2008: INR 1,525.1 million
2008-2009: INR 1,535.4 million
2009-2010: INR 1,220.6 million

As of Aug 25/10, INR 100 million = $2.15 million, so INR 1.2206 billion = $26.05 million.

July 6/10: Naval LCA. NP1, the first naval Tejas prototype, is rolled out. HAL will build NP1 and NP2 for testing, which will take place at a new facility in Goa. The naval variant adds a tailhook, strengthened undercarriage, leading-edge vortex controllers to slow down landings, auto-throttles, and a fuel dump system.

May 5/10: Engine II. GE describes 3 of the programs underway to improve its F414 engine. The most relevant is probably the F414 EPE (Enhanced Performance Engine), which has a new fan to increase airflow, and aims to increase thrust by 20%. It is explicitly “targeted for potential international customers,” which includes India’s Tejas Mk.2.

The US Navy wants the F414 EDE (Enhanced Durability Engine), which uses an advanced high pressure turbine and 6-stage high pressure compressor (HPC) that offers a 2-3X hot-section durability gain and reduced fuel consumption. F414 EDE forms the base of the EPE engine, but the gains will not be the same in both engines, owing to other design differences.

Crowded India may also appreciate the retrofittable F414 noise reduction kit project, with serrated edges where each “lobe” penetrates into or out of the primary airflow and generates a secondary flow, reducing jet noise by 2-3-decibels. The USN has identified funding for a program to further test and mature the technology to prepare it for incorporation in the USN F414 engine fleet, with work scheduled to continue through 2011. GE Aviation.

Feb 3/10: Engine II. Eurojet says it will share single-crystal engine blade technologies with India if Eurofighter wins MMRCA, or the EJ200 engine is selected for the LCA Tejas Mk2.

Feb 2/10: Indian defence minister AK Antony watches flight demonstrations by twin-seat (PV-5), and single-seat (LCP-2) Tejas test aircraft, and declares: “Serious doubts were raised about Tejas…. Now I can proudly say we will fly our own fighters.” He states Cabinet Committee of Security approval to add Rs 8,000 crore (about $1.73 billion) to the 27-year program for continued air force and naval development, and development of a new engine for the Mk.2, and expresses confidence in final operational clearance for the Mk.1 version by end of 2012. Antony also agreed that the government is in talks with parties abroad for the development of that Mk.2 engine, but would not be more specific.

The Indian Air Force has already ordered 20 LCAs, and has reportedly expressed interest in ordering another 20 aircraft. Meanwhile, the Navy is building 2-seat trainer (NP1) and a single-seat fighter (NP2) prototypes, with NP1 nearing completion of equipping after the structural assembly. it is scheduled to roll out by April 2010, followed by a hoped-for first flight in June 2010. The single-seat NP2 is scheduled for its first flight by June 2011. India’s Business Standard | The Hindu | Indian Express | Times of India | Agence France Presse | The Asian Age.

Dec 31/09: Kaveri. The Hindu reports that India’s Defence Research and Development Organisation (DRDO) has been given government permission to accept an offer from France’s Snecma to ‘partner’ with the Gas Turbine Research Establishment (GTRE) to jointly develop a new version of the Kaveri jet engine. Senior GTRE officials tell The Hindu that talks could begin early in 2010. When that might result in a signed contract is anyone’s guess.

This article’s Dec 26/08 entry covers the verdict of a senior Indian committee, which had recommended against the DRDO-Snecma collaboration. The Hindu highlights the Matheswaran team’s criticism that using Snecma’s fully developed ‘Eco’ engine core would not create sufficient transfer or control of technology, but reports:

“Snecma, which indicated that an engine run of at least 250 is required to make their offer economically viable, agrees that an existing core would be at the heart…. will take at least five years before the first production engine comes out. Snecma chairman and chief executive officer Philippe Petitcolin told The Hindu: “Yes we first stated a 15-year period to hand over the design technology, but now we have indicated that the technology can be given as fast as the Indians can assimilate it.”

Note that the article does not indicate commitment to use the “Kaveri II” engine for any particular purpose, or offer a likely timeline. Rather, the emphasis seems to be on continuing to develop India’s industrial capabilities, rather than fielding an operational engine contender. StrategyPage places the cost of that collaboration at $200 million, but this must be an estimate, as no firm deal has been negotiated. See also Sri Lanka Guardian. See also Aug 20/08 entry.

Dec 14/09: Kaveri. In a written Parliamentary reply, Defence Minister Shri AK Antony responds to Shri Gajanan D Babar:

“The proposal on the Kaveri-Snecma engine joint venture for the Light Combat Aircraft (LCA) Tejas is under consideration of the Government. Request for Proposal (RFP) for procuring 99 engines have been sent to two short-listed engine manufacturers, namely GE F414 from General Electric Aviation, USA and EJ200 from Eurojet Germany. The engine houses have responded to the RFP. Both Commercial and technical responses have been received for procurement of 99 engines along with Transfer of Technology.”

Dec 7/09: A Parliamentary response from defense minister Antony offers details regarding the initial Tejas Mk.1 contract:

“A contract for procurement of 20 Tejas Light Combat Aircraft (LCA) in Initial Operation Clearance (IOC) configuration, along with associated role equipment, reserve engines, engine support package, engine test bed and computer based training (CBT) package from Hindustan Aeronautics Limited (HAL) was signed in March 2006. The total contract cost is Rs. 2701.70 crores.” [currently about $580 million]

Dec 4/09: Radar. DRDO’s Bangalore-based Electronics & Radar Development Establishment (LRDE) reportedly invites global bids to become the development partner for a Tejas active electronically scanned array (AESA) radar. This would presumably replace the IAI Elta EL/M-2032 derivative that will requip Tejas Mk.1 fighters.

The Active Array Antenna Unit (AAAU) would be supplied by the development partner. Responsibilities would include “detailed design, development and realisation” of the antenna panel (main antenna, guard antenna and sidelobe cancellation antenna), transmit/receive modules/groups, the RF distribution network (RF manifold/combiners and RF interface), antenna/beam control chain (T/R control and T/R group control), and array calibration/BITE among other areas. Livefist.

Nov 26/09: Tejas PV-5, a 2-seat trainer version, makes its maiden flight. The Deccan Herald says that commonalities between the 2-seat trainer and Tejas naval version will help that sub-program as well, but it will take hundreds of flights over a year or more before the trainer version can be qualified for use by IAF, as a key step in pilot training and induction of the single-seat fighter into IAF operational service.

Sept 28/09: US red tape. India’s Business Standard reports that Lockheed Martin was selected in June 2009 as a consultant for developing the Naval version of the Tejas. Lockheed Martin has no serving carrier-borne fighters, but they’re developing the F-35B STOVL and F-35C Lightning II for use from carriers.

Unfortunately, delays in US government approval has led DRDO’s Aeronautical Development Agency to recommend that another consultant be chosen instead; Dassault (Rafale) and EADS (no carrier-borne aircraft) were recommended as alternatives,and EADS was eventually picked. Lockheed Martin is still fighting to get through the red tape and salvage the contract, and may continue trying until V K Saraswat, India’s Scientific Advisor to the Defence Minister, makes a decision.

This has happened before, and recently. Boeing was the front-runner for a similar role with respect to the main (IAF) version, and would be a logical consultant for any naval version – but the Indian MoD awarded EADS that contract in early 2009, after the US government failed to grant Boeing a Technical Assistance Agreement clearance in time.

Aug 4/09: Engine II. Flight International reports that the Eurojet consortium has done tests regarding the EJ200’s fit into the Tejas’ space, and believes itself to be in a strong position for the expected 99-engine order to equip the Tejas Mk.II. The RFP response date is Oct 12/09.

Aug 3/09: Kaveri. India’s DRDO is attempting to resurrect the Kaveri engine project, but the IAF’s lack of enthusiasm is pointed. MoD release:

“Defence Research and Development Organisation (DRDO) has offered to co-develop and co-produce 90 kN thrust class of upgraded Kaveri engine with M/s Snecma, France to meet the operational requirement of Light Combat Aircraft (LCA), Tejas with 48 months from the date of project inception…. The proposal for co-development was considered by Indian Air Force. Indian Air Force has suggested a proven engine that is already in production and flight worthy for meeting immediate requirement. Request for Proposal (RFP) has been issued to reputed engine manufacturers.”

A separate MoD release gives December 2012 as the target date for the LCA Tejas Mk.I’s “final Operational Clearance,” adding that project oversight currently involves a high level review by the Chief of Air Staff once per quarter, and by the Deputy Chief of Air Staff once per month.

March 4/09: India Defense reports that a multi-agency team is carrying out 2-weeks of Phase 2 weapon testing for the LCA Tejas. The focus is on safe separation, aerodynamic interference data, and complex weapon release algorithms in different modes of release. Note that the tests still involve aerodynamics, rather than full weapons system integration.

Feb 25/09: Government of India:

“A contract for 20 indigenous Light Combat Aircraft (LCA) has been signed. One IAF squadron is expected to be equipped with this aircraft in 2010-11. Government is not planning to set up a hi-tech facility at Nagpur costing about Rs. 300 crores [3 billion rupees, or about $60 million] for indigenizing components of these aircrafts. Product support including spare parts will be supplied by the vendor as per the terms of the contract that will be concluded.”

Feb 17/09: Engine II. Flight International reports that the Eurojet engine consortium may be about to change the competitive field for the expected RFP to equip LCA Tejas MkII aircraft. The firm has been working on a thrust-vectoring model of its engine, and the magazine reports that it will be offered to meet India’s expected RFP for up to 150 engines.

The Eurofighter is also an MMRCA medium fighter competitor, and twin wins for Eurojet could offer India important commonality benefits, even as they justified an in-country production line. Thrust vectoring would also offer the Tejas a level of maneuverability and performance that could be a difference-maker in combat, and on the international market. The Eurofighter is considered a long shot to win the MMRCA competition, however, and timelines could become an issue. Flight tests of a thrust vectoring EJ200 engine are not expected to begin for another 2 years.

Feb 6/09: Engine II. The Press Trust of India quotes Aeronautical Development Agency (ADA) Director P Subrahmanyam, who says that India’s state-run DRDO is still looking for partners to develop the indigenous Kaveri engine. That hasn’t stopped the Ministry of Defence’s ADA from preparing a competition to equip the LCA Mark II version from 2014 onward, after the initial aircraft are fielded with F404-IN-20 engines:

“We are looking to procure either the GE-414 from US or European consortium Eurojet’s EJ 200 to fly with the LCA Mk II version [after going through offers from various global manufacturers]. Request for Proposals (RFP) is just about to go out and very soon it would be floated.”

Eurojet’s EJ200 equips the Eurofighter Typhoon, while GE’s F414 equips Saab’s JAS-39NG Gripen and Boeing’s F/A-18 Super Hornet family. All 3 of these fighters are competitors in India’s MMRCA, which aims to buy at least 126 medium multi-role fighters to fill the gap between Tejas LCAs and India’s top-tier SU-30MKIs.

The article appears to indicate that India would be looking to switch production to the new engines after low-rate initial production equips the first 2 IAF squadrons with 48 aircraft. In practice, required engineering changes and aircraft testing make such an early switch unlikely.

Jan 29/09: AoA issues. Indopia reports that India’s DRDO/ADA and HAL are proposing a $20 million collaboration with EADS to assist with flight trials, and help to increase the fighter’s flight envelope. Performance at high “angles of attack,” in which a fighter’s nose and wings are tilted at steep angles, will reportedly be the focus for EADS efforts if the deal goes through.

At any aircraft’s critical angle of attack, the wing is no longer able to support the weight of the aircraft, causing a tail slide that generally worsens the problem and can lead to an aerodynamic stall. Different aircraft have different critical angles of attack, and design changes can lead to an expanded range for safe, sustained flight maneuvers. In some cases, such as India’s Sukhoi 30MKIs with their modern triplane configuration, the design’s flight envelope can become so large that maneuvers like the near 90 degree “Cobra” become safe and routine.

Jan 23/09: Flight #1,000. The Tejas LCA completes its 1,000th test flight since the first 18-minute flight by Technology Demonstrator-1 on 04 Jan 4/01. Frontier India | The Hindu | The Times of India.

Dec 26/08: Kaveri. The Hindu reports that a committee set up by the IAF in September 2008 has recommended against Snecma’s offer (see Aug 20/08 entry). The report says that the result would not be a co-designed, co-developed engine, but rather a license production arrangement. The group recommends continued development of the Kaveri engine and its core technologies instead, despite the failures to date.

These conclusions are less surprising when one examines the committee’s composition. Air Vice Marshal M. Matheswaran chaired the group, which included representatives from India’s state-run Aeronautical Development Agency (ADA), Hindustan Aeronautics Limited (HAL), the Centre for Military Airworthiness and Certification, and IAF officers posted at ADA, the National Flight Test Centre and the Aircraft Systems and Testing Establishment. All are state-run groups that have been involved in the Kaveri’s ongoing development, and have strong incentives to protect that turf.

Dec 13/08: A Tejas fighter prototype lands at Leh air base in the high-altitude Ladakh region of Jammu and Kashmir, at an altitude of 10,600 fee. Leh is one of the highest airfields in the world, with a temperature variation ranging from 5 to -20 C/ 41 to -4F. .

That was the whole point, of course: perform cold weather testing, while making an assessment of the aircraft’s performance in high-altitude conditions, without the confounding influence and additional challenge of high temperatures. India Defence

Oct 3/08: Radar. The Hindu newspaper relays news from ADA Programme Director P.S. Subramaniam that the Israeli Elta “EL/M-2052” radar has already undergone tests on the flight test bed and ground rig in Israel, and “airworthy units” are expected to arrive early next week.

They probably meant to print M-2032. The Elta multi-mode radar will be an “interim option” until India’s indigenous radar program performs to the required standard. Because the indigenous radar has failed to perform to standard, the ADA has reportedly been running weaponization tests on the Tejas using a weapon delivery pod, and has been forced to keep critical tests on hold.

Aug 20/08: Kaveri. The Wall Street Journal’s partner LiveMint.com has an article that more or less sums up the Kaveri project in a nutshell, and also the DRDO: “In aircraft engine development, you cannot set a timeline.” The article interviews T. Mohana Rao, director of India’s state-run Gas Turbine Research Establishment (GTRE). Rao explains why the Kaveri engine is effectively dead as a fighter aircraft engine, leaving GE’s popular F404-GE-IN20 variant to power the Tejas for at least the next 4 years.

Rao quotes the Kaveri’s performance at 11,000 lbs./ 5,000 kg dry thrust at sea level, and 16,500 lbs./ 7,500 kg thrust on afterburners. That’s about 1,000 lbs./ 400 kg short of specifications. The engine is also overweight by 330 lbs./ 150 kg, and has yet to perform long-endurance tests to assess its durability.

The GTRE cannot promise any date for successful delivery, and so political approval was granted to form a partnership with a foreign engine firm on a risk-sharing basis. Russia’s NPO Saturn and France’s Snecma responded, while GE, Rolls-Royce, and Pratt and Whitney declined. After almost 2 1/2 years, the GTRE chose France’s Snecma, but there is no contract yet because the government requires consultation with the Indian Air Force before any contract and requirements are signed.

Snecma’s proposal involves an engine core (compressor, combustor and high-pressure turbine) called Eco. Snecma would have a workshare of 45%, and GTRE’s would be 55%, with nearly 85% of the manufacturing within India. Snecma says the aircraft could be certified for fitting in the Tejas within 4 years. Assuming that project remains on time, of course. The policy question is whether this outcome was predictable from the outset. As the Live Mint article notes:

“Nearly 20 years after it promised an indigenous engine to power India’s light combat aircraft Tejas, the… country’s sole aero engine design house, is now seeking outside help….”

Aug 13/08: Kaveri KMGT. The DRDO’s GTRE in Bangalore believes it may have found a use for the Kaveri engine, in naval vessels. Using the core of the Kaveri engine, plus a low-pressure compressor and turbine, the engine would become a gas-fired 12 MW propulsion unit in warships up the he Rajput Class, or find uses as on-shore electricity generators. A Kaveri Marine Gas Turbine (KMGT) has been transported to naval dock yard at Vishakapatnam, and installed on to the marine gas turbine test bed there. Yahoo! India | RF Design.

The Rajput Class “destroyers” are modified Russian Kashin-II Class ships, though their top weight of just under 5,000 tons would mark them as large frigates in many navies.

Aug 3/08: Kaveri. The Wall Street Journal’s partner LiveMint.com reports that France’s Snecma will partner with India’s DRDO to develop a new engine, sidelining the Kaveri project.

“GTRE has spent nearly Rs1,900 crore of the Rs2,800 crore that was sanctioned since an engine project Kaveri, named after the river in southern India, began in 1989…. Vincent Chappard, a Snecma spokesman in France, said he could not immediately confirm the development.”

While the IAF waits for Snecma’s efforts, reports also suggest that the DRDO’s Aeronautical Development Agency has invited both General Electric and Eurojet Turbo GmbH, a European engine consortium, to bid for higher-powered interim engines. GE offers the F414, and the Eurojet 2000 already has higher thrust, but the engines will have to fit the Tejas’ design – or vice-versa. These engines would be slated for Tejas aircraft produced beyond the initial 48 plane order, but before any indigenous engine is certified. WSJ partner Live Mint | domain-b

March 4/08: Radar. There are reports that Europe’s EADS has offered to co-develop an active electronically scanned array (AESA) radar with India, for installation on board the Tejas fighters. Work is currently underway on an AESA radar to equip its Eurofighter, which is a long shot in India’s 126-190 aircraft MMRCA fighter competition.

The nature of AESA radars makes scaling their size possible while retaining high commonality with larger versions, with the main difference being less power and hence slightly lower overall performance. Northrop Grumman, for instance, whose AN/APG-80 AESA radar would equip Lockheed Martin’s F-16 E/F contender, and whose APG-81 equips the forthcoming F-35 fighter family, introduced its AESA Scalable Agile Beam Radar (SABR) at Singapore’s February 2007 air show. It’s designed to equip existing F-16 fighters with no modifications required, and is advertised as being scalable to other platforms.

A win for EADS in this area offers to solve a problem for India, while creating a commonality hook for the Eurofighter – or at worst, a supplier diversification option for India that will help EADS catch up in this key technology area by adding external funding.

March 3/08: Indian Defence Minister Shri A K Antony responds to a Lok Sabha (lower house of Parliament) question by saying that the Tejas flight test program is:

”...progressing as per the schedule. So far, 829 flight tests have been completed. Efforts are being made to accelerate the flight tests…. Presently, no need is felt for strategic partner. To complete the project at the earliest, a top level review is being conducted by the Chief of Air Staff once in every quarter and review by the Deputy Chief of Air Staff once in every month. So far, Rs. 4806.312 cr [DID: 48.063 billion rupees, or about $1.19 billion at current conversion] have been spent on development of various versions of Light Combat Aircraft.”

Oct 25/07: AA-11. The Tejas fires a missile for the first time: Vympel’s short-range, IR guided AA-11/R-73 Archer. Test aircraft PV-1 fired the missile at 7 km altitude and 0.6 Mach within the naval air range off the coast of Goa, marking the beginning of weaponization as a prelude to initial operational clearance (IOC) phase of the Tejas program. The main objectives of test firing were to validate safe separation of the missile, the effect of missile plume on the engine’s air-intake and on composite structures, the workings of the stores-management displays and software, and quality assessment. India DoD release | Times of India.

While the beginning of weaponization is a significant event, the state of the fighter’s indigenous radar development means that the critical weaponization event for the Tejas LCA will be its first successful test-firing of a radar-guided missile.

Aug 13/07: Radar – IAI. Defence Minister Shri AK Antony states the obvious in a written reply to Shri Sugrib Singh and others in Lok Sabha, but adds new information concerning foreign cooperation:

“There has been a time and cost overrun in the said project. The project to develop two MMR systems for ground testing was sanctioned at a cost of Rs.62.27 crore. This activity was completed in 2004 at a cost of Rs.105 crore.

Yes, but see poor testing results in the April 8/06 and May 1/06 entries, below. He does not mention them, but effectively concedes the point by adding that:

A co-development activity of MMR has been initiated for Limited Series Production and Series Production with M/s ELTA Systems Ltd, Israel, which has experience in developing similar types of radars. To expedite the project, close monitoring of activity at the highest level of Hindustan Aeronautics Limited (HAL) management has been put in place.”

See also India Defence follow-on re: the IAI Elta/ HAL agreement.

April 26/07: The of the Limited Series Production Tejas jets (LSP-1), makes its successful maiden flight at HAL airport in Bangalore, reaching an altitude of 11 km/ 6.6 miles and a speed of Mach 1.1 during the 47 minute flight. According to the Indian government release, LSP-1 marking the beginning of series production of Tejas for induction into the Air Force.

March 1/07: India’s Defence Minister Shri AK Antony offers an update re: the Tejas LCA:

“Five Tejas are currently being flight tested for Initial Operational Clearance by the Indian Air Force pilots posted at National Test Centre of Aeronautical Development Agency, Ministry of Defence. So far 629 flights accumulating 334 hours have been completed. Twenty aircraft have been ordered by the Indian Air Force as the first lot.”

Feb 7/07: F404 order #2. HAL ordered an additional 24 F404-GE-IN20 afterburning engines in a $100+ million contract, in order to power the first operational squadron of Tejas fighters for the Indian Air Force. This purchase follows a 2004 purchase of 17 F404-GE-IN20 engines to power a limited series of operational production aircraft and naval prototypes.

Jab 25/07: India tries to throw a large monkey wrench into Pakistan’s rival JF-17 project. They almost succeed.

Nov 22/06: Reuters India: “Pakistan set to get eight JF-17 fighter jets next year.” Anxieties are becoming more acute as Pakistan readies its JF-17 fighter developed in conjunction with China and Russia, and prepares to induct them into service in 2007-2008. The JF-17 is a sub-$20 million fighter designed to replace F-7P (MiG-21+) and Mirage 3/5 aircraft in Pakistan’s fleet, and is a comparable peer for the LCA Tejas.

Sept 19/06: India set to induct 28 LCA Tejas aircraft by 2007. They would have GE F404 engines rather than the Kaveri, says former project director Dr. Kota Harinarayana. As it turns out, India has 0 inducted aircraft, 5 years after that stated date.

May 2/06: India Defence reports that the Indian Navy may be interested in a Tejas LCA version of its own.

May 1/06: Radar. More bad news for the radar project. The Vijay Times also notes that that the performance of several radar modes being tested still “fell short of expectations,” and may force acquisition of American or Israeli radars (likely APG-68 or Elta’s EL/M-2032) as an interim measure.

April 8/06: Radar. The Sunday Telegraph reports that the Tejas’ radar, which was also set up as an indigenous project after foreign options like the JAS-39 Gripen’s fine PS05 radar were refused, could only perform at the most basic levels, putting tests on hold:

“According to the IAF, which proposes to buy 220 of the planes when they are ready, the radar is now “marooned in uncertainty”.... While two basic radar modes have been tested, the other modes have failed, throwing up serious questions about the system’s fundamentals.

In written replies to queries sent by The Indian Express, DRDO chief M Natarajan said: “Because of the complexity of technologies involved (in the radar project) and the extent of testing to be done, help of specialists in the field may be sought to complete the task… When Natarajan was asked why there was uncertainty over the radar so long after development began, he said: “The radar is under development by HAL and not at LRDE (the DRDO’s lab).” This, even when the signal processor built by the DRDO is the very heart of the radar.

Security analyst K Subrahmanyam has earlier called the dogged refusal to entertain foreign help by the DRDO as reflective of the organisation’s bad project management.”

February 2006: Kaveri. Jane’s claims that SNECMA won the contract to assist India in developing the Kaveri.

Appendix A: DID Analysis & Op/Ed (2006)

The complexities inherent in designing a new fighter from scratch are formidable, even for a lightweight fighter like the Tejas. As Air Marshal Philip Rajkumar (Retd) notes, India’s industry had significant experience deficits going into this project, which have delayed the project significantly, and raised costs. The insistence on pushing the envelope with a new fighter design, a new engine, and a new radar all at once has had consequences. In the long run, those consequences will lead to a smaller IAF, and could be set to create major force gaps if MiG-21 lifespans can’t be extended long enough.

As experts like Richard D. Fisher have noted, Chinese projects tend to quickly hand off significant components to others and confine the kinds of domestic expertise required. The J-10 has been an example, and the massive changes required when Israeli and Western cooperation ended have made the project incredibly challenging – but had the Chinese not outsourced major aspects like the engines to the Russians, the project would probably have failed completely.

As the J-10 shows, delays remain possible even with expensive foreign cooperation. It’s also true that every new jet engine type can expect teething issues when it is first installed. This may explain why even Sweden, with their long history of indigenous fighter development, chose the less risky approach of adopting the already-proven GE F404 engine for the JAS-39 Gripen, making minor modifications as required in conjunction with the manufacturer, then concentrating their design efforts elsewhere.

All the more reason, then, to bring in foreign partners for components like the engine etc., and minimize the complexities faced by India’s indigenous teams in its state-run organizations.

Sainis and Joseph’s examination of the benefits to Indian industry from the LCA program demonstrate that most industrial benefits would have been retained had India taken this route. So, too, would the project’s timelines, which have suffered instead as India’s fighter fleet dwindles.

In India’s case, these added complexities can also spill over onto the export front. If potential Tejas export customers aren’t offered a common, fully tested international engine like the GE F404, with a broad network of support and leverage across multiple aircraft types, risk calculations will get in the way of some sales. When deciding on their buy, potential customers will have to evaluate the Kaveri engine’s prospects for future spares, upgrades and support, available contractors with relevant skills in maintaining them, etc. This tends to make potential buyers more cautious, and is likely to reduce Kaveri’s odds when competing against options like the Chinese/Pakistani JF-17, which uses a modified version of the engine that equips many MiG-29s around the world.

As the French have found with the Rafale, lack of exports for a limited production indigenous fighter equals rising maintenance and upgrade burdens that hit right in the home budget, and make it that much harder for the design to keep up with contemporary threats over its lifetime. Which in turn affect export prospects in a vicious circle. Will India’s decision to proceed with the Kaveri engine offer short-term customization benefits at the expense of long-term pain? Or can HAL maintain the Tejas airframe design, and field a lightweight fighter that offers its customers a choice of engines?

Appendix B: The Kaveri Saga – Keystone, or Killer?

The GTRE GTX-35VS Kaveri was envisioned as a variable cycle flat-rated engine, in which the thrust drop is compensated by increased turbine entry temperature at the spool. The variable cycle flat-rated engine would be controlled by a Kaveri full authority digital control unit (KADECU/ FADEC). The goal was a powerplant with slightly more thrust than GE’s F404 engines, whose characteristics were uniquely suited to India’s hot and humid environments.

India’s frequent goal of “100% made in India content” has derailed a number of its weapon projects over the last few decades, but foreign decisions also played an important role in the Kaveri project’s genesis. In 1998, India’s nuclear tests prompted the US to place sanctions on military exports, including GE’s F404 turbofans and Lockheed Martin’s assistance in developing the Tejas’ flight control system. In response, India began its program to develop an indigenous engine. As the Rediff’s Feb 5/06 report notes:

“DRDO scientists had kept the development of the Kaveri engine under wraps, exuding confidence that India had developed the technological edge to develop its own aircraft engine, so far confined to handful of developed countries.”

The prospect of ending that dependence is a powerful lure, but some of the reasons for that small club are technical. Modern jet engines are far more complex than even Vietnam-era engines like the GE J79 that equipped the F-4 Phantom. Producing a working, reliable engine that can operate at these high pressures and thrust ratings isn’t easy, and weaking and troubleshooting a new and unproven jet engine always involves a great deal of work and expense. The Kaveri engine’s climate performance targets added even more challenges to an already-full plate. That proved difficult for the program when the program’s entire context changed.

Eventually, the USA lifted its weapons export restrictions on India. In contrast, the natural barriers to developing an advanced engine from scratch, in a country with no past experience doing so, to technical specifications more challenging than current market mainstays, were not lifted so easily. The complexities inherent in this challenge belied DRDO’s apparent confidence, forcing India to bring in turbine experts from Snecma in France and from US firms like Pratt and Whitney.

In the end, the Indian DRDO was finally forced to look for a foreign technology partner, and issue an RFP. Even then, acceptance of program realities was slow in coming. In the initial stages, DRDO secretary M Natarajan referred to it as an effort to “add value and look for a partner to stand guarantee,” and stated that any partners would have to work to India’s terms. A committee in which IAF experts would be included would evaluate the bids to decide on:

”...how much to take and from whom… But Kaveri is and would remain an Indian project… We have gone this way to shorten time for making the engine airborne, as we don’t wont to delay the LCA induction schedule.”

Those goals did not prove to be compatible.

US engine manufacturer General Electric, who supplies the F404 jet engines that power initial Tejas models, seemed unenthralled with those proposed terms. They declined to respond to the RFP for foreign assistance. Eventually, India’s state agencies were forced to concede that they could not develop an engine with the required specifications, and that seeking foreign help to improve the basic design was also unlikely to produce a design that met the required specifications.

With no engine in production as late-stage aircraft testing began, and none forthcoming in the forseeable future, India’s drive to develop an indigenous “Kaveri” jet engine had become a key roadblock for the Tejas program in India – and very possibly, beyond India as well.

In contrast to the Kaveri, F404 family engines are already proven in a number of aircraft around the world including Saab’s 4th generation JAS-39 Gripen lightweight fighter, the F-117A Nighthawk stealth fighter, models A-D of the F/A-18 Hornet fighter aircraft in service around the world, South Korea’s T/A-50 Golden Eagle supersonic trainer & light attack aircraft, and Singapore’s soon to be retired A-4SU Super Skyhawk attack jets. Kaveris equipped with F404/F414 engines would present a lower risk profile to potential export customers, due to the engines’ long-proven performance, GE’s global support network, and the number on engines in operation around the world.

Kaveri would offer none of these important benefits, in exchange for one offsetting feature: foreign sales would not require US military export approval for the engines.

India has not been a major weapons exporter, so export realities didn’t carry a lot of weight. On the other hand, the technical and timeline difficulties experienced by the main Tejas program created a potential natiional defense crisis that could not be ignored. By August 2008, the Kaveri program had effectively been sidelined, in order to get the Tejas into service within an acceptable time frame and preserve India’s operational fighter strength. While political changes may resurrect the Kaveri program as a political exercise, the Tejas program’s technical procurement path has been moving in the other direction. This kind of vague drift away from an indigenous option is common in India’s procurement history. It usually ends with off-the-shelf “interim” buys becoming permanent; and an indigenous program that’s either shelved, or bought in very low numbers alongside a much larger foreign purchase of similar equipment.

GE’s F404-IN20 will be the Tejas’ initial powerplant, to be followed by an upgraded foreign engine that may be offered as a straight purchase, or in some sort of partnership mode similar to Volvo’s adaptation of the F404 for Sweden’s JAS-39 Gripen. GE’s F414 appears to have beaten the Eurojet EJ200 as the Tejas Mk.II’s planned engine, but a contract is still under negotiation.

Even so, DRDO has continued to fund and back its long-delayed project. As of August 2011, they remain in negotiations with France’s Snecma to create a Kaveri 2.0 version using key Snecma engine technologies. They have now specified a pair of Kaveri engines for a proposed “Advanced Medium Combat Aircraft” project, which would be developed by 2020 and see service by 2025. If accepted, it would keep the Kaveri project alive and eating funds for another decade, with the hope of eventually forcing its way back into the LCA Tejas Mk.II fleet as well.

Alternate engine programs aren’t always a bad idea. They’ve been a roaring success with the world’s F-16 fleets, as many countries have divided their F-16 purchases between fighters equipped with the original PW F100 engine, and F-16s running GE’s F110. South Korea and Saudi Arabia’s F-15 fleets do the same, ensuring that problems with one engine type can’t ground the entire fleet.

A dual-engine option for India’s Tejas, with one of those options sitting beyond the reach of US export controls, could be a worthy industrial and program goal in its own right. If the Tejas program’s main track is secure based on off-the-shelf engine technology. If the price for developing the 2nd engine is right. If the odds of success in that development are good enough.

It took a long time for India to recognize the first if. The other ifs still need answers, over a decade after the Kaveri project began.

Appendix C: Additional Readings & Sources

• Indian Government – Tejas: India’s Light Combat Aircraft

• India’s Aeronautical Development Establishment – Main site. Government agency developing the LCA family.

• Wikipedia – HAL Tejas. Detailed and well footnoted.

• Aerospace Web – Hindustan (HAL) Tejas / Light Combat Aircraft (LCA) Light Multi-Role Fighter

• Air Force World – LCA

• GlobalSecurity.org – Tejas Light Combat Aircraft (LCA)

• MILAVIA – ADA Tejas LCA (Light Combat Aircraft)

• General Electric – F404 engine family

• General Electric – F414 engine family

• Eurojet – EJ200

• India’s DRDO – Kaveri

• IAI – EL/M-2032 – Multimode Airborne Fire Control Radar

• IAI – EL/M-2052 – Active Phased Array Airborne Fire Control Radar

• ACIG Database – Kfir C.10. Includes a great deal of information concerning IAI Elta’s EL/M-2032 radar.

• DID (Nov 17/06) – India’s DRDO Rethinking the Way it Does Business. Contains a very extensive set of links to articles covering India’s defense sector and its organizational/ program issues. One of which is…

• The Indian Express (Nov 15/06) – 23 yrs and first fighter aircraft hasn’t taken off. Says the LCA Tejas may face further delays, and the entire project could even be forced into joint-venture in order to successfully deliver the aircraft.

• Vijay Times (May 1/06) – Glitches in LCA radar

• The Sunday Express (April 8/06) – ‘Indigenous’ aircraft needs foreign lift, for its radar

• Rediff (Feb 5/06) – Kaveri Engine – Reignited Hopes, Technological Edge?

• Press Trust of India (Feb 2/06) – Light Combat Aircraft project to be completed in 2010

• Frontier India (March 6/05) – Light Combat Aircraft – Tejas Testing. By Air Marshal Philip Rajkumar (Retd). Good description of the issues encountered trying to design and build the aircraft.

• Bharat Rakshak Monitor (March-April 2001) LCA Development and Costs. By Sunil Sainis and George Joseph. Contains the most detailed cost and industrial participation information we have found.

• DID FOCUS – India’s MMRCA Fighter Competition. Covering the MRCA foreign competition, but will affect the Tejas LCA project. Doesn’t make predictions, but does offer some thoughts on each contender’s strengths and weaknesses.