|
Defense Tech: Fun With Nuclear Targeting by Rattle at 1:05 am EDT, Jul 24, 2005 |
This post on the Defense Tech blog covers a few articles related to STRATCOM drawing up a response to a 9/11 style attack based from Iran. Click through for more links.. The plan includes a large-scale air assault on Iran employing both conventional and tactical nuclear weapons. Within Iran there are more than 450 major strategic targets, including numerous suspected nuclear-weapons-program development sites. Many of the targets are hardened or are deep underground and could not be taken out by conventional weapons, hence the nuclear option. As in the case of Iraq, the response is not conditional on Iran actually being involved in the act of terrorism directed against the United States.
The real amusing stuff has to do with the shorfalls of the planning systems for targeting: For example, of the 12,500 targets in the SIOP at that time, one of them was slated to be hit by 69 consecutive nuclear weapons. It seems superfluous to say that this is crazy, but it is important to understand how the planning process could result in such a figure. At the level of a presidential directive, a document of a thousand words or so, you will have the reasonable-sounding requirement--if you're thinking about war-fighting at all--to, say, target the political and military leadership. That guidance goes to the Office of the Secretary of Defense, which in a 15- or 20-page document called a NUWEP (for "nuclear weapons employment policy") adds some detail: for example, what sorts of leadership facilities should be targeted. The NUWEP then goes to the Joint Strategic Target Planning Staff of the Joint Chiefs of Staff, which in hundreds of pages of a document called Annex C to the Joint Strategic Capabilities Plan lists specific facilities to be struck and damage requirements to be met. Annex C then goes to STRATCOM, where the targetting staff figures out which weapons, and how many, to apply to each target to meet the required level of damage. When I mentioned Butler's 69 weapons to Dr. Bruce Blair, a former Minuteman missileer and acknowledged expert on the operational aspects of nuclear warfighting now at the Brookings Institution, he found in his notes a statement by a high official at SAC in the late 1980s that the highest kill probability for the United States' best weapon against deeply buried, sprawling, hardened command posts was less than 5% (how they calculate this is a whole other matter, but the short answer is, they guess). Blair got out a calculator, assumed a kill probability of 4% for one weapon, and started multiplying. To attain a 50% confidence in destroying the target required 17 weapons. When Blair got up to 69 weapons, the "kill probability" had reached 94%.
Hey kids, remember to add some type of bounds or exception checking to your code.. That particular "while" statement could lead to a site getting nuked 69 times. The boys at Lockheed Martin are supposedly working on a new planning system. |
|
RE: Defense Tech: Fun With Nuclear Targeting by Jamie at 9:06 am EDT, Jul 25, 2005 |
Rattle wrote: This post on the Defense Tech blog covers a few articles related to STRATCOM drawing up a response to a 9/11 style attack based from Iran. Click through for more links.. The plan includes a large-scale air assault on Iran employing both conventional and tactical nuclear weapons. Within Iran there are more than 450 major strategic targets, including numerous suspected nuclear-weapons-program development sites. Many of the targets are hardened or are deep underground and could not be taken out by conventional weapons, hence the nuclear option. As in the case of Iraq, the response is not conditional on Iran actually being involved in the act of terrorism directed against the United States.
The real amusing stuff has to do with the shorfalls of the planning systems for targeting: For example, of the 12,500 targets in the SIOP at that time, one of them was slated to be hit by 69 consecutive nuclear weapons. It seems superfluous to say that this is crazy, but it is important to understand how the planning process could result in such a figure. At the level of a presidential directive, a document of a thousand words or so, you will have the reasonable-sounding requirement--if you're thinking about war-fighting at all--to, say, target the political and military leadership. That guidance goes to the Office of the Secretary of Defense, which in a 15- or 20-page document called a NUWEP (for "nuclear weapons employment policy") adds some detail: for example, what sorts of leadership facilities should be targeted. The NUWEP then goes to the Joint Strategic Target Planning Staff of the Joint Chiefs of Staff, which in hundreds of pages of a document called Annex C to the Joint Strategic Capabilities Plan lists specific facilities to be struck and damage requirements to be met. Annex C then goes to STRATCOM, where the targetting staff figures out which weapons, and how many, to apply to each target to meet the required level of damage. When I mentioned Butler's 69 weapons to Dr. Bruce Blair, a former Minuteman missileer and acknowledged expert on the operational aspects of nuclear warfighting now at the Brookings Institution, he found in his notes a statement by a high official at SAC in the late 1980s that the highest kill probability for the United States' best weapon against deeply buried, sprawling, hardened command posts was less than 5% (how they calculate this is a whole other matter, but the short answer is, they guess). Blair got out a calculator, assumed a kill probability of 4% for one weapon, and started multiplying. To attain a 50% confidence in destroying the target required 17 weapons. When Blair got up to 69 weapons, the "kill probability" had reached 94%.
Hey kids, remember to add some type of bounds or exception checking to your code.. That particular "while" statement could lead to a site getting nuked 69 times. The boys at Lockheed Martin are supposedly working on a new planning system.
What's wrong with nuking the same target 69 times? |
|
|
|