2 EMALS is for a single aircraft carrier. American ones have 3 catapults/EMALS for example.given the projected requirement of 2 nos EMALS in a recently released document projecting the armed forces requirement for the next 15 years .
2 EMALS is for a single aircraft carrier. American ones have 3 catapults/EMALS for example.given the projected requirement of 2 nos EMALS in a recently released document projecting the armed forces requirement for the next 15 years .
What you're referring to is a different part of the same paradigm , namely the nature of our response which what you're describing can be characterized as A2 / AD !By 2040 PLAN will have a nuclear carrier strike force permanently stationed in the Indian Ocean. Thankfully, our LRHASM, Agni P, Brahmos ER and other assets will make sure that the PLAN cannot come within 1,500 km of the Indian mainland if we want. Which also means entirety of Bay of Bengal, Arabian Sea also off limits to their surface fleet. The only issue will be their Type 93 and Type 95 nuclear submarines and sub,marine drones, for which we need to operationalize SMART and enhance our version of the SOSUS underwater network.
Hence, I am not necessarily that worried about TEDBFs delay.
Indeed. I stand corrected . So instead of a 5-6 AC Navy the IN seems reconciled for a 3 AC Navy by 2040 by the looks of it with 2 INS Vikrant types & 1 x 65,000 ton displacement INS Vishal with 2 x EMALS & N propulsion.2 EMALS is for a single aircraft carrier. American ones have 3 catapults/EMALS for example.
These mig29k's are quite new.Indeed. I stand corrected . So instead of a 5-6 AC Navy the IN seems reconciled for a 3 AC Navy by 2040 by the looks of it with 2 INS Vikrant types & 1 x 65,000 ton displacement INS Vishal with 2 x EMALS & N propulsion.
The INS Vikramaditya will potter around till 2035-40 whereas both the former as well as the MiG-25 K should've been retired by 2035 latest.
The issue isn't the operations per se , it's their absolute availability which has been abysmal at the best of times. They were are & will be sup optimal platforms.These mig29k's are quite new.
First of these entered service in 2010, they are newer than su30mki's.
Just like super sukhoi upgrade, we can operate upgraded mi29k's till 2040s, after that retirement can begin.
The IN could just be playing for time. They probably hope to piggy back on the IAFs plans for 114 Rafale which seems likely to happen post Op Sindoor. That way, they'd get the 57 MRCBF they'd originally envisaged. They can then directly ask for a 5G ship-based fighter.Those TEDBFs are likely to materialise only in the 2040s & will in all likelihood be 5th Gen FA. They aren't going to the workhorses of the IN but the tip of the spear which only implies we'd be using the Rafales in the former role.
In all likelihood we'd be going in for at least 60-70 Rafales, likely more. Won't be surprised if the figure touches 100 nos .
I'd have preferred we go in for 100 nos TEDBF & either launch a 6th Gen joint program between IN & the IAF or go in for a clean sheet 5th Gen FA program based on the AMCA .
However at the moment that plan is DoA.
Those low availability figures are from before 2020s, early to mid 2010s, which caused extensive rework by navy with its partners to improve it.The issue isn't the operations per se , it's their absolute availability which has been abysmal at the best of times. They were are & will be sup optimal platforms.
While you can always deploy them against the likes of Paxtan , against China it'd be a case of on a wing & a prayer , assuming it does go up against China which itself is a big question mark.
Regardless, it's not getting younger with time. Besides the entire design itself is sub optimal derived as it is from a land based FA , only to cash in on India's haplessness having chosen to upgrade / modernize the INS Vikramaditya from the original Admiral Gorshkov , where the naval aviation complex capabilities didn't exist & had to be created literally on the fly just to fill in their pockets. Enter the MiG-29.Those low availability figures are from before 2020s, early to mid 2010s, which caused extensive rework by navy with its partners to improve it.
Recent reports indicate avaliablity Rate of 65-70%.
The IN could just be playing for time. They probably hope to piggy back on the IAFs plans for 114 Rafale which seems likely to happen post Op Sindoor. That way, they'd get the 57 MRCBF they'd originally envisaged. They can then directly ask for a 5G ship-based fighter.
I'd rather we go back to your previous post of developing the TEDBF & building upon it for the 5th Gen capabilities instead of relying on imports for their 4th Gen FA needs.Unlike LCA Mk2 which is a stepping stone to AMCA, TEDBF is largely redundant. It's the N-LCA mk1 prog that has been the test case for indigenous carrier ac design. Sadly, the jet hasn't got its due.
The IN's threat perceptions have changed since the TEDBF prog was launched. Now that they've ordered 26 Rafale-Ms, it's only logical that they'd buy more in the future to fill the original MRBCF requirement.I'd rather we go back to your previous post of developing the TEDBF & building upon it for the 5th Gen capabilities instead of relying on imports for their 4th Gen FA needs.
No idea what their threat perceptions are except to mimic PLAN from what one can see out here.The IN's threat perceptions have changed since the TEDBF prog was launched. Now that they've ordered 26 Rafale-Ms, it's only logical that they'd buy more in the future to fill the original MRBCF requirement.
You'd have to elaborate on both your points.Unless the TEDBF is re-designed significantly, it won't fit the INs future needs, imo. I've said this before and I'll say it again, we're throwing away the lessons learned from the N-LCA mk1 prog. I'll leave it at that.
TEDBF is still on the drawing board. Could be years before it gets to even the CDR stage. Besides, ADA currently has its hands full with LCA Mk2 and AMCA related work. I suspect the IN would opt for more Rafale-M using the same line of reasoning as the IAF- commonality/sunk costs of infra, training, etc (wrt the 26 jets it has on order from DA)In any case their 5th Gen FA isn't going to arrive before the mid 40s even if they begin now & there's no indication they're beginning now . So what are they going to do between now & whenever it is their 5th Gen FA plans are sanctioned ?
Earlier reports indicated that the first flight of the Mk-2 , AMCA Mk-1 & the TEDBF would be separated by a period of ~ 2 years from each other.TEDBF is still on the drawing board. Could be years before it gets to even the CDR stage. Besides, ADA currently has its hands full with LCA Mk2 and AMCA related work.
Yes that seems likely but why should the GoI give in to the IN's fanciful wishes ? As long as it was restricted to the induction of 26 nos Rafales , it was fine.I suspect the IN would opt for more Rafale-M using the same line of reasoning as the IAF- commonality/sunk costs of infra, training, etc (wrt the 26 jets it has on order from DA)
I've read reports stating both the Rafales & the TEDBF are capable of flight off either decks. So where's the problem ?The IN appears to only have approval for a 2nd Vikrant sized STOBAR carrier at the moment. The TEDBF as it is currently designed is STOBAR specific.
Don't think so . You simulate that on land once the EMALS are ready assuming we'd be going in for an indigenous one else the US EMALS are already validated . So once again I don't see any issue.Developing a CTOL version for the projected 65k ton CATOBAR carrier is likely to have its own share of issues, considering the fact that we've not operated CTOL naval ac since the Sea Hawks/Alize, both turboprops.
The J-15 itself has been a problematic FA because the FA it's based on namely the Su-33 has been a problematic FA. Those are the perils of cut copy paste.Given the problems the Chinese have been having converting the STOBAR J-15 for CTOL ops from the Fujian carrier, the IN might opt for a clean sheet 5G design for the follow-on carrier.
By all accounts, there seems to have been a rethink at NHQ and the focus has shifted to 5G. I wouldn't be surprised if the TEDBF goes thru another round of design iterations post a CDR by the IN.Then came a somewhat major redesign of the TEDBF to mimic the Rafale M . Now the entire project has gone in limbo with no word on why has the IN postponed dates of the development of the TEDBF from later this decade to the end of the next decade
Don't think so . You simulate that on land once the EMALS are ready assuming we'd be going in for an indigenous one else the US EMALS are already validated . So once again I don't see any issue.
By all accounts, there seems to have been a rethink at NHQ and the focus has shifted to 5G. I wouldn't be surprised if the TEDBF goes thru another round of design iterations post a CDR by the IN.
I recall reading @Picdelamirand-oil 's posts on this when the MRCBF competition was on.I guess we'd have to see how the Rafale-Ms (originally designed for CATOBAR) perform in real-world conditions flying off Vikrant.
But the idea of having a common TEDBF airframe(albeit two versions) doing both STOBAR and CATOBAR will have its trade-offs.
We can always get Dassault consultancy for solutions to CATOBAR related design issues if needed. Besides the old INS Vikrant we operated had a steam driven catapult .While we have built up quite a deep knowledge base via N-LCA Mk1 on the former, CATOBAR will be a whole new ball game for both ADA and the IN.
Another sub optimal proposition though I won't put it beyond the IN given their thought process & the situation they've gotten themselves into.I suspect the IN might turn its attention to UCAV/CCAs to complement its carrier air wing in the short to medium term and ditch TEDBF for a new 5G jet. Would be a logical thing to do, imo.
Mig29K is badly born, and as all the russian jets suffer from low availability and low quality support.These mig29k's are quite new.
First of these entered service in 2010, they are newer than su30mki's.
Just like super sukhoi upgrade, we can operate upgraded mi29k's till 2040s, after that retirement can begin.
About f35 starting out as naval varient.View attachment 46470
As i was saying
From the product definition stage of the JSF program itself, the idea was to have separate variants. It is not a conversion from the Air Force version but was purposefully designed for commonality of parts.About f35 starting out as naval varient.
X35 prototype.
F35A.
F35C.
F35 started out as airforce only fighter, later it evolved into jsf with navy and marines joining.