Visiting the B-2 at home in Knob Noster, MO

So, what do I know about the B-2? 

I interviewed enlisted men and officers during three visits to the B-2 base at Whiteman AFB, beginning in 1999. All the trips were for articles that appeared in Air&Space Smithsonian Magazine. 

On those visits I took a seat in the co-pilot's position, spent an hour in the Mission Planning Cell, flew in the simulator with a B-2 pilot, watched Airmen loading a bunker-buster into the bomb-loading trainer, and interviewed aircraft maintainers while walking with an escort around the hangar. I also interviewed experts on stealth operations outside the Air Force. 

Why is the B-2 based near Knob Noster in rural Missouri, rather than a bigger base near one of the coasts? I've seen this question a lot on discussion boards. It's because missions might be executed anywhere in the world. So there's no location better than any other. From the first, the aircraft was set up to fly halfway across the world and back with refueling. As they did with Minuteman missile basing, war planners apparently preferred the central US as providing something of a defensive and security buffer. A buffer is not a bad idea, given that the Pentagon has long been concerned about ballistic missiles that could be launched from hostile submarines lurking off our coastline. See my post on the history of DEFCON alerts.

The base originated with a World War II training airfield. It was later named Whiteman after 2nd Lt. George Whiteman, who was killed in action during the Pearl Harbor attack. I met his brother on one of my visits.

What's the B-2 like, close up? Numerous articles have described the flight deck, with its cramped quarters and a small rectangular space behind the seats so one pilot can get some rest. Only two people are allowed on board, even for VIP flights; that's because the plane has only two ejection seats. I don't have much to add to what's been printed, other than the hot-dog warmer that I saw has been replaced with a microwave. 

But I haven't seen material in the news about a walk-around in the hangar, so here goes.

Senior Airman Parker J. McCauley

     Credit: Senior Airman Parker J. McCauley

When I visited (under close escort, of course!)  the hangar was as spotless as a high-end auto showroom, with not a spot of fluid on the glossy painted floor. The plane has a huge wingspan (172 feet) but it's hard to appreciate that from a few feet away. The radar-absorbent skin is extremely smooth, marked by occasional outlines of hatchways and access doors. Some of these doors are for navigation antennas, for use in civilian skies. Northrop Grumman had to be extremely careful with the fit and finish of all these doors and hatches, since exposed metal edges are visible on radar from miles away. I was told that crewmen wear gloves whenever they might come into contact with the edges. 

If the B-2 is so stealthy, why the need for a decoy flight to Guam before the attack on Iranian nuclear-development sites? The B-2 design is 35 years old, so even with upgrades, it's more vulnerable to state-of-art radar than when first used in combat. And the USAF never regarded it as “invisible” to radar, even from the first. The best way to describe a successful flight into enemy territory is that a B-2 shows up only as “faint and intermittent” on enemy radar. See below on how mission planners use the latest airspace info to achieve this. 

While the B-2 is intended for early strikes, the USAF never uses it as a “first-night” aircraft if any opposition from late-model anti-aircraft equipment or fighter aircraft can be expected. As used in Kosovo, Iraq, Libya, and lately in Iran, the B-2 followed initial sorties by less-stealthy aircraft using bombs and missiles to destroy AA radar installations, fighter bases, communication links, and command and control centers. 

How much work goes into setting up a bombing mission? A great deal, in part because of the large number of supporting aircraft (like tankers, fighters, missile-carrying aircraft) required. As far as the B-2 itself, the Blue Line is a key part of stealth planning, and those tactics are just as vital as the airplane’s design and the materials that reduce its radar cross-section. Uniquely crafted and continually updated in Whiteman's Mission Planning Cell, the Blue Line marks the flight path to assigned targets. Here's a link to one of my Air&Space articles that goes into more detail on that critical task. Rarely a straight line, the Blue Line maps out zigs and zags to avoid the most dangerous enemy defenses. One of the mission planners explained it to me this way: the B-2 should show up very faintly on radar screens, and sometimes won't be visible at all. 

Stealth-wise, B-2 mission planners have several things besides radar to worry about. The planes have to be refueled every six hours, or more often depending on conditions, so that means a B-2-aware enemy will be watching for distant tankers, which are not stealthy. Another weak spot is the engine exhaust. Because the four engines dump their exhaust on top of the fuselage, rather than the usual locations on warplanes (below or behind), the B-2 is less visible in infrared when viewed from below. But that also means a high-flying interceptor with heat detection might spot it from above. I'm also told that stealthy aircraft are vulnerable to detection by reflected AM radio signals. While this wouldn't be sufficient for AA targeting, it might narrow the search for an interceptor. 

Which are the most demanding portions of a mission? Refuelings require a lot of attention ...

     Credit: U.S. Air Force / Master Sgt. Val Gempis

... as does in-flight monitoring by the pilots of the threat picture; this task is called ISR, for intelligence, surveillance and reconnaissance. The commander of the 509th Bomb Wing described it to me this way: the pilots have “been transformed from stick-and-rudder pilots to system operators.” What would also be difficult is a change in targeting or the Blue Line, while in flight. 

Starting a Substack: On the Machine Frontier

This is the Substack link. 

Here's what I mean by the Machine Frontier, a concept that was central to my book on technological catastrophes, Inviting Disaster.

An English dictionary of 1721 defined frontier as “the Limits or Borders of a Country or Province.” In the US, the word came to mean an unsettled wilderness that was ripe for exploitation by restless – sometimes reckless – entrepreneurs.

America's geographical western frontier has long vanished, but I see similar dynamics along the machine frontier: a mix of danger and opportunity that offers innovators new, sometimes dramatic, gains. But building out such niches brings a higher risk of error, since safe and reliable methods have not been established.

My posts, then, will highlight cases where new tech needed new thinking. 

Consider what happened in January 1969 at the Hungarian Carbonic Acid Producing Company, at Répcelak, Hungary. The company was in the business of removing CO2 from natural gas and selling it. The liquid was stored in small cylinders as well as in four big storage tanks, cooled by ammonia refrigeration. The gas arrived at the plant with traces of water in it that had to be removed. On occasion this stray water caused gauges, fittings, level indicators, and even safety valves to freeze shut. But the plant kept running.

On December 31, 1968, the plant shut down with the indicators showing at least twenty tons of liquid COz in each tank. The plant opened again late on the night of January 1. Running short of cylinders to store the liquid CO2, operators directed the flow into storage tank C, which was supposed to have plenty of capacity. About a half hour later tank C exploded, and its fragments blew apart tank D.

The twin explosions killed four people nearby and ripped tank A from its foundation bolts, tearing a hole about a foot across. In escaping furiously through the new opening, the pressurized, liquid COz acted like a rocket propellant. Tank A took off under the thrust, crashing through a wall into the plant laboratory, dumping out tons of liquid CO2 across the floor, and instantly freezing five people where they stood.

The deluge left the room at a temperature of -108°F, starved of breathable air, and covered with a thick layer of dry ice.

While popular history tends to focus on seemingly overnight successes, over the long haul the greatest rewards on the machine frontier will go to innovators who proceed on solid facts and exhaustive testing. When experiments are unsatisfactory, they correct and move forward. If that means scrapping a design and starting over with a clean sheet, that's what they do.

One use for AI: Keeping an eye out for forestry hazards

I visited my brothers' tree farm in Missouri last week, in time to help clear storm damage by operating their Cat skidsteer. Storm: as in a likely F1 tornado in early May that toppled many dozens of big trees on their property. First priority was to open the roads, followed by salvaging hardwood saw logs. 

This is me climbing into the cab after chaining a log onto the road, taking care not to trip on the grapple. Tripping here would be a good way to break a leg. 

Here's how their road looked before being fully cleared: A tangle similar to what big woods loggers called "slash." The biggest logs of white oak and walnut were close to three feet in diameter, disease-free and more than 150 years old. 

But logs weighing a ton or two aren't easy to salvage in this location. This was a steep hillside, dense with brush and rock outcrops. The cut log below reflects the slope angle. 

Note the tangled nature of the downed trees. My brothers have years of experience with chain saws and their risks, but commented that clearing trees in this setting poses a bigger danger than the saws themselves. And it can be hard to monitor those dangers, which make logging one of the highest-injury jobs in the country.

Consider that when cutting a log, the operator at the Stihl is watching the saw-cut closely, wary of several things. Often a fallen log requires an undercut, bringing the bar close to chain-damaging rocks. More pressing: is the log under a force that will send something rolling or flying when cut? Will it settle and bind the bar, or worse, catch the tip of the bar, flipping the saw backward?  

Given the need to pay attention at close range, it can be hard to see what might threaten from above or from a few yards to the side. 

Overwatch could be a useful job for an AI- and LIDAR-equipped phone once those are capable of real-time visual processing. Such a tripod-mounted phone could warn about initial shifting of what loggers call a widow-maker, a broken tree that's hung up on a standing tree, and ready to fall during logging operations. With knowledge of tree physics, it could warn that a branch has come under terrific compression and will lash out when cut. 

A person could do this job, but in my limited experience with small-scale logging, there's so much to do that nobody's available to do the overwatch job, however important.