A former AOC-in-C, Operational Command, writes

[Reproduced below is an e-letter, dated Aug 10, 2014, from a highly respected Airman, a former test pilot and AOC-in-C, Operational Command, who wishes to remain anonymous.]
I read your pieces Fire Up Defence Industry & Favour Tejas to Meet IAF Needs with great interest as indeed I do your other writings.

I thought I would take the liberty of sharing with you my personal experiences borne out of having been intimately involved with the IAF Plans Branch and as a test pilot both with DRDO and the Industry.

In ‘Fire Up the Defence Industry’ whilst talking of the HF 24 programme you make the point about a foreign aircraft fixated Air Force and the aircraft being aborted for being underpowered. Also that this has resulted in an endless cycle of licensed manufacture.

Whilst it is true that the HF 24 did not get the uprated Orpheus and hence fell short of level supersonic performance, we had found it to be a first class ground attack platform. I can say with confidence that the squadrons were happy and if HAL had continued to promptly address its technical, maintenance and other design problems, perhaps it would have served the IAF well.

HAL could not introduce design changes to clear the aircraft to fire its four 30mm canons in service and there were in-service fire problems that led to serious accidents and prolonged grounding. In my view having got the HF 24 into service, the HAL design team lost interest in keeping up with in -service design changes (which are essential for any aircraft-I think the Hunter clocked many thousands in service modifications).

Instead they had their eyes on the HF 24 Mk 1R which was the airframe with GTRE modified Orpheus Reheat engines. We had many a lively discussions with the design team and I recollect their complete belief that this should enter service, not with standing the fact that modification of the rear fuselage to accommodate the reheat had increased drag and affected speed performance to below that of the Mk1! Sadly Gp Capt Das’s fatal accident put an end to this futile debate.

The HF Mk 2 was proposed with the Mig 21 (If I remember the R 25 engine). Again this would have involved major aerodynamic changes and we were not sure how this would affect the performance of a Kurt design with an ‘area ruled’ fuselage shape. Ultimately I think the proposal was dropped by HAL itself when they saw that the IAF had reservations. Such a programme even if it were viable would not have achieved fruition in time to prevent seriously depleting the IAF’s strike capability.

(You do mention Raj Mahindra in the context of the HF Mk II and if I recollect he did appreciate our reservations on modifying the HF 24 fuselage for an R 25 engine. I may mention that we worked very closely with him on clearing the HJT 16 for the IAF including the difficult spinning trials. He was truly a hands-on designer who worked so closely with us that we were one team. Perhaps this is one reason the HJT 16 has served the IAF so well for so long)

In the late sixties IAF had identified a requirement of a Fighter-bomber, as we could see that Medium Bombers like the Canberra were becoming vulnerable. After the 1971 operations, some instances of corrosion were reported from both the Hunter and Canberra fleets. This would have had a serious impact on our strike capability. This, along with our ASR for a DPSA resulted in the Jaguar induction, which was cleared by the Morarji government.

In the mid seventies the following areas were drawing our attention in the Plans Branch.

· Reduce multiplicity of types

· Reduce total dependence on Only Soviet source

· Aim for a balanced Force- Mix of High performance/High Cost & Light/low cost. Keep affordability fully in mind

· Ensure that indigenous design and production expertise grows

That is why the Ajeet programme was launched by HAL even as the LCA requirement was being formulated.

Unfortunately, in a way, the Ajeet followed the same trajectory as the HF. As soon as it entered service our industry started to look for the next design project. Not surprisingly the Ajeet, like the HF was prematurely withdrawn from service. Having been part of the HAL team during the Ajeet development I can say that enough was not done by the industry to keep this programme afloat perhaps because they had their eyes on the LCA!

It was the desire for a relatively light, maneuverable and not very high speed and low cost primarily a ground aircraft in our inventory that resulted in our evolving the initial LCA ASR. Unfortunately this was hijacked by the scientific community who wanted to build a world-class light aircraft with multi role capability. What we were promised was an indigenous design with indigenous engine and indigenous multi mode radar in a time frame to replace our ageing Mig 21. Having deliberately kept the IAF out during the Project Definition Phase when many critical decisions were taken (Arun Singh was told that IAF was coming in the way of a fast track project) the IAF was finally asked to comment of the PDP report. I can say with hindsight that every cautionary note that we struck in that report has been more than proven by subsequent events. I have often written that purely as an exercise to learn lessons, an institution like the College of Defence Management should conduct a management study of how this vital project has been mishandled by personalities for egoistic ends.

As if this was not a challenge itself, HAL Design was kept out and instead a Society to oversee ADA was formed to manage the project. So we have ADA as the design authority, HAL as the production agency and one responsible for providing product support to the IAF. ADA will be busy with the next generation design and when in service problems arise, one can visualize passing the buck between HAL and ADA with the IAF facing the consequences! I do not wish to be a pessimist, but my experience cautions me of a repeat of the HF 24 and Ajeet histories. Sadly at great cost to the nation.

Let me also say that the IAF could boast of the finest Plans Branch and planning systems starting from the sixties. Integrated within the system were not just test pilots and engineers but financial planners as well. Our Air Staff Requirements were thoroughly made and then not compromised. Because planning is a long-term activity, people with experience were rotated within the system.

ASRs were what the IAF needed not what others thought we needed. So when the LCA ASR was being discussed and the DRDO wanted these to be moderated, the ASR was not changed. Instead the concession was mentioned against the required performance. In the ASR. Similarly, if for some reason of cost or availability, the MOD wanted concessions to be made, these were recorded as concessions with reasons and not as changes to ASR.

I must say to my regret that from the early nineties IAF leaderships, for whatever reason, failed to maintain the integrity of the Planning Branch. Whether it was external pressures or those from within, it is not for me to say, although I have my serious reservations on some of the leaderships of the time. Committing the IAF to the Su 30 heavy fighter within a year of the Chief saying there was no such requirement (and that too a two cockpit fighter which has a huge impact on pilot demands) is I believe an event that has not been studied enough nor commented upon. The rot was setting in and the recent revelations about the VVIP helicopter Staff Requirements being changed due to extraneous factors merely confirms this and does not surprise me.

I have always believed and advocated that we as a nation have the wherewithal to become a producer of world-class aeroplanes. What is lacking is a strategy and to work as one. When Dr Kalam was President of the Aeronautical Society of India a paper was put up for a National Aeronautics Policy. In 2004 the AeSI revised the proposal and a paper titled ‘National Aeronautics Policy’ August 2004 was put up to the government. As one of the Vice Presidents of the Society at the time I was one of the principal architects of this paper. I understood that the then NSA Mani Dixit was pursuing it, but perhaps because of his untimely demise no follow-up took place.

I do share concern of where IAF plans are leading us. I thought that as a historian and academic you may be interested in some of the more hidden aspects from the other side as it were, aspects which otherwise will die as generations move on, depriving us to draw appropriate lessons.

About Bharat Karnad

Senior Fellow in National Security Studies at the Centre for Policy Research, New Delhi, he was Member of the (1st) National Security Advisory Board and the Nuclear Doctrine-drafting Group, and author, among other books of, 'Nuclear Weapons and Indian Security: The Realist Foundations of Strategy', 'India's Nuclear Policy' and most recently, 'Why India is Not a Great Power (Yet)'. Educated at the University of California (undergrad and grad), he was Visiting Scholar at Princeton University, University of Pennsylvania, the Shanghai Institutes of International Studies, and Henry L. Stimson Center, Washington, DC.
This entry was posted in Asian geopolitics, civil-military relations, Defence Industry, DRDO, India's strategic thinking and policy, Indian Air Force, Military Acquisitions, russian assistance, russian military, society, South Asia, Technology transfer, Weapons. Bookmark the permalink.

10 Responses to A former AOC-in-C, Operational Command, writes

  1. RV says:

    Fascinating letter/article, and thanks for posting it. With regards to the HF 24’s difficulties with its four 30 mm. Aden canons, I’ve heard that the a/c went into a spin if all four cannons were fired simultaneously. I wonder whether this is what the AM is referring to, and whether what I heard is true? One of the most telling portions is: “I do not wish to be a pessimist, but my experience cautions me of a repeat of the HF 24 and Ajeet histories. Sadly at great cost to the nation.”.

  2. RV says:

    The AM obviously served at a time when being in the IAF was a matter of pride and honor. He describes the intense interactions between Raj Mahindra and the IAF brass (“He was truly a hands-on designer who worked so closely with us that we were one team”.) That was a time long gone when design engineers like Raj Mahindra and IAF brass like the AM had CAREERS and not JOBS.

    These events happened a very long time ago, but the gist of what the AM says is still very much valid today. I can clearly see that the AM describes a day and age when many design engineers genuinely sought comradely interaction with the IAF brass, discussed engineering issues in a simple and lucid manner, and requested feedback on the tenability of design modifications, etc…. Likewise, many of the IAF brass took the time and effort to ask questions of the design engineers, closely & constructively interact with them, and gave their valued inputs in every way possible.

    Unfortunately, today many (BUT NOT ALL) the IAF brass are more at home at cocktail parties, interacting with arms dealers & touts, and dropping worthless jargon they don’t know the basic definitions of. OTOH, many (BUT NOT ALL) senior design engineers today spend quite a bit of time cribbing about their lot, trying to get assignments overseas, and exploring ways and means of getting jobs in MNC’s. The situation today is one total degeneration, perhaps beyond the point of repair, caused by complex, meaningless, and self-destructive “ego trips”!

  3. RV says:

    With due respects I’d like to make an update to the AM’s statement: “Committing the IAF to the Su 30 heavy fighter…(and that too a two cockpit fighter which has a huge impact on pilot demands) … commented upon.”, the issue of work load is being largely mitigated through data/sensor/feature fusion, in the SU 30, and more explicitly in the SU Super 30. This will also stipulated to be a part of the Tejas MK-2 fusion and networking suite, assuming of course that the Tejas MK-2 is ever allowed to fructify..

  4. RV says:

    The AM’s comments provide an eyeopener and an alternate suggestion to salvage the time and expenditure in the MMRCA sweepstakes. IMHO, the following list of possibilities could be considered:

    1. Scrap acquisition of the additional C-7’s and P-8’s. The rationale for acquisition of the first (C-7’s) in such large numbers has not been justified, and the allegedly degraded performance of the next (P-8’s) has not been seriously discussed or addressed.

    2. If 30 % of the MMRCA costs are to be plowed back into the Indian economy, the exact nature of these offsets need to be made transparent and verifiable.

    3. ToT should be limited to realistic, verifiable, and easily monitored technologies, which can be easily digested by Indian industry. Fanciful talk such as obtaining GaN technology without transferring of the foundries and the technology to build them need to be junked. Instead, the ToT should be strictly limited to complete and verifiable technology transfer of: a.) new composite materials such as carbon/ceramic fibres onto a carbon/ceramic matrix, b.) composite material tooling and multi-axis CNC machines, and if possible, c.) relevant aspects of the technology emanating from FUBICOMP program.

    4. The Contract and Price Negotiating Committee should insist that 30-50% of any MLU’s be offset to Indian industry. This will stop any repeat of the M2K upgrade charade.

    If the above can be accomplished/strictly enforced, then the Rafale deal may not be a bad option. However, under no circumstances should this come in the way of large scale induction of the Tejas MK-1/2 and the development of an acceptable and certified Kaveri engine, which are non-negotiable.

  5. RV says:

    Apart from the 4 Youtube clips on the Vayu-Stratpost roundtable on Indian air power, there is a 5th one dedicated to the LCA and the building a National capability. It makes for very interesting viewing:


    Please replace all instanced of “dot” with “.”.

    • RV says:

      In addition to the 4 Youtube clips posted by Karnad on the Vayu-Stratpost roundtable on Indian air power, there is a 5th one dedicated to the LCA, and the building of a National capability. It makes for very interesting viewing:


      Please replace all instances of “dot” with “.”.

  6. RV says:

    And a 6th Youtube clip too, summarizing findings of the roundtable:


    Again, please replace all instances of “dot” with “.”.

  7. E.R. Sakthivel says:

    Which tech rafale has like

    1. 4 channel relaxed static stability fly by wire airframe,

    2. tail less delta with low wing loading, and high thrust weight ratio to excel in high altitude himalayan theater where taking off with meaningful load within the specified runway length depends on these factors

    3. All glass cockpit, and avionics that minimizes pilot loads and designed with active inputs from test pilots through out the flight test regime,

    4. RCS reduction mechanism,

    5.latest engine tech(present engine on rafale is more than two decades old in thrust levels)

    6.Ability to fire 120 Km range BVR missiles with a decent sized radar,

    7. A fly by wire airframe with wake penetration and all weather clearance,

    8. Ability to fire the deadly HMDS enabled visually cued R-73 E WVR missile? (described as one of the best in the world by Air marshal and former HAL chairman MSD Woolen. Even tejas mk1 has it now but it is proposed to be added to rafale later at extra cost to ourself).

    9. Higher percentage of weight reducing , radar refection minimizing composites that enable high thrust to weight ratio for a given airframe mass?

    10.The combination of high TWR and low wingloading RSS delta airframe which enables agile turns to evade BVR missiles and get a first shoot ability with Visually cued R-73 E like WVR missiles in close combat, which is a must have option in modern 4.5th gen airframes

    11.Ability to carry a mini brahmos like cruise missile weighing close to 1.5 tons on its center line pylon.

    12.OBORG for extended refuelled flying in high altitude with the aid of refuelling,

    13.A 1.8 mach top speed in its service ceiling with 9 G limits.

    14. A must have less than 1 sq meter clean config which enables to drop away from long range radars once heavy external weapons and fuel tanks are released.

    15. A good fuel sipping engine that is reliable and modern for some time to come.

    16.Ability to fire ramjets 120 Km range missiles like meteor with an ASEA radar that can track long enough,

    17. Modular in design and Ability to be upgraded in batches as and when new techs like better sensor fusion, better ASEA radar and better IRST devices arrive.

    18, An option to upgrade to a higher thrust engine,

    19. A flow separation postponing arrangement like ,

    canard or levcon or cranked delta which generates vortex over the top of wing leading edge in high angle of attacks to enables air suction over the top of the smoothly blended upper wing body fuselage,

    there by delaying the onset of stall and enabling the wing to reach designed max lift coefficient of the wing which is not present in older delta platforms like mirage-2000.

    Also these lift enhancing mechanism along with flawless Relaxed static stability 4 channel fly by wire tech that allows the hassle and easy flying at sea level which is not the case with earlier tailless deltas which did not have the above mentioned techs .

    That wont be present in tejas mk2 and( mostly present in tejas mk1 with a few exceptions like G limits, OBORGs and topspeeds and a bit lower TWR)?

    Answer -NONE.

  8. Shail says:

    very interesting and thought provoking article except the last three paras. ( proved wrong today , Su-30 was actually quite a good acquisition) Designers…HPT = Horror, IJT = Horror, LCA = Ok for first timers, Mk2 = Jaane kab aayegaa, AMCA = distant dreams
    IAF= to pay price for everyones mistakes,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s