Pratyush wrote:
Why would you need to have working prototype. What is being done that requires this action. The airframe remains unchanged. The 414 integration is not a huge issue. The big change is the addition of AESA radar.
So why.
Not like the mk2 which is effectively a new design fighter.
There is still confusion about the scope of work for MK1A and MK2.
Changing the engine to GE F414 is not part of MK1A. It is for MK2 only.
MK1A has only the following major requirements:
1). Radar change to AESA Elta 2052.
2). Addition of an external EW pod. Seems it will be Israeli pod. Will be mounted mostly using a twin rack system on the mid wing pylon.
3). Internal re-organization of LRUs for ease of maintenance. Some LRUs might be indegenized, as this is a continuous endeavour. Fighting obsolescence is also a factor and some LRUs will be updated on this count.
4). Integration of better BVR missile to take advantage of the higher range radar. Most likely will be Derby-ER. If problems with Python V can be sorted out, the same will be integrated as well.
5). Software defined radio SDR, will also likely be a requirement. Some reports suggested that IAF was asking for it as part of FOC. So I guess it will be included as a requirement for MK1A.
6). Any possible weight reduction. HAL in its initial presentation for MK1A had claimed that some weight reduction is possible. Claims at the time quoted unrealistic figures like 800Kgs. However, maybe a reduction in the range of 150-300Kgs might be possible. Some of the dead ballasts used in the MK1 are likely to be got rid of.