Skip to main content

Engineering from the Sea: Establishing How Australian Army Engineers Fit Into Australia’s Amphibious Concept

Journal Edition

Abstract

The high demand historically placed on engineers by an amphibious landing force after it has deployed ashore requires that the manner that Australian Army engineers fit into Australia’s Amphibious Concept be established in order for the ADF to successfully execute amphibious operations, prior to any future such commitment. The list of engineering tasks needed to support the full spectrum of operations in the current and future operating environments is quite extensive, thereby an ad hoc engineer group to support the landing force cannot simply be formed, nor is there a one-size-fits-all engineer solution. This article is based on a paper submitted in partial fulfilment of the requirements for the degree of Master of Military Studies from the Marine Corps University. A copy of the full paper can be obtained at the Alfred M Gray Marine Corps Research Center USMC Research Library website.


The combat Marine engineer was described as the man who volunteered for nothing, but worked around the clock.

- Ralph W Donnelly1

Introduction

The Australian government stated in its Defence White Paper 2009 that ‘Australia’s defence policy should continue to be founded on the principle of self-reliance in the direct defence of Australia’.2 This White Paper dictated that Australia’s military strategy is principally a maritime one and assigned the Australian Defence Force (ADF) a primary operational environment covering approximately sixty-six million square kilometres—more than 12 per cent of the Earth’s surface.3 As a result, the Australian government decided that this expansive strategic geography requires the ADF to assume an expeditionary orientation4 at the operational level, underpinned by requisite force projection capabilities.5 Flowing from this requirement was the purchase of two amphibious Canberra class Landing Helicopter Dock (LHD) ships, due to enter service between early 2014 and mid-2015, and the early-2011 purchase of a former Royal Navy Bay class Landing Ship Dock (LSD). In order to provide the required expeditionary amphibious capability, the ADF produced Australia’s Amphibious Concept (AAC), which articulates the ADF’s aspirations for future amphibious warfare across the spectrum of amphibious operations.6

Engineers have always played, and will continue to play, a significant role in amphibious operations. The 13th Commandant of the United States Marine Corps (USMC), Major General John A Lejeune, wrote that ‘the Marine Corps for many years has carried on certain military activities of an engineering nature. Work which may properly so be designated is performed as a matter of necessity in almost every land campaign.’7 Engineers have also historically been an integral part of all major amphibious operations that Australia and its major allies, the United States and the United Kingdom, have conducted. Royal Australian Engineers (RAE) have thus played important roles in these amphibious operations, with Sapper Fred Reynolds of the 1st Field Company Engineers recorded as the first soldier to be killed on the Gallipoli Peninsula in 1915.8 The most recent amphibious operations conducted by the ADF primarily involved engineer forces providing humanitarian assistance and disaster relief following large-scale natural disasters in Indonesia in 2004–05 and 2009.

The most recent amphibious operations conducted by the ADF primarily involved engineer forces providing humanitarian assistance and disaster relief ...

With respect to engineers, neither the AAC nor the more detailed Landing Force Concept of Employment9 provide more definition than to state that engineers will be part of the battle group, around which the Amphibious Task Force (ATF) will base its landing force. Despite this, due to the high demand historically placed on engineers by a landing force after it has deployed ashore, the nature of how Australian Army Engineers fit into the AAC must be established in order for the ADF to successfully execute amphibious operations. This nature can be established through an examination and analysis of the engineer tasks and organisations that have contributed to previous successful amphibious operations from the Second World War to Operation ENDURING FREEDOM.

Description of the Military Problem

Australia's Amphibious Concept

The AAC is the concept for the employment of the ADF’s amphibious capability to its full potential, linking higher-level guidance and operational concepts with ADF operational-level doctrine for amphibious operations.10 The strategic military priorities established in the Defence White Paper 2009 are reaffirmed in the AAC: deter and defeat armed attacks on Australia, contribute to stability and security in the South Pacific and East Timor, contribute to military contingencies in the Asia-Pacific region, and contribute to military contingencies in the rest of the world.11

At the same time the ADF saw the need for the AAC, the USMC decided to get back to its amphibious roots after ten years of intense focus on ground operations in Iraq and Afghanistan.12 While closely aligned with the USMC’s Amphibious Operations in the 21st Century and Marine Corps Operating Concept – Third Edition, as well as the UK’s Littoral Manoeuvre (Amphibious Task Group) Joint Capability Concept, the AAC is tailored to secure Australia’s strategic interests with a relatively small-sized force. The AAC directs that ADF forces be prepared to conduct three distinct types of amphibious missions: amphibious operations, military support operations, and sea lift. Amphibious operations are further divided into four types: demonstration, raid, assault, and withdrawal. Military support operations are also further divided: Defence aid to the civil community or Defence Force aid to civil authorities; humanitarian assistance and disaster relief; non-combatant evacuation operations; peace operations; civil enforcement duties; and inter-agency, international organisation and nongovernment organisation liaison and support. Sea lift is the ‘administrative movement of personnel and/or equipment to and within the Joint Force Area of Operations’.13

In order to be interoperable with allies, the ADF’s amphibious concept aspires to develop Australian amphibious thinking based on an Australian analysis and conceptual models from US and UK doctrine. As a result, the four core concepts to underpin the Australian approach to amphibious operations reflect US and UK thinking: littoral manoeuvre, ship-to-objective manoeuvre, distributed manoeuvre, and sea basing. Like the US and UK, the core concepts require further development in order for the models to be fully implemented.14

For a country with relatively limited military assets, the Australian ATF must be flexible and adaptive to conduct sequential and/or simultaneous different missions. The AAC states that the ‘ATF must be a scalable organisation’, ‘be a balanced, mobile force ... with sufficient endurance to accomplish the mission, and deploy ‘without the reliance on host-nation infrastructure’.15 To achieve the large mission set, the AAC bases the future ATF around the deployment and sustainment requirements of the following two organisations:

  • Amphibious Ready Group (ARG). The ARG will be capable of the full suite of amphibious tasks. Its manoeuvre component will be a medium-weight battle group, of similar size to a USMC Marine Expeditionary Unit (MEU), of approximately 2200 personnel, with armoured vehicles, helicopters, associated stores and equipment. The engineer element will be squadron-sized.
  • Amphibious Ready Element (ARE). The ARE is a sub-element of the ARG and is primarily focused on the conduct of humanitarian assistance and disaster relief or non-combatant evacuation operations missions at very short notice. The manoeuvre component will be an infantry company based Ready Combat Team (RCT) and will include a troop-sized engineer element.16

For a country with relatively limited military assets, the Australian ATF must be flexible and adaptive to conduct sequential and/or simultaneous different missions.

Neither the AAC nor the derived Landing Force Concept for Employment defines tasks or an organisation for the engineer elements. The documents do, however, imply that substantial engineering effort will be required to ensure success. The Landing Force Concept for Employment states that the ‘ADF is to be prepared to conduct amphibious assault[s] ... into uncertain ... environments’17 and repeatedly highlights that humanitarian assistance and disaster relief operations will be a core skill set of the landing force. As the list of engineering tasks required to support these operations is quite extensive, an ad hoc engineer group to support the landing force cannot simply be put together without a detailed analysis of what it will likely do, what personnel and equipment it will require, and what training it will need.

Historical Examples Of The Employment Of Engineers In Amphibious Operations

A brief study of amphibious operational history highlights the utility of engineers and the fact that they were crucial for the manoeuvre elements in combat. The study of operational campaigns since 1943 provides examples of likely combat operations in the ADF’s primary operating environment: the USMC and RAE in New Guinea and the Central Pacific in the Second World War; the Royal Marines as they landed and advanced to their objective in the Falkland Islands (1982); the USMC entry operations into Somalia, with a focus on a low-mid intensity security environment (1992–93); and finally, the 2001 operations of the 15th and 26th MEUs for a planned non-combatant evacuation operation and the executed operations that seized two airfields inside Afghanistan in the early stages of OEF. All tasks noted were conducted within the first thirty days (many within the first seven days) of a landing force deploying ashore, which is well inside the mission duration that has been set for the ARG.18

Second World War

The strongest theme that emerged from analysing the official records of operations in New Guinea, including Gape Gloucester, on Saipan and in Borneo can be simply stated: terrain was very restrictive to the movement of the landing forces.19 The lack of key infrastructure in the region, such as roads and bridges, resulted in engineers providing the required mobility through the expedient construction and maintenance of beach exits, tracks, corduroy roads and bridges. (A lack of infrastructure in the ADF’s primary operating environment is still the case today.) These tasks were made all the more difficult during the extensive monsoon season, with its influence on both rain and surf. The weather was not the only challenge, as engineer tasks frequently had to be completed under enemy fire, often without protection.20 Other common tasks included obstacle reduction, minefield clearance, booby trap clearance and the destruction of enemy strong points to enhance mobility. General engineering tasks also had to be completed, including water supply, rapid airfield repair and improvement, and camp construction.21 In addition, the vast majority of amphibious engineers in the Second World War were required to execute infantry tasks; that is, engage in combat, the engineer’s ubiquitous secondary role.

The lack of key infrastructure in the region, such as roads and bridges, resulted in engineers providing the required mobility ...

The Falkland Islands, 1982

The Royal Engineers (RE) reinforced 59 Independent Commando Squadron (Five-Nine), which included a reconnaissance troop and a troop from 9 Parachute Squadron RE,22 provided the mobility and survivability support to 3 Commando Brigade (3 CDO BDE RM) when it secured a beachhead at San Carlos in East Falkland. The squadron then supported the advance east to the final objective, Stanley. While relatively light, with regards to engineering vehicles and specialist equipment, the amphibious engineers played a significant role in the operations to recapture the Falkland Islands. In addition to fighting as infantry, the significant engineer tasks Five-Nine undertook included: improving beach exits and roads; constructing hardstands; reconnoitring, breaching and clearing minefields and obstacles; rendering safe explosive ordnance and booby traps; constructing fighting positions and strong points; and water supply operations. Once the beachhead was secure, additional RE units were brought ashore to undertake the numerous general engineering tasks required to support the larger task force.23 The Commander of 3 CDO BDE RM wrote in his account of the war: ‘In war there are never enough Sappers and the support given to the Commando Brigade by its engineer squadron, which included a troop from 9 Squadron, was superb.’24

Somalia, 1992-93

As part of Operation RESTORE HOPE, the 1st Combat Engineer Battalion (1 CEB) supported the initial insertion of the Special Purpose Marine Air Ground Task Force (SPMAGTF) into Somalia with a reinforced combat engineer company. The bulk of effort provided by the company from 1 CEB at the start of the operation was on mobility tasks, including route reconnaissance, route maintenance, route clearance, mine clearance and work to open the port facilities. Survivability was another high priority, including strong point construction and facility hardening, as well as the provision of water and general security tasks. After the initial insertion of the SPMAGTF, additional engineers were flowed into theatre from 1 CEB, as well as from the US Navy Seabees, the Marine Wing Support Squadron and the 7th Engineer Support Battalion. At the eighteen-day mark, approximately 1300 engineers worked for the Marine Forces.25 An official and important lesson that emerged from Operation RESTORE HOPE: UN ‘chapter VI and VII operations [that is, Security and Stability Operations] in third world countries place high demands on engineer support’.26

Afghanistan, 2001

The seizure in late 2001 of forward operating base Rhino and Kandahar Airport by Task Force 58 (TF 58), consisting of the 15th MEU and the 26th MEU, is the most recent amphibious combat operation studied. Engineer support to this operation was crucial to the rapid build up of forces in Afghanistan and was almost exclusively flown in, initially by helicopter, then by KC-130 aircraft, and finally by C-17 transporters. Each MEU was supported by a reinforced combat engineer platoon, a reinforced support engineer platoon, a Marine Wing Support Squadron detachment, and an enlarged explosive detection dog section. TF 58 was also reinforced with a chemical biological inspection site team and a Seabee detachment of thirty engineers. The key tasks conducted by TF 58 engineers were: the rapid repair and expansion of the two airfields and helicopter landing zones; the conduct of high risk search tasks; the clearance of mines, booby traps, and explosive ordnance; the construction of fighting positions, strong points, and berms; the construction of hygiene-related camp facilities and the building of detainee compounds. Of particular note is the fact that both the 15th MEU and the 26th MEU were afloat when the events of 11 September 2001 occurred. Thus, neither MEU was task organised for this specific mission but they were prepared for it.27

... neither MEU was task organised for this specific mission but they were prepared for it.

Indonesia, 2004-05 and 2009

Since late 2004, the 1st Combat Engineer Regiment (1 CER) has twice provided short notice amphibious engineer forces for large-scale humanitarian assistance and disaster relief operations in Indonesia. In response to the devastating 2004 Boxing Day Indian Ocean Tsunami, 1 CER provided the main ADF contingent as part of the Australian government’s response in Banda Aceh. Here, it focused on water supply and debris clearance in order to reduce environmental health threats. In response to the 2009 magnitude 7.5 earthquake off Western Sumatra, 1 CER again provided the main ADF contingent to the Australian government’s response in Padang. On this occasion, it focused on water supply, structural building assessments, rendering safe important buildings, minor repairs to key lines of communication, and construction of semi-permanent medical centres. While both responses were very similar in nature, before deployment no contingency plans existed. This resulted in planning from first principles; that is, with a limited knowledge base for such an operation. 1 CER was very successful in both operations, largely due to the individuals who were available at the time to rapidly plan the tasks and then execute a quickly developed plan, providing modifications to it as required.28

Whether in the ADF’s primary operating environment or further afield, the range of engineer tasks required for an amphibious operation are vast, although common throughout, and cover the majority of tasks for which RAE sappers train. The review of historical operations showed that combat, support and specialist engineers were required, both individually and collectively, to complete the work and, on occasion, required supplementation. The historical employment of engineers on amphibious operations can help predict how engineers will be used on future expeditionary operations.

How Other Amphibious Forces Employ Their Engineers

United States Marine Corps

USMC engineer roles, tasks, organisation, and principles of employment differ significantly from that of the RAE. Thus, the USMC template cannot simply be transferred to the Australian ARG, even though the manoeuvre element is similar in structure to a USMC MEU. For example, petroleum operators and engineer vehicle mechanics are USMC engineer specialities but not RAE trades; conversely, electricians and explosive ordnance disposal technicians are RAE trades but not USMC engineer specialities. In addition, USMC combat engineer units have neither organic transport/drivers nor protected mobility vehicles to support a mechanised/motorised combat team. Overall, USMC engineers independently support the four elements of a Marine Air Ground Task Force: command element, ground combat element, air combat element, and the logistics combat element. As these four elements will exist in an Australian ARG, while named and organised differently, the task and breakdown of forces provide a good reference point. In addition, in order to expand on capabilities that do not exist in the USMC (but exist within RAE CERs and 6 ESR), a scalable and tailored naval construction force will often be attached. Typical engineer support to a MEU is shown in Figure 1. The engineer elements total approximately 103 to 120 personnel, without including the naval construction force.293

... the USMC template cannot simply be transferred to the Australian ARG, even though the manoeuvre element is similar in structure ...

The USMC 2024 Baseline MEB and MEU provides the future force structure of USMC manoeuvre formations, including their engineer elements.30 This baseline, used for future force concept modelling, includes very few changes to the engineer organisations organic to a MEU. The ground combat element is still supported by a reinforced combat engineer platoon and a reinforced engineer platoon is included in the combat logistics battalion. It can thus be deduced that the method by which the USMC employs its engineers will only substantially differ when the concepts of operation for USMC manoeuvre formations change significantly.

Royal Marines, Great Britain

The support provided by 24 Commando Engineer Regiment, Royal Engineers (24 Cdo Engr Regt, RE) to 3 CDO BDE RM is relatively light. This reflects the fact that 3 CDO BDE RM is a light-medium expeditionary force that does not include significant armoured elements, such as tanks, in its order of battle. Having previously supported the entire 3 CDO BDE RM with one regular independent commando squadron (Five-Nine), the RE are now upsizing to support the brigade with an engineer regiment.31 This is in accordance with the Australian model and highlights the fact that amphibious operations require considerable engineer support in order to attain success. The RE provide support to a battalion-size Royal Marine commando battle group with a squadron-size element, totalling approximately 126 to 173 personnel. The typical organisation is shown below in Figure 2.32

Australian Army

In accordance with Australian doctrine, the appropriate level of engineer support to an Australian battle group is usually provided by a combat engineer squadron, with a combat engineer troop supporting an independent company-sized combat team.33 This is not always strictly followed, with the size and composition often adjusted to cater for specific missions and operational environments. Currently in Afghanistan, a combat engineer squadron, reinforced with additional combat engineers and support engineers, provides the increased support required by the combined arms battle group. This level of support is predicated on the level of threat, type of weapons being used by the opposing forces and the counterinsurgency mission of the battle group. As Australia does not currently possess a dedicated amphibious capability, the engineer support to an amphibious operation is usually ad hoc. Another real world complicating factor exists: force structure is generally based on limits set by a manning cap rather than on an analysis of historically based likely tasks.

As Australia does not currently possess a dedicated amphibious capability, the engineer support to an amphibious operation is usually ad hoc.

Organisational chart of the Current Generic Engineer Support to a USMC MEU

Figure 1. Current Generic Engineer Support to a USMC MEU

Organisational chart of the Royal Engineer Support to a Royal Marine Commando Battle Group

Figure 2. Royal Engineer Support to a Royal Marine Commando Battle Group

The Current and Future Operating Environments

Studies in Australia, the United States and the United Kingdom34 have predicted similar future global and regional security environments, which have proved accurate in recent years. Traditionally, inter-state wars involving conflict between armed forces purpose-built for engaging in conventional combat (symmetrical warfare) have been the main focus of defence planning by Australia and its allies. In recent years, intra-state conflict among different political, ethnic or religious groups has come more to the fore in places such as Iraq and Afghanistan, where conventional military forces have had to work alongside civilian agencies and nongovernment organisations. Moreover, threats from some non-state global actors, such as al-Qaeda, have meant that armed forces have had to be employed against new types of adaptive adversaries. All of this has resulted in what is termed ‘complex war’ or asymmetrical warfare. While globalisation has seen growing interdependence between states, the Australian government still considers it premature to rule out future conventional wars between states, including the major powers.35

The ADF does not currently train for employment in a single environment; instead, it can be deployed from urban environments to jungles, from deserts to mountains. Global factors (including terrorism, pandemic disease, population growth, resource depletion and climate change security implications) as well as specific Asia-Pacific region factors (such as state fragility, poor governance, and economic underdevelopment and inequality) will affect Australia’s security interests, both directly and indirectly. Compounding these threats will be factors such as globalisation, urbanisation, the rise of new military powers, new technologies and other non-traditional challenges.36 Traditional societal structures and the ability of states to provide essential services as well as law and order will continue to be stressed by population and urban growth, no more so than in Melanesia and Southeast Asia.37 The principal physical characteristics of the ADF’s primary operating environment are its littoral nature, vast spaces between areas of human habitation and the presence of complex terrain. The broad range of topographical features tends to combine so that urban areas exist in close proximity to a mixture of agrarian land, coastal planes, mountains, tropical vegetation and coastal waterways.38 Compounding these environmental challenges are the frequent natural disasters that occur in the Southeast Asian and Pacific regions, most notably the seismic activity along the fault lines of the ‘ring of fire’. History suggests that challenges that lack opponents are more likely than those with an adversary, that is, significant opposition greater than opportunistic criminals.

The global and regional security environment means that the ADF should be prepared to face opponents who use the following capabilities: readily available ‘low tech’ capabilities; increasingly secure and sophisticated networked command and control, and ISR systems; increasingly conventional platforms that enhance lethality, survivability, and deployability; and increasingly available advanced conventional weapons as well as chemical, biological, radiological, nuclear and explosive devices.39 States now no longer possess a monopoly on advanced weaponry, as non-state actors, such as terrorist groups and irregular forces, have acquired the means, knowledge and employment capability of increased lethality.40 The conventional capabilities of many states will also improve, so both state and non-state adversaries will be able to acquire increased lethality. A significant trend, while not new, has been identified in recent conflicts where previous notions of distinct forms of war and conflict—conventional war, irregular challenges, terrorism and criminal activity—have become blurred into what is being described as hybrid challenges. These hybrid challenges can be created by state and non-state groups, and will result in opponents that can merge different approaches and integrate various weapons, tactics and technologies to deny access and freedom of action.41 A recent example is the 2006 Israel-Lebanon conflict.42

The conventional capabilities of many states will also improve, so both state and non-state adversaries will be able to acquire increased lethality.

There are numerous implications for the conduct of engineer operations arising from the forecast of the security environment in which the ADF will operate in the next twenty to thirty years. Firstly, terrain in the littoral areas will provide significant mobility challenges that engineers will need to overcome. This harks back to operations in New Guinea and the Pacific during the Second World War, where engineers directly influenced and contributed to the speed at which operations were executed. Secondly, the ADF’s adversaries will use various combinations of conventional and improvised weapons systems to attack a landing force. These may combine conventional minefields and obstacles with improvised explosive devices (IEDs) and booby traps in urban terrain, including at airfields and ports that may be used for the ingress of follow-on forces. Finally, the frequency with which natural disasters, such as earthquakes, tsunamis, volcanic eruptions and cyclones have occurred in the past six years within Australia’s primary operating environment, will ensure that the ADF’s response to humanitarian assistance and disaster relief operations is engineer intensive.

Capabilities Required Of The Amphibious Engineer Force

What do the future operation environment and historical employment of amphibious engineers indicate? Individualised lethality of modern weapons and the disaggregated battlespace means that, in complex war, land forces will encounter more lethal enemies, with less warning, in close combat and in complex terrain. Therefore, all deployed land force elements, including engineers, will need to be given sufficient levels of protection, mobility and firepower to conduct sustained close combat within the complex battlespace. Importantly, the land force will need to survive first contact with the enemy and react accordingly. Additionally, Adaptive Campaigning – Future Land Operating Concept states ‘the land force will need the capacity to conduct rapid route clearance and gap crossing, maintain essential lines of communication and operate within a contaminated environment’.43

... all deployed land force elements, including engineers, will need to be given sufficient levels of protection, mobility and firepower to conduct sustained close combat ...

Today and in the future, the combat and support engineers bring to the battlefield both constructive (e.g. building strong points and providing essential services) and destructive (e.g. obstacle breaching and demolitions) capabilities. This unique amalgamation of contrasting capabilities provides skills, knowledge and experience to commanders at the operational and tactical levels with which the commanders can reduce friction, facilitate manoeuvre and increase the morale of friendly forces, or create friction and disorder to break the cohesion of the enemy. The combat engineer earns his title most notably through assault breaching of enemy obstacles and fortifications, or by their contribution of firepower in the form of supplementary infantry support and self-protection. The capabilities provided can be decisive in maintaining momentum in the attack or responding quickly to an enemy’s counterattack.44 These required engineer capabilities are common to all current and future operations, not just amphibious operations. Due to space constraints on the amphibious ships, which restricts the amount of engineer personnel, vehicles and equipment that can be carried, the number and type of tasks that can be undertaken by amphibious engineers is also restricted.

The challenge therefore becomes determining or prioritising the most likely tasks that will be required. Once done, an engineer force can be developed that is capable of covering the majority of these tasks while remaining within the space restrictions. The wide range of military and engineer tasks for which the ADF is required to prepare, across the full spectrum of operations in the current and future operating environments, means that there cannot be a one-size-fits-all engineer solution. Therefore, five likely scenarios are proposed, covering the spectrum of amphibious operations with their multitude of engineer options. The scenarios are as follows:

  • Scenario 1. Support to an ARE conducting Phase Zero (shaping) operations, minor humanitarian assistance and disaster relief operations and non-combatant evacuation operations. Engineer tasks will include minor vertical and horizontal construction, including strong points, searches for simple IEDs and water supply.
  • Scenario 2. An engineer task force conducting a major humanitarian assistance and disaster relief operation as a result of a ‘large scale’ natural disaster, such as the Indian Ocean Boxing Day Tsunami. Engineer tasks will focus on water supply and debris clearance in order to reduce environmental health threats as well as essential infrastructure assessments, structural building assessments, rendering safe important buildings, minor repairs to key lines of communication and construction of semi-permanent community health buildings.
  • Scenario 3. Support to an ARG conducting regional stability operations, such as the Regional Assistance Mission to the Solomon Islands in 2003 and East Timor in 2006. Engineer tasks will include clearing beach obstacles, countering unsophisticated IEDs, minimal preparation of beach landing sites and small-scale expedient construction tasks.
  • Scenario 4. Support to an ARG conducting entry operations for a mediumintensity regional conflict, such as for the International Force East Timor (INTERFET) in 1999. Engineer tasks will include clearing beach obstacles, clearing basic IED/mine threat against air operations, countering IED threats on roads, the construction/enhancement of landing zones, preparation of beach landing sites and basic camp construction.
  • Scenario 5. Support to an ARG conducting entry operations for a major regional conflict involving a Coalition Task Force, in the manners of 3 CDO BDE RM in the Falkland Islands in 1982 and 15th/26th MEU in seizing APODs in Afghanistan in 2001. Engineer tasks will include clearing beach obstacles, clearing sophisticated IED/mine threats targeting air operations, countering sophisticated IED threats on roads, breaching or clearing a mine threat, the construction of landing zones, preparation of beach landing sites, the construction and maintenance of routes, basic camp construction and the construction of defences.

The likely tasks for amphibious engineers can be distilled from analysing historical records from operations similar to those that the Australian ATF will undertake, described in the five scenarios, or from operations that have occurred in Australia’s primary operating environment. From these tasks a mixture of combat, support and specialist engineers is required for low-intensity missions such as Phase Zero operations, humanitarian assistance and disaster relief operations and small-scale security operations. The majority of these engineers reside in a CER. The analysis also shows that for large-scale high-intensity operations, where the ATF conducts entry operations for a follow-on force, the variety and number of simultaneous engineer tasks that will be encountered will require a follow-on engineer force. Initially independent, it may then function as part of a coalition engineer capability to facilitate the flow of the ensuing forces. The majority of engineer tasks required to secure the points of entry, however, can be executed within the existing capabilities of a CER by a reinforced combat engineer squadron.

The likely tasks for amphibious engineers can be distilled from analysing historical records from operations similar to those that the Australian ATF will undertake ...

What is not captured in the task analysis, and is often overlooked, is the requirement for the provision of engineer advice and engineer planning. Due to the fact that there are so many different engineer tasks, the vast majority of which require technical knowledge to plan and execute, it is essential that engineers are represented from the outset in all operations planning processes.45 Therefore, an engineer planner, or at least an engineer liaison officer, must always be included in ATF planning groups as well as in the landing force headquarters. While this function is sometimes filled by the headquarters of the engineer force, the need for the engineer headquarters to monitor and control engineer tasks results in this element often being physically distanced from the supported battle group headquarters. As such, it is recommended that an RAE Officer always be included in the landing force headquarters, either as a permanent liaison officer or as one of the operations cell staff.

Concept Of Employment

Assumptions And Restrictions

Several assumptions have been made for the provision of engineer capabilities to the scenarios. For the development of engineer options it has been assumed that the light vehicles, protected mobility vehicles and trucks will be replaced with similar vehicles as part of the current ADF land vehicle fleet replacement program. It is also assumed that medical support to the engineer element will either be provided by the supported battle group element or by the main combat service support element, except for Scenario Two where the medical element would be organic. Finally, it is assumed that the follow-on engineer element will be transported by either black-bottom vessels or coalition ships.

... it is assumed that the follow-on engineer element will be transported by either black-bottom vessels or coalition ships.

A feasible and suitable engineer solution to the outlined problem must be good, fast and cheap as well as be within the restrictions set by the ADF. The Landing Force Concept for Employment and modelling data used by the Joint Amphibious Capability Implementation Team gives the size of engineer force and its equipment for which there is space available on the amphibious ships. The publication Employment of Engineers provides the governing principles and guidelines for the employment of engineers by the Australian Army. Documents for the Modular Engineer Force, which is the RAE’s ongoing Force Modernisation Review, provide the guidance as to how engineers will meet future warfighting challenges and how they will be commanded and controlled. These documents provided the constraints for this analysis, as outlined in Table 1.

Scalable Options

Taking into account the constraints, the five scenarios covering the likely employment of engineers in amphibious operations necessitate five different and scalable organisation options, due to the size of the force being support, type of amphibious mission being supported and the variety of resulting tasks. An overview of each option is as follows:

  • Scenario 1 – Support to an ARE conducting Phase Zero (Shaping) operations, minor humanitarian assistance and disaster relief operations and noncombatant evacuation operations. As the ARE is of company-size, it requires a reinforced troop-sized option. The likely security cooperation and minor HA/DR missions, which will dominate the ARE deployments, will most probably involve light construction. This would require four tradesmen and two plant operators. The military tradesmen would supervise construction works by the combat engineers as well as undertake specialist trade work. Two mechanised sections are included to provide self-protected engineer support to the combat team and can additionally serve as infantry sections for security operations. The light combat engineer section is air mobile, providing mobility capabilities, such as search, as well as the ability to conduct water supply tasks. The troop is reinforced with a two-man explosive ordnance disposal detachment and two explosive detection dog teams,46 to increase the search and explosive ordnance capabilities of the troop. The troop has organic transport, a storeman and a mechanic. Planning with the ARE headquarters would be provided by an RAE captain, as either a liaison officer or operations staff member, as well as a geospatial technician.

Table 1. Constraints on the Employment of Engineers used in the Analysis

No.

Constraint Details

How Constraint Applies

1

The Load Planner for the ARG used an estimate of 158 engineers, fourteen armoured vehicles, five light vehicles with four trailers, three medium-weight trucks with five trailers, eight heavy trucks with two heavy trailers, one water purification unit, six tracked plant machines and four wheeled plant machines. This provides total lane meterage of 413.7m. The engineer element supporting an ARG can have a strength of up to 158 persons and can have a maximum total lane meterage of 413.7m.

2

The Load Planner for the ARE used an estimate of fifteen engineers, two PMVs and no additional engineer equipment. As this load calculator had a spare capacity of 446 persons but only three lane metres, it is also assumed that up to fifty engineers can be used. The engineer element supporting an ARE can have a strength of up to fifty persons.

3

The secondary role of RAE is to fight as infantry. For low-intensity operations, such as Phase Zero and non-combatant evacuation operation, engineers can also perform the roles of infantry.

4

The solution must have centralised control with decentralised execution. The engineer element must have one overall headquarters for planning and coordination.

5

Early warning and reconnaissance – engineers must have participants in the planning of operations at the outset and be given the opportunity to conduct reconnaissance. There must be an engineer in the headquarters as well as part of any reconnaissance team.

6

Economy of effort – it is uneconomical either to apply more engineer effort than is necessary to complete tasks in the required time or to use engineer effort on the unskilled aspects of engineer tasks. Only the minimum number of engineers are included; however, engineer positions cannot be sacrificed for personnel who can provide unskilled labour.

7

The appropriate levels of engineer support for most types of operations are as follows: combat engineer troop to a manoeuvre sub-unit and combat engineer squadron to a manoeuvre unit. ARE will be supported by a reinforced troop and the ARG will be supported by a reinforced squadron.

8

Engineer sections will have eight members. This does not include the sections with protected mobility, which require a dedicated crew commander and a driver. The light combat engineer elements will have eight-man sections, while the mechanised combat engineer elements will have ten-man sections.
  • Scenario 2 – An Engineer Task Force conducting a major humanitarian assistance and disaster relief operation as a result of a ‘large scale’ natural disaster. The scale of such a disaster would require a dedicated Engineer Task Force to be deployed. As the engineer group forms the nucleus of the ATF, this option would include a sizeable organic logistics element. A chaplain and a minimum of two interpreters are included due to the nature of the work being undertaken. The option includes two combat engineer troops—one dedicated to water supply tasks and the other to general engineering—as well as medium-weight plant and tradesmen elements. An emergency response detachment has been included to handle potentially hazardous materials, such as asbestos. An RAE captain is included in the Joint Task Force headquarters, as well as a geospatial technician. It is also more than likely that a technically qualified structural assessment team, supplemented from outside a CER, would be required to technically assess building and bridge damage.
Organisational chart of the Engineer Support to an ARE (Scenario 1)

Figure 3. Engineer Support to an ARE (Scenario 1)

Organisational chart of the Engineer Support to a Major Humanitarian Assistance and Disaster Relief Operation (Scenario 2)

Figure 4. Engineer Support to a Major Humanitarian Assistance and Disaster Relief Operation (Scenario 2)

  • Scenario 3 – Support to an ARG conducting regional stability operations. As the ARG is battalion-size, it requires a reinforced engineer squadron for support. Two combat engineer troops would support the manoeuvre forces: a mechanised troop supporting the two mechanised combat teams and a light troop, with organic transport, supporting the two air mobile combat teams. The substantial general engineering tasks required of this mission, primarily the construction and maintenance of roads and airfields, as well as the construction of camp infrastructure and survivability tasks, demands a light-medium weight support engineering troop. A specialist troop is also included to provide the suite of likely explosive ordnance disposal, explosive detection dog and hazardous material capabilities. The explosive ordnance disposal team would use a Buffalo-type mine protected clearance vehicle, as is currently being used to counter the IED threat in Iraq and Afghanistan. Planning with the ARG headquarters would be provided by the squadron headquarters. No follow-on engineer element is required, unless the situation escalates and the ARG is reinforced.
  • Scenario 4 – Support to an ARG conducting entry operations for a medium intensity regional conflict. This option builds on the solution provided for in Scenario 3 by including two assault breacher vehicles and a follow-on engineer force. The latter would comprise a works team and construction squadron element. The ABVs are included with the mechanised troop to recognise the heightened IED and mine threat, providing the ability to conduct rapid route clearance, minefield and obstacle breaching, as well as the reduction of enemy strong points. The works team and construction squadron detachment are required to deploy, by either black-bottom or coalition shipping, to supplement the support engineer assets with the combat engineer squadron. The tasks of this follow-on force will primarily involve camp construction for the follow on battle groups, the construction and maintenance of roads, the expansion and maintenance of airfield(s), and the establishment of air points and sea points of disembarkation.
Organisational chart Engineer Support to an ARG – Regional Stability Operations (Scenario 3)

Figure 5. Engineer Support to an ARG – Regional Stability Operations (Scenario 3)

Organisational chart of the Engineer Support to an ARG - Medium Intensity Regional Conflict (Scenario 4)

Figure 6. Engineer Support to an ARG - Medium Intensity Regional Conflict (Scenario 4)

  • Scenario 5 – Support to an ARG conducting entry operations for a major regional conflict involving a coalition task force. This option builds on the solution postulated for in scenario 4. The squadron headquarters becomes mechanised, an armoured vehicle launched bridge is added to the mechanised troop, an additional combat engineer section is added to the light combat engineer troop, the number of explosive ordnance disposal teams is increased, an air crash rescue team is included and the follow-on engineer force is expanded to comprise a Works Team and a complete construction squadron. Mechanising the headquarters provides it with the required protected mobility to conduct engineer reconnaissance tasks in the high-threat environment. The armoured vehicle launched bridge will allow the provision of protected tactical gap crossing capabilities. The additional engineer section is included to balance the support available to the air mobile combat teams, which may be distributed due to the increased air threat. The increased air threat predicates the requirement to augment the emergency response detachment by including an air crash rescue team. The heightened IED threat demands the increase of explosive ordnance disposal capabilities, as has been experienced in Afghanistan. Finally, as the Australian ATF may be providing entry operations for a coalition follow-on force, the follow-on engineer force has been enlarged to cope with the increased demand for engineer works. The follow-on construction squadron would initially operate under command of the ARG, but would in time become part of the coalition engineers. When functioning as part of the coalition engineers, a liaison officer would be required, in addition to a level of command and control appropriate to the coalition.

Mechanising the headquarters provides it with the required protected mobility to conduct engineer reconnaissance tasks in the high-threat environment.

Required Materiel

The vast majority of vehicles and engineer equipment required to provide the recommended engineer support is either currently in service or will come into service as part of ongoing Army vehicle fleet replacement programs. Currently the Australian Army lacks any form of protected specialist combat engineering equipment, which goes against requirements of both the Defence White Paper 200947 and the AAC.48 In order for this issue to be remedied, a Buffalo-type mine protected clearance vehicle, the assault breacher vehicle and an armoured vehicle launched bridge need to be included in the ADF’s Defence Capability Plan.

Organisational chart of the Engineer Support to an ARG – Major Regional Conflict (Scenario 5)

Figure 7. Engineer Support to an ARG – Major Regional Conflict (Scenario 5)

Conclusion

The Australian government has decreed that Australia’s military strategy is principally a maritime one and that the ADF is to assume an expeditionary orientation at the operational level, underpinned by requisite force projection capabilities. The ADF has responded to this by developing an amphibious capability, with an Amphibious Task Force consisting of two LHDs and an LSD to deliver a mediumweight battalion-size battle group to its area of operations. Underpinning this capability is Australia’s Amphibious Concept, which links higher-level guidance and operational concepts with ADF operational level doctrine for amphibious operations. The concept, and its supporting concepts of employment, states the need for engineers to support amphibious operations, but specifies neither likely tasks nor organisation.

Engineers have historically always played a key enabling, and sometimes leading, role in amphibious operations, more often than not receiving praise for their work. The future operating environment will continue to demand that engineers enable, support and enhance the manoeuvre elements of a Joint Task Force by providing mobility, counter-mobility, survivability and sustainability to these combat arms in likely hybrid threat environments. Because of the wide spectrum of operations that exist both now and into the future, the required enabling tasks are too numerous to be covered by a single engineer organisation.

It is therefore proposed that five engineer contingencies be planned to cover the spectrum of possible operations, ranging from a permanent reinforced troop to support defence cooperation and short-notice security missions, to a reinforced combat engineer squadron that is followed by a construction squadron to support forced entry operations as part of a coalition at the high-intensity end of the operational spectrum. These options, and those in between, carefully balance the limited space for personnel and equipment on the amphibious ships with the array of likely tasks that have been distilled from historical examples for the types of operations that are expected to occur again. If Australia is to have a serious amphibious capability, the Australian Army must genuinely invest time, effort and money to ensure that it is capable of conducting engineering from the sea.

About The Author

Major Michael Scott is a Distinguished Graduate of the USMC Command & Staff College, where he earned a Master of Military Studies. He holds a First Class Honours Degree in Civil Engineering, a Master of Engineering Science and he is a Chartered Practicing Engineer. Major Scott has had postings to the 3rd Combat Engineer Regiment, 19th Chief Engineer Works, 17th Construction Squadron and 1st Combat Engineer Regiment. He deployed to the Solomon Islands in 2003, was embedded with US and Dutch provincial reconstruction teams in Afghanistan in 2006 and deployed an Engineer Task Group in response to the 2009 Padang earthquake. Major Scott is a student at the USMC School of Advanced Warfighting.

Endnotes


1     Ralph W Donnelly, Historical Branch, G-3 Division, Headquarters, US Marine Corps, April 1968 (regarding USMC engineers in WWII), ‘A Brief History of U.S. Marine Engineers’, Marine Corps History Division, 9 April 1968 <https://www.intranet.tecom.usmc.mil/sites/History%20Division/ default.aspx>.

2     Defending Australia in the Asia Pacific Century: Force 2030, Defence White Paper 2009, Department of Defence, Canberra, 2009, p. 48.

3     Australia’s Amphibious Concept, v5.2, Department of Defence, Canberra March 2010, p. 4; Defence White Paper 2009, p. 51. The primary operational environment extends from the eastern Indian Ocean to the island states of Polynesia and from the equator to the Southern Ocean. That area contains all Australian sovereign, offshore and economic territories, such as Cocos (Keeling) Islands, Christmas Island, Heard and McDonald Islands, Macquarie Island, Norfolk Island, plus waters adjacent to the Australian Antarctic Territory.

4     Major General Julian Thompson, RM (Rtd), ‘Expeditionary Forces and Expeditionary Warfare: Major Themes and Issues’ in Battles Near and Far: A century of overseas deployment, 2004 Chief of Army History Conference, Australian Army History Unit, Canberra, 2005, p. 6. In his keynote address to the 2004 Chief of Army History Conference, Major General Thompson defined Expeditionary Operations as: ‘A military operation that can be initiated at short notice, consisting of forward deployed or rapidly deployable, self-supporting forces tailored to achieve a clearly stated objective in a foreign country’. (Original emphasis shown)

5     Defence White Paper 2009, pp. 51–52.

6     Australia’s Amphibious Concept, p. 3. Australian Defence Doctrine Publication (ADDP) 3.2 – Amphibious Operations defines Amphibious Operations as: ‘A military operation launched from the sea by a naval and landing force embarked in ships, landing craft or rotary wing aircraft, with the principal purpose of projecting the landing force ashore tactically into an environment ranging from permissive to hostile’.

7     John A Lejeune, ‘The Engineer Battalion of the Marine Corps’, Leatherneck Magazine, August 1928, p. 4, <http://proquest.umi.com&gt;.

8     Ronald Ramsay McNicoll, The Royal Australian Engineers 1902 to 1919: The Second Volume of the History of the Royal Australian Engineers, Ligare Pty. Ltd, Riverwood, 1979, p. 27.

9     Amphibious Deployment and Sustainment System, Landing Force Concept for Employment, v2.0,, Department of Defence, Canberra, March 2010.

10    Australia’s Amphibious Concept, p. 3. The ADF doctrine is ADDP 3.2 – Amphibious Operations and ADFP 3.2.1 – Amphibious Operations Procedures.

11    Australia’s Amphibious Concept, p. 6.

12    Sam LaGrone, ‘Shifting Horizons: Marines Refocus Their Future at Sea’, Janes Defense Weekly, <http://jdw.janes.com&gt;.

13    Australia’s Amphibious Concept, p. 7.

14    Ibid., p. 10.

15    Ibid., pp. 8, 13–14.

16    Ibid., p. 14.

17    Landing Force Concept for Employment, p. 7.

18    Amphibious Deployment and Sustainment System, Logistics Concept for Employment, p. 4.

19    Official records of the Marine Corps’ 1st Division in Gape Gloucester, V Amphibious Corps on Saipan, and various RAE units in New Guinea and Borneo are cited below.

20    ‘Special Action Report, Cape Gloucester Operation, Vol II’, Headquarters, First Marine Division, Archives and Special Collections Branch, Library of the Marine Corps, Cape Gloucester Collection, Box 4, Folder 1, December 1943, p. 10.

21    Ibid.; ‘Northern Troops and Landing Force Operations Report Phase I (SAIPAN)’, Headquarters, Northern Troops and Landing Force, Archives and Special Collections Branch, Library of the Marine Corps, WWII Marianas Islands Collection, Box 4, Folder 2, 12 August 1944; and McNicoll, The Royal Australian Engineers 1919 to 1945.

22    Major General Julian Thompson, RM (Rtd), No Picnic, Pen & Sword Books Ltd, York, 1992, pp. 5–6 and 18.

23    Major General Nick Vaux, RM (Rtd), Take That Hill: Royal Marines in the Falklands War, Brassey’s (US) Inc., New York, 1990; Michael Clapp and Ewen Southby-Tailyour, Amphibious Assault Falklands: The Battle of San Carlos Water, Pen & Sword Military, Barnsley, 2007); and Ministry of Defence, Director of Public Relations (Army), The British Army in the Falklands, 1982 (London, UK: Her Majesty’s Stationery Office, 1983), 13.

24    Thompson, No Picnic, 104.

25    ‘Command Chronology for the Period 4 February to 30 June 1993’, July 15, 1993, 1st Combat Engineer Battalion, Archives and Special Collections Branch, Library of the Marine Corps, Command Chronology Collection Box 1482, Folders 9 and 10.

26    Center of Military History, United States Army, United States Forces, Somalia After Action Report (Washington, D.C.: Center of Military History, United States Army, 2003), 252.

27    ‘Command Chronology for the Period 27 October 2001 to 26 February 2002’, Task Force 58, Archives and Special Collections Branch, Library of the Marine Corps, Command Chronology Collection Box 2226, Folder 1, March 2002; ‘Command Chronology for the Period 1 July 2001 to 31 December 2001’, 15th Marine Expeditionary Unit, Archives and Special Collections Branch, Library of the Marine Corps, Command Chronology Collection Box 2205, Folder 4, 2 March 2002; and ‘Command Chronology for the Period 1 July 2001 to 28 February 2002’, 26th Marine Expeditionary Unit, Archives and Special Collections Branch, Library of the Marine Corps, Command Chronology Collection Box 2226, Folders 6 and 7, 31 May 2002.

28    1st Combat Engineer Regiment, Plan READY ASSIST – 1 CER Support to HA/DR Operations (DRAFT), Department of Defence, Darwin, July 2010, p. 1.

29    Seabee Operations in the MAGTF, MCWP 4-11.5, Headquarters US Marine Corps, Washington DC, November 1997, pp. 1-33 – 1-41, 2-10; Lieutenant Colonel Jeffrey Miller, USMC Engineer, email messages to author, 14 November 2010 and 11 January 2011; and Major Taylor White, USMC Engineer, email message to author, 20 January 2011.

30    ‘2024 Baseline MEB and MEU’, information brief, Marine Corps Combat Development Command, Quantico, VA, 7 January 2010.

31    Littoral Manoeuvre (Amphibious Task Group) Joint Capability Concept, UK: Development, Concepts and Doctrine Centre, Shrivenham, 30 June 2009, pp. A-3–A-4.

32    Captain Ben Simpson, RE, HQ 24 Commando Engineer Regiment, email message to author, 19 January 2011.

33    LWD 3-6-1 - Employment of Engineers, Land Warfare Development Centre, Puckapunyal, 16 October 2007, p. 2-5.

34    Results of these studies are reported in: Adaptive Campaigning - Army’s Future Land Operating Concept, Department of Defence, Canberra, September 2009); ; Joint Operations for the 21st Century, Department of Defence, Canberra, May 2007; Littoral Manoeuvre (Amphibious Task Group) Joint Capability Concept; and The Joint Operating Environment 2010, Headquarters United States Joint Forces Command, Norfolk, 18 February 2010.

35    Defence White Paper 2009, p. 21.

36    Joint Operations for the 21st Century, p. 4.

37    Adaptive Campaigning, p. 12.

38    Ibid., p. 14.

39    Joint Operations for the 21st Century, p. 6.

40    Adaptive Campaigning, p. 12.

41    Marine Corps Vision & Strategy 2025, Headquarters US Marine Corps, Washington DC, 18 June 2008, pp. 21–22.

42    For more information about Hybrid Wars and the 2006 Israel-Lebanon conflict, see: Frank G Hoffman, Conflict in the 21st Century: The Rise of Hybrid Wars, Potomac Institute for Policy Studies, Arlington, December 2007, <http://www.potomacinstitute.org/images/stories/publications/potomac_hyb…;; and Colonel Steven C Williamson, ‘From Fourth Generation Warfare to Hybrid War’, Master’s thesis, US Army War College, 2009, <http://www.dtic.mil/cgi-bin/GetTRDoc? AD=ADA498391&Location=U2>.

43    Adaptive Campaigning, p. 66.

44    MCWP 3-17 – Engineering Operations, Headquarters U.S. Marine Corps, Washington DC, 14 February 2000, p. 1-1.

45    Employment of Engineers, p. 10-5.

46    An explosive detection dog team consists of a handler and an explosive detection dog. 47 Defence White Paper 2009, p. 75.

48    Amphibious Deployment and Sustainment System, Landing Force Concept for Employment, p.,7.