19.01.2021, 23:28
https://www.aspistrategist.org.au/austra...placement/
Und selbst diese Aussagen sind alle fragwürdig. So ist das Datenkommunikationssystem des Tiger durchaus Link 16 kompatibel - bzw. wäre mit der MK3 Version ebenfalls ganz normal Link16 zur Verfügung gestanden.
Zitat:ASPI’s Marcus Hellyer noted in 2019 that flying hours have improved and the cost per flying hour has stabilised. With the Tiger’s airframe still enjoying flight-worthy hours, there’s no reason it couldn’t be sustained in service. Hellyer notes that in the judgement of the army’s leaders and aviation specialists it has reached a level of capability that’s deployable and useful in the current threat environment.
.......
Compared with the Tiger, the Apache is a much heavier platform and it has half the range—257 nautical miles versus 430 for the Tiger. The Apache’s suite of mission systems is fully developed, including advanced satellite communications and the Link 16 tactical data network. The Tiger has obsolescent radios, though an upgrade was in progress, and has an interim iTDL datalink developed by Elbit Systems, though not Link 16. These are major weaknesses, and the advanced digital connectivity of the Apache is a clear factor in its favour. In particular, the Apache can connect with and control armed drones through its manned–unmanned teaming (or MUM-T) system, a feature the Tiger lacks. Both helicopters have similar weapons capacity.
........
Operating cost also needs to be considered. The sustainment challenges of the Tiger drove up operating costs and shrunk flying hours—a death spiral for the capability. Airbus has suggested that operating the Tiger as it currently stands costs A$9,465 per hour; however a RUSI report estimated the cost per flying hour to be around A$27,000 and the defence annual report estimates it’s more like A$34,000 per hour. That’s in comparison to the Apache’s projected operating cost per hour at A$10,567.
Moving to the Apache also gets Australia into a very large user community—including many partners and regional countries, such as the US, Singapore, Indonesia, South Korea, Japan, Taiwan and the UK—which has benefits for interoperability, economies of scale, opportunities to learn from other users, and shared logistics.
........
the Apache must be seen not as a standalone or an army-only capability. It must be part of a system-of-systems networked capability for the entire ADF and must be able plug and play easily with the full range of ADF capabilities. The Apache is well placed to do that. For example, its advanced satellite communications and its Link 16 would enable it to share data with and be commanded from platforms such as the air force’s E-7A Wedgetail and the navy’s Hobart-class air warfare destroyers. The army will need to relinquish sole control of Apache to ensure it becomes an ADF capability, not just an army capability. That demands a significant cultural shift.
Third, the Apache needs to fully connect with armed autonomous systems. That means the ADF needs to get serious about a more ambitious and fast-moving autonomous systems strategy that deliver new capabilities later this decade, including for lethal autonomous weapon systems. It may imply additional capability acquisition for smaller ‘loitering munition’-type capabilities beyond the armed MQ-9B Sky Guardian unmanned aerial vehicle.
.........
Und selbst diese Aussagen sind alle fragwürdig. So ist das Datenkommunikationssystem des Tiger durchaus Link 16 kompatibel - bzw. wäre mit der MK3 Version ebenfalls ganz normal Link16 zur Verfügung gestanden.