Jump to content

Indian Ocean raid

From Wikipedia, the free encyclopedia
(Redirected from Operation C)
"Operation C" redirects here. For the 1991 video game, see Operation C (video game).
For the later Japanese raid, see Indian Ocean raid (1944).

Indian Ocean raid
Part of the Pacific Theatre of World War II

British heavy cruisers HMS Dorsetshire and Cornwall under Japanese air attack and heavily damaged on 5 April 1942.
Date31 March – 10 April 1942
Location
Indian Ocean and British Ceylon
Result Japanese victory
Belligerents

 United Kingdom

 Australia
Netherlands
 United States
 Canada		 Empire of Japan Japan
Commanders and leaders
United Kingdom James Somerville Empire of Japan Chūichi Nagumo[1]
Empire of Japan Mitsuo Fuchida
Units involved
United Kingdom Eastern Fleet Empire of Japan Combined Fleet
Strength
2 carriers
1 light carrier
5 battleships
7 cruisers
15 destroyers
7 submarines
100+ aircraft
30 smaller warships
50+ merchant ships.		 5 carriers
1 light carrier
4 battleships
11 cruisers
23 destroyers
5 submarines
275 aircraft
Casualties and losses
1 light carrier sunk
2 heavy cruisers sunk
2 destroyers sunk
1 Armed Merchant Cruiser (AMC) sunk
1 corvette sunk
1 sloop sunk
20 merchant ships sunk
54 aircraft destroyed
825 killed		 18 aircraft destroyed
31 aircraft damaged
32 killed

The Indian Ocean raid, also known as Operation C[2] or Battle of Ceylon in Japanese, was a naval sortie carried out by the Imperial Japanese Navy (IJN) from 31 March to 10 April 1942. Japanese aircraft carriers under Admiral Chūichi Nagumo struck Allied shipping and naval bases around British Ceylon, but failed to locate and destroy the bulk of the British Eastern Fleet. The Eastern Fleet, commanded by Admiral Sir James Somerville, was forewarned by intelligence and sailed from its bases prior to the raid; its attempt to attack the Japanese was frustrated by poor tactical intelligence.

Following the attack, the British expected a major Japanese offensive in the Indian Ocean. The main base of the Eastern Fleet relocated to East Africa, and Ceylon was reinforced, but Somerville kept his fast carrier division, Force A, "...in Indian waters, to be ready to deal with any attempt by the enemy to command those waters with light forces only."[3] However, the Japanese had no short-term plans to follow up on their success, and within the year operations in the Pacific made it impossible to do so.

Background

[edit]

Strategic situation

[edit]

The island of Ceylon was strategically important, since it commanded the Indian Ocean. Thus it controlled access to India, the vital Allied shipping routes to the Middle East and the oilfields of the Persian Gulf. Ceylon held most of the British Empire's resources of rubber. An important harbour and naval base, Trincomalee, was located on the island’s eastern coast. Japanese propaganda had an effect on some of the Sinhalese population, who now awaited their arrival.

The fall of Singapore on 15 February 1942 broke the United Kingdom's eastern defensive perimeter of the Bay of Bengal; and the Japanese occupation of the Andaman Islands on 23 March gave Japan control of the Andaman Sea enabling ships to resupply Japanese troops in the Burma Campaign for control of India. Both German and British authorities anticipated Japanese capture of Ceylon to solidify control of the Bay of Bengal and disrupt British resupply for defence of India, Australia, and perhaps the Middle East. Ceylon was hastily garrisoned by Australian troops returning from North Africa; and HMS Indomitable was relieved of naval duties to serve as a high-speed aircraft ferry shuttling available planes to Ceylon.[4]

Japanese intentions to mount a major offensive into the Indian Ocean were placed on hold in March 1942; strong naval forces were needed in the western Pacific against the United States, and the Imperial Japanese Army (IJA) refused to allocate troops for an invasion of Ceylon. In response, the IJN developed Operation C, a plan for an aggressive raid into the Indian Ocean in early April. Operation C aimed to destroy the British Eastern Fleet, and disrupt British lines of communications in the Bay of Bengal in support of the Burma Campaign.[2]

British intelligence correctly assessed the Japanese strategy. The Americans were notified; the Doolittle Raid – which was already in progress – took on the additional role of a diversion.[2]

Japanese preparations

[edit]

Admiral Isoroku Yamamoto issued the initial order to proceed with Operation C to the IJN's southern force, commanded by Admiral Nobutake Kondō, on 9 March 1942. By 16 March, the plan was to depart from Staring Bay, Celebes, on 26 March for an attack on Colombo ("C day") on 5 April.[5] The Japanese expected to destroy the British Eastern Fleet in port.[6]

The Japanese force, commanded by Admiral Chūichi Nagumo, had a core of five aircraft carriers; Akagi, Shōkaku and Zuikaku in Carrier Division 5, and Sōryū and Hiryū in Carrier Division 2.[1] The carriers were accompanied by all four Kongo-class battleships, and both Tone-class cruisers.[7]

Japanese intelligence on the composition of the British Eastern Fleet in the Indian Ocean[8] was reasonably accurate,[6] while overestimating the air strength on Ceylon.[6] The 19 March operational order vaguely advised that a "considerable" portion of British naval and air forces in the Indian Ocean were "deployed in Ceylon area".[8]

The Japanese stationed reconnaissance submarines outside of the known British anchorages at Colombo and Trincomalee; their effectiveness was limited.[9] At least one submarine was sent to scout the Maldive Islands but failed to detect Port T at Addu Atoll.[10]

At the same time as Operation C, the IJN also dispatched Malay Force under the command of Vice Admiral Jisaburō Ozawa. His force consisted of the aircraft carrier Ryūjō, six cruisers, and four destroyers to destroy shipping in the Bay of Bengal on 1 April. Malay Force was not part of Operation C.[11]

In 3 days, Ozawa's force managed to sink 23 merchant ships (20 in a single day),[12] totaling over 130,000 gross registered tons.[13] In addition, April saw 32,000 tons of shipping sunk by Japanese submarines off India's west coast.[12] Ryūjō's aircraft also bombed the ports of Cocanada and Vizagapatam, causing relatively minor damage.[12] The tonnage and number of ships sunk by Malay Force, are comparable to that of the 3-month long Operation Berlin raid conducted by two battleships of the Kriegsmarine from January to March 1941.[14] In both raids against merchant shipping, Allied merchant ships were not sailing in convoys escorted by large vessels.[15]

British preparations

[edit]
Japanese operation in the Northern Indian Ocean and Bay of Bengal in 1942. Nagumo's forces are shown at the bottom of the map.

The reinforcement of the British Eastern Fleet depended on transfers from Britain and the Mediterranean, a reflection of active warzones and the demands on the Royal Navy's (RN) resources.

In late-December 1941, a reassessment of the threat posed by Japan envisioned transferring the majority of the RN's heavy units to the Eastern Fleet. Matters were made urgent by the crippling of the United States Pacific Fleet's battle line at Pearl Harbor, which exposed the weak forces in Malaya to attack. Heavy units were freed up by American reinforcements in the Atlantic. The construction programs of the late-1930s were also starting to yield new heavy units. The Mediterranean yielded far fewer reinforcements than expected due to serious losses in that theatre in 1941.[16]

The Eastern Fleet that Vice Admiral Sir James Somerville assumed command of in March 1942 was smaller than what had been envisioned in December 1941. Somerville divided the fleet into two groups, based on speed. The faster "Force A" included the aircraft carriers HMS Formidable and HMS Indomitable, the modernized battleship HMS Warspite (as flagship), as well as the modern cruisers and destroyers. The slower "Force B" was formed around the old carrier HMS Hermes and four unmodernized Revenge-class battleships. A few submarines were also available.[17][10][18][19] The ships had never operated together before, and both ship and air crews were deficient in training.[17]

Allied intelligence accurately assessed the strength of the Japanese force.[5] Somerville planned to evade the Japanese during the day and close to launch torpedo strikes with radar-equipped Fairey Albacore bombers during the night.[10] However, the plan was based on information provided by the Far East Combined Bureau (FECB), which identified only two carriers in the Japanese force. FECB also believed the Japanese would sail from Staring Bay on 21 March for a "C day" of 1 April. Thus, Somerville sailed early expecting to fight a smaller and manageable enemy force, particularly in aircraft strength.[5] As such, Somerville likely did not see his plan as incompatible with his orders from the Admiralty, which were to protect the lines of communications in the Indian Ocean, and to maintain the Eastern Fleet as a fleet in being by avoiding unnecessary risks.[5]

The British recognized the threat of Japanese carrier-borne air attack on Ceylon after the strike on Pearl Harbor, and the island's air defences were reinforced. On 7 December 1941, air defences consisted of four obsolescent three-inch anti-aircraft guns – at Trincomalee – with neither fighters nor radar.[20] By 4 April, there were 67 Hawker Hurricanes and 44 Fairey Fulmar fighters, a radar station each at Colombo and Trincomalee, and 144 anti-aircraft guns;[21] 37 or 38 Hurricanes were serviceable around Colombo on 5 April.[22] The fighters were divided into three Royal Air Force (RAF) squadrons of Hawker Hurricanes (two at Colombo, and one at Trincomalee), and two squadrons of RN Fleet Air Arm (FAA) Fairey Fulmars.[23] In the same time frame, other air forces increased from eight obsolete torpedo bombers,[20] to seven Consolidated PBY Catalina flying boats, 14 Bristol Blenheim IV bombers, and 12 Fairey Swordfish torpedo bombers.[22] On the eve of battle, RAF forces were part of 222 Group, commanded by Air Vice-Marshal John D'Albiac.[24]

Raid

[edit]

First moves

[edit]
The Japanese strike force advancing to the Indian Ocean, 30 March. Ships shown from left to right are: Akagi, Sōryū, Hiryū, Hiei, Kirishima, Haruna, and Kongō. Taken from Zuikaku.

The Japanese sailed from Staring Bay on 26 March as planned.[7]

Somerville sailed on 30 March in expectation of an attack on 1 April, and deployed his fleet in a patrol area 100 miles (160 km) south of Ceylon.[25] Ceylon air defences and forces went on alert,[26] with land-based aerial reconnaissance concentrating on the southeast, where the Japanese were expected to approach to launch strikes at Colombo and Trincomalee.[25] Late on 2 April, the British retired toward Port T – 600 miles (970 km) southwest of Ceylon – to refuel.[25] Somerville also detached various ships to resume previous commitments; the heavy cruisers HMS Cornwall and HMS Dorsetshire were sent to Colombo, and Hermes to Trincomalee.[10] Air defences stood down, although Catalina patrols continued.[26]

At about 16:00 on 4 April, PBY Catalina flying boat (AJ155/QL-A) from the Royal Canadian Air Force's (RCAF) 413 Squadron flown by Squadron Leader Leonard Birchall spotted Nagumo's fleet 360 mi (310 nmi; 580 km) south-east of Ceylon[24][25] on a course that would have entered Somerville's previous patrol area from the south.[27] The Catalina transmitted the sighting, but not the size of the fleet, before being shot down.[25] At this time, Somerville was refuelling at Port T; Force A sailed eastward toward the Japanese upon receiving the sighting;[10] Force B could not be ready until 5 April.[23] Catalina FV-R from 205 Squadron RAF took off at 17:45 to shadow the Japanese fleet, making its first report at 22:37 on 4 April, and a final report at 06:15 on 5 April while 110 mi (96 nmi; 180 km) from Ceylon. FV-R was shot down about 90 minutes after the final report.[24]

Within an hour of QL-A's report, D’Albiac met with his subordinates to discuss an anticipated Japanese strike after dawn. 222 Group issued a warning to subordinate units before midnight, and units went on alert at 04:00 on 5 April.[24][28] On the morning of 5 April, six Swordfish from 788 Naval Air Squadron (788 NAS) began relocating from China Bay, near Trincomalee, to Colombo, in preparation for a strike on the Japanese fleet.[29] Admiral Geoffrey Layton, on Ceylon, ordered ships put to sea to avoid being attacked in harbour. Cornwall and Dorsetshire, which had just reached Colombo, were sent to rejoin Force A;[23] they sailed late on 4 April.[30] Hermes sailed from Trincomalee and was ordered to hide northeast of Ceylon.[23]

The Japanese did not perform an aerial reconnaissance sweep along their intended course on the afternoon of 4 April, and a planned reconnaissance of Colombo harbour by cruiser floatplanes was cancelled.[9] The Japanese realized surprise was lost after intercepting a signal from Colombo asking QL-A to repeat its report.[31]

Attack on Colombo

[edit]
Main article: Easter Sunday Raid

Japanese intelligence on the morning of 5 April 1942 indicated that British carriers were absent, and the Japanese morning air search was limited accordingly.[8] At dawn, Japanese aerial reconnaissance aircraft flew off to the south-west and north-west; they would fly out to a maximum of 200 miles (320 km) over the next few hours. A reconnaissance Fulmar launched from Force A at 08:00 spotted one of the Japanese aircraft at the extreme edge of the south-west search area at 08:55 about 140 miles (230 km) ahead of Force A.[32]

Shortly after 06:00[33] Nagumo's force began launching 91 bombers and 36 fighters for the strike on Colombo.[23] British early warning failed to detect and identify the incoming strike,[34] forcing British pilots to scramble under fire when the first Japanese aircraft appeared over them at 07:45. The effective defence of the Ratmalana airbase by British fighters[35] left the harbour exposed. The armed merchant cruiser HMS Hector,[36] the Norwegian tanker Soli[37] and the old destroyer HMS Tenedos were sunk; three other ships were damaged. The port was damaged[36] but was not put out of action.[23] 20 of the 41 British fighters that took off were destroyed.[20] At least one fighter was damaged and made incapable of flight while attempting to take off. The six Swordfish of 788 NAS arrived during the battle and were shot down.[29] The Japanese lost seven aircraft.[20]

Nagumo changed course to west-southwest at 08:30[33] – unknowingly causing the opposing fleets to steam toward one another[1] – and recovered the Colombo strike from 09:45 to 10:30.[1]

The size of the airstrike on Colombo was Somerville's first concrete evidence that the Japanese force contained more than the two carriers he expected. Nonetheless he continued to steam toward the enemy at 18 knots. Radar-based fighter direction would allow Force A to avoid surprise attack by neutralizing shadowing Japanese aircraft.[32]

Loss of Dorsetshire and Cornwall

[edit]
HMS Cornwall burning and sinking on 5 April 1942

At 10:00, an aircraft from Tone searching the southwest area spotted and began shadowing Dorsetshire's force; the aircraft reported that the cruiser was heading southwest and making 24 knots.[1] The cruisers reported the shadower, but had no means to drive it off.[30] Nagumo increased speed from 24 to 28 knots upon receiving the sighting. Carrier Division 5's reserve strike force was ordered rearmed with anti-ship torpedoes, replacing the high explosive bombs intended for a second strike on Colombo. The rearming encountered delays, and the strike was carried out by Carrier Division 2 instead; Soryu and Hiryu began launching dive bombers at 11:45.[1] Force A radar detected the air strike on Dorsetshire's force at 13:44, putting the aircraft 34 miles (55 km) to the northeast.[32] Cornwall and Dorsetshire were sunk at 1400;[38] ultimately 424 officers and crew were lost.[30]

The Japanese missed an opportunity to find Force A after sinking the cruisers. The aircraft shadowing the cruisers flew another 50 miles (80 km) along the cruisers' course before returning to Tone. It would have detected Force A if it had flown southwest another ten minutes.[38]

Nagumo recovered the strike against the cruisers at 14:45.[38]

Nagumo evades Somerville

[edit]

Somerville launched four Albacores from Indomitable at 14:00 to search an arc to the northeast out to 200 miles (320 km). Nagumo's southeasterly course would have taken the Japanese fleet right through the centre of the arc. However, at 15:00 or 15:30, Nagumo changed course to the southwest. Carrier Division 2 did not immediately follow; it performed a series of kinking manoeuvres starting at 15:00 that initially took it northwest.[38] Carrier Division 2 was spotted by the two northerly Albacores around 16:00. Hiryū launched Mitsubishi A6M Zero fighters to intercept the scouts; one Albacore was damaged at 16:04, and the other shot down at 16:28 without reporting.[39] The two southernmost Albacores missed Nagumo's main body.[38]

Somerville did not receive the damaged Albacore's sighting report until 16:55; the report gave the position of Carrier Division 2 with reasonable accuracy, placed the Japanese 125 miles (201 km) away, but contained no other data. At 17:00 he received signals intelligence (SIGINT) from Colombo reporting the Japanese course at 14:00 as southwesterly at 24 knots. Somerville ordered a course change to the southwest at 17:26, not knowing that Nagumo's main body was 120 miles (190 km) away, and that Carrier Division 2 was only 100 miles (160 km) away. The course change was presumably to maintain distance between a superior enemy that was believed to be still closing, or to cover Port T from attack, but it also meant the British lost an opportunity to meet the enemy; had Force A continued on its easterly course, Carrier Division 2 would have passed right in front of it at 21:00 at range of about 20 miles (32 km).[39]

The damaged Albacore landed at 17:45, less than a half-hour before sunset, and the crew was debriefed. There were two resulting revisions to the 16:00 sighting, which were transmitted to Somerville at 18:00 and 18:17 respectively, and differed significantly from the other and the original report. The final revision correctly identified the two carriers of Carrier Division 2 – which Somerville likely realized to be only part of the enemy force – but also claimed they were heading toward the northwest at a position 25 miles (40 km) or the original sighting. The course heading conflicted with the first revision, which suggested a course toward the southeast. Late on 5 April, FECB decrypted a JN 25B message containing Nagumo's planned movement on 6 April, but this did not aid Somerville as the transmission to the fleet was garbled. Somerville declined to launch a strike based on poor information, and opted to head northwest in pursuit. One radar-equipped aircraft was launched to search a northern arc out to 200 miles (320 km). Later, aircraft were sent to search the easterly arc. By this time it was too late to reestablish contact with the Japanese.[40]

For the Japanese, too, there was a lost opportunity to find the British before night fell. Nagumo did not order a search for the British carriers at the appearance of British carrier-based aircraft. Search aircraft might require homing signals from the carriers to return, homing signals which the enemy could use to locate the Japanese. The Japanese continued southeast at 20 knots completely unaware of the presence of Force A.[41] Carrier Division 2 rejoined the main body's track at 18:00,[42] and caught up at 22:00 180 miles (290 km) due east of Force A.[40] The Japanese circled wide to the south and then east in preparation for striking Trincomalee.[30] The Japanese suspected the presence of British carriers, and on the morning of 6 April they launched a much denser[8] westward[43] air search, but found nothing.[8] Further searches on route to Trincomalee were equally unsuccessful as the British carriers were by that time far to the west.[30]

By 6 April, British SIGINT indicated the Japanese force contained four carriers and three battleships, a force Somerville clearly realized as beyond the Eastern Fleet's capability to engage without undue risk. The declining serviceability of his fighter force also reinforced his caution.[44] Even so, Somerville did not immediately withdraw or return to port. Force B rejoined early on 6 April. In the afternoon 1,122 survivors[30] from Dorsetshire's force were recovered, while maintaining a look-out for the superior enemy force with all-around air reconnaissance.[45] Intelligence from Ceylon put the Japanese between Port T and Ceylon. Somerville cautiously arrived at Port T from the west at 11:00 on 8 April and refuelled.[30]

Attack on Trincomalee

[edit]

By 8 April, the Eastern Fleet had withdrawn[30] and the Japanese fleet was approaching Trincomalee from the east.[46][47] The Japanese fleet was detected by a RAF Catalina at 15:17 on 8 April.[47] The harbour at Trincomalee was cleared that night. Hermes, escorted by HMAS Vampire, was sent south along the coast.[46]

The Japanese air search on the morning of 9 April was limited as on 5 April, as British carriers were no longer expected.[8]

The Japanese strike group of 132 aircraft was detected at 07:06 on 9 April[47] by the radar of AMES 272 at a range of 91 miles (146 km).[36] The defending fighters - 17 Hurricanes and six Fulmars - took off in time,[47] and inflicted the first kills of the battle when a section of Hurricanes attacked three Zeroes and shot down two.[36] The China Bay airbase and the port were heavily bombed. The monitor HMS Erebus was damaged.[47] SS Sagaing, a merchant ship carrying aircraft and ammunition, was set on fire and abandoned.[48] Eight Hurricanes and a Fulmar were lost,[47] although no serviceable fighters were lost on the ground.[29] The Japanese lost four aircraft.[47]

At 07:16 another Catalina from 413 Squadron RCAF spotted the Japanese fleet, but was shot down while reporting.[49]

Blenheims attack the Japanese carriers

[edit]

Around 10:25, nine unescorted Blenheims from 11 Squadron RAF[49] attacked Nagumo's force. They were not detected inbound by the combat air patrol (CAP). Hiryū spotted the aircraft but failed to relay a warning to the other ships. As a result, the attack achieved total surprise.[50] The bombers unloaded at 11,000 feet (3,353 m)[51] on Akagi; the bombs fell close to the target with no hits.[50] Four bombers were shot down over the carriers by CAP A6M2 Zeroes (two of which were claimed by Kaname Harada), and another by Japanese aircraft returning from the strike on Hermes. In return, a Zero was shot down near the carriers and another in the returning strike.[51] This was the first time a Japanese carrier force had faced a concerted air attack.[50]

Loss of Hermes

[edit]
Hermes sinking after Japanese air attack on 9 April 1942.

Hermes and Vampire were 65 miles (105 km) away when Trincomalee was attacked. At 09:00 they reversed course.[46] Shortly after the end of the attack on Trincomalee, an aircraft from Haruna spotted the ships. 80 Aichi D3A "Val" bombers, held in reserve on the Japanese carriers,[47] attacked starting at 10:35.[49] Both were sunk before noon near Batticaloa.[49][52] Hermes was lost with 307 men after being hit by over forty 500 pounds (230 kg) bombs. Vampire was lost with 8 men. The nearby hospital ship Vita rescued 600 men.[52]

The Japanese attack expanded to nearby ships. The corvette HMS Hollyhock was hit by aircraft from Soryu and sunk with 53 men.[52] Also sunk were the naval auxiliary Athelstone, the tanker British Sergeant, and the cargo ship Norviken.[49]

British land-based Fulmars arrived only after Hermes was sunk. Two Fulmars and four Vals were destroyed.[49]

Nagumo disengaged after recovering the strike on Hermes.[49]

Aftermath

[edit]

British reaction

[edit]

The Japanese inflicted disproportionate damage on the enemy. They damaged port facilities, sank one carrier and two cruisers, destroyed a third of enemy ground-based fighters and nearly all of the enemy ground-based strike aircraft. In addition, 23 merchant ships,[45] totalling 112,312 tons,[46] were sunk, including those by the separate Japanese Malay Force. In return, the Japanese lost only 18 aircraft (six fighters, ten dive-bombers and two high-level bombers), with damage to about 31 more. Conversely, they failed to destroy, or even locate, the main bulk of the British Eastern Fleet.[45]

The British interpreted their position as precarious. Ceylon and the Eastern Fleet were required to safeguard the sea lines of communications through the Indian Ocean. The British expected the Japanese to continue threatening these lines. SIGINT suggested that the Japanese were preparing a deliberate advance across the Indian Ocean.[53] The raid demonstrated that the RAF was too weak to defend Ceylon and the naval anchorages,[3] and that the navy was ill-prepared to meet a Japanese carrier force.[54]

The Eastern Fleet transferred its main base to Kilindini, Kenya in East Africa, temporarily ceding the eastern Indian Ocean to the Japanese; from there it continued contesting control of the central Indian Ocean on better terms.[53] Force A, including its two aircraft carriers, Indomitable and Formidable, retired to Bombay,[3] and Somerville regularly deployed a fast carrier force to the central Indian Ocean over the next six months, during which he operated from or near Ceylon for nearly half that time. On 18 April, naval planning accorded the Eastern Fleet the highest priority for reinforcement, which also included transferring most of the carriers from the Home Fleet and the Mediterranean, with the intention of returning to Ceylon in September.[55]

By June, Ceylon was defended by three RAF squadrons (64 aircraft, plus reserves), three strike squadrons (including one of Beauforts), and much improved radar and anti-aircraft defences.[56] Ground defences were manned by two Australian army brigades.[57]

The invasion scare was short-lived. British intelligence detected the movement of the Japanese carrier force eastward in mid-April, and their deployment in the Pacific in mid-May.[58] After the Battle of Midway in June, it was realized that there was no longer the threat of major Japanese naval activity in the Indian Ocean. In September, British intelligence predicted Japan would go over to the defensive. As a result, the Eastern Fleet was not reinforced as planned and, instead, shrank after early July.[59]

Japanese reaction

[edit]

The Japanese did not exploit their victory as the British feared. The decision to postpone major operations in the Indian Ocean was upheld. The Japanese aircraft carriers required maintenance and replenishment after months of intensive operations,[60] and there was already difficulty in maintaining the strength of frontline air units.[61] Nagumo and officers such as Mitsuo Fuchida (commanding Akagi's air group) felt that the losses inflicted on the British did not justify the loss of experienced Japanese air crews.[62] Japanese attention also lay elsewhere. In early May, Japanese carriers fought the Battle of the Coral Sea in the southwest Pacific,[60] followed in June by the Battle of Midway.[59] In both cases, losses constrained Japanese options further.

In June, the IJA developed a plan for a major offensive in the Indian Ocean, including an invasion of Ceylon. The Germans were advancing in North Africa, which made an Axis link-up in the Middle East attractive. Resource constraints forced the IJN to reject it, especially once the Guadalcanal Campaign started.[59]

Subsequently, the limit of Japanese operations in the Indian Ocean was against trade using submarines and armed merchant cruisers.[63] Notably, a submarine group patrolling off East Africa attacked the harbour at Diego-Suarez, Madagascar, while the Allies were capturing the island.[64] Ironically, the Allies were motivated by fears that the Japanese might establish a base there to attack trade.[56] Overall, Japanese attacks on trade enjoyed some success, but after 1942 the presence of major Japanese naval units in the Indian Ocean virtually ceased.[65]

Criticism of Nagumo

[edit]

Nagumo's leadership has been characterized by Andrew Boyd as rigid and unimaginative, and contributed to the escape of the British Eastern Fleet. The manoeuvring of his fleet was mainly to facilitate strikes on Colombo and Trincomalee; the possibility that the enemy might be at sea was apparently not seriously considered. He failed to appreciate that the direction that Dorsetshire's force was sailing, and the later appearance of British carrier-based aircraft, were related. Furthermore, due to limited aerial reconnaissance, Nagumo had little concrete information of what was around him, especially to his front and exposed flanks. He was not served by the confidence that there was nothing else to be found outside of the few searches made.[6]

The limited air searches conducted at the start of the battle reflected contemporary IJN practice, where the intensity of air searches was scaled according to expected threats. The stronger morning search on 6 April reflected the suspicion that British carriers might be present. The intensity of later air searches dropped off when the British carriers were not found and there was little expectation of encountering them. Ultimately, all navies suffered from inadequate air search planning during this period.[66]

Problems with Japanese carrier operations

[edit]

The raid also provided early examples of problems with Japanese carrier operations. Inadequate aerial reconnaissance failing to locate the enemy fleet in a timely fashion, the difficulty of rearming aircraft for a different mission at short notice, and the penetration of the CAP by enemy aircraft due to the lack of radar-directed fighter control would all recur at the Battle of Midway.[6]

Criticism of Somerville

[edit]

Somerville's leadership was characterized by a willingness to take risks, bordering on recklessness.

The initial deployment of the fleet on 30 March endangered the British fleet in multiple ways. Somerville was relying on radar – manned by inexperienced personnel – to locate the enemy and facilitate night strikes. If the Japanese approached as expected from the southeast and the British failed to find the Japanese before dawn, the distance between the two fleets would be no more than 100 miles (160 km); the British would be detected by Japanese aerial reconnaissance at dawn and be subject to air attack for the entire day. Much the same could have been expected had Somerville still been on station when the Japanese arrived – as they did – from the southwest.[9] Somerville's decision to refuel at Port T – rather than on Ceylon – on 2 April allowed the Eastern Fleet to avoid Nagumo a few days later, and likely saved the Eastern Fleet from destruction.[10]

The failure of the Japanese fleet to appear on 1–2 April led Somerville to mistakenly believe that the entirety, rather than a part, of Allied intelligence concerning Operation C was flawed. As a result he detached Cornwall, Dorsetshire, and Hermes, which were subsequently lost after being sent into areas overflown by Japanese aerial reconnaissance.[10]

Andrew Boyd notes:

[Somerville] underestimated the risks he was running at least up to dusk on 5 April. He drew over-optimistic conclusions from the available intelligence, he grossly underestimated IJN air strength. and he hazarded his fleet in direct contravention of his instructions from the chiefs of staff. Ceylon was not his finest hour.[67]

The disquieted Admiralty broadly agreed.[67]

Somerville faced challenges not experienced by the RN in the Atlantic or Mediterranean. Japanese air superiority made it difficult to scout, close, and attack during the day. Radar-enabled night attack was the only viable offensive option. This was a high-risk strategy. A combination of careful positioning, luck, and Japanese errors nearly produced the preconditions for a strike on the night of 5 April; the enemy was within 125 miles (201 km) – 1-hour flight range in an Albacore – but accurate information on the enemy's vector was missing. Even then, it required experienced air crews to find their targets at night, using radar with a range of just 20 miles (32 km) and new tactics.[68]

References

[edit]

Notes

[edit]
  1. ^ a b c d e f Boyd, p. 373
  2. ^ a b c Boyd, p. 364
  3. ^ a b c Roskill, p. 29
  4. ^ Churchill, Winston (1950). The Hinge of Fate. Boston: Houghton Mifflin Company. pp. 138, 172–178.
  5. ^ a b c d Boyd, p. 366
  6. ^ a b c d e Boyd, p. 381
  7. ^ a b Boyd, p. 367
  8. ^ a b c d e f Tully and Yu, p. 5
  9. ^ a b c Boyd, p. 369
  10. ^ a b c d e f g Boyd, p. 370
  11. ^ Shores, Cull & Izawa, Vol. II, pp. 393, 408–411
  12. ^ a b c Black, Jeremy (2009). "Midway and the Indian Ocean". Naval War College Review. 62 (4): 135. ISSN 0028-1484. JSTOR 26397057.
  13. ^ Warner et al. 1976, p. 154.
  14. ^ Macintyre 1975, pp. 104–106.
  15. ^ Ireland 2004, p. 48.
  16. ^ Boyd, p. 356
  17. ^ a b Boyd, p. 365
  18. ^ Somerville, Sir James. Report of Proceedings (ROP) Of Eastern Fleet – 1942
  19. ^ Roskill, p. 23
  20. ^ a b c d Stuart 2014, p. 33
  21. ^ Stuart 2014, p. 35
  22. ^ a b Stuart 2014, p. 44
  23. ^ a b c d e f Roskill, p. 26
  24. ^ a b c d Stuart 2014, p. 37
  25. ^ a b c d e Boyd, p. 368
  26. ^ a b Stuart 2014, p. 36
  27. ^ Boyd, p. 375
  28. ^ Stuart 2014, p. 38
  29. ^ a b c Stuart 2014, p. 42
  30. ^ a b c d e f g h Roskill, p. 27
  31. ^ Stuart 2006, p. 69
  32. ^ a b c Boyd, p. 372
  33. ^ a b Boyd, p. 371
  34. ^ Stuart 2014, p. 38–41
  35. ^ Stuart 2014, p. 42–43
  36. ^ a b c d Stuart 2014, p. 43
  37. ^ Stuart 2014, p. 47
  38. ^ a b c d e Boyd, p. 374
  39. ^ a b Boyd, p. 377
  40. ^ a b Boyd, p. 379
  41. ^ Boyd, p. 378
  42. ^ Boyd, p. 376
  43. ^ Tully and Yu, p. 6
  44. ^ Boyd, p. 380
  45. ^ a b c Boyd, p. 384
  46. ^ a b c d Roskill, p. 28
  47. ^ a b c d e f g h Stuart 2006, p. 72
  48. ^ Rogers, James (3 April 2018). "Huge World War II shipwreck raised from the depths in massive salvage operation". news.com.au. news.com.au. Retrieved 7 April 2018.
  49. ^ a b c d e f g Stuart 2006, p. 73
  50. ^ a b c Parshall, p. 145
  51. ^ a b Shores 1993, p. 426–427
  52. ^ a b c Hobbs, David (2013). British Aircraft Carriers. Seaforth Publishing. Chapter 7: Hermes. ISBN 978-1-84832-138-0. (ebook)
  53. ^ a b Boyd, p. 385
  54. ^ Boyd, p. 388
  55. ^ Boyd, p. 389
  56. ^ a b Boyd, p. 392
  57. ^ Boyd, p. 391
  58. ^ Boyd, p. 393
  59. ^ a b c Boyd, p. 395
  60. ^ a b Parshall, ch. 1
  61. ^ Parshall, ch. 5
  62. ^ Perrett, Bryan (2014). Why the Japanese lost. Barnsley, UK: Pen & Sword Military. p. 114. ISBN 978-1-78159-198-7.
  63. ^ Boyd and Yoshida, p. 90
  64. ^ Boyd and Yoshida, p. 89
  65. ^ Kowner, Rotem (July 2017). "When Economics, Strategy, and Racial Ideology Meet: Inter-Axis Connections in the Wartime Indian Ocean" (PDF). Journal of Global History. 12 (2). Cambridge University Press: 240. doi:10.1017/S1740022817000067. Retrieved 5 May 2019.
  66. ^ Tully and Yu, pp. 4–8
  67. ^ a b Boyd, p. 383
  68. ^ Boyd, p. 382

Articles

[edit]

Books

[edit]
  • Boyd, Andrew (2017). The Royal Navy in Eastern Waters. Seaforth Publishing. ISBN 978-1-4738-9248-4.
  • Boyd, Carl & Yoshida, Akihiko (2013). The Japanese Submarine Force and World War II. Naval Institute Press. ISBN 978-1-5575-0015-1.
  • Parshall, Jonathan & Tully, Anthony (2005). Shattered Sword: The Untold Story of the Battle of Midway. Dulles, Virginia: Potomac Books. ISBN 1-57488-923-0.
  • Roskill, Stephen (1956). War at Sea 1939–1945, Volume II, the Period of Balance. United Kingdom Military Series. London: HMSO. Retrieved 2 September 2015.
  • Shores, Christopher; Cull, Brian & Izawa, Yasuho (2002). Bloody Shambles, Volume One: The Drift to War to the Fall of Singapore. Grub Street.
  • Macintyre, Donald (1975). Famous fighting ships. Hamlyn. ISBN 978-0-600-35486-4.
  • Warner, Oliver; Bennett, Geoffrey; Macyntire, Donald G.F.W.; Uehling, Franck; Wettern, Desmond; Preston, Antony; Mordal, Jacques (1976). Histoire de la guerre sur mer: des premiers cuirassés aux sous-marins nucléaires. Encyclopédie visuelle Elsevier (in French). Translated from English. Paris Bruxelles: Elsevier Séquoia. ISBN 978-2-8003-0148-8.
  • Ireland, Bernard (2004). Cuirassés du 20e siècle [20th Century Battleships]. Airelles référence (in French). St-Sulpice: Airelles. ISBN 978-2-88468-038-7.
  • Shores, Christopher; Cull, Brian & Izawa, Yasuho (1993). Bloody Shambles, Volume Two: The Defence of Sumatra to the Fall of Burma. Grub Street.

Further reading

[edit]
[edit]
Wikimedia Commons has media related to Indian Ocean raid.

Retrieved from "https://wiki.riteme.site/w/index.php?title=Indian_Ocean_raid&oldid=1252996618"