The contract has been abandoned, does it mean that the technical specs, requirements and rational behind it have been abandoned for IAF since then, maybe yes, mabey no.
“They should have opened parallel negotiations with EF & LM”, but why should they, what would be the rational behind that? I don’t see any reason for them to do so.
As far as the technical aspect was concerned, for all means and purposes, the IAF found both aircraft equally compliant. The selection of the Rafale over the Eurofighter was purely financial. And the financial bids placed by the respective companies were based solely on the MMRCA RFP. A hugely revised bid by EF was rejected because rebidding wasn’t permitted under the terms of RFP & MoD rules. Similarly, despite the F-35 providing unparalleled VLO first-day-strike capability, it was a non-starter by virtue of ToT being completely unavailable. But with the MMRCA RFP itself being abandoned, none of the assumptions apply.
The fact that the Indian gov is willing to buy the Rafale off the shelf anyway should at least indicate that the choice in terms of platform is still the same with or without the MMRCA. Also interesting is the estimated quoted price of the contract, about 4 billion for 36 aircraft, which is in line with the price paid by Egypt and the price paid by France so i don’t see why Dassault should be pressured more than it already was.
Contract hasn’t been signed so I wouldn’t put too much faith in those figures. In any case, if the Dassault was offering the best deal, it would have gotten contract even with one or two other bids on the table. BTW, the Egyptian Rafales were quite a bit more.
In any case it’s India’s prerogatives to ask the competition for info or NOT ask them and i’d rather be Dassault right now, at least they have a bit more to chew on than just hopes of a better future.
No dispute. Good or bad, the credit/blame lies with the Indian govt.
There is one problem: why would you have to negotiate to get proper support? That should be the logical follow up to any buy.
I meant better support for previously ordered aircraft. It should not have been an issue but contracts with Russia tend to be … bumpy (to put it mildly). Plus the Indian MoD isn’t the most capable negotiator, case in point: omission of the MRO facility creation from the primary Su-30 contract.
In any case, its possible that serviceability issues can be/are being addressed without unusual UAC/Sukhoi support (MRO facility is already up and running), but additional Sukhoi orders would still have given some leverage to the MoD, for whatever it was worth.
Now, Dassault already has sold the Mirages and knows, obviously, what needs to be intalled. Most of the stuff might need different coding (IFF, Link16…), some frequencies change, all that is done through software as the aircraft has everything needed as far as hardware goes anyway. And if there are specific hardware modifications (some particular circuits), chances are Dassault has had the requirements long time ago and nothing prevents them from intalling the curcuits needed inside boxes fitting the aircraft’s available spaces
True but its far from assured that issues relating to hardware and software compatibility can be addressed in a period short enough to make immediate transfers of serving AdlA aircraft to the IAF feasible. Keep in mind that while Dassault might have a rough roadmap on how to proceed, given the structure of the erstwhile MMRCA contract, they probably intended to implement it on a new aircraft delivered a full three years after the signing of the contract, rather than an quickfire (& reversible) retrofit to in-service aircraft.
Something had to be done by the PM and DM to basically give the IAF new combat aircraft. the only other viable option was more Su-30MKIs and that meant another order for direct supplies from Irkut, not from HAL, which is already stretching to deliver 16 MKIs per year. And Irkut itself is already supplying Su-30SMs to Russia, so its not like their assembly lines are idle either, so it wouldn’t mean immediate deliveries either. Plus, Russia needs to focus on resolving the in-service spares and maintenance issues for the already massive 200+ Su-30MKI fleet. There was no need to reward them with another 40 Su-30MKI order.
The IAPO line had at least as much elasticity as Dassault’s Merignac line in terms of committed orders. Also there’s no reason for an order of extra Sukhois to take the focus off addressing in-service issues with the Su-30MKIs. In fact, they could have used the prospect of supplementary orders to negotiate a deal on improving after-sales support from UAC/IAPO.
So what would India gain by ordering more Su-30MKIs directly from Russia then? Nothing, other than saving on infrastructure and training costs that are associated with a new type’s intro into service. But remember that one of the primary aims of the MRCA was to end dependence on a single country for all your fast jet needs, and so more Su-30MKIs were not an ideal option, in fact that would be the last ditch option. And the Rafale had comprehensively won the evaluations carried out by the IAF, so they really weren’t talking about pushing a hog into service just because it was Western. This whole line of questioning by some fellows here, on why Rafales were ordered, is absurd and mostly related to all these fantastic scenarios of strategic gains and what not..
Even if go by the principle of diversification, fact is the Rafale’s L1 position was specific to the MMRCA process which has been abandoned. Ideally, they should have opened parallel negotiations with EF (which also cleared the IAF’s evaluations) & LM. If nothing else, that would at least squeeze the Rafale’s cost down. As things stand this deal clearly appears a product of political grandstanding and still well short of the value that the Indian MoD ought to be putting on its dollar/rupee (regardless of mismanagement by previous administrations).
The missile in flight will not see from the same point of view as the DAS which is on the plane. Will the DAS be able to tell the missile exactly where to look from his point of view, that’s the question.
The missile is equipped with an inertial navigation system and a two-way datalink to the aircraft. How do you think radar guided missiles accept mid-course updates from the launch aircraft if they cannot see from the same point of view as the radar?
It might work, we’ll see when they test it. One thing’s for sure, a LOBL launch works very reliably, and the plane could pull a hard turn a get a shot quickly with the help of the DAS/HMD.
How do you know that LOAL doesn’t work reliably?
I am not criticising the EOTS here. The fact that it has a wide FOV is good indeed ( even though it is not a pure air to air IRST ).
We’re talking WVR or near-WVR. ‘Pure air to air IRST’ is irrelevant.
I never said that the missile’s seeker should scan the entire FOV. I say that the DAS will tell the pilot in which direction the threat is coming from, and the missile’s seeker will be cued to the DAS while it is on the rail.
There’s no reason why the missile’s seeker must be cued while its on the rail.
This way the pilot can either immediately shoot if the threat is in the forward hemisphere, or make a quick turn to expose the missile’s seeker. It would happen very quickly because the missile’s seeker is already cued to the DAS.
The missile can turn tighter than any aircraft. Instead of turning the aircraft, you let missile turn and lock on.
At least in that case you’re sure that the missile will achieve lock on, because there is no distance/velocity issue. It is in LOAL mode that it gets awkward, because of course the DAS and the missile are not looking from the same spot.
The aircraft and missile are connected by a two-way datalink. Spatial awareness is not an issue any more than it is for two fighters sharing a Link 16 connection.
The LOAL is a good capability to extend the effective range of the missile or to get off boresight shots with reliable targetting informations, which is not the case with a DAS like system.
The missile has an excellent IIR seeker and cues from the DAS, which is a lot more effective and reliable than a plain vanilla HMS.
How can this have no bearing on resolution lol? The sensor scans 120 degrees, which is a a huge volume, how can you expect to get a decent resolution with that? Originally the system was a missile launch detector, it is NOT an IRST.
The presence or absence of an optical zoom has zero bearing on the DAS’ native resolution. Where required the pilot can digitally magnify DAS imagery.
Why don’t you go ahead and define ‘decent’ resolution and then contrast the figures with the actual (indecent) resolution. ‘Originally’ =/= ‘Currently’
Most air forces will use the F-35 as their primary fighter, and the USAF will in the end have a limited number of F-22s. Not making sure ( with enough missile tests ) that it would be a competent dogfighter with very good off boresight capability was a bad idea.
Neither did you, given the fact that this DAS/LOAL capability has never been tested before.
Both the LOAL & DAS have been tested. And even in a very primitive form where it provides no mid-course updates to missile and does not track surrounding aircraft, the DAS is still far better than any HMS by virtue conferring 360 deg visibility to the pilot even in inclement weather.
Surely you’re aware of how the Indian procurement system works by now..small orders, followed by larger follow-on orders..the Su-30MKI deals, the MiG-29K deals, the Pilatus deal, the C-130J, the P-8I..the list goes on.
The Su-30MKI yes, but all the rest are single contract deals with options for more aircraft (at a fixed cost). As per most reported information, follow-on orders for the Rafale in contrast will be negotiated independently. So they lose the cost benefits of a larger purchase and also lose the constant price gotten through an ‘option’ on the contract.
One can be pretty sure that there will be more Rafales ordered, but whether or not the ToT and local assembly line goes ahead, one can’t be sure.
According to the DM, all future Rafale orders will be negotiated directly with the French govt, thus excluding HAL-Dassault/Reliance-Dassault licensing/ToT deals from the reckoning.
Of course the missile can only lock on the target in the forward hemisphere, but if it does so, its probability of kill is quite high. With a DAS guided shot, it is not sure that it will acquire the target within one second after launch during a hard pull, when it doesn’t even know where the target is exactly.
The EOTS tracks all targets in the frontal hemisphere a lot more effectively than the best missile seeker. And any pilot turning hard, where enemy aircraft can emerge at any aspect, will not want the limitation of cockpit visibility or missile FoV. (BTW not all missiles can scan 90 deg off-boresight. Eg – MICA-IR.)
The DAS/HMD would have been nice to have capabilities even with the ability to lock on before launch.
If it turns out that the target is behind the F-35, the pilot could have done a high alpha turn to get a quick HOBS shot, or even the DAS could have been used to get a shot in LOAL mode, but with a lower pk.
There’s a reason they put a two-way datalink on the Aim-9X Blk2. LOBL or LOAL, makes no difference to its pk. If the target is behind the F-35, he doesn’t need to pull a high alpha turn, he can launch irrespective of aspect or speed, and the missile will be guided both by the DAS and by its HOBS seeker, meshing together for a high pk.
The DAS is not an an IRST, it doesn’t have the ability to focus on a target. So its resolution will obviously be poor. To have an accurate speed, you need very accurate position data to be able to calculate the velocity vector. You won’t get that with that kind of sensor.
The DAS is an IRST. By definition. And while its not equipped with an optical zoom function, that has no bearing on its native resolution.
The JSF was not designed as a pure fighter, and was meant to be cheap. So they skipped the side bays and found this half-ass solution with a distributed aperture system.
– The last aircraft designed as a ‘pure fighter’ was decades ago.
– It’ll match the Eurocanards at FRP which is cheap enough for most operators.
– Half assed solution is what any F-35 pilot will call an HMS dependent dogfighter. Line up your aircraft with your target or you’re sunk. (And then hope and pray the missile does the job without help.)
Time will tell if it really works.
Sounds like you didn’t wait for ‘time’ before making up your mind.
With an HMS shot the missile is locked before launch. The missile’s seeker looks straight at the target so has a much better resolution of it than a wide field camera like the DAS would.
No its not. The missile seeker can scan only the frontal hemisphere, a large portion of which will be masked by the airframe. In addition, the pilot will be limited by what he can see from his cockpit. BTW at WVR ranges, locking on before launch would not significantly increase the pk compared to a lock achieved after launch.
How can the DAS have the distance with its poor resolution, except for a very vague estimate? How can it have the airspeed of the target given that it doesn’t know the distance, so the variation of the distance in the first place. To be able to do that, the F-35 would have to combine the DAS with the EOTS which probably has a telemetry capability, or at least a much better resolution of the target. Would using the EOTS work in a dogfight when he planes are moving fast relative to one another? That get very complicated.
The DAS’s actual performance with its ‘poor resolution’ (according to whom?) will be known to those who need to know. According to NG, it has the capability to ID other aircraft around it, which would make determining speed/range relatively easy. A more relevant question is how does your HMS cue a target that’s out of the cockpit’s viewing zone, or out of the missile seeker’s scan zone, how does it calculate distance/airspeed/bearing and how does it update the missile in flight?
Who cares about ALA when there is Apache. The real question is can Rafale handle Kh-31?
Apache? SCALP-EG or ASMP-A yes, but hardly the Apache which is successor to the Durandal. With diminishing numbers of ordered Rafale on one hand, and crashing Franco-Russian relations on the other, its likely that the Kh-31 integration will fall through.
Not likely, given that the “Air Launched Article” is basically an air-launched BrahMos that Rafale is unable to carry. Forty MKI airframes have been strengthened for the task.
Not the ‘Air Launched Article’ (which is a paper project at the moment), just the BrahMos-A. But you’re right in that the purpose built BrahMos equipped Su-30s will be the platform of choice for strategic air missions. The first choice however is still likely to be the Nirbhay LACM. In the end, 36 Rafales are too few to make a difference and too expensive to be a stopgap. They say more will be coming but if that were the case, there was no reason to postpone the second order to a later date. Payments would have been staggered in either case.
It looks like the govt is placing the order as a face-saving exit. Like emptying a gun for safety, but discharging the last round into your foot.
Dassault doesn’t build their own tooling any more than Lockmart. There are vendors that specialize in this. The tooling is not the problem with the price.
I know that which is why you’ll notice I said – supplied through Dassault. The fixed costs for production in France have already been amortized.
Also, its not just the tooling for the assembly line that’s contributes to the cost, its the entire supply chain servicing the Rafale project. For many of the contractors involved the Rafale is a ‘side-show’ that piggybacks off their primary business (be it supplying to Airbus, Alstrom or Areva). For local production in India, at minimum, the units involved in the production of spares have to be entirely replicated, often from scratch, without significant diversification for greater economies of scale. Plus, there’s a very significant overhead involved when it comes to parts sourced from the OEM. Point is, the manpower costs are far from the primary driver of the costs incurred in licensed production.
Only reporting what is being said. The. HAL’s manpower ratio brought the cost way too high.
The average cost of technical staff at HAL is probably $10-15,000/yr compared to $50,000+ in France. Even if the manpower ratio is 2.7:1, in plain monetary terms the former is a cheaper proposal.
There are no mention of the investments there. But the info is neither confirmed nor complete. In any case the ratio seem high, possibly due to considering more manual tasks ,with the problems this induce ,over investing in more machinery for automated tasks. On processing of wings composite for instance seems HAL did consider going manual as opposed, to Dassault.prescribed automated process .now in term of cost/benefit it might have been the wrong choice. Labor might be cheap, but numbers do not make for qualified resources and adapted process.
What you’re describing is actually the problem not a difference in approach. For example, HAL would be more than happy to adopt Dassault’s prescribed automated process for the manufacture of composites. That will however require a brand new very expensive machine supplied through Dassault. That cost is just one of many (both at the HAL assembly line & at the subcontractor level) contributing to the whopping cost of local production in India.
One detail that appear to be left out, in all that frenzy, is the HAL’s manpower ratio of 2.7 to 1, reported initially by Vishal Taphar, who seem to be the source of the news (link https://twitter.com/thaparvishal)
That is sure to be an ice cold, shower for anybody. Also very concerning ..
Given the labour costs in India, it may in fact be a cheaper proposition. The problem isn’t labour or efficiency, its quite simply the massive investment in infrastructure required to replicate the Rafale’s production chain in France.
Well, they should be concerned about seeing before believing. You can’t take for granted that revolutionary systems will work.
They have trouble apparently with flare discriminations with the DAS, and with vibrations in transsonic. How will that affect the pk of the missile is hard to tell for now. We will see when they really test missile launches. And not just one or two missiles, but at least 10 in all sorts of flight configurations. You don’t want to have bad surprises when it is time to go to war…
The DAS is supposed to track all enemies around it – bearing, air speed, altitude etc, use that data to optimize a missile shot for max pk, and employ the datalink post-launch to refine the trajectory with in-flight updates.
Even in the worst possible case, it cannot be worse than an HMS which just points the missile in the general direction of the target and expects missile’s seeker to do the rest. That’s hardly a problem for the DAS. And unlike the HMS it’s not limited by cockpit visibility.