<?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/Main/HomePage?action=rss</link>
<lastBuildDate>Thu, 19 Nov 2026 13:11:05 GMT</lastBuildDate>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/USNI-Sale-2026</guid>
<link>https://www.navalgazing.net/Main/USNI-Sale-2026</link>
<title>Main / USNI Sale 2026</title>
<dc:date>2026-11-15T13:00:00Z</dc:date>
<pubDate>Sun, 15 Nov 2026 13:00:00 GMT</pubDate>
<description><![CDATA[<p>It's the time of year when we celebrate the holidays by stocking up on naval books.  The Naval Institute Press, which probably publishes the majority of books this blog draws on, has made everything 50% off, including stuff on the clearance shelf, if you use the code HOLIDAY at checkout, so now is definitely the time to buy.  
</p>
<p>The first recommendation I have is <a class='urllink' href='https://www.usni.org/press/books/fifty-year-war' rel='nofollow'>The Fifty Year War</a>, Norman Friedman's excellent history of the Cold War.  Things at work have calmed down, so I'm going to make this the official second selection for Naval Gazing Book Club, to kick off after Christmas.  It's a little over $11 including shipping, although shipping costs per book fall if you buy more.
<a id="break"></a>
</p>
<p>And if you want more, then the obvious place to start is with new releases.  The selection this year is a bit anemic, but I'm particularly looking forward to <a class='urllink' href='https://www.usni.org/press/books/seaforth-world-naval-review-2027' rel='nofollow'>the Seaforth World Naval Review 2027</a>, <a class='urllink' href='https://www.usni.org/press/books/british-aircraft-carrier-0' rel='nofollow'>Friedman's new book on British aircraft carriers in the Cold War</a> and <a class='urllink' href='https://www.usni.org/press/books/british-light-cruisers-first-world-war' rel='nofollow'>Aidan Dodson's on WWI RN light cruisers</a>.  
</p>
<p>But there's a lot of good stuff in the back catalog.  As always, this starts with Friedman, including the <a class='urllink' href='https://www.usni.org/press/books?f%5B0%5D=subject%3A544' rel='nofollow'>Illustrated Design History</a> series, covering most of his books on US warships, <a class='urllink' href='https://www.usni.org/press/books/british-aircraft-carrier' rel='nofollow'>The British Aircraft Carrier in Two World Wars</a>, <a class='urllink' href='https://www.usni.org/press/books/cold-war-anti-submarine-warfare' rel='nofollow'>his truly excellent book on Cold War ASW</a>, <a class='urllink' href='https://www.usni.org/press/books/us-navy-attack-aircraft-1920-2020' rel='nofollow'>US Navy Attack Aircraft</a> and <a class='urllink' href='https://www.usni.org/press/books/british-cruisers-0' rel='nofollow'>British Cruisers of the 20th Century</a>, which is on the sale shelf, so you should get it while you can.  From other authors, there's D.K. Brown's <a class='urllink' href='https://www.usni.org/press/books/atlantic-escorts-0' rel='nofollow'>Atlantic Escorts</a> and <a class='urllink' href='https://www.usni.org/press/books/rebuilding-royal-navy' rel='nofollow'>Rebuilding the Royal Navy</a>, both by a retired naval architect.  
</p>
<p>Other books worth looking at include <a class='urllink' href='https://www.usni.org/press/books/aircraft-royal-navy-1908' rel='nofollow'>Aircraft of the Royal Navy since 1908</a>, which gives details on everything the RN has operated, <a class='urllink' href='https://www.usni.org/press/books/two-navies-divided' rel='nofollow'>Two Navies Divided</a>, a single-volume overview of the USN and RN in WWII, the 14-volume set of Samuel Eliot Morison's <a class='urllink' href='https://www.usni.org/press/books/history-us-naval-operations-world-war-ii' rel='nofollow'>History of US Naval Operations in World War II</a>, or if that's too much and you want to go through the book club from earlier in the year, <a class='urllink' href='https://www.usni.org/press/books/two-ocean-war' rel='nofollow'>Morison's Two-Ocean War</a>.  For those whose interests are more recent, there's <a class='urllink' href='https://www.usni.org/press/books/china-twenty-first-century-naval-power' rel='nofollow'>China as a 21st Century Naval Power</a>, a deep look at the PLAN's development, and past volumes of Seaforth World Naval Review, as there's substantial new content each year.  I will also mostly endorse <a class='urllink' href='https://www.usni.org/press/books?search=&amp;f%5B0%5D=subject%3A1966' rel='nofollow'>Drachinifel's reading list</a>, although there are a few books on there I don't have or didn't particularly like.
</p>
<p>It's also worth checking out the <a class='urllink' href='https://www.usni.org/press/books?search=&amp;f%5B0%5D=subject%3A51' rel='nofollow'>"Clear the Decks" sale section</a>, which has a ton of great stuff, much for $10-20.  Standouts include <a class='urllink' href='https://www.usni.org/press/books/battleship-builders-0' rel='nofollow'>The Battleship Builders</a>, <a class='urllink' href='https://www.usni.org/press/books/british-battleships-1919-1945-0' rel='nofollow'>British Battleships 1919-1945</a>, <a class='urllink' href='https://www.usni.org/press/books/spoils-war' rel='nofollow'>Spoils of War</a>, about what happened to captured ships postwar, <a class='urllink' href='https://www.usni.org/press/books/battlecruiser' rel='nofollow'>Before the Battlecruiser</a>, <a class='urllink' href='https://www.usni.org/press/books/world-battleship' rel='nofollow'>The World of the Battleship</a>, <a class='urllink' href='https://www.usni.org/press/books/jutland-1' rel='nofollow'>Before Jutland</a> and <a class='urllink' href='https://www.usni.org/press/books/british-pacific-fleet' rel='nofollow'>David Hobb's book on the British Pacific Fleet</a>.
</p>
<p>There's also a lot of goodness in the regular back catalog, but I don't have time to go through and sort it out.  Suffice it to say that if you want to build up a naval library, this is the time to do it.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Oriskanys-Aluminum-Deck</guid>
<link>https://www.navalgazing.net/Main/Oriskanys-Aluminum-Deck</link>
<title>Main / ''Oriskany'''s Aluminum Deck</title>
<dc:date>2026-11-08T13:00:00Z</dc:date>
<pubDate>Sun, 08 Nov 2026 13:00:00 GMT</pubDate>
<description><![CDATA[<p>In the comments recently, someone made reference to <em>Oriskany</em> receiving an aluminum deck as part of her SCB-125A refit.  And something smelled off about that claim.  It was the sort of thing I really should have remembered if it was true, because it's such a delightfully weird bit of trivia.  So I started digging.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/USS_Oriskany_underway_at_sea_on_6_December_1950.jpg?v=1793635528.jpg' alt='' /><br /><span class='caption'><em>Oriskany</em> in her original configuration </span></span></div>
<p>Now, before I go further, I should probably explain what I'm talking about.  <a class='urllink' href='https://en.wikipedia.org/wiki/USS_Oriskany' rel='nofollow'><em>Oriskany</em></a> was one of the <a class='urllink' href='https://en.wikipedia.org/wiki/Essex-class_aircraft_carrier' rel='nofollow'><em>Essex</em> class carriers</a>, famous as the backbone of the carrier task forces in WWII.  But she had a rather unique history.  She was still incomplete at the end of the war, and it was becoming obvious that significant modifications were going to be required to allow the existing carriers to operate the new jets entering service.  So in 1947, she became the prototype for what was known as <a class='urllink' href='https://en.wikipedia.org/wiki/SCB-27' rel='nofollow'>SCB-27A</a>, refitting the <em>Essex</em>s with more powerful catapults, improved arresting gear, stronger elevators and flight deck, and an island rebuilt to be smaller and have better spots for radar.  All of this added significant weight, requiring the ships be blistered to compensate despite the removal of the armored belt.  But it was also necessary to keep the numerous <em>Essex</em>s viable in a world where <a class='wikilink' href='https://www.navalgazing.net/Main/Revolt-of-the-Admirals-Part-1'>funds for newer ships were difficult to find</a>.  
</p>
<p>But the development of faster and heavier jets quickly outstripped the capabilities of SCB-27A, and something more was needed.  Starting in 1951, ships were modernized to the SCB-27C standard instead, which included steam catapults in place of the previous hydraulic units, further strengthening of the flight deck and arresting gear, fitting bigger blisters and moving the aft centerline elevator to the starboard side to improve aircraft flow.  Six unmodified ships received this upgrade, the last three in combination with a later upgrade known as <a class='urllink' href='https://en.wikipedia.org/wiki/SCB-125' rel='nofollow'>SCB-125</a>, which enclosed the bow to better deal with <a class='wikilink' href='https://www.navalgazing.net/Main/Weather-at-Sea'>heavy weather</a> and fitted the newly-developed <a class='wikilink' href='https://www.navalgazing.net/Main/A-Brief-History-of-the-Aircraft-Carrier'>angled deck and mirror landing system</a>.  With the exception of <em>Lake Champlain</em>, all of the other modernized ships also received SCB-125, with the aft elevator on the SCB-27A ships being moved as part of the upgrade.  Uniquely, <em>Oriskany</em> received what was known as SCB-125A, an upgrade that also included steam catapults and the various other changes included under SCB-27C.  She was the last of the <em>Essex</em>s to be modernized, and these changes allowed her, along with the SCB-27Cs, to serve as attack carriers through the early 70s, while the SCB-27A ships were relegated to anti-submarine duties, where their less powerful catapults were adequate.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/USS_Oriskany_at_sea_in_1959.jpg?v=1793635531.jpg' alt='' /><br /><span class='caption'><em>Oriskany</em> shortly after the SCB-125A upgrade </span></span></div>
<p>But that brings us back to the aluminum flight deck claims, and I wasn't sure what to make of them.  My first stop, of course, was Friedman's US Carriers, which was completely silent on this.  The only notable fact he had was that unlike the other SCB-27C ships, <em>Oriskany</em> was down to two <a class='wikilink' href='https://www.navalgazing.net/Main/Secondary-Armament-Part-3'>5"/38 guns</a> by the time she retired, instead of four for the others.  This was enough to make me skeptical, as the obvious reason for installation of an aluminum flight deck would be to reduce <a class='wikilink' href='https://www.navalgazing.net/Main/Stability'>topweight</a>, and the removal of guns strongly suggests <em>Oriskany</em> had more trouble there than did the others.  A search online didn't turn up anything in independent sources like DANFS, and while it was on several different pages on Wikipedia, it was either unsourced, had a reference to a Proceedings article that didn't mention anything about aluminum or was a bare reference to Friedman, which is what warship Wiki does when it's making things up.<a class='footnote' id='fnr1_1' href='#fn1_1'><sup>1</sup></a>  More than that, the various pages weren't particularly clear on exactly what had been done, with most at least implying that the deck had been replaced by aluminum and some stating it outright.  Fortunately for me, <em>Oriskany</em> was sunk as a reef, which meant that there was environmental paperwork available, and the <a class='urllink' href='https://www.researchgate.net/publication/235115403_Ex-ORISKANY_Artificial_Reef_Project_Ecological_Risk_Assessment' rel='nofollow'>risk assessment</a> confirmed (p.39) that there was wooden flight decking aboard until it was removed to limit the amount of PCBs released by the sunken ship.<a class='footnote' id='fnr1_2' href='#fn1_2'><sup>2</sup></a>  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/OriskanySinkingPic.jpg?v=1793635529.jpg' alt='' /><br /><span class='caption'><em>Oriskany</em> being scuttled as a reef<a class='footnote' id='fnr1_3' href='#fn1_3'><sup>3</sup></a></span></span></div>
<p>The only possibility left seemed to be that they'd rebuilt the understructure of the flight deck with aluminum in place of steel during the refit, presumably to save topweight.<a class='footnote' id='fnr1_4' href='#fn1_4'><sup>4</sup></a>  But that would be an enormous undertaking, the sort of thing that would definitely be discussed at length in Friedman, and probably mentioned in places like DANFS, too.  There would be serious concerns about <a class='wikilink' href='https://www.navalgazing.net/Main/Corrosion-at-Sea'>bimetallic corrosion</a>, aluminum's different structural properties, and the fact that it <a class='wikilink' href='https://www.navalgazing.net/Main/Survivability-Fire'>softens much more quickly in a fire</a>.  So, with all of that taken into account, I was reasonably certain that Wiki had gotten it wrong.  I was able to trace the original mention in the <em>Oriskany</em> article back to <a class='urllink' href='https://en.wikipedia.org/w/index.php?title=USS_Oriskany&amp;diff=prev&amp;oldid=40894157' rel='nofollow'>an edit made in 2006</a>, when citation standards weren't what they are today.  But just to be sure, I ordered a couple of books on the <em>Essex</em> class, by Alan Raven and Andrew Faltum.  I didn't see anything in either book about this, and thus started work on this post to expose the error.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Oriskany1957Refit.jpg?v=1793636332.jpg' alt='' /><br /><span class='caption'><em>Oriskany</em> getting her SCB-125A refit</span></span></div>
<p>And it was while I was preparing the summary of the <em>Essex</em> modernization at the top of this post that I realized I'd overlooked something.  In Faltum's summary of the SCB-125A modification on p.159, when listing differences from SCB-27C ships, he states "CV-34 had a light metal cladding for the flight deck."  Now, this would explain both the aluminum and the continued presence of wood on the flight deck, and is what at least some of the Wiki articles mention.  "Light metal" is somewhat ambiguous, and while it could mean thin steel, it's also frequently used to refer to a group of metals significantly lighter than steel, typically aluminum or magnesium.  Magnesium can be ruled out for <a class='urllink' href='https://www.youtube.com/watch?v=JTNF1K7joZo' rel='nofollow'>obvious reasons</a>, but I still wanted more evidence that we were talking about aluminum, and I found it in the Raven book.  On p.182-183, there's a diagram of the deck coverings on an SCB-27C, which shows that much of the deck is wood underneath various thicknesses of polyurethane overlay.  A few areas, mostly the catapult section, landing area and elevator tops are steel,<a class='footnote' id='fnr1_5' href='#fn1_5'><sup>5</sup></a> while there's one small section that has aluminum over the wooden deck, and no sections where steel is used this way.  Checking more of Friedman turned up a discussion on p.351 of a proposed refit of the SCB-27A ships to keep them active after plans for new anti-submarine carriers fell through, with a mention of a plan to replace the wooden deck with "aluminum-clad hickory" to reduce the maintenance burden.  That dates from the mid-60s, but it would make sense that <em>Oriskany</em>, the last of the ships to get modernized, might well have gotten something similar.
</p>
<p>And I was all ready to leave it there, having solved the mystery, before I decided to see if I could find some confirmation of this theory by looking at reports of the fire aboard <em>Oriskany</em> in October 1966.  Unfortunately, there wasn't much technical on the fire.  But while looking into it, I found a <a class='urllink' href='https://books.google.com/books?id=DFMEAAAAMBAJ&amp;q=A%20Carrier%27s%20Agony%20-%20Hell%20Afloat&amp;pg=PA104#v=onepage&amp;q=A%20Carrier%27s%20Agony%20-%20Hell%20Afloat&amp;f=false' rel='nofollow'>long article in Life magazine</a>.  As Life was a general-interest publication, the article focuses on the story of the men involved, and lacks basically any technical detail.  But it does start with a few very nice full-color photos of men working on deck, which very clearly show wooden planks.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/OriskanyFireWoodenPlanks.jpg?v=1793636236.jpg' alt='' /><br /><span class='caption'>Men fight the fire aboard <em>Oriskany</em>.  The deck is very clearly wood planks.</span></span></div>
<p>In despair, I <a class='urllink' href='http://www.navsource.net/archives/02/34.htm' rel='nofollow'>went to NavSource</a> to see what sort of photos they had of the flight deck, and found what appeared to be the solution to my problem.  <a class='urllink' href='https://www.navsource.net/archives/02/023456.jpg' rel='nofollow'>A picture of a 1957 BuShips journal article</a> says "aluminum decking will be added to the landing area," which would square the various circles nicely.  Except that I then started going through other photos on NavSource, and a lot of the landing ones clearly showed wood in the area where planes were touching down.  Eventually, I was able to find a few that did show some sort of metal in the landing area, such as the one below of a Skyhawk going into the barrier in November 1967.  Presumably this is the aluminum mentioned by BuShips, but coverage is nowhere near what the diagram in Raven led me to expect.  It's the kind of minor change that happens all the time as ships go through yards, and not worth mentioning unless you're working at the sort of detail that tracks, say, every change of radio equipment.  The planes are still clearly touching down on wood, while Raven has pretty much the whole landing area as <a class='wikilink' href='https://www.navalgazing.net/Main/Armor-Part-4#fn1_2'>STS</a>, which makes a great deal of sense in an area where tens of thousands of pounds of planes are slamming into it.  But that's obviously not what's going on here.  The wood stays visible on parts of the deck as late as <a class='urllink' href='https://www.navsource.net/archives/02/0234ay.jpg' rel='nofollow'>1976</a>, during the ship's final deployment.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/SkyhawkBarrier1967Oriskany.jpg?v=1793460022.jpg' alt='' /></span></div>
<p>At this point, I started asking questions about Raven.  My initial assumption was that his diagram described a configuration used on one of the other SCB-27C ships, most likely <em>Lexington</em>, which stayed in service until 1991 as a training carrier.  But this doesn't work either.  The diagram shows the deck-edge elevators as being nonskid paint on steel, but there's <a class='urllink' href='https://www.navsource.net/archives/02/021674a.jpg' rel='nofollow'>a 1975 photo of a T-2 Buckeye clearly showing wood on Lady Lex's elevators</a>.  And Raven credits almost everything forward of the angle as being STS, but <a class='urllink' href='https://www.navsource.net/archives/02/0216ak.jpg' rel='nofollow'>this 1985 photo</a> shows wood running between the catapults all the way to the bow.  It's possible that one of the other ships was configured this way, but I don't feel like doing detailed checks of the photos of every SCB-27C, particularly given how hard it is to see the wood in some photographs.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Douglas_EA-1F_Skyraider_of_VAW-13_aboard_USS_Oriskany_in_1966.jpg?v=1793636936.jpg' alt='' /><br /><span class='caption'>The entirety of the fabled "aluminum deck," clearly surrounded by wood.  Click to enlarge.</span></span></div>
<p>Having gone through all of that, I can come to a simple conclusion.  My initial suspicions were correct, and <em>Oriskany</em> never received anything that could be described as an aluminum flight deck.  There was at most a small amount of the metal in the rollout area forward of the arresting gear, but nothing worth talking about unless we're getting way deeper into the weeds than any source I have does.  I suspect Faltum may have run across the BuShips article and described it poorly, and the other sourcing flows from there.  But the photos are clear that her flight deck remained primarily wood to the end of her life.  I'm not sure why the Navy never got around to replacing it, but the evidence on the matter is clear.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn1_1'>
<p><span class='footnote-number'>1</span> Well, usually.  Sometimes, there's a specific page number that doesn't actually check out.  One example is in <a class='urllink' href='https://en.wikipedia.org/wiki/index.php?title=USS_John_F._Kennedy_&lpar;CV-67&rpar;&amp;oldid=1381438087#Design_and_early_years' rel='nofollow'>the page for <em>Kennedy</em> at time of writing</a>, where it claims that the ship was originally ordered as a nuclear carrier, and only converted to conventional power after construction began, citing p.387 of Friedman.  It also cites this same page for the claim that she was developed under SCB-127C, and that she was 12' shorter than the <em>Kitty Hawk</em> class.  The page contains none of these claims.  It's in the appendix about magazines, and while it mentions SCB-127C, it has no mention of <em>Kennedy</em> herself, and certainly nothing about either the ship's length or her being ordered as a nuclear carrier.  On p.399, Friedman gives a specification block for the ship, with overall length being 1051' 3", with a footnote saying she was 1072' 1" over the catapult booms, while <em>America</em>, the previous ship, is listed as 1069' 9" overall, and <em>Constellation</em>,  the closest he lists to <em>Kitty Hawk</em>, is 1047' 6".  I'm not quite sure what to make of these numbers, particular as Andrew Faltum's book on the ships gives LOAs of 1062'8" for <em>Kitty Hawk</em>, 1072'6" for <em>Constellation</em> and 1047'7" for both <em>America</em> and <em>Kennedy</em>.  <br clear='all' /><br clear='all' /> Also on p.399 of Friedman, there are specifications for SCB-203, which is listed as having 4 A3W reactors, the same configuration Wiki gives for <em>Kennedy</em>'s original design.  More than that, the claim that she was ordered as a CVN and then changed at the last minute (I've heard versions that it was because the Kennedy family didn't want his name on a CVN for some reason) is obviously false given how ships are actually designed and built.  The reactors are pretty much the first components ordered, and nuclear power is built into the basic fabric of the design.  A CVN doesn't need boiler uptakes or nearly as much fuel storage as a dinosaur-burner, but it also has to house reactors that are not very power-dense compared to diesel boilers.  On p.283, Friedman confirms that CVA-67 was ordered as a conventional carrier by SecDef McNamara on 9 October 1963, despite the Navy's desire for a CVN, which also rules out political pressure by the Kennedy family (as if that wasn't obvious nonsense anyway).  He does credit it as SCB-127C on p.285. <br clear='all' /><br clear='all' /> I first noticed this back in 2012, and sat on it because Wiki editing was kind of a mess even back then and I wanted to see how long it persisted.  But that was 14 years ago, and I think the experiment has run its course.  Odds are it's been corrected by the time you read this. <a href='#fnr1_1'>&#8657;</a>
</p></div><div class='footnote' id='fn1_2'>
<p><span class='footnote-number'>2</span> I'm genuinely confused why the refitted ships continued to have wooden flight decks.  <a class='wikilink' href='https://www.navalgazing.net/Main/Wolverine-and-Sable'><em>Sable</em></a> pioneered metal flight decks for the USN in the early 40s, and <em>Midway</em> commissioned with one in 1945.  Unfortunately, this doesn't appear to be answered by any of my sources, and <em>Lexington</em> and <em>Intrepid</em> never got back to me when I asked them. <a href='#fnr1_2'>&#8657;</a>
</p></div><div class='footnote' id='fn1_3'>
<p><span class='footnote-number'>3</span> It appears that they didn't actually remove all of the flight decking, given the markings aft, which for a moment I thought would force me to reopen this.  Fortunately, an inspection of a high-res version revealed that the aft section was wood, as best I can tell.  Maybe there were no PCBs there. <a href='#fnr1_3'>&#8657;</a>
</p></div><div class='footnote' id='fn1_4'>
<p><span class='footnote-number'>4</span> Given that <em>Oriskany</em> is a reef, I briefly considered <a class='wikilink' href='https://www.navalgazing.net/Main/SCUBA-Part-1'>sending John Schilling down</a> with a magnet to check, but it turns out that her flight deck is <a class='wikilink' href='https://www.navalgazing.net/Main/SCUBA-Part-2'>too deep for most recreational divers</a>. <a href='#fnr1_4'>&#8657;</a>
</p></div><div class='footnote' id='fn1_5'>
<p><span class='footnote-number'>5</span> Interestingly, I discovered that the USN made early elevator tops out of aluminum, to save weight and reduce cycle time.  This was discontinued, I think with the <em>Midway</em>s, due to concerns about protection. <a href='#fnr1_5'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Museum-Review-Turner-Joy</guid>
<link>https://www.navalgazing.net/Main/Museum-Review-Turner-Joy</link>
<title>Main / Museum Review - ''Turner Joy''</title>
<dc:date>2026-11-01T13:00:00Z</dc:date>
<pubDate>Sun, 01 Nov 2026 13:00:00 GMT</pubDate>
<description><![CDATA[<p>This is a first, but hopefully not a last.  While on my quest to see the Coast Artillery Museum before it closed, I took a few hours to stop in Bremerton and see the destroyer <em>Turner Joy</em>, as well as the Puget Sound Navy Museum a couple blocks away.  But while I've reviewed a lot of museums, and even in some cases reviewed a ship twice, what makes this unique is that reader <a class='urllink' href='https://papyrusrampant.substack.com/' rel='nofollow'>Evan Þ</a> <a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-USS-Turner-Joy'>reviewed it four years ago</a>, giving me an opportunity to compare my take on the ship to his.
</p>
<div  style='text-align: center;' class='img'> <span class='px'> <img width='600' src='/attach/TurnerJoy26External.jpg?v=1793399417.jpg' alt='' />  </span></div>
<div class='property-Type'>Type: Cold War Destroyer</div>
<div class='property-Location'>Location: Bremerton, WA</div>
<div class='property-Rating'>Rating: A good way to spend a couple hours, extremely open and well-signed</div>
<div class='property-Price'>Price: $23 for normal adults</div>
<p><a class='urllink' href='https://ussturnerjoy.org/' rel='nofollow'>Website</a>
</p>
<p>First, some logistical bits to get out of the way: if you're coming from Seattle, <em>Turner Joy</em> is a short walk from the terminus of the Bremerton-Seattle ferry.  If you're not, you need to find parking in downtown Bremerton, because neither museum has its own parking lot.  I would recommend the former, if possible, because the later is annoying and/or expensive.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/TurnerJoy26DCMuseum.jpg?v=1793399419.jpg' alt='' /><br /><span class='caption'>The Damage Control section aboard, a nice display of DC gear</span></span></div>
<p>As for <em>Turner Joy</em> herself, I walked in expecting her to be nice but sort of underwhelming.  I've toured a couple destroyers, and never been all that impressed, because on a ship that's under 5,000 tons, there just isn't enough ship to get a really satisfying experience.  Or so I thought.  <em>Turner Joy</em> managed to handily beat expectations, solving this problem by doing another thing I didn't think would turn out well: making sure everything is open.  This appears to be the goal of a lot of museum ships (<a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-Battleship-Cove-Massachusetts'><em>Massachusetts</em></a>, <a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-Midway-Redux'><em>Midway</em></a> and <a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-Alabama-Redux'><em>Alabama</em></a> all spring to mind) and I generally think it's a mistake.  If the ship is that big, it's easy for visitors to get lost or overwhelmed, and even I'm getting old enough that I start to feel it after 4-5 hours onboard.  My take on this may be influenced by the fact that I got my start on <em>Iowa</em>, the only major museum ship which has consciously taken the other tack, deliberately building a 2-hour tour route for the average visitor, even if it means skipping a bunch of cool stuff.  But it turns out that when you really open up a small ship and add excellent signage, the result is kind of magical.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/TurnerJoy26SignageBelow.jpg?v=1793399419.jpg' alt='' /><br /><span class='caption'>One of many examples of excellent signage</span></span></div>
<p>Because <em>Turner Joy</em> is open in ways that I've never seen approached.  One of the crew claimed 90%, and while I'm not sure exactly how that would be measured, it feels about right.  Even writing this review hours later, I can't think of a single space I would seriously have wanted to see that I couldn't.  Maybe the view of the officer's pantry wasn't great, and you couldn't get into the chain locker itself, but those are really minor niggles.  And, even better and more importantly, they've done a really inspired job using the ship they have, particularly with I think the best signage I've ever seen on a ship.<a class='footnote' id='fnr2_1' href='#fn2_1'><sup>1</sup></a>  Two things they did that I particularly liked were studding the berthing spaces with "Who slept here?" signs that let them talk about all of the various ratings the Navy has and putting signs outside many closed hatches with pictures of what is on the other side.  I'm sort of kicking myself for not thinking of either of those, and other ships should copy both ideas, pronto.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/TurnerJoy26Sonar.jpg?v=1793399418.jpg' alt='' /><br /><span class='caption'>The sonar room</span></span></div>
<p>Hand-in-hand with the signage is the fact that they cover all aspects of the ship's operation.  Everything from the guns and torpedoes to the mail room, offices, and sonar suite.  The only thing I don't remember having particularly good signage was the galley, and I was moving pretty fast and might have just overlooked it.  And, as someone with an eye on "what would it be like to take people through this ship?" the signage would have made it a lot easier to do that, because while I may know things, getting everything out of your brain and into your mouth at the right time is hard unless you've had time to build up a tour, which you can't do on a ship you only visit every few years.  There were lots of signs that I could easily have glanced at, then talked about for a couple minutes with the reminder.  I was only aboard for maybe 75 minutes, but could easily have gone twice that if I'd been reading a lot of the signs or taking someone curious through.  And there were some cool touches, like a shell suspended in netting, allowing visitors to get a sense of how heavy it was without the possibility of dropping it.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/TurnerJoy26PugetSoundMuseum.jpg?v=1793399799.jpg' alt='' /><br /><span class='caption'>A display at the Puget Sound Navy Museum</span></span></div>
<p><em>Turner Joy</em> is just outside Puget Sound Naval Shipyard, which has its own museum, less than a 10-minute walk away.  And, unfortunately, it's nowhere near as good.  It's in a building that dates back to 1896, and started life as the administrative headquarters of the new Navy Yard.  The ground floor is a small museum on the history of the shipyard, and there are some neat artifacts, but I was hoping for some serious detail on the technical side of the shipyard, and in that, I was disappointed.  Upstairs, they have a section on life aboard a carrier, which is pretty clearly designed to give sailors whose families are visiting a chance to explain what their life is like without having to actually bring them aboard the ship.  It wasn't bad, but it was very basic.  There's also a a couple galleries with rotating collections.  When I was there, one of them was on fashion in the Navy, and there were some interesting bits on the way sailors had modified their uniforms, but it didn't really go into the evolution of naval uniforms, instead spending a lot of time on the ways in which naval clothing has entered civilian fashion.  Cynically, that's because the pictures of that are a lot easier to find.  
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/TurnerJoy26ParcheSail.jpg?v=1793399798.jpg' alt='' /></span></div>
<p>On the whole, I don't regret visiting the museum (particularly because, like most Navy museums, it's free) but I wouldn't hurry through <em>Turner Joy</em> to go see it, and I would think twice before extending my parking session for it.  The only really cool thing they have is outside, where they've gotten the sail of <em>Parche</em>, the most decorated ship in the history of the US Navy, for her long career of <a class='wikilink' href='https://www.navalgazing.net/Main/Submarine-Espionage'>sneaking around and tapping other people's</a> <a class='wikilink' href='https://www.navalgazing.net/Main/Submarine-Cables-Part-1'>cables</a>.  That was pretty cool.  It's also not the only ship part around there.  Just north of <em>Parche</em>'s sail, there's a park thing with a bit of history of the shipyard and the very tip of the bow of the nuclear cruiser <em>South Carolina</em>.  There's a decent chance you'll go past it on the way back to your car.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn2_1'>
<p><span class='footnote-number'>1</span> I should note that I am being pedantic here and counting <a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-USS-Nautilus-and-Submarine-Force-Museum'><em>Nautilus</em></a> as a boat.  I'm not sure she's better, but she's the only thing I can think of that's plausibly in the same league. <a href='#fnr2_1'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Navy-Day-2026</guid>
<link>https://www.navalgazing.net/Main/Navy-Day-2026</link>
<title>Main / Navy Day 2026</title>
<dc:date>2026-10-27T12:00:00Z</dc:date>
<pubDate>Tue, 27 Oct 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>Nine years.  That's how long it's been since I started this blog, and I'm amazed that it's still going strong.  It's been far longer since this stopped being the official day for the celebration of the USN, but we'll ignore that.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='600' src='/attach/navy_day_poster_2026.jpg?v=1792879687.jpg' alt='' /><br /><span class='caption'>Thanks to quanticle for this year's poster</span></span></div>
<p>The highlight of the year was obviously the Dayton meetup.  Thanks to everyone who came to that, and in particular to John and Laz for doing parts of the tour, Rebecca, the Friedmans and my mom for cooking, and everyone who contributed gear to make that possible.  I plan to do next year's in LA, although the details are still up in the air.  Cassander did the heresy tour and contributed a couple of posts, Albert and Ryan contributed museum reviews and Obormot kept things running on the technical side.  I also appreciate everyone who makes the <a class='urllink' href='https://discord.gg/NZwv8NYbM8' rel='nofollow'>Discord</a> a fun place to hang out, and those who participated in the book club earlier in the year.  I do intend to restart that once things elsewhere in my life calm down some.  And of course, there's Lord Nelson, ho has to put up with me bursting in at random times talking about some mostly-forgotten battle.  But most of all, it's the people who read and comment who make this worth doing.  On to year 10.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Submarine-Aviation-Part-1</guid>
<link>https://www.navalgazing.net/Main/Submarine-Aviation-Part-1</link>
<title>Main / Submarine Aviation Part 1</title>
<dc:date>2026-10-25T12:00:00Z</dc:date>
<pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>Aircraft and submarines seem like strange bedfellows.  Beyond each operating entirely immersed in a single fluid, they don't have much in common.  But that hasn't stopped attempts to make them work together, usually with extremely limited results.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/German_submarine_U-12.jpg?v=1792515958.jpg' alt='' /><br /><span class='caption'>U-12 with an FF.29 aboard  </span></span></div>
<p>The first collaboration between submarines and aircraft took place barely a decade after both entered widespread service.  In the opening days of the First World War, after securing most of the <a class='wikilink' href='https://www.navalgazing.net/Main/Coastal-Defenses-Part-7'>Belgian coast</a>, the Germans established a base at Zebrugge, where submarines could attack shipping in the North Sea.  One of these scored an early victory, <a class='wikilink' href='https://www.navalgazing.net/Main/The-Germans-Strike-Back'>sinking three British armored cruisers</a>, and they generally made the southern reaches of the North Sea untenable for the British.  Soon, a small group of <a class='urllink' href='https://en.wikipedia.org/wiki/Friedrichshafen_FF.29' rel='nofollow'>Friedrichshafen FF.29</a> floatplanes were added, almost as an afterthought, and their operators had to figure out what to do with them.  In addition to the obvious (patrolling the North Sea), they fitted their planes to carry tiny bombs and began launching raids on the southeastern bits of England.  The problem that these first aerial raiders over Britain faced was that their planes were still incredibly primitive, and it was often a struggle to make the 150 nm round trip to even the nearest portions of the UK before the fuel lines plugged or the igniters fouled.  
</p>
<p>The submariners and aviators, both operating new and untried weapons, decided to collaborate,  On January 6th, 1915, <a class='urllink' href='https://en.wikipedia.org/wiki/SM_U-12_&lpar;Germany&rpar;' rel='nofollow'><em>U-12</em></a> went to sea carrying one of the FF.29s across its bow.  The plan was simple.  They would carry the aircraft out into the North Sea, then ballast down the bow and the seaplane would take off normally.  Almost from the moment they left the breakwater at Zebrugge it was obvious that the swell, which had felt almost inconsequential to the U-boats, was a serious problem for its awkward, fragile burden.  Despite this, the plane survived its ride to the launching point about 20 miles west of Zebrugge, and the pilot was able to get airborne, although he promptly decided that the second half of the plan, where he would land near <em>U-12</em> and be carried back home, was too dangerous.  After a brief flight over the coast of Kent, which nobody down below seems to have noticed, he returned to Zebrugge directly, followed a few hours later by the U-boat.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Friedrichshafen_FF.29_closeup.jpg?v=1792515964.jpg' alt='' /><br /><span class='caption'>An FF.29</span></span></div>
<p>The response from higher-ups was about what might be expected given the degree of success.  The order swiftly came down that "U-boats operate in the water, air­planes in the air; there is no connection be­tween the two".  And this was undoubtedly the right call given what had been attempted.  The advantage of using a U-boat over a conventional boat was mostly its ability to float the plane on and off with the ballast tanks.  Diving with the plane aboard would be effectively impossible, and the low U-boat suffered badly in any kind of sea.  The British learned this lesson the next year when they tried unsuccessfully to use <em>E-22</em> as the base for a pair of floatplanes intended to intercept <a class='wikilink' href='https://www.navalgazing.net/Main/Naval-Airships-Part-2'>raiding Zeppelins</a> over the North Sea.  But the idea of providing a submarine with a plane that could be taken under the surface would come up repeatedly over the next few decades.  
</p>
<p>But the basic logic was almost always very different from the wartime efforts.  Despite <a class='wikilink' href='https://www.navalgazing.net/Main/Billy-Mitchell-and-the-Ostfriesland-Part-1'>certain claims</a>, aircraft of the 1920s were pretty limited at delivering weapons, but still extremely useful at scouting, and most submarine aviation proposals involved using aircraft to extend a submarine's horizons.  Despite the role that submarines played in both world wars, this was rarely driven by the desire to find merchant ships to sink.  Instead, most of the work in the 20s, when interest in submarine aviation was at its height, appears to have been driven by the desire to use a submarine as a scout for the fleet.  A big submarine had the range to operate far from the fleet and the ability to hide if the enemy came looking, but couldn't expect to see ships more than maybe 15 miles even in clear weather.<a class='footnote' id='fnr3_1' href='#fn3_1'><sup>1</sup></a>  Giving it an airplane could extend this to a hundred miles or more.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/S-1SS-105_MS-1.jpg?v=1792515962.jpg' alt='' /><br /><span class='caption'>An MS-1 aboard <em>S-1</em></span></span></div>
<p>A number of nations made reasonably serious investigations of this concept.  Even before the end of the war, the Germans had developed two planes designed to fit aboard long-range submarines, the <a class='urllink' href='https://en.wikipedia.org/wiki/Hansa-Brandenburg_W.20' rel='nofollow'>W.20</a> and <a class='urllink' href='https://en.wikipedia.org/wiki/LFG_Stralsund_V_19_Putbus' rel='nofollow'>V 19</a>, but it was the USN that was the first to attempt something like an operational test, buying a dozen submarine-based scoutplanes of two <a class='urllink' href='https://en.wikipedia.org/wiki/Cox-Klemin_XS' rel='nofollow'>different</a> <a class='urllink' href='https://en.wikipedia.org/wiki/Martin_MS-1' rel='nofollow'>types</a>, and trialing them aboard the submarine <a class='urllink' href='https://en.wikipedia.org/wiki/USS_S-1' rel='nofollow'><em>S-1</em></a> in 1923.  But performance wasn't great, planes were still launched by ballasting down, which restricted operations to the calmest seas, and assembling and disassembling an airplane on the deck of a submarine was tricky and time-consuming.  As a result, the US abandoned the project in the mid-20s.  <a class='urllink' href='https://en.wikipedia.org/wiki/Italian_submarine_Ettore_Fieramosca' rel='nofollow'>Italy</a>, <a class='urllink' href='https://en.wikipedia.org/wiki/Nikol_A-2' rel='nofollow'>Poland</a> and <a class='urllink' href='https://en.wikipedia.org/wiki/Chyetverikov_SPL' rel='nofollow'>the Soviet Union</a> all investigated the idea in the 20s and 30s, but abandoned it before actually sending a plane to sea aboard a submarine.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/British_Submarine_HMS_M2_Hoisting.jpg?v=1792515961.jpg' alt='' /><br /><span class='caption'><em>M2</em> hoists its floatplane aboard</span></span></div>
<p>Instead, it would be the British who were the first to make a serious attempt at implementing the idea, removing the 12" gun from the monitor submarine <a class='urllink' href='https://en.wikipedia.org/wiki/HMS_M2' rel='nofollow'><em>M2</em></a><a class='footnote' id='fnr3_2' href='#fn3_2'><sup>2</sup></a> and replacing it with a hangar for a small floatplane.  A catapult<a class='footnote' id='fnr3_3' href='#fn3_3'><sup>3</sup></a> was installed forward, allowing the plane to be launched in rougher seas, with the plane landing in the water alongside for a crane to bring back aboard.  Unfortunately, the catapult was short and the plane, the <a class='urllink' href='https://en.wikipedia.org/wiki/Parnall_Peto' rel='nofollow'>Parnall Peto</a>, was flimsy, so some natural wind was required to launch.  
</p>
<p>The launch process was simple enough.  As the submarine surfaced, the five-man hangar crew would be at their stations, and oil heaters would ensure that the plane was ready for immediate launch, instead of needing to wait for the engine to warm up.  Once surfaced, even if the ballast tanks weren't completely empty yet, the hangar door would be lowered, and the plane's trolley wheeled across the tracks built into it and connected to the catapult while the wings were unfolded and locked into place.  The observer had a crank to rotate the engine, and once it was running smoothly, the Peto would be catapulted off.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Parnall_Peto_1926.jpg?v=1792516274.jpg' alt='' /><br /><span class='caption'>A Parnall Peto</span></span></div>
<p>The conversion was completed in late 1928, and for the next two years, trials went reasonably well.  But on January 26th, 1932, <em>M2</em> foundered with all hands.  Salvage efforts revealed that the hangar was open, and a leading theory was that the practice of opening the hangar door before the ballast tanks were fully empty, with the submarine held on the surface by the diving planes, may have backfired.  However, this was a known risk, and orders were to close the door from the hangar into the rest of the submarine to prevent it.  That door was open, and a passing merchant ship saw <em>M2</em> sink by the stern, which suggests that the hangar was not the main problem.  Instead, the more likely case is that the aft ballast tank valves were left open, allowing that tank to refill after the submarine surfaced.  Ironically, the hatch from the hangar into the submarine was probably opened to pass the order to close the valves, but it was already too late, and the flooding through it doomed the submarine.  Several salvage attempts were made, recovering the wreck of the Peto and several bodies, but the hull itself was eventually abandoned, and remains a reasonably popular dive site today.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/British_Submarine_HMS_M2_Catapult.jpg?v=1792515959.jpg' alt='' /><br /><span class='caption'><em>M2</em> catapults off a Peto</span></span></div>
<p>And for most nations, interest in submarine aviation dried up in the 30s.  One of the big drivers was the 1930 <a class='wikilink' href='https://www.navalgazing.net/Main/Interwar-Naval-Diplomacy'>London Naval Treaty</a>, which limited submarines to 2,000 tons, a bit too small to effectively operate airplanes.  We'll look at other drivers of the decline of the concept, and at the two nations which soldiered on, France and Japan, next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn3_1'>
<p><span class='footnote-number'>1</span> This is not 100% true.  The smoke from coal-burning ships could frequently be seen much farther away, but by the 20s, it was obvious that coal was on its way out. <a href='#fnr3_1'>&#8657;</a>
</p></div><div class='footnote' id='fn3_2'>
<p><span class='footnote-number'>2</span> The <a class='urllink' href='https://en.wikipedia.org/wiki/British_M-class_submarine' rel='nofollow'><em>M</em> class</a> were very weird boats.  The original proposal was for shore bombardment, but this was swiftly shelved on the grounds that it was crazy.  Instead, the idea was that the gun would be far better at hitting moving targets such as warships, which were effectively impossible to torpedo beyond 1,000 yards or so at the time.  The submarine would aim with a special periscope, surface enough to expose the muzzle of the gun, then dive again, hopefully before any escorts could intervene.  The 12" shell, fired from <a class='urllink' href='https://www.navweaps.com/Weapons/WNBR_12-40_mk9.php' rel='nofollow'>a gun</a> previously used aboard the <a class='wikilink' href='https://www.navalgazing.net/Main/Pre-Dreadnoughts'><em>Formidable</em> class pre-dreadnoughts</a>, should be enough to devastate anything short of a battleship, and the submarine would withdraw to reload and find a new target.  The gun had to be reloaded on the surface and it was difficult to bring the exposure for a shot under a minute, so only three were completed. <a href='#fnr3_2'>&#8657;</a>
</p></div><div class='footnote' id='fn3_3'>
<p><span class='footnote-number'>3</span> It appears this catapult could be driven by either compressed air or powder, which is a weird combination. <a href='#fnr3_3'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Open-Thread-198</guid>
<link>https://www.navalgazing.net/Main/Open-Thread-198</link>
<title>Main / Open Thread 198</title>
<dc:date>2026-10-23T12:00:00Z</dc:date>
<pubDate>Fri, 23 Oct 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/Main/Going-back-to-Iowa'>Going back to <em>Iowa</em></a>, Survivability - <a class='wikilink' href='https://www.navalgazing.net/Main/Survivability-Flooding'>Flooding</a> and <a class='wikilink' href='https://www.navalgazing.net/Main/Survivability-Fire'>Fire</a>, <a class='wikilink' href='https://www.navalgazing.net/Main/Underbottom-Explosions'>Underbottom Explosions</a>, <a class='wikilink' href='https://www.navalgazing.net/Main/In-Defense-of-Missile-Defense'>In Defense of Missile Defense</a>, and for 2025, Exotic Hulls Parts <a class='wikilink' href='https://www.navalgazing.net/Main/Exotic-Hulls-Part-5'>five</a> and <a class='wikilink' href='https://www.navalgazing.net/Main/Exotic-Hulls-Part-6'>six</a>, <a class='wikilink' href='https://www.navalgazing.net/Main/Drone-Countermeasures'>Drone Countermeasures</a> and <a class='wikilink' href='https://www.navalgazing.net/Main/Happy-250th-USN'>Happy 250th USN</a>.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/The-Dawn-of-Flight</guid>
<link>https://www.navalgazing.net/Main/The-Dawn-of-Flight</link>
<title>Main / The Dawn of Flight</title>
<dc:date>2026-10-18T12:00:00Z</dc:date>
<pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>I've been busy the last few weeks, and the blog post I had planned didn't quite come together in time, so please have this extract from the tour I did at <a class='urllink' href='https://www.navalgazing.net/Museum-Review-NMUSAF' rel='nofollow'>the National Museum of the US Air Force</a> in Dayton back in May.  (I'm also still working on editing the audio recording of the tour.  As I said, I've been busy.)
</p>
<hr />
<p>At the dawn of the 20th century, it looked like man was finally on the verge of fulfilling his dream of flying like the birds.  The first people to disconnect themselves from Earth's surface by a means other than falling off something were Jean-François Pilâtre de Rozier and the Marquis d’Arlandes, who rode the <a class='urllink' href='https://en.wikipedia.org/wiki/Montgolfier_brothers' rel='nofollow'>Montgolfier brothers'</a> hot air balloon in 1783, but most people soon realized that this mechanism wasn't very good, and many of the greatest scientists and engineers of the age turned their attention to the problem of flight using lift instead of buoyancy.  Among those interested in the problem were a pair of brothers, proprietors of a bicycle shop about six miles from where you are standing right now.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/WrightBrothersDayton.jpeg?v=1792286903.jpeg' alt='' /><br /><span class='caption'>Wilbur and Orville Wright</span></span></div>
<p><a class='urllink' href='https://en.wikipedia.org/wiki/Wright_brothers' rel='nofollow'>Orville and Wilbur Wright</a> first became interested in the problem of powered flight in 1899, reading everything available on the subject and then beginning their own experiments with gliders.  Ultimately, they made two major innovations.  First, unlike most other prospective airplane designers, they realized that the biggest problem would be <a class='wikilink' href='https://www.navalgazing.net/Main/The-Anatomy-of-an-Airplane'>controlling the airplane in the air</a>, and developed a method of warping the wings to control roll.  Ailerons eventually turned out to be a better option, but it was a significant breakthrough at the time.  Second, after a series of experiments with full-scale gliders in 1901 in a windy town on the coast of North Carolina known as Kitty Hawk,<a class='footnote' id='fnr4_1' href='#fn4_1'><sup>1</sup></a> they realized that the aerodynamic data they had been using wasn’t very good, and set about gathering their own, first conducting experiments using a bicycle to generate airflow and then building their own wind tunnel to study possible airfoil shapes.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Wright_First_Flight_1903Dec17_full_restore_115.jpg?v=1792286905.jpg' alt='' /><br /><span class='caption'>Orville makes man's first powered flight</span></span></div>
<p>Armed with this data, their 1902 glider was a success, and after adding an engine and designing a propeller, they returned to Kitty Hawk in 1903 with their <a class='urllink' href='https://en.wikipedia.org/wiki/Wright_Flyer' rel='nofollow'>Wright Flyer</a>.  On December 14th, Wilbur won the coin toss for the first true powered flight, but promptly crashed.  Three days later, after the damage was repaired, Orville took the plane down the track they had laid in the sands and into history.  The brothers made three more flights that day, the last one, piloted by Wilbur, lasting almost a minute and traveling 852 feet.  They did announce the flight, but after the very public crash of <a class='urllink' href='https://en.wikipedia.org/wiki/Samuel_Langley' rel='nofollow'>Samuel Langley's</a> <a class='urllink' href='https://en.wikipedia.org/wiki/Langley_Aerodrome' rel='nofollow'>attempt at a flying machine</a> a few days before, public interest had cooled.  The Wrights decided to keep their invention largely secret for fear of it being stolen, and spent the next two years refining their design, mostly working out of <a class='urllink' href='https://en.wikipedia.org/wiki/Huffman_Prairie' rel='nofollow'>Huffman Prairie</a>, a field about three miles northeast of here.  Their efforts culminated in a <a class='urllink' href='https://en.wikipedia.org/wiki/Wright_Flyer_III' rel='nofollow'>40-minute, 24-mile flight in October 1905</a>. 
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Avion_Bleriot_XI_1909.jpg?v=1792286905.jpg' alt='' /><br /><span class='caption'>The plane Bleriot crossed the Channel in</span></span></div>
<p>The next year saw <a class='urllink' href='https://en.wikipedia.org/wiki/Alberto_Santos-Dumont' rel='nofollow'>Alberto Santos-Dumont</a> make the first public flight near Paris, although his machine was primitive compared to what the Wrights had, and the center of aviation activity quickly moved to France.  In 1909, <a class='urllink' href='https://en.wikipedia.org/wiki/Louis_Bl%C3%A9riot' rel='nofollow'>Louis Bleriot</a> flew <a class='urllink' href='https://en.wikipedia.org/wiki/Bl%C3%A9riot_XI' rel='nofollow'>a machine of his own design</a> across the English Channel, the first significant demonstration that the airplane might be more than just a curiosity.  That same year, the US Army Signal Corps procured the world's first military aircraft, the <a class='urllink' href='https://en.wikipedia.org/wiki/Wright_Model_A' rel='nofollow'>1909 Wright Military Flyer</a>.  This is not that plane.  That plane belongs to <a class='wikilink' href='https://www.navalgazing.net/Main/Museum-Review-The-Smithsonian'>the Smithsonian</a>, and this is a replica, as are all of the planes in this particular section.  The Army didn't buy any more for two years, before picking up several more planes, mostly from the Wrights' great rival, <a class='urllink' href='https://en.wikipedia.org/wiki/Glenn_Curtiss' rel='nofollow'>Glenn Curtiss</a>.  But the airplane remained a military curiosity in the years leading up to 1914, even as aviators continued to push the boundaries of flight.  Although their machines were primitive and dangerous by today's standards, the foundation they built would prove vital when war broke out.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn4_1'>
<p><span class='footnote-number'>1</span> Technically, most of the work was done at Kill Devil Hills, a few miles from Kitty Hawk, but Kitty Hawk was the nearest settlement, and its name became attached to this story. <a href='#fnr4_1'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/Three-Museums-South-of-San-Francisco</guid>
<link>https://www.navalgazing.net/Main/Three-Museums-South-of-San-Francisco</link>
<title>Main / Three Museums South of San Francisco</title>
<dc:date>2026-10-11T12:00:00Z</dc:date>
<pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p><a class='wikilink' href='https://www.navalgazing.net/Main/Hornet-Take-3'><em>Hornet</em></a> wasn't the only museum I visited during my recent trip to San Francisco.  There were three others, all on the San Francisco side of the Bay, and all confused about what sort of museum they were.  Despite that, two are reasonably strong recommendations, while the third was fine, though I wouldn't recommend going out of the way for it.
</p>
<div  style='text-align: center;' class='img'> <span class='px'> <img width='600' src='/attach/HillerMuseumOverview26.jpg?v=1791679341.jpg' alt='' /> </span></div>
<p>The best of the three was the <a class='urllink' href='https://www.hiller.org/' rel='nofollow'>Hiller Aviation Museum</a> in San Carlos, about 30 miles south of San Francisco.  It's firmly at the upper end of the medium air museum category, although it's not entirely sure if it wants to be an air museum with a major focus on children, or a children's museum with airplanes.  Fortunately, it looks like they're the former for now, in addition to having probably the world's best collection of insanely dangerous rotorcraft.  
</p>
<p><a class='urllink' href='https://en.wikipedia.org/wiki/Stanley_Hiller' rel='nofollow'>Stanley Hiller</a> was an American engineer and a pioneer of the helicopter, who managed to get a draft deferment by showing the Army his design for the nation's first <a class='urllink' href='https://en.wikipedia.org/wiki/Coaxial-rotor_aircraft' rel='nofollow'>coaxial-rotor</a> helicopter.  He spent the next two decades building helicopters of various kinds, routinely pushing the boundaries of sanity in rotorcraft design, before selling his company and going on to work as a corporate turnaround specialist.  The museum that bears his name is one of the better medium-sized air museums I've ever been to.  I went in expecting a large collection of weird and dangerous rotorcraft (to the point that this is how I mentally have the museum tagged) and I wasn't disappointed.  There was basically every possible variety of "how could they possibly think that was a good idea?" with helicopters, from <a class='urllink' href='https://en.wikipedia.org/wiki/Hiller_VZ-1_Pawnee' rel='nofollow'>"guy standing over a ducted fan"</a> to "two ducted fans on the back" to <a class='urllink' href='https://en.wikipedia.org/wiki/Hiller_YH-32_Hornet' rel='nofollow'>"let's power the helicopter with ramjets on the rotor tips, then fly around firing rockets at ground targets"</a>.  
</p>
<div  style='text-align: center;' class='img'> <span class='px'> <img width='600' src='/attach/HillerAttackTipRotors.jpg?v=1791679343.jpg' alt='' />  </span></div>
<p>But it's not just helicopters where the museum's collection is full of oddities and one-offs.  There's a good section on early flight with a focus on work done in California, which was a place of daredevils and nutjobs.  Some were successful, like <a class='wikilink' href='https://www.navalgazing.net/Main/Carrier-Operations-Part-1'>Eugene Ely</a>, who they have a number of artifacts from, and others were less so, like the madman who tried to build <a class='urllink' href='https://www.hiller.org/aerocycloid/' rel='nofollow'>a weird quasi-helicopter paddle-wheel thing</a> in 1908.  Fortunately for him, it didn't get off the ground, and thus didn't kill him, and he apparently learned enough from the experience to stop building things like that.  The rest of their fixed-wing collection is eclectic to say the least.  They've got everything from <a class='urllink' href='https://en.wikipedia.org/wiki/Colomban_Cri-cri' rel='nofollow'>tiny homebuilts</a> to <a class='urllink' href='https://en.wikipedia.org/wiki/Boeing_Condor' rel='nofollow'>a giant UAV</a> to <a class='urllink' href='https://en.wikipedia.org/wiki/NASA_AD-1' rel='nofollow'>a NASA experimental plane that pivoted a single wing in flight</a>.  They did have a Mustang, but it was an air racer and suspended instead of being the focus of veneration, so <a class='wikilink' href='https://www.navalgazing.net/Main/The-Problem-with-Air-Museums'>points for that</a>.  
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/HillerMuseum747.jpg?v=1791679342.jpg' alt='' /></span></div>
<p>Beyond that, as I mentioned at the start, they've done more to integrate kid-friendly activities than any air museum I can remember.  Most have a few things off to one side, but Hiller has their stuff spread throughout, including a tower to drop parachutes off of, a paper airplane launcher thing, and a lot of simulators, several of which were free.  It almost felt like it might have taken over the museum, but they stayed just on the "still an air museum" side.  There's also a 747 fuselage outside with the cockpit opened up, and a restoration hangar you can see into.  Signage is uniformly good, and the atmosphere is great, with lots of close-packed planes.  On the whole, I think it's probably my favorite air museum ever that has no supersonic aircraft, although it's not really worth traveling for in and of itself.  If you're in the Bay Area and want to see something military/aviation adjacent, I think <em>Hornet</em> is probably the better choice, but Hiller is a pretty strong candidate, too.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img height='440' src='/attach/SFOMuseumPlanes.jpg?v=1791681213.jpg' alt='' /></span></div>
<p>A dozen miles north of Hiller is San Francisco International Airport, which is home to the <a class='urllink' href='https://www.sfomuseum.org' rel='nofollow'>SFO Museum</a>, apparently the first museum subsidiary of a major airport.  And it's probably unfair to characterize this as confused about its identity.  It's not.  It's an art museum unconvincingly wearing the mask of an air museum.  There's a bunch of different stuff scattered throughout the terminal, including a couple of galleries airside in Terminal 1, but it's all just art.  There is a small section just outside security in the international terminal that is trying to be about aviation, but they rather gave the game away when an engine on display had its materials listed like it was a sculpture or something.  They did have a cool Pan Am globe, and the space itself is gorgeous, but the displays are on things like historic travel brochures about San Francisco and photos of the city instead of "here's how the airport runs", like it should be.  There's also a very nice aviation reference library on the upper level, but it's all in locked cases and requires a reservation because whoever runs the place is clearly a sadist taking out their frustrations on aviation enthusiasts.  If you don't have an appointment, it's still not a bad place to spend an extra 15 minutes (plus however long it takes to get to/from your terminal) at SFO, but I wouldn't go out of my way to visit if I wasn't flying through the airport.
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/ComputerHistoryMuseumNTDS.jpg?v=1791681447.jpg' alt='' /></span></div>
<p>The last museum is further south in Mountain View, and while the <a class='urllink' href='https://computerhistory.org/' rel='nofollow'>Computer History Museum</a> may not be squarely in scope, they do have an <a class='wikilink' href='https://www.navalgazing.net/Main/ICNW-Part-4'>NTDS</a> rack and a bunch of stuff from <a class='urllink' href='https://en.wikipedia.org/wiki/Semi-Automatic_Ground_Environment' rel='nofollow'>SAGE</a>, so I can shoehorn it in.  On the whole, I enjoyed it, particularly the look through the early history of computing, which they take back to the abacus and the slide rule.  But while the stuff through the introduction of the PC feels fairly coherent, after that, the museum becomes extremely unsure what story it's telling.  Museums are good at presenting hardware, but as software comes to dominate and computers become more widespread, it starts to ramble.  There are other issues, too.  The signage on the NTDS rack is woefully lacking, and it's right next to a sign about fire control that isn't much better.  Oh, and they don't actually have any of the good <a class='wikilink' href='https://www.navalgazing.net/Main/Fire-Control-Part-2'>fire-control computers</a>.  Seriously, I'm sure they could scrounge up a Mk 37 system from somewhere and open up the case.  The main gallery also looks to have been last updated in about 2010, and while this doesn't really matter to the first half of the museum, it's rather weird that the name "Facebook" isn't mentioned anywhere in the main museum.  Also, the layout is one of the most baffling I've ever seen.  There are all sorts of blind alleys, and it often felt like the big "route this way" signs on the floor were telling me to skip things.  All that said, it's not a bad museum, and if you're interested in the olden days of computing and happen to be in the area, I would recommend it.
</p>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/OEF-25-Part-1</guid>
<link>https://www.navalgazing.net/Main/OEF-25-Part-1</link>
<title>Main / OEF 25 Part 1</title>
<dc:date>2026-10-04T12:00:00Z</dc:date>
<pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>The 9/11 attacks shook America to its core.  Someone was responsible, and they would have to pay.  The only questions were who and how.  Who was surprisingly easy to figure out.  A check of the passenger manifests revealed that several were known members of <a class='urllink' href='https://en.wikipedia.org/wiki/Al-Qaeda' rel='nofollow'>Al Qaeda</a>, and intercepted communications between members of the group talked about a successful operation.  But that made how extremely difficult.<a class='footnote' id='fnr5_1' href='#fn5_1'><sup>1</sup></a>  Since Sudan had kicked him out under diplomatic pressure back in 1996, <a class='urllink' href='https://en.wikipedia.org/wiki/Osama_bin_Laden' rel='nofollow'>Osama bin Laden</a> and most of his network had been based in Afghanistan, a country that was going to be as difficult to access for the US military as almost anywhere on the planet.  Direct access from the sea was impossible, and the shortest route from US bases in the region ran through Iran, which was unlikely in the extreme to grant overflight rights.  Coming in from the south would mean overflying Pakistan, the major sponsor of the <a class='urllink' href='https://en.wikipedia.org/wiki/Taliban' rel='nofollow'>Taliban</a>, while access from the north meant going through Turkmenistan, Uzbekistan or Tajikistan, all former Soviet republics that the US wasn't particularly close to.  
</p>
<div  style='text-align: center;' class='img imgonly'> <span class='px'> <img width='600' src='/attach/AfghanistanMap.jpeg?v=1791044699.jpeg' alt='' /></span></div>
<p><a class='urllink' href='https://en.wikipedia.org/wiki/Operation_Infinite_Reach' rel='nofollow'>The last time the US had gone after bin Laden</a>, in retaliation for <a class='urllink' href='https://en.wikipedia.org/wiki/1998_United_States_embassy_bombings' rel='nofollow'>the attacks on the US embassies in Kenya and Tanzania</a>, it had used <a class='wikilink' href='https://www.navalgazing.net/Main/Tomahawk-Part-3'>Tomahawk cruise missiles</a>, flying through Pakistani airspace.  But cruise missiles alone were clearly an inadequate response if the Taliban refused to hand over bin Laden, and a plan was put together under the codename <a class='urllink' href='https://en.wikipedia.org/wiki/Operation_Enduring_Freedom' rel='nofollow'>Operation Enduring Freedom</a> (OEF).<a class='footnote' id='fnr5_2' href='#fn5_2'><sup>2</sup></a>  Fortunately for the US, there was an active civil war in Afghanistan, with the so-called "<a class='urllink' href='https://en.wikipedia.org/wiki/Northern_Alliance' rel='nofollow'>Northern Alliance</a>"<a class='footnote' id='fnr5_3' href='#fn5_3'><sup>3</sup></a> still holding onto a significant corner of the country.  Both sides were poorly equipped, but with US air support, coordinated by CIA and special forces teams, there was a good chance the Northern Alliance could rout the Taliban with minimal American presence on the ground.
</p>
<p>But that was a very different thing from "minimal American presence", and planners and diplomats quickly set to work assembling the basing and overflight rights necessary to support this campaign, as well as the units required to execute it.  The most important problem was Pakistan.  The bulk of any US air effort would clearly come in from the south, either from carriers operating in the Arabian Sea or bombers flying out of Diego Garcia in the Indian Ocean, and that would mean transiting Pakistani airspace.  But while Pakistan had been an American ally during the Cold War, most prominently when America was providing support to the mujahideen fighting against the Soviets, relations had grown frosty in recent years, particularly after <a class='urllink' href='https://en.wikipedia.org/wiki/Chagai-I' rel='nofollow'>Pakistan first tested a nuclear weapon in 1998</a> and a <a class='urllink' href='https://en.wikipedia.org/wiki/1999_Pakistani_coup_d%27%C3%A9tat' rel='nofollow'>military coup a year later</a>.  Making matters worse, Pakistan had been the Taliban's major sponsor, seeing it as a way of ending the anarchy that had gripped Afghanistan,<a class='footnote' id='fnr5_4' href='#fn5_4'><sup>4</sup></a> and public opinion in Pakistan was fairly hostile to the United States.  The Bush administration gave Pakistani President <a class='urllink' href='https://en.wikipedia.org/wiki/Pervez_Musharraf' rel='nofollow'>Pervez Musharraf</a> a clear choice: either support the US in its new "War on Terror" and be rewarded with sanctions relief and increased aid, or be added to the enemies list.  Despite all of the problems, Musharraf officially chose to side with the US, and American airpower had its route into Afghanistan.<a class='footnote' id='fnr5_5' href='#fn5_5'><sup>5</sup></a>
</p>
<div  style='text-align: center;' class='img imgcaption'> <img src='/attach/Bush_in_Islamabad.jpeg?v=1791044700.jpeg' alt='' /><br /><span class='caption'>Bush and Musharraf</span></div>
<p>Pakistani support alone wouldn't be enough to enable the campaign that Central Command (CENTCOM)<a class='footnote' id='fnr5_6' href='#fn5_6'><sup>6</sup></a> wanted to fight.  Sending American aircraft over Afghanistan without CSAR<a class='footnote' id='fnr5_7' href='#fn5_7'><sup>7</sup></a> support was risky, and while units based in Pakistan, Oman or on aircraft carriers in the Arabian Sea could provide cover in the southern portion of the country, the operations in the north would need support from CSAR units based somewhere in one of the former Soviet republics.  And because all of the organized opposition was in the north, an air campaign limited to the south wouldn't be all that effective relative to one where the US could embed CIA and special forces teams with the Northern Alliance and provide air support for troops on the ground.  Tajikistan was quick to offer a base, but getting into Afghanistan from there would involve navigating high and treacherous mountains, while the Uzbek-Afghan border was relatively flat.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Members_of_the_16th_SOW_offload_a_MH-53J_Pave_Low_helicopter_from_a_C-17_in_support_of_OEF.jpeg?v=1791044699.jpeg' alt='' /><br /><span class='caption'>A CSAR MH-53J is offloaded during OEF</span></span></div>
<p>But even though Uzbekistan had hosted a secret CIA Predator base for several years, the government was being difficult, holding out for increased US aid, including against its <a class='urllink' href='https://en.wikipedia.org/wiki/Islamic_Movement_of_Uzbekistan' rel='nofollow'>own homegrown Islamist movement</a>.  Some of this might have been because it was not on good terms with Russia, whose new President, an obscure former KGB officer named Vladimir Putin, had offered Russia's full support to the war on terror.<a class='footnote' id='fnr5_8' href='#fn5_8'><sup>8</sup></a>  Uzbekistan finally agreed to allow CSAR to be based in its territory on October 1st, although getting the unit ready in time for the anticipated kickoff on the 7th would be difficult, given the primitive facilities and the need to send in 67 C-17 flights to set up the CSAR team there.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/CarlVinsonUNREPOEF.jpg?v=1791045468.jpg' alt='' /><br /><span class='caption'><em>Carl Vinson</em> replenishes during Enduring Freedom </span></span></div>
<p>The logistics situation was slightly better in the south.  The <em>Enterprise</em> group had been just about to head home when the attacks happened, while <em>Vinson</em> was on her way to take over in CENTCOM, and both carriers were ordered to stay on station in the Arabian Sea.  The <em>Roosevelt</em> group had been preparing to deploy, and was ordered to join them from Norfolk, while <em>Kitty Hawk</em>, stationed in Japan, was ordered to CENTCOM sans air wing, to be used as a "lily pad" for special forces operating in southern Afghanistan.  But they'd need a base further forward for good CSAR coverage, and a place to divert if any of the aircraft had serious problems.  Musharraf agreed to allow the Americans to use an airfield near Jacobabad, halfway between the coast and Kandahar.  Security there would be provided by a detachment of Marines from the <a class='urllink' href='https://en.wikipedia.org/wiki/15th_Marine_Expeditionary_Unit' rel='nofollow'>15th MEU(SOC)</a>,<a class='footnote' id='fnr5_9' href='#fn5_9'><sup>9</sup></a> aboard the <em>Peleliu</em> Amphibious Ready Group, which had rushed to the area from Australia.
</p>
<div  style='text-align: center;' class='img imgcaption'> <img src='/attach/HornetRefuelOEF.jpeg?v=1791045469.jpeg' alt='' /><br /><span class='caption'>A Hornet refuels over Afghanistan</span></div>
<p>If the Navy was going to contribute to the air campaign, it was also going to need quite a bit of help from the Air Force.  Much of the fleet's striking power was provided by short-legged <a class='wikilink' href='https://www.navalgazing.net/Main/Hornet-Part-1'>Hornets</a>, which were going to struggle to get past 250 nm on internal fuel, so multiple aerial refuelings would be required to reach targets in Afghanistan, which were at least twice that far away.  To maintain safety margins, at least two refuelings were needed each direction, requiring an elaborate plan to make sure nobody had to land in Pakistan or Afghanistan.  Some of the fuel could be provided by S-3 Vikings off the carriers, but the bulk would need to come from land-based tankers, flying either from Diego Garcia or the various nations on the shores of the Arabian Gulf.  The US had an extensive network of bases there, heavily used in <a class='urllink' href='https://en.wikipedia.org/wiki/Operation_Southern_Watch' rel='nofollow'>the campaign against Saddam</a>, although the Saudis, concerned about domestic reaction to Americans bombing a Muslim country from their territory,<a class='footnote' id='fnr5_10' href='#fn5_10'><sup>10</sup></a> came close to refusing to allow CENTCOM to use the new air operations center that had opened at Prince Sultan Air Base just months before.  The other Gulf States were more cooperative, and Kuwait, Bahrain, Qatar, the UAE and Oman all played host to tankers and other support aircraft.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/RAF_Tristar_USN_F-18C_Afghanistan_Oct2008.jpeg?v=1791045468.jpeg' alt='' /><br /><span class='caption'>An RAF Tristar passes fuel to Hornets</span></span></div>
<p>And it was here that international support for the US showed itself beyond simply basing and overflight rights.  There was no way the British could stay out of such an <a class='wikilink' href='https://www.navalgazing.net/Main/Falklands-Part-6'>insane aerial refueling plan</a>, and RAF VC10s and Tristars served alongside <a class='wikilink' href='https://www.navalgazing.net/Main/US-Military-Aircraft-Part-2'>KC-135s and KC-10s</a>, providing about 20% of all tanking for the Navy's effort.  The RAF also contributed <a class='wikilink' href='https://www.navalgazing.net/Main/Nimrod'>Nimrods</a> and Canberras to gather information for targeting purposes, while Australia sent fighters to defend the base at Diego Garcia, home not only to tankers but also to B-52 and B-1 bombers, the Air Force's way of making sure it didn't feel left out from the fun.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/Preparing_weapons_for_war_Vinson.jpg?v=1791046284.jpg' alt='' /><br /><span class='caption'>Bombs are readied aboard <em>Vinson</em></span></span></div>
<p>Things began to kick off in late September, when the CIA started infiltrating members of the secretive <a class='urllink' href='https://en.wikipedia.org/wiki/Special_Activities_Center' rel='nofollow'>Special Activities Division</a> into the country to meet up with the Northern Alliance and prepare for the arrival of uniformed special forces units, which would first arrive in mid-October.  Before they could get there, the air campaign began, with the first bombs falling on October 7th.  The initial targets were what passed for the Taliban's air defenses, mostly systems inherited from the Soviet-backed government that had fallen in 1992.  About 100 MiG-21 and Su-22 fighters were in the country, although only half were even vaguely operational, and there weren't enough pilots even for those.  The same could be said of radar and SAM systems, with only a few SA-3s near Kabul and Kandahar that could pose any threat to US aircraft at medium or high altitude.  Lower down, AA guns and shoulder-fired SAMs were more dangerous, but easy enough to avoid.  Still, there was no point taking chances, and the highest-risk targets would be dealt with by a pair of B-2s flying direct from Missouri carrying 32 <a class='wikilink' href='https://www.navalgazing.net/Main/JDAM'>JDAMs</a> between them, with numerous aerial refuelings during their 44-hour mission.  Other targets, including tank concentrations and Al Qaeda training camps, were hit by <a class='wikilink' href='https://www.navalgazing.net/Main/US-Military-Aircraft-Part-1'>5 B-1s and 10 B-52s</a> from Diego Garcia, as well as 25 fighters from the carriers.  All told, the attacks on the first night, which also included 50 <a class='wikilink' href='https://www.navalgazing.net/Main/Tomahawk-Part-3'>TLAMs</a> from destroyers and submarines (including the British SSNs <em>Triumph</em> and <em>Trafalgar</em>), went after 31 targets with 275 individual aimpoints, destroying about 85% of them.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img height='440' src='/attach/John_Paul_Jones_Tomahawk_Launches_into_Afghanistan.jpg?v=1791046285.jpg' alt='' /><br /><span class='caption'><em>John Paul Jones</em> launches a Tomahawk into Afghanistan</span></span></div>
<p>But taking out the Taliban's air defenses, and even some strategic targets, would not be enough to topple their government.  That would take American soldiers on the ground to provide air support for the Northern Alliance, and ultimately a wholesale occupation of the country, a topic we will turn to next time.
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn5_1'>
<p><span class='footnote-number'>1</span> I'm going to ignore the diplomatic, intelligence and financial efforts made to fight terrorism in favor of studying the military campaign.  This isn't to underrate the importance of these, particularly the financial aspects. <a href='#fnr5_1'>&#8657;</a>
</p></div><div class='footnote' id='fn5_2'>
<p><span class='footnote-number'>2</span> The original codename had been "Infinite Justice", but this was changed when it was pointed out that many Muslims think that only Allah can deliver infinite justice. <a href='#fnr5_2'>&#8657;</a>
</p></div><div class='footnote' id='fn5_3'>
<p><span class='footnote-number'>3</span> Afghanistan is split between different ethnic groups, and the Pakistan-backed Taliban was largely Pashtun, who made up about 40% of the population, while the Northern Alliance was largely Tajik and Uzbek, and received a lot of support from Iran. <a href='#fnr5_3'>&#8657;</a>
</p></div><div class='footnote' id='fn5_4'>
<p><span class='footnote-number'>4</span> And of getting rid of the Afghan refugees that had flooded over the border starting with the Soviet invasion. <a href='#fnr5_4'>&#8657;</a>
</p></div><div class='footnote' id='fn5_5'>
<p><span class='footnote-number'>5</span> Unofficially, I trust we all remember <a class='urllink' href='https://en.wikipedia.org/wiki/Death_of_Osama_bin_Laden' rel='nofollow'>where they finally found bin Laden</a>. <a href='#fnr5_5'>&#8657;</a>
</p></div><div class='footnote' id='fn5_6'>
<p><span class='footnote-number'>6</span> The US <a class='wikilink' href='https://www.navalgazing.net/Main/A-Brief-Overview-of-the-United-States-Fleet'>combatant command</a> responsible for the Middle East and Central Asia. <a href='#fnr5_6'>&#8657;</a>
</p></div><div class='footnote' id='fn5_7'>
<p><span class='footnote-number'>7</span> Combat Search and Rescue <a href='#fnr5_7'>&#8657;</a>
</p></div><div class='footnote' id='fn5_8'>
<p><span class='footnote-number'>8</span> This wasn't out of the goodness of his heart.  He was still something of an international pariah thanks to Russia's <a class='urllink' href='https://en.wikipedia.org/wiki/Second_Chechen_War' rel='nofollow'>brutal suppression of a revolt in Chechnya</a>, and, fortunately for him, there were significant ties between the Chechen rebels and Al Qaeda. <a href='#fnr5_8'>&#8657;</a>
</p></div><div class='footnote' id='fn5_9'>
<p><span class='footnote-number'>9</span> A reinforced Marine battalion, with its own aircraft and logistics. <a href='#fnr5_9'>&#8657;</a>
</p></div><div class='footnote' id='fn5_10'>
<p><span class='footnote-number'>10</span> The presence of American forces in the home of Islam's holy sites was one of bin Laden's cited grievances, after all. <a href='#fnr5_10'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
<item>
<author>bean</author>
<guid>https://www.navalgazing.net/Main/GM-Patriot-and-the-ISV</guid>
<link>https://www.navalgazing.net/Main/GM-Patriot-and-the-ISV</link>
<title>Main / GM, Patriot and the ISV</title>
<dc:date>2026-09-27T12:00:00Z</dc:date>
<pubDate>Sun, 27 Sep 2026 12:00:00 GMT</pubDate>
<description><![CDATA[<p>There have been a few news stories lately about General Motors producing missile casings for the PAC-3, and delivering the parts within 22 days of the contract being signed.  And, obviously, there has been commentary overinterpreting this as being a sign that players outside the traditional defense industry are better and that the glorious dawn of fast weapons manufacturing is just around the corner, if we embrace new, agile companies like... General Motors.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/PAC-3_MSE_interceptor_missile_-_MSPO_2026_Poland_Kielce.jpg?v=1790463681.jpg' alt='' /><br /><span class='caption'>A PAC-3 missile with a defective casing</span></span></div>
<p>Obviously, I think all of this is nonsense.  First, let's be clear what we're talking about.  These are missile casings, basically mildly specialized pieces of metal.  Shaping metal is not a particularly new technology, and I find it hard to believe that casings are the main limiting factor in expanding PAC-3 production.  Seekers, warheads and motors are all much more specialized and much harder to expand.  The most likely reason behind all of this is that there was some hiccup on the part of whoever normally makes the casings, and Lockheed turned to GM to bail them out.  I spoke to an industrial engineer who has experience in missile production, and she said that 3 weeks would be a reasonable turnaround time for this kind of thing in the civilian world if the customer supplied the tooling.  GM probably did some extra work to avoid the delays you frequently get on defense projects, but it's either a short-term stopgap or the whole thing was a publicity stunt, and Lockheed is now holding onto a bunch of casings that they won't use until mid-February.  
</p>
<p>But it's also worth noting that this isn't GM's only foray into defense production.  They famously built a lot of stuff in WWII, everything from trucks to airplanes to weapons.  After the war, they stayed in the industry.  Besides building various vehicles, they owned <a class='urllink' href='https://en.wikipedia.org/wiki/Allison_Engine_Company' rel='nofollow'>Allison</a>, a major jet engine manufacturer, as well as being heavily involved in military electronics, most notably inertial navigation systems, through its AC Spark Plugs/Delco division.  In the mid-80s, they bought Hughes Aircraft, becoming a major player in the satellite and missile spaces.  But as GM got into deeper and deeper financial trouble during the 90s and 00s, these were all sold off, with Allison going to Rolls-Royce, the satellite divisions to Boeing and most of the rest of the business to Raytheon.  The last bit to be sold was the ground vehicle group, which became part of General Dynamics Land Systems shortly after it won the contract for the <a class='urllink' href='https://en.wikipedia.org/wiki/Stryker' rel='nofollow'>Stryker</a>.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/3rd_Brigade_2nd_Infantry_Division_Stryker_convoy.jpeg?v=1790463680.jpeg' alt='' /><br /><span class='caption'>An early Stryker exercise</span></span></div>
<p>I bring this all up mostly as a way to remind people that the history of the defense industry is complicated, and that a lot of the reports of consolidation are overblown.  Many of you have probably seen the chart from the <a class='urllink' href='https://www.18theses.com/' rel='nofollow'>"18 theses"</a> <del>advertisement for Palantir</del>, which shows 51 primes falling to 5.  At least three different groups mentioned in the previous paragraph are listed separately among the 51, and the people who made said chart played similar games elsewhere.  Most notably, at least three different divisions of General Dynamics are shown as separate "primes", rolling up to Lockheed and Raytheon, even though GD is one of the 5 current primes.  And Avondale Industries, Litton Industries and Newport News Shipbuilding are all shown rolling up into Northrop Grumman, even though the vast bulk of those businesses was spun off as Huntington Ingalls in 2011.  Yes, I'm sure they can point to some bits of those companies that Northrop kept, but HII is the 7th largest defense contractor, behind the big 5 and L3Harris.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/YF-22_and_YF-23.jpeg?v=1790463925.jpeg' alt='' /><br /><span class='caption'>ATF prototypes</span></span></div>
<p>But even if we ignore the many flaws in the chart, the basic thesis behind it is deeply flawed.  1980 wasn't some golden age when "51 primes" rushed in to bid on every possible defense contract.  The defense industry is big and specialized, and many of the "primes" in question only did one or two things.  Boeing didn't build tanks, Chrysler didn't build airplanes and "Jappesen Sanderson" didn't exist.<a class='footnote' id='fnr6_1' href='#fn6_1'><sup>1</sup></a>  A lot of the movement on the chart is reflective of the stock market's growing distaste for general-purpose conglomerates, which has applied far outside the defense industry.  This isn't to say that there hasn't been actual consolidation in terms of "how many companies could plausibly bid on this contract", because there absolutely has been, but it's closer to 50% than 90%.  For instance, in 1986 the Advanced Tactical Fighter program that ultimately became the F-22 attracted bids from Boeing, General Dynamics, Grumman, Lockheed, Northrop, McDonnell Douglas, and North American Rockwell, whereas the only competitors for a similar program today would be Boeing, Northrop Grumman and Lockheed Martin.  But this mirrors a general drop in budgets.  Keeping design and production capability around is expensive, and if we wanted more people able to do it, we would need to pay for it somehow.
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/A-GMV_during_exercise_Immediate_Response_19.jpg?v=1790463680.jpg' alt='' /><br /><span class='caption'>An M1297 Army Ground Mobility Vehicle</span></span></div>
<p>But another part of the "defense reform" thesis is that outside companies are somehow more efficient, because they're subject to market discipline rather than being able to grow fat and lazy servicing the undemanding DoD.<a class='footnote' id='fnr6_2' href='#fn6_2'><sup>2</sup></a>  But GM itself gives us one of the better tests of this.  They returned to the defense business 10 years ago, focusing on military applications of their existing automotive technologies.  And while they've done some development work, their main focus has been on competing in the Army's ongoing efforts to provide a light, airmobile vehicle for its normal "leg" infantry.  The first competition was held in 2014, and while GM entered a vehicle based on their Chevrolet Colorado ZR2 off-road truck, they found themselves up against a field largely of more bespoke off-road vehicles, including the purpose-built <a class='urllink' href='https://en.wikipedia.org/wiki/General_Dynamics_Flyer#Flyer_72' rel='nofollow'>General Dynamics Flyer 72</a>, <a class='urllink' href='https://en.wikipedia.org/wiki/Polaris_Inc.#DAGOR' rel='nofollow'>Polaris DAGOR</a> and <a class='urllink' href='https://en.wikipedia.org/wiki/Phantom_Badger' rel='nofollow'>Boeing Phantom Badger</a>.  The Flyer won the initial round, becoming the <a class='urllink' href='https://en.wikipedia.org/wiki/M1297_Army_ground_mobility_vehicle' rel='nofollow'>M1297 Army Ground Mobility Vehicle</a>, but a second round saw GM triumph with the <a class='urllink' href='https://en.wikipedia.org/wiki/M1301_infantry_squad_vehicle' rel='nofollow'>M1301 Infantry Squad Vehicle</a>.  
</p>
<div  style='text-align: center;' class='img imgcaption'> <span class='px'> <img width='600' src='/attach/US_Army_M1301_with_9_troops.jpg?v=1790463683.jpg' alt='' /><br /><span class='caption'>M1301 Infantry Squad Vehicle</span></span></div>
<p>I don't want to get into the debates about the soundness of the idea behind the M1301,<a class='footnote' id='fnr6_3' href='#fn6_3'><sup>3</sup></a> and instead look at the finances, at least as far as that makes sense given the <a class='wikilink' href='https://www.navalgazing.net/Main/Military-Procurement-Pricing'>usual wackiness of military pricing</a>.  For a start, a civilian Colorado ZR2 looks to be running $50-55k, while the cost of one M1301 per <a class='urllink' href='https://www.asafm.army.mil/Portals/72/Documents/BudgetMaterial/2027/Discretionary%20Budget/Procurement/Other%20Procurement%20-%20BA1%20-%20Tactical%20&amp;%20Support%20Vehicles.pdf#page=103' rel='nofollow'>the FY 2027 justification book</a> is about $190k.  I honestly don't find this all that surprising.  GM may claim 90% off-the-shelf parts, but I think some of those aren't on the base ZR2, and <a class='wikilink' href='https://www.navalgazing.net/Main/The-Problem-of-Defense-Economics'>the military is a terrible and annoying customer</a>, so 3x the price isn't that weird.<a class='footnote' id='fnr6_4' href='#fn6_4'><sup>4</sup></a>  Perhaps a better comparison is how the cost of GM's approach compares to other vehicles.  One place to look is at Army budget projections before and after the contract went to GM in 2020.  The <a class='urllink' href='https://www.asafm.army.mil/Portals/72/Documents/BudgetMaterial/2021/Base%20Budget/Procurement/OPA_BA_1_FY_2021_PB_Other_Procurement_BA1_Tactical_and_Support_Vehicles.pdf#page=90' rel='nofollow'>FY21 book</a>, submitted Feb 2020, shows a predicted FY21 cost of $190k per ISV, while the <a class='urllink' href='https://www.asafm.army.mil/Portals/72/Documents/BudgetMaterial/2022/Base%20Budget/Procurement/OPA_BA_1_FY_2022_PB_Other_Procurement_BA1_Tactical_and_Support_Vehicles.pdf#page=83' rel='nofollow'>FY22 book</a>, submitted in May 2021, shows only $150k per vehicle in FY 21.  So it does look like this produced some real savings relative to what the other options probably would have cost, although it's on the order of 20-25%, and we don't know what other tradeoffs the lower-cost vehicle may have required.  But it's also worth noting that the same FY22 book shows the per-unit cost for the new-production M1152A1 HMMWV, a significantly larger vehicle without a civilian production line to draw from, at $144k per unit.  
</p>
<p>The lesson that should be drawn from all of this is that there is no silver bullet for the problems plaguing American defense procurement.  Outsiders may have advantages over the incumbents, but these tend to be small and swamped by the mess built into the structure of the system.  If all you look at is the headline figures, you'll be <a class='wikilink' href='https://www.navalgazing.net/Main/Abstractions-in-Defense-Analysis'>deeply confused about the problems</a>, which in turn leads to ineffective solutions.  
</p>
<hr />
<div class='footnotes'>
<div class='footnote' id='fn6_1'>
<p><span class='footnote-number'>1</span> <a class='urllink' href='https://en.wikipedia.org/wiki/Jeppesen' rel='nofollow'>Jeppesen Sanderson</a>, which did exist, made navigation and flight planning products.  It's now part of Boeing, consolidated with the mythical division of Boeing that previously made navigation products. <a href='#fnr6_1'>&#8657;</a>
</p></div><div class='footnote' id='fn6_2'>
<p><span class='footnote-number'>2</span> People who claim this never seem to talk about Boeing, which alone among the major primes makes about 50% of its money in non-defense businesses.  By all rights, it should be head and shoulders above everyone else, which I don't think is the general consensus. <a href='#fnr6_2'>&#8657;</a>
</p></div><div class='footnote' id='fn6_3'>
<p><span class='footnote-number'>3</span> The <a class='wikilink' href='https://www.navalgazing.net/Main/Pentagon-Wars-and-Procurement'>Pentagon's evaluators</a> viewed it as "not survivable", which is probably true.  On the other hand, it's also a lot faster than walking, and easier to airlift than other vehicles. <a href='#fnr6_3'>&#8657;</a>
</p></div><div class='footnote' id='fn6_4'>
<p><span class='footnote-number'>4</span> If you go fishing for per-unit numbers, you'll find ones that are a lot higher, because people are just dividing the annual topline by the total procurement number, which is going to roll in a lot of sustainment that isn't included in actual procurement.  Because of how variable that work is, it's easy to get numbers that are all over the place. <a href='#fnr6_4'>&#8657;</a>
</p></div></div>
]]></description><dc:contributor>bean</dc:contributor>
</item>
</channel>
</rss>
