<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Naval Gazing</title>
<description>Main.Naval Gazing</description>
<link>https://www.navalgazing.net/HomePage?action=rss</link>
<lastBuildDate>Sun, 16 Aug 2026 18:12:53 GMT</lastBuildDate>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Airliner-COD</guid>
<link>https://www.navalgazing.net/Airliner-COD</link>
<title>Main / Airliner COD</title>
<dc:date>2026-08-16T12:00:00Z</dc:date>
<pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>Probably the most obscure corner of carrier aviation is COD, Carrier Onboard Delivery.  This is exactly what it sounds like, the practice of delivering high-priority cargo, mail and personnel from bases ashore to aircraft carriers.  The role originated in the immediate postwar years, and was first carried out by TBM Avengers modified to carry six passengers or cargo in the former bomb bay.  But it was soon clear that the limited cargo weight and volume would be a problem for air-delivery of important cargoes like jet engines and nuclear weapons.<a class='footnote' id='fnr1_1' href='#fn1_1'><sup>1</sup></a>
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Grumman_C-1_aboard_USS_America.jpg?v=1786733363.jpg' alt='' /><br /><span class='caption'>A C-1 Trader   </span></span></div>
<p>The Navy ultimately chose to procure the <a class='urllink' href='https://en.wikipedia.org/wiki/Grumman_C-1_Trader' rel='nofollow'>C-1 Trader</a>, a variant of their existing <a class='urllink' href='https://en.wikipedia.org/wiki/Grumman_S-2_Tracker' rel='nofollow'>S-2 Tracker ASW aircraft</a> with an enlarged fuselage.  Entering service in 1956, the Trader would go on to serve for three decades in the USN, ultimately becoming the last operational piston-engined aircraft to fly from American carriers.  But it was slow and limited in range, and, more importantly, it was soon unable to carry the largest jet engines in use by the fleet.  The Navy again turned to Grumman to adapt an existing design with a new fuselage, turning the <a class='urllink' href='https://en.wikipedia.org/wiki/Grumman_S-2_Tracker' rel='nofollow'>E-2 Hawkeye</a> into the <a class='urllink' href='https://en.wikipedia.org/wiki/Grumman_C-2_Greyhound' rel='nofollow'>C-2 Greyhound</a>.  Ultimately, it would serve for almost 60 years until the growth of jet engines, in particular the F135 for the F-35C, caused the Navy to procure a new COD airplane capable of carrying it.  The winner in this case was the CMV-22,<a class='footnote' id='fnr1_2' href='#fn1_2'><sup>2</sup></a> based on the <a class='urllink' href='https://en.wikipedia.org/wiki/Bell%E2%80%93Boeing_V-22_Osprey' rel='nofollow'>V-22 Osprey</a> beloved of the Marines and loathed by budget analysts.
<a id='break'></a>
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/Lockheed_KC-130F_Hercules_aboard_USS_Forrestal.jpeg?v=1786733365.jpeg' alt='' /><br /><span class='caption'>The Hercules aboard <em>Forrestal</em></span></span></div>
<p>But while only three aircraft have actually served in the COD role since the mid-50s, there have been numerous other proposals, often for larger and longer-ranged aircraft.  In 1963, looking for an emergency option that could better the C-1 Trader's range, the Navy carried out tests aboard <em>Forrestal</em> using a barely-modified <a class='urllink' href='https://en.wikipedia.org/wiki/Lockheed_Martin_KC-130' rel='nofollow'>KC-130F Hercules</a> borrowed from the Marines.  A pair of experienced carrier aviators were checked out on the Hercules and sent to conduct the tests about 500 miles out in the Atlantic.  They were able to successfully conduct 29 touch-and-go landings, 21 full stop landings and 21 takeoffs, all without the assistance of the carrier's <a class='wikilink' href='https://www.navalgazing.net/Carrier-Operations-Part-4'>catapults</a> and <a class='wikilink' href='https://www.navalgazing.net/Carrier-Operations-Part-2'>arresting gear</a>.  Famously, one test saw the Hercules stop opposite the ship's island with "Look Ma, No Hook" painted on the side, and it set a record for the heaviest aircraft operated from a carrier that stands to this day.  But there were also problems.  The biggest is that while it was technically possible, getting the necessary stopping distances required reversing their engines 3-4' off the deck, a maneuver that is <a class='urllink' href='https://admiralcloudberg.medium.com/the-luxembourg-maneuver-the-crash-of-luxair-flight-9642-8eb41563c668' rel='nofollow'>generally frowned upon</a>.  The second was that the C-130 is a very big airplane by carrier standards, and landed straight down the deck instead of using the angle, which required the deck to be almost entirely clear of other aircraft.  Since <a class='wikilink' href='https://www.navalgazing.net/Carrier-Operations-Part-3'>the days of <em>Langley</em></a>, the USN has kept a lot of planes on deck, so even landing a C-130 for five minutes would be extremely disruptive to normal operations, and it was way too large to park out of the way if something went wrong or they needed to wait.  As a result of all this, despite the success of the tests, the procedure has never been repeated.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/C-2A_Greyhound_makes_an_arrested_landing_during_flight_deck_qualifications_aboard_USS_Abraham_Lincoln.jpg?v=1786736354.jpg' alt='' /><br /><span class='caption'>A C-2 lands aboard <em>Lincoln</em></span></span></div>
<p>The Navy was still interested in the idea of a COD plane with more range and capacity than the C-2, and conducted a number of studies over the years.  Because it was likely to be a small fleet, and the available funds were limited, very few of these were designed from scratch.  Some were intended, like the C-2, to share commonality with other carrier aircraft,<a class='footnote' id='fnr1_3' href='#fn1_3'><sup>3</sup></a> while others were based on whatever sub-C-130 transport was on the drawing board at the time.  But the most interesting were a few proposals to use airliners as the basis for COD planes.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/United_737-200_N3013U_at_CLE.jpg?v=1786733364.jpg' alt='' /><br /><span class='caption'>A 737-200 in gray with "United" on the side, so it's basically a USN jet</span></span></div>
<p>When I first heard this, I assumed it was a joke, or possibly the result of a gross violation of <a class='urllink' href='https://en.wikipedia.org/wiki/General_Order_No._99' rel='nofollow'>General Order 99</a>.  And while much of me still has a hard time believing it's real, and the <a class='wikilink' href='https://www.navalgazing.net/Commercial-Aviation-Part-5'>former airline structures guy</a> is still running around in terror,<a class='footnote' id='fnr1_4' href='#fn1_4'><sup>4</sup></a> the math is just plausible enough to warrant investigation.  The first round of proposals came in the early 70s, with a <a class='urllink' href='https://en.wikipedia.org/wiki/McDonnell_Douglas_DC-9' rel='nofollow'>DC-9-10</a><a class='footnote' id='fnr1_5' href='#fn1_5'><sup>5</sup></a> and a 737 variant of some sort<a class='footnote' id='fnr1_6' href='#fn1_6'><sup>6</sup></a> put forward as candidates.  I'm going to focus on the DC-9, as I have <a class='urllink' href='https://www.aahs-online.org/images/Navy_SAC/C-9B.pdf' rel='nofollow'>a spec sheet for the military version of the DC-9-30</a> and I don't have anything equivalent for the 737-200Adv.<a class='footnote' id='fnr1_7' href='#fn1_7'><sup>7</sup></a>  Both would have been big for carrier operations, but they were significantly smaller than the later members of their family, and just might have squeezed aboard.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/C-9B_Skytrain_Carrier.jpeg?v=1786733582.jpeg' alt='' /><br /><span class='caption'>A C-9 flies past a carrier, though not to land on it</span></span></div>
<p>Now, to be clear, neither would have fit aboard very well, but the biggest problem the C-130 had was its 132' wingspan, while the <a class='urllink' href='https://www.boeing.com/content/dam/boeing/v2/airports/acaps/DC9.pdf' rel='nofollow'>DC-9-10's</a> was 89' and the <a class='urllink' href='https://www.boeing.com/content/dam/boeing/v2/airports/acaps/737CL_REV_E.pdf' rel='nofollow'>737Adv</a> was about 93'.  While this was still significantly wider than anything regularly flown from a carrier (at this point, that was probably the A-3 Skywarrior at 72.5') the extra 40' and the fact that they were planning to use arresting gear and catapults meant that they could slot (probably fairly awkwardly) into the existing flight deck ops instead of having to kick everyone off.  Obviously, sticking around might be a problem but COD birds were generally expected to fly aboard, unload, get refueled and then leave again.  Of course, other modifications would be required, and McDonnell Douglas planned to fit not only a tailhook, but also a new nosewheel that incorporated catapult fittings and could be extended to give a higher angle of attack for takeoff, an in-flight refueling probe, and strengthened structure to take the loads of carrier operations.  Folding wings were even proposed, though don't seem to have been accepted as part of the initial study.
</p>
<p>But all of this assumes that it's physically possible to land and take off in the appropriate distances.  Sure, you can do it with a C-130, a plane deliberately designed for short-field operations, provided you have enough <a class='wikilink' href='https://www.navalgazing.net/Carrier-Operations-Part-1'>wind over deck</a>, but these are airliners designed to operate from relatively big runways.  They may not chew up tarmac like the first generation of jets, but would they really be small and slow enough to be compatible with the equipment on a carrier?
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/F-111B_CVA-43_approach_July1968.jpeg?v=1786733846.jpeg' alt='' /><br /><span class='caption'>An F-111B lands on <em>Coral Sea</em></span></span></div>
<p>Let's start by looking at the problem of landing.  Per <a class='urllink' href='https://www.aahs-online.org/images/Navy_SAC/C-9B.pdf' rel='nofollow'>the SAC</a>, for the design mission (10,000 lb of cargo), the C-9B should be landing at around 73,000 lb, with a power-off stall speed of 85 kts.  If we assume 40 knots wind-over-deck, then it's going into the arresting gear at something like 45 kts, but it's also going to be landing at a similar weight to the weight the A-3 Skywarrior, the heaviest plane to regularly operate from a carrier, took off.  But weight is only half the story.  Speed is the other half, and it's here that I found something surprising.  Looking through possible comparison aircraft, I found the <a class='urllink' href='https://www.aahs-online.org/images/Navy_SAC/F-111B.pdf' rel='nofollow'>F-111B</a>, the result of an extremely dumb attempt to turn an Air Force light bomber into a Navy missile-slinger.  It was cancelled before entering service, but it was definitely carrier-capable and even flew a few carrier tests.  And at the maximum listed landing weight of 57,000 lb, it was stalling at about 100 kts, for a speed relative to the deck of 60 kts.  If we assume that the arresting gear is basically limited by the kinetic energy of the landing aircraft<a class='footnote' id='fnr1_8' href='#fn1_8'><sup>8</sup></a> then the total kinetic energy of the F-111B is 102.6<a class='footnote' id='fnr1_9' href='#fn1_9'><sup>9</sup></a> while the C-9B comes in at only 74.1, a value lower enough that I'm actually reasonably confident that this could have worked, structural issues aside.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Douglas_A3D-2_Skywarrior_of_VAH-2_is_launched_from_USS_Coral_Sea.jpeg?v=1786733845.jpeg' alt='' /><br /><span class='caption'>A Skywarrior prepares to launch, also from <em>Coral Sea</em></span></span></div>
<p>But what about launch?  Here, we're going to use the <a class='urllink' href='https://www.aahs-online.org/images/Navy_SAC/A-3B%20CLE.pdf' rel='nofollow'>A-3B</a>, the heaviest plane regularly to take off from a carrier,<a class='footnote' id='fnr1_10' href='#fn1_10'><sup>10</sup></a> as our exemplar.  It took off at 73,000 lb and a power-off stall speed of 124 kts.  The C-9B's numbers are a takeoff at 99,700 lb and a power-off stall speed of 100 kts.  If we again assume 40 kt wind over deck, we see the A-3 needing to get 257.5 from a combination of its engines and the catapult, while the C-9B needs only 179.5.  Weirdly, it looks like the C-9 actually has a slightly higher thrust-to-weight ratio than the A-3, so again, we pass a plausibility check for this scheme.<a class='footnote' id='fnr1_11' href='#fn1_11'><sup>11</sup></a>  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/TC-52_Fokker_28_Fuerza_Aerea_Argentina.jpeg?v=1786733846.jpeg' alt='' /><br /><span class='caption'>An F-28 from a carrier navy on final approach, sadly sans tailhook</span></span></div>
<p>Despite the fairly impressive performance (10,000 lb of cargo for 2,200 nm) the plans for the C-9 COD went nowhere.  But it was far from the only airliner proposed for conversion, either in the early 70s or later.  I've already mentioned the Boeing alternative, but at the same time, Hawker-Siddley proposed a version of their <a class='urllink' href='https://en.wikipedia.org/wiki/Hawker_Siddeley_HS_748' rel='nofollow'>HS 748 turboprop airliner</a>, with folding wings and the usual structural modifications, but it seems to have gone even less far than the jet alternatives.  Later, in the 80s, when the Navy was looking at a new COD plane to replace the C-2, they seriously investigated the <a class='urllink' href='https://en.wikipedia.org/wiki/Fokker_F28_Fellowship' rel='nofollow'>Fokker F28</a>, a somewhat smaller airliner than the DC-9 and 737, but ultimately decided to build more C-2s instead.  And it looks like we'll probably never see such proposals again.  Modern airliners are less rugged, because structural weight costs money to haul around, and there's just not much demand for a long-range high-capacity COD, particularly now that the CMV-22 has aerial refueling capability.  But it's an interesting rabbit hole of history to go down.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn1_1'>
<p><span class='footnote-number'>1</span> To be clear, these were nuclear weapons for <a class='wikilink' href='https://www.navalgazing.net/Nuclear-Weapons-at-Sea-Heavy-Attack'>other</a> <a class='wikilink' href='https://www.navalgazing.net/Nuclear-Weapons-at-Sea-Light-Attack-Part-1'>planes</a>, and the COD bird didn't have a secondary nuclear strike role. <a href='#fnr1_1'>&#8657;</a>
</p></div><div class='footnote' id='fn1_2'>
<p><span class='footnote-number'>2</span> Yes, it would normally be the CV-22, but the Navy thinks its people are deeply stupid and would confuse the resulting aircraft with either the <a class='urllink' href='https://en.wikipedia.org/wiki/USS_Independence_%28CVL-22%29' rel='nofollow'>USS <em>Independence</em></a> or the program to develop a long-term replacement for the <a class='wikilink' href='https://www.navalgazing.net/The-Ford-Class'><em>Ford</em> class</a>.  And no, I don't know what was wrong with UV-22 either. <a href='#fnr1_2'>&#8657;</a>
</p></div><div class='footnote' id='fn1_3'>
<p><span class='footnote-number'>3</span> There were several proposals to use the S-3 Viking ASW plane as the basis of a new COD bird, with differing levels of redesign.  Ultimately, all of them failed, and half a dozen S-3s were stripped out and redesignated as US-3, used to carry a few people and small cargoes like avionics and mail to carriers operating far from land bases. <a href='#fnr1_3'>&#8657;</a>
</p></div><div class='footnote' id='fn1_4'>
<p><span class='footnote-number'>4</span> While he's here, he would also like to note that he is extremely baffled by the recent media coverage of the 737MAX airworthiness directive.  That kind of thing is basically Tuesday in the airline structures world, and after looking into it a bit, this is almost the definition of a routine issue.  Boeing released the inspection in late 2024, and the planned AD was made public in November 2025.  For that matter, the first MAX isn't going to need to do these inspections for probably another 3-5 years. <a href='#fnr1_4'>&#8657;</a>
</p></div><div class='footnote' id='fn1_5'>
<p><span class='footnote-number'>5</span> Technically, it was based on the DC-9-10 with DC-9-20 slats and a C-9B cargo door. <a href='#fnr1_5'>&#8657;</a>
</p></div><div class='footnote' id='fn1_6'>
<p><span class='footnote-number'>6</span> My one source on this (American Secret Projects Vol 3) is really light on details, but the timing suggests it would have been a 737-200 Advanced.  The only detail I do have is that a Boeing test pilot in a company plane managed to stop a 737 in 559' on a simulated carrier deck, without the benefit of arresting gear.  There was also a Boeing proposal to use a 727 as a COD bird, which makes even less sense, as it's a larger, heavier airplane and it doesn't seem like the Navy needed more cargo space. <a href='#fnr1_6'>&#8657;</a>
</p></div><div class='footnote' id='fn1_7'>
<p><span class='footnote-number'>7</span> The DC-9-30 had a 14' fuselage stretch to counter the threat of the 737, and a bigger wing.  For some reason, possibly deck space, they didn't use the bigger wing on the COD version, but I think this is a reasonable bound on performance and I don't have decent data on the original DC-9-10. <a href='#fnr1_7'>&#8657;</a>
</p></div><div class='footnote' id='fn1_8'>
<p><span class='footnote-number'>8</span> To put this a slightly different way, we assume that the arresting gear is exerting a constant force across the length of the landing zone.  Obviously, this is likely to annoy any arresting gear engineers reading this.  If you are one of these people, get in touch and we can come up with a better model. <a href='#fnr1_8'>&#8657;</a>
</p></div><div class='footnote' id='fn1_9'>
<p><span class='footnote-number'>9</span> The unit is 1e6 lb*kts<sup>2</sup>, which is not a unit you should use on your physics homework.  But I'm using the same unit throughout, and the important thing here is the relative values. <a href='#fnr1_9'>&#8657;</a>
</p></div><div class='footnote' id='fn1_10'>
<p><span class='footnote-number'>10</span> The A-3 was <a class='wikilink' href='https://www.navalgazing.net/Nuclear-Weapons-at-Sea-Heavy-Attack'>designed for long range and built with early, thirsty jet engines</a>, so maximum landing weight was only 49,000 lb, hence the use of the F-111B for the landing analysis. <a href='#fnr1_10'>&#8657;</a>
</p></div><div class='footnote' id='fn1_11'>
<p><span class='footnote-number'>11</span> Apparently, it would even have been possible to launch the jet with one engine out, although I can't imagine this happening regularly for safety reasons. <a href='#fnr1_11'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Saving-Houston-Part-2</guid>
<link>https://www.navalgazing.net/Saving-Houston-Part-2</link>
<title>Main / Saving ''Houston'' Part 2</title>
<dc:date>2026-08-09T12:00:00Z</dc:date>
<pubDate>Sun, 09 Aug 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>In mid-October 1944, the American carriers under Admiral Halsey were operating in the waters between Taiwan (then known as Formosa) and the Philippines, to destroy Japanese power in the area before the US <a class='wikilink' href='https://www.navalgazing.net/Leyte-Gulf-75'>invasion of Leyte</a>.  Unfortunately, on October 13th, the heavy cruiser <em>Canberra</em> was <a class='wikilink' href='https://www.navalgazing.net/Saving-Canberra'>torpedoed by Japanese aircraft, flooding both engine rooms</a>.  Normal practice would have been to take the crew off and abandon her, but Admiral Halsey decided to tow her clear by cruiser <em>Wichita</em> instead.  The next day, light cruiser <em>Houston</em> was also torpedoed, losing not only her engines but also all of her boilers, which meant there was only emergency power available throughout the ship.  <a class='wikilink' href='https://www.navalgazing.net/Saving-Houston-Part-1'>She was in considerably worse shape than <em>Canberra</em>, with serious concerns that she would break up early on, leading most of the crew to abandon ship before the decision was made to try to tow her clear as well.</a>
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/CripDiv1Map.jpeg?v=1786203149.jpeg' alt='' /><br /><span class='caption'>The path of CripDiv 1<a class='footnote' id='fnr2_1' href='#fn2_1'><sup>1</sup></a></span></span></div>
<p>On the morning of October 15th, a group, dubbed "CripDiv 1", was formed to protect the two crippled cruisers, with three light cruisers and eight destroyers to provide close cover.  Light carriers <em>Cabot</em> and <em>Cowpens</em>, with a separate group of escorts, would provide air cover.  <em>Houston</em>, towed by heavy cruiser <em>Boston</em>, spotted the group shortly after <em>Wichita</em> passed the tow to tug <em>Munsee</em>, and finally reached her station around noon.  Meanwhile, <a class='urllink' href='https://en.wikipedia.org/wiki/Tokyo_Rose' rel='nofollow'>Radio Tokyo</a> was putting out increasingly outlandish claims about the damage inflicted on the Americans, prompting parties in the streets. Halsey's staff wondered about how much was deliberate propaganda and how much the Japanese genuinely believed.  If they were taking their more outrageous claims (half a million tons of shipping sunk, 53 ships including 16 carriers on the bottom) seriously, then it was plausible that they'd send surface forces out to mop up.  One carrier group was sent to hit airfields around Manila on the 15th and 16th, while two others were pulled out of range of Japanese search planes in the hopes of luring them out.  Only one was left in position to protect CripDiv 1, an understandably unpopular move among the men of the group.  One of the captains of the escorting light cruisers commented "Now I know how a worm on a fishhook must feel" and the name "BaitDiv1" began to circulate.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/HoustonAftDamage1stHit.jpg?v=1783746323.jpg' alt='' /><br /><span class='caption'><em>Houston</em> after the catapult was jettisoned</span></span></div>
<p>The men aboard <em>Houston</em> were too busy to think much about that.  First, there was still the matter of flooding.  They had done a good job <a class='wikilink' href='https://www.navalgazing.net/Survivability-Flooding'>stopping the spread of water through the ship</a>, but there were still 6,400 tons of extra water aboard a ship that normally displaced 13,900 tons fully loaded, and a 12&#176; list to starboard.  Normally, this might have been evened out by pumping fluids around, but concerns about the ship's structural integrity and the fact that all of the pumps were busy trying to dewater flooded compartments meant that they would need to jettison weight on the starboard side instead.  Over the side went the starboard catapult and float plane, searchlights, one of the ship's boats and even some armored doors.  The <a class='wikilink' href='https://www.navalgazing.net/Survivability-Mission-Kills'>lack of power</a> meant there was no ventilation down below, and crews worked to dewater compartments on the 3rd Deck in conditions so humid that electrical fires spontaneously broke out.  There was little fresh water, and the only noise besides that of the damage control efforts was the creaking of the ship's hull.  But they were clearly winning their battle, and during the 15th managed to seal off and drain most of the flooded compartments on the 3rd Deck, lightening the ship by 1,900 tons and reducing the list to a mere 8&#176;.
</p>
<p>The Japanese hadn't given up on sinking the "remnants of the American fleet", although their efforts on the 15th were less than successful.  Three air attacks were launched, although the first failed to locate them, the second ran into the buzzsaw of the one carrier group providing a distant screen for CripDiv 1, and the third turned back after the flight leader developed engine trouble.  The 16th dawned inauspiciously aboard <em>Houston</em>, with a major electrical fire breaking out in the emergency steering space.  It was brought under control fairly quickly, although it disrupted the power supply from the main emergency generator aft.  But the forward generator was still operational, although power available was limited because of contaminated fuel, and it provided power to haul in the anchor chain as the crew prepared to transfer the tow from <em>Boston</em> to tug <em>Pawnee</em>, which had finally arrived to release the heavy cruiser for duty as flagship of CripDiv 1.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <img src='/attach/USS_Pawnee_ATF-74.jpeg?v=1786192724.jpeg' alt='' /><br /><span class='caption'><em>Pawnee</em></span></div>
<p>Passing the tow was difficult, as there was still a heavy swell, and the fire had disabled <em>Houston</em>'s rudder control.  As <em>Pawnee</em> came alongside, a wave slammed her into the cruiser's side, where the bigger ship's anchor became entangled on the tug's bulwark.  When the seas reversed and the two ships parted, the anchor tore loose and went crashing through the tug's deck.  Aboard <em>Houston</em>, the anchor chain went whipping across the deck, threatening the legs of any man who didn't jump over it.  Fortunately, there were no actual injuries, and the rest of the process proceeded smoothly.  An hour and a half after they started, <em>Pawnee</em> was pulling <em>Houston</em> into position a mile from <em>Canberra</em>, and took over as the guide ship for the group, as the jammed rudder made <em>Houston</em> the more difficult ship to tow.  
</p>
<p>Unfortunately for everyone involved, the Japanese weren't quite done with the group.  On the 15th, they had dispatched the Second Striking Force, a pair of heavy cruisers, a light cruiser and a destroyer screen, to annihilate the "remnants" of the fleet.  This was exactly what Halsey had wanted, a chance at more of the Japanese surface fleet, but it obviously made the men of CripDiv 1 rather nervous.  Another threat came from the other string on Japan's bow, the air attacks they were still sending against the force.  For some reason the first strike, 99 planes flying from southern Japan, was recalled before it found the target.  The same happened to the Second Striking Force shortly thereafter, when it came under attack by a few planes from <em>Bunker Hill</em>, and the decision to withdraw was confirmed a few hours later when Japanese scouts spotted some of the waiting carriers.  They would survive to take a rather inglorious part at <a class='wikilink' href='https://www.navalgazing.net/The-Battleships-of-Pearl-Harbor-Part-3'>Surigao Strait</a> later in the month.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/HoustonTorpedoedUnderTow.jpeg?v=1786192724.jpeg' alt='' /></span></div>
<p>But the second airstrike, 107 planes from Formosa, was more successful, arriving overhead around 1300.  The outnumbered fighters from <em>Cabot</em> and <em>Cowpens</em> did excellent work, shooting down many of the attackers<a class='footnote' id='fnr2_2' href='#fn2_2'><sup>2</sup></a> and scattering most of the rest, but a trio of land-based torpedo bombers penetrated the screen around the crippled cruisers.  <em>Houston</em>, without power, had to rely on her <a class='wikilink' href='https://www.navalgazing.net/Secondary-Armament-Part-4'>20mm guns and what her 40mms could do in manual mode</a>.  It wasn't enough, and one of the bombers, a <a class='urllink' href='https://en.wikipedia.org/wiki/Yokosuka_P1Y_Ginga' rel='nofollow'>Fran</a>, dropped a torpedo dead astern before crashing a few moments later, riddled by AA fire from the cruiser.  The 20mm gunners switched their fire to the torpedo, but their efforts were in vain, and the weapon struck on the starboard side of the stern, underneath the floatplane hangar that took up a lot of the stern and, more importantly, underneath the supply of aviation gasoline for the <a class='wikilink' href='https://www.navalgazing.net/Battleship-Aviation-Part-3'>floatplanes</a>.  The hangar hatch was blown into the sky, slicing the crane in two as it went, and most of the men who had been manning the aft pair of 20 mm guns were blown overboard.  A massive fire erupted from the volatile avgas, soon spreading to the oil slick that <em>Houston</em> had been trailing, and endangering the men in the water.<a class='footnote' id='fnr2_3' href='#fn2_3'><sup>3</sup></a>  Forward of <em>Houston</em>, <em>Pawnee</em> was also in a tricky situation.  She, like <em>Houston</em>, had weathered an air attack at only 4 kts, unable to dodge, and she was shackled to a now-burning cruiser of unknown structural integrity.  Her captain ordered the message "WE'LL STAND BY YOU" transmitted to <em>Houston</em>, but also stationed a sailor with an acetylene torch to cut the towing cable in case the cruiser sank.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/HoustonDamageControlChart.jpg?v=1786192863.jpg' alt='' /><br /><span class='caption'>The diagram from the <a class='urllink' href='https://www.history.navy.mil/research/library/online-reading-room/title-list-alphabetically/w/war-damage-reports/uss-houston-cl81-war-damage-report-no-53.html' rel='nofollow'>damage report</a>. Click to enlarge.</span></span></div>
<p>But the men still aboard <em>Houston</em> had bigger things on their minds.  After the initial shock of the torpedo hit, they rallied, laying out the fire hoses (previously kept rolled up for fear they would be cut by shrapnel during an attack) and rigging pumps.  <a class='wikilink' href='https://www.navalgazing.net/Survivability-Fire'>Foam quickly brought the fire, already dwindling as the avgas burned itself out, under control</a>, and within 20 minutes, the crew could turn their attention to the other effects of the hit.  The most obvious was that the hangar was now flooded, adding a thousand tons or so to the ship and basically undoing all of the pumping and jettisoning the crew had done so far.  To make matters worse, the water in the hangar was sloshing back and forth, not only adding significant <a class='wikilink' href='https://www.navalgazing.net/Stability'>free surface</a> to the problems facing the ship, but also threatening to smash through the bulkheads.  We'll pick up the story with their attempts to deal with this threat next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn2_1'>
<p><span class='footnote-number'>1</span> Own work, based on <a class='urllink' href='https://www.naturalearthdata.com' rel='nofollow'>Natural Earth Data</a>. <a href='#fnr2_1'>&#8657;</a>
</p></div><div class='footnote' id='fn2_2'>
<p><span class='footnote-number'>2</span> American claims were 41, the Japanese admitted to the loss of 27. <a href='#fnr2_2'>&#8657;</a>
</p></div><div class='footnote' id='fn2_3'>
<p><span class='footnote-number'>3</span> Ultimately, only four of the ten men blown overboard from the fantail survived, but several were killed immediately. <a href='#fnr2_3'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Museum-Reviews-Upstate-New-York</guid>
<link>https://www.navalgazing.net/Museum-Reviews-Upstate-New-York</link>
<title>Main / Museum Reviews - Upstate New York</title>
<dc:date>2026-08-02T12:00:00Z</dc:date>
<pubDate>Sun, 02 Aug 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>After the Naval Gazing meetup in Dayton, my parents and I headed for Montreal,<a class='footnote' id='fnr3_1' href='#fn3_1'><sup>1</sup></a> which meant a road trip, mostly across upstate New York.  I've already talked about one of the museums we visited along the way, <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-Old-Fort-Niagara'>Old Fort Niagara</a>, but there were several others, none of which deserve a full review of their own.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/PortByronCanalBoat.jpg?v=1785620131.jpg' alt='' /><br /><span class='caption'>The canal boat at Port Byron</span></span></div>
<p>The first was only sort of naval-related, but fits well with my general interests.  The <a class='urllink' href='https://newyorkcanals.org/the-heritage-park' rel='nofollow'>Old Erie Canal Heritage Park at Port Byron</a> is just west of Syracuse and right off I-90, and is dedicated to the history of, unsurprisingly, the Erie Canal, originally opened in 1825.  This was one of the great wonders of the era, dramatically easing transportation between the Hudson River Valley and the interior of the continent, and this fairly small park has the remains of one of the locks, as well as an old tavern, where crews would get a beer while their boat was locked through, and a visitor center with some exhibits on the construction and history of the Canal.  The tavern has recently been restored, and is a fairly typical slice-of-life history museum, while the museum has recently acquired a replica canal boat, which they are in the process of setting up to open to the public.  On the whole, it's a pretty nice way to take a break if you happen to be cruising that part of I-90, although it's probably not worth going particularly far out of your way for.
</p>
<p>Afterwards, on the way up to the Canadian border, I visited the <a class='urllink' href='https://history.army.mil/Army-Museum-Enterprise/Find-an-Army-Museum/10th-Mountain-Division-and-Fort-Drum-Museum/' rel='nofollow'>10th Mountain Division and Fort Drum Museum</a>, covering both the Army's activities in northern New York, and the history of the <a class='urllink' href='https://en.wikipedia.org/wiki/10th_Mountain_Division' rel='nofollow'>10th Mountain Division</a>, which is based there, in an area chosen back during WWII for its suitability for training armored forces and general lack of mountains.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/10thMountainKowiaWarrior.jpg?v=1785620130.jpg' alt='' /><br /><span class='caption'>A <a class='urllink' href='https://en.wikipedia.org/wiki/Bell_OH-58_Kiowa' rel='nofollow'>Kiowa Warrior</a> on display outside the museum</span></span></div>
<p>The 10th Mountain Division was activated during WWII to give the US expertise in cold-weather and mountain warfare, and the initial population was heavily drawn from members of the Ski Patrol and other expert mountaineers and skiers.  One battalion was used to spearhead the <a class='urllink' href='https://en.wikipedia.org/wiki/Operation_Cottage' rel='nofollow'>"recapture" of Kiska</a>, but other than that, they didn't get overseas until 1945, taking part in the last stages of fighting in northern Italy.  After the war the division was disbanded, although veterans went on to found more than half of all ski resorts in the US.  It was briefly reactivated as the 10th Infantry Division in the 50s, then shut down again until the mid-80s, when it was reactivated once again as a light, deployable infantry division in the last-ever major expansion of the US Army.  Since then, it has been deployed all over, from natural disasters in the US to Somalia and Haiti to dozens of tours in Afghanistan and Iraq.  Despite the name, it has no particular expertise in mountain warfare today, although it might be the premier cold-weather force in the US given how cold the area gets.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/10thMountainWeasel.jpg?v=1785620132.jpg' alt='' /><br /><span class='caption'>An M29 Weasel and sled at the museum</span></span></div>
<p>The museum itself is pretty small, and I was able to read basically every sign there in about an hour.  But it was well-done and quite informative about an area of military activity I'm not particularly familiar with.  One section covered the history of the area, from military activities before Europeans arrived through its use as a maneuver area in WWII, where, among other units, the <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-45th-Infantry-Division-Museum'>45th Infantry Division</a> did training.  Then it was the history of the 10th Mountain, which trained in Colorado during the war.  This is split up between a big WWII room, including an <a class='urllink' href='https://en.wikipedia.org/wiki/M29_Weasel' rel='nofollow'>M29 Weasel</a>, and another section about the activation and activities of the modern division.  Which comes up basically to the present, because the museum was opened in 2022, so even the Afghanistan War is past rather than present.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/PXL_20260520_184050593.jpg?v=1785620916.jpg' alt='' /><br /><span class='caption'>A sign in the bathroom</span></span></div>
<p>The only real downside is that Fort Drum is kind of in the middle of nowhere, and the museum isn't big enough to be worth going very far out of your way for.  But if you happen to be passing through Watertown, it's worth taking some time to visit.  It's an interesting and competent museum, and they also took advantage of their bathrooms to deliver a bit more information, something I really like when museums do.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/BulbasaurSaratogaBluffs.jpg?v=1785620132.jpg' alt='' /><br /><span class='caption'>The view down onto the Hudson.  Also, it's a really pretty area.</span></span></div>
<p>Lastly, we flew out of Albany, and on our way south, we stopped by the <a class='urllink' href='https://www.nps.gov/sara/index.htm' rel='nofollow'>Saratoga battlefield</a>.  There's a nice visitor center, including a lovely room about the wider global context of the Revolutionary War, and a driving tour of the battlefield, which is managed to keep it looking approximately like it did during the battle itself.  It's an interesting chance to get out and study the terrain of a historic battle more or less intact.  Looking down on the Hudson from the bluffs makes it abundantly clear why the battle was fought where it was, although we were shorter on time than I would have liked.  Still, it was a nice day, and worth a visit if you happen to be in the Albany area.  The other thing potentially worth doing in the Albany area is the destroyer escort <em>Slater</em>, which would have had priority except that, like in Buffalo, we were through on a day she was closed.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn3_1'>
<p><span class='footnote-number'>1</span> The prime attraction there was the Canadian Grand Prix, which was a lot of fun, but also sort of outside my scope here. <a href='#fnr3_1'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Open-Thread-195</guid>
<link>https://www.navalgazing.net/Open-Thread-195</link>
<title>Main / Open Thread 195</title>
<dc:date>2026-07-31T12:00:00Z</dc:date>
<pubDate>Fri, 31 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>It's time once again for our regular Open Thread.  Talk about whatever you want, so long as it isn't culture war.
</p>
<p>Something of interest to lots of you is <a class='urllink' href='https://elouda.itch.io/naval-estimates' rel='nofollow'>Naval Estimates</a>, a new game that is best described as Rule the Waves, but with a much more detailed engineering simulator built in.  Or at least that's the plan.  Right now, it's just the weapon and ship design simulator that's available, and it's just set up for the British, c.1905.  That said, it's remarkably good for that.  I did some checking against a few books, and it does as good a job as you can ask modeling pretty much everything.  I plan to do a longer writeup when the battle system is available, but it's still an impressive result for a one-man operation, and Elouda (the creator) is hopefully just getting started.
</p>
<p>Overhauls are <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-USS-Batfish'>my review of <em>Batfish</em></a>, <a class='wikilink' href='https://www.navalgazing.net/Falklands-Part-4'>Falklands Part 4*</a>, <a class='wikilink' href='https://www.navalgazing.net/Museum-Ships-United-States'>Museum Ships - United States</a>, Signalling Parts <a class='wikilink' href='https://www.navalgazing.net/Signalling-Part-1'>one</a>, <a class='wikilink' href='https://www.navalgazing.net/Signalling-Part-2'>two</a> and <a class='wikilink' href='https://www.navalgazing.net/Signalling-Part-4'>four</a>, <a class='wikilink' href='https://www.navalgazing.net/Nuclear-Weapons-at-Sea-ASW-Part-1'>NWAS - ASW Part 1</a>, <em>Zumwalt</em> Parts <a class='wikilink' href='https://www.navalgazing.net/The-Zumwalt-Class-Part-1'>one</a> and <a class='wikilink' href='https://www.navalgazing.net/The-Zumwalt-Class-Part-2'>two</a> and for 2025, <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-Oakland-Aviation-Museum'>my review of the Oakland Air Museum</a>, Military Spaceflight Parts <a class='wikilink' href='https://www.navalgazing.net/Military-Spaceflight-Part-11'>eleven</a> and <a class='wikilink' href='https://www.navalgazing.net/Military-Spaceflight-Part-12'>twelve</a> and <a class='wikilink' href='https://www.navalgazing.net/Allied-Military-Aircraft-Part-1'>Allied Military Aircraft Part 1</a>.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/The-Tanker-War-Part-3</guid>
<link>https://www.navalgazing.net/The-Tanker-War-Part-3</link>
<title>Main / The Tanker War Part 3</title>
<dc:date>2026-07-26T12:00:00Z</dc:date>
<pubDate>Sun, 26 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>When Iraq's 1980 invasion of Iran ended in a bloody stalemate, it was natural for both sides to turn to other ways of bringing pressure on their enemies.  These ranged from <a class='urllink' href='https://en.wikipedia.org/wiki/War_of_the_cities' rel='nofollow'>firing missiles at the other guy's cities</a> to <a class='wikilink' href='https://www.navalgazing.net/The-Tanker-War-Part-1'>attacking the oil exports that fueled their economies</a>.  Iraq had started to route its exports through Kuwait and Saudi Arabia, and as Iran expanded its attacks to include neutral shipping, the US grew increasingly concerned, both about the flow of oil from the Arabian Gulf,<a class='footnote' id='fnr4_1' href='#fn4_1'><sup>1</sup></a> and potential Soviet influence in that vital region.  As a result, the Administration agreed in March 1987 to reflag 11 Kuwaiti tankers as American vessels, allowing the USN to escort them through the Gulf.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Damaged_USS_Stark_at_Bahrain_with_USS_La_Salle_in_May_1987.jpeg?v=1785028263.jpeg' alt='' /><br /><span class='caption'><em>Stark</em> next to flagship <em>La Salle</em> in Bahrain</span></span></div>
<p>Two months later, even before the escort operations began, <a class='wikilink' href='https://www.navalgazing.net/The-Tanker-War-Part-2'>the frigate <em>Stark</em> was accidentally attacked by the Iraqis in a tragic case of mistaken identity</a>.  Previously, the increasing US involvement in the Gulf had been a matter of little concern, but 37 dead sailors was enough to get the country's attention.  Opponents of the administration charged that it was involving the US in an open-ended war against Iran without thinking through what would be needed to win or getting the approval of Congress.  Many compared it to the Administration's <a class='urllink' href='https://en.wikipedia.org/wiki/1983_Beirut_barracks_bombings' rel='nofollow'>bungled Lebanon strategy</a> of a few years earlier.  A particular concern was that the Iranians usually attacked tankers in retaliation for Iraqi strikes, so the vulnerability of American ships depended heavily on what Saddam did, and he wasn't even vaguely an ally.  But he was smart enough to pause attacks on Iranian shipping as the escort operation began.  The Iranians were obviously upset, but their actions rarely matched their rhetoric, so the reflagging went ahead and the first convoy was scheduled for late July 1987.  
</p>
<p>There was controversy over the management of the escort operation even before it started.  <a class='urllink' href='https://en.wikipedia.org/wiki/United_States_Central_Command' rel='nofollow'>Central Command (CENTCOM)</a>, which controlled forces inside the Gulf, had been set up only four years earlier, and many in the Navy believed that the convoy operation, named Earnest Will, should be run by <a class='urllink' href='https://en.wikipedia.org/wiki/United_States_Indo-Pacific_Command' rel='nofollow'>Pacific Command (PACOM)</a>, which was vastly more experienced and controlled everything up to the Strait of Hormuz.  Ultimately, though, the existing command structure would be respected, which meant that while the actual convoy would be under CENTCOM control, the bulk of the air support would be provided by the PACOM-owned carrier <em>Constellation</em> in the Arabian Sea.  Unfortunately, this was the only air support available, as both Kuwait and Saudi Arabia refused to let the US use their bases, which meant that north of Bahrain, the convoy would be more or less on its own in the face of potential Iranian threats.<a class='footnote' id='fnr4_2' href='#fn4_2'><sup>2</sup></a>  The biggest concern was the Chinese-made <a class='urllink' href='https://en.wikipedia.org/wiki/Silkworm_%28missile%29' rel='nofollow'>Silkworm missile</a>, primarily positioned to cover the strait of Hormuz.  Elsewhere along the route, the main threat came from the armed speedboats known as <a class='urllink' href='https://en.wikipedia.org/wiki/Boghammar' rel='nofollow'>"Boghammars"</a>.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Iranian_Boghammer_in_the_1980s_colored.jpg?v=1785028264.jpg' alt='' /><br /><span class='caption'>A Boghammar at sea</span></span></div>
<p>Unfortunately, the USN didn't have a great answer to either threat with the available forces.  <a class='wikilink' href='https://www.navalgazing.net/Aegis'>Aegis</a> was not in wide service yet, and while shooting down a Silkworm wasn't impossible, it also wasn't something they could count on.  The Boghammars were an even more serious problem, as American training and doctrine had emphasized open-ocean warfare against the Soviets, not fighting speedboats in the confined waters of the Gulf.  One thing not well-addressed by this plan was mines, which both Iraq and Iran had laid in considerable quantities.  The USN hadn't commissioned a new minesweeper since 1958,<a class='footnote' id='fnr4_3' href='#fn4_3'><sup>3</sup></a> preferring to rely on NATO allies for the job, but that was obviously impossible here.  They did provide some aid to the Saudis and Kuwaitis in clearing a minefield laid by the Iranians near the shipping channel, but mine protection for the convoy would come solely from sailors in the bows with binoculars and rifles, a tactic mostly effective against mines that had come loose and were drifting.  The only real solution they had to this was deterrence, threatening severe retaliation against Iran for any attack on the convoys.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Earnest_Will_Bridgeton.jpg?v=1785028486.jpg' alt='' /><br /><span class='caption'><em>Bridgeton</em></span></span></div>
<p>The first convoy would include only two merchant ships, <a class='wikilink' href='https://www.navalgazing.net/Merchant-Ships-Oil-Tankers'>supertanker</a> <em>Bridgeton</em> and <a class='wikilink' href='https://www.navalgazing.net/Merchant-Ships-Specialized-Tankers'>LNG carrier</a> <em>Gas Prince</em>, protected by cruiser <em>Fox</em>, destroyer <em>Kidd</em><a class='footnote' id='fnr4_4' href='#fn4_4'><sup>4</sup></a> and frigate <em>Crommelin</em>.  Things didn't get off to a good start when House Armed Services Committee Chairman <a class='urllink' href='https://en.wikipedia.org/wiki/Les_Aspin' rel='nofollow'>Les Aspin</a> told reporters about the convoy's July 22nd departure date a week before it sailed, but that morning, <em>Fox</em> led the other ships into the Strait of Hormuz.  Fighters from <em>Constellation</em> prowled overhead, and radars probed for Silkworms.  In the heart of the missile envelope, the escorts moved in close, hoping that if a Silkworm leaked through, it would head for the larger and less vulnerable merchantman.  Other merchant ships generally steered clear of the area, with traffic falling to a third of its normal level, but the only opposition was a trio of Iranian Phantoms, quickly scared off by the fire control radars of the escorts.
</p>
<p>The next challenge was the Iranian Boghammar base on <a class='urllink' href='https://en.wikipedia.org/wiki/Abu_Musa' rel='nofollow'>Abu Musa Island</a>, just outside the western entrance to the Strait, and they passed it shortly after darkness fell.  To make things more nerve-wracking, the area near the island was teeming with fishing boats and <a class='urllink' href='https://en.wikipedia.org/wiki/Dhow' rel='nofollow'>dhows</a>, and it was impossible to tell on a radar screen if a small boat that refused to get out of the way was attempting to attack or just a sailor who was going on as his ancestors had for centuries.  But no Iranians appeared, and the daytime passage past Bahrain went smoothly, even as the Iranians declared it was carrying "prohibited goods of some sort".  The only remaining obstacle was a second Boghammar base on <a class='urllink' href='https://en.wikipedia.org/wiki/Farsi_Island' rel='nofollow'>Farsi Island</a>, smack in the middle of the Gulf about halfway between Qatar and Kuwait.  The original schedule also had the convoy passing Farsi at 3 AM, at least until AWACS covering the area picked up Iranian speedboats operating in the area.  Nobody was particularly interested in a night battle with the Boghammars, so the convoy was ordered to stop for a few hours and make the passage after daybreak.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/BridgetonFromKidd.jpg?v=1785028936.jpg' alt='' /><br /><span class='caption'><em>Bridgeton</em> as seen from <em>Kidd</em></span></span></div>
<p>The Iranians had gone home by the time the sun rose, and <em>Fox</em> led the convoy past Farsi Island, with <em>Bridgeton</em> a thousand yards behind her.  A few minutes before 7, the temperature had just hit 100&#176;F, and breakfast was being served aboard <em>Bridgeton</em> when an enormous shock struck the ship near the bow, sending objects flying on the bridge a thousand feet aft and knocking a sleeping crewman out of his bunk.  Fortunately, nobody was seriously injured, but it soon became clear that the tanker had hit a mine, laid by the Iranians the previous night.  Fortunately, being enormous meant that despite taking on 20,000 tons of water, more than the combined displacement of the escorts, <em>Bridgeton</em> was still basically intact and able to continue to Kuwait.  <em>Bridgeton</em>'s captain, a retired USN officer, suggested that the other vessels get in behind her, using his ship as a "deep-draft minesweeper".  The suggestion was accepted with alacrity, although the convoy commander chose to press on, assuming that the Iranians had laid only a single line of mines across the shipping channel.  Sentries were stationed in the bow with rifles, but no further mines were encountered<a class='footnote' id='fnr4_5' href='#fn4_5'><sup>5</sup></a> and the convoy reached Kuwait without further incident.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/BridgetonMineDamage.jpg?v=1785028937.jpg' alt='' /><br /><span class='caption'>Mine damage to <em>Bridgeton</em>, from <a class='urllink' href='https://www.usni.org/magazines/proceedings/1988/may/ss-bridgeton-first-convoy' rel='nofollow'>a Proceedings article by the ship's captain</a></span></span></div>
<p>But while the damage to <em>Bridgeton</em> was ultimately pretty minor, the damage to the USN's reputation was not.  The first convoy had been the subject of considerable media attention, with a number of journalists aboard both <em>Fox</em> and <em>Kidd</em>, and they quite reasonably pointed out the USN's complete lack of preparation for what was in retrospect a pretty obvious threat.  The Reagan Administration tried to downplay the whole thing, refusing to retaliate due to the lack of American casualties, while the Iranians blamed it on "the Hand of God" and avoided too obviously gloating about their victory.  But it was apparent that if the convoy operation was to continue, the US would need not only better minesweeping capabilities, but also new tactics to deal with the Boghammars.  We'll take a look at those next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn4_1'>
<p><span class='footnote-number'>1</span> Though it's worth noting that this is easy to overstate.  While the start of the Iraq-Iran War triggered a major oil price spike, by 1986 that had turned into a glut, and prices were falling rapidly. <a href='#fnr4_1'>&#8657;</a>
</p></div><div class='footnote' id='fn4_2'>
<p><span class='footnote-number'>2</span> The Saudis did allow a long-term deployment of E-3s to provide AWACS support to US forces in the area, and while this was useful, an E-3 isn't capable of shooting down an Iranian fighter on its own.  Kuwait was also wary of appearing too close to the US, and insisted that the warships stay outside its territorial waters.  They did at least provide an oil tanker to make sure they were fully fueled for the trip home. <a href='#fnr4_2'>&#8657;</a>
</p></div><div class='footnote' id='fn4_3'>
<p><span class='footnote-number'>3</span> In fairness, the USN's main mine warfare force was helicopter-based, and using them was impossible because of the diplomatic issues that kept US fighters out of Kuwait and Saudi Arabia.  As for ships, the <a class='urllink' href='https://en.wikipedia.org/wiki/Avenger-class_mine_countermeasures_ship' rel='nofollow'><em>Avenger</em> class</a> was under construction, and the first one commissioned in September 1987. <a href='#fnr4_3'>&#8657;</a>
</p></div><div class='footnote' id='fn4_4'>
<p><span class='footnote-number'>4</span> Amusingly, <em>Kidd</em> was originally ordered by the Shah of Iran, and taken over by the US after his government fell. <a href='#fnr4_4'>&#8657;</a>
</p></div><div class='footnote' id='fn4_5'>
<p><span class='footnote-number'>5</span> This was at least in large part down to luck.  The Iranians had actually laid two lines of mines, and they simply passed through the second one. <a href='#fnr4_5'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Letters-of-Last-Resort</guid>
<link>https://www.navalgazing.net/Letters-of-Last-Resort</link>
<title>Main / Letters of Last Resort</title>
<dc:date>2026-07-19T12:00:00Z</dc:date>
<pubDate>Sun, 19 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>One of the first tasks of a new British prime minister is writing four letters.  These "Letters of Last Resort", each identically worded and written by hand after a briefing on the destructive power of the <a class='wikilink' href='https://www.navalgazing.net/NWAS-Trident-Part-3'>Trident missile</a>, are sealed and delivered to the four British <a class='urllink' href='https://en.wikipedia.org/wiki/Vanguard-class_submarine' rel='nofollow'><em>Vanguard</em> class submarines</a>.  They contain instructions on what to do in the event of nuclear war, and will only be opened if the submarine's crew determines that Britain has suffered an attack and no orders are forthcoming.  If this doesn't happen, they will be destroyed unopened when the next Prime Minister takes office.
</p>
<div  style='text-align: center;' class='img'> <span class='px'> <img width='600' src='/attach/Vanguard-class_submarine_HMS_Victorious_MOD_45159449.jpg?v=1784323639.jpg' alt='' />  </span></div>
<p>One of the chief problems of any nuclear deterrent is that both the weapons themselves and the command-and-control infrastructure will be prime targets for an enemy's nuclear weapons.  The first problem is relatively easy to deal with, and most countries solve it by sending some of their nukes to sea aboard submarines, which are by nature difficult to find.  The British, in fact, like this approach so much that they <a class='wikilink' href='https://www.navalgazing.net/NWAS-British-Polaris'>chose it for their entire nuclear arsenal</a>.  But nuclear weapons aboard a submarine, while fairly safe, are also of little use if orders to fire them can't be given.  The US solves this with a massive command-and-control infrastructure, including not <a class='urllink' href='https://en.wikipedia.org/wiki/Boeing_E-4' rel='nofollow'>one</a>, not <a class='urllink' href='https://en.wikipedia.org/wiki/Boeing_E-6_Mercury' rel='nofollow'>two</a> but <a class='urllink' href='https://en.wikipedia.org/wiki/Boeing_VC-25' rel='nofollow'>three</a> different converted airliners.  But there are two problems with this kind of system from a British perspective.  First, it's really expensive, and the British can't afford US defense budgets.  Second, Britain is considerably closer to potential threats, who should remain nameless but who I will assign the randomly-chosen name "Russia" to, than the US is.  This gives even less time to get a message off to any nuclear forces, to say nothing of the <a class='wikilink' href='https://www.navalgazing.net/NWAS-Polaris-Part-4'>problems of communicating with SSBNs</a>.
  
</p>
<p>Obviously, Britain has some infrastructure to get messages to the <a class='wikilink' href='https://www.navalgazing.net/Continuous-At-Sea-Deterrent'>Continuous At Sea Deterrent</a>.  The system is centered at <a class='urllink' href='https://en.wikipedia.org/wiki/Northwood_Headquarters' rel='nofollow'>Northwood</a> in the suburbs of London, which in the late 60s was linked to Downing Street by a two-way closed-circuit television system, tested daily.  Unlike the US, Britain didn't have a clear constitutional line of succession, so the Prime Minister designated a pair of "nuclear deputies" that would be empowered to make decisions in an emergency.  But by the early 70s, the threat of a Soviet "bolt from the blue" taking out the entire command and control infrastructure was simply too great, and a uniquely British solution was found.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/MOD_Police_Escort_Trident_submarine_Leaving_Faslane.jpg?v=1784323641.jpg' alt='' /></span></div>
<p>Each submarine would be issued with a sealed letter from the Prime Minister, with instructions that it be opened if it appeared to the crew that Britain had been the victim of a nuclear attack and the country was effectively destroyed.  A number of indicators have been given for this, the most famous (and most curious) being the absence of the long-wave broadcast of <a class='urllink' href='https://en.wikipedia.org/wiki/BBC_Radio_4' rel='nofollow'>the BBC's Radio 4</a>.<a class='footnote' id='fnr5_1' href='#fn5_1'><sup>1</sup></a>  If it looks like Britain is gone, then the letter will be opened, revealing which of the four potential options the Prime Minister has taken:
1. Retaliate
2. Don't retaliate
3. Don't do anything yet, but see if you can find a surviving friendly government (the US and Australia are frequently mentioned) and place yourself under their control
4. Use your own judgement
</p>
<p>Whichever option is taken would probably be the last official act of His Majesty's Government, and might not even have been by the current Prime Minister.  Switching out the letters while a boat is on patrol is obviously impossible, and Tony Blair was rather irritated that one submarine that departed shortly before he took office in 1997 would carry John Major's letter, but the deployment and political schedules don't always align.<a class='footnote' id='fnr5_2' href='#fn5_2'><sup>2</sup></a>  As the use of the letters has thankfully been unnecessary and retired PMs are understandably reluctant to speak on the matter, the only man whose letters we have any insight into is <a class='urllink' href='https://en.wikipedia.org/wiki/James_Callaghan' rel='nofollow'>Jim Callaghan</a>, Prime Minister from 1976 to 1979, who hinted in an interview that he would have ordered retaliation.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/James_Callaghan.jpg?v=1784323640.jpg' alt='' /><br /><span class='caption'>Jim Callaghan</span></span></div>
<p>But all of this requires that the British think about nuclear weapons in a fundamentally different way from the United States.  The United States makes extensive use of <a class='urllink' href='https://en.wikipedia.org/wiki/Permissive_action_link' rel='nofollow'>"Permissive Action Links"</a>, devices that block the use of nuclear weapons unless a code, known only to higher headquarters, is passed to the unit with the bombs.  This was set up to relieve <a class='wikilink' href='https://www.navalgazing.net/Nuclear-Strategy'>Kennedy/Johnson/McNamaraite fears of some unit in the field flying off the handle and starting WWIII</a>, but means that an extensive and robust communications infrastructure is required to make sure America's nuclear arsenal isn't suddenly rendered useless by a nuclear strike.<a class='footnote' id='fnr5_3' href='#fn5_3'><sup>3</sup></a>  The British have instead chosen to place their trust in the officers and men of the Royal Navy.  In theory, if the entire crew of one of the <a class='urllink' href='https://en.wikipedia.org/wiki/Vanguard-class_submarine' rel='nofollow'><em>Vanguard</em>s</a> went crazy together, they could launch their missiles, but in practice, this threat is minuscule.  The launch procedure requires several officers to work together, and even if they were to form a conspiracy to do so without being noticed,<a class='footnote' id='fnr5_4' href='#fn5_4'><sup>4</sup></a> it's almost certain that other members of the crew would interfere if they hadn't gotten proper orders or the confirmation that the Letter of Last Resort was necessary.
</p>
<p>As this goes out, Keir Starmer's letters are about to be recalled and destroyed, and Andy Burnham will sit down to write his version.  I hope and pray we never find out what is in them, or any of those written by his successors.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn5_1'>
<p><span class='footnote-number'>1</span> The long-wave broadcast of BBC Radio 4 was shut down weeks before this post went up.  I don't know what they do now, although the obvious answer is a basic satellite internet service. <a href='#fnr5_1'>&#8657;</a>
</p></div><div class='footnote' id='fn5_2'>
<p><span class='footnote-number'>2</span> I looked into whether or not Liz Truss, who served for only 50 days in 2022, ever got a letter to sea, and the answer wasn't entirely clear.  Patrols in 2022 were running to something like 130 days, so statistically she probably didn't, and internet rumors suggested the same. <a href='#fnr5_2'>&#8657;</a>
</p></div><div class='footnote' id='fn5_3'>
<p><span class='footnote-number'>3</span> This is the reason that the American PAL codes were famously set to all 0s for many years.  The military knew that Dr. Strangelove was fiction, and wanted to be sure they wouldn't be stuck with dud bombs if something happened to Washington before the codes went out. <a href='#fnr5_3'>&#8657;</a>
</p></div><div class='footnote' id='fn5_4'>
<p><span class='footnote-number'>4</span> And this is unlikely because, deep down, very few people want to destroy the world. <a href='#fnr5_4'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Saving-Houston-Part-1</guid>
<link>https://www.navalgazing.net/Saving-Houston-Part-1</link>
<title>Main / Saving ''Houston'' Part 1</title>
<dc:date>2026-07-12T12:00:00Z</dc:date>
<pubDate>Sun, 12 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>On October 14th, 1944, the three carrier groups of TF 38 were conducting strikes on Formosa.  The operation had been planned to provide distant cover for the approaching <a class='wikilink' href='https://www.navalgazing.net/Leyte-Gulf-75'>landings at Leyte</a>, and had been scheduled to wrap up the previous day.  However, <a class='wikilink' href='https://www.navalgazing.net/Saving-Canberra'>heavy cruiser <em>Canberra</em> had been torpedoed during the last set of strikes</a>, and it was decided to tow her home instead of scuttling her, which required an extension.  Three groups would again spend the morning pounding the airfields of Formosa, while the fourth was dispatched against Japanese air bases in northern Luzon.  The strikes themselves encountered little opposition, but also failed to shut down the air bases, and all of the US carriers groups were trailed by snoopers throughout the day.  TG 38.2 and TG 38.3 began to withdraw in the afternoon, leaving behind TG 38.1, the Task Group <em>Canberra</em> had originally been assigned to, to cover the withdrawal of the crippled cruiser.   
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/HoustonUnderwayJan1944.jpg?v=1783746324.jpg' alt='' /><br /><span class='caption'><em>Houston</em> underway earlier in 1944</span></span></div>
<p>As such, it was TG 38.1 that caught the bulk of the Japanese dusk attack, again in the form of <a class='wikilink' href='https://www.navalgazing.net/Air-Attack-on-Ships-Part-3'>torpedo bombers</a>.  11 to 16 Frans appeared, and while most were shot down or driven off by AA fire, a few got through to drop their torpedoes.  This time, their target was light cruiser <em>Houston</em>, transferred from TG 38.2 the previous day to take over <em>Canberra</em>'s station.  She found herself facing three torpedoes in the water, two to port and one to starboard.  Only the one from starboard got through, but it hit in the worst possible spot.  The ship had been turning to evade, rolling heavily to port, so the torpedo detonated against the ship's bottom, halfway between the centerline and the bilge keel, and directly under the <a class='wikilink' href='https://www.navalgazing.net/Engineering-Part-4'>turbines for shaft 1 in the forward engine room</a>.  The space flooded almost instantly, and the explosion damaged the bulkheads forward and aft, flooding both boiler rooms over the next few minutes.
</p>
<div  style='text-align: center;' class='img imgcaption'> <img src='/attach/HoustonMidshipsTorpedoHit.jpg?v=1783746323.jpg' alt='' /><br /><span class='caption'>The damage from the torpedo </span></div>
<p>Even if that had been the extent of the damage, it would have been catastrophic.  The ship's boilers provided steam not only for propulsion but also for the turbogenerators that powered the ship, so <a class='wikilink' href='https://www.navalgazing.net/Survivability-Mission-Kills'><em>Houston</em> fell dark and silent</a>, except for the noises of water rushing in and the ship's damaged hull creaking and groaning as it worked in the waves.  But the destruction of the turbines had other consequences.  One was that, with the reduction gear blown to bits, shaft 1 was dragged aft about 5' by the propeller, damaging the stuffing glands where the shaft passed through the aft engine room, which soon had to be evacuated.<a class='footnote' id='fnr6_1' href='#fn6_1'><sup>1</sup></a>  And the low-pressure turbine itself was thrown upward with enough force to drive the 2" plates of the armored deck about 6" upward under the ship's machine shop, which also opened the way for a jet of high-temperature steam to kill everyone inside.  A bigger long-term problem was that the explosion had warped doors and started seams, making it difficult to control flooding on the 3rd deck above the machinery.  And the shock violently shook the ship, toppling the <a class='wikilink' href='https://www.navalgazing.net/Naval-Radar-Introduction'>air-search radar</a>, although it caused remarkably few <a class='wikilink' href='https://www.navalgazing.net/Underbottom-Explosions'>injuries to ankles or legs</a>, as sailors belowdecks had been trained to sit or lie down whenever possible.
</p>
<p>But in the first few minutes, the biggest threat was to the cruiser's stability.  She was running fairly light on fuel, leaving her somewhat top-heavy even before thousands of tons of floodwater began to slosh back and forth across the engineering spaces.  This <a class='wikilink' href='https://www.navalgazing.net/Stability'>free-surface effect</a> had the cruiser rolling up to 37&#176;, perilously close to the 41&#176; that her crew thought would be enough to turn her over and far enough that the edge of the main deck occasionally dipped below the sea, before the spaces filled and the roll stabilized at 20&#176; or so.  But 5,000 tons of water posed still more problems.  With the extra weight concentrated amidships and the ship held up by buoyancy in the bow and stern, the <a class='wikilink' href='https://www.navalgazing.net/Ship-Structure-and-Strength'>hull girder</a> began to sag and buckle.  Ominous creaks rang through the hull, rivets sprang out of their holes and the bow and stern began to move a bit relative to each other.  The ship's Captain, worried that his ship was about to break up and receiving reports of <a class='wikilink' href='https://www.navalgazing.net/Survivability-Flooding'>progressive flooding</a> on 3rd deck, gave the order to abandon ship about two hours after the torpedo hit.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/HoustonDestroyerTakingOffMen.jpg?v=1783746361.jpg' alt='' /><br /><span class='caption'>A destroyer stands by <em>Houston</em>, ready to take men off, as seen from <em>Boston</em></span></span></div>
<p>Even this was complicated by <em>Houston</em>'s situation.  The ship was rolling too much in the heavy swell for destroyers to safely come alongside, and many men went into the water, relying on lifejackets and rafts for flotation.  The lucky ones were quickly found and rescued, with destroyer <em>Boyd</em> recovering 380 men from <em>Houston</em>, outnumbering her own crew.  The unlucky ones remained adrift throughout the night, as Japanese planes prowling overhead pounced on ships which switched on their searchlights, and the really unlucky ones were never seen again.   
</p>
<p>But many of <em>Houston</em>'s crew were unwilling to abandon their ship, which wasn't obviously going down, and the engineering team soon convinced the Captain to rescind the order and allow them to fight to save the ship.  The first order of business was getting a tow from heavy cruiser <em>Boston</em>, standing by to assist, but even this was complicated.  Most of the deckhands who would normally have done the job of rigging the tow were among the two thirds of the crew that had already gone over the side, and a scratch crew had to be formed to do the hazardous work of rigging the tow.  One early complication was that <em>Boston</em> was riding much higher than <em>Houston</em>, so the normal practice of the towing ship approaching from windward would see her drift down onto the light cruiser.  Instead, she had to make her approach from the downwind side, on a night so dark that the bridge had to be guided by messages relayed from the stern, while aboard <em>Houston</em>, the crew worked to pull the lines over by hand.  Another complication came when they attempted to attach the towing rope to the ship's anchor chain.  The shackle required was held by a bolt that required a small retaining pin, and in the chaos aboard <em>Houston</em>, the retaining pin couldn't be found.  Eventually, the crew decided to substitute rope for the pin, hoping that it would hold.  If it didn't, they'd have to haul the 270' of anchor chain they planned to let out as part of the towing process back aboard before a second tow could be rigged.  Normally, this wouldn't be a big deal, but with all power out, the work would have to be done by hand.<a class='footnote' id='fnr6_2' href='#fn6_2'><sup>2</sup></a>
</p>
<div  style='text-align: center;' class='img imgcaption'> <img src='/attach/HoustonBuckledDeck.jpg?v=1783747053.jpg' alt='' /><br /><span class='caption'>A buckled deck aboard <em>Houston</em></span></div>
<p>Eventually, the work was done, and the crew began to pay out the anchor chain as <em>Boston</em> started to move off.  One problem that was immediately apparent was that the towing cable wasn't long enough.  Normal practice was to make sure the tow line was partially submerged, so that the water dampened shocks and reduced the chance of a sudden surge snapping the tow, which required getting another 270' of chain out.  And while this was going on, the crews belowdecks set to work shoring bulkheads and plugging the numerous leaks that still threatened <em>Houston</em>'s buoyancy.  Cables leaked, hatches didn't seal properly, rivets had sprung and welds had cracked.  But all were eventually fixed with whatever materials were to hand, and the process of pumping out these spaces, occasionally via bucket brigade, began.  By daybreak, the list had been reduced to 12&#176; and it was pretty obvious that <em>Houston</em> had some life left in her.  But she was still days away from being safely out of range of Japanese air attack, and her path to getting there was far from smooth.  We'll pick up the story there next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn6_1'>
<p><span class='footnote-number'>1</span> For the sake of fairness, it's worth noting that <em>Canberra</em> and <em>Houston</em> were the only two of 11 US cruisers torpedoed in the machinery spaces during the war to suffer these kind of problems from shaft damage. <a href='#fnr6_1'>&#8657;</a>
</p></div><div class='footnote' id='fn6_2'>
<p><span class='footnote-number'>2</span> Ultimately, the lashing didn't hold, but the chain kinked in such a way as to keep the bolt in. <a href='#fnr6_2'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Admiralty-Law</guid>
<link>https://www.navalgazing.net/Admiralty-Law</link>
<title>Main / Admiralty Law</title>
<dc:date>2026-07-05T12:00:00Z</dc:date>
<pubDate>Sun, 05 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>"For depriving us in many cases, of the benefits of Trial by Jury:"
</p>
<p>This line from the Declaration of Independence, which we have just celebrated the 250th anniversary of, comes from the practice of trying certain cases relating to navigation, smuggling and the <a class='urllink' href='https://en.wikipedia.org/wiki/Stamp_Act_1765' rel='nofollow'>Stamp Act of 1765</a> in <a class='urllink' href='https://en.wikipedia.org/wiki/Vice_admiralty_court' rel='nofollow'>Vice-Admiralty Courts</a>.  These operated under a completely different legal system from that of the standard Common Law, and as you can guess from the quote, didn't have juries.  From the perspective of actually getting the law enforced, this made a great deal of sense.  In the nascent United States, the Stamp Act was wildly unpopular, as it imposed taxes on various kinds of goods to support British troops stationed in North America after the <a class='urllink' href='https://en.wikipedia.org/wiki/Seven_Years%27_War' rel='nofollow'>Seven Years War</a>.  Local juries would simply refuse to convict even obvious violations, so the Vice-Admiralty courts where judges from England could deliver verdicts directly were the obvious place to turn.  And also an obvious instrument of repressive tyranny that fully justified the Revolution.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img height='440' src='/attach/United_States_Declaration_of_Independence.jpg?v=1783204604.jpg' alt='' /></span></div>
<p>But how did it get to the point that there was this entirely separate system of laws that the British could turn to when they needed to bypass local juries?  The idea of there being a separate Admiralty law, common among nations, is so old that nobody is quite sure how old it is.  Nineteenth-century legal scholars often traced its origins to a code dating to 900 BC on the island of Rhodes, although there's not a ton of evidence that there was a coherent law code dating back quite that far.  However, we do have references to a "Rhodian law" in a Roman law text from the third century AD, the idea that if some part of a vessel's cargo has to be jettisoned in an emergency, the loss will be shared among everyone who had cargo aboard.  Astonishingly, this principle, known as <a class='urllink' href='https://en.wikipedia.org/wiki/General_average' rel='nofollow'>General Average</a>, continues to be part of maritime law today.
</p>
<p>Even as the Roman Empire collapsed and the Mediterranean littoral fragmented, the law of trade and shipping remained surprisingly unified, with specialized courts set up by merchants operating in many ports and attempting to enforce judgements based on what was customary among merchants in the area.  Whoever was running the port was generally content to let the merchants deal with their own disputes, at least so long as they paid their taxes, producing a genuinely international set of laws.  This principle extended as maritime trade began to flourish in the waters of Northwestern Europe in the late Middle Ages, an important source being the <a class='urllink' href='https://en.wikipedia.org/wiki/Rolls_of_Ol%c3%a9ron' rel='nofollow'>Rolls of Oleron</a>, traditionally ascribed to Eleanor of Aquitaine.  In practice, she was probably not personally involved in regulation of the wine trade, but despite this, they became the basis of maritime law in every country in the area, and continue to form part of the foundation of the field to this day.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/LordHighAdmiral.jpg?v=1783204741.jpg' alt='' /><br /><span class='caption'>The Lord High Admiral</span></span></div>
<p>In England, maritime law came under the jurisdiction of the <a class='urllink' href='https://en.wikipedia.org/wiki/Lord_High_Admiral_of_the_United_Kingdom' rel='nofollow'>Lord High Admiral</a>, the senior naval official of the country, and thus became known as Admiralty Law.  But it was still an attempt to implement the international law being developed, and thus moved in step with developments in the rest of Europe, where Roman-inspired Civil Law used judges to deliver verdicts without the need for a jury.  This caused obvious tension between the admiralty courts and the rest of the country, and in 1389, Parliament limited admiralty jurisdiction by statute to "a thing done upon the sea" to stop those courts intruding into land-based matters.  Other courts interpreted this extremely narrowly, claiming that a contract for shipping signed on land was not "a thing done upon the sea".  This more or less moved the traditional "law merchant" functions of the admiralty courts to the common-law courts, and limited them to dealing with <a class='wikilink' href='https://www.navalgazing.net/Letters-of-Marque-Today'>prizes</a>, salvage, seaman's wages and similar matters.  As a result, the Admiralty courts in England<a class='footnote' id='fnr7_1' href='#fn7_1'><sup>1</sup></a> shrank as a specialized branch, and eventually ended up combined, rather oddly, with the Probate and Divorce division of the High Court.<a class='footnote' id='fnr7_2' href='#fn7_2'><sup>2</sup></a>  Today, the only remaining dedicated admiralty court is that for the <a class='urllink' href='https://en.wikipedia.org/wiki/Cinque_Ports' rel='nofollow'>Cinque Ports</a>, <a class='urllink' href='https://cinqueports.org/history/the-courts/' rel='nofollow'>a truly baffling English oddity</a> that looks to be entirely ceremonial today.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Flight_of_Hutchinson_before_the_rioters_1765.jpg?v=1783204740.jpg' alt='' /><br /><span class='caption'>Americans deal with oppressive British officials</span></span></div>
<p>With the growth of Britain's North American colonies, it was obvious that admiralty courts would need to follow, and by 1763, there were nine Vice-Admiralty courts throughout the colonies, unbounded by the statute that limited their English counterparts.  But they were never particularly popular, as they were the chief enforcers of British trade policy.  Some of this was clearly absurd, like the belief that the colonists should <a class='urllink' href='https://en.wikipedia.org/wiki/Sugar_Act' rel='nofollow'>pay taxes on imported goods</a>, while in other cases, there were genuine abuses, such as when naval officers realized they could line their pockets by requesting papers from small coastal trading vessels that Parliament hadn't intended to include in the requirements for stricter documentation, then sending them to be condemned by the admiralty courts.  In normal courts, the use of a jury would temper the implementation of London's policy, but that obviously wasn't the case in the admiralty courts.<a class='footnote' id='fnr7_3' href='#fn7_3'><sup>3</sup></a>  Things were made worse when the Stamp Act of 1765 deliberately gave jurisdiction over cases, which were not particularly maritime-related, to the admiralty courts.  There was actually some basis for this.  Britain had specialized courts for everything, including cases involving revenue, but there was no Court of Exchequer in America,<a class='footnote' id='fnr7_4' href='#fn7_4'><sup>4</sup></a> and given colonial feelings, the admiralty courts were much more likely to actually enforce the law.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Supreme_Court_2022.png?v=1783205070.png' alt='' /><br /><span class='caption'>The highest admiralty court, 2022</span></span></div>
<p>The tension continued until the outbreak of open hostilities in 1775, when the Americans suddenly realized that they might need admiralty courts of their own if they wanted to be able to seize British ships as prizes without being considered pirates under international law.  Massachusetts was among the first to set up such a court, although their version used a jury, at least for a few years, before it was decided that admiralty law was simply too complicated for "good and lawful men".  Things were made even more complicated a few years later, when the <a class='urllink' href='https://en.wikipedia.org/wiki/Articles_of_Confederation' rel='nofollow'>Articles of Confederation</a> assigned some parts of admiralty law, most notably dealing with prizes, to the Continental Congress.  After those failed, the Constitution adopted in 1787 fully gave admiralty jurisdiction to the new Federal government, and it has become part of the normal powers of the Federal court system.  In some areas, it forms a significant portion of the docket, but it's really only of interest to specialists and weirdos with absurd theories about the meaning of a fringe on a flag.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn7_1'>
<p><span class='footnote-number'>1</span> This also applied later, and with slightly different details, to Wales, Scotland and Northern Ireland.  And probably also the Channel Islands and the Isle of Man, but none of my sources specifically had anything to say about them. <a href='#fnr7_1'>&#8657;</a>
</p></div><div class='footnote' id='fn7_2'>
<p><span class='footnote-number'>2</span> Actually, this is slightly less odd than it sounds.  Traditionally, personal property and divorce were the responsibility of the church courts, and even after it became part of the normal court system, it remained heavily influenced by civil law, with judges acting without juries. <a href='#fnr7_2'>&#8657;</a>
</p></div><div class='footnote' id='fn7_3'>
<p><span class='footnote-number'>3</span> This isn't to say that the vice-admiralty courts were always perfect instruments of the oppressor's will.  In Rhode Island in the 1760s, for instance, the judge and prosecutor were both natives, and frustrated attempts by the customs collector to enforce the laws. <a href='#fnr7_3'>&#8657;</a>
</p></div><div class='footnote' id='fn7_4'>
<p><span class='footnote-number'>4</span> Though it is worth pointing out that this was a common-law court with juries. <a href='#fnr7_4'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Open-Thread-194</guid>
<link>https://www.navalgazing.net/Open-Thread-194</link>
<title>Main / Open Thread 194</title>
<dc:date>2026-07-03T12:00:00Z</dc:date>
<pubDate>Fri, 03 Jul 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>It's time once again for our regular Open Thread.  Talk about whatever you want, so long as it isn't Culture War.
</p>
<p>Overhauls are <a class='wikilink' href='https://www.navalgazing.net/Jackie-Fisher'>Jackie Fisher</a>, <a class='wikilink' href='https://www.navalgazing.net/Auxiliaries-Part-2'>Auxiliaries Part 2</a>, <a class='wikilink' href='https://www.navalgazing.net/Impressment'>Impressment</a>, <a class='wikilink' href='https://www.navalgazing.net/The-3T-Missiles-Introduction'>The 3T Missiles - Introduction</a> and for 2025, my reviews of <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-Fort-Point'>Fort Point</a> and <a class='wikilink' href='https://www.navalgazing.net/Museum-Review-Nike-Site-SF88'>Nike Site SF88</a>, <a class='wikilink' href='https://www.navalgazing.net/Thoughts-on-the-Israel-Iranian-War'>Thoughts on the Israel-Iranian War</a> and <a class='wikilink' href='https://www.navalgazing.net/The-Tanker-War-Part-1'>The Tanker War Part 1</a>.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Saving-Canberra</guid>
<link>https://www.navalgazing.net/Saving-Canberra</link>
<title>Main / Saving ''Canberra''</title>
<dc:date>2026-06-28T12:00:00Z</dc:date>
<pubDate>Sun, 28 Jun 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>On Friday, October 13th, 1944, <a class='urllink' href='https://en.wikipedia.org/wiki/Fast_Carrier_Task_Force' rel='nofollow'>TF 38</a> was conducting strikes off the coast of Formosa (now Taiwan).  It was the second and final day of an operation to wipe out Japanese air strength on the island in preparation for the upcoming <a class='wikilink' href='https://www.navalgazing.net/Leyte-Gulf-75'>landings on Leyte</a>, and they had been reasonably successful all day.  But as evening fell, a group of Japanese Betty <a class='wikilink' href='https://www.navalgazing.net/Air-Attack-on-Ships-Part-3'>torpedo bombers</a> attacked, coming in so low that radar failed to spot them.  Four went for the carrier <em>Franklin</em> and while all of their torpedoes missed, one crashed onto her deck, bursting into flames before sliding over the side.<a class='footnote' id='fnr8_1' href='#fn8_1'><sup>1</sup></a>  Eight others bored in on heavy cruiser <a class='urllink' href='https://en.wikipedia.org/wiki/USS_Canberra_%28CA-70%29' rel='nofollow'><em>Canberra</em></a>,<a class='footnote' id='fnr8_2' href='#fn8_2'><sup>2</sup></a> and while six were shot down by the group's AA fire, one of the torpedoes struck home, detonating at the boundary between the two aft boiler rooms.  A mast-high fireball was followed by the usual geyser of water, and violent vertical vibrations ran through the hull.  Both boiler rooms flooded almost immediately, leaving no survivors, and fuel oil blown out of the air intakes from boiler 4 covered the deck nearby, but fortunately didn't ignite.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CanberraOct101944.jpeg?v=1782590155.jpeg' alt='' /><br /><span class='caption'><em>Canberra</em> with 3rd Fleet a few days before being torpedoed</span></span></div>
<p>But the bigger problem was that the explosion was directly under one of the bearings for shaft 1, which was ripped from the reduction gearing forward and thrown upwards and inboard, tearing holes in the bulkheads of both the fore and aft engine rooms.  Water began pouring into both, filling the aft engine room in 4 minutes and the forward one in 10.  Although the boilers in the forward two rooms remained intact and continued to generate power, <em>Canberra</em> was dead in the water.  Her rudder was also jammed over, the result of a last-minute attempt to dodge the torpedo, and while the emergency diesel generator would normally have provided power to the steering gear, breakers kept tripping.  Eventually, the rudder was put amidships using the ship's roll, opening the hydraulic valves on the steering gear to allow it to swing amidships, then closing them to stop it swinging back.  The electrical problems were not helped by numerous leaks in spaces fore and aft of the flooded machinery spaces, as the stuffing glands for electrical cables proved to be less watertight than expected.  <a class='wikilink' href='https://www.navalgazing.net/Survivability-Flooding'>The leaks were all controlled fairly quickly</a>, thanks to the cruiser's highly-trained damage control team, and only a few spaces saw more than a couple inches of water.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CanberraFire3IntoFire4Shaft.jpg?v=1782590161.jpg' alt='' /><br /><span class='caption'>The bent shaft, looking aft</span></span></div>
<p>But although there was no particular danger of her sinking, <em>Canberra</em> was still stranded 90 miles off an enemy-held coast, and she was unlikely to move under her own power without a stint in drydock.  Normal procedure would have been to simply take off the crew and scuttle the ship, but the strength of the American carrier force prompted <a class='urllink' href='https://en.wikipedia.org/wiki/William_Halsey_Jr' rel='nofollow'>Admiral Halsey</a> to take a chance and order another day of air strikes on Formosa while <em>Canberra</em> was towed clear, allowing the ship to be repaired to fight another day.  Fellow heavy cruiser <a class='urllink' href='https://en.wikipedia.org/wiki/USS_Wichita_%28CA-45%29' rel='nofollow'><em>Wichita</em></a> was ordered to take the stricken ship under tow, and within 20 minutes, her crew had the necessary lines rigged out on deck.  But the winds were high and a heavy swell was running, and while the initial messenger lines were passed successfully, at one point the two ships yawed apart so violently that a 4.5" manila line crushed three sailors,<a class='footnote' id='fnr8_3' href='#fn8_3'><sup>3</sup></a> then knocked a fire hydrant loose, sending water spewing high into the air.  The line then snapped, but <em>Wichita</em>’s quick-thinking crew passed another line and managed to get the towing wire across on their second attempt.  Unfortunately, they hadn't sent their towing shackle, and <em>Canberra</em>’s was too big to fit into the eye on the rope.  It took about two hours, but <em>Canberra</em>’s crew managed to attach the wire to the port anchor chain with a couple of spares and <em>Wichita</em> set off, slowly turning towards the southeast.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CanberraDamageDiagram.jpg?v=1782590160.jpg' alt='' /><br /><span class='caption'>The diagram from the <a class='urllink' href='https://www.history.navy.mil/content/history/nhhc/research/library/online-reading-room/title-list-alphabetically/w/war-damage-reports/uss-canberra-ca70-war-damage-report-no54.html' rel='nofollow'>damage report</a>.  Click to enlarge.</span></span></div>
<p>The night was spent shoring up bulkheads, plugging leaks and dewatering spaces outside the machinery.  Emergency power cables had already been strung before the attack, allowing quick restoration of power through most of the aft portion of the ship.  Communication was harder to restore, as many of the relevant circuits had shorted out in the flooded spaces.  And because all of the evaporators<a class='footnote' id='fnr8_4' href='#fn8_4'><sup>4</sup></a> were inaccessible, extreme measures to conserve fresh water began immediately.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CanberraHoustonUnderTow.jpeg?v=1782590156.jpeg' alt='' /><br /><span class='caption'><em>Canberra</em> and <em>Houston</em> under tow</span></span></div>
<p>Things were made more complicated when light cruiser <em>Houston</em>, detailed to take over <em>Canberra</em>'s spot, was torpedoed the next day,<a class='footnote' id='fnr8_5' href='#fn8_5'><sup>5</sup></a> and again the decision was made to tow her clear.  The two cruisers were assigned to what was known as "CripDiv (Cripple Division) 1" and provided with air cover from a pair of CVLs and some light cruisers and destroyers as escorts, while they were slowly towed out of the range of enemy aircraft.  On the morning of the 15th, tugs <em>Munsee</em> and <em>Pawnee</em> arrived, with <em>Munsee</em> taking over the tow from <em>Wichita</em>.  Aboard <em>Canberra</em>, the crew continued the slow work of dealing with the problems of a ship with the middle full of water, which occasionally meant things like manually rebuilding pipes to keep salt water out of the boilers.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CanberraDrydockClaxtonKillen.jpeg?v=1782590157.jpeg' alt='' /><br /><span class='caption'><em>Canberra</em> in drydock at Manaus, with destroyers <em>Claxton</em> and <em>Killen</em></span></span></div>
<p>On the 20th, a week after she was torpedoed and halfway to the forward base at <a class='wikilink' href='https://www.navalgazing.net/Auxiliaries-Part-3'>Ulithi</a>, salvage ship <em>Current</em> came alongside, transferring extra pumps and divers who were able to go in and salvage several pump motors from the forward engine room, as well as doing preliminary work on a patch for the hole in that space.  A first attempt while at sea failed, but the second, made the day after reaching Ulithi, succeeded, and then it was a simple matter of pumping out the space and shoring up the bulkhead, the main complication being that asbestos insulation in the water kept plugging up the pumps.  The motors were used to put one of the evaporators back in operation, giving the ship fresh water for the week's tow to Manaus, where she was finally <a class='wikilink' href='https://www.navalgazing.net/Drydocks'>drydocked</a>.  The extent of the damage could finally be fully understood, the holes were patched, any salvageable equipment was preserved to make it easier to restore to operation, all three surviving shafts were put back in operation, and in January, she departed for Boston Navy Yard under her own power.  Repairs would ultimately stretch past the end of the war, and <em>Canberra</em> would go on to serve as one of the first platforms for the <a class='wikilink' href='https://www.navalgazing.net/The-3T-Missiles-Introduction'>Terrier missile</a>.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/USS_Canberra_CAG-2_at_sea_c1956.jpg?v=1782590348.jpg' alt='' /><br /><span class='caption'><em>Canberra</em> in the 50s, showing her missiles aft</span></span></div>
<p>But <em>Canberra</em>'s was not the most dramatic survival story that played out in the eastern reaches of the Philippine Sea in October 1944.  <em>Houston</em> was hit not once but twice, and lost not only her propulsion but also all boilers.  We'll look at her story next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn8_1'>
<p><span class='footnote-number'>1</span> For those who might be confused, this is a separate incident from when <a class='wikilink' href='https://www.navalgazing.net/OCallahan-and-the-Franklin'><em>Franklin</em> was badly damaged in March 1945</a>. <a href='#fnr8_1'>&#8657;</a>
</p></div><div class='footnote' id='fn8_2'>
<p><span class='footnote-number'>2</span> <em>Canberra</em> was unique among USN ships in being named after a foreign ship, in this case, <a class='urllink' href='https://en.wikipedia.org/wiki/HMAS_Canberra_%28D33%29' rel='nofollow'>HMAS <em>Canberra</em></a>, sunk at <a class='urllink' href='https://en.wikipedia.org/wiki/Battle_of_Savo_Island' rel='nofollow'>Savo Island</a>.  LCS-30 has since used the same name. <a href='#fnr8_2'>&#8657;</a>
</p></div><div class='footnote' id='fn8_3'>
<p><span class='footnote-number'>3</span> This is a remarkably good performance given the difficult conditions.  While all suffered broken bones, none of the men died. <a href='#fnr8_3'>&#8657;</a>
</p></div><div class='footnote' id='fn8_4'>
<p><span class='footnote-number'>4</span> The things that turn salt water into fresh water. <a href='#fnr8_4'>&#8657;</a>
</p></div><div class='footnote' id='fn8_5'>
<p><span class='footnote-number'>5</span> We will come to her story soon enough. <a href='#fnr8_5'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
</channel>
</rss>
