12.04.2013 Views

The Wreck of DKM Bismarck − A Marine Forensics Analysis 1 The ...

The Wreck of DKM Bismarck − A Marine Forensics Analysis 1 The ...

The Wreck of DKM Bismarck − A Marine Forensics Analysis 1 The ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>The</strong> <strong>Wreck</strong> <strong>of</strong> <strong>DKM</strong> <strong>Bismarck</strong> <strong>−</strong> A <strong>Marine</strong> <strong>Forensics</strong> <strong>Analysis</strong><br />

buoyancy. Following this engagement, Admiral Lütjens to abort the mission and<br />

head to France for repairs.<br />

○ <strong>The</strong> aerial torpedo hit in the stern late in the afternoon <strong>of</strong> 26 May wrecked the<br />

<strong>Bismarck</strong>’s steering gear, making the ship un-maneuverable. <strong>The</strong> ship gradually<br />

turned into the prevailing seas, heading directly towards the pursuing British.<br />

○ Long-range gunfire from the battleships King George V and Rodney on the morning<br />

<strong>of</strong> 27 May early on in the final engagement destroyed much <strong>of</strong> the <strong>Bismarck</strong>’s main<br />

battery and destroyed the ship’s primary gunfire control system. <strong>The</strong> gunnery<br />

engagement lasted from 0847 to 1021.<br />

○ Closer-range gunfire (eventually, at virtually point-blank range for battleship main<br />

battery guns) later in the engagement devastated the superstructure and exposed<br />

sections <strong>of</strong> the hull (above the waterline) and caused massive casualties, but<br />

contributed little to the eventual sinking <strong>of</strong> the ship.<br />

○ Late in the final engagement, the Bismark was defeated, sinking as the result <strong>of</strong><br />

uncontrollable progressive flooding, and virtually defenseless. <strong>The</strong> Executive Officer,<br />

CDR Hans Oels, ordered the scuttling <strong>of</strong> the ship <strong>−</strong> “Measure V [V = ‘Versunken’]”<br />

<strong>−</strong> and the charges were detonated shortly after 1020. By 1035, the ship had assumed<br />

a heavy port list, capsizing slowly and sinking by the stern. <strong>The</strong> bow disappeared<br />

about 1040.<br />

TORPEDO DAMAGE ANALYSIS:<br />

One <strong>of</strong> the significant achievements <strong>of</strong> the 2002 Cameron Expedition was the exploration<br />

<strong>of</strong> damage on the starboard side aft, which is believed to have been caused by the combination <strong>of</strong><br />

the effects <strong>of</strong> a torpedo hit and by hydraulic outburst. While a torpedo likely damaged this area<br />

<strong>of</strong> the hull aft, it did not warp, buckle <strong>of</strong> displace the 45-mm torpedo bulkhead inboard <strong>of</strong> the<br />

tank. <strong>The</strong> sacrificial tankage served its purpose by dispersing the explosive force. No individual<br />

armored plates were displaced in either the armored bulkhead or the armor deck over the tank.<br />

While there was leakage through small cracks <strong>of</strong> failed welds from a torpedo hit on the port side<br />

aft from one <strong>of</strong> the Ark Royal aircraft on 26 May, as confirmed by evidence from Josef Statz and<br />

Gerhard Junack, the resulting flooding contributed little to the sinking <strong>of</strong> the ship. <strong>The</strong> hits<br />

claimed for ship-launched torpedoes during the final battle on 27 May came minutes before the<br />

battleship foundered, when some <strong>of</strong> the major vitals were already flooding from scuttling<br />

charges. Some German survivors, including Baron von Müllenheim-Rechberg during an<br />

interview with authors Dulin and Garzke, have stated that no torpedo holes could be observed<br />

when the ship capsized. It is very probable that these torpedo holes were probably hidden from<br />

sight.<br />

51

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!