CIMSEC is committed to keeping our content FREE FOREVER. Please consider donating to our annual campaign now so we can continue to provide free content.
By LTJG Kyle Cregge, USN
In response to the four recent mishaps, the U.S. Navy Surface Force is going through a cultural shift in training, safety, and mission execution. The new direction is healthy, necessary, and welcomed in the wake of the tragedies. Admiral Davidson’s “Comprehensive Review of Recent Surface Force Incidents” examines a myriad of different aspects of readiness in the Surface Force and the recommendations are far-reaching. There will likely be more training and scrutiny added to officer pipelines and ship certifications, some of which will come from the newly-created Naval Surface Group Western Pacific.
Included in the review were the subjects of Human Systems Integration (HSI) and Human Factors Engineering (HFE), in which the Review Team Members describe how “Navy ships are equipped with a navigation ‘system-of-systems,’” and that “The large number of different bridge system configurations, with increasingly complex and ship-specific guidance on how to make them work together, increases the burden on ships in achieving technical and operational proficiency.” I had the same experience – one where an Officer of the Deck (OOD) was challenged to monitor up to five different consoles with assistance from six different watchstanders while maintaining safety of navigation and executing the plan of the day. Thankfully, the recommendations in the Comprehensive Review address these difficulties, and five specifically address the immediate, unique needs of OODs:
3.2 Accelerate plans to replace aging military surface search RADARs and electronic navigation systems.
3.3 Improve stand-alone commercial RADAR and situational awareness piloting equipment through rapid fleet acquisition for safe navigation.
3.4 Perform a baseline review of all inspection, certification, assessment and assist visit requirements to ensure and reinforce unit readiness, unit self-sufficiency, and a culture of improvement.
3.8 As an immediate aid to navigation, update AIS laptops or equip ships with hand-held electronic tools such as portable pilot units with independent ECDIS and AIS.
3.13 Develop standards for including human performance factors in reliability predictions for equipment modernization that increases automation.
One solution to the recommendations would be the addition of Automated Celestial Navigation (CELNAV) systems which could provide additional navigation support to Bridge watchstanders. Specifically, the systems could continuously fix the ship’s position in both day and night with as good, if not better, accuracy provided by sights and calculations using a computer, without the risk of human error or GPS spoofing. An automated celestial navigation system could either feed directly into the ship’s Inertial Navigation System (INS) or feed into a display in the pilothouse (with which a Navigator could verify the accuracy of active GPS inputs within a specified tolerance), both of which would provide redundancy to existing navigation systems. Automatic CELNAV systems are already used in the military, could be applied to surface ships rapidly, and could serve as a redundant, automated, and immediate aid to navigation against the potential threat of GPS signal disruption.
The Review Team’s recommendation to accelerate replacement of aging radars is a primary focus to support OODs, but given the capabilities of peer competitors against our GPS, rapid investment in shipboard CELNAV systems would be a worthwhile secondary objective. There is significant evidence of Russia testing a GPS spoofing capability in the Black Sea in June of this year, when more than twenty merchant ships’ Automated Identification Systems (AIS) were receiving locations placing them 25 nautical miles inland of Russia, near Gelendyhik Airport, rather than in the north-eastern portion of the Black Sea. Further, China maintains plans to actively combat the use of the Global Hawk UAV, to include, “electronic jamming of onboard spy equipment and aircraft-to-satellite signals used to remotely pilot the drones, [and] electronic disruption of GPS signals used for navigation.” At the outbreak of broader conflict one can imagine a far greater and more extensive denial effort for surface forces.
Due to potential threats, there are built-in securities for military GPS receivers to combat disruption threats. These include the Selective Availability Anti-Spoofing Module (SAASM) and expected upgrades for GPS Block III, to include more secure signal coding, with a scheduled inaugural launch in Spring 2018. Automated CELNAV can actively compliment both security mechanisms by providing redundancy against a technical failure or a cyber-attack and before the remaining GPS Block III satellites are brought online.
From a training perspective, the U.S. Navy reinstituted celestial navigation instruction for midshipmen in 2016 and quartermasters and junior officers in 2011 throughout their pipelines. The officers and quartermasters are trained to use the computer-based program STELLA (System To Estimate Latitude and Longitude Astronomically), developed by George Kaplan of the U.S. Naval Observatory in the 1990s. While the use of the program has sped the process of sightings to fixes from nearly an hour down to minutes, there is still a delay and the potential for human error. Automated CELNAV systems can provide both an extra layer of shipboard security against the potential threat of GPS disruption and assist in fixing the ship’s position continuously and as accurately as human navigators. Both arguments support increased readiness in the surface force and make ships more self-sufficient in the event of potential GPS disruption.
In 1999 George Kaplan argued that independent alternatives to GPS were necessary and required and that the hardware to implement these alternatives was readily available. Potential Automated CELNAV systems that could be configured for surface ships are already used in both the Navy and the Air Force. Intercontinental Ballistic Missiles (ICBMs), SR-71 Blackbird, RC-135, and the B-2 Bomber each use systems like the NAS-26, an astro-inertial system initially developed in the 1950s by Northrop for the Snark long-range cruise missile. Similar systems have previously been proposed for the Surface Forces. Cosmo Gator, an automated celestial navigation system, was submitted by LT William Hughes, then-Navigator of USS Benfold (DDG 65). This system would update the ship’s Inertial Navigation System (INS) with the calculated celestial position to provide essential navigation data for the rest of the combat system. OPNAV N4 funded LT Hughes’ proposal in March 2016 following the Innovation Jam event onboard USS Essex (LHD 2). Rapidly acquiring any of these various Automated CELNAV options supports the same piloting and situational awareness recommendations as an integrated bridge RADAR suite. The Navy can continue to cultivate a culture of improvement and further equip ships through the acquisition of more immediate aids to navigation like CELNAV systems.
Conclusion
As a result of the Comprehensive Review and associated ship investigations, the Surface Force is looking at innovative solutions to ensure that tragedies aren’t repeated. While the Navy strives to build a culture of improvement and to implement the CNO’s “High-Velocity Learning” concept continually, we must seek answers not only to the problems we face today but the threats we face tomorrow. The threats from peer competitors are defined and growing, but the options to provide greater shipboard redundancy are already created. In the same context that the Surface Force will endeavor to improve human systems integration for our bridge teams, we also should pursue Automated Celestial Navigation systems to make sure those same teams are never in doubt as to where they are in the first place.
Lieutenant (junior grade) Kyle Cregge is a U.S. Navy Surface Warfare Officer. He served on a destroyer and is a prospective Cruiser Division Officer. The views and opinions expressed are those of the author and do not necessarily state or reflect those of the United States Government or Department of Defense.
Featured Image: PHILIPPINE SEA (Sept. 3, 2016) Midshipman 2nd Class Benjamin Sam, a student at the U.S. Merchant Marine Academy, fixes the ship’s position using a sextant aboard the Arleigh Burke-class guided-missile destroyer USS Benfold (DDG 65). (U.S. Navy photo by Mass Communication Specialist 3rd Class Deven Leigh Ellis/Released)
In this two-part series on contested access in the Solomon Islands campaign, Part One will explore one of the IJN’s most successful weapons of World War II, which made area denial a reality for the IJN, the Type 93 ‘Long Lance’ torpedo. Part Two will compare the similarities of the Long Lance development to that of the DF-21D and discuss how the U.S. ultimately dealt with the Long Lance.
By Bob Poling
As I mentioned in my introductory post, the intent of this column is to explore the historical use of strategies, tactics, and technologies which fall under the broad definition of anti-access and area denial (A2/AD). One of the most common practices of a nation using A2/AD is the adoption of asymmetric tactics and associated weapons systems to mitigate an adversary’s advantages in numbers and technology.
However, it this column’s assertion that the U.S. Navy may lack an appreciation for these asymmetric threats. This is not due to a wanton disregard for A2/AD strategies and tactics, nor an unhealthy reliance on its weapons systems and technology. Instead, this lack of appreciation can be attributed to two factors. First, the U.S. Navy has not been truly challenged at sea since the end of the World War II. As such the Navy has produced several generations of naval officers that have no high-end combat experience. The second factor is a byproduct of the first. Since there has been no combat at sea for over 70 years, the Navy lacks case studies for training its current batch of officers. Therefore, this column will tap into the Navy’s combat history and offer historical examples that are arguably useful for contemporary and future challenges. For instance, the Solomon Islands Campaign is littered with examples of what today can easily be categorized as A2/AD strategies and tactics.
Contesting Access in the Solomon Islands
During the Solomon Islands Campaign, the Imperial Japanese Navy (IJN) employed a strategy based on anti-access, in which they aimed to keep out the U.S. and allied powers from the inner reaches of the Japanese Empire. To that end, Japan developed several platforms, weapons systems, and tactics which would facilitate this strategy. Moreover, in the years leading up to the start of WWII, the IJN faced a predicament like the one that drove the Chinese to develop the DF-21D anti-ship ballistic missile, that is, the challenge of how to deny freedom of access and maneuver to and ultimately defeat the U.S. Navy.
Type 93 torpedo, recovered from Point Cruz, Guadalcanal, on display outside U.S. Navy headquarters in Washington, D.C., during World War II.
One of the most sophisticated and deadly weapons of WWII was the Type 93 torpedo. This torpedo was the ship killer of that era. The asymmetric tactics developed for its use in combat were revolutionary. Much like the DF-21D, the Long Lance was in development for 20 years. Experimental work began in 1916, and by 1935, IJN weapons designers had produced a working 24-inch torpedo. “Long Lance was the most powerful weapon of its kind in the world as it was 29ft, 6.3 in long, weighed 5982 lbs, carried a warhead of 1080 lbs, and had a range of 21,900 yards at 48-50 knots, 35,000 yards at 40-42 knots or 43,700 yards at 36-38 knots.”1Granted, launches beyond 20 miles were unlikely, but the Type 93 gave the IJN a standoff weapon that could be launched outside of visual detection range, especially at night. Additionally, the Long Lance out-ranged the guns of all USN ships except battleships, making this a particularly effective long range anti-access weapon. Finally, the U.S. Navy had no effective countermeasures or defenses against this torpedo.
To optimize the capability and destructive power of the Long Lance, the IJN incorporated it into their night-fighting tactics. “The origin of the Japanese Navy’s tactic of stressing the night engagement was old; in both the Sino-Japanese and Russo-Japanese wars this tactic was used.”2It should have come as no surprise that the IJN continued to develop night-fighting tactics given their success in these two conflicts. However, the USN surface forces had an air of invincibility and arrogance about them and held the IJN in contempt.
This contempt was based on beliefs that the USN was technologically superior and more experienced, especially when compared to the IJN, which was only 70 years old.3 While USN battle tactics were still dominated by the pursuit of daytime gunnery engagements, and some U.S. Navy ships had radar, the IJN developed tactics to counter this practice mainly by the use of torpedoes coupled with guns fired in nighttime engagements. “Standard Japanese night-fighting doctrine was to launch torpedoes first, use gunfire only when necessary and searchlights as little as possible.”4 As the Long Lance was wakeless, it was nearly impossible to detect at night. The IJN counted on the USN to be taken unawares by this tactic and thus to be unlikely to maneuver. To facilitate this tactic and remain undetected, the Japanese’ primary method of detecting surface ships was the use of superb night optics. In fact, the IJN was constantly refining night optics during the interwar period and was regularly producing world-class optics in the 1930s. “Particularly noteworthy were binoculars of powerful magnification and light-gathering capacity, featuring lenses as large as 21 centimeters.”5 To use these binoculars, the IJN selected men to be trained as Masters in Lookout, and these petty officers trained day and night to hone their skills.6No other navy of the era had lookouts as highly trained as these. When combined with the night optics, these men were in fact a part of the Long Lance weapons system.
The U.S. Navy’s first encounter with the Long Lance was in the early morning of August 8, 1942 in Savo Sound off Guadalcanal. On the previous morning, the U.S. Navy had landed Marines on Guadalcanal and Tulagi as part of Operation Watchtower. Upon hearing the news of the invasion, Vice Admiral Gunichi Mikawa, Commander 8th Fleet, pulled together a force of seven cruisers and one destroyer and sailed for Guadalcanal that afternoon.
Arrayed against Mikawa were six heavy cruisers, two light cruisers, and eight destroyers, which were divided into three groups. Of the eight U.S. destroyers, two were assigned radar picket duties patrolling both the western and eastern approaches to Savo Sound, but Mikawa’s striking force remained undetected. According to IJN accounts both radar pickets were detected visually at 10,000 meters by the IJN cruiser Chokai. However, neither Blue nor Ralph Talbot made radar contact even though Mikawa’s ships were only a little over five miles away.7Once clear of the picket, Mikawa gave the order to attack. The IJN achieved complete surprise, and its use of an A2 weapon coupled with asymmetric tactics had devastating results on the USN and RAN. As RADM Crutchley wrote,
“The result of the night actions fought during the night 8th-9th August proved costly. Four of our heavy cruisers – Vincennes, Quincy, Astoria and Canberra had been lost. Another heavy cruiser Chicago had been damaged and required dockyard repair. Two destroyers had been damaged, Ralph Talbot fairly heavily and Patterson not seriously.8
During the engagement, IJN cruisers Chokai, Aoba, Kako, Kinugasa and Furrutaka fired 45 Type 93 torpedoes.9 Of the four USN cruisers participating in the battle, Quincy and Vincennes were sunk due to damage caused by Long Lance torpedo hits and Chicago had her bow blown off by a Long Lance, which immediately took her out of the fight.10 The other two cruisers lost in the battle, Astoria and Canberra, both were sunk due to damage inflicted by naval gunfire from the IJN cruisers.11
The Japanese heavy cruiser Chokai, which led the IJN attack at Savo Island. The recessed torpedo tubes are clearly visible under the whaleboat and second stack.
Two things stand out here as noteworthy anti-access tactics. First, part of an area defense strategy will likely include forward-based forces that can rapidly respond to an incursion and immediately conduct active defensive operations. In this case, it was Mikawa’s eight ships which caught the U.S. Navy completely unawares even though this operation was being conducted inside the IJN’s defensive sphere. The second A2 tactic was the night attack using a long-range, undetectable weapon. Much of today’s angst regarding A2 systems assumes the very same thing. Once the defenders realized they were under attack, it was entirely too late to respond and because of the nature of the Long Lance, it remained undetectable. The element of surprise was made all the more decisive by the effective use of a powerful anti-access weapon.
Conclusion
A2 tactics are nothing new, and today’s Navy is aware of what those tactics may entail and which potential adversaries embrace these tactics today. Back in the Solomons, the USN’s troubles with the Long Lance would continue well into 1943. Ultimately, the Navy learned to adapt its tactics, techniques, and procedures (TTPs) to mitigate the threat posed by the Long Lance. However, what is important in this example is that no active counter measure was developed. Instead there was a realization that the threat was not going away, and a significant amount of risk was going to be present while conducting operations in the waters of the Solomon Islands. Acceptance of significant risk is an important part of defeating an adversary that aligns its strategy and tactics with A2/AD. Part Two will explore this aspect as well and how the Navy ultimate dealt with the Long Lance threat.
Bob Poling is a retired Surface Warfare Officer who spent 24 years on active duty including tours in cruisers, destroyers and as commanding officer of Maritime Expeditionary Security Squadron TWO and Mission Commander of Southern Partnership Station 2013. From May 2011 to May 2015, Bob served on the faculty of the Air War College teaching in the Departments of Strategy and Warfighting. He was the Naval History and Heritage Command 2014-2015 Samuel Eliot Morison scholar and is pursuing his Ph.D. with the Department of Defence Studies, King’s College London where he is researching Air-Sea Battle concepts used to combat A2/AD challenges encountered during the Solomon Islands Campaign.
References
1. John Bullen, “The Japanese Long Lance Torpedo and Its Place in Naval History,” Imperial War Museum Review 3 (1988): 69–79.
2. ‘Development of the Japanese Navy’s Operational Concept against America’, Jisaburo Ozawa in Dillon and Goldstein, The Pacific War Papers, (Washington D.C., Potomac Books Inc., 2005), 74.
3.David C. Evans and Mark R. Peattie, Kaigun: Strategy, Tactics, and Technology in the Imperial Japanese Navy, 1887-1941, Reprint edition (Annapolis, Md.: Naval Institute Press, 2012), 7.
4. Bullen, 69–79.
5. Evans and Peattie, 275.
6. Bruce Loxton and Chris Coulthard-Clark, The Shame of Savo: Anatomy of a Naval Disaster, 1st edition (Annapolis, Md: Naval Institute Press, 1994), 43.
7. Captain Toshikazu Ohmae, IJN Ret., “The Battle of Savo Island,” U.S. Naval Institute Proceedings 83, no. 12 (December 1957): 1263–78.
8. RADM Victor Crutchley, “Solomons ‘Watchtower’ OPS. Guadalcanal – Tulagi. Admiral Crutchley Report T.G. 66.6 Screening Force,” August 13, 1942, National Archives of Australia: B6121, 105A.
9. Eric LaCroix, Linton Wells, and Linton Wells II, Japanese Cruisers of the Pacific War, 1St Edition,(Annapolis, Md: US Naval Institute Press, 1997), 306.
10. Bureau of Ships, “USS QUINCY (CA39), USS ASTORIS (CA34), USS VINCENNES (CA44) LOSS IN ACTION BATTLE OF SAVO ISLAND 9 AUGUST 1942,” War Damage Report (Navy Department, June 21, 1943), The Navy Department Library, http://www.history.navy.mil/research/library/online-reading-room/title-list-alphabetically/w/war-damage-reports/uss-quincy-ca39-astoria-ca34-vincennes-ca44-war-damage-report-no29.html, 21; Office of Naval Intelligence, “Solomon Islands Campaign II The Battle of Savo Island 9 August 1942 The Battle of the Eastern Solomons 23-25 August 1942,” Combat Narratives (Washington, D.C.: U.S. Navy, October 1, 1943), The Navy Department Library, http://www.history.navy.mil/research/library/online-reading-room/title-list-alphabetically/s/solomon-islands-campaign-ii-savoisland-III-easternsolomons.html., 10.
11. Bureau of Ships, “USS QUINCY (CA39), USS ASTORIA (CA34), USS VINCENNES (CA44) LOSS IN ACTION BATTLE OF SAVO ISLAND 9 AUGUST 1942”; RADM Victor Crutchley, “Report of Proceedings Operation – ‘Watchtower,’” August 18, 1942, National Archives of Australia: B6121, 105A.
Featured Image: IJN DD Isokaze at Saeki Bay, October 20, 1941. Colorized by Lootoko Jr.
CNO Admiral John Richardson recently struck the term A2/AD from Navy lexicon. The debate that follows aims to ascertain the value of the term and understand the context of the CNO’s decision. Bob Poling takes the affirmative position that A2/AD is still a relevant term while Jon Askonas takes the negative.
Affirmative: Dear CNO, A2/AD Still Matters…
By Bob Poling
CNO Richardson speaks at CSIS (CSIS)
On October 3, 2016, while participating in a Maritime Security Dialogue at the Center for Strategic and International Studies (CSIS), Chief of Naval Operations Admiral John Richardson announced that the Navy would strike A2/AD from its vocabulary. Admiral Richardson stated, “To some, A2/AD is a code-word, suggesting an impenetrable ‘keep-out zone’ that forces can enter only at extreme peril to themselves. To others, A2/AD refers to a family of technologies. To still others, a strategy. In sum, A2/AD is a term bandied about freely, with no precise definition, that sends a variety of vague or conflicting signals, depending on the context in which it is either transmitted or received.” Richardson went on to say, “To ensure clarity in our thinking and precision in our communications, the Navy will avoid using the term A2/AD as a stand-alone acronym that can mean many things to different people or almost anything to anyone.”
But A2/AD is not just Navy terminology. The acronym is used in any number of joint publications and is recognized as a part of joint doctrine. After all, there is perhaps no topic more “joint” than the study of countering A2/AD, and as such, the Navy should continue to use the same terminology being used by the rest of the services instead of abandoning doctrine.
In Line with Naval Tradition
With his prohibition on A2/AD, CNO has upheld the Navy’s reputation for ignoring doctrine. It is no secret that naval officers rail against doctrine and adhere to it grudgingly. Corbett warned naval strategists to not become enamored with maxims when studying war as it stifles good judgment. Roger W. Barnett in his book on the Navy’s strategic culture provides an accurate description of this anathema noting, “Navy strategists look upon written doctrine as maxims and are wholly uncomfortable with it. To the naval strategist, the combination of definitions and doctrine becomes rather toxic.” Admiral Richardson exemplifies Barnett’s views and if one watches the video of his remarks at CSIS, his disdain for A2/AD is clear. But A2/AD is not just jargon. It is a viable term that if used in the proper context can convey the fidelity CNO is looking for. Moreover, it is a term that the joint force is familiar with and continues to use. Admiral Richardson’s ban on A2/AD has in essence forced the Navy to turn its back on prescribed joint doctrine and terminology
Granted, blind adherence to doctrine is not necessarily a good thing. However, in this case adherence to the terminology laid forth in doctrine is useful, especially since all of the services are so vested in counter A2/AD. In Chapter One of Joint Publication One (JP-1), former Chief of Staff of the U.S. Army, General George H. Decker’s stated, “Doctrine provides a military organization with a common philosophy, a common language, a common purpose and a utility of effort.” The Department of Defense’s position on doctrine is clearly articulated in subsequent paragraphs declaring, “the use of joint doctrine standardizes terminology, training, relationships, responsibilities and processes among all of the U.S. forces to free the joint force commanders (JFCs) and their staffs to focus on solving strategic, operational, and tactical problems.” Finally, Naval Doctrine Publication 1, Naval Warfare defines doctrine thus, “Doctrine is not an impediment to a commander’s exercise of imagination; rather, it is a framework of fundamental principles, practices, techniques, procedures, and terms that guides a commander, commanding officer, or officer-in-charge in employing force(s) to accomplish the mission. Doctrine provides the basis for mutual understanding within and among the Services and national policy makers. It ensures familiarity and efficiency in the execution of procedures and tactics.” Based on these definitions alone, including the Navy’s cut on doctrine, Admiral Richardson’s comments clearly contradict the expectations articulated for the joint force. Instead of fostering unity of effort and a common approach to A2/AD, CNO’s edict has the potential to drive a wedge between the Navy and the other services.
Need for Inter-Forces Cooperation
Another problem with CNO Richardson’s proclamation is it contradicts the Joint Operational Access Concept (JOAC), 1.0which guides the joint force on how to approach A2/AD. “The JOAC describes in broad terms how joint forces will operate in response to emerging anti-access and area-denial security challenges” and, “… envisions a greater degree of integration across domains and at lower echelons than ever before.” Likewise, the JOAC defines anti-access (A2) and area-denial (AD) for the joint force as follows, “Anti-access refers to those actions and capabilities, usually long-range, designed to prevent an opposing force from entering an operational area. Anti-access actions tend to target forces approaching by air and sea predominantly, but also can target the cyber, space, and other forces that support them. Area-denial refers to those actions and capabilities, usually of shorter range, designed not to keep an opposing force out, but to limit its freedom of action within the operational area. Area-denial capabilities target forces in all domains, including land forces.”
Granted these definitions may not be as concise as CNO may like, but they are the accepted joint definitions, and they do cover the spectrum of potential threats. As these definitions are not suitable for CNO then why not approach the A2/AD conundrum in the same fashion as the Navy approaches warfare? For example, the Navy’s approach to Air Defense is just as convoluted as CNO suggests A2/AD is. The Air and Missile Defense Commander (AMDC) is responsible for defending the force against air threats. But air threats can be a variety of things like ballistic missiles, aircraft and anti-ship cruise missiles (ASCM); all of which must be dealt with in a different fashion based on each one’s ranges and capabilities. To manage the variety of threats the AMDC publishes an OPTASK Air Defense plan which provides specific guidance that has been tailored based on the area of operations and the threats that are present, thus leveling the playing field and ensuring all the players are on the same page. The point is, this methodology represents how the Navy has successfully operated for decades. The inherent flexibility of this approach to warfare allows the Navy to adapt to ever changing environments and threats, regardless of the region. It should be no different where A2/AD is concerned.
Conclusion
Admiral Richardson’s decision to strike A2/AD from the Navy’s lexicon only sends conflicting signals to the rest of the Joint Force, our allies, and partners. On the surface, it looks as if the Navy is no longer a team player where A2/AD is concerned. Still, others are no doubt wondering why CNO has done this when none of the other services have gone this route. Arguably, the elimination of A2/AD from the Navy’s vocabulary is more likely to undermine the clarity of thinking and precise communication CNO desires. If I could whisper in CNO’s ear, I would recommend he demand more rigorous thinking and adherence to the JOAC’s vision of A2/AD instead of throwing out the term.
Negative: A2/AD is an Unoriginal and Unhelpful Term In Understanding Threats
By Jonathan D. Askonas
A2/AD, for the uninitiated, stands for “Anti-Access/Area Denial,” shorthand for a variety of technological and tactical changes supposedly creating new and unique military challenges for the United States to confront. What makes doctrinal language useful? It provides a name and set of concepts that help us think about a phenomenon in order to improve military performance. My contention is that A2/AD conceals and obscures more than it clarifies and is thus not useful doctrinal language.
What is an “Anti-Access/Area Denial” military system? In normal use, A2/AD refers to technologies and tactics which, through precision guidance, communications, and firepower, make the deployment and use of American forces riskier and more expensive. Which is to say, they are military systems. One of the beauties of A2/AD is that anything short of tactical scenarios the U.S. military is itching to engage (like a rerun of the 1991 Iraqi Turkey Shoot) becomes “A2/AD.” Anti-ship ballistic missiles (ASBMs)? A2/AD. Small, swarm-tactic Iranian littoral boats? A2/AD. Integrated air defense systems (IADSs)? A2/AD. Diesel attack subs? A2/AD. Any modern military technology that enables a great power to project force past its own borders in ways which even marginally threaten the West’s ability to conduct combined arms operations can be subsumed in a sexy operational concept. But this overbroad idea has at least three fatal problems which doom it to the conceptual dustbin.
A2/AD Deceives Us Into Confusing the Tactical, Operational, and Strategic Levels of Warfare
While their role in an A2/AD strategy is up for a debate, substantial Chinese investment in new technologies, like this Type 039 Song Class diesel-electric submarine, is undeniable. (PRC Stock Photo)
The biggest problem with A2/AD is that it carelessly elides the distinguishing levels of war, smuggling all kinds of assumptions and non sequiturs into our thinking. When most people talk about A2/AD, they refer to technological capabilities which are capable of attacking/hampering Western capabilities (tactical) in ways which increase the risk of the West acting in specific areas (operational), to the end of limiting Western influence (strategic). But reality almost never lines up with this picture, even in the canonical examples of A2/AD. Take the South China Sea, where Chinese investment in ASBMs, diesel attack subs, and other hardware are supposedly part of a strategy of A2/AD designed to minimize American ability to intervene in the region. And yet, this picture falls apart on closer inspection. At the technological level, complex kill-chains create all kinds of vulnerabilities in China’s new (and relatively untested) weapons systems which, when it comes to operational considerations, render them unreliable, particularly as American forces adapt to them (the traditional response to operating in “denied” territory). And at the strategic level, A2/AD as a strategy is absurd. War is politics by other means – how are extra missiles by themselves supposed to force American carrier battle groups not to enforce freedom of the seas? China has not attempted to sink them in the past not because it lacked the capability but because it lacked the will. The ultimate anti-missile defense system is threat of unstoppable violence should the American people be attacked. A2/AD’s conceptual confusion about how technologies, tactics, operations and strategy interrelate undermines any utility the idea might have.
A2/AD Lends Itself To An Overly Cautious, Defensive, and Unhistorical Mindset
As the CNO himself pointed out, A2/AD encourages a cautious, defensive, and unhistorical mindset. To the first point, A2/AD, with its language of “area denial” lends itself to being construed as defensive in nature. For example, “A2AD capability is not offensive or aggressive in nature,”French General Denis Mercier and NATO supreme allied commander for transformation said last October. “It’s principally a defensive measure. So we have to consider it, we have to be aware of it, we have to include it in our planning but it’s not the threat as such.” Because it elides the levels of warfare, A2/AD transforms the defensive capabilities of the weapon (tactical) into a defensive intent on behalf of the enemy (strategic). And yet, as even the most greenhorn strategist knows, because warfare is a competitive activity, changes in relative advantage determine outcomes and shape the overall operational picture, regardless of whether the weapons themselves are offensive or defensive in nature. Moreover, in many cases, the weapon systems in question are not obviously solely defensive in nature, nor only capable of targeting American forces.
To the second point, that A2/AD is anachronistic, it seems peculiar that a concept as old as warfare has been highlighted as the next big new defense threat. The ability to make certain areas of the battlespace difficult or impossible for the enemy to access, thus shaping his choices, is one of the foundational mechanics of warfare. Conceptually, minefields, coastal defense guns, and U-Boats had (or sometimes had) identical functions to contemporary “A2/AD” weaponry. Because it highlights new technologies of area denial, A2/AD hampers rather than helps our ability to use military history and analogical thinking to come up with creative solutions to contemporary military challenges.
A2/AD traps Us Into a Rigid Conception of the Enemy and the Enemy’s Strategy
By fogging up the distinguishing levels of war and highlighting the ways great power rivals are working to defend against U.S. intervention, A2/AD lulls us into projecting our operational challenges onto the intentions of our enemies. In other words, A2/AD tricks us into thinking that, because it is the case that widespread ASBM deployment in the East China Sea or IADSs over Syria increase the relative risk of an American intervention, those actions were taken for that purpose. By tying an operational fact (ASBMs are a threat to American ships) to a strategic assumption (therefore, ASBMs are primarily intended to deny access to American ships), A2/AD hurts our ability to imagine what else the enemy might be up to. The same missiles which can sink an American carrier can also hold Taiwanese naval forces at risk; the same IADS that limits American intervention in Crimea can also target actively target Lithuanian or Estonian fastmovers. I don’t mean to suggest that these are likely possibilities, but they are possibilities, and ones which A2/AD belays. The problem is that the enemy gets a say, too. Just because we have an operational concept which says that Chinese investment in a blue water navy or Russian research into advanced air-to-air missiles are primarily aimed at limiting U.S. influence does not make it so. And, even if this is true today, there is nothing to suggest that the enemy might change his mind. By incorporating assumptions about enemy intent into its model, A2/AD lulls us into thinking we understand the enemy.
Conclusion
At the end of the day, A2/AD furthers a strategic culture that obsesses over the “next big thing” and neglects the fundamentals. To the extent that A2/AD is correct about the need to incorporate standoff weaponry into our tactical calculations, it is trivial; that is a well-understood part of operational art. And to the extent that A2/AD makes non-trivial claims about the enemy’s strategy or intent (or the nature of warfare), it is dangerously blithe, imprecise, and blinkered. Like the Revolution in Military Affairs, Full Spectrum Warfare, and NetWar before it, A2/AD will soon join the graveyard of Pentagon intellectual fads that preceded it. And well it should.
Bob Poling is a retired Surface Warfare Officer who spent 24 years on active duty including tours in cruisers, destroyers and as commanding officer of Maritime Expeditionary Security Squadron TWO and Mission Commander of Southern Partnership Station 2013. From May 2011 to May 2015 Bob served on the faculty of the Air War College teaching in the Departments of Strategy and Warfighting. He was the Naval History and Heritage Command 2014-2015 Samuel Eliot Morison scholar and is pursuing his Ph.D. with the Department of Defence Studies, King’s College London where he is researching Air-Sea Battle concepts used to combat A2/AD challenges encountered during the Solomon Islands Campaign.
Jon Askonas is a 2nd year DPhil candidate in International Relations at the University of Oxford, where he is a Beinecke Scholar and a Healy Scholar. He is interested in the relationship between knowledge production/transmission and decision-making in large organizations. He has a BS in International Politics (summa cum laude) from Georgetown University and a MPhil(Merit) from Oxford. He has worked at the Council on Foreign Relations and the US Embassy in Moscow.
The opinions and assertions contained herein are the private opinions of the authors and are not to be construed as official or reflecting the views of the Department of Defense, the United States Government, or the United States Navy, or any organization – they are the authors’ personal opinions.
Featured Image: U.S. Navy guided missile cruiser USS Princeton. U.S. Navy Photo by Mass Communication Specialist Seaman Jake Berenguer (Released)
To better meet today’s force demands, [we must] explore alternate fleet designs, including kinetic and non-kinetic payloads and both manned and unmanned systems. This effort will include exploring new naval platforms and formations – again in a highly “informationalized” environment – to meet combatant commander needs.
– Admiral John RichardsoninA Design for Maintaining Maritime Superiority
Today’s military operating environment is more complex than ever. While the principles of warfare have remained relatively unchanged throughout history, the development of advanced military capabilities and employment of unconventional styles of warfare increasingly challenge the way commanders are thinking about future conflict. Potential adversaries are further complicating the operating environment through various anti-access/area denial (A2/AD) mechanisms. While many countries are developing such capabilities, this article will focus primarily on the threat of the People’s Republic of China (PRC’s) maritime development. The PRC is rapidly improving its air, surface, and subsurface platform production as it continues its quest for exclusive control of untapped natural resources within the “nine-dash line” region.1 Additionally, the PRC is equipping these platforms with improved weapons that can reach further and cause more damage.2 As a result, the U.S. Navy will assume greater risk when operating in complex A2/AD environments such as the Western Pacific. To mitigate this risk, the U.S. Navy is developing innovative warfighting concepts that leverage technologies and assets available today. The incorporation of unmanned systems into maritime domain operations provides one example where the U.S. Navy is making significant progress. Another example is the inception of a new surface warfighting concept called Distributed Lethality.
In January 2015, Vice Admiral Thomas Rowden (Commander U.S. Naval Surface Forces) and other members of the surface warfare community’s higher leadership formally introduced the opening argument for how the Surface Navy plans to mitigate the A2/AD challenge in an article titled “Distributed Lethality.”3 In this inaugural piece, the authors argue, “Sea control is the necessary precondition for virtually everything else the Navy does, and its provision can no longer be assumed.”4 The “everything else” corresponds to promoting our national interests abroad, deterring aggression, and winning our nation’s wars.5 At its core, Distributed Lethality (DL) is about making a paradigm shift from a defensive mindset towards a more offensive one. To enable DL, the U.S. Navy will increase the destructive capability of its surface forces and employ them in a more distributed fashion across a given theater of operation.
DL shows promise in executing the initiatives provided in the Chief of Naval Operations’ Design for Maintaining Maritime Superiority in the years to come.6 However, as the U.S. Navy continues to invest in promoting DL, there is a danger that improper fusion of this new operating construct with the foundational principles of war could lead to a suboptimal DL outcome.7 To optimize the combat potential inherent to DLin an A2/AD environment, the Navy must develop and apply the concept of “Autonomous Warfare.” Autonomous Warfare addresses both enabling decentralized, autonomous action at the tactical level through carefulcommand and control (C2) selection at the operational level and further incorporating unmanned systemsinto the Navy’s maritime operating construct. A flexible C2 structure enabling autonomous action supported by squadrons of unmanned systems optimizes DL and ensures its forces will deliver the effects envisioned by this exciting new concept in the most challenging A2/AD environments. DL advocates put it best in saying that “we will have to become more comfortable with autonomous operations across vast distances.”8 This paper will first examine why DL is an appropriate strategy for countering A2/AD threats before developing the main argument for Autonomous Warfare. This paper concludes by examining how the combined effect of autonomous C2 and aggressive implementation of unmanned systems will achieve the desired results for Autonomous Warfare as it applies to DL, followed by a series of recommendations that will assist with implementing this new idea.
Why Distributed Lethality?
“Naval forces operate forward to shape the security environment, signal U.S. resolve, protect U.S. interests, and promote global prosperity by defending freedom of navigation in the maritime commons.”9 During war, one of the Navy’s principal functions is to gain and maintain sea control to facilitate air and ground operations ashore. An adversary’s ability to execute sea denial makes the endeavor of exercising sea control increasingly challenging. A key driver behind DL is countering advances in A2/AD capability, a specific sea denial mechanism, which inhibits the Navy’s capacity to operate in a specific maritime area.10
A2/AD is a two-part apparatus. Anti-access attempts to preclude the entrance of naval forces into a particular theater of operation. For example, the threat and/or use of anti-ship cruise and ballistic missiles can hold surface vessels at risk from extended ranges.11 The PRC’s People’s Liberation Army Navy (PLAN) is one of the many navies that deploy various anti-ship cruise missiles (ASCMs), out of a global arsenal of over 100 varieties that can reach nearly 185 miles.12 Of its anti-ship ballistic missiles (ASBMs), the PRC’s renowned “carrier killer” (DF-21D), with a range of 1000 plus miles, is generating cause for concern from an anti-access perspective.13 Additionally, submarines operating undetected throughout a given area of operation (AO) can deter surface forces from entering that area without significant anti-submarine warfare (ASW) capability. On the other hand, area denial seeks to prevent an adversary’s ability to maneuver unimpeded once a vessel has gained access to an area.14 While employment of the aforementioned missiles poses a threat in a combined A2/AD capacity, the PRC’s shipbuilding trend is triggering additional alarms from an area denial perspective. A recent workshop facilitated by the Naval War College’s China Maritime Studies Institute (CMSI) highlighted that the PRC has surged its shipbuilding efforts more than ten times over from 2002 to 2012 and will likely become the “second largest Navy in the world by 2020” if production continues at this pace.15 Indeed, the PRC has generated and continues to produce significant capacity to practice A2/AD and maintains a formidable shipbuilding capability. These observations are just a few amongst a host of many that spark interest in shifting American surface forces toward a DL-focused mindset.
One might ask, “How does DL help mitigate these A2/AD concerns?” Ever since carrier operations proved their might in the Pacific theater during World War II, U.S. naval surface combatants have principally acted in defense of the aircraft carrier. Essentially, the surface force relies predominantly on the firepower wrought by the carrier air wing, while other surface ships remain relatively concentrated around the carrier and defend it against enemy threats from the air, surface, and sub-surface. A well-developed A2/AD operational concept married with a diverse and sophisticated array of systems is advantageous against this model for two reasons: that adversary could hold a limited number of high value units (the carriers) at risk with only a small number of ASBMs, while the imposing navy could only employ a fraction of its offensive capability due to a necessary focus on defensive measures. DL addresses both concerns by deploying progressively lethal “hunter-killer” surface action groups (SAGs – more recently referred to as Adaptive Force Packages) in a distributed fashion across an area of operation (AO). By doing so, the DL navy will provide a more challenging targeting problem while offering the commander additional offensive options.16 DL shifts the focus of the Navy’s offensive arsenal from its limited number of aircraft carriers to the surface navy as a whole.
Potential Shortcomings
DL addresses the challenges of operating in an A2/AD environment by dispersing offensively focused surface combatants across the theater. To be effective, however, the operational commander must assign an appropriate C2 structure for DL forces. The DL operating concept could rapidly dissolve through the development and implementation of complex command and control structures. Furthermore, inadequate use of unmanned systems presents an additional potential shortcoming to the effective application of DL. While the consequences of these shortcomings would not be cause for instantaneous failure, they could create adverse second and third order effects and result in deterioration of the DL concept.
Command and Control
Effective C2 is the cornerstone of the successful execution of any military operation. Service doctrine aids in establishing the proper balance between centralized and decentralized C2. The Naval Doctrine Publication 1 for Naval Warfare defines C2 as “the exercise of authority and direction by a properly designated commander over assigned and attached forces in the accomplishment of the mission.”17 Further, the Joint Publication for C2 and Joint Maritime Operations highlights that a clear understanding of commander’s intent should enable decentralized execution under the auspices of centralized planning.18 Instituting the appropriate C2 structure based on the mission at hand and composition of employed forces helps achieve maximum combat utility while minimizing the need to communicate. This is particularly important when the operational commander has cognizance over a large number of forces and/or when the enemy has degraded or denied the ability to communicate. As the absence of a notional C2 architecture for Adaptive Force Packages (AFPs) at the operational level represents a significant gap in the DL concept, this paper will provide a traditional Composite Warfare Commander (CWC) approach to commanding and controlling AFPs, followed by a potential solution through the lens of Autonomous Warfare.19 The intent is to show that thinking about AFPs as autonomous units will uncover innovative ways to assign C2 functions and responsibilities amongst DL forces.
Unmanned Systems
The proper employment of unmanned systems will prove equally critical in developing the design for Autonomous Warfare as it relates to DL.20 Increasing the offensive capability of smaller groups of warships is one of DL’s main functions (if not the main function). A key enabler to this is the ability to provide ISR-T in a manner that reduces risk to the organic vessels. The concern is that targeting requires the ability to detect, track, and classify enemy vehicles – which oftentimes requires emission of electronic signals that will alert the enemy. Unmanned systems have the ability to provide ISR-T while reducing the risk for organic vessels to reveal their location. Autonomous Warfare will leverage the use of unmanned systems in all three maritime domains (air, surface, and sub-surface). Anything less would unnecessarily limit the potential for delivering maximum offensive firepower while minimizing risk to the organic platforms. Furthermore, critics should note that the U.S. Navy’s adversaries are making similar advances in unmanned systems.21 The bottom line is that underutilization of unmanned systems will be detrimental to DL. The effectiveness of DL as an operational concept depends on the effective employment of unmanned systems.
Providing A Frame of Reference
The following hypothetical situation offers a frame of reference for the remainder of the Autonomous Warfare argument.22 The goal is to show that Autonomous Warfare will optimize DL employment in a scenario where multiple BLUE AFPs must operate in the same AO against multiple RED force SAGs and other RED forces.23
Figure One: A notional scenario for DL24
The area depicted in Figure 1represents the AO for the given scenario. Country GREY is an abandoned island and has an airfield that BLUE forces want to capture to facilitate follow-on operations against RED. The Joint Force Maritime Component Commander (JFMCC) receives the task of capturing the airfield. As such, he establishes two objectives for his forces: establish sea control on the eastern side of the island (indicated in yellow) to support an amphibious landing in preparation for seizing the airfield, and establish sea denial on the western side of the island (indicated in orange) to prevent RED from achieving the same.
BLUE’s Order of Battle (OOB) consists of one carrier strike group (CSG), one expeditionary strike group (ESG), and three AFPs. Each AFP is comprised of an ASW capable Littoral Combat Ship (LCS), a Flight III Arleigh Burke-class destroyer, and a Zumwalt-class destroyer. Together, each AFP is capable of the full range of offensive and defensive measures needed to defeat enemy targets in each of the three maritime domains.25 RED’s OOB consists of one CSG, three SAGs, and two diesel-electric submarines. RED has a more difficult targeting problem than if BLUE elected to concentrate its forces, since BLUE distributed them across the AO utilizing multiple AFPs capable of delivering offensive firepower in all three traditional warfare domains. How then should BLUE best establish its C2 structure? Will that C2 structure continue to function while operating under emissions control (EMCON) and in the event RED is able to degrade or deny BLUE communications? What roles should unmanned systems play in optimizing ISR-T while minimizing risk to the organic platforms? By developing and applying the concepts of Autonomous Warfare, BLUE will operate with a C2 construct that enables more autonomous action at the lower levels. Additionally, BLUE will leverage the use of unmanned systems, relieving the stress of ambiguity in a communications denied environment.
A Traditional Approach for Applying the CWC Concept to DL
One could argue that AFPs operating under the DL construct should follow a traditional CWC C2 structure, which provides a counter-argument for the Autonomous Warfare approach. The CWC concept attempts to achieve decentralized execution and is defensively oriented. The composite warfare commanders direct the various units of a task force on a warfare-specific basis.26 By delegating oversight of each warfare area to lower levels, the command structure avoids creating a choke point at the task force commander level (the CWC). This configuration is “structurally sound – if not brilliant” for its inherent capacity to simplify the offensive and defensive aspects of maritime warfare down to each warfare area.27 AFPs employed in the scenario described above would then operate under the cognizance of the different warfare commanders on a warfare-area basis. These AFPs are simply groups of disaggregated forces forming a distributed network that would otherwise maneuver as a concentrated assembly around the carrier.
Figure 2: Traditional CWC Operational C2 Structure for a DL Task Force
Putting the given scenario into action and using the C2 structure depicted in Figure 2, to what degree are the APFs enabled to achieve the given objectives? BLUE AFPs are stationed as shown in Figure 1 and will attack any RED forces attempting to contest BLUE’s sea control in the yellow box. BLUE also has a continuously operating defensive combat air (DCA) patrol stationed west of the sea denial box to prevent any RED advancements towards island GREY. Just as BLUE forces get into position, RED attempts to form a blockade of the island by sending two SAGs, each escorted by a submarine, around the north and south ends of the island. The first indication of a RED attack comes from a synchronized ASCM salvo from unidentified targets (they were fired from RED’s submarines) followed by radar contact on the RED SAGs from BLUE UAVs providing ISR-T. BLUE’s distributed AFPs, fully enabled by commander’s intent, are capable of self-defense and defeating the RED forces.
Close coordination with the warfare commanders is not required. Each AFP commander understands that in order to maintain sea control to the east, he must dominate in the air, sub-surface, and on the surface. The CWC remains informed as the situation develops and the warfare commanders provide additional guidance for regrouping following the destruction of enemy threats. Thus, a traditional CWC approach to commanding and controlling AFPs provides the opportunity for centralized planning with decentralized execution with respect to DL. Further efforts to decouple the C2 of the AFPs from the task force as a whole could jeopardize unity of effort amidst a complex maritime contingency. AFPs should not be totally self-governing since “uncontrolled decentralized decision-making is just as likely to result in chaos on the battlefield” as no command and control at all.28
An Autonomous Warfare Approach for DL Command and Control
The traditional CWC approach for DL C2 works in this case only because the given scenario is relatively simple. Uncertainty and adversity (often times referred to as fog and friction) are problems that commanders will enduringly have to overcome in wartime. “A commander can no more know the position, condition, strength, and intentions of all enemy units than the scientist can pinpoint the exact location, speed, and direction of movement of subatomic particles.”29 The best he can do is generate an estimate of the situation based on the information available. In the previous scenario, RED’s COA was generic; BLUE should anticipate this type of COA to a degree, relative to RED’s overall plan of attack. Replaying the scenario with two slight yet profound modifications will show that we should not think of the traditional CWC C2 concept as a universal solution. An Autonomous Warfare approach will simplify managing the fog and friction of war from an operational C2 perspective and maximize AFP combat potential.
Assume the forces available and assigned objectives on each side are unchanged. In this case, RED brings to bear more of its A2/AD capabilities, including jamming BLUE’s communications network. Additionally, RED has sufficient ISR capabilities to determine the location and composition of BLUE’s AFPs. As a result, RED concentrates its forces to the north in an attempt to annihilate BLUE’s AFPs in series. The AFP to the north is now overwhelmingly outmatched. Similar to the previous scenario, BLUE’s first indication of a RED attack is a salvo of ASCMs fired from RED’s submarines. As a result, the LCS is damaged to the extent that it provides no warfare utility. Because communications are jammed, the remaining AFP forces cannot communicate with the CWC and his warfare commanders on the carrier to receive guidance on how to proceed. How does the affected AFP protect itself with the loss of its primary ASW platform? Does the traditional C2 structure allow the affected AFP to coordinate directly with the adjacent AFP for re-aggregation? Collectively, the remaining AFPs still offer the commander adequate capability to thwart the RED attack. This is not to say that Autonomous Warfare completely nullifies the principles of the CWC concept. Autonomous Warfare simply optimizes the principles behind the CWC concept for DL.30
The following is an analysis of how an Autonomous Warfare approach to C2 for AFPs optimizes the combat potential that DL offers – especially in an A2/AD environment. A notional Autonomous Warfare DL C2 structure is provided in Figure 3. Each AFP would have an assigned AFP commander and designated alternate. Tactical decision-making would occur at the AFP level. Communications requirements would be drastically reduced. The delegated C2 structure obviates the need for dislocated command and control – AFPs under the auspices of the CSG. Thus, the “search-to-kill decision cycle” is completely self-contained.31 This degree of autonomy avoids the particular disadvantages of centralized command indicated in the previous example. Autonomous Warfare enables the AFP commander to make best use of his available forces based on the tactical situation and in pursuit of the assigned objectives. Furthermore, Autonomous Warfare prioritizes local decision-making founded on training, trust, mission command, and initiative rather than top-down network-centric command and control.32
Figure 3: Autonomous Warfare C2 Structure for a DL Task Force
There is an additional significant advantage to having a more autonomous C2 structure. Although the operational commander could assign each AFP a geographic area of responsibility, they could combine forces and disagreggate as necessary in the event of a loss or an encounter with concentrated enemy forces. In the second scenario above, two AFPs could coordinate directly with each other to counter the larger enemy compliment. They could avert the challenges and ambiguity of reaching back to the centralized commanders altogether as long as they maintained accountability for their assigned areas of responsibility. In the case where the LCS was eliminated, the AFP commanders should have the autonomy to adapt at the scene to accomplish the objective without seeking approval for a seemingly obvious response to adversity.
Another reason why a more flexible, autonomous C2 structure is imperative for DL forces is that there is no “one-size-fits-all” AFP.33 The operational commander may assign different combinations of platforms based on the assets available and the given objectives. The harsh reality of war is that ships sink. The doctrine in place must allow for rapid adaptation with minimal need to communicate to higher authority. The Current Tactical Orders and Doctrine for U.S. Pacific Fleet (PAC-10) during World War II captures this notion best: “The ultimate aim [of PAC-10 was] to obtain essential uniformity without unacceptable sacrifice of flexibility. It must be possible for forces composed of diverse types, and indoctrinated under different task force commanders, to join at sea on short notice for concerted action against the enemy without interchanging a mass of special instructions.”34
Optimizing DL with Unmanned Systems
The aggressive employment of unmanned systems is the second feature of Autonomous Warfare through which the U.S. Navy should optimize DL. “It is crucial that we have a strategic framework in which unmanned vehicles are not merely pieces of hardware or sensors sent off-board, but actual providers of information feeding a network that enhances situational awareness and facilitates precise force application.”35 While there are many applications for unmanned systems, Autonomous Warfare exploits the information gathering and dissemination aspects to increase the lethality of organic platforms. By enhancing the capacity to provide localized and stealthier ISR-T using unmanned systems, AFPs will assume less risk in doing the same and can focus more on delivering firepower.36 The examples provided below solidify this assertion.
Submarines provide a healthy balance of ISR and offensive capabilities to the operational commander. A submarine’s ability to remain undetected is its foundational characteristic that gives friendly forces the advantage while “complicating the calculus” for the enemy.37 There is a significant tradeoff between stealth and mission accomplishment that occurs when a submarine operates in close proximity to its adversaries or communicates information to off-hull entities. By making use of UUVs, AFPs can still rely on stealthy underwater ISR-T while allowing the organic submarine to focus on delivering ordinance. In the given scenario, a small fleet of UUVs could be stationed west of the island and provide advanced warning of the approaching enemy forces. If traditional manned submarines took on this responsibility, they would likely have to engage on their own as the risk of counter-detection might outweigh the benefits of communicating. AFPs themselves could remain stealthy and focus on efforts to defeat the enemy.
While UUVs provide additional support in the undersea domain, UAVs are potential force multipliers in the DL application for two additional reasons. A cadre of unmanned aircraft could provide valuable ISR-T and line-of-sight (LOS) communications to further enable AFP lethality.38 From an ISR-T perspective, AFPs could deploy UAVs to forward positions along an enemy threat axis to provide indications and warning (I&W) of an advancing enemy target or SAG. Their smaller payloads means they can stay on station longer than manned aircraft, and they eliminate the risk of loss to human life. Additionally, the benefits of providing LOS communications are numerous. LOS communication is particularly advantageous because it eliminates the need to transmit over-the-horizon, which becomes exceedingly risky from a counter-detection perspective as range increases.39 A UAV keeping station at some altitude above the surface could provide LOS communications capability among various vessels within the AFP that are not necessarily within LOS of each other. Further, a UAV at a high enough altitude may afford the opportunity for one AFP to communicate LOS with an adjacent one. The level of autonomy these AFPs can achieve, and therefore lethality, only improves as battlespace awareness becomes more prolific and communication techniques remain stealthy.
Featured Image: The prototype of DARPA’s ACTUV, shown here on the day of its christening. (Photo: DARPA)
Just as UUVs and UAVs offer significant advantages to Autonomous Warfare, there is great value in the application for USVs in the surface domain. Take for instance the Defense Advanced Research Projects Agency’s (DARPA) anti-submarine warfare (ASW) Continuous Trail Unmanned Vessel (ACTUV). This stunning new technology has the capability of tracking the quietest diesel-electric submarines for extended periods.40 If this type of vessel was available to provide forward deployed ASW capabilities in the second scenario described above, the likelihood of RED submarines attacking BLUE would have diminished. While this particular USV would operate primarily for ASW purposes, it is completely feasible that the designers could equip the ACTUV with radar capabilities to provide additional ISR against air and surface threats. USVs simply provide an additional opportunity for operational commanders to provide ISR-T to weapons-bearing platforms.
The Combined Effect
The true value intrinsic to Autonomous Warfare stems from the combined effect of an appropriate C2 structure for DL that enables autonomous action and the force multiplier effect the operational commander realizes from unmanned systems. Distributed Lethality has serious potential for raising the status of our surface force as a formidable contender to one of deterrence. In an age where leaders measure warfighting capacity in technological advantage, it is refreshing to see an emerging concept that applies innovative thinking to warfighting techniques with the Navy we have today. A more autonomous C2 structure at the operational level will afford DL forces the flexibility to rapidly deliver offensive measures as contingencies develop. “By integrating unmanned systems in all domains, the U.S. Navy will increase its capability and capacity,” especially with respect to DL.41
Recommendations
It will take both time and effort to achieve an optimized Distributed Lethality construct through Autonomous Warfare. The following recommendations will assist in making this vision a reality:
1. There is risk that by disconnecting the AFPs from the CSG from a C2 perspective, the CSG becomes more vulnerable and unnecessarily sacrifices situational awareness. The Surface Warfare Directorate) N96 and the Distributed Lethality Task Force should further evaluate the tradeoffs associated with implementing a more autonomous C2 structure to DL at the operational level. Additionally, this paper proposes an operational C2 structure for DL. The conclusions derived from this paper should support further development of tactical level C2 for DL.
2. While many of the unmanned systems mentioned above are currently operational or under development, there is limited analysis of how to employ them in a Distributed Lethality environment. OPNAV N99 (Unmanned Warfare Systems), working in conjunction N96 and the DL Task Force, should consider incorporating unmanned systems within the DL concept as outlined above.
3. The U.S. Navy should conduct wargames and real world exercises to both validate the strengths of Autonomous Warfare and identify areas for improvement. Wargames will help refine Autonomous Warfare from a developmental approach. Naval exercises have two benefits: realistic testing provides proof of concept with the same force that will go to war. They also provide the opportunity to practice and inculcate new concepts.
4. Doctrine should begin to foster a culture of Autonomous Warfare throughout the U.S. Navy. The battlefield is becoming more volatile, uncertain, complex, and ambiguous. The more we enable our highly trained and experienced officers to think and act autonomously, the greater combat potential the Navy will realize. Submarines, by nature, operate this way on a continuous basis. Other warfare communities will benefit from having the ability to operate in a more autonomous manner. As Autonomous Warfare represents a paradigm shift from a “connected force” towards a more autonomous one, the U.S. Navy must understand and embrace Autonomous Warfare before implementing it.
Conclusion
Distributed Lethality’s impending contribution to the joint force depends on its ability to maintain flexibility. An autonomous C2 structure allows for localized assessment and force employment, rapid adaptation in the face of adversity, and the ability to combine forces and re-aggregate as the situation dictates. Aggressive employment of autonomous vehicles only enhances these principles. Unmanned systems operating across the maritime domains will provide valuable ISR-T and facilitate localized decision-making, while minimizing risk to the organic platforms. By providing a means of stealthy communication among ships within an AFP or even between adjacent ones, Autonomous Warfare fosters an environment of secure information sharing. Less need to reach back to a command node means that DL forces can spend more time taking the fight to the enemy and less time managing a complicated communications network.
Maritime warfare is a complex process. Characterized by uncertainty and ambiguity, no weapon, platform, or operating concept will eliminate the fog and friction of war. Commanders must mitigate these challenges by setting the conditions necessary for their subordinate leaders to prosper. Commanders at the tactical level earn the trust of their superiors before taking command. We should not compromise that trust by establishing rigid command and control structures that ultimately inhibit the subordinate’s ability to perform as trained. Applying the autonomous approach to C2 for distributed lethality will enable AFPs to operate in accordance with commander’s intent and is in keeping with the initiative to promote Mission Command throughout the U.S. Navy.
LT Coleman Ward is a Submarine Officer who is currently a student at the Naval War College. The preceding is his original work, and should not be construed for the opinions of views of the Department of Defense, the United States Navy, or the Naval War College.
Featured Image: The prototype of DARPA’s ACTUV, shown here on the day of its christening. Image Courtesy DARPA.
1. Timothy Walton and Bryan McGrath, “China’s Surface Fleet Trajectory: Implications for the U.S. Navy,” in China Maritime Study No. 11: China’s Near Seas Combat Capabilities, ed. Peter Dutton, Andrew Erickson, and Ryan Martinson, (U.S. Naval War College: China Maritime Studies Institute, February 2014), 119-121, accessed May 5, 2016, https://www.usnwc.edu/Research—Gaming/China-Maritime-Studies-Institute/Publications/documents/Web-CMS11-(1)-(1).aspx.; Peng Guangqian, Major General, People’s Liberation Army (Ret.), “China’s Maritime Rights and Interests,” in China Maritime Study No. 7: Military Activities in the EEZ, ed. Peter Dutton, (U.S. Naval War College: China Maritime Studies Institute, December 2010), 15-17, accessed May 12, 2106, https://www.usnwc.edu/Research—Gaming/China-Maritime-Studies-Institute/Publications/documents/China-Maritime-Study-7_Military-Activities-in-the-.pdf.
2. Walton and McGrath, “China’s Surface Fleet Trajectory: Implications for the U.S. Navy,” 119-121.
3. Thomas Rowden, Peter Gumataotao, and Peter Fanta, “Distributed Lethality,” U.S. Naval Institute, Proceedings Magazine 141, no. 1 (January 2015): 343, accessed March 11, 2016, http://www.usni.org/magazines/proceedings/2015-01/distributed-lethality.
4. Rowden et. al. “Distributed Lethality.”
5. James Bradford, America, Sea Power, and the World (West Sussex, UK: John Wiley and Sons, 2016), 339.
6. John Richardson, Admiral, Chief of Naval Operations, A Design for Maintaining Maritime Superiority (Washington, D.C.: Government Printing Office, January 2016), 6.
7. Matthew Hipple, “Distributed Lethality: Old Opportunities for New Operations,” Center for International Maritime Security, last modified February 23, 2016, accessed May 12, 2016, https://cimsec.org/distributed-lethality-old-opportunities-for-new-operations/22292.
8. Thomas Rowden et. al., “Distributed Lethality.”
9. U.S. Navy, U.S. Marine Corps, U.S. Coast Guard, A Cooperative Strategy for 21st Century Seapower (Washington, D.C.: Headquarters U.S. Navy, Marine Corps, and Coast Guard, March 2015), 9.
10. Thomas Rowden et. al, Distributed Lethality.
11. United States Navy, Naval Operations Concept 2010 (NOC): Implementing the Maritime Strategy (Washington D.C.: Government Printing Office, 2010), 54-55.
12. United States General Accounting Office, Comprehensive Strategy Needed to Improve Ship Cruise Missile Defense, GAO/NSIAD-00-149 (Washington, DC: General Accounting Office, July 2000), p. 5, accessed April 14, 2016, http://www.gao.gov/assets/230/229270.pdf.
13. Andrew Erickson and David Yang, “Using the Land to Control the Sea?,” Naval War College Review 62, no. 4, (Autumn 2009), 54.
14. United States Navy, Naval Operations Concept 2010: Implementing the Maritime Strategy, 54-56.
15. Andrew S. Erickson, Personal summary of discussion at “China’s Naval Shipbuilding: Progress and Challenges,” conference held by China Maritime Studies Institute at U.S. Naval War College, Newport, RI, 19-20 May 2015, accessed April 25, 2016, http://www.andrewerickson.com/2015/11/chinas-naval-shipbuilding-progress-and-challenges-cmsi-conference-event-write-up-summary-of-discussion/.
16. Thomas Rowden et. al., “Distributed Lethality.”
17. United States Navy. Naval Doctrine Publication (NDP) 1: Naval Warfare (Government Printing Office: Washington, D.C. March 2010), 35.
18. This is also referred to as “Mission Command” or “Command by Negation;” U.S. Office of the Chairman, Joint Chiefs of Staff, Joint Publication (JP) 3-32, Command and Control for Joint Maritime Operations (Washington D.C.: CJCS, August 7, 2013), I-2.
19. The Naval War College’s Gravely Group recently conducted a series of three DL Workshops with representation from offices across the Navy and interagency. One of the key findings was that “AFP SAG C2 architecture requires further development in view of information degraded or denied environments.” This paper proposes a notional operational level C2 structure – tactical level C2 is addressed in the recommendations section; William Bundy and Walter Bonilla. Distributed Lethality Concept Development Workshops I – III Executive Report. (U.S. Naval War College: The Gravely Group, December 29, 2015), 9.
20. This paper considers three types of maritime unmanned systems currently employed or under development: Unmanned Aerial Vehicles (UAVs), Unmanned Underwater Vehicles (UUVs), and Unmanned Surface Vessels (USVs).
21. See the below article featuring a newly developed Chinese drone similar to the U.S.’s Predator drone currently employed for operations in the Middle East; Kyle Mizokami, “For the First Time, Chinese UAVs are Flying and Fighting in the Middle East,” Popular Mechanics, last modified December 22, 2015, accessed May 10, 2016, http://www.popularmechanics.com/military/weapons/news/a18677/chinese-drones-are-flying-and-fighting-in-the-middle-east/.
22. This scenario does not represent a universal application for DL.
23. The Rowden “Distributed Lethality”article provides its own “Hunter-Killer Hypothetical” situation while supporting its main argument. However, the scenario is basic and does not afford the opportunity to explore how AFP C2 and unmanned systems would function in a complex maritime contingency.
24. Google Maps, “South Atlantic Ocean” map (and various others), Google (2016), accessed April 14, 2016, https://www.google.com/maps/@-50.3504488,-53.6341245,2775046m/data=!3m1!1e3?hl=en.
25. This is the same AFP force composition suggested in the Rowden Distributed Lethality article “Hunter-Killer Hypothetical” situation; Thomas Rowden et. al., “Distributed Lethality.”
26. For a full explanation of the CWC concept and roles and responsibilities of CWC warfare commanders, see: United States Navy, Navy Warfare Publication (NWP) 3-56: Composite Warfare Doctrine (Washington, D.C.: Government Printing Office, September 2010).
27. Larry LeGree, “Will Judgement be a Casualty of NCW?,” U.S. Naval Institute, Proceedings Magazine 130, no. 10 (October 2004): 220, accessed April 14, 2016, http://www.usni.org/magazines/proceedings/2004-10/will-judgment-be-casualty-ncw.
28. CNO’s Strategic Studies Group (XXII), Coherent Adaptive Force: Ensuring Sea Supremacy for SEA POWER 21, January 2004.
29. Michael Palmer, Command at Sea (Cambridge: Harvard University Press, 2005), 319.
30. Jimmy Drennan, “Distributed Lethality’s C2 Sea Change,” Center for International Maritime Security, last modified July 10, 2015, accessed April 14, 2016, https://cimsec.org/?s=Distributed+lethality+c2+sea+change.
31. Jeffrey Kline, “A Tactical Doctrine for Distributed Lethality,” Center for International Maritime Security, last modified February 22, 2016, accessed March 17, 2016, https://cimsec.org/tactical-doctrine-distributed-lethality/22286.
32. Palmer, Command at Sea, 322.
33. Jeffrey Kline, “A Tactical Doctrine for Distributed Lethality.”
34. Commander-in-Chief, U.S. Pacific Fleet, Current Tactical Orders and Doctrine, U.S. Pacific Fleet (PAC–10), U.S. Navy, Pacific Fleet, June 1943, pg. v, section 111.
35. Paul Siegrist, “An Undersea ‘Killer App’,” U.S. Naval Institute: Proceedings Magazine 138, no. 7, (July 2012): 313, accessed April 30, 2016, http://www.usni.org/magazines/proceedings/2012-07/undersea-killer-app.
36. Thomas Rowden et. al., “Distributed Lethality.”
37. Ibid.
38. Robert Rubel, “Pigeon Holes or Paradigm Shift: How the Navy Can Get the Most of its Unmanned Vehicles,” U.S. Naval Institute News, last modified February 5, 2013, https://news.usni.org/2012/07/25/pigeon-holes-or-paradigm-shift-how-navy-can-get-most-its-unmanned-vehicles.
39. Jonathan Soloman, “Maritime Deception and Concealment: Concepts for Defeating Wide-Area Oceanic Surveillance-Reconnaissance-Strike Networks,” Naval War College Review 66, no. 4 (Autumn 2013): 89.
40. Scott Littlefield, “Anti-Submarine Warfare (ASW) Continuous Trail Unmanned Vessel (ACTUV),” Defense Advanced Research Projects Agency, accessed April 30, 2016, http://www.darpa.mil/program/anti-submarine-warfare-continuous-trail-unmanned-vessel.
41. Robert Girrier, Rear Admiral, Director, Unmanned Warfare Systems (OPNAV N99), “Unmanned Warfare Systems,” Lecture at U.S. Naval War College, May 11, 2016.
Featured Image: PHILIPPINE SEA (Oct. 4, 2016) The forward-deployed Arleigh Burke-class guided-missile destroyer USS McCampbell (DDG 85) patrols the waters while in the Philippine Sea. McCampbell is on patrol with Carrier Strike Group Five (CSG 5) in the Philippine Sea supporting security and stability in the Indo-Asia-Pacific region. (U.S. Navy photo by Petty Officer 2nd Class Christian Senyk/Released)
