What's new

The nuclear nightmare of Savage Mountain: when a B-52 crashed... with two nukes

SvenSvensonov

PROFESSIONAL
Joined
Oct 15, 2014
Messages
1,617
Reaction score
207
Country
United States
Location
Sweden
Savage-Mountain.jpg


0138 (Local) Romeo Time Zone (UTC-5:00). 13 January, 1964. USAF B-52D Stratofortress Callsign “Buzz 14”, Flight Level 295 over Savage Mountain, Maryland.


Major Tom McCormick, USAF, can barely see.

Whiteout conditions and buffeting winds at 29,500 feet are so bad he radios Cleveland Air Route Traffic Control Center (ZOB) for clearance to change altitude to flight level 330, or 33,000 feet. He is trying to get his B-52 bomber above the freak winter blizzard.

“Cleveland Control, this is Air Force Buzz one-four, request climb to level three-three-zero. Weather, over…”

“Roger Buzz one-four, this is Cleveland Control. Ahhh… Please stand by.”

As with the tragic crash of the AirAsia Airbus A320 flight QZ8501 over the Java Sea two weeks ago McCormick’s big bomber must find clean, stable air or risk breaking up, stalling and falling out of the sky. But unlike an airliner over turbulent seas McCormick’s two passengers are far more crucial. And deadly.

B-53_nuclear_bomb-706x469.jpg


Buzz 14 is carrying two live, 9 mega-ton B53 thermonuclear bombs. They are among the largest nuclear bombs in the U.S. arsenal. This warhead also rides atop the giant Titan II ICBM, a ballistic missile designed for smashing secret Soviet underground installations and wiping out Russian cities. And Buzz 14 is carrying them over the eastern United States.

McCormick has another concern. His nuke-bloated bomber was diverted to the place this flight took off from after its original crew reported… a technical problem. The mission started as part of the Chrome Dome nuclear-armed airborne alert patrol but was forced to land at Westover AFB in Massachusetts because of an in-flight emergency, in this case, an engine failure. After the in-flight diversion the nuclear warheads were not off-loaded.

Problems with the B-52 are not new. Three days earlier a structural problem with another B-52H, aircraft number 61-0023,resulted in a famous incident when its vertical stabilizer completely fell off. Since the aircraft was able to find relatively calm conditions after the extreme turbulence where the accident happened, it managed to land safely. A famous photo of the plane still in flight with its tail completely gone is one of the most widely viewed of the B-52 bomber.

B-52-no-tail.jpg


Right now Buzz 14 needs to find relatively calm air too. If it has another engine failure or losses its tail in this blizzard it will not be as lucky as 61-0023 was three days before.

And 61-0023 didn’t have live nukes on board.

McCormick abandons his experienced, light grip of the Stratofortress control wheel for the authoritative hand of a man trying to tame a machine bucking out of control. The rudder pedals are kicking back; wild swings of the wheel seem to have no affect on the aircraft’s flight attitude. Trying to keep the giant Stratofortress in level flight in the howling frozen sky is like arm wrestling an abominable snowman.

Then suddenly… nothing.

The pedals go light. The control links to the rudder are severed. The aircraft pivots. Yawing. Snaking wildly, first one side, then skidding back the other way on the frozen air in the blinding snow squall. McCormick and his co-pilot Capt. Parker Peedin are expert bomber pilots. They try to use ailerons to stabilize the giant bomber. But there is no solid purchase in the icy maelstrom outside. The B-52 becomes a giant, nuclear-armed Frisbee, entering a flat spin and departing controlled flight.

Five miles above the ground Buzz 14 rolls on its back in the driving blizzard, its last fatal surrender.

Ejection seats in the B-52 work when miniature thrusters blow hatches off the aircraft, resulting in rapid decompression of the cockpit and a howl of arctic air at near supersonic speed that is so cold the wind chill is impossible to calculate at 500 M.P.H. The navigator and radar operators’ seats eject downward… when the plane is right side up. But Buzz 14 is upside down now. And losing altitude fast.

B-52-crew-positions-706x465.jpg


The B-52 half-rolls again, this time near level attitude. The crewmembers reach for their ejection seat handles. Explosive fasteners in the crew hatches detonate when the pilot orders, “Eject, eject, eject…” over the intercom.

The pilot, Maj. Tom McCormick, co-pilot, Capt. Parker Peedin, navigator, Major Robert Lee Payne and tail gunner Tech Sgt. Melvin E. Wooten all managed to actuate their ejection seats and egress the aircraft into the black, freezing sky. Presumably, alive.

Major Robert Townley may have been pinned inside the B-52 by G-forces as the crash accelerated out of control and he struggled with his parachute harness, his ejection seat may have malfunctioned or he may have been knocked unconscious in the bone-breaking turbulence. He never got out. His body was discovered days later in the wreckage.

But the most critical survivors, at least to national security, are the pair of live B53 nuclear bombs. They ride the plane into the ground. Where two of the deadliest weapons known to man will lie unattended and unguarded.

For almost a day.

This is where the story could fly off the non-fiction shelf and onto the pages of a Clancy, MacLean or Fleming novel. All three authors started stories like this; Ice Station Zebra, Thunderball, The Sum of All Fears. Ian Fleming’s novelThunderball was published in 1961, three years before the Buzz 14 crash. The film adaptation of Thunderball was released in 1964, a year after the Buzz 14 incident. Fiction that recounts the horror of a nuclear weapon or critical national security asset lost, something that has actually happened more frequently than you care to imagine. A few have never been recovered.

But in this instance the weapons are found. Not entirely safe, but “…relatively intact…” according to the Air Force. It’s a scary sounding moderation to describe radioactive A-bombs lying around in the woods of the Eastern U.S. unattended. The bombs come to rest on the placid Stonewall Green Farm.

Pilot Maj. Thomas McCormick survived the ejection and landed in relatively good condition. He reported seeing lights on the ground during his parachute descent and was found by a local resident who drove him to the Tomlinson Inn on National Road near Grantsville where he reported the crash by phone.

Co-pilot Capt. Parker Peedin also survived, but went through a 36-hour survival ordeal in the harsh winter conditions before being found. The rest of the crew, radar bombardier Maj. Robert J. Townley; the navigator, Maj. Robert Lee Payne and tail gunner, TSgt. Melvin F. Wooten did not survive.

[Read also: On this day in 1968 a B-52 crashed in Greenland with 4 hydrogen bombs]

There are some… potentially disturbing… inconsistencies about the reports on the crash of Buzz 14.

Buzz 14 pilot in command USAF Major Thomas McCormick would report after the crash that, “I encountered extreme turbulence, the aircraft became uncontrollable and I ordered the crew to bail out,” he said. “I then bailed out myself after I was sure that the other crew members had bailed out.” [emphasis added]. But Major Robert Townley did not get out of Buzz 14. One account even suggests that the aircraft navigator, Major Robert Lee Payne, seated next to Townley in theB-52, may have attempted to assist Townley in refastening his parachute harness after a bathroom break inside the aircraft. If he did, we’ll never know. Major Payne died of “exposure” after the crash.

The official Air Force account suggests the B-52 was at 29,500 feet at the time of its first radio call to Cleveland Air Traffic Control and the crew requested a climb to 33,000 feet to get above the bad weather. To most pilots this makes sense. Other news accounts, including The Baltimore Sun newspaper corroborate this flight profile.

An account by journalist David Wood of the Newhouse News Service appears to quote actual radio transcripts from the crash. Wood’s report says the B-52 crew requested a descent from 33,000 ft to 29,500 ft. Why? Also, Wood’s account mentions the crew used their Air Force call sign with civilian air traffic control, a seemingly unusual practice for a bomber carrying live nuclear weapons. Today nuclear armed aircraft like B-2 Spirit stealth bombers transiting civilian airspace may use an alias call sign to avoid detection by civilian listeners on ATC radio scanners. Recently a failure to use (alias) civilian call signs resulted in civilians monitoring the flight data of B-2’s on their way to bomb Libya, a serious security breach.

A search of ATC contacts for the region surrounding the crash site indicates that, while Cleveland ATC center is repeatedly mentioned as the air traffic control center in contact with Buzz 14, the Washington Air Route Traffic Control Center (ZDC) is actually closer to the area where the crash occurred and listed by several resources as the center controlling air traffic in the region of Buzz 14’s crash. Why was Buzz 14 using Cleveland Center ATC instead?

Details about the retrieval of the weapons themselves are sketchy. E. Harland Upole Jr., a retired state parks veteran, told the The Baltimore Sun that he located the crash site and the bombs. Upole’s account said the bombs’ “…insulation was torn off”.

Upole went on to report the bombs were “loaded onto a flatbed truck” and driven through the city of Cumberland at 2:30 AM on the way to what is now called the Greater Cumberland Regional Airport.

Another report in The Washington Times dated January 14, 2014 says, “A local excavator was authorized by the military to move the bombs two days after the crash. He used a front-end loader, but first lined it with mattresses from a nearby youth camp – to keep the nukes nice and swaddled, just to be on the safe side.”

A typical large front-end loader, like a Caterpillar 906H2, has a lifting capacity (according to Caterpillar) of “3,483 pounds”. But a B-53 nuclear weapon weighs 8,850 pounds, or more than twice the capacity of a large bulldozer like the Cat 906H2. How were the two nukes moved if they were relatively intact?

And here is another minor wrinkle: The official website for Greater Cumberland Regional says its longest runway is RW 5/23, a 5050-foot long by 150-foot wide grooved asphalt runway. More than one resource says the take-off distance (to clear 50ft.) for a loaded C-130 transport, the most likely aircraft to have retrieved the heavy nuclear bombs from Buzz 14, is 1,573 meters or 5,160 feet. That suggests the main runway at Greater Cumberland Regional is over 100 feet too shortto accommodate a C-130 cargo plane loaded with the two heavy nuclear weapons. The total weight of both bombs would have been over half the maximum weight the C-130 could carry, so presumably a little extra runway may have been nice, especially at night in winter weather.

The crash location is mentioned as “Savage Mountain, Garrett County (near Barton, Maryland) at coordinates 39.565278° North and 79.075833° West. Today Google Earth shows that as an empty farm field. Some news accounts said portions of the crash “were buried” at the crash scene, an unusual sounding practice for a crash of great significance and one that involved nuclear materials.

Is gathering the lose ends of the threads that unravel at the end of this story and weaving them into a Clancy-esque conspiracy tale a reasonable conclusion?

No.

And this is the exact place where fiction departs from non-fiction. But there is one axiom that every good fiction writer knows compared to a non-fiction reporter of actual facts: fiction has to be believable.

memorial.jpg


From The Aviationist » The nuclear nightmare of Savage Mountain: when a B-52 crashed due to turbulence. With two nukes
 
Indeed that must have scared the hell out of American's Army ...

but i have a question here , suppose a plane or bomber carry nukes , get shot or crash landed and destroyed, can it be the cause of Nuclear explosion ?
 
Indeed that must have scared the hell out of American's Army ...

but i have a question here , suppose a plane or bomber carry nukes , get shot or crash landed and destroyed, can it be the cause of Nuclear explosion ?

That depends on whether or not the weapon has been armed and has fallen for the minimum arming distance. Nuclear weapons have a series of safeguards called "Permissive Action Links" - one of which prevents misfires, but others are designed to prevent tampering to foil the misuse of a stolen or lost nuclear weapons. This is the reason the "terrorist nuke" scenario tends to be a bit BS. Some also prevent the weapons crew from going rouge and using the weapon without permission.

I know that on US nuclear weapons an operator has one chance to input the arming sequence into the weapon. If the sequence is incorrectly offered, the electronic arming device will fry itself rendering the weapon inert. Since these are dangerous and destructive systems, they do have safeguards, but all bombs, nuclear or conventional do to prevent accidental detonation.

The Russians tended to be a lot more careless with their weapons. I can't speak for India, Pakistan, North Korea, China, France or the UK though.

So to answer your question more shortly, yes, a downed or crashed bomber can cause a nuclear catastrophe, but only if the weapon is armed and meets the minimum travel distance.

Permissive Action Link - Wikipedia, the free encyclopedia

While this can happen, instances of armed nuclear weapons crashing are rare, though crashed bombers with nuclear weapons and the USAF have a dark history. Here's a few of those accidents.

Fifty-eight years ago, on May 22, 1957, a “broken arrow” rattled Albuquerque, New Mexico, frightening residents and killing one very unlucky cow. Used by the U.S. military, the term refers to a thermonuclear bomb that is accidentally detonated or lost. The Department of Energy has acknowledged more than two dozen such incidents between 1950 and 1980, many of them on U.S. soil.

1. May 22, 1957: Kirtland Air Force Base, New Mexico
Albuquerque residents enjoying a spring day on May 22, 1957, found themselves literally rocked by what felt like a nuclear explosion. They weren’t far off. No one knows precisely what happened aboard the B-36 aircraft transporting a nuclear weapon from Texas to New Mexico that day, but somehow the device fell through the bomb bay doors, plummeting about 1,700 feet into a field south of Kirtland Air Force Base. The conventional explosives detonated, blasting a crater 12 feet deep and 25 feet across. Luckily the nuclear capsule had been separated from the conventional explosives during transport for safety reasons, and that capsule was found intact. The only casualty of the blast? An unfortunate cow grazing nearby.

2. February 5, 1958: Savannah River, Georgia
When a B-47 carrying a nuclear device experienced a midair collision with an F-86 aircraft during a training simulation in February 1958, officials decided to jettison the bomb into the Savannah River. Fortunately, the device’s conventional explosives didn’t detonate when the weapon slid into the water and, as is standard with the nuclear version of a “live fire” exercise, the nuclear capsule wasn’t installed in the weapon. The Air Force searched until mid-April but never located the bomb. Today residents refer to this broken arrow as the Tybee Bomb.

3. March 11, 1958: Florence, South Carolina
In March 1958, as a team of military divers scoured the Savannah River in Georgia for a broken arrow, another one fell in the southeast quadrant of the United States. A B-47E aircraft carrying a thermonuclear weapon took off from South Carolina for an overseas base, accidentally jettisoning it shortly thereafter. The conventional explosives detonated on impact with the ground in a suburban Florence neighborhood, demolishing a house and causing several injuries.

4. November 4, 1958: Dyess Air Force Base, Texas
When a B-47 carrying a nuclear warhead catches fire on takeoff, it’s a problem. That’s what happened when a B-47 left Texas’ Dyess Air Force Base in November 1958 to transport a thermonuclear device to another location. At 1,500 feet it began experiencing trouble. Three of the plane’s crew members ejected safely, but one was killed when the plane subsequently crashed, setting off the bomb’s conventional explosives and blasting a crater 35 feet in diameter and 6 feet deep. All the nuclear components were recovered at the scene.

5. January 24, 1961: Goldsboro, North Carolina
In one of the closest calls in accidental nuclear detonation history, a single safety switch prevented a 20-megaton Mk39 hydrogen bomb from exploding in North Carolina in January 1961. When a B-52 carrying two of the bombs suffered a fuel leak in the wing, the plane exploded and dropped both bombs earthward. The parachute of one bomb deployed, but the other weapon nearly detonated when five of its six safety devices failed and it broke apart upon impact with the ground. While the Air Force recovered the bomb’s plutonium, the thermonuclear stage containing uranium was never found. The Air Force subsequently purchased and fenced off a land easement in the area where officials believe the uranium lies.

6. March 14, 1961: Yuba City, California
In March 1961, a heroic Air Force commander ordered his crew to bail out of a crippled B-52 carrying a pair of thermonuclear devices when the plane’s compartment pressurization system failed at 10,000 feet. The commander stayed aboard to pilot the plane away from populated areas near Yuba City, California, before ejecting to safety at 4,000 feet. The two nuclear weapons aboard the aircraft were torn from the plane when it crashed, but nothing exploded and no radioactive contamination was released.

7. January 17, 1966: Palomares, Spain
It’s pretty hard to cover up the midair explosion of a B-52 carrying four hydrogen bombs when the event is witnessed by hundreds of onlookers. So it came as no surprise to anyone when the Palomares incident, as it has come to be known, hit the front page of the New York Times in January 1966, just three days after the event occurred. During a routine refueling operation over Spain, an American B-52 patrolling on airborne alert was struck by the fuel plane’s boom, which instantly destroyed both planes and killed seven of the 11 total crew members. Two of the B-52′s bombs exploded on impact with the ground near the village of Palomares, contaminating approximately 1 square mile with radioactive plutonium. Another bomb was found unexploded in a riverbed, while the fourth weapon fell into the Mediterranean Sea. That broken arrow was sighted by a local fisherman, who promptly went to court to claim salvage rights. Under prevailing maritime law, the salvage rights would have conferred 1 percent of the device’s $2 billion value—or about $20 million—on the fisherman. The Air Force reportedly settled out of court for an undisclosed sum.

8. January 21, 1968: Thule Air Force Base, Greenland
When a fire broke out in the navigator’s compartment of a B-52 flying on alert near the Arctic Circle in January 1968, the plane attempted to land at Thule Air Force Base in Greenland. It crashed about seven miles short of the runway and burst into flames, causing one bomb to detonate, one to burn and two others to sink through the ice sheet into the bay. The accident spread radioactive contamination from the plutonium core across a 1,000-foot area around the crash. Nearly a quarter of a million cubic feet of contaminated ice, snow, water and crash debris were removed to a storage site in the United States over the course of four months. Of the two weapons that went through the ice sheet, one was finally recovered in 1979, but an as-yet-unrecovered broken arrow still lies on the floor of Baffin Bay.

9. September 19, 1980: Damascus, Arkansas
When an Air Force repairman in Damascus, Arkansas, dropped his wrench into a Titan II ICBM missile silo during a routine maintenance operation in September 1980, his fumble spelled disaster. The heavy wrench punctured the pressurized fuel tank of the missile, which leaked slowly for over eight hours before exploding, killing one service member and injuring 21 others. A nuclear warhead contained in the missile’s reentry vehicle was ejected in the blast but was subsequently recovered intact.

9 Tales of Broken Arrows: Thermonuclear Near Misses Throughout History — History in the Headlines

This is how the USAF would respond so such an incident... in the 1980s

 
Last edited:
That depends on whether or not the weapon has been armed and has fallen for the minimum arming distance. Nuclear weapons have a series of safeguards called "Permissive Action Links" - one of which prevents misfires, but others are designed to prevent tampering to foil the misuse of a stolen or lost nuclear weapons. This is the reason the "terrorist nuke" scenario tends to be a bit BS. Some also prevent the weapons crew from going rouge and using the weapon without permission.

I know that on US nuclear weapons an operator has one chance to input the arming sequence into the weapon. If the sequence is incorrectly offered, the electronic arming device will fry itself rendering the weapon inert. Since these are dangerous and destructive systems, they do have safeguards, but all bombs, nuclear or conventional do to prevent accidental detonation.

The Russians tended to be a lot more careless with their weapons. I can't speak for India, Pakistan, North Korea, China, France or the UK though.

So to answer your question more shortly, yes, a downed or crashed bomber can cause a nuclear catastrophe, but only if the weapon is armed and meets the minimum travel distance.

Permissive Action Link - Wikipedia, the free encyclopedia

While this can happen, instances of armed nuclear weapons crashing are rare, though crashed bombers with nuclear weapons and the USAF have a dark history. Here's a few of those accidents.

Fifty-eight years ago, on May 22, 1957, a “broken arrow” rattled Albuquerque, New Mexico, frightening residents and killing one very unlucky cow. Used by the U.S. military, the term refers to a thermonuclear bomb that is accidentally detonated or lost. The Department of Energy has acknowledged more than two dozen such incidents between 1950 and 1980, many of them on U.S. soil.

1. May 22, 1957: Kirtland Air Force Base, New Mexico
Albuquerque residents enjoying a spring day on May 22, 1957, found themselves literally rocked by what felt like a nuclear explosion. They weren’t far off. No one knows precisely what happened aboard the B-36 aircraft transporting a nuclear weapon from Texas to New Mexico that day, but somehow the device fell through the bomb bay doors, plummeting about 1,700 feet into a field south of Kirtland Air Force Base. The conventional explosives detonated, blasting a crater 12 feet deep and 25 feet across. Luckily the nuclear capsule had been separated from the conventional explosives during transport for safety reasons, and that capsule was found intact. The only casualty of the blast? An unfortunate cow grazing nearby.

2. February 5, 1958: Savannah River, Georgia
When a B-47 carrying a nuclear device experienced a midair collision with an F-86 aircraft during a training simulation in February 1958, officials decided to jettison the bomb into the Savannah River. Fortunately, the device’s conventional explosives didn’t detonate when the weapon slid into the water and, as is standard with the nuclear version of a “live fire” exercise, the nuclear capsule wasn’t installed in the weapon. The Air Force searched until mid-April but never located the bomb. Today residents refer to this broken arrow as the Tybee Bomb.

3. March 11, 1958: Florence, South Carolina
In March 1958, as a team of military divers scoured the Savannah River in Georgia for a broken arrow, another one fell in the southeast quadrant of the United States. A B-47E aircraft carrying a thermonuclear weapon took off from South Carolina for an overseas base, accidentally jettisoning it shortly thereafter. The conventional explosives detonated on impact with the ground in a suburban Florence neighborhood, demolishing a house and causing several injuries.

4. November 4, 1958: Dyess Air Force Base, Texas
When a B-47 carrying a nuclear warhead catches fire on takeoff, it’s a problem. That’s what happened when a B-47 left Texas’ Dyess Air Force Base in November 1958 to transport a thermonuclear device to another location. At 1,500 feet it began experiencing trouble. Three of the plane’s crew members ejected safely, but one was killed when the plane subsequently crashed, setting off the bomb’s conventional explosives and blasting a crater 35 feet in diameter and 6 feet deep. All the nuclear components were recovered at the scene.

5. January 24, 1961: Goldsboro, North Carolina
In one of the closest calls in accidental nuclear detonation history, a single safety switch prevented a 20-megaton Mk39 hydrogen bomb from exploding in North Carolina in January 1961. When a B-52 carrying two of the bombs suffered a fuel leak in the wing, the plane exploded and dropped both bombs earthward. The parachute of one bomb deployed, but the other weapon nearly detonated when five of its six safety devices failed and it broke apart upon impact with the ground. While the Air Force recovered the bomb’s plutonium, the thermonuclear stage containing uranium was never found. The Air Force subsequently purchased and fenced off a land easement in the area where officials believe the uranium lies.

6. March 14, 1961: Yuba City, California
In March 1961, a heroic Air Force commander ordered his crew to bail out of a crippled B-52 carrying a pair of thermonuclear devices when the plane’s compartment pressurization system failed at 10,000 feet. The commander stayed aboard to pilot the plane away from populated areas near Yuba City, California, before ejecting to safety at 4,000 feet. The two nuclear weapons aboard the aircraft were torn from the plane when it crashed, but nothing exploded and no radioactive contamination was released.

7. January 17, 1966: Palomares, Spain
It’s pretty hard to cover up the midair explosion of a B-52 carrying four hydrogen bombs when the event is witnessed by hundreds of onlookers. So it came as no surprise to anyone when the Palomares incident, as it has come to be known, hit the front page of the New York Times in January 1966, just three days after the event occurred. During a routine refueling operation over Spain, an American B-52 patrolling on airborne alert was struck by the fuel plane’s boom, which instantly destroyed both planes and killed seven of the 11 total crew members. Two of the B-52′s bombs exploded on impact with the ground near the village of Palomares, contaminating approximately 1 square mile with radioactive plutonium. Another bomb was found unexploded in a riverbed, while the fourth weapon fell into the Mediterranean Sea. That broken arrow was sighted by a local fisherman, who promptly went to court to claim salvage rights. Under prevailing maritime law, the salvage rights would have conferred 1 percent of the device’s $2 billion value—or about $20 million—on the fisherman. The Air Force reportedly settled out of court for an undisclosed sum.

8. January 21, 1968: Thule Air Force Base, Greenland
When a fire broke out in the navigator’s compartment of a B-52 flying on alert near the Arctic Circle in January 1968, the plane attempted to land at Thule Air Force Base in Greenland. It crashed about seven miles short of the runway and burst into flames, causing one bomb to detonate, one to burn and two others to sink through the ice sheet into the bay. The accident spread radioactive contamination from the plutonium core across a 1,000-foot area around the crash. Nearly a quarter of a million cubic feet of contaminated ice, snow, water and crash debris were removed to a storage site in the United States over the course of four months. Of the two weapons that went through the ice sheet, one was finally recovered in 1979, but an as-yet-unrecovered broken arrow still lies on the floor of Baffin Bay.

9. September 19, 1980: Damascus, Arkansas
When an Air Force repairman in Damascus, Arkansas, dropped his wrench into a Titan II ICBM missile silo during a routine maintenance operation in September 1980, his fumble spelled disaster. The heavy wrench punctured the pressurized fuel tank of the missile, which leaked slowly for over eight hours before exploding, killing one service member and injuring 21 others. A nuclear warhead contained in the missile’s reentry vehicle was ejected in the blast but was subsequently recovered intact.

9 Tales of Broken Arrows: Thermonuclear Near Misses Throughout History — History in the Headlines

This is how the USAF would respond so such an incident... in the 1980s


thanks for the explanation .. well i dont know much about Pakistani Nuclear system or etc, but i guess as world shown their concern over the Pak nukes , we must have taken some major precaution about it .. i dont know what kin but obviously Pakistan army wont be fools to put missile ready to launch ...

next question, does a external force or ammunition can detonate the nuke ? for example a nuke in the air shot by a AA missile , could that trigger the Nuclear reaction ?
 
thanks for the explanation .. well i dont know much about Pakistani Nuclear system or etc, but i guess as world shown their concern over the Pak nukes , we must have taken some major precaution about it .. i dont know what kin but obviously Pakistan army wont be fools to put missile ready to launch ...

next question, does a external force or ammunition can detonate the nuke ? for example a nuke in the air shot by a AA missile , could that trigger the Nuclear reaction ?


No, that scenario wouldn't yield a nuclear detonation, but it could destroy the bomb and spread radioactive materials. There are two (there are more than two designs, but these are the two that are used), very precise methods to achieve a nuclear detonation.

Gun-type fission weapon - Wikipedia, the free encyclopedia

And

Nuclear weapon design - Wikipedia, the free encyclopedia - jump to the implosion section.

In either scenario a conventional explosive is used to achieve detonation (one to propel a pellet into a mass of radioactive material, the other to compress a radioactive mass into a critical state), but only under very specific circumstances. An outside detonation, such as an AA missile would not achieve the necessary conditions to yield a nuclear detonation, even if the weapon is armed.
 
Last edited:
No, that scenario wouldn't yeild a nuclear detonation, but it could destroy the bomb and spread radioactive materials. There are two (there are more than two designs, but these are the two that are used), very precise methods to achieve a nuclear detonation.

Gun-type fission weapon - Wikipedia, the free encyclopedia

And

Nuclear weapon design - Wikipedia, the free encyclopedia - jump to the implosion section.

In either senario a conventional explosive is used to achieve detonation (one to propel a pellet into a mass of radioactive material, the other to compress a radioactive material in a critical mass), but only under very specific circumstances. An outside detonation, such as an AA missile would not achieve the necessary conditions to yeild a nuclear detonation, even if the weapon is armed.

thanks once again , so basically there is very less chance for any AA or outside detonation to trigger the Nuclear reaction , which is it self a good sign ..so in case of Nuke with active Nuclear warhead , dropped by accident on a non target location , so it will not trigger the nuke but conventional warhead does explode right ?? obviously there are some conventional warhead in every Nuke BM and CM's right ?!
 
Back
Top Bottom