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.

A PAC-3 missile with a defective casing

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. Read more...

It's time once again for our regular open thread. Talk about whatever you want, so long as it isn't culture war.

Overhauls are Understanding Hull Symbols, Auxiliaries Part 3, ICNW Part 5, the Arleigh Burke class, Standard Part 1, Evan's review of Turner Joy, and for 2025, Exotic Hulls Parts two, three and four, as well as Fighting the Last War.

While in San Francisco for the Pokemon World Championships, I made a third attempt to visit Hornet, this time making sure there wasn't a furry convention going on. Things started off well when I decided to take the ferry from downtown San Francisco to the Alameda Seaplane Terminal, which is maybe half a mile from the ship. The trip was lovely if a bit windy, with gorgeous views of San Francisco and a nice pass by Hornet on the arrival end.

Hornet from the ferry

Website

Hornet is one of the Essex class carriers that won the Pacific War, having been named after the previous Hornet, sunk during the fighting in the Solomons. She racked up an impressive score in WWII, then was modernized to fly early jets, with steam catapults and an angled deck. However, she missed out on the second round of modernization and was reclassified as an anti-submarine carrier (CVS), flying SH-3 Sea King helicopters and S-2 Tracker ASW aircraft as a companion to the strike carriers.¹ Just before her retirement in 1970, she was the recovery ship for the Apollo 11 and 12 missions, and the deck is marked with the spot where Neil Armstrong took his first steps after his return to Earth. Read more...

During strikes against Formosa in October 1944, two American cruisers were torpedoed, Canberra and Houston. Both suffered damage that took their engines entirely offline, and Houston lost her boilers as well, leaving her almost entirely without power, but instead of taking the crews off and scuttling the ships, the decision was made to tow them home. Two days after the original torpedoing, Houston was struck again, this time in the stern. The resulting avgas fire was quickly dealt with, but it left the hangar flooded and threatening the stability of the ship thanks to free surface as well as the structural integrity of the adjacent bulkheads.

Damage to Houston's stern after the second torpedo hit

The crew quickly swung into action, building shoring around the forward bulkhead of the hangar to make sure that the flooding didn't spread, using up the last of their materials in the process and having to scavenge whatever wood they could find elsewhere on the ship, including 14 planks usually used to support men cleaning and painting the sides. But there were other problems to deal with. The hit aft had sent shocks ripping through the ship, exacerbating the structural damage caused by the first torpedo hit, although the stress amidships was reduced by the additional weight aft. More urgently, leakage from the hit had shorted out the main emergency generator, and with only the secondary generator, there wasn't enough power to provide the crew remaining onboard with anything like adequate sanitation or food. 300 of the 550 men aboard would need to be transferred to the escorting destroyers, but the seas were too rough for them to come alongside. Read more...

It's weird visiting a doomed museum. Not one that's slowly dying, with money and volunteer enthusiasm gradually ebbing away, where you sort of know in the back of your head that if there's a catastrophe with the roof or something like that, there may not be enough money to fix it. I've been to a few of those over the years. In those cases, there's always hope. Maybe a donor can be found, or new leadership can turn things around. This wasn't that. This was a museum that is already dead, and we're just waiting to pull the plug.

A week ago, I visited the Puget Sound Coast Artillery Museum in Fort Worden, Washington, at the gateway to Puget Sound. Tomorrow, September 7th, 2026, is their last day after 50 years.² And I, crazy person that I am, said "well, I'm going to be on the West Coast anyway, might as well tack on a couple days and see it before it closes." So I left Lord Nelson among the Pokemon people of San Francisco and flew up to Seattle, then drove out to see what there was. And it was a nice little museum. It's clearly a smaller operation, with laminated printouts for signage and displays that show what they have, rather than a carefully-selected subset of the collection to best tell the story they're trying to tell. But those can be lovely and charming. That was more or less how the 45th Infantry Museum felt, and I regularly miss it now that it's been replaced by something more modern and sterile. As for this museum, well, it wasn't going to set the world alight. It wasn't even the best one I visited that day. (Turner Joy down in Bremerton is one of the best-executed museum ships I've ever seen. Review coming at some point soon.) But they did a pretty good job of telling the story of coastal defenses in the early 20th century, and it's a story that is pretty hard to find elsewhere. I've tried quite often to visit coastal fortifications, and it's generally been a frustrating experience in some dimension. The concrete may be there, but the stories aren't. The Fort MacArthur museum seems to have folded at some point in the last couple years, and there wasn't anything in the area around San Francisco except for Fort Point, which is from an older generation. Here, there was not only a place to learn the stories, but also several lovely batteries to go hike around, and I'm sad that only the second half will remain for visitors after tomorrow. Read more...

I've long wanted to do an analysis of how bomb accuracy has changed over the last 80 years or so, and how this impacts the cost of destroying a target from the air. The problem has always been that all of the data I need, from bomb accuracy to the cost of flying the planes, is scattered and sparse, and so I haven't really made much progress. But a recent comment from cassander inspired me to give it a try in Command: Modern Operations, which is basically a medium-level simulation package that is sold on Steam. I've used it for other experiments, and it could give at least a fairly reasonable number for how many bombs it takes from a given platform/delivery mechanism to destroy a generic target.

The basic setup I used for all of these tests was fairly simple. I set up a grid of 10 medium buildings (130' x 80') in CMO and then on the opposite side set up a nearby airbase with 12 planes of the type under test. All were given the same loadout (usually the heaviest one for the weapon in question) and set up to attack one at a time, using only one bomb at a time on a given target to prevent overkill from messing up my numbers. I would run the scenario until either all of the targets were destroyed or all of the planes had flown their sorties. Variables included the plane, the weapon, attack altitude and environmental conditions (day/night and weather). Read more...

It's time once again for our regular Open Thread. Talk about whatever you want, so long as it isn't culture war.

Overhauls are Information, Communication and Naval Warfare Part 1, Falklands Part 5, The Battleship of the Future?, Wedding Decorations, A Brief Overview of the United States Fleet, Naval Radar - More Advanced Stuff, Speed and Range in Battleships, and for 2025, SCUBA Parts one and two, The Tanker War Part 2 and Exotic Hulls Part 1.

I've been watching through the documentary series The World at War lately, and figured it was worth talking about here. For those who don't know, it was aired in the early 70s, and is generally acclaimed as one of the greatest documentary series ever. I'm not much of one for documentaries in areas I'm familiar with, because they're frequently not particularly efficient and I often find myself frustrated by the editorial decisions made, but The World at War mostly manages to avoid these problems, and illustrates a conscious approach to doing history for the public that I really like.

The most obvious problem that any series like this is going to run into is simply how to divide up the war, because even with 26 episodes, a lot is going to be left out. TWAW handled this particularly well, abandoning any real pretense that it was going to be comprehensive and instead making each episode a self-contained story about a specific aspect of the war. This could be a battle or a campaign, the home-front experience of some nation or it could be something narrower like the Holocaust or the occupation of Holland. Particularly groundbreaking at the time was a significant focus on Russian experience during the war, and those portions were still some of the most interesting to me, as it's not an area I've studied extensively. But more importantly, each story generally does a really good job of balancing the human stories with the broad operational story of the war. Often history focuses either on "what happened and why?" or on "what was it like to be there?", and TWAW manages to balance both rather well. Read more...

Probably the most obscure corner of carrier aviation is COD, Carrier Onboard Delivery. This is exactly what it sounds like, the practice of delivering high-priority cargo, mail and personnel from bases ashore to aircraft carriers. The role originated in the immediate postwar years, and was first carried out by TBM Avengers modified to carry six passengers or cargo in the former bomb bay. But it was soon clear that the limited cargo weight and volume would be a problem for air-delivery of important cargoes like jet engines and nuclear weapons.³

A C-1 Trader

The Navy ultimately chose to procure the C-1 Trader, a variant of their existing S-2 Tracker ASW aircraft with an enlarged fuselage. Entering service in 1956, the Trader would go on to serve for three decades in the USN, ultimately becoming the last operational piston-engined aircraft to fly from American carriers. But it was slow and limited in range, and, more importantly, it was soon unable to carry the largest jet engines in use by the fleet. The Navy again turned to Grumman to adapt an existing design with a new fuselage, turning the E-2 Hawkeye into the C-2 Greyhound. Ultimately, it would serve for almost 60 years until the growth of jet engines, in particular the F135 for the F-35C, caused the Navy to procure a new COD airplane capable of carrying it. The winner in this case was the CMV-22,⁴ based on the V-22 Osprey beloved of the Marines and loathed by budget analysts. Read more...

In mid-October 1944, the American carriers under Admiral Halsey were operating in the waters between Taiwan (then known as Formosa) and the Philippines, to destroy Japanese power in the area before the US invasion of Leyte. Unfortunately, on October 13th, the heavy cruiser Canberra was torpedoed by Japanese aircraft, flooding both engine rooms. Normal practice would have been to take the crew off and abandon her, but Admiral Halsey decided to tow her clear by cruiser Wichita instead. The next day, light cruiser Houston was also torpedoed, losing not only her engines but also all of her boilers, which meant there was only emergency power available throughout the ship. She was in considerably worse shape than Canberra, with serious concerns that she would break up early on, leading most of the crew to abandon ship before the decision was made to try to tow her clear as well.

The path of CripDiv 1⁵

On the morning of October 15th, a group, dubbed "CripDiv 1", was formed to protect the two crippled cruisers, with three light cruisers and eight destroyers to provide close cover. Light carriers Cabot and Cowpens, with a separate group of escorts, would provide air cover. Houston, towed by heavy cruiser Boston, spotted the group shortly after Wichita passed the tow to tug Munsee, and finally reached her station around noon. Meanwhile, Radio Tokyo was putting out increasingly outlandish claims about the damage inflicted on the Americans, prompting parties in the streets. Halsey's staff wondered about how much was deliberate propaganda and how much the Japanese genuinely believed. If they were taking their more outrageous claims (half a million tons of shipping sunk, 53 ships including 16 carriers on the bottom) seriously, then it was plausible that they'd send surface forces out to mop up. One carrier group was sent to hit airfields around Manila on the 15th and 16th, while two others were pulled out of range of Japanese search planes in the hopes of luring them out. Only one was left in position to protect CripDiv 1, an understandably unpopular move among the men of the group. One of the captains of the escorting light cruisers commented "Now I know how a worm on a fishhook must feel" and the name "BaitDiv1" began to circulate. Read more...