Read Command and Control Online

Authors: Eric Schlosser

Command and Control (52 page)

BOOK: Command and Control
4.01Mb size Format: txt, pdf, ePub
ads

After the B-52 crash near Cumberland, Maryland, an Air Force EOD team started to remove the weapons from the wreckage of the plane, using improvised heavy machinery—until a representative from Sandia intervened and asked them to stop. The bombs weren't moved until their condition had been assessed. A naval bomb disposal team began to disassemble the Mark 28 bomb recovered from the ocean near Palomares—until another Sandia nuclear safety specialist made clear that a ship, rolling over swells, might not be the best place for the task. Peurifoy and Stevens thought that, most of the time, there was no need to rush. “Don't move someone who's hurt before you know the extent of the injuries,” a basic rule of first aid, also applied to nuclear weapons. Ease of disassembly had never been a top priority among weapon designers. In fact, it was rarely considered when weapons were on the drawing board. Inside the metal casing, parts were tightly welded or glued together. If you weren't careful, thermal batteries could be ignited, high explosives set off. Peurifoy took an EOD course and gained tremendous respect for the soldiers and airmen who put on bomb suits to render bombs safe. They were fearless. But the weapons they typically handled might kill them and injure people within about a quarter of a mile. Peurifoy didn't want anyone to feel hurried or gung ho while trying to dismantle a thermonuclear warhead.

The need to retrofit and retire older weapons in the stockpile became more urgent after a discovery about the Mark 28 hydrogen bomb.
Stan Spray found that one of the bomb's internal cables was located too close to its skin. If the weapon was exposed to prolonged heat, the insulation of the cable would degrade—and the wires inside it could short circuit. One of those wires was connected to the ready/safe switch, another to the thermal battery that charged the X-unit. It was a serious problem. The heat from a fire could arm a Mark 28 bomb, ignite its thermal battery, charge its
X-unit, and then fully detonate the high explosives. Depending on the particular model of the Mark 28, a blast of anywhere from 70 kilotons to 1.5 megatons would immediately follow.

The problem with the Mark 28 was more significant than the safety flaws in other weapons. Mark 28 bombs were routinely carried by B-52 bombers on ground alert. And those B-52s sometimes caught on fire, even when they never left the ground. The bomber carried more than 300,000 pounds of highly flammable JP-4 jet fuel, a mix of gasoline and kerosene. In preparation for a typical B-52 flight, the crew would spend at least an hour in the plane, going through checklists, before starting the engines—and then the engines would be started one after another, until all eight were running. It could take an hour and a half for the pilot to get a B-52 into the air. But planes on ground alert were expected to be airborne within ten or fifteen minutes, the maximum time available for a “
base escape.” Explosive cartridges on the four engine pods would be detonated by the copilot, as soon as he climbed into the plane, spinning the turbines rapidly and starting all eight engines in about a minute. A “cartridge start” was a memorable sight—a series of small explosions, B-52s filling the runway with clouds of smoke—and crews on ground alert practiced it regularly. And yet it could also start a fire.

The combination of Mark 28 bombs and B-52 bombers on alert was increasingly dangerous. Peurifoy doubted it was worth the risk. Both were aging weapon systems; many of the B-52s were older than their pilots. And most of the planes would probably never reach their targets, let alone return safely from a mission. After a 1975 briefing on the role of the Strategic Air Command's bombers in executing the SIOP, the head of the CIA, William Colby, expressed surprise that “
our B-52s are planned for one-way missions.” Once an emergency war order was transmitted, the bombers on ground alert would quickly take off from their bases in the United States, fly eight to ten hours toward Soviet targets—and find what? The Soviet Union would have already been hit by thousands of warheads delivered by American missiles. Targets that hadn't been destroyed were likely to be surrounded by antiaircraft missiles, and dust clouds of unimaginable scale would blanket the landscape. Each B-52 was assigned a poststrike base in
Europe or the Middle East where it was supposed to land, refuel, and pick up more nuclear weapons for another run at the Soviets. Would any of those bases still exist, if bombers somehow managed to survive their first passage through Soviet airspace? Most B-52 crews didn't count on it.

Stan Spray added components from the Mark 28 bomb to his Burned Board briefing, along with a dramatic flourish: when the bomb's wires short-circuited, a flashbulb went off. The briefing was given to hundreds of officials—with little immediate effect.
A study of all the nuclear weapons in the American arsenal was completed by one of Peurifoy's deputies in 1977. It provided the Department of Defense with a list of the weapons posing the greatest threat and a timetable for retiring them or improving their safety.
The Mark 28 bomb was at the top of the list, followed by the W-25 warhead of the Genie antiaircraft missile. Despite being the oldest sealed-pit weapon in the stockpile, vulnerable to lightning, and fitted with an outdated accelerometer, the Genie was still being loaded onto fighter planes. On the list of weapons requiring urgent attention, the only strategic warhead was the W-53 atop the Titan II missile. It needed
a “retrofit for Enhanced Electrical Safety.”

In 1979 the Department of Defense finally accepted some of the recommendations that Sandia's safety department had been making for years—but didn't want to pay for them. The Pentagon agreed to schedule retrofits of weapons like the Mark 28, so long as the cost wouldn't interfere with the acquisition of new weapons. And until the funds were obtained, the Mark 28 could still be carried by B-52s on ground alert. Although the Air Force balked at devoting a few hundred million dollars to improve the safety of hydrogen bombs,
it planned to spend at least $10 billion to equip B-52s with cruise missiles. Instead of trying to penetrate Soviet airspace, the bombers would launch cruise missiles a thousand miles from their targets, turn around, and come home. Until those cruise missiles were available, B-52s were loaded with Short-Range Attack Missiles (SRAMs), carried in a rotary rack. It turned as each missile was fired, like the cylinder of a revolver shooting bullets. The SRAMs were designed to fly a hundred miles or so, destroy Soviet air defenses, and give the B-52 a better chance of
reaching its target. The missiles had a destructive force of as much as 200 kilotons, and a single B-52 could carry a dozen of them.

Peurifoy was frustrated by the delays. Even the retrofit of the Mark 28, top on the list, kept getting pushed back. Through a friend in the Air Force, Peurifoy arranged for General Howard W. Leaf to visit Sandia on June 13, 1980. Leaf would be given the Burned Board briefing. The safety problems with the Mark 28 would be outlined in detail, as well as the history of nuclear weapon accidents and the development of weak link/strong link devices. Leaf had an important job, inspector general of the Air Force, with the authority to cut through red tape. The false alarm caused by a faulty computer chip at NORAD, ten days earlier, had brought renewed attention to the importance of command and control, the limits of technology, the risks of human error. After lengthy meetings at Sandia, General Leaf returned to Washington, D.C.—and commissioned another study on the safety of the Mark 28 bomb.

•   •   •

O
N
S
EPTEMBER
15, 1980,
Jeffrey A. Zink was pulling an alert at Grand Forks Air Force Base in North Dakota. Zink was the navigator of a B-52. Once a month he and the rest of his crew would sleep in a building at the end of a runway, with a tunnel leading to their plane. Four or five other B-52 crews would stay there, too, along with the crews of their tankers. In some respects it felt like being confined in a prison. The alert quarters were surrounded by concertina wire, motion detectors, and security police carrying M-16s. Zink and his friends spent most of their time being bored. They would eat, sleep, read books, take naps, watch crap like
The Love Boat
on TV. But Zink always thought boredom, in this case, was good. Boredom meant that deterrence still worked. So long as these fifty young men were stuck there doing nothing, America's nuclear strategy was a success. About once a week, however, the Klaxons would sound, and life would suddenly become more interesting.

Zink had never intended to join the Air Force. In the mid-1970s he was a long-haired, true-blue hippie attending the University of Pittsburgh and
planning to go to law school. One day he walked into an Air Force recruiter's office, thinking it would be cool to fly planes. The recruiter told Zink that his eyes weren't good enough to become a pilot—but he could become a navigator. Zink put aside law school and joined the Air Force in 1977, right after graduation. His hippie girlfriend was stunned, and their relationship soon ended. At first, Zink didn't fit into the tough, regimented culture of the Strategic Air Command. “
What have I gotten myself into?” he wondered. “I don't think I like these people.” But his feelings gradually changed, and he eventually became a lieutenant colonel.

The navigator of a B-52 sat at a desktop in the “chin” of the plane, a lower level beneath the pilot. Beside the navigator sat the bombardier. They both had ejection seats that fired downward. Their compartment was small, cramped, and windowless, with a ceiling about five feet high. Training flights lasted six to eleven hours, and they could be rough. The eight engines were so loud that the navigator and the bombardier, seated a foot or two from each other, couldn't shout loud enough to have a conversation. They had to speak on the intercom. And most of the time they'd wear earplugs. The B-52 had originally been designed to attack the Soviet Union at an altitude of about 50,000 feet. But Soviet air defenses now forced the bomber to approach at a low altitude—very low. For three to four hours during a training flight, Zink's plane would fly 150 to 350 feet off the ground. At that altitude, especially in the summer months, the air turbulence was terrible. The hot sun would send thermals of air swirling upward from the ground. Sitting in his little windowless compartment, getting bounced so hard that things would slide off the desk, Zink often felt airsick. But he also felt too busy to get sick. “
I'll throw up later,” he'd tell himself. “I have too much to do right now.”

The navigator would be in constant communication with the pilot, warning of the terrain that was approaching. The B-52's navigational tools were rudimentary. Its avionics still relied on vacuum tubes, instead of integrated circuits, and data was entered into the bombing computer with IBM punch cards. At low altitudes, the B-52 was an extraordinary sight, a huge plane with a wingspan about sixty yards wide, hugging the terrain, casting a long shadow, traveling seven or eight miles a minute. Zink's crew often
flew through the Rocky Mountains, and the one time that Zink sat in the cockpit, it was fun to watch the pilot bank around hills and drop into alpine valleys. But sitting down below, without any frame of reference other than his radar screen, the experience could be terrifying. On more than one nighttime flight, Zink thought, “
we're going to die,” as the pilot ignored his warning that a mountain was dead ahead and waited an extra moment to climb.

During low-altitude practice runs, Zink's crew would radar bomb targets throughout the American West, hitting SAC radar huts in places like Sheridan, Wyoming; Bismarck, North Dakota; and La Junta, Colorado. And before a training mission ended, the pilot would spend an hour or two doing “pattern work,” landing the plane, rolling down the runway, and then taking off again. Zink found these touch-and-go landings even harder to endure than heavy turbulence. At the end of every training flight, he felt like someone had just pummeled him for hours.

The Klaxons sounded about once a week during ground alerts. The drills were supposed to be “no-notice” and come as a total surprise. But by the late 1970s, SAC was taking some precautions. Whenever Zink and his buddies saw three fire trucks and the wing commander's car park on the alert pad, they'd know a drill was about to begin. They'd stand in the tunnel, waiting, making bets on how many seconds would pass before the Klaxons went off. And then they'd run to their planes. As navigator, Zink would decode the message from SAC headquarters. It usually called for an engine start or a “mover,” an exercise that involved taxiing the bomber to the end of the runway, turning around, and returning to the alert pad. Once the drills were completed, the crew would spend about three hours reconfiguring the plane for the next alert.

A few months earlier, during the first week of June, Zink had been fast asleep at about twelve thirty in the morning when the Klaxons sounded. He jumped out of bed, looked out the window—and didn't see any fire trucks or the wing commander's car. He and the bombardier thought, “
Oh my God, it's the real thing.” Drills were never held late at night. Hearts pounding, they ran to the plane. Zink decoded the message and felt profoundly relieved that it didn't contain an emergency war order. The whole
episode felt strange, and it wasn't until weeks later that they learned NORAD had experienced a false alarm. The gunner on Zink's crew, a young staff sergeant, was so shaken by the experience that he quit the Air Force. All of a sudden, the meaning of their wartime mission had become clear, and he realized, “
I can't do this.” Zink believed strongly in the value of nuclear deterrence and tried not to dwell on what would happen if deterrence failed. He knew that any attack on the Soviet Union by his crew would be not only murderous but suicidal. And yet he never thought about those things while crawling around the Mark 28s and Short-Range Attack Missiles in the bomb bay, checking their serial numbers before an alert.

Zink and his crew were expecting the drill on September 15,
1980. It was about eight thirty in the evening, and out the window you could see the fire trucks and the wing commander's car. The Klaxons sounded. They ran to the plane. Zink put on his headphones and turned the crew volume low, so he could hear the code from SAC headquarters over the radio.

BOOK: Command and Control
4.01Mb size Format: txt, pdf, ePub
ads

Other books

Private Message by Torella, Danielle
Seducing the Demon by Erica Jong
The North Water by Ian McGuire
Couples by John Updike
Landslayer's Law by Tom Deitz
A Rebel Without a Rogue by Bliss Bennet
Damian by Jessica Wood
Death in a Summer Colony by Aaron Stander
The Shop on Blossom Street by Debbie Macomber