#DesertStorm30 – Electric Avenue: Electronic Warfare and the battle against Iraq’s air defences during Operation Desert Storm

#DesertStorm30 – Electric Avenue: Electronic Warfare and the battle against Iraq’s air defences during Operation Desert Storm

By Dr Thomas Withington

In January 1991, a US-led coalition launched Operation DESERT STORM to evict Iraq from Kuwait, which the former had invaded six months earlier. DESERT STORM was a combined operation involving a major air campaign. At the time, Iraq had one of the world’s most sophisticated air defence systems. The radars and communications necessary to spot hostile aircraft and coordinate their engagement were integral to this. As a result, the coalition correctly determined that the air campaign would only succeed by establishing air superiority and supremacy. This would be achieved through an Offensive Counter Air (OCA) campaign against the Iraqi Air Force (IQAF). A crucial part of this was an electronic war waged against Iraqi air defence radars and communications. This article explains the extent to which Iraq’s air defences threatened coalition air power, how the electronic war against these air defences was fought and why they were not able to overcome the coalition’s electromagnetic supremacy.

When Operation DESERT STORM began on the morning of 17 January 1991, Iraq possessed one of the world’s most fearsome Integrated Air Defence Systems (IADS). At 02:38, its demise began. Task Force Normandy, an armada of US Army AH-64A Apache gunships and US Air Force (USAF) MH-53J Pave Low helicopters attacked a group of IQAF radars. These were positioned a few miles behind the midpoint of the Saudi-Iraqi border within the Iraqi 1st Air Defence Sector’s area of responsibility. The radars consisted of P-18 Very High Frequency (VHF), P-15 Ultra High Frequency (UHF) and P-15M2 UHF ground-based air surveillance radars.[1] This attack left a large swathe of Iraq’s southwest airspace without radar coverage. As a result, Iraq’s IADS failed to detect waves of incoming aircraft tasked with hitting strategic targets. These planes followed USAF F-117A Nighthawk ground-attack aircraft which had slipped through Iraqi radar coverage earlier to hit targets in Baghdad.

The Story so Far: From Vietnam to DESERT STORM

The United States had learned about well-operated air defences the hard way during the Vietnam War. Vietnam’s air war saw the United States lose over 3,300 fixed-wing aircraft across all services. Rotary-wing and uninhabited aerial vehicle losses pushed this figure to over 10,000.[2] In addition, the North Vietnamese IADS, consisting of Anti-Aircraft Artillery (AAA) and SA-2 high-altitude Surface-to-Air Missiles (SAMs), reaped a grim toll on American aircraft. The experience led to the development of the USAF’s Wild Weasel concept.

Republic F-105G
Republic F-105G ‘Wild Weasel’ in flight on 5 May 1970. External stores include QRC-380 blisters, AGM-45 Shrike and AGM-78B Standard Anti-Radiation Missile. (Source: Wikimedia)

First seeing service in the summer of 1965, customised F-105F Thunderchief fighters outfitted with radar detectors, listened for transmissions from an SA-2’s accompanying radar. The purpose of locating the accompanying radar was that it helped locate the associated SAM battery. The aircraft would then attack the radar, initially with gunfire and rockets and later with specialist Anti-Radar Missiles (ARMs). These attacks destroyed the radar site and blinded the SAM site, thus reducing the threat to incoming attack aircraft. These aircraft were eventually upgraded to F-105G standard. The Wild Weasel concept was progressively honed during and after the Vietnam War with ever-more capable radar sensors, ordnance, and platforms. When the USAF deployed to Saudi Arabia in 1990, the Wild Weasels used F-4G Phantom-II jets with sophisticated radar-hunting equipment and AGM-88 high-speed anti-radar missiles.

The skies over Southeast Asia gave the US armed forces, and their North Atlantic Treaty Organisation (NATO) allies a taste of the potency of Soviet and Warsaw Pact air defences as they had for the Israeli Air Force during the Six-Day War of 1967 and the Yom Kippur War of 1973. No sooner had the last US units left Vietnam than the so-called ‘New Cold War’ began to unfold. Both NATO and the Warsaw Pact prepared for a confrontation that might engulf East and West Germany. Part of the Warsaw Pact’s role was to ensure that air approaches into the European USSR were heavily defended. This required robust IADSs of fighter defences and an umbrella of short-range/low-altitude, medium-range/medium-altitude SAM systems covering the altitudes NATO aircraft were likely to use. This SAM umbrella protected everything from dismounted troops on the front line pushing through the Fulda Gap on the Inner German Border to strategic politico-military leadership targets in the Soviet Union.

The Wild Weasel units were not the only assets involved in degrading Soviet air defences. Also important were SIGINT (signals intelligence) platforms, such as the USAF’s RC-135U Combat Sent ELINT (Electronic Intelligence) gathering aircraft. These aircraft allowed NATO to develop an understanding of where the radars supporting Soviet and Warsaw Pact air defences were situated. Understanding where the radars were located allowed NATO to build up an electronic order of battle of the ground-based air surveillance radars and Fire Control/Ground-Controlled Interception (FC/GCI) radars the air defences depended upon to detect and engage targets with SAMs or fighters. Many aircraft configured to collect SIGINT and prosecute Soviet/Warsaw Pact air defences were the same that deployed to the Persian Gulf. After arriving, they soon discovered similar defences to those on the eastern side of the Inner German Border.

KARI: Defending Iraqi Airspace

The US Department of Defence’s official report on DESERT STORM did not mince its words regarding the potential ferocity of Iraq’s IADS:

The multi-layered, redundant, computer-controlled air defence network around Baghdad was denser than that surrounding most Eastern European cities during the Cold War, and several orders of magnitude greater than that which had defended Hanoi during the later stages of the Vietnam War.[3]

The components of Iraq’s air defence system were sourced from the USSR and France. In the wake of the 17 July Revolution in 1968, which brought the Iraqi affiliate of the Arab Socialist Ba’ath Party to power, France steadily deepened its relationship with Iraq. As a result, France sold some of its finest materiel to Iraq during the 1970s and 1980s. For Iraq’s President Saddam Hussein, who had seized power in July 1979, this was ideal.

With tensions growing between Iraq and Iran, the Iraqi armed forces needed as much support as the regime could muster. They were not disappointed. Paris supplied Roland Short-Range Air Defence (SHORAD) SAM batteries. The Soviet Union, meanwhile, furnished Iraq with SA-2 batteries, SA-3 medium-range/medium-altitude, SA-6A low/medium-altitude/medium-range, SA-8, and SA-9 SHORAD SAM batteries. Additional SHORAD coverage was provided by a plethora of ZSU-23-4 and ZSU-57-2 AAA systems and SA-13 Man-Portable Air Defence Systems (MANPADS). The SAMs were mainly to protect Iraqi strategic targets. Divisions of the elite Republican Guard also had some organic SA-6 and Roland units. AAA was used for corps and division air defence, along with the point defence of strategic targets. These units would also have MANPADS coverage, some SA-8s and Rolands. These provided air defence coverage over the manoeuvre force.[4]

These air defences received targeting information from Chinese-supplied Type-408C VHF ground-based air surveillance radars with a range of 324 nautical miles/nm (600 kilometres/km). Iraq received five of these radars between 1986 and 1988. France also supplied six TRS-2215/2230 S-band ground-based air surveillance radars between 1984 and 1985. These had a range of 335nm (620km).[5] Iraq supplemented these with five French TRS-2206 Volex ground-based air surveillance radars transmitting on an unknown waveband with a range of 145nm (268.5km). The Soviet Union also supplied several ground-based air surveillance and height-finding radars for use with Iraq’s SAM batteries and independently. These included six P-12 and five P-14 VHF ground-based air surveillance radars with ranges of 135nm (250km) and 216nm (400km), respectively, plus ten P-40 radars with a 200nm (370km) range and five PRV-9 height-finding radars with a 162nm (300km) range.[6]

The IQAF’s radars, fighters, airbases, SAM batteries and supporting infrastructure that provided operational/strategic level air defence were networked using the French-supplied KARI Command and Control system.[7] The nerve centre of the IADS was the Air Defence Operations Centre in downtown Baghdad. This was responsible for Iraq’s operational/strategic air defence, particularly industrial and political installations.

Iraq’s airspace was segmented into four sectors (see figure 1).[8] Each was commanded from a Sector Operations Centre. Subordinate to the Sector Operations Centres were the Intercept Operations Centres. The Intercept Operations Centres would control a segment of airspace in a specific sector using organic radars. Their radar pictures would be sent to the Sector Operations Centre. There they would be fused together creating a Recognised Air Picture (RAP) of the sector and its air approaches. The recognised air picture was sent up the chain of command to the Air Defence Operations Centre using standard radio, telephone, and fibre optic links. A ‘Super RAP’ of Iraq’s airspace and approaches was created at the Air Defence Operations Centre. KARI used several means of communication to provide redundancy. If radio communications were jammed, communications with the Air Defence Operations Centre could be preserved using telephone and fibre optic lines. If telephone exchanges and fibre optic nodes were hit, radio communications could be used.

Iraq Air defence
Figure 1 – Iraqi Air Defence Sectors, Sector Operations Centres, and Intercept Operations Centres

Cooking up a Storm

Coalition air planners had two critical Iraqi threats to contest in the bid to achieve air superiority and air supremacy; the Iraqi IADS and deployed Ground-Based Air Defences (GBAD) protecting the Iraqi Army and Republican Guard units. The IADS/GBAD had to be degraded to the point where they would effectively be useless if coalition aircraft enjoyed relative freedom in the skies above the Kuwait Theatre of Operations. Electronic Warfare (EW) was intrinsic to this effort. The IADS and GBAD relied on air surveillance, battle management and weapons control.[9] Air surveillance was dependent on radar, battle management was dependent on communications, and both depended on the electromagnetic spectrum.

The concept of operations for coalition electronic warfare to support the air campaign was to attack the two electronic elements of the IADS/GBAD, namely radar and radio communications, without which situational awareness and command and control would be badly degraded if not neutralised altogether. Alongside electronic warfare, kinetic attacks on radars were made using anti-radiation missiles and against key nodes and targets in the IADS using conventional ordnance. Following Kuwait’s occupation, the coalition’s immediate task was to build an electronic order of battle of the radars and communications intrinsic to the IADS and GBAD. Space and airborne assets were instrumental to this effort. Although much information regarding the specifics of the US Central Intelligence Agency/National Reconnaissance Office Magnum SIGINT satellite constellation remains classified, they were almost certainly employed to collect raw signals intelligence germane to the IADS/GBAD. This would have been analysed at facilities in the US before being disseminated to allies.[10]

SIGINT collection followed a hierarchical approach. The Magnum satellites made a ‘broad brush’ collection of Iraqi electromagnetic emissions, discerning potential signals of interest from radars or communications from the prevailing electromagnetic noise generated by the country.[11] Further investigation of these signals of interest would be done using airborne SIGINT assets.[12] For example, the USAF based two RC-135Us at King Khalid International Airport, Riyadh, Saudi Arabia.[13] These jets flew close to Iraq’s borders to ‘hoover up’ as much ELINT as possible.[14] This served two purposes. First, the collection of ELINT allowed the coalition to determine which radars were used by Iraq’s IADS/GBAD and where they were located. This allowed potential gaps or more weakly defended areas in Iraqi air defence coverage to be identified. Second, regular ELINT collection allowed SIGINT experts to determine the pattern of electromagnetic life. This would have helped answer pertinent questions about whether Iraqi SA-2 batteries switched their radars off every evening or every weekend. By identifying geographical or temporal gaps in radar coverage, coalition planners could take advantage of weak coverage.

American SIGINT aircraft were joined by Royal Air Force Nimrod RMk.1s flying from Seeb airbase in Oman, and Armée de l’Air (French Air Force) C-160G Gabriel and DC-8F Sarigue SIGINT planes based at King Khalid International Airport. However, the Iraqis knew they were being watched. Iraqi air defenders had correctly deduced that coalition SIGINT efforts would extract as much usable SIGINT as possible. As a result, they tried to keep their radar and radio use to a minimum while coalition warplanes relentlessly probed Iraqi air defences to tempt radar activation and communications traffic for collection by SIGINT aircraft hanging back from the fighters.[15]

Support was also provided by the US Navy’s Operational Intelligence Centre’s Strike Projection Evaluation and Anti-Air Research team, better known as SPEAR. This unit helped build a comprehensive order-of-battle of the Iraqi IADS/GBAD.[16] In cooperation with the USAF and national US intelligence agencies, SPEAR identified key nodes in the Iraqi IADS that would badly degrade its efficacy if destroyed.[17] In addition, the process helped draft simulation programmes that built an increasingly detailed model of the Iraqi IADS/GBAD system. These programmes were continually updated as new intelligence arrived, allowing analysts to perform ever-more detailed replications of the expected potency of Iraqi air defences.[18]

DESERT SHIELD
An RC-135V/W Rivet Joint from the 9th Strategic Reconnaissance Wing approaches a KC-135 Stratotanker from the 1700th Air Refueling Squadron Provisional during Operation DESERT SHIELD. (Source: Wikimedia)

Alongside the RC-135Us discussed above, USAF RC-135V/W Rivet Joint and US Navy EP-3E Aries planes primarily collected Communications Intelligence (COMINT) on Iraq’s IADS/GBAD. Although the Rivet Joints were primarily configured to collect COMINT from radios and telecommunications transmitting on V/UHF wavebands of 30 megahertz to three gigahertz, these frequencies were also used by several Iraqi early warning and ground-based air surveillance radars. This allowed the Rivet Joints to assist their Combat Sent counterparts in gathering ELINT.[19]

Determining Iraq’s electronic order of battle allowed the radars to be attacked kinetically by USAF F-4G Wild Weasels using the AGM-88B/C missiles. Radars were also engaged electronically by USAF EF-111A Raven EW aircraft. Likewise, radio communications were attacked electronically with USAF EC-130H Compass Call planes. However, the USAF was not the only custodian of the suppression of enemy air defence mission. The US Navy was an avid user of the AGM-88 and, together with the US Marine Corps (USMC), flew EA-6B Prowlers. These jets could electronically and kinetically target hostile radars and gather ELINT.

Now in the streets, there is violence

‘The attack on the Iraqi electronic order of battle affected every aspect of the air supremacy operation,’ noted the official record of Operation DESERT STORM.[20] The initial focus of the electronic warfare battle was to destroy critical radars and communications nodes in the Iraqi IADS to paralyse the air defence network at strategic and operational levels.[21] At the tactical level, deployed SAM systems were then attacked with anti-radiation missiles when they illuminated coalition aircraft. This was done by patrolling F-4Gs and EA-6Bs, waiting for these radars to be activated or having the same aircraft and other anti-radiation missile-armed warplanes, such as the Royal Air Force’s Tornado GR.1 ground attack aircraft with their ALARMs (Air-Launched Anti-Radiation Missiles) accompany strike packages of aircraft. This had the dual purpose of helping keep these aircraft safe and continually attritting the kinetic elements of Iraq’s air defence.[22]

As noted earlier in this article, plans for attacking Iraq’s IADS/GBAD system became a reality in the early morning of 17 January. While Task Force Normandy laid waste to Iraqi radars, F-117As hit the Sector Operations Centres and Intercept Operations Centres in the 1st and 2nd Air Defence Sectors.[23] The actions of the Nighthawks and Task Force Normandy opened gaps in southern and western Iraqi radar coverage and air defence command and control network, which was then exploited.[24] Stealthy and non-stealth aircraft alike ingressed into Iraqi airspace to reach their strategic targets with electronic attack assistance provided by EF-111As and EA-6Bs. These platforms effectively jammed Iraqi early warning/ground-based air surveillance radars transmitting on V/UHF frequencies and FC/GCI radars transmitting in higher wavebands.[25] Typically, the EF-111As and EA-6Bs flew jamming orbits to protect air operations in a particular segment of the Kuwait Theatre of Operations. For example, USAF EF-111As flew orbits in western Iraq, providing jamming support to strikes in that part of the country, performing similar missions in the vicinity of Baghdad.[26] The EF-111As and EA-6Bs also relayed near-real-time updates on the Iraqi Electronic Order of Battle in their locale using radio and tactical datalink networks. Air campaign planners then adjust the air campaign’s electronic dimension accordingly.[27]

EA-6B DESERT STORM
EA-6B Prowlers of VAQ-130 refuelled by a KC-135 Stratotanker en-route to an attack during Operation DESERT STORM. (Source: NARA)

With one part of its radars destroyed and jamming afflicting the others, coalition aircraft headed into Iraq, clearing a path through the IADS, and hitting IADS targets with anti-radiation missiles and air-to-ground ordnance.[28] As well as hitting these targets, BGM-109 cruise missiles hit transformer yards dispersing carbon fibre filaments. This caused short circuits in the power supply.[29] Air defence facilities without backup power went offline. Even those with generators would still see their systems shut down before being reactivated, costing valuable time.[30]

Influenced by Israeli Air Force operations over the Bekaa Valley in Lebanon close to that country’s border with Syria in June 1982, another tactic used by the coalition was the use of USAF launched BQM-74C Chukar drones to mimic coalition combat aircraft ingressing Iraq’s 1st Air Defence Sector. The intention was for Iraqi air defenders to illuminate the drones and engage them. This allowed anti-radiation missile-equipped aircraft to determine the position of SAM batteries engaging the drones and attack their radars. The US Navy performed similar missions with their ADM-141A/B Tactical Air-Launched Decoys This was an effective tactic as it not only revealed the location of Iraqi SAM batteries, but it forced them to expend missiles.[31]

The Continuing Campaign

Initial overtures in the air defence suppression campaign were aimed at attritting Iraqi long and medium-range/high and medium-altitude SAM systems to help sanitise the airspace for following coalition strikes.[32] Typically, AAA would be effective up to altitudes of circa 15,000 feet/ft (4,572 metres/m), with Iraqi SAM batteries effective up to circa 40,000ft (12,192m).[33] The controlled kinetic and electronic violence unleashed against the Iraqi IADS/GBAD during the first 24 hours of the war was palpable. The official record notes that almost 48 targets, including an array of air defence aim points, were hit: ‘This was not a gradual rolling back of the Iraqi air defence system. The nearly simultaneous suppression of so many vital centres helped cripple Iraq’s air defence system.’[34] This inflicted a level of damage from which the Iraqi IADS/GBAD could not recover.

As the campaign unfolded Iraqi air defenders learnt that activating their radar invited an AGM-88 or ALARM attack. By the end of the first week of combat operations, the Iraqis realised that a significant dimension of the coalition air campaign focused on destroying their air defences.[35] SAMs would still be fired ballistically in the hope of a lucky strike, but sans radar, SAM capabilities were severely degraded. Switching off the radars did not stop the attacks. AAA or SAM sites that kept their radars switched off were engaged with conventional air-to-ground ordnance.[36] Life was increasingly unpleasant for Iraqi air defenders who realised that switching off their radars did not stop the attacks. One can only imagine the demoralisation this must have caused.

Assessment

Benjamin Lambeth correctly asserted that DESERT STORM exemplified the decisive migration of electronic countermeasures and EW in general ‘from a supporting role to a direct combat role.’[37] Quite simply, without EW, the coalition would not have succeeded in degrading the Iraqi IADS/GBAD to a point where it could no longer meaningfully challenge coalition air power in such a short space of time. One of the major successes of the electronic warfare aspect of the air campaign was its dislocation of Iraqi IADS/GBAD command and control. Despite the technological sophistication of KARI, it could not mitigate the hierarchical nature of Iraqi air defence doctrine. The Intercept Operations Centres struggled to operate when their Sector Operations Centre and the Air Defence Operations Centre was neutralised.[38] There appeared to be little redundancy within KARI by which these centres could assume the responsibilities of their destroyed or badly degraded counterparts. For instance, the Air Defence Operations Centre was destroyed as a priority target at the start of the air campaign. It does not appear that Iraqi air defenders could rapidly replicate Air Defence Operations Centre functions at either a back-up facility or at one of the Sector Operations Centres. Likewise, when Sector Operations Centres were taken out of the fight, their functions were not immediately assumed by Intercept Operations Centres in their area of responsibility or adjacent sectors.

While KARI was a sophisticated system, Iraq possessed radars and SAM systems already known to the US and its allies on the eve of DESERT STORM. The US had encountered similar SAM systems in the skies over Vietnam and during Operation Eldorado Canyon in 1986 when the US attacked strategic targets in Libya in retaliation for the sponsorship of political violence by its leader Colonel Muammar Gaddafi. Likewise, Israel had faced similar defences during numerous conflicts with its neighbours. Although Israel remained outside the US-led coalition, it is all but certain that intelligence germane to Iraq’s air defence systems would have been made available to the US.[39] The French are also thought to have shared intelligence regarding Iraq’s Roland and KARI systems in a similar fashion.[40] Egypt, an avid user of Soviet-supplied air defence equipment and member of the US-led coalition, was also believed to have been furnished the latter with intelligence.[41] Some of Iraq’s air defence equipment may have lacked Electronic Counter-Countermeasure (EECM) protection to exacerbate matters. Some of Iraq’s radars, notably early versions of the SNR-75 S-band and C-band 65nm (120km) to 75nm (140km) range fire control radars accompanying the SA-2 batteries may not have been fitted with ECCM.[42]

Once the war commenced, the Iraqis fell for the US ruse of using drones to seduce radars into revealing themselves, only to receive an ARM for their trouble. A glance at the history books would have revealed that given the success the Israeli Air Force had enjoyed using this tactic a decade previously, there was every chance the coalition may follow suit. This tactic was recently revisited during the 2020 conflict between Azerbaijan and Armenia. The Azeri armed forces skilfully exploited Uninhabited Aerial Vehicles (UAVs). UAVs were used to tempt Armenian GBADs to activate their radars. By activating the radars their location could be determined, and the GBADs then struck with suicide UAVs equipped with explosives.

Furthermore, Iraq’s air defence doctrine lacked flexibility. Indeed, it has been argued that Iraq’s air command and control writ large during the preceding Iran-Iraq War was characterised by over-centralisation and rigid planning.[43] This may have resulted from two factors; the authoritarian nature of Saddam Hussein’s regime and the procurement of Soviet materiel not only for air defence but across the Iraqi armed forces with a similar acquisition of Soviet doctrine not known for its flexibility.[44] There are significant questions to ask regarding the degree to which subordinates in the IADS believed they had latitude and blessing for individual initiative in the tactical battle. Similar questions apply to higher echelons. Did operational commanders in the air force and air defence force feel emboldened to take decisions as the battle unfolded? Saddam Hussein presided over a totalitarian state where insubordination, real or perceived, could be punished harshly. This raises the question as to whether the fear of taking the wrong decision paralysed decision-making. The result being that the Iraqi IADS lost the initiative in the coalition’s electronic battle. An initiative it never recovered. The net result of a lack of doctrinal flexibility, and against the backdrop of Saddam Hussein’s regime, meant that Iraq’s air defences did not respond and adjust to the electronic battle. Tactical and operational flexibility did not extend beyond radar operators switching off their systems to avoid an attack by an ARM.

However, the coalition’s success was underpinned by a vitally important factor, the luxury of time. DESERT STORM was not a ‘come as you are’ war. The US and its allies had 168 days between Iraq’s invasion of Kuwait and the commencement of the air campaign to plan the electromagnetic scheme of manoeuvre that supporting the air war.

DESERT STORM underlined a truism in air power: Air superiority as a prerequisite for air supremacy must be achieved over an opponent as early as possible. OCA was central to this effort. Electromagnetic superiority and supremacy are central to OCA. One must ensure one can manoeuvre in the spectrum with minimal interference from one’s adversary while denying their adversary use of the spectrum. Working towards electromagnetic superiority and supremacy reduces red force access to the spectrum, denying its use for situational awareness and command and control. Denying Iraqi air defenders’ situational awareness and command and control blunted the efficacy of the kinetic elements of Iraq’s IADS/GBAD, which were then attritted using ARMs and conventional ordnance.

DESERT STORM ended on 28 February. Electronic warfare was intrinsic to the air campaign’s success. Iraq’s IADS and GBAD were prevented from meaningfully interfering with the coalition’s actions. However, this was not the end of the story. The US and the UK would continue to confront the rump of Iraq’s air defences for several years to come until the final showdown with Saddam Hussein’s regime in 2003.

Dr Thomas Withington specialises in contemporary and historical electronic warfare, radar, and military communications, and has written numerous articles on these subjects for a range of general and specialist publications. He holds a PhD from the University of Birmingham.

Header image: EF-111A Raven aircraft prepare to take off on a mission during Operation Desert Shield. (Source: Wikimedia)

[1] C. Kopp, ‘Operation Desert Storm: The Electronic Battle, Part-2’ @http://www.ausairpower.net/Analysis-ODS-EW.

[2] J. Schlight, A War Too Long: The USAF in Southeast Asia 1961-1975 (Washington DC: Air Force History and Museum Programme, 1996), p. 103.

[3] Conduct of the Persian Gulf War: Final Report to Congress, (Alexandria, VA: US Department of Defence, 1992), p. 15.

[4] Ibid.

[5] Author’s proprietary information.

[6] Ibid.

[7] KARI is the French name for Iraq spelt backwards.

[8] ‘Iraqi Air Defense – Introduction’.

[9] P.W. Mattes, ‘Systems of Systems: What, exactly, is an Integrated Air Defense System?’, The Mitchell Forum No.26, (Arlington VA: The Mitchell Institute, June 2019), p. 3.

[10] Confidential interview with US electronic intelligence expert, 17/3/21.

[11] Ibid.

[12] Ibid.

[13] Ibid.

[14] Ibid.

[15] S. Morse (ed), Gulf Air War Debrief, (London: Aerospace Publishing, 1991), p. 37.

[16] Conduct of the Persian Gulf War, p. 124.

[17] Ibid.

[18] Kopp, ‘Operation Desert Storm’.

[19] Morse (ed.), Gulf Air War Debrief, p. 37.

[20] Conduct of the Persian Gulf War, p. 220.

[21] Kopp, ‘Operation Desert Storm’.

[22] Ibid.

[23] Conduct of the Persian Gulf War, p. 153.

[24] Ibid.

[25] Ibid, p. 172.

[26] Ibid, p. 220.

[27] Ibid.

[28] Kopp, ‘Operation Desert Storm’.

[29] Ibid.

[30] Confidential interview with US electronic intelligence expert.

[31] Kopp, ‘Operation Desert Storm’.

[32] Ibid.

[33] Conduct of the Persian Gulf War, p. 202.

[34] Ibid, p. 156.

[35] C. Kopp, ‘Operation Desert Storm: The Electronic Battle, Part-3’ @http://www.ausairpower.net/Analysis-ODS-EW.html consulted 12/2/21.

[36] Ibid.

[37] B. Lambeth, The Winning of Air Supremacy in Operation Desert Storm, (Santa Monica, CA: RAND Corporation, 1993), p. 5.

[38] ‘Iraqi Air Defense – Introduction’.

[39] Confidential interview with US electronic intelligence expert.

[40] Ibid.

[41] Kopp, ‘Operation Desert Storm: The Electronic Battle, Part-1’.

[42] Ibid.

[43] A.H. Cordesman, A.R. Wagner, The Lessons of Modern War Volume-II: The Iran-Iraq War, (London: Mansell, 1990).

[44] Conduct of the Persian Gulf War, p. 9.

Bringing It All Back Home: How one sortie by the No. 1474 Flight RAF in December 1942 helped save the lives of countless aircrew

Bringing It All Back Home: How one sortie by the No. 1474 Flight RAF in December 1942 helped save the lives of countless aircrew

By Dr Thomas Withington

The weather was mild for early December as scattered showers, and high winds continued to visit RAF Gransden Lodge near Cambridge.[1] It was a shade after 02:00 on the morning of 2 December 1942 when Flight Sergeant Edwin Paulton (Royal Canadian Air Force/RCAF) gently rotated the yoke causing the Vickers Wellington Mk1C of the Royal Air Force’s (RAF) No. 1474 (Special Duties) Flight to unstick from the runway and climb into the East Anglian night.[2] Paulton’s sortie that autumnal evening was part of the RAF’s response to the growing intensity of the Luftwaffe’s defensive effort against Bomber Command’s attacks on targets in Germany.

Emil-Emil

With most of Western Europe’s occupation now complete, and the invasion of the UK postponed indefinitely by Adolf Hitler in September 1940 following the Battle of Britain, the German high command turned its attention towards bolstering the country’s defences against RAF Bomber Command.[3] Even with the commencement of the Axis invasion of the Soviet Union on 22 June 1941, which involved a significant effort by the Luftwaffe, this did not deprive Germany of fighter defences to resist the Command’s efforts.[4] These fighters were able to exact heavy losses and between July 1942 when the RAF commenced recording aircraft loss and damage to separate causes, and December 1942 Bomber Command lost 305 aircraft to fighters during the day and night operations; 2.3 per cent of all sorties despatched.[5]

C 5477
A low-level aerial reconnaissance photograph of the ‘Freya’ radar installations at Auderville, taken using an F.24 side-facing oblique aerial camera. (Source: © IWM (C 5477))

It was imperative for Bomber Command to staunch the bleeding. By late August 1942 Bomber Command understood the workings of the Luftwaffe’s integrated air defence system. The initial detection of incoming bombers was performed by a chain of FuMG-80 Freya ground-based air surveillance radars. A defensive ‘belt’ known as the Kammhuber Line, named after Generalleutnant Josef Kammhuber, the head of the Luftwaffe’s XII Fliegerkorps, stretched from Kiel in northern Germany southwest past Luxembourg. Behind this line lay all of Germany’s major cities and industrial centres including Cologne, Düsseldorf, Frankfurt, Hamburg, Hanover, and Stuttgart. Quite simply it was almost impossible for bombers to approach their targets without crossing this line. The line was subdivided into separate ‘boxes’ each covering 247 square miles (640 square kilometres). Within each box were two FuMG-62D Würzburg ground-controlled interception radars. One of these radars would hold the fighter in its gaze while another would search the box for a bomber. A ground controller would coordinate the interception seeing the position of the fighter and bomber on his radar screens. He would then bring these two together. Once the fighter was just short of one nautical mile/nm (1.8 kilometres/km) from the bomber, the ground controller would hand over the interception to the fighter. The crew would activate their Lichtenstein-BC airborne interception radar to locate the bomber and then press home their attack. All the while the fighter and the ground controller would remain in radio contact.[6]

The British Air Ministry issued a report in July 1942 which stated that Signals Intelligence (SIGINT) had revealed that from early 1942 the Luftwaffe’s night fighters had been using a device codenamed ‘Emil-Emil’. Little was known about this beyond the fact that it seemed to assist interceptions and may have used either radar or infrared technology to do so. Initially, this equipment appeared to be used exclusively by night fighters near Vlissingen on the Netherlands’ west coast. Further investigations revealed that by October 1942 Emil-Emil appeared to be in widespread service elsewhere in the night fighter force. Such was the discipline of Luftwaffe fighter crews and their ground controllers that the purpose of Emil-Emil was not betrayed in radio chatter.[7]

Experts from the Telecommunications Research Establishment (TRE), tasked with developing and producing electronic countermeasures for the British armed forces, collected radio signals on the East Coast which revealed transmissions on a 491 megahertz/MHz frequency strongly suspected of being transmitted by Emil-Emil.[8] This information was a breakthrough, but the relationship of these transmissions to Emil-Emil had to be confirmed. The only way to do so would be to fly one of the RAF’s SIGINT gathering aircraft from No. 1474 Flight into hostile airspace where there was a high chance that enemy fighters would be encountered. The rationale was to use the aircraft for two interrelated tasks. First, entice a night fighter into an attack and then record the characteristics of any hostile radio signals it transmitted. By doing this, it would be possible to determine whether Emil-Emil was an airborne interception radar. As always in electronic warfare, once it was discerned that the enemy was using a particular type of radar in a particular way, it would be possible to devise means to jam it.

Paulton and his crew were tasked with collecting SIGINT across an area stretching from the French north coast to Frankfurt in central Germany.[9] The specifics of the mission called for the Wellington, which was equipped with a radio receiver, to lure a fighter into an interception. The aircraft would then record the radio signals transmitted by the fighter. So far No. 1474 Flight had performed 17 sorties, but none resulted in the desired interception. Finally, on the night of 2 December, the Luftwaffe would cooperate, although this would almost cost the Wellington’s crew their lives.

Against All Odds

At 04:31, two-and-a-half hours into the flight, the aircraft was northeast of the Luftwaffe airfield at Pferdsfeld in southeast Germany. Paulton set a course to fly north. As he turned Pilot Officer Harold Jordan, the aircraft’s ‘Special Operator’ tasked with the SIGINT collection, began receiving signals which seemed to match those the crew were tasked to investigate. As the Wellington flew north, the signals became stronger. Jordan warned the crew that a fighter attack was likely. As Jordan received signals, he was passing this information to wireless operator Flight Sergeant Bill Bigoray (RCAF) who coded and transmitted them back to the UK. Ten minutes later the aircraft turned west to head for home while the signals received by Jordan were getting stronger still. At that moment cannon fire from a Junkers Ju-88 fighter slammed into the Wellington. Paulton immediately put the aircraft into a violent corkscrew turn in a bid to shake off the fighter. Jordan was hit in the arm but realised that the signals he was receiving were correct with Bigoray relaying this information back to base. Despite Jordan’s injuries he continued to record the transmissions while Bigoray continued to send coded messages, having received no ‘R’ transmission from base to indicate their reception. Unbeknownst to Bigoray, they had been received at 05.05. Flight Sergeant Everitt Vachon (RCAF), the Wellington’s rear gunner, managed to fire almost 1000 rounds at the Ju-88 but his turret was hit and rendered unserviceable, with Vachon wounded in the shoulder.[10]

The Ju-88 manoeuvred for another attack. This hit Jordan in the jaw but did not stop him operating his equipment and telling Paulton from which side the next attack would occur. Along with Jordan Flight Sergeant Grant, the front turret gunner was hit, as was Bigoray who was injured in both legs as he tried to free Grant from the turret. Grant was eventually being extricated by the navigator Pilot Officer Alexander Barry (RCAF). The third attack hit Jordan again, this time in the eye. Try as he might, he could no longer operate his radio receiver. Instead, he struggled forward to find Barry to show him how to operate the receiver so that the signals collection could continue. Nonetheless, now almost blinded this proved an impossible task.[11]

While Jordan had been trying in vain to instruct Barry Vachon had managed to free himself from the rear turret. He went into the aircraft’s Astrodome to provide a running commentary on the Ju-88’s position. Vachon was hit once again, this time in the hand, and Barry took over. Throughout the engagement, those in the aircraft had been thrown around like ragdolls as Paulton’s evasive actions saw the aircraft descend from 14,000ft to a mere 500ft. The Wellington suffered twelve attacks in total; six of which may have been successful. The damage to the aircraft was extensive: The port and starboard engine throttles were jammed. The front and rear turrets were unserviceable along with the starboard ailerons and trim tabs. The starboard fuel tank was holed and the hydraulics useless, causing both engines to run erratically. The aircraft’s pitot heads were also damaged preventing the airspeed indicator showing the plane’s velocity.[12]

Despite the Wellington’s near-mortal damage Paulton managed to reach 5,000ft altitude and crossed the coast ten miles northeast of Dunkirk at 06:45. Being mistaken for a hostile aircraft was an ever-present danger when RAF planes were returning from operations over the continent. Bigoray switched the aircraft’s IFF (Identification Friend or Foe) Mk.3 transmitter to squawk that the plane was friendly and sent out a mayday message. Deciding to ditch in daylight after realising that the Wellington’s landing light was insufficient to perform a safe water landing, Paulton asked the crew if anyone wanted to bail out. Bigoray asked to do so concerned that his leg would stiffen up so much that he would be unable to leave the aircraft once it was in the water. As he was about to jump, he realised he had not secured the transmission key of his radio to prevent it accidentally retransmitting. Moving back into the fuselage and in much pain, he secured the key and jumped landing near Ramsgate on the Kent coast. Paulton finally ditched the Wellington in the channel near Walmer beach, south of Deal. Even the aircraft’s dingy, packed for such eventualities, was a casualty and despite a valiant attempt by Jordan to plug some of the holes, it was unusable. Instead, the crew climbed on top of the Wellington, being rescued by a small boat some moments later.[13]

Results

The intelligence Paulton and his crew gathered on that fateful December night had implications for the rest of the war. Their actions enabled the TRE ‘boffins’ to not only confirm that the Emil-Emil device was the Lichtenstein-BC radar but also to divine the radar’s characteristics. Once these were known it was possible to develop an Electronic Countermeasure (ECM) in the form of the Ground Grocer jammer. This was installed at Dunwich on the Suffolk coast commencing operations on 26 April 1943.[14] The jammer would blast electronic noise at the Lichtenstein-BC across a waveband of 486MHz to 501MHz. Even for Luftwaffe fighters flying 120nm (222 kilometres) distant from the transmitter could have their radar ranges reduced to 1500ft (457 metres) from their usual range of four nautical miles (eight kilometres). This forced the fighter to come closer to the bomber to detect it in darkness; greatly increasing the chances of the bomber crew hitting the fighter as it commenced its attack.[15] Nonetheless, Ground Grocer was not bereft of imperfections: It tended to work best when a fighter was flying towards the transmitter and was generally used to protect bombers on their outward and return journeys. The official record notes that by the end of June 1943 Ground Grocer had caused six of the seven cases of radar interference reported by Luftwaffe fighter crews to their ground controllers.[16]

C 5635
A Royal Air Force Avro Lancaster bomber over Essen dropping WINDOW to interfere with ground gunners during a 1000 bomber raid on the city. (Source: © IWM (C 5635))

Ground Grocer was not the only ECM developed because of the intelligence obtained by the Wellington. By gathering details on the Lichtenstein-BC’s characteristics, the TRE was able to develop several versions of Window, arguably the most famous countermeasure of the Second World War, capable of jamming this radar. Window consisted of millions of metal foil strips cut to precisely half the wavelength of the radar they were intended to jam. The TRE also developed a system known as Serrate based on the same intelligence. This was one of the RAF’s most successful electronic systems of the war. Serrate was installed on De Havilland Mosquito fighters, entering service in September 1943. It detected transmissions from the Lichtenstein-BC allowing Serrate-equipped aircraft to find and attack fighters using the radar. Serrate was employed extensively over enemy territory contributing to the 242 Luftwaffe fighters that the Mosquitoes of Bomber Command’s No. 100 Group shot down following its introduction.[17] Moreover Ground Grocer, Window and Serrate may have hastened the withdrawal of the Lichtenstein-BC which was all but phased out of service by April 1944 in favour of new radars with improved resistance to such countermeasures.[18]

The Legacy

The endeavours of Paulton and his crew were relayed to the Chief of the Air Staff, Air Chief Marshal Sir Charles Portal who told them: ‘I have just read report of your investigation flight […] and should like to congratulate you all on a splendid performance.’[19] Their deeds were recognised with the award of a Distinguished Flying Cross for Barry and Paulton, Distinguished Service Order for Jordan and Distinguished Flying Medals for Bigoray and Vachon. It is miraculous that the Wellington returned to the UK yet the actions of Paulton and his crew helped pave the way for the development of ECMs which undoubtedly saved Bomber Command lives. Their legacy can still be seen today. Radar jammers are now standard equipment on most military aircraft venturing in harm’s way, illustrating how one sortie on a cold December night would have implications for airpower which are still felt today.

Dr Thomas Withington specialises in contemporary and historical electronic warfare, radar, and military communications, and has written numerous articles on these subjects for a range of general and specialist publications. He holds a PhD from the University of Birmingham.

Header Image: A Vickers Wellington Mark IC (R1448) of No. 218 Squadron RAF on the ground at RAF Marham, Norfolk. R1448 was presented to the RAF by the Gold Coast Fund. This was the mark of Wellington flown by No. 1474 Flight during the operation described in this article. (Source: © IWM (CH 3477))

If you would like to contribute to From Balloons to Drones, then visit our submissions page here to find out how.

[1] Monthly Weather Report of the Meteorological Office, December 1942.

[2] The National Archives (TNA), AIR 50/503, No. 1474 Flight, December 1942.

[3] TNA, AIR 20/8962, War in the Ether: Europe 1939 to 1945: Radio Countermeasures in Bomber Command: An Historical Note (High Wycombe: Signals Branch, Headquarters Bomber Command, October 1945), p. 6.

[4] Ibid.

[5] Charles Webster and Noble Frankland, The Strategic Air Offensive Against Germany 1939-1945: Volume IV, Annexes and Appendices (Uckfield: Naval and Military Press, 2006), pp. 429-39.

[6] TNA, AIR 20/8962, War in the Ether, p. 9.

[7] Air Historical Branch, The Second World War 1939-1945 – Royal Air Force Signals, Volume VII: Radio Countermeasures (London: Air Ministry, 1950), p. 151.

[8] Ibid.

[9] TNA, AIR 27/1156, No.1474 Flight Operations Record Book.

[10] Ibid.

[11] Ibid.

[12] Ibid.

[13] Ibid.

[14] Air Historical Branch, The Second World War 1939-1945, p. 153.

[15] TNA, AIR 20/8070, Glossary of Code Names and Other Terms Used in Connection with RCM; AIR 20/8070, Ground Grocer.

[16] Air Historical Branch, The Second World War 1939-1945, p. 154.

[17] M.W. Bowman and T. Cushing, Confounding the Reich: The RAF’s Secret War of Electronic Countermeasures in World War Two (Barnsley: Pen and Sword, 2004), pp. 235-42.

[18] Air Historical Branch, The Second World War 1939-1945, p.154.

[19] TNA, AIR 27/1156, No. 1474 Flight ORB.

Arrows from the Ground – Or how an incident on 17 March 2017 may change the relationship between ground and air forces

Arrows from the Ground – Or how an incident on 17 March 2017 may change the relationship between ground and air forces

By Dr Jacob Stoil and Lieutenant Colonel Kyle C. Burley

On 17 March 2017, Israel launched the Arrow missile interceptor for the first time, and a new dimension was added to the relationship between the air and ground forces. This was the first operational employment of the Arrow system but that it is not the wholly new aspect of this incident. What was special was the type of target the Arrow engaged. The Arrow was designed to intercept incoming ballistic missiles at high altitudes. In this case, the missiles it intercepted were SA-5 Surface-to-Air missiles (SAMs) targeted at Israeli strike aircraft. This event, whether a one-off or part of a new doctrine, shows a way forward for the integration of ground and air forces in which the ground forces can help provide a reciprocal umbrella to their colleagues in the air.

040729-N-8229-001
Arrow 2 launch on 29 July 2004, at the Naval Air Station Point Mugu Missile Test Center. (Source: Wikimedia)

Attempting to disable and destroy SAMs is not new.  It is a critical mission for which air forces around the world train and which they regularly undertake. The coordination of ground and air systems in the most general sense is by no means a new phenomenon. As early as the Second World War, the German military integrated their ground-based flak defences with their fighter aircraft to create integrated zones of operations through designating flak boxes. At times, such as during the 1973 War, ground forces have been used to punch a hole through SAM umbrellas to allow the air force to conduct strike operations.

In all of these cases, the fundamental relationship between air and ground forces has remained consistent. The air forces have the ability to intervene in the ground domain and provide an umbrella for the ground forces, supporting them and protecting them from threats. So what changed on 17 March? Ground forces demonstrated their ability to enter the aerial domain and provide an umbrella covering the air force and protecting them from harm.

The Israeli use of ground-based missiles to provide screening fires for manned strike aircraft has opened a window for the exploration of new concepts.  The soon to be released US Army ‘FM 3-0 Operations’ manual anticipates the future possibilities of land forces as enablers for air and maritime forces. This is a break from the previous doctrine, which only envisioned that air and sea forces would act as enablers for land combat.  Extrapolating from the Israeli case provides a vision of the possibility of US Army forces using ground-based air-defense missile systems such as Patriot and Terminal High Altitude Air Defense (THAAD) for a SAM interdiction capability.  Forward deployed batteries could provide this covering fire along ingress and egress routes of strike aircraft where the Threat Integrated Air Defense Systems (IADS) is still capable or of an unknown status.  Sea-based forces such as Guided Missile Cruisers might also provide this type of coverage.

It is possible to push this vision further in considering the possibilities of ground or sea-launched Unmanned Aerial Systems (UAS). Envision a weapon that has to loiter and hypersonic propulsion which could target ground based IADS launchers, radar, and SAMs in-flight.  Such systems would no longer be dependent upon ground basing within direct fire range and the flight time of a Patriot or THAAD type battery. They could loiter, or even swarm to cover friendly air-breathing and manned mission aircraft in a contested area.

patriot_missile_launch_b
MIM-104 Patriot surface-to-air missile system. (Source: Wikimedia)

Each year, the US Army School of Advanced Military Studies (SAMS) conducts a planning exercise using a Joint Forcible Entry scenario.  In such a scenario, students must plan for the entry of US forces into a hostile environment against armed opposition. Students learn about the need to destroy hostile IADS capability before risking a single airlifter either to conduct an airborne assault or establish an Aerial Port of Debarkation (APOD).  Operations to remove the IAD threat can be time-consuming. Since the action on 17 March, it is now possible to imagine a US force conducting a Joint Forcible Entry within hours of deployment alert because the US no longer has to conduct a prolonged “IADS takedown” phase within the air campaign. A covering force of counter-IADS UASs could protect the strike and air assault forces through an array of tactics such as escort, prepositioning swarm, or forward sense and attack.  Using such a capability could radically redefine the approach to forcible entry and enhance the ability of airborne inserted ground forces as a US flexible deterrent option.

Whatever the future holds, the 17 March incident demonstrated the ability of missile defence technology to provide cover for aircraft engaged in strike operations. No more does dealing with SAMs need to be solely the role of the air force: ground forces can provide cover.  In doing so, this sets up a new dynamic of reciprocity in which air forces provide cover to ground forces, which in turn protect air forces. As missile defence technology such as that employed by Israel proliferates, this has the potential to revolutionise the way SAM threats are negated and alter the relationship between air and ground forces and give new meaning to ‘joint operations’.

Kyle C. Burley is a US Army Lieutenant Colonel and the Deputy Exercise Director for the US Army School of Advanced Military Studies (SAMS) at Fort Leavenworth, Kansas.  As the SAMS Simulations Officer he prepares, resources, and provides control for SAMS’ robust military planning exercise program.  Before assignment at SAMS, LTC Burley served as the US Third Army’s G7 (Forward) & Joint Readiness Exercise Team Chief.  He has also served in an array of Armor, Cavalry, as well headquarters staff positions from Division to OSD levels during his 24 years of service.  Kyle is a lifelong student of military history and a “Master” High Power rifle competitor.

Dr Jacob Stoil is a military historian and currently Assistant Professor of Military History at the US Army School of Advanced Military Studies. He received his doctorate in history from University of Oxford. He holds a BA in War Studies, as well as an MA in History of Warfare from the Department of War Studies, at King’s College London. He has published on indigenous force cooperation, the Second World War, and the Israeli military. Dr Stoil is the co-director of The Second World War Research Group (North America). He can be reached on Twitter at @JacobStoil.

The opinions and conclusions expressed herein are those of the authors and do not necessarily represent the views of the U.S. Army Command and General Staff College or any other government agency. (References to this study should include the foregoing statement.)

Header Image: A Terminal High Altitude Area Defense interceptor being fired during an exercise in 2013 (Source: Wikimedia)