The destruction of Prince of Wales and Repulse was the first time major capital ships had been sunk solely by aircraft in the open seas while actively defending themselves. Their loss shocked the world and psychologically crippled the British Empire in the Far East. Aside from the historical importance, their sinking also offers lessons relevant to today – especially how these large ships were overtaken by a swarm of small aircraft.
Major capital ships, such as World War II battleships or modern aircraft carriers, are large systems, made up of several interlocking elements that together answer the commands of the leadership. Their large crew sizes and complexities rival the size of corporations, large computer networks, or government agencies. These systems function very well on a large scale, but can be vulnerable to small disruptions in key areas. Alternately, a swarm of small actors moving in coordination can overwhelm and pressure the systems until they crack.
Today, technology and social media increasingly enables small actors to affect large systems. Social media creates “flash mobs” and can quickly mass a group to move toward a common goal, such as the street protests in Cairo that ultimately brought down Egyptian President Hosni Mubarak in 2012. Alternately, a single motivated and skillful hacker can compromise key systems and render serious damage to a large system – much like the Target data compromise in December 2013.
The fate of Force Z is a metaphor to help understand how small actors can destroy larger foes. It also offers lessons applicable to both military and corporate leaders.
The Story of Force Z
In the fall of 1941, Singapore and Malaya represented the keystone of the British Empire in Asia. As tensions rose with Japan, Britain strained to enhance the defenses in this area. British strategy hinged on the entire main fleet arriving from England to assist in the defense of Singapore, and a large naval base had been built on Singapore Island capable of handling the bulk of the Royal Navy. This base was central to the entire defense plan; the stated purpose of the 88,000 troops and 141 aircraft in Malaya was to defend the naval base.
These plans ignored the possibility that the fleet might be busy elsewhere when needed, and Britain faced just this problem in the summer of 1941. Battles in the Atlantic and Mediterranean stretched available modern ships to the limit, with little to spare for Singapore.
After much debate with the Admiralty (who wanted to send four older battleships), Prime Minister Winston Churchill dispatched Prince of Wales, one of his newest battleships, and Repulse, one of his best battlecruisers, under the command of Admiral Sir Thomas S. Phillips, former Vice Chief of the Naval Staff. Rounding out Phillips’ little fleet, designated Force Z, were the British destroyers Electra, Express, Encounter, and Jupiter. Force Z had a dual mission, to defend Singapore and also give the Japanese second thoughts about attacking. Churchill said Force Z was to be a “vague menace” but also confidently declared that Prince of Wales could “catch and kill” any like Japanese ship. To increase the political effect, maximum publicity attended Phillips’ movements to Malaya.
[1]
Force Z’s leadership. Admiral Sir Thomas S. Phillips (right) and his Chief of Staff, Rear Admiral Sir Arthur F. E. Palliser, on the dock at Singapore, 2 December 1941. (Imperial War Museum)
Force Z arrived in Singapore on 2 December 1941 to much fanfare. While his men and ships refitted and acclimated to Southeast Asia, Admiral Phillips flew to Manila to confer with his U.S. counterparts about combined operations. He returned on 7 December 1941 (6 December in Hawaii). The war started the next day in Malaya with the bombing of Singapore and landings at Singora on the Thailand coast.
After consultation with his staff and ship captains, Admiral Phillips decided to sortie and engage the Japanese invasion fleet. Royal Air Force commanders promised reconnaissance on the 9th and 10th, but stated that fighter cover would be unavailable. “We must get on without it,” said Phillips. Prince of Wales and Repulse sailed in company with the destroyers Electra, Express, HMAS Vampire, and HMS Tenedos at twilight on 8 December 1941.[2]
Without air cover, Phillips depended on surprise for success. He sailed northward, hiding in weather as much as possible. Japanese aircraft and submarines detected Force Z the evening of the 9th, and Phillips reluctantly turned for home. Japanese aircraft in Saigon launched a strike, but missed the fleet entirely.
That night Phillips received a report of enemy landings at Kuantan on the Malay coast, and diverted to investigate. A Japanese sub reported Force Z’s location;in response a new airstrike took off at dawn from Saigon. At daybreak on 10 December Force Z scouted Kuantan but found nothing, and Phillips turned east to investigate some suspicious trawlers. At this point the first raiders found Force Z.
At 1107 Repulse‘s Captain William G. Tennant ordered, “Enemy aircraft approaching. Action stations!” Captain John C. Leach gave a similar order on Prince of Wales, as did his counterparts in the destroyers. All ships sped up to 25 knots, opened antiaircraft fire, and began evasive maneuvers. The first group of planes bombed Repulse from 12,000 feet, scoring one minor hit on the boat deck and several near misses. Repulse remained in action, accompanied by cheers from Electra.[3]
The first bombing attack against Force Z, 10 December 1941, seen from a Japanese plane. Repulse (left) has been bombed and taken one hit, while Prince of Wales is maneuvering to starboard. Note the calm sea. (U.S. Navy)
Shortly after the bombers departed, a wave of torpedo planes swarmed. Splitting their effort against both ships, they flew in at 400 feet and launched their torpedoes. On Repulse, Captain Tennant calmly ordered the helm about, deftly maneuvering the battlecruiser out of the way of all torpedoes. After the attack concluded, he proudly signaled Phillips: “We have dodged 19 torpedoes so far, thanks to Providence.”[4]
The flagship was not so lucky. One torpedo hit Prince of Wales’ port side aft at 1144, wrecking both port side screw shafts, flooding much of the port side engineering spaces, and knocking out power to much of the ship. Her speed slowed to 15 knots and she developed an immediate 11-degree list to port. The power loss cut most internal and external communications, and froze many turrets in place; between that and the list, most antiaircraft guns were no longer effective. Pumps stopped working, and the ship’s electric steering failed. Leach hoisted the “Not Under Control” signal. As a 2012 analysis put it, “it had taken just one torpedo and less than half an hour to turn the pride of the British Navy into an unresponsive, indefensible wreck of a ship.”[5]
Captain John C. Leach, HMS Prince of Wales. (Imperial War Museum)
Over in Repulse, Captain Tennant received no messages from the flagship. After reporting the attacks to Singapore, he deliberately slowed Repulse and maneuvered her close to Prince of Wales to render assistance. At this point, more Japanese planes struck from the east. Three torpedoes slammed into Prince of Wales’ starboard side, while Repulse took one hit amidships after dodging attacks from several directions. Another wave of nine aircraft swept in, making a coordinated torpedo attack on Repulse from several directions at once. Repulse took four hits that collectively spelled her doom. Tennant ordered his crew to abandon ship. At 1233 Repulse rolled over and sank.[6]
Prince of Wales meanwhile continued to struggle. The Japanese bombed her again, scoring one hit. All damage after the first torpedo only hastened the inevitable end. Admiral Phillips signaled for Express to take off the wounded and unneeded men. In the midst of this process, Prince of Wales rolled over to port and sank at 1320.
It had taken 85 Japanese planes less than three hours to sink two of Britain’s most powerful ships, at a cost of just three planes destroyed. Destroyers saved 2,081 men from both ships, but 840 perished. Phillips and Leach on Prince of Wales made no effort to save themselves. Tennant of Repulse had the same idea, but his staff physically pulled him away from his post and tossed him into the sea. Most of Phillips’ staff drowned. At a stroke, British naval power in the Far East had been broken.[7]
The Lessons of Force Z
Force Z’s destruction offers much for leaders to study and consider. Both military and organizational leaders can find significant lessons applicable today. This section will examine each in turn.
Military Lessons. Force Z’s fate is a warning to modern naval leaders. Large capital ships require considerable protection at all times, and past performance is no guarantee of future results. Despite several tries, the Germans and Italians had failed to sink British capital ships from the air before December 1941. This record inspired overconfidence; Churchill’s belief in his ships’ ability to defeat the Japanese trickled down to the British wardrooms, affecting strategy and tactics. The sinking’s’ psychological blow was therefore greater.[8]
Today the aircraft carrier is the preeminent capital ship in the world. Possessing one is an expression of naval power, and number of carriers is the yardstick by which major navies are compared – much like battleships had been counted before 1942. The United States Navy has not lost an aircraft carrier sunk or knocked out of combat by enemy action since 1945. Except for the USS Cole (DDG-67) attack in 2000, it has been 25 years since a cruiser or frigate was knocked out – even longer since one was sunk by enemy action. The Navy must be careful that this track record does not create overconfidence and affect strategy and tactical decision making.
Much like Japan fielded an air fleet to help counter British capital ships in 1941, Iran, North Korea, and China are perfecting missiles, submarines, and other countermeasures to neutralize U.S. capital ships. The tactic is not necessarily to sink the enemy, but simply knock them out of action – a “mission kill” or “mobility kill.” The Japanese achieved that with one torpedo hitting the right spot on Prince of Wales, as did terrorists with a single boat against the Cole. Today’s naval thinkers should ponder the implications of those events.
Prince of Wales arriving in Singapore, 2 December 1941. (Imperial War Museum)
A final lesson for military leaders is the effect of peacetime budgeting on the fleet. Because of prewar austerity, Britain did not have enough modern capital ships to answer all the crises it faced during World War II. The Royal Navy’s Captain Russell Grenfell explained: “The people of Britain set their face against spending money on armaments between the wars. They were prepared to back any policy, expedient, or nostrum that offered reduction of such expenditure.” Global conflict stretched the Royal Navy to the breaking point, forcing reuse of many obsolescent World War I-era battleships. These were the ones Churchill rejected sending to Singapore in favor of the more modern Prince of Wales – a gamble of modern quality over older quantity.[9]
Organizational Lessons. Writers like Thomas Friedman and Malcolm Gladwell have pointed out that today’s technology increasingly enables large systems to be taken down by small actors who target key areas or overwhelm by attacks from all directions. The destruction of Force Z shows that this trend is not new.
The modern equivalent of a plane torpedoing Prince of Wales’ engineering is a lone hacker (or small group) exploiting vulnerabilities in critical parts of large networks to gain access and do major damage. To cite just one recent case, the Heartbleed hack in April 2014 did not directly target main systems or databases, but rather the OpenSSL library that encrypts communications between networks and websites. Hacking OpenSSL thus provided access to sites and personal information across a wide spectrum. The result of this one hit on a key system rippled across the Internet, causing major disruption. Russian hackers did something similar when raiding the bitcoin market server in early 2014. The information technology managers working to contain the damage in both cases would understand Prince of Wales’ ordeal.
Computers and social media also enable mass gatherings (real or virtual) to move in a common purpose against a single target – much like how the Japanese attacked Repulse. Viral posts show how quickly information (and misinformation) can spread, creating a mob effect. Social media’s ability to mobilize masses of people has been demonstrated in protests around the world over the past three years, several of which have changed governments.
This mass generation of effort also shows up in the stock market, as smaller traders detect vulnerable corporations and attack them in a mass fashion from all directions. In 2008, short sellers used these methods to target and spiral the stock prices of both Bear Stearns and Lehman Brothers; as their prices fell, other investors began pulling out their money, which overwhelmed those companies to the point of collapse. Morgan Stanley barely survived a similar attack. “Shorts are destroying great companies,” observed CNBC’s Jim Cramer at the time.[10]
The Force Z Solution
The story of Force Z also offers a solution as to how large systems can survive against smaller actors, be they planes, hackers, short sellers, or something else. Passive defense alone does not work; it is impossible to close all vulnerabilities or to anticipate all threats in terms of timing or direction.
The answer is to stay agile and vigilant. HMS Repulse dodged 19 torpedoes due to her maneuverability and the alertness of her bridge crew in spotting the incoming planes. Just as the Japanese released their weapons, Captain Tennant made a hard turn and avoided incoming torpedoes. Prompt and disciplined damage control kept the ship in action after hits. Repulse only succumbed after she voluntarily restricted her mobility to stay by the stricken Prince of Wales.
William G. Tennant of Repulse, shown later as a Vice Admiral. (Imperial War Museum)
In the corporate world, an example of this concept is the famed “fortress balance sheet” strategy, advocated most prominently by JPMorgan Chase’s chief executive, Jamie Dimon. “The fortress balance sheet demands nothing less than full attention to the reality of the situation and a constant focus on the risks,” described one of Dimon’s biographers. It is structurally designed to anticipate threats, operate with discipline, and preserve flexibility through good times and bad. This vigilance enabled JPMorgan Chase to weather the financial hurricane of 2008, while having the ability to acquire several major companies and exploit opportunities to move forward.[11]
Force Z’s Legacy
The sinking of Prince of Wales and Repulse shocked the world and reverberates today. Psychologically, Britain and her regional allies never fully recovered from this blow. Force Z’s destruction “marked, in fact, the end of an epoch; that of British pre-eminence as a sea power,” according to Captain Grenfell. Militarily, the loss of this fleet knocked out the centerpiece of British defense in the Far East.
Suddenly vulnerable, Australia and New Zealand turned to the United States for defense assistance, planting the seeds of today’s alliance. Grenfell explained, “The . . . resultant passing of the command of the south-west Pacific to the Japanese was never redeemed, at least by the British. When redemption came, it was the achievement of the Americans.”[12] This fact continues to influence Asian geopolitics.
Today Prince of Wales and Repulse rest on the floor of the Gulf of Thailand, with naval ensigns attached to each. Passing Royal Navy ships pay their respects. Aside from periodic visits by divers, they and their men sleep undisturbed. These wrecks are monuments to the twilight of the British Empire, but also symbolize much more than that. Leaders should ponder their stories and lessons, for they have much to teach, even from the deep.
Repulse leaving Singapore on the evening of 8 December 1941. (Imperial War Museum)
One reply on “The Lessons of Force Z by Chris Kolakowski”
Aw, this was an extremely good post. Taking a few minutes and actual effort to generate a very good article… but what can I say… I hesitate a lot and don’t seem to get nearly anything done.