What's new

Russians go slow, Sukhoi fleet in trouble

Not our problem, the avionics on the Su-30MKI are mostly European and Indian not Russian.

This is what happens when you mix Western and Russian technology into a inbred bastard with questionable maintenance practices.

Its a false report ...
 
Yellow Journalism Yet Again

In this news-report (Russians go slow, Sukhoi fleet in trouble), it has been alleged that 50% of the IAF’s Su-30MKI fleet remains grounded because of A) multiple cases of repeated failure of Mission Computer-1 and blanking out of Head Up Displays (HUD) and all Multi-Function Displays (MFD) in flight since 2012. B) Due to non-availability of facilities for overhaul of aggregates (aircraft parts), following which the serviceability (availability for flying) of Su-30MKI is slowly decreasing and demand for Aircraft on Ground (AOG) items on the rise as of December 24, 2013. C) Due to Russia’s inability to set up the MRO workshops at HAL’s Nashik-based facility by December 2013, and that this facility was originally scheduled to overhaul the first Su-30MKI by June 2014. Consequently, five Su-30MKIs are already parked at HAL for extensive overhaul, and another 15 will be due for overhaul in the current year.

Su-30MKI.jpg


Now, let’s separate fact from fiction. Firstly, both the Su-30MKI and MiG-29B-12 were originally designed and certified to log in no more than 120 flight-hours per annum. Despite this, the IAF has been following Western standards of flight operations by requiring its air warriors to log in at least 25 flight-hours per month, or about 275 flight-hours every year, or 2,750 hours in a decade. Furthermore, the IAF has been way behind schedule when it came to service-induction of cockpit procedures trainers and full-flight simulators for the Su-30MKI. Ideally, such flying training aids should have been commissioned into service in a progressive manner since the last quarter of 2002, but this process didn’t commence until the final quarter of 2009. Now, if 275 flight-hours are logged in by a Su-30MKI, then within five-and-a-half-years itself it would have reached its scheduled time-between-overhauls (TBO) of 1,500 hours for both the airframe and turbofans, while the prescribed Russian timetables call for the Su-30MKI to approach its TBO after only a decade, i.e. after the Su-30MKI has been flown for 120 hours every year for at least a decade. What this translates into is that the HAL-owned-and-operated MRO facility for the IAF’s Su-30MKIs should have become operational by early 2008 at the latest. Consequently, HAL is behind schedule by six full years when it comes to commissioning such a MRO facility.

IAF+Su-30MKI+cockpits.jpg


Now, coming to the issue of the premature in-flight malfunctions of the Su-30MKI’s ELBIT Systems-built Type 967 HUD, THALES-developed MFD-55 and MFD-66 AMLCDs, and the DARE-developed and HAL-built mission computer. Firstly, it must be noted that the malfunctions are not across-the-board or affecting the entire fleet of Su-30MKIs, but only those airframes produced for the last tranche of 10i-standard Su-30MKIs and the first tranche of 11i-standard Su-30MKIs. At most, therefore, no more than 40 Su-30MKIs will be affected by such avionics-related malfunctions. This then brings us to the probable causes of such malfunctions. Prima facie, there is only one probable cause: faulty hardware—most likely wiring harnesses or cable connectors. What has to be established is whether these items came directly from Russian OEMs (in which case product liabilities will those of Rosboronexport State Corp and IRKUT Corp) or were they sourced from India-based OEM-licenced vendors. This can easily be done PROVIDED HAL has its in-house required set of item-specific test-benches and ATE equipment. As another option, HAL can also make use of ADA’s test-benches and ATE equipment, while DARE can be approached for replicating a fully-functional mock-up of the Su-30MKI’s cockpit avionics architecture—since DARE is presently involved with a similar task concerning the cockpits of the projected Super Su-30MKI.

Su-30MKI's+AMLCDs.jpg


But what is most exasperating is that despite decades of experience in licenced-manufacturing of various types of combat aircraft of foreign origin, neither the MoD’s Department of Defence Production & Supplies nor HAL till this day have grasped the need for achieving 100% indigenisation for the tens of thousands of rotables, consumables and accessories that go into each aircraft-type. Instead, the focus continues to be on the licenced-production of airframes through raw materials sourced locally and from abroad. Such a distortion can only result in an undesirable reliance on foreign OEMs for the smallest but most critical components, which in turn severely compromises the IAF’s operational sovereignty over its aircraft/weapons assets.

Su-30MKI's+RCs+&+MC.jpg


Lastly, a word on the so-called combat aircraft fleet availability rates in peacetime. No air force in peacetime boasts of combat aircraft fleet availability rates of 75%. Such high rates are mandatory for only flying training aircraft like BTTs, AJTs and LIFTs. In reality, the availability rate of combat aircraft fleets hovers between 50% and 60%. If the national security scenario worsens over a period of time, then the availability rates are increased progressively (as was the case with the IAF in both 1999 and 2002), depending on the type of conflict envisaged, i.e. limited high-intensity conflict confined to a single theatre, or a full-blown all-out war. In case of the latter, fleet availability rates are jacked up to 90% for Day-1 of the war. By Day-2, the rate drops to 75% and by Day-4, the availability rate stabilises at 50% while ensuring a high tempo of daily sortie generation. It is based on such estimates that any self-respecting air force does its force-structure planning.

HAL+Graphic.jpg


TRISHUL

A very detailed & objective counter to the stupid reports which are filed by part-time defence journos.
This one nails it! Thanks buddy!
 
And had I brought such an oblique reference to JF 17 in an unrelated thread, @Oscar would have accused me of being biased and hateful towards Pakistan :)
I still accuse you of that. NOTHING will change my opinion of it.

Yellow Journalism Yet Again

In this news-report (Russians go slow, Sukhoi fleet in trouble), it has been alleged that 50% of the IAF’s Su-30MKI fleet remains grounded because of A) multiple cases of repeated failure of Mission Computer-1 and blanking out of Head Up Displays (HUD) and all Multi-Function Displays (MFD) in flight since 2012. B) Due to non-availability of facilities for overhaul of aggregates (aircraft parts), following which the serviceability (availability for flying) of Su-30MKI is slowly decreasing and demand for Aircraft on Ground (AOG) items on the rise as of December 24, 2013. C) Due to Russia’s inability to set up the MRO workshops at HAL’s Nashik-based facility by December 2013, and that this facility was originally scheduled to overhaul the first Su-30MKI by June 2014. Consequently, five Su-30MKIs are already parked at HAL for extensive overhaul, and another 15 will be due for overhaul in the current year.

Su-30MKI.jpg


Now, let’s separate fact from fiction. Firstly, both the Su-30MKI and MiG-29B-12 were originally designed and certified to log in no more than 120 flight-hours per annum. Despite this, the IAF has been following Western standards of flight operations by requiring its air warriors to log in at least 25 flight-hours per month, or about 275 flight-hours every year, or 2,750 hours in a decade. Furthermore, the IAF has been way behind schedule when it came to service-induction of cockpit procedures trainers and full-flight simulators for the Su-30MKI. Ideally, such flying training aids should have been commissioned into service in a progressive manner since the last quarter of 2002, but this process didn’t commence until the final quarter of 2009. Now, if 275 flight-hours are logged in by a Su-30MKI, then within five-and-a-half-years itself it would have reached its scheduled time-between-overhauls (TBO) of 1,500 hours for both the airframe and turbofans, while the prescribed Russian timetables call for the Su-30MKI to approach its TBO after only a decade, i.e. after the Su-30MKI has been flown for 120 hours every year for at least a decade. What this translates into is that the HAL-owned-and-operated MRO facility for the IAF’s Su-30MKIs should have become operational by early 2008 at the latest. Consequently, HAL is behind schedule by six full years when it comes to commissioning such a MRO facility.

IAF+Su-30MKI+cockpits.jpg


Now, coming to the issue of the premature in-flight malfunctions of the Su-30MKI’s ELBIT Systems-built Type 967 HUD, THALES-developed MFD-55 and MFD-66 AMLCDs, and the DARE-developed and HAL-built mission computer. Firstly, it must be noted that the malfunctions are not across-the-board or affecting the entire fleet of Su-30MKIs, but only those airframes produced for the last tranche of 10i-standard Su-30MKIs and the first tranche of 11i-standard Su-30MKIs. At most, therefore, no more than 40 Su-30MKIs will be affected by such avionics-related malfunctions. This then brings us to the probable causes of such malfunctions. Prima facie, there is only one probable cause: faulty hardware—most likely wiring harnesses or cable connectors. What has to be established is whether these items came directly from Russian OEMs (in which case product liabilities will those of Rosboronexport State Corp and IRKUT Corp) or were they sourced from India-based OEM-licenced vendors. This can easily be done PROVIDED HAL has its in-house required set of item-specific test-benches and ATE equipment. As another option, HAL can also make use of ADA’s test-benches and ATE equipment, while DARE can be approached for replicating a fully-functional mock-up of the Su-30MKI’s cockpit avionics architecture—since DARE is presently involved with a similar task concerning the cockpits of the projected Super Su-30MKI.

Su-30MKI's+AMLCDs.jpg


But what is most exasperating is that despite decades of experience in licenced-manufacturing of various types of combat aircraft of foreign origin, neither the MoD’s Department of Defence Production & Supplies nor HAL till this day have grasped the need for achieving 100% indigenisation for the tens of thousands of rotables, consumables and accessories that go into each aircraft-type. Instead, the focus continues to be on the licenced-production of airframes through raw materials sourced locally and from abroad. Such a distortion can only result in an undesirable reliance on foreign OEMs for the smallest but most critical components, which in turn severely compromises the IAF’s operational sovereignty over its aircraft/weapons assets.

Su-30MKI's+RCs+&+MC.jpg


Lastly, a word on the so-called combat aircraft fleet availability rates in peacetime. No air force in peacetime boasts of combat aircraft fleet availability rates of 75%. Such high rates are mandatory for only flying training aircraft like BTTs, AJTs and LIFTs. In reality, the availability rate of combat aircraft fleets hovers between 50% and 60%. If the national security scenario worsens over a period of time, then the availability rates are increased progressively (as was the case with the IAF in both 1999 and 2002), depending on the type of conflict envisaged, i.e. limited high-intensity conflict confined to a single theatre, or a full-blown all-out war. In case of the latter, fleet availability rates are jacked up to 90% for Day-1 of the war. By Day-2, the rate drops to 75% and by Day-4, the availability rate stabilises at 50% while ensuring a high tempo of daily sortie generation. It is based on such estimates that any self-respecting air force does its force-structure planning.

HAL+Graphic.jpg


TRISHUL

A very detailed & objective counter to the stupid reports which are filed by part-time defence journos.

All this has done is that it has shifted the blame from the IAF(correctly so) to HAL and the Russians.
Yay.
 
I still accuse you of that. NOTHING will change my opinion of it.



All this has done is that it has shifted the blame from the IAF(correctly so) to HAL and the Russians.
Yay.

Just kidding but...did you expect it to shift the blame to ISI ?
 
I guess you forgot that while ordering P-8I, C-130J, Apache and Light Howitzers from USA. India is the largest importer of US weapons.

Try using common sense. The only problem is common sense is not very common.
Wrong. India imported just $1.9 Billion weapon from USA last year compared to almost $5 Billion from Russia. Now tell me how is $1.9 Billion greater than $5 Billion? May be you have read some false report.
 
This proves nothing! Just says the ruskies visited HAL. After all they wanted to know how in the world were you guys screwing up an aircraft that was doing pretty well for them!! :yahoo:
:lol: why you missed the first link???
 
:lol: why you missed the first link???

Didn't miss it, it is so fully of self righteous crap that I decided it didn't deserve my comments!

As a combat aviator I can personally tell you that article is nothing but BS to hide India's incompetence. nothing else!
 
Didn't miss it, it is so fully of self righteous crap that I decided it didn't deserve my comments!

As a combat aviator I can personally tell you that article is nothing but BS to hide India's incompetence. nothing else!

It is aimed at clearing the mist of lies and put the blame in it's right place. Nothing more.

Furthermore it clears a very big fact : the error is present only on batch 10i and 11i aircraft
and not the whole fleet. When did you see any product that doesn't have such
LRU issues now and then? Pressing the mouth of the media doesn't mean some
planes are immune to defects.
 

Latest posts

Back
Top Bottom