- Look what we have here! From the vault, 48 pg #ebook no registration required.Our #CyberSecurity Summer Review '16. goo.gl/gNGC1A 7 hours ago
- #USNavy is sending warships on a freedom of navigation op in the #SouthChinaSea. Our warships report keeps count… twitter.com/i/web/status/8… 10 hours ago
- UK Sec of State Michael Fallon tells Munich Security Conference the migration consequences of Afghanistan, and UK d… twitter.com/i/web/status/8… 12 hours ago
- Mattis has given Europe #NATO 2% spend ultimatum. See what the #EU is doing for their own logistics in our intervie… twitter.com/i/web/status/8… 13 hours ago
- #Raytheon Missile Systems looks at the market trends for fighter jets and their place in the mix… twitter.com/i/web/status/8… 3 days ago
We are the IQ of global defence.
Secret testing grounds: Airborne electronic warfare comes of age in Libya
July 14, 2011Posted by on
The EW AORBAT (electronic warfare air order of battle) – in any strike scenario – is plagued by complexity. EA-6B Prowler and EA-18G Growler crews must, at all times, maintain complete situational awareness of the strike picture (and the threat picture), even as it ‘flexes’ in the real time threat environment. Libya has proven to be a significant testing ground for recent Growler developments and this infographic attempts to deconstruct the AEW strike mission in bite size chunks.
Click on the image above to enlarge.
Moving from top to bottom:
- Breakdown of airborne EW, ES (electronic surveillance) and EP (electronic protect) capabilities by country of origin.
- Essential parametrics of the EA-18G and EA-6B, presented side-by-side and including loadout, service ceilings, airspeeds and the like.
- A (very) notional description of the EW strike profile executed within the first days of the Libya campaign (I hope my former crewmates don’t hold me to account for this).
- And finally, a geographic layout of the AD (air defence) profile along the Libyan coastline, with threat rings of relevant SAM systems.
The location of SAM sites and coalition strike packages is entirely notional (I don’t think I’ve ever written that disclaimer before).