6 ms·
Command and Control [video]
- dmourati 10y agoCuriously I just picked up the book last weekend. Enjoying it so far.
- Cacti 10y agoThe book is fantastic. I'd also recommend "One Point Safe," which is similar.
- gerry_shaw 10y agoTrailer looks true to the book. Looking forward to this.
- Tech1 10y agoEx US Army bomb technician here (eod). This entire story is somewhat of a legend among our community (those that actually went through nukes at least). Added to our (me and the SO) calendar for the weekend. Looking forward to seeing it.
- sandworm101 10y ago"...chronicle nine hours of terror that prevented an explosion 600 times more powerful than Hiroshima." I'm calling out the film's makers on that statement. I challenge anyone to describe a situation whereby an ICBM with a leaky first stage could ever detonate the warhead in a manner resulting in such an explosion. These things don't go off when you drop them. They don't go off when you set them on fire. They don't go off when you surround them with explosives. Getting a thermonuclear weapon to detonate requires hundreds of things to happen in a precise manner. That cannot happen by accident.
- CoolGuySteve 10y agoYou should read the book, he addresses the trigger mechanisms in great detail.
- dfsegoat 10y agoI've read the book. The issue is not the trigger mechanisms/lack of security - we are talking about the durability of the warheads and accidental detonation.
- detaro 10y agoWhile I agree that they overdo it here: You really should read the book if you believe nukes were (are?) this safe.
- throwanem 10y agoI did, and found no particular cause for concern with regard to safety. Past practice lacked in some regards, I agree. But, as I recall the book, even Schlosser conceded that those issues have been effectively addressed, and that the balance between agility of response and effective C&C had been swung pretty firmly in the latter direction even by the time of the 1980 Titan accident, to say nothing of today.
- msl 10y ago> Past practice lacked in some regards This seems like a rather mild interpretation. As for the effective addressing of safety issues, it was not that long ago that the USAF last "lost" nuclear weapons [1]. (The weapons were in fact in USAFs possession, but no one knew were they were, or even that they weren't where they should have been. During this time the weapons were not handled according to the normal procedures.) [1] https://en.wikipedia.org/wiki/2007_United_States_Air_Force_nuclear_weapons_incident https://en.wikipedia.org/wiki/2007_United_States_Air_Force_n...
- throwanem 10y agoTrue. That was also the first time in forty years that such an incident had occurred. The officers responsible were relieved of their commands; the enlisted personnel involved were retrained and in some cases demoted; the entire command structure around nuclear-armed formations was reworked to reduce the likelihood of future such incidents. What about this response strikes you as having been ineffective?
- sandworm101 10y agoI don't disagree that they are dangerous objects. They are radioactive material surrounded by explosives atop a rocket full of other explosives. But the 600x description means a full and proper thermonuclear detonation. That is a very different beast than an on-pad/in-silo explosion possibly releasing a small amount of radioactive material in an isolated location, a 'dirty bomb' at best. The reference to a large nuclear mushroom cloud is improper. It was never a possibility short of someone actually wanting it[1]. [1] There is much evidence that these things could have been set off deliberately (see "111111") but that isn't what this film is about.
- dfsegoat 10y agoAgreed 100%: 1958 Mars Bluff B-47 nuclear weapon loss incident: HE component detonated on impact. Warhead did not. 1956 Lakenheath B-47 accident A USAF B-47 crashed into a storage igloo spreading burning fuel over three Mark 6 nuclear bombs at RAF Lakenheath. ... and so on. These things are built to sit in pools of burning fuel. (and yes, i have read the book)
- mikeash 10y agoNote that your two examples didn't involve any nuclear material, as the fissile cores were kept separately and weren't installed in the bombs at the time.
- dfsegoat 10y agoYes - a very good point. Thanks for noting that - I didn't have time to go back through the list and obviously omitted the Palomares incident.
- dogma1138 10y agoI don't understand the downvotes, the OP is correct, the explosion could have resulted in a environmental disaster but in effect it would've been a "dirty bomb". In the book they went over the trigger mechanism and overall there was no way for the 1st stage fission warhead to detonate not to mention for the 2nd stage fusion reaction to kick off. A nuclear warhead is pretty darn hard to detonate, the detonation sequence is extremely precise and the smallest deviation would result in a dud and in rare cases an extremely low yield fizzle. You can do whatever you want to a nuke, blow it up, set it ablaze, put it in a microwave, hit it, drop it even from orbit, it will not go off, not even because there are failsafes but because there is virtually no way for the nuke to "fail" in a way that would be even remotely close to a detonation sequence, an accidental detonation especially through brute force that would physically damage the warhead is about as likely as a tornado passing through a junkyard leaving assembled 747's in it's wake.
- sandworm101 10y ago>> an accidental detonation especially through brute force that would physically damage the warhead is about as likely as a tornado ... Even if you do damage the warhead, even if you get the high explosives of the warhead to detonate, that detonation will not be symmetrical. If it isn't perfect, the shell doesn't collapse evenly --> no critical mass --> no nuclear fission --> no nuclear fusion == a week dirty bomb. No mushroom cloud. The bomb's brain has to be involved. It has to want to go off.
- Kadin 10y agoI am in complete agreement, with the exception of this statement: > there is virtually no way for the nuke to "fail" in a way that would be even remotely close to a detonation sequence That is not true, at least not universally. Nuclear bombs are, by definition, designed to go off, and as a result there is a category of failure modes that could lead to inadvertent detonation. Basically, a failure that produces the same command that would cause the normal detonation sequence to begin, could cause an unintended detonation. The Mk. 39 bomb involved in the 1961 North Carolina B-52 crash [0] reportedly came close to detonating in this manner. Additionally, there are weapons designs that are not "one point safe", such that a failure which causes ignition of the high explosive could lead to a nuclear detonation. Weapons considered "one point safe" require multiple, carefully timed or simultaneous ignitions of the high explosive. The last non-one-point-safe weapons in the US arsenal were built in the 50s but not disassembled until recently; the W56 was reportedly not one point safe [1], or at least not provably so to the safety margins now recognized as reasonable. I don't know of any information in the unclassified literature about whether Soviet weapons are universally one-point-safe or not. It would not surprise me if there are a variety of weapon designs still floating around in the world that aren't one-point-safe. Single compression "gun type" bombs, like the Fat Man design, would require additional engineering to make one-point-safe beyond what is minimally required to get them to detonate, which makes me suspect that some marginal nuclear powers probably don't bother. [0]: https://en.wikipedia.org/wiki/1961_Goldsboro_B-52_crash https://en.wikipedia.org/wiki/1961_Goldsboro_B-52_crash [1]: https://web.archive.org/web/20070110205223/http://www.pogo.org/p/homeland/hl-061201-bodman.html https://web.archive.org/web/20070110205223/http://www.pogo.o...
- ekianjo 10y agoThe book agrees with you on that, but the trailer goes for sensationalism...
- JoeDaDude 10y agoIt is described as an American Experience film, with the Corporation for Public Broadcasting listed as an underwriter. Surely we'll see this on a PBS TV broadcast soon.
- ekianjo 10y agoLoved the book but the trailer looks a little.. meh. I hope the movies does not disapppoint, this ia a very important topic folks should care and know about.
- BoringCode 10y agoAs someone who hasn't read the book or heard about the incident for that matter, I thought it was an interesting trailer. I certainly want to see the film now.
- smoyer 10y agoThe Wikipedia article on this "incident": https://en.m.wikipedia.org/wiki/1980_Damascus_Titan_missile_explosion https://en.m.wikipedia.org/wiki/1980_Damascus_Titan_missile_...
- jdiez17 10y agoThe movie looks interesting, but seems I'll never get to see it, as there are no screenings in London, and I bet they won't offer a digital download option on their website...
- wingerlang 10y agoIs the name a reference to Command and Conquer? Got some flashbacks from the logo http://i.imgur.com/riegcsv.png http://i.imgur.com/riegcsv.png
- ablation 10y agoThe book was very good.
- ChicagoHero 10y agoTLDR: documentary about nine hours of terror that prevented an explosion 600 times more powerful than Hiroshima at Titan II missile complex in Arkansas; September, 1980.
- throwanem 10y agoIs that your characterization or theirs? It's been a while since I read the book, but I don't recall either that or any other source suggesting that there was at any point a serious risk of the warhead going off.
- dfsegoat 10y agoYeah, this really bugs me - having read the book. But I guess one needs to sell a movie somehow.