Ground-Based Midcourse Defense

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
A Ground-Based Interceptor loaded into a silo at Fort Greely, Alaska, in July 2004

Ground-Based Midcourse Defense (GMD) is the United States' anti-ballistic missile system for intercepting incoming warheads in space, during the midcourse phase of ballistic trajectory flight. It is a major component of the American missile defense strategy to counter ballistic missiles, including intercontinental ballistic missiles (ICBMs) carrying nuclear, chemical, biological or conventional warheads. GMD is administered by the U.S. Missile Defense Agency (MDA), while the operational control and execution is provided by the U.S. Army, and support functions are provided by the U.S. Air Force. Previously known as National Missile Defense (NMD), the name was changed in 2002 to differentiate it from other U.S. missile defense programs, such as space-based and sea-based intercept programs, or defense targeting the boost phase and reentry flight phases.[1] The program is projected to cost $40 billion by 2017.

Description

Prototype of the Exoatmospheric Kill Vehicle

The system consists of ground-based interceptor missiles and radar which would intercept incoming warheads in space. Boeing Defense, Space & Security is the prime contractor of the program, tasked to oversee and integrate systems from other major defense sub-contractors, such as Computer Sciences Corporation.

The key sub-systems of the GMD system are:

Interceptor sites are at Fort Greely, Alaska[2][3][4] and Vandenberg Air Force Base, California. A third site was planned for a proposed US missile defense complex in Poland,[5] but was canceled in September 2009.

In December 2008, the U.S. Missile Defense Agency awarded Boeing a $397.9 million contract to continue development of the program.[6]

In March 2013, the Obama administration announced plans to add 14 interceptors to the current 26 at Fort Greely in response to North Korean threats.[7] The deployment of a second TPY-2 radar to Japan was announced at the same time.[8] While Obama said that the additional deployment was a hedge against unexpected capabilities, Chinese Ministry of Foreign Affairs spokesman Hong Lei complained that the additional defenses would impact on global strategic balance and strategic trust.[9] In late 2013, there are plans for a proposed Eastern United States missile defense site to house a battery of these missiles.[10]

On 30 April 2014, the Government Accountability Office issued a report stating that the system may not be operational any time soon because "its development was flawed". It says the GBI missile is "capable of intercepting a simple threat in a limited way".[11] On 12 August 2015, David L. Mann[who?] characterized GMD as the nation's only ground-based defense against limited ICBM attacks.[11]

Program costs

Expenditures on the Ground-Based Midcourse Defense program have been estimated at US$30.7 billion by 2007.[12] In 2013, it is estimated that the program will cost $40.926 billion from inception through FY2017; in 2013–17 spending is to total $4,457.8M, an average of $892M per year.[13]

Flight tests

BV: Booster Verification Test
CMCM: Critical Measurements and Countermeasures
FTG: Flight Test Ground-Based Interceptor
FTX: Flight Test Other[14]
IFT: Integrated Flight Test

Intercept tests

As of June 2014, 9 of the 17 (53%) hit-to-kill intercept tests have succeeded. The flight intercept tests from 2010 to 2013 were not successful.[15] In response the Pentagon is asking for a budget increase and another test for the fielded program.[16]

Name Date Result Description[17][18][19]
IFT-3 Oct 2, 1999 Success This was an element test of the EKV that relied on a surrogate booster vehicle. Because the Inertial Measurement Unit malfunctioned, the EKV used a backup acquisition mode to acquire the target.
IFT-4 Jan 18, 2000 Failure This was the first end-to-end system test, again relying on a surrogate booster vehicle. The test was designed to target a mock warhead, transmitting its location by GPS, and ignore a single large decoy balloon. The failure to intercept was traced to an obstructed cooling line on the EKV that disrupted the IR sensors' ability to cool down to their operating temperatures in time, leaving the EKV unable to detect its target.
IFT-5 Jul 8, 2000 Failure This was the second end-to-end system test. The test was designed to target a mock warhead, transmitting its location by C-band, and ignore a single large decoy balloon. The failure to intercept occurred because the EKV did not separate from the boost vehicle due to an apparent failure of the 1553 data bus in the booster.
IFT-6 Jul 14, 2001 Success This test repeated IFT-5. The prototype X-Band radar falsely reported a missed target but was confirmed by a satellite, jet, and ground stations.
IFT-7 Dec 3, 2001 Success This test repeated IFT-6 except that the target booster used Orbital’s Target Launch Vehicle instead of Lockheed Martin’s Multi-Service Launch System.
IFT-8 Mar 15, 2002 Success The test was designed to target a mock warhead, transmitting its location by C-band, and ignore both a large decoy balloon and two small decoy balloons.
IFT-9 Oct 14, 2002 Success Twice delayed from August, this was the first test to use the Aegis SPY-1 radar, although it was not used to achieve the intercept. After the classification of decoys since May 2002, no information is known on their details.
IFT-10 Dec 11, 2002 Failure The failure to intercept occurred because the EKV did not separate from the boost vehicle because a pin broke that should have activated a laser to release the boost vehicle’s restraining units.
IFT-13C Dec 15, 2004 Failure Delayed several times from December 2003 due to bad circuitry, this test was designed to use the Orbital Sciences booster from Kwajalein to hit a target from Kodiak, Alaska. The target flew as planned but the booster failed to leave the ground. The failure was traced to a software problem on the 1553 communications data bus, which may be incapable of processing messages at a rate that is fast enough for the GMD system to work effectively.
IFT-14 Feb 13, 2005 Failure This test repeated IFT-13C, with a booster from Kwajalein designed to hit a target from Kodiak, Alaska. Again, the target flew as planned but the booster failed to leave the ground. The failure was traced to the arms that hold the interceptor up in the silo. When they failed to fully retract, the launch was automatically aborted.
FTG-02 Sep 1, 2006 Success This test involved the first ground-based interceptor launched out of Vandenberg Air Force Base to intercept a "threat-representative" target from Kodiak, Alaska. This was the first time that operational radar was used to capture targeting information. Not officially an intercept test, this was originally designed to collect data on the phenomenology of the intercept and act as a radar certification test. No decoys were used.[20]
FTG-03 May 25, 2007 Failure With the same setup as FTG-02, the test target flew off-course and an intercept did not occur.
FTG-03A Sep 28, 2007 Success This test was scheduled in response to the failure of FTG-03, this time with a successful intercept.
FTG-05 Dec 5, 2008 Success This test launched a threat-representative mock warhead from the Kodiak Launch Complex, Alaska followed by a Ground-Based Interceptor from Vandenberg AFB. All components performed as designed.[21]
FTG-06 Jan 31, 2010 Failure This test was to be the first to assess both a CE-II EKV and a complex target scene and the first test to use a newly developed FTF LV-2 target.[22] While the target missile and interceptor launched and performed nominally, the Sea Based X-Band Radar did not perform as expected, and an investigation will explain the failure to intercept.[23]
FTG-06a Dec 15, 2010 Failure This test was similar to FTG-06, over a distance of 4,200 miles.[24] While the Sea Based X-Band radar and all sensors performed as planned, the test was unable to achieve the planned intercept of a ballistic missile target.[25]
FTG-07 Jul 5, 2013 Failure[26] This intercept test used an improved CE-I EKV.[27]
FTG-06b Jun 22, 2014 Success[28] This test is designed to demonstrate an intercept and meet the unmet objectives of FTG-06a.[18][27]

Non-intercept tests

Name Date Result Description[17][29][30]
IFT-1A Jun 24, 1997 Success This test allowed the program to assess the Boeing EKV seeker's ability to collect target phenomenological data, and evaluate target modeling and discrimination algorithms for a cluster of 10 objects.
IFT-2 Jan 16, 1998 Success This test allowed the program to assess the Raytheon EKV seeker's ability to collect target phenomenological data, and evaluate target modeling and discrimination algorithms for a cluster of 10 objects. As a result Raytheon was selected over Boeing and was awarded the EKV contract.
BV-1 Apr 28, 2001 Success This was a ground test to certify the procedures that lead to an actual flight test, including all ground and safety checks as well as launch and safety steps. The missile was not launched.
BV-2 Aug 31, 2001 Success This was a flight test of three-stage Boeing Booster Vehicle with a mass-simulated kill vehicle payload. An anomaly occurred in the first-stage vehicle roll control, but the second- and third-stage motors performed normally.
BV-3 Dec 13, 2001 Failure This flight test resulted in failure when the Boeing Booster Vehicle steered off course 30 seconds after launch and was then ordered to self-destruct off the coast of California.
BV-6 Aug 16, 2003 Success This was a flight test of the three-stage Orbital Sciences Booster Vehicle with a mass-simulated kill vehicle payload. The launch from Vandenberg Air Force Base proceeded normally over the Pacific Ocean.
BV-5 Jan 9, 2004 Failure This flight test of the Lockheed Martin Booster Vehicle with a mass-simulated kill vehicle payload resulted in failure due to an apparent power drop that prevented the mock EKV from separating from the booster. The flight was delayed by the third-stage rocket motor's circuit boards.
IFT-13B Jan 26, 2004 Success This was a system-level test of the Orbital Sciences booster carrying a simulated EKV from Kwajalein Atoll against a simulated target from Vandenberg AFB in California.
Medium-range air-launch target Apr 8, 2005 Success This test featured a C-17 dropping a medium-range target from its rear, 800 miles (1,300 km) northwest of the Pacific Missile Range Facility in Hawaii.
CMCM-1A/FT 04-2A Aug 4, 2005 Success This test was the first of two medium-range target vehicles.
CMCM-1B/FT 04-2B Aug 18, 2005 Success This test was the second of two medium-range target vehicles.[31]
FT 04-5/FTG 04-5 Sep 26, 2005 Success This test was an apparent variant of IFT-19 and featured an air-launched long-range target tracked by Cobra Dane radar.
FT-1 Dec 13, 2005 Success Originally designed as IFT-13A, this test featured an interceptor missile from the Ronald Reagan test site in the Marshall Islands to hit a target from Kodiak, Alaska. The operationally configured warhead and its booster left the ground successfully.
FTX-01/FT 04-1 Feb 23, 2006 Success Originally designed as IFT-16, then changed to a radar characterization flight test as IFT-16A, then FT 04-1, then FTX-01. This test incorporated radar and targets testing.
CMCM-2B/FTC-02B Apr 13, 2006 Success This test was a radar certification flight and featured a missile system powered by a two-stage SR-19 rocket flown from the Kauai Test Facility in the Pacific Missile Range Facility. The payload included complex countermeasures, a mock reentry vehicle, and on-board sensor package.
CMCM-2A/FTC-02A Apr 28, 2006 Success This test repeated FTC-02B to test its radars in the Pacific Missile Range Facility in Hawaii against a target missile that carried countermeasures, a mock warhead, and an on-board sensor package.
FTX-02 Mar 27, 2007 Mixed This test of the Sea-Based X-Band Radar revealed "anomalous behavior", and demonstrated a need for software modifications to improve performance.
FTX-03 Jul 18, 2008 Success This test demonstrated the integration of missile defense sensors to support an interceptor engagement. This revealed the success of the Sea-Based X-Band Radar to be used in future missions.[32]
BVT-01 Jun 6, 2010 Success A two-stage Ground-Based Interceptor successfully launched from Vandenberg Air Force Base, and after separating from the second-stage booster, the exoatmospheric kill vehicle executed a variety of maneuvers to collect data to further prove its performance in space. All components performed as designed.[33]
GM CTV-01 Jan 26, 2013 Success The three-stage booster deployed the Exoatmospheric Kill Vehicle to a point in space and executed a variety of pre-planned maneuvers to collect performance data. Initial indications are that all components performed as designed.[18][34]
Sea based X band platform arriving in Pearl Harbor, January 2006

Canceled tests

Throughout the program's history, multiple test flights have been canceled, including BV-4, IFT-11, -12, -13, -13A, -15, FTC-03, and most recently, FTG-04.[35][36]

See also

References

  1. Reorganization of the Missile Defense Program: Hearing Before the S. Armed Services Comm. Strategic Forces Subcomm. (statement of Ronald T. Kadish). MDA. 13 March 2002.
  2. Begich, Gates visit Alaska missile defense base By Tim Bradner, Alaska Journal of Commerce, June 5, 2009.
  3. Northrop Grumman Contribution to Support Missile Defense Workforce in Alaska. reuters.com, Oct 30, 2009.
  4. Commanding Alaska's Guard w/ 24/7 missile defense
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. "Boeing Wins Missile Deal". Washington Post, December 31, 2008, p. D2.
  7. "US to beef up missile defense against NKorea."
  8. "Alaska's Ground Based Interceptors to Pivot US Defenses Against North Korea."
  9. "China: U.S. risks antagonizing North Korea."
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 "Mann addresses missile defense future during symposium"
  12. "More Dollars, Less Sense, Individual Contract Report: Ground-Based Midcourse Defense (Missile Defense)". United States House Of Representatives, Committee On Oversight And Government Reform, June 2007.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. "Missile Defense Test Conducted". U.S. Department of Defense, 5 July 2013.
  27. 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. "U.S. missile defense system destroys target in key test". Reuters, 22 June 2014.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.

External links