The Broken Arrow Up North

This is a follow-up to my last post about the B-29 crash near Fairfield in 1950. Today falls within those several days in August when we think about Hiroshima and Nagasaki, so here’s a tale from the Cold War about the other Broken Arrow incident to happen nearby.

On 14 March 1961 a B-52F bomber carrying two Mark 39 Mod 2 thermonuclear weapons, each with a yield of 3.8 megatons, crashed in Sutter County about fifteen miles west of Yuba City and 40 miles north of our location in Davis. The plane had taken off 22 hours previously from Mather Air Force Base just east of Sacramento. (This base closed in 1993 and the field is now a general aviation airport). The plane was flying on an Operation Chrome Dome mission doing circuits over the Aleutian Islands. Chrome Dome was a Cold War mission between 1961 and 1968 where bombers would fly on alert armed with thermonuclear weapons in a position to attack targets in the Soviet Union if they got the call, with some portion of the nuclear bomber force airborne 24 hours a day.

The mission of this particular B-52F did not go well from the start. About twenty minutes into the flight very hot air started bleeding into the cockpit and the crew was unable to sort out the problem. Temperatures within the cabin grew to between 125–160 °F, and the crew took turns going to the deck below the cockpit to escape the heat. In contact with the Mather command post, the crew received instructions to continue with the mission as long as possible. Fourteen hours into the flight the pilot’s window cracked with the heat, depressurizing the aircraft. The crew decided to descend to 12,000 feet following the depressurization.

At this point the crew was exhausted and dehydrated and started making many mistakes. One of these errors was miscalculating the fuel burn rate, which was higher than normal because of the lower altitude, and a stuck fuel gauge didn’t help with the perception of the problem. Eventually they alerted Mather of their need for an air tanker, but they ran out of fuel about 2 1/2 miles before the rendezvous with the tanker. With the plane doomed to crash at that point, all crew members were able to bail out successfully, with the pilot steering the plane at the last minute toward a fallow rice field. The only fatality in the incident occurred on the ground when a fire truck responding from Beale Air Force Base overturned. The two hydrogen bombs aboard the plane were severely damaged in the crash but the high explosives they contained did not detonate and no radioactive materials were released.

In hindsight the crew should have aborted the mission when the cockpit temperatures grew unbearable. But this was the height of the Cold War, and Strategic Air Command was pushing their wing commands very hard to keep the early airborne alert program operational at all times.

The Broken Arrow Down The Road

A Broken Arrow incident is, in United States military terminology, an accidental event involving nuclear weapons or components that does not create a risk of nuclear war. Today is the 75th anniversary of a Broken Arrow event that happened in Solano County less than 25 miles from here.

On 5 August 1950 a Boeing B-29 bomber was leaving Fairfield-Suisun Air Force Base bound for Guam when it crashed shortly after takeoff. It was carrying a Mark 4 nuclear bomb and was part of a contingent of 10 nuclear-capable B-29s being sent to Guam to serve as a deterrent to the People’s Republic of China at the start of the Korean War. The bomb in this B-29 did not have its fissile core installed so there was no risk of a nuclear explosion, but the high explosives in the bomb could and did explode in the fire subsequent to the crash. 12 of the 20 crew and passengers on the plane died in the event, as well as 7 people on the ground in the explosion which spread wreckage over about 2 square miles.

One of the passengers killed in the crash was Brigadier General Robert F. Travis, who at the time was commanding the 5th and 9th Strategic Reconnaissance Wings. To honor him, the base was renamed Travis Air Force Base in 1951.

I learned about this anniversary by seeing a reference to it on my Cat Lovers Against The Bomb calendar. I very much like the version of this calendar (the “classic” version) with black-and-white photographs of cats and have been using it as my office calendar for many years now.

Google Creepiness Example 587

A couple weeks back, I bought a new cellphone. This was after the battery died on my old phone from 2019. I took the phone to a local shop to try to get the battery replaced, but despite a valiant attempt at the replacement, the phone was moribund and I ended up spending $160 to acquire a 2023 Moto Power 5G running Android 13. I have not put many apps on the phone to date, and don’t plan to load it up much.

The other day I opened my phone to a notification giving me a tour of the new features these days in Android. Google is now pushing their Gemini AI chatbot technology as much as possible. I have tried to disable Gemini as far as I can on my phone, but I’m sure it will creep back. Anyway, the first slide of this tour was about Gemini, and the slide suggested Gemini would be helpful in finding interesting places to check out in Barcelona, specifically in the Gràcia district. Um. This is all too close to my current interests to be a coincidence. I don’t think Google knows I currently have two books checked out on Barcelona from the public library, since libraries are extremely good about keeping patron information private, but on June 29 I did watch an Easy Catalan video entitled Barcelona’s Neighborhoods: Gràcia. (I know the date because I’m keeping a log of my Catalan input). I try my best to keep Google off my trail, but this is obviously quite hard to do.

Two Days at The Marine Mammal Center

I have just spent two days in the fog on the Marin Headlands, doing graphic recording for a workshop on vessel strikes on whales. Climate change and other causes are forcing whales to change their movement patterns and when they get hit by a ship — or even a pleasure craft, like a sailboat — they get injured and often killed. There is an estimate that of every dead whale that is recorded, either floating or washed up on shore, there are probably ten that are never seen. This is particularly bad in the case of gray whales which have been coming into San Francisco Bay more and more to feed, a body of water that is full of risks for them.

This was a group of scientists, tech folks and policy folks assessing the ways to find out more about where the whales are, what the boat traffic is doing (this is very well recorded for large vessels, less so for small fishing or pleasure craft), and what can be done to reduce or mitigate the risks. It’s a bit depressing especially in the current funding crisis but being around people who are so passionate about what they do, who keep trying to find ways to save the planet in the face of unbelievable odds, was inspiring.

Artificial Intelligence and Language Learning Part Two

Pica a few days ago mentioned how she just took a German class on the theme of artificial intelligence. This seems to be a common theme nowadays among language learning groups, since the topic came up in my Spanish conversation group on Friday. It ended up being something of a debate about whether AI is a good tool in language learning. I am in the middle on this one. AI is very useful in providing translations on the fly: my favorite translation service is the one provided by Kagi, and I also like having a browser plugin that allows you to click on a word in a text and get a translation of it, such as TransOver for Chrome-based browsers (I use Vivaldi). I have never tried using a chatbot for foreign language chatting practice, and tend not to think it would work well. One person in our conversation group didn’t like using a foreign language chatbot because they didn’t seem to take the initiative in conversations. Another person in the group said that since the whole point of learning another language is to connect with others, it’s not very rewarding to be talking to a chatbot. There are other AI tools that seem useful for language students. Text-to-speech generators may be able to help with pronunciation of blocks of text. The Kagi translation tool I mentioned above has a proofreading feature which might help with correcting writing errors. As always with AI, one has to be careful since these are never perfect.

Artificial Intelligence

As I’ve mentioned previously, I’ve been learning German for the past three years, initially through Duolingo and more recently through Lingoda. I’ve taken 46 classes — 46 hours of instruction in group sizes of five students or fewer (and, mostly the average class size has been three). The classes are divided up into the categories of Communication, Reading, Grammar, and Speaking. The level of instruction has been high and I’m glad to say I was today awarded a certificate: I’ve progressed through the beginner level of B2. This means I’m technically now an intermediate intermediate.

This morning’s class was talking about AI, which in German is Kunstliche Intelligenz (or KI). I’m normally the oldest student in the class which I don’t mind, especially since it allows my inner curmudgeon out to howl. I’ve been avoiding taking this particular lesson for weeks because I hate what AI is doing to people’s minds, to the planet, to the political economy, and to political life in general. There were two other students today, both in their early thirties (I’d guess). They use Chat GPT every single day both in their work and in their daily lives. There’s no point in fighting this, is there.

My First Computer Build

I’ve always wanted to build my own computer. My transition to semi-retirement seemed a good opportunity to do this, especially with the uncertainty over future computer part pricing because of the tariffs. After a couple of months of researching computer part capabilities and compatibilities, I ordered lots of different parts on 2 May 2025 and worked on the build between 11 May and 16 May. I’d describe it as a midrange desktop computer. Here are some of the technical specs:

• It is a microATX format factor build, and the case is a Lian Li A3
• The processor is a AMD Ryzen 5 9600x
• It has a MSI Nvidia GeForce 3060 graphics card with 12 GB of video memory
• I put in 64 GB of RAM, and for storage it has both a 500 GB and 2 TB SSD drive
• It’s running Linux Mint 23.1 XFCE

I’m very happy with how the project turned out. I would definitely build another, now that I understand the process. But I’m not sure when I will need to! I anticipate this computer will last a long time, and a major reason to build one’s one computer is that if you can build your own computer, you can repair it too. It’s satisfying to get away from electronic devices that are sealed black boxes, with no ability to tinker with them or fix things if a part fails.