DEFCON

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The five levels of DEFCON

The defense readiness condition (DEFCON) is an alert state used by the United States Armed Forces.[1]

The DEFCON system was developed by the Joint Chiefs of Staff (JCS) and unified and specified combatant commands.[2] It prescribes five graduated levels of readiness (or states of alert) for the U.S. military. It increases in severity from DEFCON 5 (least severe) to DEFCON 1 (most severe) to match varying military situations.[1]

DEFCONs are a subsystem of a series of Alert Conditions, or LERTCONs, which also include Emergency Conditions (EMERGCONs).[3]

Operations

The DEFCON level is controlled primarily by the U.S. President and the U.S. Secretary of Defense through the Chairman of the Joint Chiefs of Staff and the Combatant Commanders, and each DEFCON level defines specific security, activation and response scenarios for the troops in question.

Different branches of the U.S. Armed Forces (i.e. U.S. Army, U.S. Navy, Air Force) and different bases or command groups can be activated at different defense conditions. In general, there is no single DEFCON status for the world or country and it may be set to only include specific geographical areas. According to Air & Space/Smithsonian, as of 2014, the worldwide DEFCON level has never risen higher than DEFCON 3. The DEFCON 2 levels in the Cuban Missile Crisis and 1991 Gulf War were not worldwide.[4]

There is no single DEFCON status for the country, and in fact different branches of the military can be at separate defense readiness conditions at the same time. DEFCONs should not be confused with similar systems used by the U.S. military, such as Force Protection Conditions (FPCONS), Readiness Conditions (REDCONS), Information Operations Condition (INFOCON) and its future replacement Cyber Operations Condition (CYBERCON),[5] and Watch Conditions (WATCHCONS), or the former Homeland Security Advisory System used by the United States Department of Homeland Security.

Levels

Defense readiness conditions vary between many commands and have changed over time,[2] and the United States Department of Defense uses exercise terms when referring to the DEFCONs.[6] This is to preclude the possibility of confusing exercise commands with actual operational commands.[6] On 12 January 1966, NORAD "proposed the adoption of the readiness conditions of the JCS system", and information about the levels was declassified in 2006:[7]:{{{3}}}

Readiness condition Exercise term Description Readiness
DEFCON 1 COCKED PISTOL Nuclear war is imminent Maximum readiness
DEFCON 2 FAST PACE Next step to nuclear war Armed Forces ready to deploy and engage in less than 6 hours
DEFCON 3 ROUND HOUSE Increase in force readiness above that required for normal readiness Air Force ready to mobilize in 15 minutes
DEFCON 4 DOUBLE TAKE Increased intelligence watch and strengthened security measures Above normal readiness
DEFCON 5 FADE OUT Lowest state of readiness Normal readiness

History

After NORAD was created, the command used different readiness levels (Normal, Increased, Maximum) subdivided into eight conditions, e.g., the "Maximum Readiness" level had two conditions "Air Defense Readiness" and "Air Defense Emergency".[7]:{{{3}}} In October 1959, the JCS Chairman informed NORAD "that Canada and the U. S. had signed an agreement on increasing the operational readiness of NORAD forces during periods of international tension."[7]:{{{3}}} After the agreement became effective on 2 October 1959,[7]:{{{3}}} the JCS defined a system with DEFCONs in November 1959 for the military commands.[2] The initial DEFCON system had "Alpha" and "Bravo" conditions (under DEFCON3) and Charlie/Delta under DEFCON4, plus an "Emergency" level higher than DEFCON1 with two conditions: "Defense Emergency" and the highest, "Air Defense Emergency" ("Hot Box" and "Big Noise" for exercises).[7]:{{{3}}}

DEFCON 2

Cuban Missile Crisis

During the Cuban Missile Crisis on October 22, 1962, the U.S. Armed Forces (with the exception of United States Army Europe (USAREUR)) were ordered to DEFCON 3. On October 24, Strategic Air Command (SAC) was ordered to DEFCON 2, while the rest of the U.S. Armed Forces remained at DEFCON 3. SAC remained at DEFCON 2 until November 15.[8]

Gulf War

On January 15, 1991, the Joint Chiefs of Staff declared DEFCON 2 in the opening phase of Operation Desert Storm during the Gulf War.[9]

As such, the defense readiness framework is not only for emergency response, but also for general force mobilization.

DEFCON 3

Yom Kippur War

On October 6, 1973, Egypt and Syria launched a joint attack on Israel resulting in the Yom Kippur War. The U.S. became concerned that the Soviet Union might intervene, and on October 25, U.S. forces, including Strategic Air Command, Continental Air Defense Command, European Command and the Sixth Fleet, were placed at DEFCON 3. Over the following days, the various forces reverted to normal status with the Sixth Fleet standing down on November 17.[10]

Operation Paul Bunyan

Following the axe murder incident at Panmunjom on August 18, 1976, readiness levels for American forces in South Korea were increased to DEFCON 3, where they remained throughout Operation Paul Bunyan which followed thereafter.[11]

September 11 attacks

During the terrorist attacks of September 11, 2001, the then U.S. Secretary of Defense Donald Rumsfeld ordered the increased DEFCON level to 3, and also a stand-by for a possible increase to DEFCON 2. That eventuality however did not come to pass. [12]

In other media

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found. (DEFCON is not mentioned in the 2010 and newer document)
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Chairman of the Joint Chiefs of Staff Instruction 6510.01F
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Nighthawks over Iraq, a study a study of the F117-A stealth fighter in operations Desert Shield and Desert Storm
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 911 Compmission Report