Deprecated: Creation of dynamic property AAL_Main::$notifications is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/aryo-activity-log/aryo-activity-log.php on line 103

Deprecated: Creation of dynamic property AAL_Main::$export is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/aryo-activity-log/aryo-activity-log.php on line 104

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: Creation of dynamic property Mongoose_Page_Plugin::$settings_page_url is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/facebook-page-feed-graph-api/inc/class-mongoose-page-plugin.php on line 228

Deprecated: Creation of dynamic property Post_Views_Counter::$settings_api is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 128

Deprecated: Creation of dynamic property Post_Views_Counter::$functions is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 139

Deprecated: Creation of dynamic property Post_Views_Counter::$update is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 140

Deprecated: Creation of dynamic property Post_Views_Counter::$settings is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 141

Deprecated: Creation of dynamic property Post_Views_Counter::$admin is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 142

Deprecated: Creation of dynamic property Post_Views_Counter::$query is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 143

Deprecated: Creation of dynamic property Post_Views_Counter::$cron is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 144

Deprecated: Creation of dynamic property Post_Views_Counter::$counter is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 145

Deprecated: Creation of dynamic property Post_Views_Counter::$columns is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 146

Deprecated: Creation of dynamic property Post_Views_Counter::$crawler_detect is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 147

Deprecated: Creation of dynamic property Post_Views_Counter::$frontend is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 148

Deprecated: Creation of dynamic property Post_Views_Counter::$dashboard is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 149

Deprecated: Creation of dynamic property Post_Views_Counter::$widgets is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 150
印度國產航母測試升降機,僅能容下米格29K,美國法國又被耍了 – 有海水的地方就有中國人

印度國產航母測試升降機,僅能容下米格29K,美國法國又被耍了

印度國產航母測試升降機,僅能容下米格29K,美國法國又被耍了
2,226

印度海军近日公开了首艘国产航母“维克兰特”号(Vikrant, IAC-I)的最新测试画面,其中包括机库和升降机的画面都是首次公布。在完成现阶段试验后,“维克兰特”号将在未来两个月内正式服役,届时,印度将再次成为亚太地区拥有“双航母”的国家,整体海上作战能力亦得到提升。尽管印度对这艘航母寄予厚望,但在专家眼中这艘航母只不过是印度展示大国地位的象征性资产,其无论是设计还是设备,都面临着诸多弊病,若要形成完整战力恐怕要耗费不少时日。

▲ 印度国产航母“维克兰特”号的升降机尺寸(10m×14m)只能容纳一架米格-29

在这其中最让印度人头疼的当属舰载机问题。除了已经从俄罗斯采购的“米格”-29K/KUB及自用版的舰载型“光辉”(LCA)外,印度仍然在法国“阵风”-M及美国F/A-18E/F“超级大黄蜂”之间纠结。这时候有人会问为什么好好的“米格”-29K/KUB不用,偏要引入新机,徒增后勤负担呢?说到底还是印度飞行员对该机不靠谱的质量所引发的担忧。他们认为“米格”-29K机体结构存在缺陷,动力系统性能也不完美,在长期的飞行训练过程中容易产生损耗,自2016年该机正式交付印度海军以来,已经发生了三起坠机事故。面对印方的质疑,俄罗斯米格集团并没有主动揽责,而是要求受损的战机送返俄罗斯维修保养,企图再赚一笔费用。在意识到自己成了“冤大头”后,印度只能面向市场再度招标新一代舰载战斗机,取代老旧的“米格”-29K/KUB。

▲ 2018年1月3日,印度1架米格-29KUB战斗机在果阿邦的汉莎海军航空站起飞时坠毁

法国达索和美国波音为了争得印度海军高官的青睐可谓想尽了各种手段。达索公司的“阵风”-M于今年年初在“维克兰特”号的模拟甲板上进行兼容性实验,加之空基型的成功引进,因此优势相当大。其竞争对手波音公司也没有闲着,他们将F/A-18E/F“超级大黄蜂”整机升级到最新的Block III型,还在印度果阿邦的汉萨海军航空基地秀了几轮滑跃起飞/阻拦降落测试,给观摩军官留下深刻印象。理想很丰满,现实很骨感,尽管这两种机型都针对性的进行补充和改良,以达到上舰的目的,但这意味着它们在载弹量等方面会遭到严重限制,从而影响战力的发挥。除非印度有能力在未来十年内研发(或引进)带有弹射器的航母,否则就是花钱买罪受,独自承担后期昂贵的保养/训练费用。

▲ F/A-18E/F“超级大黄蜂”Block III 舰载战斗机升级细节

根据相关人士透露,印度虽然全力招标国外舰载机,但其长久目标仍然是研发建造印度国防部国防研究与发展组织(DRDO)与印度斯坦航空公司(HAL)联合推出的双发舰载战斗机(Twin Engine Deck Based Fighter, TEDBF)项目,以实现硬件的自给自足,这也贴合印度总理莫迪特别推崇的“印度制造”路线。该机使用与F/A-18E/F相同的F414推力涡扇发动机,配有AESA主动相控阵雷达及国产武器系统,最大速度1.8马赫、最大起飞重量26吨、最大载弹量8吨,仅从蓝图判断,各项性能数据都优于现役的“米格”-29K。

▲ TEDBF航展模型

有不少人将该机视为中号版的“光辉”,其实两者除了机体(单垂尾无尾翼加双三角翼布局)相似外,差距还是很大的。将单发改为双发,意味着整架飞机的气动布局需要进行大幅度的改动,各项数值皆推翻重算;考虑到隐身性能,包括飞机的材料、电子设备也都要换代,整个“脱胎换骨”般的工作量不亚于研制新机,我想印度人可能是受到F/A-18放大升级成F/A-18E/F的启发,因此才祭出这一对策。

▲ 2020年1月11日,印度“光辉”轻型舰载战斗机成功降落在“超日王”号航母

对于TEDBF项目,印度方面预测的最快首飞期限是2026年,对此,笔者认为印方有点过分乐观了,“超级大黄蜂”的改进美国投入了40多亿美元,而HAL对TEDBF的研发拨款只有130亿卢比(折合1.6亿美元),这让人不得不怀疑TEDBF是否会重走“光辉”的老路,另外,印度连自己的五代机AMCA都没摸索清楚,又从哪里来的技术经验去打造4.5代舰载战斗机呢。假设印度一路走到黑,真的在2026年把TEDBF搞出来的话,面对我们已经形成战力的“海五代”歼-35舰载战斗机难道就不犯怵吗?

▲ 我国自研自产歼-35舰载战斗机有望在未来三年内入役

摆在印度面前的还有个残酷的现实——俄罗斯的将印度拿捏得死死的,从最新放出的视频来看,印度维克兰特号国产航母的升降机大小只能勉强放下米格29K,已经基本上断绝了其他重型舰载机的上舰可能,阵风M的机翼无法折叠,更不可能放下,几轮竞标测试,印度人看来又把美国和法国给耍了。由于“维克兰特”号采用的是滑跃起飞、拦阻着舰的俄式设计,因此无论出于何种原因,在印度国产航母二号舰“维沙尔”(据传采用电磁弹射系统)问世前,印度海军只能硬着头皮将“米格”-29K/KUB当做舰载航空部队的主力机型,提出采购其他国家舰载机,估计也只是想从中获取一些经验和技术,助力自己的国产机研发。

在舰载机招标中,不管印度最终敲定了哪一方的飞机,对美国而言都是符合自身利益的:削弱俄罗斯在国际军火市场上的影响力,从而拉拢印度向西方靠拢,继而影响到周边地区的国际局势,这正是美国所希望的景象。印度作为南亚最大的发展中国家,有着成为世界强国的雄心壮志,不可能一直被人当枪使,如果他们足够务实的话,那么在舰载机上继续选择“米格”-29K,并且投入更多资金技术用于TEDBF研发,从长远来看无疑是最精明选择。但不管怎么样,以印度目前的实力,想要成为比肩中美的航母大国,依旧不太现实。

▲ 与“维沙卡帕特南”级驱逐舰进行编队训练的“维克兰特”号航母

Leave a Reply

Your email address will not be published. Required fields are marked *

You cannot copy content of this page

error: Content is protected !!
%d bloggers like this: