Battle of the Santa Cruz Islands

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

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

The Battle of the Santa Cruz Islands, fought during 25–27 October 1942, sometimes referred to as the Battle of Santa Cruz or in Japanese sources as the Battle of the South Pacific (南太平洋海戦?), was the fourth carrier battle of the Pacific campaign of World War II and the fourth major naval engagement fought between the United States Navy and the Imperial Japanese Navy during the lengthy and strategically important Guadalcanal campaign. In similar fashion to the battles of Coral Sea, Midway, and the Eastern Solomons, the ships of the two adversaries were rarely in direct visual range of each other. Instead, almost all attacks by both sides were mounted by carrier or land-based aircraft.

In an attempt to drive Allied forces from Guadalcanal and nearby islands and end the stalemate that had existed since September 1942, the Imperial Japanese Army planned a major ground offensive on Guadalcanal for 20–25 October 1942. In support of this offensive, and with the hope of engaging Allied naval forces, Japanese carriers and other large warships moved into a position near the southern Solomon Islands. From this location, the Japanese naval forces hoped to engage and decisively defeat any Allied (primarily U.S.) naval forces, especially carrier forces, that responded to the ground offensive. Allied naval forces also hoped to meet the Japanese naval forces in battle, with the same objectives of breaking the stalemate and decisively defeating their adversary.

The Japanese ground offensive on Guadalcanal was under way in the Battle for Henderson Field while the naval warships and aircraft from the two adversaries confronted each other on the morning of 26 October 1942, just north of the Santa Cruz Islands. After an exchange of carrier air attacks, Allied surface ships were forced to retreat from the battle area with one carrier sunk and another heavily damaged. The participating Japanese carrier forces, however, also retired because of high aircraft and aircrew losses plus significant damage to two carriers. Although a tactical victory for the Japanese in terms of ships sunk and damaged, the loss of many irreplaceable, veteran aircrews would prove to be a long term strategic advantage for the Allies, whose aircrew losses in the battle were relatively low and could be quickly replaced. The high casualties for the Japanese prevented their carrier forces from further significant involvement in the battle for Guadalcanal, contributing to the eventual Allied victory in that campaign.

Background

Lua error in Module:Details at line 30: attempt to call field '_formatLink' (a nil value).

On 7 August 1942, Allied forces (primarily U.S.) landed on Japanese-occupied Guadalcanal, Tulagi, and Florida Islands in the Solomon Islands. The landings on the islands were meant to deny their use by the Japanese as bases for threatening the supply routes between the U.S. and Australia, and to secure the islands as starting points for a campaign with the eventual goal of neutralising the major Japanese base at Rabaul while also supporting the Allied New Guinea campaign. The landings initiated the six-month-long Guadalcanal campaign.[1]

After the Battle of the Eastern Solomons from 24–25 August, in which the aircraft carrier USS Enterprise was heavily damaged and forced to travel to Pearl Harbor, Hawaii, for a month of major repairs, three U.S. carrier task forces remained in the South Pacific area. The task forces included the carriers USS Wasp, Saratoga, and Hornet plus their respective air groups and supporting surface warships, including battleships, cruisers, and destroyers, and were primarily stationed between the Solomons and New Hebrides (Vanuatu) islands. At this location, the carriers were charged with guarding the line of communication between the major Allied bases at New Caledonia and Espiritu Santo, supporting the Allied ground forces at Guadalcanal and Tulagi against any Japanese counteroffensives, covering the movement of supply ships to Guadalcanal, and engaging and destroying any Japanese warships, especially carriers, that came within range.[2]

USS Wasp burns after being torpedoed on 14 September

The area of ocean in which the U.S. carrier task forces operated was known as "Torpedo Junction"[3] by U.S. forces because of the high concentration of Japanese submarines in the area.[4]

On 31 August, USS Saratoga (CV-3) was torpedoed by Japanese submarine I-26 and was out of action for three months for repairs.[5][6] On 14 September, USS Wasp (CV-7) was hit by three torpedoes fired by Japanese submarine I-19 while supporting a major reinforcement and resupply convoy to Guadalcanal and almost engaging two Japanese carriers Shōkaku and Zuikaku (which withdrew just before the two adversaries came into range of each other's aircraft). With power knocked out from torpedo damage, Wasp's damage-control teams were unable to contain the ensuing large fires, and she was abandoned and scuttled.[7]

Although the U.S. now had only one operational carrier (Hornet) in the South Pacific, the Allies still maintained air superiority over the southern Solomon Islands because of their aircraft based at Henderson Field on Guadalcanal. However, at night, when aircraft were not able to operate effectively, the Japanese were able to operate their ships around Guadalcanal almost at will. Thus, a stalemate in the battle for Guadalcanal developed, with the Allies delivering supplies and reinforcements to Guadalcanal during the day, and the Japanese doing the same by warship (called the "Tokyo Express" by the Allies) at night, with neither side able to deliver enough troops to the island to secure a decisive advantage. By mid-October, both sides had roughly an equal number of troops on the island.[8] The stalemate was briefly interrupted by two large-ship naval actions. On the night of 11/12 October, a U.S. naval force intercepted and defeated a Japanese naval force en route to bombard Henderson Field in the Battle of Cape Esperance. But just two nights later, a Japanese force that included the battleships Haruna and Kongō successfully bombarded Henderson Field, destroying most of the U.S. aircraft and inflicting severe damage on the field's facilities.[9] Although still marginally operational, it took several weeks for the airfield to recover from the damage and replace the destroyed aircraft.

Enterprise conducts air operations in the South Pacific on 24 October 1942. The aircraft pictured is an F4F Wildcat.

At this time, the U.S. made two moves to try to break the stalemate in the battle for Guadalcanal. First, repairs to Enterprise were expedited so that she could return to the South Pacific as soon as possible. On 10 October, Enterprise received her new air groups; on 16 October, she left Pearl Harbor; and on 23 October,[10] she arrived back in the South Pacific and rendezvoused with Hornet and the rest of the Allied South Pacific naval forces on 24 October, 273 nmi (506 km; 314 mi) northeast of Espiritu Santo.[11]

Second, on 18 October, Admiral Chester Nimitz, Allied Commander-in-Chief of Pacific Forces, replaced Vice Admiral Robert L. Ghormley with Vice Admiral William Halsey, Jr. as Commander, South Pacific Area: this position commanded Allied forces involved in the Solomon Islands campaign.[12] Nimitz felt that Ghormley had become too myopic and pessimistic to lead Allied forces effectively in the struggle for Guadalcanal. Halsey was reportedly respected throughout the U.S. naval fleet as a "fighter."[13] Upon assuming command, Halsey immediately began making plans to draw the Japanese naval forces into a battle, writing to Nimitz, "I had to begin throwing punches almost immediately."[14]

The Japanese Combined Fleet was also seeking to draw Allied naval forces into what was hoped to be a decisive battle. Two fleet carriers—Hiyō and Junyō—and one light carrier—Zuihō—arrived at the main Japanese naval base at Truk Atoll from Japan in early October and joined Shōkaku and Zuikaku. With five carriers fully equipped with air groups, plus their numerous battleships, cruisers, and destroyers, the Japanese Combined Fleet, directed by Admiral Isoroku Yamamoto, was confident that it could make up for the defeat at the Battle of Midway.[15] Apart from a couple of air raids on Henderson Field in October, the Japanese carriers and their supporting warships stayed out of the battle for Guadalcanal in the northwestern area of the Solomon Islands, waiting for a chance to approach and engage the U.S. carriers. With the Japanese Army's next planned major ground attack on Allied forces on Guadalcanal set for 20 October, Yamamoto's warships began to move towards the southern Solomons to support the offensive and to be ready to engage any Allied (primarily U.S.) ships, especially carriers, that approached to support the Allied defenses on Guadalcanal.[16]

Prelude

From 20–25 October, Japanese land forces on Guadalcanal attempted to capture Henderson Field with a large-scale attack against U.S. troops defending the airfield. However, the attack was decisively defeated with heavy casualties for the Japanese during the Battle for Henderson Field.[17]

Incorrectly believing that the Japanese army troops had succeeded in capturing Henderson Field, a force of Japanese warships approached Guadalcanal on the morning of 25 October to provide further support for the army offensive. Aircraft from Henderson Field attacked the convoy throughout the day, sinking the light cruiser Yura and damaging the destroyer Akizuki.[18]

Map of the Battle of the Santa Cruz Islands, 26 October 1942. Red lines are Japanese warship forces and black lines are U.S. carrier forces. Numbered yellow dots represent significant actions in the battle.

Despite the failure of the Japanese ground offensive and the loss of Yura, the rest of the Combined Fleet continued to maneuver near the southern Solomon Islands on 25 October with the hope of encountering Allied naval forces in battle. The Japanese naval forces now consisted of four carriers, because Hiyō had suffered an accidental, damaging fire in her engine room on October 22 that forced her to return to Truk for repairs.[19]

The Japanese naval forces were divided into three groups: The "Advanced" force consisted of the carrier Junyō, plus two battleships, four heavy cruisers, one light cruiser, and 10 destroyers, and was commanded by Vice Admiral Nobutake Kondō in heavy cruiser Atago;

the "Main Body" consisted of Shōkaku, Zuikaku, and Zuihō plus one heavy cruiser and eight destroyers, and was commanded by Vice Admiral Chuichi Nagumo aboard Shōkaku;

the "Vanguard" force contained two battleships, three heavy cruisers, one light cruiser, and seven destroyers, and was commanded by Rear Admiral Hiroaki Abe in battleship Hiei. In addition to commanding the Advanced force, Kondo acted as the overall commander of the three forces.[20]

The U.S. naval forces were deployed as two separate carrier groups, Task Force 16 under command of Rear Admiral Thomas Kinkaid and built around carrier Enterprise, and Task Force 17 under command of Rear Admiral George Murray and built around carrier Hornet. The two groups were under overall command by Kinkaid, and were separated from each other by about 10 nmi (19 km; 12 mi). The carriers were supported by one battleship (USS South Dakota), three heavy cruisers (Portland, Northampton, Pensacola), three light anti-aircraft cruisers (San Juan, San Diego, Juneau), and 14 destroyers. A third US task force, Task Force 64, commanded by Rear Admiral Willis Lee, consisted of battleship USS Washington, heavy cruiser San Francisco, light cruiser Helena, anti-aircraft cruiser Atlanta, and 6 destroyers. This last force, however, had withdrawn to the South East for fueling, and played no part in the upcoming battle.

The two U.S. carrier groups swept around to the north of the Santa Cruz Islands on October 25 searching for the Japanese naval forces. A U.S. PBY Catalina based in the Santa Cruz Islands located the Japanese Main body carriers at 11:03. However, the Japanese carriers were about 355 nmi (657 km; 409 mi) from the U.S. force, just beyond carrier aircraft range. Kinkaid, hoping to close the range to be able to execute an attack that day, steamed towards the Japanese carriers at top speed and, at 14:25, launched a strike force of 23 aircraft. But the Japanese, knowing that they had been spotted by U.S. aircraft and not knowing where the U.S. carriers were, turned to the north to stay out of range of the U.S. carriers' aircraft.[21] Thus, the U.S. strike force returned to their carriers without finding or attacking the Japanese warships.[22]

Battle

Carrier action on 26 October: first strikes

At 02:50 on 26 October, the Japanese naval forces reversed direction and the naval forces of the two adversaries closed the distance until they were only 200 nmi (370 km; 230 mi) away from each other by 05:00.[23] Both sides launched search aircraft and prepared their remaining aircraft to attack as soon as the other side's ships were located. Although a radar-equipped PBY Catalina sighted the Japanese carriers at 03:10, the report did not reach Kinkaid until 05:12. Therefore, believing that the Japanese ships had probably changed position during the intervening two hours, he decided to withhold launching a strike force until he received more current information on the location of the Japanese ships.[24]

Japanese fighter and dive bomber aircraft on Shōkaku prepare to launch for an attack on U.S. carrier forces the morning of 26 October 1942.

At 06:45, a U.S. scout aircraft sighted the carriers of Nagumo's main body.[25] At 06:58, a Japanese scout aircraft reported the location of Hornet's task force.[26] Both sides raced to be the first to attack the other. The Japanese were first to get their strike force launched, with 64 aircraft, including 21 Aichi D3A2 dive bombers, 20 Nakajima B5N2 torpedo bombers, 21 A6M3 Zero fighters, and two Nakajima B5N2 command and control aircraft on the way towards Hornet by 07:40.[27] Also at 07:40, two U.S. SBD-3 Dauntless scout aircraft, responding to the earlier sighting of the Japanese carriers, arrived and dove on Zuihō. With the Japanese combat air patrol (CAP) busy chasing other U.S. scout aircraft away, the two U.S. aircraft were able to hit Zuihō with both their 500-pound bombs, causing heavy damage and preventing the carrier's flight deck from being able to land aircraft.[26]

Meanwhile, Kondo ordered Abe's Vanguard force to race ahead to try to intercept and engage the U.S. warships. Kondo also brought his own Advanced force forward at maximum speed so that Junyō's aircraft could join in the attacks on the U.S. ships. At 08:10, Shōkaku launched a second wave of strike aircraft, consisting of 19 dive bombers and eight Zeros, and Zuikaku launched 16 torpedo bombers at 08:40. Thus, by 09:10 the Japanese had 110 aircraft on the way to attack the U.S. carriers.[28]

As a TBF Avenger prepares to take off from Enterprise on 26 October, the signs held aloft by deck crewmen give the last known location of the Japanese carriers as well as instructions to proceed without waiting for Hornet's aircraft.

The U.S. strike aircraft were running about 20 minutes behind the Japanese. Believing that a speedy attack was more important than a massed attack, and because they lacked fuel to spend time assembling prior to the strike, the U.S. aircraft proceeded in small groups towards the Japanese ships, rather than forming into a single large strike force. The first group—consisting of 15 SBD dive bombers, six TBF-1 Avenger torpedo bombers, and eight F4F Wildcat fighters, led by Lieutenant Commander R. Eation from Hornet—was on its way by about 08:00. A second group—consisting of three SBDs, seven TBFs, and eight Wildcats from Enterprise—was off by 08:10. A third group—which included nine SBDs, eight TBFs, and seven Wildcats from Hornet—was on its way by 08:20.[29]

At 08:40, the opposing aircraft strike formations passed within sight of each other. Nine Zeros from Zuihō surprised and attacked the Enterprise group, attacking the climbing aircraft from out of the sun. In the resulting engagement, four Zeros, three Wildcats, and two TBFs were shot down, with another two TBFs and a Wildcat forced by heavy damage to return to Enterprise.[30]

At 08:50, the lead U.S. attack formation from Hornet spotted four ships from Abe's Vanguard force. Pressing on, the U.S. aircraft sighted the Japanese carriers and prepared to attack. Three Zeros from Zuihō attacked the formation's Wildcats, drawing them away from the bombers they were assigned to protect. Thus, the dive bombers in the first group initiated their attacks without fighter escort. Twenty Zeros from the Japanese carrier CAP attacked the SBD formation and shot down four of them. The remaining 11 SBDs commenced their attack dives on Shōkaku at 09:27, hitting her with three to six bombs, wrecking her flight deck and causing serious damage to the interior of the ship. The final SBD of the 11 lost track of Shōkaku and instead dropped its bomb near the Japanese destroyer Teruzuki, causing minor damage.[31] The six TBFs in the first strike force, having become separated from their strike group, missed finding the Japanese carriers and eventually turned back towards Hornet. On the way back, they attacked the Japanese heavy cruiser Tone, missing with all of their torpedoes.[32]

Japanese cruiser Chikuma under attack on 26 October. The white spot in the center of the ship is where a 1,000 lb (450 kg) bomb hit directly on the bridge, causing heavy damage and high casualties.

The TBFs of the second U.S. attack formation from Enterprise were unable to locate the Japanese carriers and instead attacked the Japanese heavy cruiser Suzuya from Abe's Vanguard force but caused no damage. At about the same time, the third U.S. attack formation—from Hornet—found Abe's ships and attacked the Japanese heavy cruiser Chikuma, hitting her with two 1,000 lb (450 kg) bombs and causing heavy damage. The three Enterprise SBDs then arrived and also attacked Chikuma, causing more damage with one bomb hit and two near-misses. Finally, the eight TBFs from the third strike group arrived and attacked the smoking Chikuma, scoring one more hit. Chikuma—escorted by two destroyers—withdrew from the battle and headed towards Truk for repairs.[33]

The U.S. carrier forces received word from their outbound strike aircraft at 08:30 that Japanese attack aircraft were headed their way.[34] At 08:52, the Japanese strike force commander sighted the Hornet task force (the Enterprise task force was hidden by a rain squall) and deployed his aircraft for attack. At 08:55, the U.S. carriers detected the approaching Japanese aircraft on radar—about 35 nmi (65 km; 40 mi) away—and began to vector the 37 Wildcats of their CAP to engage the incoming Japanese aircraft. However, communication problems, mistakes by the U.S. fighter control directors, and primitive control procedures prevented all but a few of the U.S. fighters from engaging the Japanese aircraft before they began their attacks on Hornet.[35] Although the U.S. CAP was able to shoot down several dive bombers, most of the Japanese aircraft commenced their attacks relatively unmolested by U.S. fighters.[36]

A damaged Japanese dive bomber (upper left) dives towards Hornet at 09:14...
...and seconds later crashes into the carrier.

At 09:09, the anti-aircraft guns of Hornet and her escorting warships opened fire as the 20 untouched Japanese torpedo planes and remaining 16 dive bombers commenced their attacks on the carrier.[37] At 09:12, a dive bomber placed its 551 lb (250 kg), semi-armor-piercing bomb dead center on Hornet's flight deck, across from the island, which penetrated three decks before exploding, killing 60 men. Moments later, a 534 lb (242 kg) "land" bomb struck the flight deck, detonating on impact and creating an 11 ft (3.4 m) hole as well as killing 30 men. A minute or so later, a third bomb hit Hornet near where the first bomb hit, penetrating three decks before exploding, causing severe damage but no direct loss of life.[38] At 09:14, a dive bomber was hit and damaged by Hornet's anti-aircraft guns; On fire, the damaged aircraft deliberately crashed into Hornet's stack, killing seven men and spreading burning aviation fuel over the signal deck.[39]

At the same time that the dive bombers were attacking, the 20 torpedo bombers were also approaching Hornet from two different directions. Despite suffering heavy losses from anti-aircraft fire, the torpedo planes planted two torpedoes into Hornet's side between 09:13 and 09:17, knocking out her engines. As Hornet glided to a stop, a damaged Japanese dive bomber approached and purposely crashed into the carrier's side, starting a fire near the ship's main supply of aviation fuel. At 09:20, the surviving Japanese aircraft departed, leaving Hornet dead in the water and burning.[40] Twenty-five Japanese aircraft and six American aircraft were destroyed in this attack.[41]

With the assistance of firehoses from three escorting destroyers, the fires on Hornet were under control by 10:00. Wounded personnel were evacuated from the carrier, and an attempt was made by the heavy cruiser USS Northampton to tow Hornet away from the battle area. However, the effort to rig the towline took some time, and more attack waves of Japanese aircraft were inbound.[42]

Carrier action on October 26: post-first strike actions

Starting at 09:30, Enterprise landed many of the damaged and fuel-depleted CAP fighters and returning scout aircraft from both carriers. However, with her flight deck full, and the second wave of Japanese aircraft inbound, which was detected on radar at 09:30, Enterprise ceased landing operations at 10:00. Fuel-depleted aircraft then began ditching in the ocean as the carrier's escorting destroyers rescued the aircrews. One of the ditching aircraft, a damaged TBF from Enterprise's strike force that had been attacked earlier by Zuihō Zeros, crashed into the water near the destroyer USS Porter. As Porter rescued the TBF's aircrew, she was struck by a torpedo, perhaps from the ditched aircraft, causing heavy damage and killing 15 crewmen.[43] After the task force commander ordered the destroyer scuttled, the crew was rescued by the destroyer USS Shaw which then sank Porter with gunfire (Lua error in package.lua at line 80: module 'strict' not found.).[44]

A Japanese dive bomber (center) is shot down during the attack on the Enterprise (lower right). Enterprise is smoking from earlier bomb hits as another bomb near-misses the carrier. In the lower middle is the battleship USS South Dakota.[45]

As the first wave of Japanese strike aircraft began returning to their carriers from their attack on Hornet, one of them spotted the Enterprise task force (which had just emerged from a rain squall) and reported the carrier's position.[46] Thus, the second Japanese aircraft strike wave—believing Hornet to be sinking—directed their attacks on the Enterprise task force, beginning at 10:08. Again, the U.S. CAP had trouble intercepting the Japanese aircraft before they attacked Enterprise, shooting down only two of the 19 dive bombers as they began their dives on the carrier. Attacking through the intense anti-aircraft fire put up by Enterprise and her escorting warships, the bombers hit the carrier with two 551 lb (250 kg) bombs and near-missed with another. The bombs killed 44 men and wounded 75, and caused heavy damage to the carrier, including jamming her forward elevator in the "up" position.[47] Twelve of the 19 Japanese bombers were lost in this attack.[48]

Twenty minutes later, the 16 Zuikaku torpedo planes arrived and split up to attack Enterprise. One group of torpedo bombers was attacked by two CAP Wildcats which shot down three of them and damaged a fourth. On fire, the fourth damaged aircraft purposely crashed into the destroyer Smith, setting the ship on fire and killing 57 of her crew. To make matters worse, the torpedo carried by this aircraft somehow survived the initial impact but detonated shortly afterward, causing even more damage. The fires initially seemed out of control until Smith's commanding officer ordered the destroyer to steer into the large spraying wake of the battleship USS South Dakota, which helped put out the fires. Smith then resumed her station, firing her remaining anti-aircraft guns at the still attacking torpedo planes.[49]

A Hornet Wildcat that just landed minutes earlier skids across Enterprise's flight deck as the carrier maneuvers violently during Junyo's dive bomber attack. Two crewmen are taking defensive postures on the deck as smoke from earlier bomb hits swirls around them.

The remaining torpedo planes attacked Enterprise, South Dakota, and cruiser Portland, but all of their torpedoes missed or were duds, causing no damage. The engagement was over at 10:53; nine of the 16 torpedo aircraft were lost in this attack.[50] After suppressing most of the onboard fires, at 11:15 Enterprise reopened her flight deck to begin landing returning aircraft from the morning U.S. strikes on the Japanese warship forces. However, only a few aircraft landed before the next wave of Japanese strike aircraft arrived and began their attacks on Enterprise, forcing a suspension of landing operations.[51]

Between 09:05 and 09:14, Junyō had arrived within 280 nmi (320 mi; 520 km) of the U.S. carriers and launched a strike of 17 dive bombers and 12 Zeros.[52] As the Japanese Main body and Advanced force maneuvered to try to join formations, Junyō readied follow-up strikes.[53] At 11:21, the Junyō aircraft arrived and dove on the Enterprise task force. The dive bombers scored one near miss on Enterprise, causing more damage, and one hit each on South Dakota and light cruiser San Juan, causing moderate damage to both ships. Eleven of the 17 Japanese dive bombers were destroyed in this attack.[54]

At 11:35, Kinkaid decided to withdraw Enterprise and her screening ships from the field of battle, since Hornet was out of action, Enterprise was heavily damaged, and surmising (correctly) that the Japanese had one or two undamaged carriers in the area.[55] Leaving Hornet behind, all Kinkaid could do was to direct the carrier and her task force to retreat as soon as they were able. Between 11:39 and 13:22, Enterprise recovered 57 of the 73 airborne U.S. aircraft as she headed away from the battle.[56] The remaining U.S. aircraft ditched in the ocean, and their aircrews were rescued by escorting warships.[57]

Between 11:40 and 14:00, the two undamaged Japanese carriers, Zuikaku and Junyō, recovered the few aircraft that returned from the morning strikes on Hornet and Enterprise and prepared follow-up strikes. It was now that the devastating losses sustained during these attacks became all too apparent. Lt. Cmdr. Okumiya Masatake, Junyō's air staff officer, described the return of the carrier's first strike groups:

<templatestyles src="Template:Blockquote/styles.css" />

We searched the sky with apprehension. There were only a few planes in the air in comparison with the numbers launched several hours before... The planes lurched and staggered onto the deck, every single fighter and bomber bullet holed... As the pilots climbed wearily from their cramped cockpits, they told of unbelievable opposition, of skies choked with antiaircraft shell bursts and tracers.

Only one of Junyō's bomber leaders returned from the first strike, and upon landing he appeared "so shaken that at times he could not speak coherently."[58]

At 13:00, Kondo's Advanced force and Abe's Vanguard force warships together headed directly towards the last reported position of the U.S. carrier task forces and increased speed to try to intercept them for a warship gunfire battle. The damaged carriers Zuihō and Shōkaku, with Nagumo still on board, retreated from the battle area, leaving Rear Admiral Kakuji Kakuta in charge of the Zuikaku and Junyō aircraft forces. At 13:06, Junyō launched her second strike of seven torpedo planes and eight Zeros, and Zuikaku launched her third strike of seven torpedo planes, two dive bombers, and five Zeros. At 15:35, Junyō launched the last Japanese strike force of the day, consisting of four bombers and six Zeros.[59]

Hornet, sinking and abandoned.

After several technical problems, Northampton finally began slowly towing Hornet out of the battle area at 14:45, but only at a speed of five knots. Hornet's crew was on the verge of restoring partial power [60] but at 15:20, Junyō's second strike arrived, and the seven torpedo planes attacked the almost stationary carrier. Although six of the torpedo planes missed, at 15:23, one torpedo struck Hornet mid-ship, which proved to be the fatal blow. The torpedo hit destroyed the repairs to the power system and caused heavy flooding and a 14° list. With no power to pump out the water, Hornet was given up for lost, and the crew abandoned ship. The third strike from Zuikaku attacked Hornet during this time, hitting the sinking ship with one more bomb. All of the Hornet's crewmen were off by 16:27. The last Japanese strike of the day dropped one more bomb on the sinking carrier at 17:20.[61]

After being informed that Japanese forces were approaching and that further towing efforts were unfeasible, Admiral Halsey ordered the Hornet sunk. While the rest of the U.S. warships retired towards the southeast to get out of range of Kondo's and Abe's oncoming fleet, destroyers USS Mustin and Anderson attempted to scuttle Hornet with multiple torpedoes and over 400 shells, but she still remained afloat. With advancing Japanese naval forces only 20 minutes away, the two U.S. destroyers abandoned Hornet's burning hulk at 20:40. By 22:20, the rest of Kondo's and Abe's warships had arrived at Hornet's location. Upon finding the carrier that had launched the Doolittle Raid, the Japanese briefly considered taking Hornet as a war trophy, but ultimately decided that she was too damaged to try to capture. The destroyers Makigumo and Akigumo then finished Hornet with four 24 in (610 mm) torpedoes. At 01:35 on 27 October 1942, she finally sank[62] on the approximated position Lua error in package.lua at line 80: module 'strict' not found.. Several night attacks by radar-equipped Catalinas on Junyō and Teruzuki, knowledge of the head start the U.S. warships had in their retreat from the area, plus a critical fuel situation apparently caused the Japanese to reconsider further pursuit of the U.S. warships. After refueling near the northern Solomon Islands, the ships returned to their main base at Truk on 30 October. During the U.S. retirement from the battle area towards Espiritu Santo and New Caledonia, South Dakota collided with destroyer Mahan, heavily damaging the destroyer.[63]

Aftermath

The crew of Enterprise conducts a burial at sea on 27 October for 44 of their fellow crewmen killed during the battle the day before.

The Japanese claimed victory by claiming to have sunk three American carriers, one battleship, one cruiser, one destroyer and one "unidentified large warship" along with 79 American carrier aircraft destroyed (plus many more sunk on the carriers). In fact, the Americans lost one carrier (Hornet) and the destroyer Porter. The Enterprise was heavily damaged as was the battleship South Dakota, the light cruiser San Juan, and the destroyers Smith and Mahan. Of the 175 U.S. aircraft at the start of the battle, 81 were lost (33 fighters, 28 dive-bombers, and 20 torpedo bombers).

For the Japanese, two carriers (Shōkaku and Zuihō) and the heavy cruiser Chikuma had been badly damaged and 99 of 203 Japanese carrier aircraft involved in the battle had been lost.

The loss of Hornet was a severe blow for Allied forces in the South Pacific, leaving Enterprise as the one operational, but damaged, Allied carrier in the entire Pacific theater. As she retreated from the battle, the crew posted a sign on the flight deck: "Enterprise vs Japan."[64][65][66][67]

Enterprise received temporary repairs at New Caledonia and, although still somewhat damaged, returned to the southern Solomons area just two weeks later to support Allied forces during the Naval Battle of Guadalcanal, playing an important role in what turned out to be the decisive naval engagement in the overall campaign for Guadalcanal.[68]

Although a tactical victory for the Japanese in terms of ships sunk, it came at a high cost for Japanese naval forces. Both damaged carriers were forced to return to Japan for extensive repairs and refitting. After repair, Zuihō returned to Truk in late January 1943. Shōkaku was under repair until March 1943 and did not return to the front until July 1943, when she was reunited with Zuikaku at Truk.[69]

The most significant losses for the Japanese Navy, however, were in aircrew. The U.S. lost 81 aircraft along with 26 pilots and aircrew members in the battle.[70] The Japanese, on the other hand, lost 99 aircraft and 148 pilots and aircrew members including two dive bomber group leaders, three torpedo squadron leaders, and 18 other section or flight leaders. Forty-nine percent of the Japanese torpedo bomber aircrews involved in the battle were killed along with 39% of the dive bomber crews and 20% of the fighter pilots.[71] The Japanese lost more aircrew at Santa Cruz than they had lost in each of the three previous carrier battles at Coral Sea (90), Midway (110), and Eastern Solomons (61). By the end of the Santa Cruz battle, at least 409 of the 765 elite Japanese carrier aviators who had participated in the Attack on Pearl Harbor were dead.[72]

Having lost so many of its veteran carrier aircrew, and with no quick way to replace them because of an institutionalized limited capacity in its naval aircrew training programs and an absence of trained reserves, the undamaged Zuikaku and Hiyō were also forced to return to Japan because of a scarcity of trained aircrew to man their air groups. Although the Japanese carriers returned to Truk by the summer of 1943, they played no further offensive role in the Solomon Islands campaign.[68][73]

Admiral Nagumo, upon being relieved of command shortly after the battle and reassigned to shore duty in Japan, stated in his report to the Combined Fleet Headquarters: "This battle was a tactical win, but a shattering strategic loss for Japan. Considering the great superiority of our enemy's industrial capacity, we must win every battle overwhelmingly in order to win this war. This last one, although a victory, unfortunately, was not an overwhelming victory."[73]

In retrospect, despite being a tactical victory, the battle effectively ended any hope the Japanese navy might have had of scoring a decisive victory before the industrial might of the United States placed that goal out of reach. Historian Eric Hammel summed up the significance of the Battle of the Santa Cruz Islands as, "Santa Cruz was a Japanese victory. That victory cost Japan her last best hope to win the war."[68]

Notes

  1. Hogue, Pearl Harbor to Guadalcanal, p. 235–236.
  2. Lua error in package.lua at line 80: module 'strict' not found. p. 106.
  3. Frank, Guadalcanal, p. 335.
  4. Hammel, Carrier Strike, p. 6–7.
  5. Hammel, Carrier Strike, p. 10–12.
  6. After this incident the then U.S. carrier task force commander Frank Jack Fletcher was relieved of his command and reassigned to shore duty for the remainder of the war. Frank, Guadalcanal, p. 204–205
  7. Evans, Japanese Navy, p. 179–180, Hammel, Carrier Strike, p. 24–41. Battleship North Carolina and destroyer O'Brien were also hit by torpedoes during the same attack. O'Brien later sank as a result of the torpedo damage, and North Carolina was under repair at Pearl Harbor until November 16, 1942.
  8. Hammel, Carrier Strike, p. 19–21, 84–85.
  9. Frank, Guadalcanal, p. 316–319.
  10. Hammel, Carrier Strike, p. 154–155.
  11. McGee, The Solomons Campaigns, p. 145.
  12. McGee, The Solomons Campaigns, p. 134.
  13. Frank, Guadalcanal, p. 334.
  14. Hammel, Carrier Strike, p. 150.
  15. Hammel, Carrier Strike, p. 146–149.
  16. Hara, Japanese Destroyer Captain, p. 124–125. According to Hara, the Japanese believed that U.S. Navy forces were likely to be in the Solomon Islands area because they had read a report from the United Press dated 20 October that stated that the United States Navy was preparing for a major sea and air battle in the South Pacific.
  17. Hammel, Carrier Strike, p. 95–97.
  18. Hammel, Carrier Strike, p. 103–106. The force consisted of Japanese cruiser Yura, and destroyers Akizuki, Harusame, Murasame, and Yudachi (Parshall, Imperial Japanese Navy Page. Combinedfleet.com). Although Hammel says that it was a supply convoy, Parshall says that it was a bombardment force. Akizuki went to Japan for repairs, which were completed on 16 December 1942. This incident is usually considered a separate action from the Battle of the Santa Cruz Islands.
  19. Hara, Japanese Destroyer Captain, p. 124.
  20. Frank, Guadalcanal, p. 374–375.
  21. Hara, Japanese Destroyer Captain, p. 127.
  22. Hammel, Carrier Strike, p. 163–174.
  23. Hammel, Carrier Strike, p. 186.
  24. Frank, Guadalcanal, p. 381.
  25. Hammel, Carrier Strike, p. 187.
  26. 26.0 26.1 Frank, Guadalcanal, p. 382.
  27. Hammel, Carrier Strike, p. 191–192.
  28. Frank, Guadalcanal, p. 383.
  29. Hammel, Carrier Strike, p. 198–199.
  30. Frank, Guadalcanal, p. 384–385. Only the Wildcat safely recovered.
  31. The crew of Shōkaku fights fires on the flight deck after the strike by US carrier aircraft.
    Hammel, Carrier Strike, p. 213–223.
  32. Frank, Guadalcanal, p. 387–388.
  33. Hara, Japanese Destroyer Captain, p. 132, and Parshall, The Imperial Japanese Navy Page. Chikuma was under repair at Truk and later Kure, Japan, until January 1943.
  34. Hammel, Carrier Strike, p. 235.
  35. Hammel, Carrier Strike, p. 235–239.
  36. Frank, Guadalcanal, p. 385.
  37. Hammel, Carrier Strike, p. 249–251. Hornet's screening ships included heavy cruisers Northampton and Pensacola, light cruisers San Diego and Juneau, and six destroyers.
  38. Hammel, Carrier Strike, p. 253–356.
  39. Frank, Guadalcanal, p. 386, and Hammel, Carrier Strike, p. 262–267.
  40. Hammel, Carrier Strike, p. 269–271.
  41. Frank, Guadalcanal, p. 386, Hammel, Carrier Strike, p. 284.
  42. Hammel, Carrier Strike, p. 271–280.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Evans, Japanese Navy, p. 520, Frank, Guadalcanal, p. 388–389, Hammel, Carrier Strike, p. 299.
  45. Fahey, The Ships and Aircraft of the United States Fleet, p. 5.
  46. Hammel, Carrier Strike, p. 283.
  47. Hammel, Carrier Strike, p. 300–313.
  48. Frank, Guadalcanal, p. 390.
  49. Frank, Guadalcanal, p. 390–391. Smith eventually went to Pearl Harbor for repairs, which were completed in February 1943.
  50. Frank, Guadalcanal, p. 391.
  51. Hammel, Carrier Strike, p. 335–337.
  52. Hammel, Carrier Strike, p. 330–331, and Frank, Guadalcanal, p. 391.
  53. Hammel, Carrier Strike, p. 331.
  54. Frank, Guadalcanal, p. 391–393. Anti-aircraft fire from battleship South Dakota was credited with 26 of the total of 99 enemy planes downed in the battle (South Dakota in Dictionary of American Naval Fighting Ships, DANFS, U.S. Dept. of Navy).
  55. Frank, Guadalcanal, p. 395.
  56. Lundstrom, Guadalcanal Campaign, p. 444. One U.S. aircraft was able to reach a U.S. airbase at Espiritu Santo.
  57. Hammel, Carrier Strike, p. 345–352.
  58. Lundstrom, Guadalcanal Campaign, p. 446.
  59. Hara, Japanese Destroyer Captain, p. 129–131, Hammel, Carrier Strike, p. 357–358.
  60. Frank, Guadalcanal, p. 395–396.
  61. Hammel, Carrier Strike, p. 359–376.
  62. Hammel, Carrier Strike, p. 380.
  63. Evans, Japanese Navy, p. 520, Frank, Guadalcanal, p. 399. Mahan returned to action on January 9, 1943.
  64. USS Enterprise CV-6 - 1942.
  65. USS Enterprise CV-6 at Pacific Wrecks.com.
  66. Battles - USS Enterprise.
  67. Battle 360, Episode 5: Enterprise versus Japan. The History Channel, 2008.
  68. 68.0 68.1 68.2 Hammel, Carrier Strike, p. 384.
  69. Parshall & Tully, Imperial Japanese Navy Page (Combinedfleet.com), Shokaku & Zuiho.
  70. Lundstrom, Guadalcanal Campaign, p. 456.
  71. Frank, Guadalcanal, p. 400–401, Hammel, Carrier Strike, p. 381, and Lundstrom, Guadalcanal Campaign, p. 454.
  72. Peattie, p. 180 & 339. The aircrew losses included 55 from Shōkaku, 57 from Zuikaku, 9 from Zuihō, and 27 from Junyō.
  73. 73.0 73.1 Hara, Japanese Destroyer Captain, p. 135.

References

  • 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.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • 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.
  • 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.

External links

  • Lua error in package.lua at line 80: module 'strict' not found., Interactive animation of the battle
  • 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.