Every day for more than six years, somewhere over the Arctic or the Mediterranean, a handful of American B-52s were flying with thermonuclear bombs in their bomb bays. They were not on exercise and they were not going anywhere in particular. They were simply there, refuelling in mid-air and flying long loops around the edge of the Soviet Union’s reach, so that no surprise attack could ever catch all of America’s bombers on the ground.
This was Operation Chrome Dome, the best-known of Strategic Air Command’s airborne alert programmes. From November 1961 until January 1968, it kept a standing force of nuclear-armed B-52 Stratofortresses in the air around the clock. It was expensive, exhausting and, as it turned out, risky. It was also one of the most extraordinary sustained flying operations of the Cold War.
Informations clés
- Opération: Chrome Dome, Strategic Air Command airborne alert
- Dates : November 1961 to 22 January 1968; airborne alert trials from 1958
- Aéronef: Nuclear-armed B-52 bombers, refuelled by KC-135 tankers
- Normal level: 12 B-52 sorties a day on a northern and a southern route; down to four airborne alert aircraft by 1966
- Cuban Missile Crisis: Up to 75 launches a day; 2,088 sorties and 41,168 flying hours, 22 October to 21 November 1962
- Architect: Gen. Thomas S. Power, SAC commander 1957 to 1964
- End: Terminated after the B-52 crash near Thule, Greenland, on 21 January 1968
The fear that put bombers in the sky
The idea grew out of the shock of Sputnik. After the Soviet Union launched its first satellites in 1957, American planners feared that intercontinental ballistic missiles might one day destroy SAC’s bombers before they could even take off. Gen. Curtis LeMay had already pushed SAC to keep part of its force on 15-minute ground alert. His successor, Gen. Thomas S. Power, wanted more: some bombers armed and airborne 24 hours a day.
Power, a bomber pilot who had flown B-24s from North Africa and B-29s in the Pacific, commanded SAC from July 1957 to November 1964. His logic was brutal and simple. If a share of the bomber force was always in the air, no first strike could destroy all of it, and the Soviet Union could never be sure of escaping retaliation.

A pilot programme began in 1958, with one bomb wing launching a combat-ready B-52 every six hours. Power announced the airborne alert publicly in January 1961, and by early that year, according to Air & Space Forces Magazine, more than 6,000 airborne alert missions had been flown under a variety of code names. Through 1961 SAC ran a series of “indoctrination” operations named Cover All, Clear Road, Keen Axe and Wire Brush, each built around 12 bomber sorties a day along “ladder” routes up into the Canadian Arctic.
A declassified 1960 US Air Force film on the SAC command post and the early airborne alert (Association of Air Force Missileers).
Two routes and a dozen bombers a day
Those ladder routes soon became congested, and planners worried that adding more bombers would compromise flight safety. Chrome Dome was the fix. Approved by the Department of Defense and launched in November 1961, it replaced the ladders with two routes: a northern one that circled Canada, and a southern one that crossed the Atlantic to the western Mediterranean.
Twelve B-52 sorties a day flew the two routes. KC-135 tankers operating from the northeastern United States, Alaska and Spain, including Morón Air Base, kept them topped up. Two of the twelve had a special job: they orbited near Thule in Greenland to keep watch on the Ballistic Missile Early Warning System radar there, which was thought to be near the top of the Soviet target list. If it went silent, SAC wanted to know why.

A unit history from late 1964 shows what a typical northern mission looked like. B-52Ds of the 494th Bombardment Wing took off from Sheppard Air Force Base in Texas, each armed with four B28 thermonuclear bombs. They flew across the United States to New England, refuelled over the Atlantic, headed north past Newfoundland and over Baffin Bay towards Thule, crossed the Canadian Arctic islands, refuelled again near Alaska and flew home.
Twenty-four hours in a B-52
The missions lasted around 24 hours in a cramped bomber. Crews carried bombs with all the codes and procedures needed to arm and release them, and they flew the same long racetracks again and again. Some crews took an extra pilot along to share the load. SAC did not hide the programme. It advertised it as deterrence, and the press was allowed to talk to the crews.
That publicity was the point. A deterrent only works if the other side knows about it, and SAC wanted Moscow to understand that some of its bombers were always already airborne, beyond the reach of any surprise attack.
Cuba: the day the dial went to one-eighth
Chrome Dome was designed to scale up fast, and in October 1962 it did. On 22 October, at the start of the Cuban Missile Crisis, Power raised the airborne alert to one-eighth of the bomber force for the first and only time. Initially 66 B-52s launched every day, 28 on the northern route and 36 on the southern; by 5 November the figure was 75. SAC even authorised B-52s to continue their sorties with an engine shut down.
Restored-colour 1962 film footage of nuclear-armed B-52s on high alert (ZenosWarbirds).
The surge lasted until 21 November, almost 30 days. In that month SAC launched 2,088 B-52 sorties, every one carrying multiple thermonuclear bombs, and logged 41,168 flying hours. At peak, about 65 aircraft were in position to strike at any moment. In December, President John F. Kennedy presented Power with a flight safety award, because no significant accidents had occurred during the surge.

In Moscow, Nikita Khrushchev noticed. He later wrote about the airborne bombers with a figure higher than SAC’s own one-eighth peak, which is precisely the kind of impression deterrence is meant to leave.
Winding down, and the end at Thule
Chrome Dome was never the only airborne alert. It ran alongside other, more temporary programmes with names like Hard Head, Round Robin and Butterknife. But it was the longest-running and the best known, partly because several of the US Air Force’s most serious nuclear weapons accidents were linked to airborne alert flying, from the Goldsboro crash during Cover All in 1961 to the mid-air collision with a tanker over Palomares, Espagne, in January 1966.
By the time of Palomares the programme had already shrunk. Larger Minuteman missile forces and better early warning had changed the surprise-attack calculations, and Air & Space Forces Magazine reports that Chrome Dome was down to four airborne alert aircraft. The risk, however, remained.

The end came on 21 January 1968. A B-52 flying the Thule monitor mission caught fire, and its crew bailed out over the Greenland ice before the bomber crashed near the base with four hydrogen bombs aboard. Six of the seven crew survived, and Afterburner told the full story in Thule 1968. Greenland belonged to Denmark, which had a nuclear-free policy. Chrome Dome was terminated the next morning, 22 January 1968.
What Chrome Dome left behind
From 1968 on, SAC’s bombers stood alert on the ground instead. The bomber remained one leg of the nuclear triad, while the growing Minuteman force carried more of the burden of surviving a surprise attack. The days of continuous airborne nuclear alert were over.
Chrome Dome also seeped into popular culture. Films such as Dr. Strangelove et Fail-Safe, both released in 1964, imagined nuclear bombers on exactly this kind of patrol receiving an order they should never have received. In real life, the order never came. For more than six years, nuclear-armed B-52s flew to the edge of the map every day, turned around and flew home, and that was the whole idea.
Historiespanarna’s overview of Chrome Dome and the B-52’s round-the-clock nuclear deterrence mission.
Sources: Air & Space Forces Magazine (“The Perils of Chrome Dome”, 2011), History of the 494th Bombardment Wing (Heavy), October-December 1964, Air Force Historical Research Agency, Canada Department of National Defence, Time
Header photo: US Air Force via Wikimedia Commons, public domain




0 Comments