McDonnell Douglas F/A-18 Hornet in Australian service

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
McDonnell Douglas F/A-18 Hornet in Australian service
Photo of three modern fighter aircraft flying in formation over a desert
Three RAAF F/A-18A Hornets during 2012
Role Multirole fighter
Manufacturer Most assembled by Government Aircraft Factories
Primary user Royal Australian Air Force
Produced 1984–1990
Number built 57 F/A-18A, 18 F/A-18B
Career
Serial A21-1 to A21-57 (F/A-18A)
A21-101 to A21-118 (F/A-18B)
In service 1984–current

The Royal Australian Air Force (RAAF) has operated McDonnell Douglas F/A-18 Hornet fighter aircraft since 1984. The Australian Government purchased 75 "A" and "B" variants of the F/A-18 in 1981 to replace the RAAF's Dassault Mirage III fighters. The Hornets entered service with the RAAF between 1984 and 1990, and 71 remain in operation as of 2012. The other four Hornets were destroyed in flying accidents during the late 1980s and early 1990s.

RAAF Hornets were first sent on a combat deployment as part of the Australian contribution to the 2003 invasion of Iraq. During the invasion, 14 Hornets flew patrols over Iraq, as well as close air support sorties to assist coalition ground forces. RAAF F/A-18s also provided security for the American air base at Diego Garcia between late 2001 and early 2002, and have protected a number of high-profile events in Australia. From 2015 they have been striking ISIL targets as part of Operation Okra.

Since 1999 the RAAF has put its Hornets through a series of upgrades to improve their effectiveness. However, the aircraft are becoming increasingly difficult to operate and are at risk of being outclassed by the fighters and air-defence systems operated by other countries. As a result, the RAAF will begin to retire its F/A-18s in the late 2010s, and the last aircraft will leave service in the early 2020s. Under current Australian Government planning they will be replaced by up to 72 Lockheed Martin F-35 Lightning II fighters.

Selection

The RAAF began the initial stages of scoping a replacement for its Dassault Mirage III fighters in 1968.[1] The service issued an Air Staff Requirement for new fighter aircraft in December 1971, which received a larger than expected number of proposals from manufacturers. At this time the RAAF expected to start phasing out the Mirage IIIs in 1980.[2] In 1973, a team of RAAF personnel inspected the McDonnell Douglas F-15 Eagle, Northrop YF-17, Saab 37 Viggen and Dassault Mirage F1 programs, but recommended that any decisions about a suitable replacement be delayed so that several new fighters that were expected to soon become available could also be considered.[1][3] In August 1974 the Australian Government decided to defer the fighter replacement project and extend the Mirage IIIs' operational life into the 1980s. One of the four Mirage III-equipped squadrons was also disbanded at this time.[3]

Photo of a modern fighter aircraft parked on tarmac
USAF F-16A in 1980

Work on the Mirage replacement program resumed in 1975, and the Tactical Fighter Project Office was established in 1976 to manage the process of selecting the RAAF's next fighter.[1][3] A request for proposals was issued in November that year and attracted eleven responses. By March 1977 the office had chosen to focus on the F-15 Eagle, General Dynamics F-16 Fighting Falcon, Dassault Mirage 2000 and Panavia Tornado, as well as the McDonnell Douglas F-18A and F-18L; the F-18A was a carrier-based fighter developed from the YF-17 for the United States Navy, and the F-18L was a land-based variant of this design. The Grumman F-14 Tomcat was also considered by the project office, but was regarded as unsuitable and never placed on the official shortlist.[1] In November 1978 the F-15 and Tornado were removed from the list of aircraft being considered. The Tornado was excluded as it was principally a strike aircraft and had limited air-to-air capability. While the F-15 was an impressive aircraft that met or exceeded almost all of the RAAF's requirements, it was believed that the air force did not need a fighter with such advanced capabilities and that introducing it into service could destabilise Australia's region.[4]

Further evaluation of the remaining aircraft took place during 1979. Wing Commander (and later Air Vice-Marshal) Bob Richardson test-flew a Mirage 2000 in April 1979, and reported that while the aircraft had excellent aerodynamic characteristics, its avionics, radar, fuel system, cockpit and weapons capability were inferior to those of US designs.[5] Richardson also test-flew a YF-17 that was being used as a demonstrator for the F-18L in mid-1979, and was impressed by its capabilities. No F-18Ls had been ordered at this time, however, and the RAAF did not want to take on the risk of being the lead customer for the design.[6] At about the same time, the RAAF rejected an offer of F-14 Tomcats that had been originally ordered by the Iranian Government but not delivered as a result of the revolution in that country. While the Tomcats were made available at a greatly reduced price, the air force judged that these aircraft were too large and complex for its requirements.[6]

File:F-18A Hornet VMFA-531 Cairo 1985.jpeg
US Marine Corps F/A-18A in 1985

With the Mirage 2000 and F-18L rejected, the RAAF was faced with a choice between the F-16 and F-18A. Richardson and several other RAAF pilots tested United States Air Force (USAF) F-16Bs in 1979 and 1980, and reported that the aircraft had excellent performance but could be difficult to control at times. The evaluation team was also concerned about the reliability of the F-16's engine and regarded the aircraft as technologically immature. It was also noted that the aircraft's radar was inferior to that of the F-18A, and that F-16s could not fire the beyond-visual-range (BVR) air-to-air missiles and long-range anti-shipping missiles that the F-18A was capable of operating.[7] In contrast, the evaluation team was impressed by the F-18A, and regarded it as being a more robust and survivable aircraft as it had been designed to operate from aircraft carriers; these features were important for operations from bare bases in northern Australia.[8] Richardson and three other RAAF pilots test-flew F-18As, and reported that the aircraft handled well, but had some deficiencies with its flight control system and engines; these were not seen as major flaws by the evaluation team, however.[9] The F-18A's twin engines were considered to be its main advantage over the single-engined F-16, as research conducted by the evaluation team found that the attrition rate for single-engined fighters was twice that for aircraft with two engines.[10] Overall, however, the RAAF judged that both the F-16 and F-18A were too immature for a decision to be made in 1980 as had been originally planned, and recommended to the Government that this be deferred by a year.[10]

The Government accepted the RAAF's recommendation, and delayed its decision on a Mirage III replacement until late 1981. This gave General Dynamics an opportunity to offer the improved F-16C to the RAAF. The capability of these aircraft was closer to that of the F-18 as they were equipped with BVR missiles. Richardson and another RAAF pilot test-flew F-16Cs in May 1981.[10] The F-18 design was also improved during 1981, and was redesignated the F/A-18. When RAAF test pilots flew these aircraft during 1981, they found that the deficiencies they had detected in 1980 were now addressed.[11] Overall, the RAAF concluded that while both aircraft met its requirements and the F-16 was less expensive, the F/A-18 was the superior design as it was more technologically mature, easier to maintain during operational deployments, and likely to have a much lower attrition rate.[12] The Government accepted this advice, and announced on 20 October 1981 that 75 F/A-18s would be ordered. As part of this announcement, Minister for Defence Jim Killen acknowledged that the F-16 would have been seven percent cheaper to purchase, but stated that the F/A-18's lower running costs and expected attrition rate greatly reduced the difference between the lifetime cost of the two designs.[13]

Instead of directly ordering the aircraft from McDonnell Douglas, the Australian Government purchased its F/A-18s through the US Government's Foreign Military Sales (FMS) program.[14] Ordering the aircraft via the US Government allowed the RAAF to take advantage of the superior purchasing power of the US military, and reduced the service's project management requirements.[15] This led to a complicated arrangement whereby the aircraft were ordered by the US Government, delivered to the US Navy, and then transferred to the RAAF once initial flight testing had taken place.[14] The process functioned smoothly, however, and was cost effective.[16]

Production

File:2OCU 1985.jpg
One of the RAAF's first F/A-18Bs in October 1985

The RAAF's order of 75 Hornets comprised 57 single-seat "A" variant fighters and 18 two-seat "B" variant operational training aircraft.[17] It was planned that each of the three fighter squadrons and the single operational conversion unit that were to operate the F/A-18 would be allocated 16 aircraft, of which 12 were expected to be operational at any time while the other four were undergoing maintenance. The remaining eleven Hornets were labelled the "half-life attrition buy" and would replace the aircraft that were expected to have been lost by 2000; as it happened, this greatly exceeded the RAAF's actual losses.[18] Deliveries were planned to start in late 1984 and be completed in 1990.[18] The total cost of the F/A-18 program, including the aircraft, spare parts, other equipment and modifications to the RAAF's fighter bases, was calculated as A$2.427 billion in August 1981, but was rapidly revised upwards due to the depreciation of the Australian dollar at this time.[17][19]

The Australian Hornets were very similar to the standard US Navy variants, but incorporated a number of minor modifications. These included the addition of an Instrument Landing System/Very High Frequency Omnidirectional Range (ILS/VOR) system, a high-frequency radio, a different ejection seat harness and the deletion of all equipment used only to launch the aircraft from catapults.[18] In addition, two of the Australian aircraft were fitted with flight-test instrumentation so that they could be used as part of trials.[20]

F/A-18A and B variant deliveries[21]
Year F/A-18A F/A-18B Total
1985 1 7 8
1986 12 0 12
1987 7 7 14
1988 21 4 25
1989 12 0 12
1990 4 0 4
Total 57 18 75

The Government sought to use the Mirage III replacement program as a means to increase the capabilities of Australia's manufacturing industry. Accordingly, it was decided to build the aircraft in Australia, though it was recognised that this would lead to higher costs than if the fighters were purchased directly from the United States.[19] While the first two RAAF Hornets were built in the United States, the remainder were assembled at the Government Aircraft Factories plant at Avalon Airport in Victoria, and their engines were produced by the Commonwealth Aircraft Corporation at Fishermans Bend in Melbourne. Another twelve Australian companies were involved in other stages of the project.[22] These firms were sub-contracted to McDonnell Douglas and the other major US companies that produced components for the F/A-18, and had to comply with the requirements of the FMS program.[15] The Australian Government hoped that Singapore and New Zealand would purchase Australian-built Hornets, but this did not eventuate. The Canadian Government expressed interest in purchasing 25 Australian-built F/A-18As in 1988 in order to increase its force of these aircraft after they had ceased to be manufactured in the United States, but this did not lead to any sales.[23]

File:RAAF FA-18A landing at 2011 Avalon Air Show.jpg
An F/A-18A (A21-49) landing in 2011

The Australian Hornets began to roll off the production lines in 1984. The first two aircraft (serial numbers A21-101 and A21-102) were entirely built at McDonnell Douglas' factory in St. Louis, and were handed over to the RAAF on 29 October 1984. These aircraft remained in the United States until May 1985 for training and trials purposes.[24][25] The next two Australian Hornets (A21-103 and A21-104) were also built at St. Louis, but were then disassembled and flown to Avalon in June 1984 on board a USAF Lockheed C-5 Galaxy. The aircraft were then reassembled, and A21-103 was rolled out at a ceremony attended by Prime Minister Bob Hawke and the Chief of the Air Staff, Air Marshal David Evans, on 16 November. However, the aircraft's initial test flight was delayed until 26 February 1985 by a demarcation dispute over which category of pilot was permitted to fly the aircraft.[26]

In order to meet production targets, GAF was required to complete 1.5 Hornets per month. Production fell behind schedule during the first half of 1987, however, as a result of inefficiencies at the company's factory and industrial relations problems. GAF was able to accelerate production later in the year, though some components that were planned to be manufactured in Australia were purchased from companies in the United States instead.[21] The final cost of the Hornet project was A$4.668 billion; after adjusting for the depreciation of the Australian dollar this was $186 million less than the initial estimate.[19]

The RAAF began to accept Hornets into service in 1985. A21-103 was formally delivered on 4 May of that year.[26] Two weeks later, A21-101 and 102 were flown from Naval Air Station Lemoore in California to RAAF Base Williamtown in New South Wales between 16 and 17 May 1985. This ferry flight was conducted as a non-stop journey, and USAF McDonnell Douglas KC-10 Extender tankers refuelled each of the Hornets 15 times as they crossed the Pacific. As of 2005 this remained the longest single flight to have been undertaken by F/A-18s.[27] Despite the delays to production in 1987, the final Australian Hornet (A21-57) was delivered on schedule at a ceremony held in Canberra on 16 May 1990.[18][21] The F/A-18As were allocated serial numbers A21-1 through to A21-57 and the F/A-18Bs were allocated A21-101 to A21-118.[21]

A major capital works program was also undertaken to prepare RAAF bases for the Hornets. Over $150 million was spent upgrading the runways, hangars and maintenance facilities at RAAF Base Williamtown, which has been the main F/A-18 base throughout the aircraft's service. The pre-existing airfield at RAAF Base Tindal in the Northern Territory was also developed into a major air base between 1985 and 1988 at a cost of $215 million so that it could accommodate No. 75 Squadron. Until this time the squadron had been stationed at RAAF Base Darwin which, due to its location on Australia's north coast, was vulnerable to damage from cyclones and difficult to defend during wartime.[28]

Owing to concerns over the airworthiness of the RAAF's General Dynamics F-111 bombers and delays to the Lockheed Martin F-35 Lightning II program, the Australian Government ordered 24 F/A-18F Super Hornets in 2006. This design is significantly different from the original (or "classic") Hornet, however. The RAAF's first Super Hornets entered service in 2010 and deliveries were completed the next year.[29][30]

Maintenance and upgrades

Maintenance of the RAAF's Hornets is carried out by both air force personnel and civilian contractors. Until the early 1990s, all routine servicing and a significant proportion of intensive "deeper maintenance" was undertaken by the air force. However, the share of intensive maintenance tasks outsourced to the private sector was increased during the 1990s under the RAAF-wide Commercial Support Program.[31] Under current arrangements, the four Hornet-equipped units undertake all routine servicing and some of the more complex deeper maintenance tasks. The remainder of the deeper maintenance work, as well as all major refurbishments and upgrade projects, are carried out by commercial firms.[32] BAE Systems has been the lead contractor for Hornet deeper maintenance since 2003, and Boeing Australia has also provided maintenance services for the aircraft since it won a contract to do so in 2010.[33][34]

The RAAF's Hornet fleet received few modifications until the late 1990s. During this period, the AN/AAS-38 "Nite Hawk" targeting pod was the only new system fitted to the aircraft.[35] However, several Asian countries introduced Mikoyan MiG-29 fighters into service during the 1990s, raising concerns that the RAAF's aircraft would be outclassed. The air force considered replacing the Hornet with the Eurofighter Typhoon or Boeing F/A-18E/F Super Hornet, but concluded that both aircraft were technologically immature.[35] As a result, it was decided to upgrade the Hornets.[35]

File:RAAF Hornet DRW Butler-1.jpg
Hornet A21-3 in August 2010. The aircraft is carrying a LITENING targeting pod and ASRAAM missiles as well as training bombs and external fuel tanks.

The Hornet Upgrade Program (HUG) began in 1999, and has had three main phases.[35] In Phase 1, which ran from mid-2000 through 2002, the Hornets' computer systems, navigation system and radio were replaced. The aircraft were also fitted to operate the ASRAAM air-to-air missile; these weapons replaced the AIM-9 Sidewinder.[36] HUG Phase 2 comprised four sub-elements and sought to improve the Hornets' combat performance.[35] During Phase 2.1 the APG-65 radar was replaced with the improved AN/APG-73, and the aircraft were fitted with a secure voice encryption communications system as well as various updates to their computer systems.[36] In HUG Phase 2.2, the most important element of the program, the Hornets were fitted with a Joint Helmet Mounted Cueing System, equipment needed to share data through the Link 16 network, a new countermeasures dispensing system and several upgrades to their cockpit displays. All of the Hornets were upgraded to this standard between January 2005 and December 2006.[37] In Phase 2.3, an improved Electronic Counter Measures system was fitted to the Hornets; the AN/ALR-2002 was originally selected, but proved unsuccessful. It was replaced by the ALR-67 Radar Warning Receiver in late 2006. As of early 2012, 14 Hornets had been fitted with the system and the remainder were scheduled to receive it by the end of the year.[38][39] During HUG Phase 2.4 the Hornets were modified to be able to use the AN/AAQ-28(v) "LITENING" targeting pod and 37 of these systems were purchased; this phase was completed in 2007.[38]

The third stage of the Hornet Upgrade Program sought to rectify airframe damage.[35] HUG Phase 3.1 involved minor structural work to all aircraft as they passed through other phases of the program. The centre fuselages of the ten Hornets assessed as suffering the greatest amount of structural damage were replaced in HUG Phase 3.2. It was originally intended that all the RAAF's Hornets would receive new centre fuselages, but the scope of this phase of the program was reduced after it was found that the number of man-hours needed to upgrade each aircraft was much greater than originally estimated. The ten aircraft were upgraded at an L-3 Communications facility in Canada, and all were returned to service by June 2010.[38]

The long-running HUG process has complicated the RAAF's management of its fleet of F/A-18s. At any one time, the capabilities of individual aircraft have differed considerably depending on their upgrades. Accordingly, the long-standing arrangement where aircraft were almost permanently assigned to each squadron was replaced by a system where they are pooled. Attempts to allocate Hornets with similar levels of modifications from the common pool to each squadron have not been successful.[40]

Armament

Colour photo of a flying fighter aircraft firing a missile
An RAAF F/A-18 Hornet firing an AIM-7M Sparrow missile in 1990 while also carrying two Harpoon missiles, two Sidewinder missiles and another Sparrow

The RAAF's Hornets have been fitted with several different types of air-to-air weapons. The aircraft are equipped with an internal M61A1 cannon for use against air and ground targets; 578 rounds can be carried for this weapon.[41] During the initial years of the Hornet's service, the aircraft were equipped with AIM-9M Sidewinder short range air-to-air missiles and AIM-7M Sparrow medium-range air-to-air missiles. The Sparrows were replaced by the AIM-120 AMRAAM in 2002, and in 2004 the Sidewinders were replaced by ASRAAMs.[42] The older missiles are occasionally used in training exercises, however.[43]

The AGM-65 Maverick air-to-ground tactical missile (AGM) can be used for close air support.[44] A variety of unguided and guided weapons can also be used against ground targets. The Hornets carry Mark 82, Mark 83 and Mark 84 bombs, as well as GBU-10, GBU-12 and GBU-16 Paveway II laser-guided bombs.[45] In addition, the aircraft have operated bombs fitted with JDAM guidance kits since 2008.[46] The long-ranged JDAM-ER variant of these bombs were ordered in 2011 and will begin to enter service in 2015.[47] During exercises the Hornets carry BDU-33 and BDU-57 LGTR training bombs.[48] Since November 2011, the RAAF's Hornets have also been equipped with AGM-158 JASSM cruise missiles.[35][49] The F/A-18s main weapon in the maritime strike role is the Harpoon anti-ship missile; the RAAF initially operated the Block IC variant of this missile, but purchased Block II variants in 2003.[50] In addition to these weapons, the Hornets can also be fitted with 330-US-gallon (1,200 L) drop tanks to extend their range.[51]

Operational history

Introduction into service

Four RAAF units converted to the Hornet between 1985 and 1988. The first 14 Hornets were allocated to No. 2 Operational Conversion Unit (2OCU) at RAAF Base Williamtown, and were used to train the pilots and instructors needed to convert the RAAF's three fighter squadrons to the aircraft. 2OCU's first Hornet operational conversion course began on 19 August 1985.[18][52] In addition to the unit's training activities, 2OCU aircraft travelled widely around Australia and South East Asia during 1985 and 1986 to showcase the new aircraft.[53] No. 3 Squadron was the first fighter unit to convert from the Mirage III, and became operational with the Hornet in August 1986. It was followed by No. 77 Squadron in June 1987 and No. 75 Squadron in May 1988.[24] No. 81 Wing, whose headquarters is located at Williamtown, has commanded these four units since they converted to the F/A-18.[54][55] As of 2012, 2OCU, No. 3 and No. 77 Squadrons are stationed at Williamtown and No. 75 Squadron is located at Tindal.[55] In addition, two Hornets are allocated to the Aircraft Research and Development Unit at RAAF Base Edinburgh in South Australia.[56]

File:RAAF Hornet CBR Gilbert-1.jpg
An F/A-18A in special colours to mark the 20th anniversary of the Hornet's introduction into RAAF service

The RAAF's Mirage III pilots generally found the process of converting to the Hornet to be straightforward. While the F/A-18 was considered to be easier to fly, its more sophisticated avionics and weapons systems required improved cockpit workload management skills. The Hornets have also proven to be mechanically reliable and easy to maintain, though shortages of spare parts reduced availability rates during the early years of their service with the RAAF.[57] The updates installed as part of the HUG process have further simplified maintenance procedures. In recent years, however, the aging aircraft have required much more servicing than was the case in the past.[40]

To extend the Hornet's range, four of the RAAF's six Boeing 707 transport aircraft were converted to tankers in the early 1990s; the first Boeing 707 tanker entered service in 1990.[58] The tankers were operated by No. 33 Squadron and supported the Hornet units until the 707s were retired in 2008.[59][60] These aircraft were replaced with KC-30A tanker-transports in 2011.[59]

The RAAF has at times suffered from shortfalls of Hornet-qualified pilots. The service began to experience shortages of F/A-18 and F-111 fast-jet pilots in the mid-1980s due to competition from commercial airlines and relatively low recruitment rates.[61] By June 1999 the three operational Hornet-equipped squadrons had only 40 pilots, which was less than the number of aircraft allocated to these units. The RAAF claimed that the squadrons were able to meet their readiness targets, however.[62] To overcome this shortfall, the RAAF gave its fast jet units a higher priority for aircrew, implemented measures to reduce separation rates, and recruited pilots from other countries. These reforms coincided with reduced demand for civil pilots following the 11 September attacks, and by late 2003 the RAAF's fast-jet units were at near full strength.[63] A 2010 article in the magazine Australian Aviation stated that No. 3 Squadron typically had "about 18 pilots on strength" at any point in time.[64] At this time the total strength of the squadron, including air and ground crew, was around 300 personnel.[65]

Training

File:RAAF F-18 Alaska 2008.JPG
A RAAF Hornet refueling over Alaska in 2008

As the Hornets are multi-role fighters, their pilots practice a wide range of tasks during peacetime training.[66] Each year the three Hornet squadrons rotate between four-month training "blocks" focused on air-to-air combat, air-to-ground tactics and Australian Defence Force support tasks. The units undertake the air-to-air and air-to-ground "blocks" before assuming responsibility for Australian Defence Force support (which involves operating with the Australian Army and Royal Australian Navy). No. 81 Wing's headquarters oversees this training program and monitors adherence to common standards and procedures.[67] Training sorties may include such tasks as defending air bases, infrastructure and shipping from enemy aircraft, attacking naval and ground targets, and practicing in-flight refueling. More unusual tasks such as dropping naval mines have also been practiced at times. Major exercises often involve other RAAF units and aircraft, as well as units from the Army and Navy and contingents from other countries.[68][69]

As part of their regular training activities, F/A-18 Hornets operate in different parts of Australia and the Asia-Pacific region. Regular deployments are made to Singapore and RMAF Butterworth in Malaysia as part of Integrated Air Defence System exercises. In addition, RAAF F/A-18s have participated in exercises in the Philippines, Thailand and the United States.[52] These deployments have seen Australian fighter squadrons range as far afield as Eielson Air Force Base in Alaska, where they took part in Red Flag – Alaska exercises in 2008 and 2011.[70][71]

Four of the RAAF's Hornets were destroyed in flying accidents during the late 1980s and early 1990s. A21-104 was the first aircraft to be lost when it crashed at Great Palm Island in Queensland on 18 November 1987; its pilot was killed. The next loss occurred on 2 August 1990 when two No. 75 Squadron Hornets (A21-21 and A21-42) collided. A21-42 crashed, killing the unit's commanding officer; the other aircraft was damaged but managed to return to base. On 5 June 1990 A21-41 crashed 100 kilometres (62 mi) north-east of Weipa, Queensland, killing its pilot. A21-106 was the fourth aircraft to be lost when it crashed inland from Shoalwater Bay in Queensland on 19 May 1992 – its pilot and a passenger from the Defence Science and Technology Organisation died.[72][73] As of February 2012, all of the remaining 71 F/A-18s were still in service.[74]

Deployments

In late 1990 consideration was given to deploying a squadron of F/A-18s to the Middle East as part of an expanded Australian contribution to the Gulf War. The Department of Defence opposed dispatching the aircraft on the grounds that doing so would greatly strain the fighter force in Australia, and this option was not adopted by the government.[75] As a result, the Hornets' only role in the war was to support the training of the Royal Australian Navy warships which were sent to the Gulf by conducting mock attacks on the vessels as they sailed from Sydney to Perth.[76]

During late 1999, No. 75 Squadron was placed on alert to provide close air support and air defence for the international forces deployed to East Timor as part of INTERFET. While Indonesian forces posed a potential threat to this force, no fighting eventuated and the Hornets were not required.[77]

File:US Navy 030414-F-6591P-003 Aircraft of the 379th Air Expeditionary Wing and coalition counterparts stationed together in a deployed location in southwest Asia fly over the desert.jpg
An Australian Hornet (at top) flying in formation with US and British aircraft on 14 April 2003 following the invasion of Iraq

The first operational deployment of RAAF Hornets took place in 2001. Following the 11 September terrorist attacks, the Australian Government agreed to deploy F/A-18s to protect the major USAF air base on the Indian Ocean island of Diego Garcia, which was being used to mount operations in Afghanistan. Four No. 77 Squadron Hornets and 70 personnel departed for the island on 9 November. No. 3 Squadron pilots and ground crew relieved the No. 77 Squadron personnel in early February 2002. While the Hornets were occasionally scrambled in response to reports of aircraft near the base, no threat developed. The detachment returned to Australia on 21 May 2002.[78]

No. 75 Squadron formed part of the Australian contribution to the 2003 invasion of Iraq. The squadron began initial planning for this deployment in December 2002, and intensive training was undertaken from January 2003. To improve the unit's readiness, air and ground crew as well as aircraft were also posted to No. 75 Squadron from other units.[79] The Australian Government announced on 1 February that it would begin deploying RAAF aircraft, including a squadron of F/A-18s, to the Middle East. No. 75 Squadron departed from Tindal on 13 February, and arrived at Al Udeid Air Base in Qatar on the 16th of the month. The 14 F/A-18A Hornets selected for this deployment had received the HUG 2.1 package of upgrades and recently completed major servicing.[80] In addition to No. 75 Squadron, several experienced Hornet pilots were also posted to the USAF Combined Air and Space Operations Center in the Middle East to provide advice on how to make the best use of the squadron.[81]

The Australian Hornets saw combat in several roles during the Iraq War. Following the outbreak of war on 20 March, No. 75 Squadron was initially used to escort high-value Coalition aircraft, such as tankers and airborne early warning and control aircraft.[82] As it rapidly became clear that the Iraqi Air Force posed no threat, from 21 March No. 75 Squadron also began to also conduct air interdiction sorties against Iraqi forces. These sorties were initially flown in support of the United States Army's V Corps, but the squadron was rarely assigned any targets to attack. As a result, the Australian commanders in the Middle East had No. 75 Squadron reassigned to support the United States Marine Corps' I Marine Expeditionary Force. At this time the squadron also began flying close air support sorties. During the first two weeks of the war the squadron typically flew 12 sorties per day. To avoid pilot fatigue, additional aircrew were posted to the Middle East from Australia. The number of sorties dropped to between six and ten per day from 5 April onwards as the American forces closed on Baghdad and few targets remained in southern Iraq.[83] On 12 April, No. 75 Squadron supported elements of the Special Air Service Regiment and 4th Battalion, Royal Australian Regiment, which occupied Al Asad Airbase. During the last weeks of the war the squadron continued to fly sorties across western, central and southern Iraq to support British and American forces. In several of the squadron's operations in the final week of the war, the Hornets made low altitude and high speed passes over Iraqi positions to encourage their defenders to surrender. No. 75 Squadron conducted its final combat sorties on 27 April.[84] During the war the squadron flew 350 combat missions (including 670 individual sorties) and dropped 122 laser-guided bombs. No. 75 Squadron did not suffer any casualties, and all 14 Hornets returned to Tindal on 14 May 2003.[85]

File:An Australian F-18 fighter flies over Iraq on 22 December 2015.jpg
An Australian F/A-18 Hornet over Iraq in December 2015

RAAF Hornets have also provided air defence for several high-profile events in Australia since the 11 September attacks. In 2002, Hornets patrolled over the Commonwealth Heads of Government Meeting (CHOGM) at Coolum Beach, Queensland; this was the first time RAAF aircraft had flown air defence sorties over Australia since World War II.[86] On 22 and 23 October that year a detachment of Hornets patrolled over Canberra during US President George W. Bush's visit to the city.[87] A detachment of aircraft from No. 77 Squadron was deployed to RAAF Base East Sale in March 2006 to protect the Commonwealth Games, which were being held in Melbourne.[88] In September 2007, Hornets patrolled over Sydney during the APEC leaders meeting there.[89] Eight Hornets were also deployed from Williamstown to RAAF Base Pearce in October 2011 to protect the CHOGM meeting in nearby Perth.[90] On 16 and 17 November that year, Hornets operated over Canberra and Darwin while President Barack Obama was present.[91][92]

In March 2015 six F/A-18As from No. 75 Squadron were deployed to the Middle East as part of Operation Okra, replacing a detachment of Super Hornets.[93] By the end of November 2015 the Hornets had conducted 580 sorties over Iraq, during which they dropped 363 munitions. The aircraft also flew 18 sorties over Syria in September 2015, dropping two munitions.[94]

Planned replacement

While the Hornet Upgrade Program has been successful, the RAAF's Hornets are approaching retirement. It is expected that the aircraft will be increasingly expensive to operate as they age, and improvements to the fighter aircraft and air defences operated by other countries will reduce the Hornets' combat effectiveness. Under current planning, the F/A-18s will begin to be withdrawn from service in the late 2010s, with the final aircraft being retired in the early 2020s.[95] In the meantime, the RAAF has implemented several measures to keep the Hornets in service. These include a structural refurbishment program, increased monitoring of fatigue-related issues as well as repainting the aircraft and frequently washing them to reduce the risks posed by corrosion.[96] In 2015 the Defence Science and Technology Group conducted new statistical analysis of the Hornets' structural condition which found that the airframes were less fatigued than previously believed, and so able to remain in service for a longer period than planned if necessary. This finding was accepted by the Directorate General Technical Airworthiness – Australian Defence Force.[97]

The Australian Government is currently planning to replace the RAAF's F/A-18 Hornets with Lockheed Martin F-35A Lightning II fighters from 2017 onwards.[98] The Defence Materiel Organisation's Project AIR 6000 Phase 2A/B specifies that up to 72 F-35A fighters will be acquired to equip three squadrons and an operational training unit. However, only 14 aircraft had been funded as at June 2012, and the first two will be delivered in 2014. The next twelve are scheduled to be delivered between 2017 and 2019. The government will make a decision on funding the remainder of the aircraft at an unspecified future date. Up to 28 additional F-35As may also be ordered to replace the Super Hornets.[98]

As a result of delays to the F-35 program, the Australian Government is considering buying additional F/A-18F Super Hornets or further extending the life of the "classic" F/A-18s.[99] Writing in 2011, Australian Strategic Policy Institute analyst Andrew Davies recommended that, owing to the increasing difficulty and expense of keeping the aircraft operational, a program to retain the F/A-18A and B Hornets in service should only be attempted if it is expected that the F-35 will be delayed for an additional one or two years.[100]

Notes

Citations
  1. ↑ 1.0 1.1 1.2 1.3 McLaughlin (2005), p. 51
  2. ↑ Wilson (1993), p. 80
  3. ↑ 3.0 3.1 3.2 Wilson (1993), p. 81
  4. ↑ McLaughlin (2005), p. 52
  5. ↑ McLaughlin (2005), p. 53
  6. ↑ 6.0 6.1 McLaughlin (2005), p. 55
  7. ↑ McLaughlin (2005), pp. 56–57
  8. ↑ McLaughlin (2005), p. 57
  9. ↑ McLaughlin (2005), pp. 57–58
  10. ↑ 10.0 10.1 10.2 McLaughlin (2005), p. 59
  11. ↑ McLaughlin (2005), p. 60
  12. ↑ McLaughlin (2005), pp. 60–61
  13. ↑ McLaughlin (2005), pp. 61–62
  14. ↑ 14.0 14.1 Wilson (1993), p. 83
  15. ↑ 15.0 15.1 McLaughlin (2005), p. 67
  16. ↑ McLaughlin (2005), pp. 69–70
  17. ↑ 17.0 17.1 Wilson (2005), p. 35
  18. ↑ 18.0 18.1 18.2 18.3 18.4 McLaughlin (March 2005), p. 55
  19. ↑ 19.0 19.1 19.2 McLaughlin (March 2005), p. 54
  20. ↑ Wilson (1993), p. 86
  21. ↑ 21.0 21.1 21.2 21.3 Wilson (2005), p. 42
  22. ↑ McLaughlin (March 2005), pp. 54–55
  23. ↑ Wilson (1993), pp. 127–128
  24. ↑ 24.0 24.1 Wilson (2005), p. 41
  25. ↑ McLaughlin (2005), p. 70
  26. ↑ 26.0 26.1 Wilson (2005), pp. 41–42
  27. ↑ McLaughlin (2010), pp. 12–13
  28. ↑ Wilson (1993), p. 110
  29. ↑ McLaughlin (2010), pp. 42–44
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Stephens (2006), pp. 301, 307
  32. ↑ ANAO (2007), p. 54
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ 35.0 35.1 35.2 35.3 35.4 35.5 35.6 Pittaway (2012), p. 22
  36. ↑ 36.0 36.1 Pittaway (2012), p. 23
  37. ↑ Pittaway (2012), pp. 23–24
  38. ↑ 38.0 38.1 38.2 Pittaway (2012), p. 24
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ 40.0 40.1 Frawley (2010), p. 48
  41. ↑ McLaughlin (2005), p. 115
  42. ↑ McLaughlin (2005), pp. 115–116
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Karim (1996), p. 71
  45. ↑ Moclair and McLaughlin (2014), p. 71
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Moclair and McLaughlin (2014), p. 72
  48. ↑ McLaughlin (2005), p. 165
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ McLaughlin (2005), p. 118
  51. ↑ McLaughlin (2005), p. 119
  52. ↑ 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Wilson (1993), p. 118
  54. ↑ Wilson (1993), p. 112
  55. ↑ 55.0 55.1 Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ McLaughlin (March 2005), p. 56
  57. ↑ McLaughlin (2005), p. 64
  58. ↑ Wilson (1993), p. 119
  59. ↑ 59.0 59.1 Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ ANAO (2000), p. 42
  62. ↑ ANAO (2000), p. 44
  63. ↑ ANAO (2004), pp. 14–18
  64. ↑ Frawley (2010), p. 45
  65. ↑ Frawley (2010), p. 49
  66. ↑ Wilson (1993), p. 120
  67. ↑ Frawley (2010), p. 44
  68. ↑ Wilson (1993), pp. 122–123
  69. ↑ Frawley (2010), p. 46
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Wilson (1993), pp. 124–125
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Horner (2011), pp. 383–384
  76. ↑ Horner (2011), p. 314
  77. ↑ Wilson (2003), p. 32
  78. ↑ McLaughlin (2005), p. 96
  79. ↑ ANAO (2004), pp. 53–54
  80. ↑ Holmes (2006), pp. 85–86
  81. ↑ Holmes (2006), p. 88
  82. ↑ Holmes (2006), p. 86
  83. ↑ Holmes (2006), pp. 89–91
  84. ↑ Holmes (2006), pp. 91–92
  85. ↑ Holmes (2006), p. 93
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  95. ↑ Davies (2011), pp. 7–8
  96. ↑ Moclair and McLaughlin (2014), p. 67
  97. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  98. ↑ 98.0 98.1 Lua error in package.lua at line 80: module 'strict' not found.
  99. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  100. ↑ Davies (2011), pp. 8–9
References
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=McDonnell_Douglas_F/A-18_Hornet_in_Australian_service&oldid=717143042"