Category Archives: History

Naval and maritime history section.

Enabling Distributed Lethality: The Role of Naval Cryptology

Distributed Lethality Topic Week

By LCDR Chuck Hall and LCDR David T. Spalding

The U.S. Navy’s Surface Force is undergoing a cultural shift.  Known as “Distributed Lethality,” this strategy calls for our naval combatants to seize the initiative, operate in dispersed formations known as “hunter-killer” surface action groups (SAG), and employ naval combat power in a more offensive manner. After years of enjoying maritime dominance and focusing on power projection ashore, the U.S. Navy is now planning to face a peer competitor in an Anti-Access/Area Denial (A2AD) environment. Long overdue, Distributed Lethality shifts the focus to one priority – warfighting.  Far from a surface warfare problem alone, achieving victory against a peer enemy in an A2AD environment will require leveraging all aspects of naval warfare, including naval cryptology.

[otw_shortcode_button href=”https://cimsec.org/buying-cimsec-war-bonds/18115″ size=”medium” icon_position=”right” shape=”round” color_class=”otw-blue”]Donate to CIMSEC![/otw_shortcode_button]

Naval Cryptology has a long, proud history of supporting and enabling the Fleet. From the Battle of Midway in 1942, to leading the Navy’s current efforts in cyberspace, the community’s expertise in SIGINT, Cyber Operations, and Electronic Warfare is increasingly relevant in an A2AD environment. Led by Commander, U.S. Fleet Cyber Command/U.S. TENTH Fleet, the community is comprised of officers and enlisted personnel serving afloat and ashore and who are well integrated with the Fleet, intelligence community, and U.S. Cyber Command. Given its past history and current mission sets, naval cryptology is poised to enable distributed lethality by providing battlespace awareness, targeting support, and effects, in and through the electromagnetic spectrum and cyberspace.   

Battlespace Awareness

Battlespace Awareness, as defined in the Information Dominance Roadmap, 2013-2028, is “the ability to understand the disposition and intentions of potential adversaries as well as the characteristics and conditions of the operational environment.”  It also includes the “capacity, capability, and status” of friendly and neutral forces and is most typically displayed as a Common Operating Picture (COP).  To be effective, however, battlespace awareness must seek to provide much more than just a COP. It must also include a penetrating knowledge and understanding of the enemy and environment — the end-user of which is the operational commander. The operational commander must be able to rely on predictive analysis of enemy action in the operational domain to successfully employ naval combat power in an A2AD environment.  

Naval Cryptology has historically provided battlespace awareness through the execution of Signals Intelligence (SIGINT) operations.  During World War II, Station HYPO, located in Pearl Harbor and headed by Commander Joseph Rochefort, collected and decrypted the Japanese naval code, known as JN-25. Station HYPO’s exploitation of Japanese naval communications was sufficient to provide daily intelligence reports and assessments of Japanese force dispositions and intentions. These reports were provided to naval operational commanders, to include Admiral Chester W. Nimitz, Commander in Chief, U.S. Pacific Fleet and Commander in Chief, Pacific Ocean Areas. On May 13, 1942, navy operators intercepted a Japanese message directing a logistics ship to load cargo and join an operation headed to “Affirm Fox” or “AF.”  Linguists from Station HYPO had equated “AF” to Midway in March after the Japanese seaplane attack on Hawaii (Carlson, 308) and was thus able to confirm Midway as the objective of the upcoming Japanese naval operation.  Station HYPO was also able to give Nimitz the time and location of the Japanese attack point: 315 degrees, 50 nm from Midway, commencing at 7:00AM (Carlson, 352). This allowed Nimitz to position his forces at the right place, designated Point Luck, northeast of Midway, placing the U.S. fleet on the flank of the Japanese (Carlson, 354). Had Station HYPO’s efforts failed to provide this battlespace awareness, Admiral Nimitz would not have had enough time to thwart what might have been a surprise Japanese attack.  

Photo shows work being done on the Japanese Naval code J-25 by Station HYPO in Hawaii. The Japanese order to prepare for war was sent in J-25 prior to the attack on Pearl Harbor, but decoders had been ordered to suspend work on the Naval code and focus efforts on the diplomatic code. Later, enough of J-25 was broken to be used as an advanced warning to the Japanese attack on Midway. NSA photo.
Photo shows work being done on the Japanese Naval code J-25 by Station HYPO in Hawaii. The Japanese order to prepare for war was sent in J-25 prior to the attack on Pearl Harbor, but decoders had been ordered to suspend work on the Naval code and focus efforts on the diplomatic code. Later, enough of J-25 was broken to be used as an advanced warning to the Japanese attack on Midway. NSA photo.

Victory at Midway was founded on the operational commander’s knowledge of the enemy’s force construct and disposition. Currently the product of both active and passive, organic and non-organic sensors, achieving battlespace awareness in an A2AD environment will require more emphasis on passive and non-organic sensors, and increased national-tactical integration in order to prevent detection and maintain the initiative.  The “hunter-killer” SAGs will be entirely dependent upon an accurate and timely COP – not just of enemy forces, but of dispersed friendly forces as well.  Just as battlespace awareness enabled triumph against the Imperial Japanese Navy, so too will it be the very foundation upon which the success of distributed lethality rests. Without it, the operational commander cannot effectively, and lethally, disperse his forces over time and space.    

Targeting Support

Another key enabler of the Surface Navy’s shift to the offensive will be accurate and timely targeting support.  Though support to targeting can come in many forms, as used here it refers to the triangulation and precision geolocation of adversary targets via communications intelligence and radio direction finding (RDF).  In an environment in which options to “fix” the enemy via radar or other active means introduces more risk than gain, RDF presents itself as a more viable option.  Indeed, the passive nature of direction finding/precision geolocation makes it particularly well suited for stealthy, offensive operations in an A2AD environment.  Leveraging both organic and non-organic sensors in a fully integrated manner — RDF will provide “hunter-killer” SAG commanders with passive, real-time, targeting data.     

Perhaps one of the best historical examples of Naval Cryptology’s support to targeting can be seen in the Battle of the Atlantic. The Third Reich had threatened the very lifeline of the war in Europe as Admiral Donitz’ U-boats were wreaking havoc on Allied merchant vessels throughout the war. Though America had begun intercepting and mapping German naval communications and networks as early as 1938, it was not as critical then as it was upon entry into the war. By the time America entered the war, the U.S. Navy’s SIGINT and cryptanalysis group, OP-20-G, boasted near 100 percent coverage of German naval circuits. Many of these circuits were used for high frequency (HF), long range shore-ship, ship-shore, and ship-ship communications. The ability to both intercept these communications and to locate their source would be necessary to counter the Axis’ attack. That ability was realized in an ever growing high frequency direction finding (HFDF) network.

The HFDF network originally consisted of only a handful of shore stations along the Atlantic periphery. Throughout the course of the war it grew to a rather robust network comprised of U.S., British, and Canadian shore-based and shipborne systems. The first station to intercept a German naval transmission would alert all other stations simultaneously via an established “tip-off” system.  Each station would then generate a line of bearing, the aggregate of which formed an ellipse around the location of the target.  This rudimentary geolocation of German U-boats helped to vector offensive patrols and enable attack by Allied forces — thus taking the offensive in what had previously been a strictly defensive game.  The hunter had become the hunted.        

German U-boats threatened the very lifeline of the war in Europe by wreaking havoc on Allied merchant vessels throughout the war.
German U-boats threatened the very lifeline of the war in Europe by wreaking havoc on Allied merchant vessels throughout the war.

Enabling the effectiveness of increased offensive firepower will require more than battlespace awareness and indications and warning.  Going forward, Naval cryptologists must be agile in the support they provide — quickly shifting from exploiting and analyzing the enemy, at the operational level, to finding and fixing the enemy at the tactical level. Completing the “find” and “fix” steps in the targeting process will enable the “hunter-killer” SAGs to accomplish the “finish.”

Cyber Effects

Finally, cyber.  Receiving just a single mention, the original distributed lethality article in Proceedings Magazine refers to the cyber realm as, “the newest and, in many ways most dynamic and daunting, levels of the battlespace—one that the Surface Navy, not to mention the U.S. military at large—must get out in front of, as our potential adversaries are most certainly trying to do.” Indeed, the incredible connectivity that ships at sea enjoy today introduces a potentially lucrative vulnerability, for both friendly forces and the adversary. Similar to battlespace awareness and targeting, Naval Cryptology has history, albeit limited, in cyberspace. Cryptologic Technicians have long been involved in Computer Network Exploitation (CNE) and the Navy was the first service to designate an enlisted specialty (CTN) in the cyber field. According to the FCC/C10F strategy, not only do they, “operate and defend the Navy’s networks,” but they also, “plan and direct operations for a subset of USCYBERCOM’s Cyber Mission Forces.”  The combination of history and experience in cyberspace, coupled with the FCC/C10F designation as the Navy’s lead cyber element, clearly places the onus on naval cryptology. As the Navy seeks to protect its own cyber vulnerabilities, and exploit those of the adversary, the execution of effective cyber operations by the cryptologic community will be critical in enabling distributed lethality.

Going Forward

Today, through a wide array of networked, passive, non-organic sensors, and integration with national intelligence agencies and U.S. Cyber Command, naval cryptology is well-positioned to enable distributed lethality by providing battlespace awareness, targeting support, and effects, in and through the electromagnetic spectrum and cyberspace. Yet, similar to the surface force, a cultural shift in the cryptologic community will be required. First, we must optimize national-tactical integration and better leverage and integrate off-board sensors. The uniqueness of the A2AD environment demands the integration and optimization of passive, organic and non-organic sensors in order to prevent counter-targeting. Second, we must prioritize the employment of direction finding and geolocation systems, ensuring they are accurate and sufficiently integrated to provide timely targeting data for weapons systems. This will require a shift in mindset as well, from simple exploitation to a focus on “find, fix.” Third, we must continue to lead in cyberspace, ensuring cyber defense in depth to our ships at sea while developing effects that effectively exploit adversary cyber vulnerabilities. Finally, naval cryptology’s role in distributed lethality cannot occur in a vacuum — increased integration with the Fleet will be an absolute necessity.

Distributed lethality is the future of Naval Surface Warfare — a future in which the cryptologic community has a significant role. In order to ensure the Surface Force can seize the initiative, operate in dispersed formations known as “hunter-killer” SAGs, and employ naval combat power in a more offensive manner in an A2AD environment, Naval Cryptology must stand ready to provide battlespace awareness, targeting support, and effects, in and through the electromagnetic spectrum and cyberspace.

LCDR Chuck Hall is an active duty 1810 with more than 27 years of enlisted and commissioned service.  The opinions expressed here are his own.

LCDR David T. Spalding is a  former Cryptologic Technician Interpretive.  He was commissioned in 2004 as a Special Duty Officer Cryptology (Information Warfare/1810).  The opinions expressed here are his own.

[otw_shortcode_button href=”https://cimsec.org/buying-cimsec-war-bonds/18115″ size=”medium” icon_position=”right” shape=”round” color_class=”otw-blue”]Donate to CIMSEC![/otw_shortcode_button]

Works cited:

Ballard, Robert. Return to Midway. Washington, D.C: National Geographic, 1999.

Parshall, Jonathan. Shattered Sword : The Japanese Story of the Battle of Midway. Dulles, Va. Poole: Potomac Chris Lloyd distributor, 2007.

Carlson, Elliot. Joe Rochefort’s War: the Odyssey of the Codebreaker Who Outwitted Yamamoto at Midway. Annapolis, MD: Naval Institute, 2011. Print.

On Naval History, Books, and Coal: An Interview with Rear Admiral James Goldrick, RAN(ret.)

By Christopher Nelson

A little over a month ago, I had the opportunity to sit down and talk to Rear Admiral James Goldrick, RAN(ret.), over lunch.  It was a fascinating conversation that covered books, naval history, and yes, even coal.  Admiral Goldrick is, in my opinion, that rare naval officer that combines a deep understanding of history with operational naval experience.   I hope you all enjoy the interview as much as I enjoyed talking with him. 

Admiral, thank you for taking the time to sit down and talk.  Starting off, who is a historian writing today that you admire? And why?

Nicholas Rodger.  Nicholas – apart from an extraordinary intellect, the ability to read in multiple languages, a wonderful literary style and a very strong work ethic – has the ability to look deeply, to look again, and to bring things together.  All that is combined with a deep understanding of how navies work.  He is currently writing a three volume history of the British Royal Navy.  The first two volumes (The Safeguard of the Sea and The Command of the Ocean) have already been published, and he is currently working on the third.  Now, it’s not in fact a history of the British Navy – it is a naval history of Britain.   I particularly admire Nicholas because he avoids the trap that naval historians often fall into, that is, of being too tunneled.  What he is trying to do is explain the role of the navy as a national institution and what its relationship was with the nation.  What is quite clear from his studies, for example, is that it can be strongly argued that the Royal Navy was a key trigger of the industrial revolution.  The things required for the Royal Navy – for example, long range distribution and preservation of food – helped with the ability to operate big industrial cities.  The mass production systems developed to run Nelson’s fleet – the manufacturing of blocks, and so on – were another contribution through the application of such ideas in the commercial sphere.  Like all the greatest historians, Nicholas can synthesize a great deal of information and bring it all together to tell a story.  What I can tell you, is that his third volume is late.  And the reason for that is that, while he always knew that he had to synthesize a massive amount of material for the nineteenth and twentieth centuries, he has also found that the canon of naval history in the modern era is superficial. When you start to dig into things, you often realize that is not the way it works, that is not the way it happened.

Talking earlier, you mentioned Rodger’s book The Wooden World, and strongly recommended it, and that the movie “Master and Commander” was in part based on that book, which is something I had not heard before.

One of the reasons I think it is really important, and a The Wooden Worldreally good book for naval officers to read, is because Master and Commander is slightly anachronistic.  What Nicholas is talking about in The Wooden World: An Anatomy of the Georgian Navy is the mid-18th  century Royal Navy, although Peter Weir and Russell Crane applied it to the service of the Napoleonic Wars as, arguably, did the author of the original series of Jack Aubrey novels, Patrick O’Brian.  Nicholas’ mid-18th century navy is one that is pre-ideological, and has a pre-rigid class organization. Some of this still applied in the first decade of the nineteenth century and this is where Master and Commander is right to show the legacy – even if the navy was changing.  There was in the navy of Nelson an officer who flew his flag at sea as, I think, a vice admiral, who had been flogged around the fleet as a naval seaman for desertion.  He was a real person and ended up as Knight Commander of the Bath – Sir William Mitchell.  Now, what I am getting at is the pre-ideological situation of circa 1760, in that you have a navy which is based on mutual confidence, mutual respect and professionalism.  We talk about patronage, and yes, if you were from the upper class and had good connections, it was much easier to get ahead.  But if you were incompetent, you generally didn’t get ahead, since if you are the First Lord of the Admiralty or a commander-in-chief, and you are promoting people who are idiots, your ships won’t last.  They’ll sink for a start just from the effects of weather, they won’t be able to capture the enemy, and so on.  However, late on in the eighteenth century, what you begin to get, and the American revolution marks the first rumblings of this (it really sets in after the French revolution), is that ideology and class and the fear of subversion become factors. In the navy that Nicholas Rodger talks about it was OK to mutiny in certain circumstances – if you haven’t been paid for instance.  If the food was bad.  And it is very interesting, in that navy, that if there were a mutiny for other reasons the Admiralty usually fired the captain, however harshly they dealt with the ringleaders.  Because, if there were a mutiny for other reasons than pay or food – or losing accustomed officers – the Admiralty’s assumption was it was resulted from a failure in leadership.  I hope you begin to see where I am coming from.  When we are in are a post-ideological, post-class system in 2016, what do we actually base our navy on?  We base it on mutual respect and professionalism and support for each other. And if there is a problem in a ship, how do the admiralties of the western navies now generally respond? They fire the captain.  In between, roughly from 1800 to 1990, when you have ideology, subversion and all the rest of it, there is always this idea that a mutiny will have external motivations.  In such circumstances, admiralties may have to support the command because they have to support the system. That’s not the case now. What I am seeing in The Wooden World that Nicholas Rodger is telling me about is a navy that I recognize, much more in certain ways than the navy of the centuries in between.

What advice would you give to a junior or senior officer on how to use history to think about our current challenges in the naval profession?

I like the aphorism “history doesn’t repeat itself, but it rhymes.”  You use history to identify the rhymes, to start identifying the questions that you should be asking.I’m particularly seeing rhymes when we look at the First World War and many of the challenges we face now.  And many of these challenges are caused by technological change, but the key shared issue is command and control. I think we are facing some real problems of a similar nature to 1914 at the moment.  We have got ourselves used to an uncontested electronic environment and a virtual reality which allows constant communication between commands and subordinates.  That creates two problems: the one that gets talked about most frequently is the “thousand mile screwdriver.”  But there is another problem that worries me even more and this is also a World War I problem – subordinates won’t make a decision; many would rather ask permission than seek forgiveness.  And that I think creates the prospect that if communications are cut off, operations will be paralyzed because people will wait and see if communications become reestablished rather than do anything themselves.  The direct parallel is the effect of radio on naval culture in 1914.  Before radio, it was inherently bipolar.  If you were in sight of the admiral you were doing exactly what the admiral directed.  But if you were not in sight of the admiral before radio, you knew what the intent was, and you went. As one British prime minister of the nineteenth century remarked, if he had a problem overseas, he’d send a naval officer. 

Your latest book is about The Battle of Jutland?

It predates Jutland; it’s about the opening months of the war and is called Before Jutland.  One of my argumentsBefore Jutland is that there were failures of leadership which were based on this “virtual unreality.” I can see why people are failing to exercise initiative which I am pretty sure wouldn’t have been the case to the same extent had there been no radio.  The problem was that, with the introduction of radio, when the practical problems and the associated concepts had still to be worked through – and the conceptual changes in particular were profound – detached commanders began to behave in the way that they would when they could actually see their boss. People acted as if they could see the admiral and get an immediate direction to go here or there, and they also assumed the admiral had the picture they have. 

To be fair, there was a whole raft of unrecognized problems of understanding on how people talked to each other remotely.  That was another art and another science that had to be learned, effectively from scratch.  For example, the first time the Royal Navy issued a format for radio reporting of an enemy contact there was no position.  Why?  Because when you are in a visual environment you are really only interested in two things: what the enemy bear and what they are steering. It is remote reports, with the much greater distances involved, that require much greater detail and precision. The fact was that the out-of-sight admiral did not have the full picture in 1914. Arguably, given transmission delays, deficiencies in reporting systems and the combined navigational errors both true and relative, he could never, at least in 1914-18, have that full picture.

You can also see in 1914 an essentially arithmetical approach to the correlation of forces.  What I mean by that: It is a simplistic approach, the idea that if someone has a long range and a longer gun, we can’t go for
them. This happened during the chase of the German battlecruiser Goeben in the Mediterranean in August 1914 and it also happened more than once in the North Sea.  Sorry, but, as Nelson used to say, “something must be left to chance.” 

Großer_Kreuzer_SMS_Goeben
SMS Goeben on a postcard pre-World War I/Wikipedia

Another thing that is similar in 1914 to now, is how short of money the navies were at the time.  We talk about the great expansion, the arms race, and it’s absolutely true that enormous amounts of money were being spent. Both the Germans and the British had budgetary crises over such expenditure.  But the money is going to the battle fleets, not operations. The British are enforcing strict fuel economy.  Why?  Because they are building fifteen inch gun battleships which cost the earth, as does oil fuel.  There is a major cabinet crisis going on about the naval estimates and the Admiralty has to make economies where it can.  So you have limited time at sea and limited exercises in a period of very rapid technological change. You haven’t got the ability to exercise sufficiently, to experiment sufficiently, to become proficient enough to even understand the risks. Arguably, the Germans were even more constrained and thus even worse off.

Now to tie your earlier comments about the challenges of radio and command and control in World War I to today. Is flexibility, and the assumption that you are not going to have secure communications, those assurances, are those the going in conversation?

I’m old enough to remember having to navigate out of sight of land for extended periods of time with no artificial aids.  When people talk about the revolution in military affairs, I go, come on guys, the first naval combat data systems went operationally to sea about 1960.  The data links were running about 1961-1962.  The revolution in military affairs is not computer systems and it is not data links – it’s GPS.  Because GPS puts everybody in the same constant frame of reference.  Trust me.  Try doing a link picture before GPS.  Manually updating and watching your whole system slide sixty miles, and all of the other problems that occur if one ship fails in reporting or muddles its settings.  Same with joint fires; it’s all GPS.  OK.  So what happens if you are in a contested environment and your GPS doesn’t work?  I think we are coming to an era where we will be very vulnerable if we go on this way. The truth is that you won’t be able to do the things that you think you can.  

That similarity with the First World War – I mean – do you know what the most useful thing in navigation was in the First World War in the North Sea?  Depth soundings.  Bathymetry.  What did the British do?  What are they doing enormous amounts of from about 1908 on?  They are surveying the North Sea to get the depths and the currents. These are things we don’t think about anymore because we don’t have to.  But the trouble is I think we have to think about these things because the remote data sources will not necessarily be accessible in a contested electronic environment.  As I understand it, the United States Naval Academy is going back to teaching astro-navigation. 

What are the top three history books that you’ve read and that you would recommend to anyone?

The Rules of the Game by Andrew Gordon is one of them.  IRules of the Game was really pleased to be sitting on one occasion with my chief of the navy and Vice Admiral Art Cebrowski. Both had read the book and were talking about the take-aways from The Rules of the Game.  Next, is Nicholas Rodger’s naval history of Britain that I’ve already mentioned.  My third book would probably be one of Norman Friedman’s works.  Which one would depend who you are.  For me personally, one of the highlights is his U.S. Destroyers book.  It encapsulates all the best that Norman does in terms of understanding how a design evolves, what the operational factors are, the financial factors, etc.  I would also say his book on interwar aircraft carrier development is really worth reading (American & British Aircraft Carrier Development 1919-1941).  See, one of the real problems is hindsight, and not understanding that things change and that they change in relation to each other.  What Norman conveys really well is that there are always changing variables.  He explains very well why the Brits got some things wrong in naval aviation, but often for very good reasons that were valid at the time.  

There is another wonderful history book, and it is sort of a joke about British cultural education.  It’s a book called 1066 and All That.  It is a satire of history.  It is written by two guys, who I think were middle and secondary school history teachers.  It’s called 1066 and All That 1066 And All Thatbecause the book is about the history that people remember, not what they were taught.  The authors called it that because they reckon that 1066 is the only date in British history that all Brits would remember from their school days.  And there is a great quote in the book about “The Irish Question.”  And it is worth thinking about: “The English never settled the Irish question because every time the English found the answer the Irish changed the question.” Naval policy and force structure development are a bit like that.

World War I produced some of the best poets in the English language.  Do you read poetry?

I do enjoy it.  I have a number of anthologies.  I particularly like Field Marshal Wavell’s anthology, Other Men’s Flowers.  If there is a poet of the navy, it’s actually FlowersRudyard Kipling.  Kipling wrote about the navy very sympathetically and very well.  Kipling is the poet of technology; he’s the poet of the engineers.  And he is also the poet of commanders – “The Song of Diego Valdez” and its examination of the “bondage of great deeds” is worth reading carefully.

Of course the naval experience was never the same as that of the army, and in many ways the education you needed in the navy was not the same in the army.  The navy didn’t get that sort of flower of a generation from liberal arts universities that the army did in 1914-18.  They didn’t get the Siegfried Sassoons, Robert Graves, and all the rest.  However, rather than poetry, when I lecture on leadership, particularly at the staff course to all three services, I suggest officers read these works: 

For the army, I suggest a book by John Masters.  He wrote Nightrunners of Bengal and other stuff.  Masters was an Indian Army lieutenant colonel at the age of thirty-two, and he earned a DSO and an OBE by the end of World War II, having been one of the leaders of Wingate’s Chindits in Burma.  I recommend his book called Man of War. It is set in pre-Dunkirk France.  It’s about a lieutenant colonel who ends up running a battalion group.  And it is based on history.  He faces off against Rommel.  Army officers like it because it is a great book on that level of command.

man of war

For the navy, I recommend The Cruel Sea by Nicholas Monsarrat.  He was a volunteer, a reservist, who started his war with complete inexperience as a sub-lieutenant and finished it commanding a frigate. So he understands his subject, leadership at sea in the Battle of the Atlantic. Another is Herman Wouk’s Caine Mutiny, which I would put in the same league.  It is the study of leadership in a slightly different context, but very valuable for all that.  Herman Wouk did the same as Monsarrat, he served in the Pacific War as a reserve officer.  I met him many years ago when he visited Australia and he told me that he had to write this book, but he was terrified how it would be received.  You know, that the US Navy (which he loved) would never talk to him. Instead what happened was that The Caine Mutiny was published and became a best seller very quickly.  And then for six weeks after it came out there was a deathly silence; none of his navy friends would talk to him.  Wouk was thinking “Oh God.”  Then someone asked the then-CNO publicly if he had read the book.  And the CNO said “It’s a great book!  I’ve met every one of the single people in that book, not on the same ship, but I’ve met all of them – it’s a great book.”  Herman Wouk told me he breathed a huge sigh of relief after hearing that.

Now, for air power, you should read the book Twelve O’clock High.  And actually, I recommend you watch the film as much as reading the book because the men who wrote the book wrote the film script.  And both of them had done full deployments in the US Army Air Corps in the bombing campaign over Europe.  In theory it is a high command novel, but in reality it isn’t, it’s about unit command in attrition warfare.

All these works convey a reality of the experience of command and war that in some ways expert fiction can do more easily than history.  If you read all of these books seriously, they’ll tell you the sort of things you should be thinking about. 

What is the best Nelson biography you would recommend? Other biographies you recommend?

Roger Knight’s The Pursuit of Victory: The Life and Achievement of Horatio Nelson.  Very good indeed; Head and shoulders above others.  I also think that Andrew Lambert’s Admirals book is very good – especially about his nineteenth century subjects.  I also recommend that every US naval officer read Admiral Elmo Zumwalt’s book On Watch.  Zumwalt made his mistakes as CNO from 1970 to 1974.  And of course he won’t admit many of them in his autobiography.  But, as the story of a genuine change effort as well as some interesting – and continuing – naval problems and how you deal with them, it is a very worthwhile read.  If you think of the subtext, and then you go and read other stuff, you can see he is sort of admitting that where he failed is engaging commissioned and noncommissioned leaders.  The US Navy was in a bad state in 1970 and something had to be done.  Navies can get disconnected from the culture of their nations.  This is not to do with standards or things like that.  It has more to do with cultural mores.  It’s the old thing about are you allowed to wear jeans as a liberty uniform?  If jeans are the accepted thing in society…well, then, yes, you should be.

What four people from history would you have at your dinner table?  And why?

If I start with Americans, William S. Sims. I suspect I would like to have dinner with Abraham Lincoln and Teddy Roosevelt.  And I admire Harry S. Truman – he and the other two presidents were all readers, too.  Next, I’d like to meet Nelson.  Whatever Nelson had, the really striking thing about him is that he had this extraordinary ability that if the enemy did anything wrong Nelson went straight at them.  Nelson led at all levels.  Everybody working for Nelson loved him.  And he was, by all accounts, a great host at dinner himself!

As a historian digging into the archives, and as you’ve studied history, what are those things that you’ve touched and read that reminded you why you love being a historian?

Yes, there is that moment when you find something that nobody else has looked at before.  When you find something, a particularly important piece of evidence…there is one I found about the Battle of the Dogger Bank in January 1915.  It was in Beatty’s flag commander’s recollections written within two days of the battle – and nobody had picked up on this.  They were written before they got back in harbor.   There is a key narrative there about one vital tactical decision in the battle.  And if you read this you understand very differently why and how everybody else reacted.  

Another thing I ended up getting heavily involved in when doing research for World War I, was coal.  Coal turns out to be fundamental.  I ended up writing an academic paper on it because it was so important (“Coal and the Advent of the First World War at Sea).  It’s all to do with the sort of coal you used.  First, it is about understanding how the ships worked.  You now we have this picture of it being the boilers and the stokers…well, that’s not the problem.  The problem is the bunkers, and what’s called trimming.  It’s getting the coal from the bunkers to the stoke hold, that’s the problem, not shoveling it into the boilers.  In fact, quite a lot of the deck crew had to support trimming operations.  And because of this, the British had to change their manning to support trimming.  In World War I, for all major units, the last 25% of the coal was inaccessible if they were doing any sort of reasonable speed.  They couldn’t get the coal from the bunkers to the stoke holds fast enough.  That problem started at 60% capacity with the battle cruisers.  

800px-British.coalfields.19th.century
British Coalfields in the 19th Century

Then you get into types of coal.  The right coal for a warship boiler is what’s called semi-bituminous coal.  There is one area which produces the best such coal in the world – and it’s a particular section of the Welsh coal fields.  There were 40 collieries which produced what was called “Admiralty coal.”  Now, outside of them, are what’s called “steam coal” areas.  It’s still pretty good coal, but the Admiralty coal burnt producing almost no smoke (and that’s really important for its effect on visibility in battle). Furthermore, the coal lumps were the right size, and they “cauliflowered” – as the Admiralty coal heats up the top breaks open which actually increases the surface area and increases the efficiency of combustion.  Admiralty coal is what the Royal Navy used.  Basically, the difference in coal performance was – and here I have the Australian figures – because for this purpose [powering warships] Australian coal was crap. When the battle cruiser Australia arrived in Australia in 1913, naturally enough, the Australian government wanted it provided with Australian coal rather than Welsh Admiralty coal because Welsh Admiralty coal was much more expensive.  Now, Australia, with 31 boilers on Admiralty coal alone, could do 26 knots.  Using Australian coal, with supplementary oil firing, on all boilers, she could barely do 15 knots and her range was reduced by 40%-50%; and in fact, even then she would start having incredible problems with the boilers choking…with ash and debris buildup. 

Circumstantial evidence supports my contention that the Imperial German Navy did their high-speed steam trials using Welsh admiralty coal.  Knowing the German Navy was a political institution and that its official history Der Krieg zur See was written with an eye to encouraging Germany to rearm, it is not surprising that this doesn’t get a mention. I think what happened is that they were embarrassed, because this is not something you can admit, you know, you did your power trials with your prospective enemy’s fuel source.  The German battle cruisers could do 28 knots during sea trials.  As far as I can figure in an operational environment, no German major unit never achieved more than 24 knots sustained.  And in every German operation the ships are complaining about the quality of coal, because they are using Westphalian coal.  So you have serious operational implications.  It’s actually when you look at this closely that it does matter.

Sir, thank you for your time.

Thank you.

Rear Admiral James Goldrick, RAN(ret.), AO,CSC joined the Royal Australian Navy in 1974 and retired in 2012 as a two star Rear Admiral. He is a graduate of the RAN College, the Harvard Business School Advanced Management Program, the University of New South Wales and the University of New England, and a Doctor of Letters honoris causa of UNSW. He commanded HMA Ships Cessnock and Sydney (twice),

Rear Admiral James Goldrick, RAN(ret.)
Rear Admiral James Goldrick, RAN(ret.)

the RAN task group and the multinational maritime interception force in the Persian Gulf (2002) and the Australian Defence Force Academy (2003-2006 and 2011-12). He led Australia’s Border Protection Command (2006-2008) and the Australian Defence College (2008-2011). He is a Fellow of the RAN’s Sea Power Centre-Australia, a Non-Resident Fellow of the Lowy Institute for International Policy, Adjunct Professor of UNSW at ADFA and SDSC at The Australian National University and a Professorial Fellow of the Australian National Centre for Ocean Resources and Security. In the first half of 2015 he was a Visiting Fellow at All Souls College in the University of Oxford. James Goldrick’s books include: The King’s Ships Were at Sea: The War in the North Sea August 1914-February 1915 and No Easy Answers: The Development of the Navies of India, Pakistan, Bangladesh and Sri Lanka, and, with Jack McCaffrie, Navies of South-East Asia: A Comparative Study. His latest book is Before Jutland: The Naval War in Northern European Waters, August 1914 — February 1915. The comments above are the author’s own.

Lieutenant Commander Christopher Nelson, USN, is an intelligence officer stationed at the US Pacific Fleet Headquarters in Honolulu, Hawaii.  Lieutenant Commander Nelson is a graduate of the US Naval War College and the navy’s operational planning school, the Maritime Advanced Warfighting School in Newport, Rhode Island.  The comments above are the author’s own and do not necessarily reflect those of the US Department of Defense or the US Navy.

Declassified: US Nuclear Weapons At Sea

This piece was originally published by the Federation of American Scientists.  It is republished here with the author’s permission.  Read it in its original form here.

By Hans M. Kristensen

ASROC nuclear test.
ASROC nuclear test.

Remember during the Cold War when US Navy warships and attack submarines sailed the World’s oceans bristling with nuclear weapons and routinely violated non-nuclear countries’ bans against nuclear weapons on their territories in peacetime?

The weapons were onboard ballistic missile submarines, attack submarines, aircraft carriers, battleships, cruisers, destroyers, frigates and supply ships. The weapons were brought along on naval exercises, spy missions, freedom of navigation demonstrations and port visits.

Sometimes the vessels they were on collided, ran aground, caught fire, or sank.

Not many remember today. But now the Pentagon has declassified how many nuclear weapons they actually deployed in the Atlantic, Pacific, and Mediterranean. In our latest FAS Nuclear Notebook published in the Bulletin of the Atomic Scientists we review this unique new set of declassified Cold War nuclear history. 

The Numbers

The declassified documents show that the United States during much of the 1970s and the 1980s deployed about a quarter of its entire nuclear weapons stockpile at sea. The all-time high was in 1975 when 6,191 weapons were afloat, but even in 1990, after the fall of the Berlin Wall, there were 5,716 weapons at sea. That’s more nuclear weapons than the size of the entire US nuclear stockpile today.

The declassified data provides detailed breakdowns for weapons in the Atlantic, Pacific, and Mediterranean for the 30-year period between 1961 and 1991. Prior to 1961 only totals are provided. Except for three years (1962, 1965 and 1966), most weapons were always deployed in the Atlantic, a reflection of the focus on defending NATO against the Soviet Union. When adding the weapons in the Mediterranean, the Euro-centric nature of the US nuclear posture during the Cold War becomes even more striking. The number of weapons deployed in the Pacific peaked much later, in 1987, at 2,085 weapons.

afloat_table
Click to view full size

The declassified numbers end in 1991 with the offloading of non-strategic naval nuclear weapons from US Navy vessels. After that only strategic missile submarines (SSBNs) have continued to deploy with nuclear weapons on board. Those numbers are still secret.

In the table above we have incorporated our estimates for the number of nuclear warhead deployed on US ballistic missile submarines since 1991. Those estimates show that afloat weapons increased during the 1990s as more Ohio-class SSBNs entered the fleet.

Because the total stockpile decreased significantly in the early 1990s, the percentage of it that was deployed at sea grew until it reached an all-time high of nearly 33 percent in 2000. Retirement of four SSBNs, changes to strategic war plans, and the effect of arms control agreements have since reduced the number of nuclear weapons deployed at sea to just over 1,000 in 2015. That corresponds to nearly 22 percent of the stockpile deployed at sea.

The just over 1,000 afloat warheads today may be less than during the Cold War, but it is roughly equivalent to the nuclear weapons stockpiles of Britain, China, France, India, Israel, Pakistan and North Korea combined.

Mediterranean Mystery

The declassification documents do not explain how the numbers are broken down. The “Atlantic,” “Pacific,” and “Mediterranean” regions are not the only areas where the U.S. Navy sent nuclear-armed warships. Afloat weapons in the Indian and Arctic oceans, for example, are not listed even though nuclear-armed warships sailed in both oceans. Similarly, the declassified documents show the number of afloat weapons in the Mediterranean suddenly dropping to zero in 1987, even though the U.S. Navy continued so deploy nuclear-armed vessels into the Mediterranean Sea.

During the naval deployments in support of Operation Desert Storm against Iraq in early 1991, for example, the aircraft carrier USS America (CV-66) deployed with its nuclear weapons division (W Division) and B61 nuclear strike bombs and B57 nuclear depth bombs. The W Division was still onboard when America deployed to Northern Europe and the Mediterranean in 1992 but had been disbanded by the time it deployed to the Mediterranean in 1993.

B61 and B57 nuclear weapons are displayed on board the USS America (CV-66) during its deployment to Operation Desert Storm in 1991. The nuclear division was also onboard in 1992 but gone in 1993.
B61 and B57 nuclear weapons are displayed on board the USS America (CV-66) during its deployment to Operation Desert Storm in 1991. The nuclear division was also onboard in 1992 but gone in 1993.

As ships offloaded their weapons, the on-board nuclear divisions gradually were disbanded in anticipation of the upcoming de-nuclearization of the surface fleet. One of the last carriers to deploy with a W Division was the USS John F. Kennedy (CV-67), which upon its return to the United States from a Mediterranean deployment in 1992-1993 ceremoniously photographed the W crew with the sign: “USS John F. Kennedy, CV 67, last W-Division, 17 Feb. 93.” The following year, the Clinton administration publicly announced that all carriers and surface ships would be denuclearized.

afloat_last_carrier_1993
The last nuclear weapons division on the USS John F. Kennedy (CV-67) is disbanded in February 1993. The following year the entire surface fleet was denuclearized.

Since nuclear weapons clearly deployed to the Mediterranean Sea after the declassified documents showing zero afloat nuclear weapons in the area, perhaps the three categories “Atlantic,” “Pacific,” and “Mediterranean” refer to overall military organization: “Atlantic” might be weapons under the command of the Atlantic Fleet (LANTFLT); “Pacific” might refer to the Pacific Fleet (PACFLT); and “Mediterranean” might refer to the Sixth Fleet. Yet I’m not convinced that organization is the whole story; the Atlantic numbers didn’t suddenly increase when the Mediterranean numbers dropped to zero.

The declassified afloat numbers end in 1991. After that year the only nuclear weapons deployed at sea have been strategic weapons onboard ballistic missile submarines. Most of those deploy in the Atlantic and Pacific but have occasionally deployed into the Mediterranean even after the declassified documents list zero afloat weapons in that region, and even after the surface fleet was denuclearized.

In 1999, for example, the ballistic missile submarine USS Louisiana (SSBN-743) conducted a port visit to Souda Bay on Crete with it load of 24 Trident missiles and an estimated 192 warheads. The ship’s Command History states that the port visit, which took place December 12-16, 1999, occurred during the “Alert Strategic Deterrent Patrol in support of national tasking” that included a “Mediterranean Sea Patrol.”

Risks of Nuclear Accidents

accident_belknap1975_brokenarrowflash

Deploying nuclear weapons on ships and submarines created unique risks of accidents and incidents. Because warships sometimes collide, catch fire, or even sink, it was only a matter of time before the nuclear weapons they carried were threatened, damaged, or lost. This really happened.

During night air exercises on November 22, 1975, for example, the aircraft carrier USS John F. Kennedy (CV-67) and cruiser USS Belknap (CG-26) collided in rough seas 112 kilometers (70 miles) east of Sicily. The carrier’s flight deck cuts into the superstructure of the Belknap setting off fires on the cruiser, which burned out of control for two-and-one-half hours. The commander of Carrier Striking Force for the U.S. Sixth Fleet on board the Kennedy issues a Broken Arrow alert to higher commands stating there was a “high probability that nuclear weapons (W45 Terrier missile warheads) on the Belknap were involved in fire and explosions.” Eventually the fire was stopped only a few meters from Belknap’s nuclear weapons magazine.

accident_belknap1975
The fire-damaged USS Belknap (CG-26) after colliding with USS John F. Kennedy (CV-67) new Sicily in 1975. The fire stopped a few meters from the nuclear warhead magazine.

The Kennedy also carried nuclear weapons, approximately 100 gravity bombs for delivery by aircraft. The carrier caught fire but luckily it was relatively quickly contained. Another carrier, the USS Enterprise (CVN-65), had been less fortunate six years earlier when operating 112 kilometers (70 miles) southwest of Pearl Harbor, Hawaii. A rocket on a F-4 Phantom aircraft exploded puncturing fuel tanks and starting violent fires that caused other rockets and bombs to explode. The explosions were so violent that they tore holes in the carrier’s solid steel deck and engulfed the entire back of the ship. The captain later said: “If the fire had spread to the hangar deck [below], we could have very easily lost the ship.” The Enterprise probably carried about 100 nuclear bombs and was powered by eight nuclear reactors.

accident_enterprise1969
The nuclear-armed and nuclear-powered USS Enterprise (CVN-65) burns off Hawaii on January 14, 1969. The carrier could have been lost, the captain said.

Dozens of nuclear weapons were lost at sea over the decades because they were on ships, submarines, or aircraft that were lost. On December 5, 1965, for example, while underway from operations off Vietnam to Yokosuka in Japan, an A-4E aircraft loaded with one B43 nuclear weapon rolled overboard from the Number 2 Elevator. The aircraft sank with the pilot and the bomb in 2,700 fathoms (4,940 meters) of water. The bomb has never been recovered. The Department of Defense reported the accident took place “more than 500 miles [805 kilometers] from land” when it revealed the accident in 1981. But Navy documents showed the accident occurred about 80 miles (129 kilometers) east of the Japanese Ryukyu Island chain, approximately 250 miles (402 kilometers) south of Kyushu Island, Japan, and about 200 miles (322 kilometers) east of Okinawa. Japan’s public policy and law prohibit nuclear weapons. (For a video if B43 aircraft carrier handling and A-4 loading, see this video.)

accident_ticonderoga1965
An A-4 Skyhawk with a B43 nuclear bomb under its belly rises on an elevator from the hangar deck to the flight deck on the USS Independence (CV-62) in an undated US Navy photo. In December 1965, a B43 attached to an A-4 rolled off the elevator on the USS Ticonderoga (CVA-14) while the carrier was on its way to Yokosuka in Japan.

Three years later, on May 27, 1968, the nuclear-powered attack submarine USS Scorpion (SSN-589) suffered an accident and sank with all 99 men on board in the Atlantic Ocean approximately 644 kilometers (400 miles) southwest of the Azores. The Department of Defense in 1981 mentioned a nuclear weapons accident occurred in the Atlantic in the spring of 1968 but continues to classify the details. It is thought that two nuclear ASTOR torpedoes were on board the Scorpion when it sank.

accident_scorpion1968
The USS Scorpion (SSN-589) photographed in the Mediterranean Sea in April 1968, one month before it sank in the Atlantic Ocean. The Navy later located and photographed the wreck (inserts).

Risks of Nuclear Incidents

Another kind of risk was that nuclear weapons on board US warships could become involved in offensive maneuvers near Soviet warships that also carried nuclear weapons. Sometimes those nuclear-armed vessels collided – sometimes deliberately. Other times they were trapped in stressful situation. The presence of nuclear weapons could significantly increase the stakes and symbolism of the incidents and escalate a crisis.

Some of the most dramatic incidents happened during the Cuban Missile Crisis in 1962 where crisis-stressed personnel on Soviet nuclear-armed submarines readied nuclear weapons for actual use as they were being hunted by US naval forces, many of which were also nuclear-armed. At the time there were approximately 750 U.S. nuclear weapons deployed in the Atlantic Ocean.

Less serious but nonetheless potentially dangerous incidents continued throughout the Cold War. In May 1974 the nuclear-powered attack submarine USS Pintado (SSN-672) collided almost head-on with a Soviet Yankee I-class ballistic missile submarine while cruising 200 feet (60 meters) below the surface in the approaches to the Petropavlovsk naval base on the Kamchatka Peninsula. The collision smashed much Pintado’s bow sonar, jammed shut a starboard side torpedo hatch, and damaged the diving plane. The Pintado, which probably carried 4-6 nuclear SUBROC missiles, sailed to Guam for seven weeks of repairs. The Soviet submarine, which probably carried its complement of 16 SS-N-6 ballistic missiles with 32 nuclear warheads, surfaced immediately and presumably limped back to port.

accident_pintado1974

On August 22, 1976, for example, US anti-submarine forces in the Atlantic and Mediterranean had been tracking a Soviet nuclear-powered and nuclear-armed Echo II-class attack submarine for ten days. The Soviet sub partially surfaced alongside the US frigate USS Voge (FF-1047), then turned right and ran into the frigate. The collision tore off part the Voge’s propeller and punctured the hull. The Voge is thought to have carried nuclear ASROC anti-submarine rockets. At the time there were around 430 U.S. nuclear weapons deployed in the Mediterranean Sea. The Soviet submarine suffered serious damage to its sail and some to its front hull section. (For a US account of the incident, see here; a Russian account is here.)

Even toward the very end of the Cold War in the late-1980s, nuclear-capable warships continued to get involved in serious incidents at sea. During a Freedom of Navigation exercise in the Black Sea on February 12, 1988, the cruiser USS Yorktown (CG-48) and destroyer USS Caron (DD-970) were bumped by a Soviet Krivak-class frigate and a Mirka-class frigate, respectively. Both U.S. ships were equipped to carry the nuclear-capable ASROC missile and the Caron had completed a series of nuclear certification inspections prior to its departure from the United States. Yet the W44 warhead for the ASROC was in the process of being phased out and it is possible that the vessels did not carry nuclear warheads during the incident. The declassified data shows that the number of U.S. nuclear weapons in the Mediterranean dropped to zero in 1987. The Soviet Krivak frigate, however, probably carried nuclear anti-submarine weapons at the time of the collision.

accident_blacksea1988
The nuclear-capable USS Caron (DD-970) and USS Yorktown (CG-48) are bumped by Soviet frigates during Freedom of Navigation operations inside Soviet territorial waters on February 12, 1988. For a video of the Caron collision, see here, and the Yorktown collision, see here.

Nuclear Diplomacy Headaches

In addition to the risks created by accidents and incidents, nuclear-armed warships were a constant diplomatic headache during the Cold War. Many U.S. allies and other countries did not allow nuclear weapons on their territory in peacetime but the United States insisted that it would neither confirm nor deny the presence of nuclear weapons anywhere. So good-will port visits by nuclear-armed warships instead turned into diplomatic nightmares as protesters battled what they considered blatant violations of the nuclear ban.

The port visit protests were endless, happening in countries all over the world. The national governments were forced to walk a fine line between their official public anti-nuclear policies and the secret political arrangements that allowed the weapons in anyway.

Public sentiments were particularly strong in Japan because it was the target of two nuclear weapon attacks in 1945. Japanese law banned the presence of nuclear weapons on its territory and required consultation prior to introduction, but the governments secretly accepted nuclear weapons in Japanese ports.

During the 1970s and early-1980s, opposition to nuclear ship visits grew in New Zealand and in 1984 culminating in the David Lange government banning visits by nuclear-powered and nuclear-armed vessels. The Reagan administration reacted angrily by ending defense cooperation with New Zealand under the ANZUS alliance. Only much later, during the Obama administration, have defense relations been restored.

afloat_SSN604_Oakland1979
The nuclear-powered and nuclear-armed attack submarine USS Haddo (SSN-604) is barraged by protestors during a port visit to Oakland in New Zealand in 1979.

The treatment of New Zealand was partially intended to deter other more important allies in Europe from adopting similar anti-nuclear legislation. But not surprisingly, the efforts backfired and instead increased opposition. In Denmark the growing evidence that nuclear weapons were actually being brought into Danish harbors despite its clear prohibition soon created political pressure to tighten up the ban. In 1988, this came to a head when a majority in the parliament adopted a resolution requiring the government to inform visiting warships of Denmark’s ban. The procedure did not require the captain to reveal whether his ship carried nuclear weapons, but the conservative government called an election and asked the United States to express its concern.

afloat_DDG17_Aalborg1988
The crew of the nuclear-armed destroyer USS Conyngham (DDG-17) uses high-pressure hoses to wash anti-nuclear protestors off its anchor chain during a standoff in Aalborg, Denmark, in 1988.

Across the Danish Straits in Sweden, the growing evidence that non-nuclear policies were violated in 1990 resulted in the government party deciding to begin to reinforce Sweden’s nuclear ban. The policy would essentially have created a New Zealand situation in Europe, a political situation that was a direct threat to the US Navy sailing its nuclear warships anyway it wanted.

These diplomatic battles over naval nuclear weapons were so significant that many US officials gradually began to wonder if nuclear weapons at sea were creating more trouble than good.

After The Big Nuke Offload

Finally, on September 27, 1991, President George H.W. Bush announced during a prime-time televised address that the United States would unilaterally offload all non-strategic nuclear weapons from its naval forces, bring all those weapons home, and destroy many of them. Warships would immediately stop loading nuclear weapons when sailing on overseas deployments and deployed vessels would offload their weapons as they rotated back to the United States. The offload was completed in mid-1992.

Two years later, the Clinton administration’s 1994 Nuclear Posture Review, decided that all surface ships would lose the capability to launch nuclear weapons. Only selected attack submarines would retain the capability to fire the nuclear Tomahawk land-attack sea-launched cruise missile (TLAM/N), but the weapons would be stored on land. Sixteen years later, in 2010, the Obama administration decided to retire the TLAM/N as well, ending decades of nuclear weapons deployments on ships, attack submarines, and on land-based naval air bases.

After the summer of 1992, only strategic submarines armed with long-range ballistic missiles have carried U.S. nuclear weapons at sea, a practice that is planned to continue through at least through the 2080s. These strategic submarines (SSBNs) have also been involved in accidents and incidents, risks that will continue as long as nuclear weapons are deployed at sea. Because secrecy is so much tighter for SSBN operations than for general naval forces, most accidents and incidents involving SSBNs probably escape public scrutiny. But a few reports, mainly collisions and groundings, have reached the public over the years.

accident_VonSteuben1968
USS Von Steuben (SSBN-632) after collision with tanker Sealady.

During a strategic deterrent patrol on August 9, 1968, the USS Von Steuben (SSBN-632) was struck by a submerged tow cable while operating submerged about 40 miles (64 kilometers) off the southern coast of Spain. As it surfaces, the submarine collides with the tanker Sealady, suffering damage to the superstructure and main deck (see image right). The submarine carried 16 Polaris A3 ballistic missiles with 48 nuclear warheads.

Two years later, on November 29, 1970, a fire breaks out onboard the nuclear submarine tender USS Canopus (AS-34) at the Holy Loch submarine base in Scotland. Two nuclear-powered ballistic missile submarines (USS Francis Scott Key (SSBN-657) and USS James K. Polk (SSBN-645)) were moored alongside Canapus. The Francis Scott Key cast off, but the Polk remained alongside. The fire burns out of control for four hours killing three men. The submarine tender carried nuclear missiles and warheads and the two submarines combined carried 32 Polaris A3 ballistic missiles with a total of 96 nuclear warheads.

Four years later, in November 1974, after having departed from its base at Holy Loch in Scotland, the ballistic missile submarine USS James Madison (SSBN-627) collides with a Soviet submarine in the North Sea. The collision left a nine-foot scrape in the Madison, which apparently dove onto the Soviet submarine, thought to have been a Victor-class nuclear-powered attack submarine. The Madison carried 16 Poseidon (C3) ballistic missiles with 160 nuclear warheads. The Soviet submarines probably carried nuclear rockets and torpedoes. Madison crew members called the incident The Victor Crash. Two days after the collision, the Madison enters dry dock at Holy Loch for a week of inspection and repairs.

accident_madison1974
The missile submarine USS James Madison (SSBN-627) in dry dock in Scotland in 1974 only days after it collided with a Soviet Victor-class nuclear-powered attack submarine in the North Sea.

After nuclear weapons were offloaded from surface ships and attack submarines in 1991-1992, nuclear-armed ballistic missile submarines have continued to run aground or bump into other vessels from time to time.

On September 24, 1993, for example, after conducting a medical evacuation for a suck crew member, the ballistic missile submarine USS Maryland (SSBN-738) ran aground at Port Canaveral, Florida. The submarine was on a strategic deterrent patrol with 24 missiles onboard carrying an estimated 192 warheads. The Maryland eventually pulled free and continued the patrol two days later.

On March 19, 1998, while operating on the surface 125 miles (200 kilometers) off Long Island, New York, the ballistic missile submarine USS Kentucky (SSBN-737) was struck by the attack submarine USS San Juan (SSN-751). The Kentucky suffered damaged to its rudder and San Juan’s forward ballast tank was ruptured. In a typical display of silly secrecy, the Navy refused to say whether the Kentucky carried nuclear weapons. But it did; the Kentucky was in the middle of its 21st strategic deterrent patrol and carried its complement of 24 Trident II missiles with an estimated 192 nuclear warheads.

accident_kentucky1998
In 1998, the USS Kentucky (SSBN-737) carrying nearly 200 nuclear warheads collided with an attack submarine less than 230 miles (378 kilometers) from New York City.

Conclusions and Recommendations

The Obama administration has made an important contribution to nuclear policy by declassifying the documents with official numbers of US nuclear weapons deployed at sea during the Cold War. This adds an important chapter to the growing pool of declassified information about the history of the U.S. nuclear arsenal.

The new declassified information helps us better understand the extent to which nuclear weapons were involved in day-to-day operations around the world. Every day, nuclear-armed warships of the US and Soviet navies were rubbing up against each other on the high seas in gong-ho displays of national determination. Some saw it as necessary for nuclear deterrence; others as dangerous nuclear brinkmanship. Many of those who were on the ships submarines still get goosebumps when they talk about it and wonder how we survived the Cold War. The tactical naval nuclear weapons were considered more acceptable to use early in a conflict because there would be few civilian casualties. But any use would probably quickly have escalated into large-scale nuclear war and the end of the world as we know it.

The declassified information, when correlated with the many accidents and incidents that nuclear-armed ships and submarines were involved in over the years, also helps us remember a key lesson about nuclear weapons: when they are operationally deployed they will sooner or later be involved in accidents and incidents.

This is not just a Cold War lesson: thousands of nuclear weapons are still operationally deployed on ballistic missile submarines, on land-based ballistic missiles, and on bomber bases. And not just in the United States but also in Britain, France, and Russia. Some of those deployed weapons will have accidents in the future. (See here for the most recent)

Moreover, growing tensions with Russia and China now make some ask if the United States needs to increase the role of its nuclear weapons and once again equip aircraft carriers with the capability to deliver nuclear bombs and once again develop and deploy nuclear land-attack sea-launched cruise missiles on attack submarines.

Doing so would be to roll back the clock and ignore the lessons of the Cold War and likely make the current tensions worse than they already are.

Instead, the United States should seek to work with Russia – even though it is challenging right now – to reduce deployed nuclear weapons and jointly try to persuade smaller nuclear-armed countries such as China, India, and Pakistan from increasing the operational readiness of their nuclear forces. That ought to be one thing Russia and the United States could actually agree on.

Background information:

Hans M. Kristensen is the director of the Nuclear Information Project at the Federation of American Scientists where he provides the public with analysis and background information about the status of nuclear forces and the role of nuclear weapons.

The research for this publication was made possible by a grant from the New Land Foundation, and Ploughshares Fund. The statements made and views expressed are solely the responsibility of the authors.

Book Review: Andrew Gordon’s The Rules of the Game

Gordon, Andrew. The Rules of the Game: Jutland and British Naval Command. Annapolis: Naval Institute Press, 2013, reprint ed. 708pp. $34.95

9780141980324

By Captain Dale Rielage

There is always interest, and usually value, in reading what the boss is reading. Since General Al Gray established the Marine Corps reading list in the late 1980s, reading lists have proliferated across the military services. The Marine Corps Library website lists more than twenty. While the original Marine Corps reading list bore General Gray’s own unique stamp, today most military reading lists feel like the product of a committee – because most are – developed with an eye towards representing every facet and constituency in their institution. What has personally informed and moved a thoughtful warrior, however, is more interesting than the consensus of any committee…which is why, for example, Admiral Stavridis’s reading recommendations are always worth taking aboard. Earlier this month, one of my colleagues made reference to the classic work The Rules of the Game. His comment sent me back to my bookshelf. There, in the recent Naval Institute reprint edition, I noticed an epigraph that escaped my attention years ago:

This edition has been brought to publication with the generous assistance of VADM John M. Richardson, USN, Commander, Submarine Force, and VADM Peter H. Daly, USN (ret.) CEO, US Naval Institute, in the interest of helping put this book in the hands of current and future naval professionals.

It is one thing for a book to make an official reading list, but when the (then) future Chief of Naval Operations is willing to help a book to remain in print, it bears a second look. What any particular senior officer saw in this volume I can only speculate, but a couple lost weekends later, it is clear that Rules of the Game speaks to the most profound challenges facing the U.S. Navy.

On the surface, a 600-plus page (708 pages with notes and appendixes) book about the Battle of Jutland seems an unlikely means to examine the established order of U.S. Navy command and control. The fight between the British Royal Navy and the German High Sea Fleet in the North Sea on 31 May and 1 June 1916 was the largest naval battle of World War I. This epic clash of dreadnought battleships is widely regarded as a draw, with neither side achieving clear victory. Gordon, however, turns the Royal Navy at Jutland into a long case study of the role of doctrine, training, centralization, initiative, and institutions in naval warfare. He begins his analysis as the fleet engagement at Jutland is starting, with the Battle Fleet and the Battle Cruiser Fleet, the two key combat formations that comprised the Royal Navy’s Grand Fleet, getting underway from their respective homeports 200 miles from each other. So good was British naval intelligence in this era that the Grand Fleet weighed anchor in response to a planned German sortie more than four hours before the German High Sea Fleet reached the open sea.

As the narrative arrives at the moment enemy forces are in contact and key tactical decisions are being made, Gordon shifts his view back a century. In a 200 page excursion, he introduces the competing naval schools of thought and the resulting institutional habits and personal relationships that led to the British fleet acting as it did at Jutland.

Britain left the Napoleonic Wars with a navy second to none and a tradition of victory built on the aligned independence of Nelson’s band of brothers. Nelson’s famous flag hoist opening Trafalgar was the last he made during that battle – not because of his death, but because he needed no other. Shortly after the war, however, new visual signaling systems promised increasing control over the movements of forces in combat. In peacetime drills, these systems yielded reliable execution of complex maneuvers. However, the reality of how this signals system would work in combat was lost over decades. In the breach, smoke from engineering and gunnery, signal masts and halyards destroyed by gunfire, signalmen lost to shot and shell, and the sheer volume of communications in a fleet engagement would conspire to negate centralized command and control. The promise of centralized control and effective coordinated combat action, however, produced a deep influence on the Royal Navy.

In what Gordon memorably dubbed “the long lee of Trafalgar,” the Royal Navy continued to dominate the seas. Its officers retained the expectation of victory bequeathed them by their predecessors. That there had been no major fleet action in living memory was discussed, but rarely with concern. The French or Russian navies occasionally caused alarm, but no “peer competitor” called into question the fundamentals of the system – the rules of the game.

There was good reason for this comfort. By almost every metric, the Royal Navy in the second half of the nineteenth century was extraordinarily successful. Its officers were masters of seamanship and navigation and created the standard for contemporary and modern navies. Operating forward in defense of a worldwide empire, many Royal Navy officers had seen combat and had demonstrated personal courage and resourcefulness. Beatty, commander of the Battle Cruiser Fleet at Jutland, had earned distinction – and favorably impressed a young Winston Churchill – in littoral action using river gunboats to support ground forces in Egypt. Work to understand and incorporate new technologies proceeded apace, with a limited cadre of specialists articulating the new technology to the fleet at large. There were efforts to change operational culture, most prominently spearheaded by the driven and charismatic Admiral Sir George Tyron. Tyron advocated a looser form of control, emphasizing formations following the Commander’s intent as understood or expressed in the movements of his flagship. His untimely death in a collision at sea – ironically and unfairly blamed on his style of signaling – arrested reform efforts for decades.

Having allowed the German Fleet to avoid decisive battle and escape home, the Royal Navy left the field at Jutland with a sense of failure that grew as the war concluded. Denied the decisive fleet action they expected, senior British commanders engaged in decades of controversy over what signals were sent, received, intended, and expected. This controversy colors any discussion of the battle to this day. Gordon, however, seeks to move this discussion to a more profound level. While individual commanders executed the action at Jutland, their failure to exercise initiative at key moments was not truly an individual act. Indeed, Gordon asserts that the sudden exercise of tactical initiative would have been an unnatural rejection of the culture that had nurtured them through their entire professional lives.

In his final chapter, Gordon draws twenty-eight specific observations from the Jutland experience. They are directed toward the Royal Navy of the early 1990s, but will resonate with serving officers today. Gordon rails against command and control being driven by the tools of information processing. Absent deliberate restraint, every increase in the capacity to transmit information produces an increase in the amount of information transmitted – with the capacity of the senior to send information, rather than the capacity of the junior to assimilate information, driving the flow. The focus too easily becomes getting the mechanisms of communications right, believing that with that information dominance achieved, success in command and control ensues. Ready access to information and the ability to transmit orders raises the level of decision making further from the point of action. When these links fail – today from jamming, cyber attack, or destruction of communications satellites – it is folly to expect naval commanders in combat will suddenly be able to shed the culture in which they have been trained.

Gordon also highlights the difficulty of integrating new concepts and technologies into a peacetime navy. In the Royal Navy of 1900, enthusiasts for new technologies drove the stated purpose and design of new weapons – much like our navy today. Their specialized focus ignored or obscured real operational challenges to their systems. Once a new system or platform arrived in the Fleet, however, its integration and employment became the business of fleet officers who were and are often working from different approaches than the cadre of experts who designed it. As practical naval officers, they rarely set a capability aside as too flawed for use, but rather would often “make the best of it,” sometimes using the ship for an entirely different purpose than intended. At Jutland, the Royal Navy Battle Cruiser Fleet consisted of ships designed to mount heavy guns but limited armor. Their superior speed was intended to allow them to manage their range to more heavily protected enemies. In actual combat, managing this thin envelope of safety proved too difficult. 3,300 British sailors died in these ships – ten percent of all the British sailors who participated in the battle – in what Gordon aptly calls “a costly rediscovery of the designer’s terms of reference.”

That insight brings us to Gordon’s overarching theme – how the Royal Navy dealt with a long peace, technological change, and an emerging German challenge to its comfortable dominance of the maritime domain. It is a short leap to ask to what extent the U.S. Navy remains, to paraphrase, in the long lee of Midway. It is a question the service must be comfortable asking, whether or not the answers are comfortable.

Aside from its impact and insight, The Rules of the Game is delightfully written. Gordon has a knack for memorable turns of phrase and admirable clarity (if not economy) of expression that makes the long journey through his thinking as enjoyable as it is intriguing. Every naval professional’s bookshelf should have a well-thumbed copy of this volume.

Captain Rielage serves as Director for Intelligence and Information Operations for U.S. Pacific Fleet, the headquarters where the Midway operation was commanded and controlled. He has served as 3rd Fleet N2, 7th Fleet Deputy N2, Senior Intelligence Officer for China at the Office of Naval Intelligence and Director of the Navy Asia Pacific Advisory Group. His opinions do not represent those of the U.S. Government, Department of Defense, or Department of the Navy.

Twenty-Eight Observations from The Rules of the Game
by Andrew Gordon

Lessons from the Battle of Jutland
31 May to 1 June 1916

1) In times of peace, empirical experience fades and rationalist theory takes its place.
2) The advent of new technology assists the discrediting of empirical doctrine.
3) The purveyors of new technology will be the most evangelizing rationalists.
4) Rationalism, unlike empiricism, tends to assume an accretion of vested interests.
5) The training establishment may try to ignore short bouts of empirical experience to preserve its ‘rationalist’ authority.
6) Military cultures impart doctrine by corporate ambience as much as by explicit teaching.
7) In long periods of peace, ‘ambient’ doctrine may be no more than the habits of years in which war has been forgotten.
8) If doctrine is not explicitly taught, vested interests will probably ensure that wrong doctrine is ambiently learned.
9) In peacetime, doctrine is vulnerable to commandeering by ‘systems lobbyists.’
10) Innovations adopted in accordance with peacetime doctrine may lock the Fleet into both systems and doctrine which will fail the empirical test of war.
11) Purveyors of technical systems will seek to define performance criteria and trials conditions.
12) A service which neglects to foster a conceptual grasp of specialized subjects will have too few warriors able to interrogate the specialists.
13) The volume of traffic expands to meet capacity.
14) Signals ‘capacity’ tends to be defined by how much the senior end can transmit rather than how much the junior end can conveniently assimilate.
15) Signal prioritizing mechanisms become dislocated in times of overload.
16) Incoming traffic can act as a brake on decision-making.
17) The more signals, the more the sun shines on signalers.
18) The ‘center’ must subject its own transmissions to the strictest self-denying ordinance.
19) Signaling promotes the centralization of authority.
20) There is an inverse law between robust doctrine and the need for signaling.
21) Heavy signaling, like copious orders, is symptomatic of doctrinal deficiency.
22) The promise of signaling fosters a neglect of doctrine.
23) War-fighting commanders may find themselves bereft of communications faculties on which they have become reliant in peacetime training.
24) Properly disseminated doctrine offers both the cheapest and the most secure command-and-control method yet devised by man.
25) Every proven military incompetent has previously displayed attributes which his superiors rewarded.
26) Peacetime highlights basic ‘primary’ skills to the neglect of more advanced, more lateral ‘secondary’ abilities, the former being easier to teach, easier to measure, and more agreeable to superiors.
27) The key to efficiency lies in the correct balance between organization and method.
28) Doctrine draws on the lessons of history.