This is a good article. Click here for more information.

Battle off Endau

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

The Battle off Endau was a Second World War battle that took place off Endau on 26–27 January 1942. Part of the Battle of Malaya, it was the first major naval engagement since the sinking of the battleship Prince of Wales and the battlecruiser Repulse on 10 December 1941, and the last effort by the Royal Navy to intercept Japanese convoy shipping around the Malay Peninsula.[1]

A Japanese convoy approaching Endau was detected by reconnaissance aircraft on 26 January and was ineffectually attacked multiple times by Allied aircraft as it was landing its troops. The Allies suffered heavy casualties, while the Japanese lost only a single aircraft. The Royal Navy committed two destroyers later that day to break up the Japanese landings, despite the much larger Japanese escort force. Sailing under the cover of darkness, they were able to locate the convoy anchored there without being detected, but could not find the troopships in the darkness. The ships attempted to disengage, but were fired upon by the convoy's escorts and one destroyer was sunk in the early morning hours of 27 January.

Background

The sinking of Prince of Wales and Repulse in the opening stages of the Malayan Campaign left the task of intercepting Japanese convoys in the Gulf of Siam to the submarines of the Royal Netherlands Navy as the surface ships were occupied escorting Allied convoys to and from Ceylon and the Dutch East Indies.[1][2] The Dutch recorded their first success when the troopship Awazisan Maru was sunk off Kota Bharu on 12 December 1941, probably by HNLMS K XII.[3] On 24 December, HNLMS K XVI sank the destroyer Sagiri off the coast of Kuching, Borneo.[4] Several other vessels were also damaged or sunk during the early weeks, but losses were high for the Dutch submarines and they could do little to stem the Japanese advance.[5]

Endau

File:Location Sribuat.png
Seribuat, circled in red; Endau is at far left

An amphibious landing at Mersing was originally planned by the Japanese to sever the lines of communication between the British forces and Singapore, but the Southern Expeditionary Army Group decided to land the rest of the 18th Division at Singora instead,[6] believing that the Allied defences at Mersing were too formidable. Although ground forces captured Endau on 21 January, they lacked the strength to break through the Australian defences at Sungei-Mersing.[1]

On 20 January 1942, a convoy of eleven troopships departed Cam Ranh Bay, Indochina, to unload ground forces at Singora, of which two would proceed to Endau.[7] The two transports, Kansai Maru and Canberra Maru, were carrying troops of the 96th Airfield Battalion, assigned to bring the airfields of Kahang and Kluang into operation.[6] They were escorted by the 1st Escort Unit, which was formed around Torpedo Squadron 3, which consisted of the light cruiser Sendai, flagship of Rear-Admiral Shintarō Hashimoto, and six Fubuki-class destroyers, Fubuki, Hatsuyuki, Shirayuki, Asagiri, Amagiri, and Yūgiri. The squadron was augmented with the five W-1-class minesweepers of the 1st Minesweeper Division, three CH-4-class submarine chasers of the 11th Submarine Chaser Division, and four converted patrol boats.[8]

Air attacks

Malaya Command anticipated that the Japanese force would soon be reinforced by a naval convoy, a suspicion confirmed on 26 January when two Royal Australian Air Force (RAAF) Lockheed Hudson aircraft sighted them 20 miles (32 km) north of Endau.[1] Although they spotted the Japanese convoy at 07:45, their radio transmissions were jammed, and news did not reach higher command until they landed in Singapore at 09:20. The RAF decided to attack the convoy with all available aircraft. The attack had to be delayed until that afternoon, however, to allow the crews of the Vickers Vildebeest and Fairey Albacore torpedo bombers of No. 36 Squadron RAF and No. 100 Squadron RAF to rest after their night missions.[9] The decision to use the elderly Vildebeest biplanes against the ships in daylight came as a shock to the pilots,[6] who had been restricted to the relative safety of night sorties following the first day of the invasion.[10]

Vickers Vildebeest of No. 100 Squadron RAF making a torpedo drop during target practice, c. 1936

The first air attack was carried out by the Vildebeests of Nos. 36 and 100 Squadrons and the Hudsons of Nos. 1 and 8 Squadron RAAF. Twelve Vildebeests and nine Hudson bombers took off from Singapore in the early afternoon of January 26, with a fighter escort composed of twelve Brewster F2A Buffalos and nine Hawker Hurricanes.[11] The Japanese landings on Endau had been in progress for over four hours by the time the planes arrived at 15:00.[6] The Japanese naval force had air cover consisting of 19 Nakajima Ki-27s from the 1st and 11th Squadrons and a single Nakajima Ki-44 fighter.[12] Despite heavy opposition, the two transports were bombed, and men and equipment on the beach were strafed.[13] Five Vildebeests were lost in the attack, including the commanding officer of No. 100 Squadron, while one Ki-27 was shot down.[14]

A second wave set off from Singapore at 16:15, consisting of seven Vildebeests and three Albacores of No. 36 Squadron and two Vildebeests of No. 100 Squadron. They arrived over Endau at 17:30, but their escort of seven Hurricanes and four Buffalos were late and the British biplanes were set upon by ten Ki-27s and two Ki-44s before their escorts could reach them. Five Vildebeests, two Albacores and one Hurricane were lost from this wave.[15] Of the 72 aircrew from Nos. 36 and 100 Squadrons who participated in the raids, 27 were killed, seven were wounded and two were captured. The returning pilots were congratulated by Air Vice-Marshal Paul Maltby, who promised them that further daylight attacks were unnecessary.[16]

A third raid, consisting of six unescorted Hudsons of No. 62 Squadron RAF, flying from Palembang, Sumatra, attacked shortly afterwards, losing two of their number, with their entire crews, to six Ki-27s. A fourth raid, made up of five Bristol Blenheims of No. 27 Squadron RAF, set off from Palembang later in the day, but had only got as far as Singapore by sunset, so aborted the mission.[17] Despite claims to have scored multiple hits on both transports and a cruiser, neither the transports, nor any of their escorts were damaged; the former were hit by splinters that killed 8 and wounded 18, but Sendai and the smaller ships were untouched.[18]

Naval battle

File:Japanese minesweeper MSC4.jpg
The minesweeper W-4 at anchor, July 1930

Rear-Admiral Ernest Spooner, commander of naval forces at Singapore, ordered his only combat-ready warships, the elderly destroyers HMS Thanet and HMAS Vampire, to attack the shipping off Endau later that night. Commander William Moran was captain of Vampire while Thanet was under the command of Lieutenant Commander Bernard Davies. The destroyers departed Singapore at 16:30 with Moran in charge of the two ships and headed north. Initial intelligence reports assessed the Japanese strength defending the convoy as a dozen destroyers, but this was revised downward to a pair of destroyers at 22:55, based on inaccurate reporting by surviving RAF aircrew. The 1st Escort Unit was prepared for a surface attack based on an incorrect intelligence report that two British light cruisers were at sea and Hashimoto oriented his ships' patrol sectors to the north.[19]

Moran led his ships between the Seribuat Archipelago and the coast of Johor in brilliant moonlight and then altered course northeast to search the area north of the archipelago. When dark clouds obscured the moon at 01:51, he turned southwestwards at a speed of 15 knots (28 km/h; 17 mph) for Endau, keeping Tioman Island behind him to ensure that his ships were not silhouetted against the horizon. At 02:37, Vampire saw a Japanese destroyer (probably Amagiri), but was not spotted in return and the Allied ships continued on their course. Three minutes later, they located another Japanese ship (the minesweeper W-4) dead ahead at point-blank range. Moran decided to attack, as discovery was inevitable at such short range, and increased his speed to 25 knots (46 km/h; 29 mph), simultaneously firing two of his three torpedoes at a distance of 600 metres (660 yd). One torpedo missed ahead by 15–20 yards (14–18 m) and the other passed underneath the minesweeper. W-4, in the middle patrol zone, was trying to identify the two destroyers when Moran attacked, but failed to alert any other Japanese ships to the Allied presence in their midst for 20 minutes before giving a location six nautical miles (11 km; 6.9 mi) away. W-4 did not return fire and Moran resumed his search for the transports, reducing his speed again to 15 knots to reduce the visibility of his wakes. A half-hour later, with shallow water approaching, and no transports spotted, the Allied destroyers altered course to the north to clear the shallows and increased speed to 25 knots at 03:13 before turning southeast by east.[20]

At 03:18, Vampire sighted the destroyer Shirayuki off the port bow and another ship astern. Vampire and Thanet made minor course adjustments to fire their torpedoes at Shirayuki at a range of 1,500 yards (1,400 m) – one from Vampire and all four of Thanet's – but all missed as Shirayuki, having spotted the Allied ships at the same time, altered course to come behind the Allied destroyers and then signalled to confirm their identities. Not receiving a reply, the Japanese ship illuminated the Allied ships with her searchlight and finally opened fire at 03:31 despite the smoke screen being laid by both ships. Moran ordered both his ships to return fire with their four-inch guns while retiring southeast at maximum speed. Thanet only fired three volleys from her guns before she was hit in the engine room. The hit fractured both the main and auxiliary steam lines to the engines, causing the ship to go dead in the water and lose all electrical power. Constantly making small changes of course to throw off Japanese gun layers, neither ship hit any Japanese ships during the battle.[21]

Allied and Japanese accounts of the gunnery action are difficult to reconcile, particularly as neither of the Allied destroyers recorded any times after firing their torpedoes at 03:18. Shirayuki fired 18 rounds at Vampire at a range of 4,500 yards (4,100 m) before the muzzle blast from her rear gun mounts tripped the circuit breakers in her main electrical switchboard, causing complete electrical failure throughout the ship. While electrical service was restored within two minutes, the ship had a series of smaller electrical failures that bedeviled her for the next 15 minutes. When she resumed firing, Vampire was no longer visible and Shirayuki targeted Thanet instead at a range of 3,050 metres (10,010 ft), firing 82 rounds at her. Yugiri opened fire at 03:38 at Thanet 4,500 yards (4,100 m) away and both ships observed their target slowing down at 03:45. At that same time, Yugiri radioed Hashimoto that "The enemy is two destroyers" so she had spotted Vampire as she fled, although Yugiri lost sight of Vampire 10 minutes later. Sendai, Fubuki, Asagiri, Amagiri, Hatsuyuki and W-1 all subsequently opened fire, mostly at Thanet, although Vampire reported being under fire for a considerable time. All told, the Japanese ships fired 469 rounds at the Allied destroyers, failing to hit Vampire even once. Shirayuki reported that Thanet had sunk at 04:18 and rescued an officer and 30 ratings from the water; another officer and 11 ratings died in the battle. The Japanese did not pursue[22] and Vampire reached Singapore at 10:00 that morning.[23]

Aftermath

Shirayuki handed over the 30 ratings to troops on Endau the following day. They were never seen again, but are believed to have been executed in retaliation for losses sustained by the Japanese in an ambush by the Australian 2/18th Battalion, which occurred south of Mersing about the same time as the naval action off Endau. Davies, four other officers, and 61 ratings from Thanet managed to reach shore and made their way to Singapore,[23] together with shot down aircrew.[24]

The Japanese were able to finish landing their troops, which may have contributed to the impression of significant forces in front of the Australian defenders and their subsequent withdrawal. The heavy losses suffered by the Allied aircraft and aircrew virtually eliminated their ability to influence the subsequent ground battles.[25] Moran's report on Japanese incompetence at night fighting was the most important result of the battle. Since few details about the subsequent night combats off Java survived, Moran's assessment influenced Allied thinking about the IJN until the stunning victory during the nighttime Battle of Savo Island in August flipped the Allied beliefs about the Japanese ability at night fighting on their heads.[26]

Notes

  1. 1.0 1.1 1.2 1.3 Dull 2007, p. 40
  2. Gill, p. 502
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Rohwer 2005, p. 126
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 Warren 2007, p. 188
  7. Rohwer 2005, p. 137
  8. Cannon, pp. 62–64
  9. Shores, Cull and Izawa 1993, pp. 18–19
  10. Shores, Cull and Izawa 1992, pp. 83–84
  11. Shores, Cull and Izawa 1993, pp. 19–20
  12. Shores, Cull and Izawa 1993, p. 20
  13. Dull 2007, pp. 40–41
  14. Shores, Cull and Izawa 1993, pp. 22–29
  15. Shores, Cull and Izawa 1993, pp. 29–37
  16. Warren 2007, p. 189
  17. Shores, Cull and Izawa 1993, pp. 37–38
  18. Cannon, p. 64
  19. Cannon, pp. 64–65, 69
  20. Cannon, pp. 68–71
  21. Cannon, pp. 70–75, 78–79
  22. Cannon, pp. 71–77
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Shores, Cull and Izawa 1993, pp. 39–42
  25. Wigmore, p. 266
  26. Cannon, p. 79

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.