Japanese destroyer Shikinami (1929)

For the Japanese destroyer Shikinami (1905), see Shikinami-class destroyer. For JDS Shikinami (DD-106), see Ayanami-class destroyer.
Shikinami underway on 13 November 1929.
History
Empire of Japan
Name: Shikinami
Namesake: Japanese destroyer Shikinami (1905)
Ordered: 1923 Fiscal Year
Builder: Maizuru Naval Arsenal
Yard number: Destroyer No. 46
Laid down: 6 July 1928
Launched: 22 June 1929
Commissioned: 24 December 1929
Struck: 10 October 1944
Fate: Sunk in action, 12 September 1944
General characteristics
Class & type: Fubuki-class destroyer
Displacement:
Length:
  • 111.96 m (367.3 ft) pp
  • 115.3 m (378 ft) waterline
  • 118.41 m (388.5 ft) overall
Beam: 10.4 m (34 ft 1 in)
Draft: 3.2 m (10 ft 6 in)
Propulsion:
  • 4 × Kampon type boilers
  • 2 × Kampon Type Ro geared turbines
  • 2 × shafts at 50,000 ihp (37,000 kW)
Speed: 38 knots (44 mph; 70 km/h)
Range: 5,000 nmi (9,300 km) at 14 knots (26 km/h)
Complement: 219
Armament:
Service record
Operations:

Shikinami (敷波 "Spreading Waves")[1] was the 12th of 24 Fubuki-class destroyers, built for the Imperial Japanese Navy following World War I. When introduced into service, these ships were the most powerful destroyers in the world.[2] They served as first-line destroyers through the 1930s, and remained formidable weapons systems well into the Pacific War.

History

Construction of the advanced Fubuki-class destroyers was authorized as part of the Imperial Japanese Navy's expansion program from fiscal 1923, intended to give Japan a qualitative edge with the world's most modern ships.[3] The Fubuki class had performance that was a quantum leap over previous destroyer designs, so much so that they were designated Special Type destroyers (特型 Tokugata). The large size, powerful engines, high speed, large radius of action and unprecedented armament gave these destroyers the firepower similar to many light cruisers in other navies.[4] Shikinami, built at the Maizuru Naval Arsenal was the second in an improved series, which incorporated a modified gun turret which could elevate her main battery of Type 3 127 mm 50 caliber naval guns to 75° as opposed to the original 40°, thus permitting the guns to be used as dual purpose guns against aircraft.[5] Shikinami was laid down on 6 July 1928, launched on 22 June 1929 and commissioned on 24 December 1929.[6] Originally assigned hull designation “Destroyer No. 46”, she was completed as Shikinami.

The 4th Fleet Incident occurred only a year after her commissioning, and Shikinami was quickly taken back to the shipyards to have her hull strengthened.

Operational history

On completion, Shikinami, along with her sister ships, Uranami, Ayanami, and Isonami, were assigned to Destroyer Division 19 under the IJN 2nd Fleet. During the Second Sino-Japanese War in 1937, Shikinami covered landing of Japanese forces in Shanghai and Hangzhou. From 1940 on, she was assigned to patrol and cover landings of Japanese forces in south China.

World War II history

At the time of the attack on Pearl Harbor, Shikinami was assigned to Destroyer Division 19 of DesRon 3 of the IJN 1st Fleet, and had deployed from Kure Naval District to the port of Samah on Hainan Island, escorting Japanese troopships for landing operations in the Battle of Malaya at the end of 1941.

In January–February, 1942, Shikinami was assigned to the escort of the aircraft carrier Ryūjō as it conducted air strikes in the Java Sea. During the Battle of Sunda Strait on 1 March, Shikinami entered the battle late, but contributed by firing the final torpedo, which sank the United States Navy heavy cruiser USS Houston,[7][8] She escorted troopship convoys from Saigon to Rangoon through the remainder of March. From 13–22 April, she returned via Singapore and Camranh Bay to Kure Naval Arsenal, for maintenance.[9]

On 4–5 June, Shikinami participated in the Battle of Midway as part of Admiral Isoroku Yamamoto’s main fleet. Shikinami sailed from Amami-Ōshima to Mako Guard District, Singapore, Sabang and Mergui for a projected second Indian Ocean raid. The operation was cancelled due to the Guadalcanal campaign, and Shikinami was ordered to Truk instead, arriving in late August. During the Battle of the Eastern Solomons on 24 August, Shikinami escorted the fleet supply group to Guadalcanal. She was assigned to numerous "Tokyo Express" transport missions to various locations in the Solomon Islands in October and November.[10]

During the Second Naval Battle of Guadalcanal on 14–15 November 1942.[11] Shikinami was attached to a scouting force under the command of Rear Admiral Shintarō Hashimoto in the light cruiser Sendai. Shikinami survived the battle without damage, and returned to Kure by the end of the year.

In January 1943, Shikinami escorted a troop convoy from Pusan to Palau and on to Wewak. For the remainder of January–February, she patrolled out of Truk or Rabaul. On 25 February, Shikinami was reassigned to the IJN 8th Fleet.

During the Battle of the Bismarck Sea on 1–4 March, Shikinami escorted a troop convoy from Rabaul to Lae. She survived the Allied air attack on 3 March, which sank her sister ship Shirayuki and rescued Rear Admiral Masatomi Kimura and other survivors.[12] After returning to Kure briefly in March, Shikinami continued to serve in an escort and transport role in the Solomon Islands and New Guinea area through the end of October 1943. At the end of October 1943, Shikinami was refit in Singapore, and assigned to escort of transports between Singapore and Surabaya and Balikpapan for the remainder of the year.

At the end of January 1944, Shikinami escorted the cruisers Aoba, Ōi, Kinu, and Kitakami on a resupply run to the Andaman Islands, and towed the torpedoed Kitakami back to Singapore afterwards. In a month-long refit in Singapore from mid-March-mid-April, additional anti-aircraft guns were fitted. In May–June, Shikinami made numerous escort missions between Singapore, the Philippines and Palau. During a troop transport mission to Biak as flagship for Admiral Naomasa Sakonju, Shikinami came under a strafing air attack, which set fire to her depth charges, which were jettisoned just before they exploded, killing two crewmen and wounding four others. Shikinami continued to escort ships between Singapore, Brunei and the Philippines from June–August, rescuing the survivors of the torpedoed Ōi on 19 July. On 12 September, after departing Singapore with a convoy bound for Japan, Shikinami was torpedoed by the submarine USS Growler 240 nmi (440 km; 280 mi) south of Hong Kong at position 18°16′N 114°40′E / 18.267°N 114.667°E / 18.267; 114.667Coordinates: 18°16′N 114°40′E / 18.267°N 114.667°E / 18.267; 114.667. Eight officers and 120 men rescued by the destroyer Mikura, but her captain — Lieutenant Commander Takahashi — and Rear Admiral Sadamichi Kajioka were killed in action.

On 10 October 1944, Shikinami was removed from the navy list.[13]

Notes

  1. ↑ Nelson. Japanese-English Character Dictionary. Page 461, 540
  2. ↑ Globalsecurity.org. "IJN Fubuki class destroyers".
  3. ↑ Fitzsimons, Illustrated Encyclopedia of 20th Century Weapons and Warfare p.1040
  4. ↑ Peattie & Evans, Kaigun page 221-222.
  5. ↑ F Fitzsimons, Illustrated Encyclopedia of 20th Century Weapons and Warfare (London: Phoebus, 1977), Volume 10, p.1040.
  6. ↑ Nishidah, Hiroshi (2002). "Fubuki class 1st class destroyers". Materials of the Imperial Japanese Navy.
  7. ↑ Muir, Order of Battle - The Battle of the Sunda Strait 1942
  8. ↑ Brown. Warship Losses of World War II
  9. ↑ Nevitt, Allyn D. (1997). CombinedFleet.com "IJN Shikinami: Tabular Record of Movement" Check |url= value (help). Long Lancers. Combinedfleet.com.
  10. ↑ D’Albas. Death of a Navy: Japanese Naval Action in World War II.
  11. ↑ Kilpatrick. Naval Night Battles of the Solomons.
  12. ↑ Hammel. Guadalcanal: Decision at Sea.
  13. ↑ Nishidah, Hiroshi (2002). "Fubuki class destroyers". Materials of the Imperial Japanese Navy.

References

External links

This article is issued from Wikipedia - version of the Sunday, October 11, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.