USA-193

From Infogalactic: the planetary knowledge core
(Redirected from NRO L-21)
Jump to: navigation, search
USA-193
Delta II 7920 launch with NROL-21.jpg
Delta II launching USA-193, Vandenberg Air Force Base, 2006
Operator US National Reconnaissance Office
COSPAR ID 2006-057A
Mission duration Communications lost after orbit achieved
Spacecraft properties
Launch mass 2,300 kilograms (5,100 lb)[1]
Start of mission
Launch date December 14, 2006, 21:00:00 (2006-12-14UTC21Z) UTC
Rocket Delta II 7920-10
Launch site Vandenberg SLC-2W
End of mission
Disposal Destroyed by ASAT
Destroyed 21 February 2008 (2008-02-22)
Orbital parameters
Reference system Geocentric
Regime Low Earth
Perigee 242 kilometers (150 mi)
Apogee 257 kilometers (160 mi)
Inclination 58.48 degrees
Epoch 21 February 2008

USA-193, also known as NRO launch 21 (NROL-21 or simply L-21), was a U.S. military reconnaissance satellite (radar imaging) launched on December 14, 2006.[2] It was the first launch conducted by the United Launch Alliance.[3] Owned by the National Reconnaissance Office (NRO), the craft's precise function and purpose were classified.

The satellite malfunctioned shortly after deployment, and was intentionally destroyed 14 months later on February 21, 2008, by a modified SM-3 missile fired from the warship USS Lake Erie, stationed west of Hawaii.[4][5] The event highlighted growing distrust between the U.S. and China, and was viewed by some to be part of a wider "space race" involving the U.S., China, and Russia.[6]

Design

USA-193 was part of the NRO's Future Imagery Architecture, which was begun in 1997 to produce a fleet of inexpensive reconnaissance satellites, but has become the agency's most spectacular failure.[7] USA-193 was initially developed by Boeing, which won the contract in 1999, beating out Lockheed Martin with proposals for innovative electro-optics and radar. But after cost overruns, delays, and parts failures, NRO sent the contract to Lockheed, which built USA-193 around the Boeing radar design.[7] Lockheed Martin and Boeing both supported the launch, the first in the joint effort known as the United Launch Alliance.[8]

USA-193 weighed about 5,000 pounds (2,268 kg),[1] with a body thought to be 15 feet (5 m) long and 8 feet (2 m) wide, estimates based on the maximum Delta II payload. With the radar antenna extended, USA-193 was about the size of a basketball court (~30 x 15m).[9]

Launch data

USA-193 (NROL-21) launch patch.
USA-193 (NROL-21) launch patch

Malfunction and orbital decay

The satellite entered orbit successfully but lost contact with the ground within hours.[1]

In late January 2008, reports from anonymous U.S. officials indicated a U.S. spy satellite, later confirmed as USA-193,[1] was in a deteriorating orbit and was expected to crash onto Earth within weeks.[16][17] This came as no surprise to amateur satellite watchers, who had been predicting the deorbit of the satellite for some time.[18]

Hazardous materials on-board

Federal Emergency Management Agency (FEMA) reports indicate that the satellite contained the hazardous materials hydrazine and beryllium.[19] Though there was some speculation that the satellite might have a "nuclear" power core,[20] i.e. a radioisotope thermoelectric generator, the FEMA report indicates otherwise.

On January 29, 2008 an Associated Press story quoted a U.S. Air Force general as saying that contingency plans were being made since intact pieces of the satellite "might re-enter into the North American area".[21]

In respecting the Liability Convention, the United States vowed to pay for any damage or destruction caused by their failed satellite.[22]

Destruction

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

Planning for the destruction of USA-193 with a missile reportedly began on January 4, 2008, with President Bush approving the plan on February 12,[23] at an expected cost of $40 million to $60 million.[24] The task force had as its goal to "rupture the fuel tank to dissipate the approximately 1,000 pounds (453 kg) of hydrazine, a hazardous fuel which could pose a danger to people on Earth, before it entered into Earth's atmosphere".[25]

Launch of the SM-3 missile that intercepted USA-193.

On February 14, 2008, U.S. officials announced the plan to destroy USA-193 before atmospheric reentry, stating that the intention was "saving or reducing injury to human life". They said that if the hydrazine tank fell to Earth it "could spread a toxic cloud roughly the size of two football fields".[26] General James Cartwright confirmed that the United States Navy was preparing to launch an SM-3 missile to destroy the satellite, at an altitude of 130 nautical miles (240 km), shortly before it entered Earth's atmosphere.[1]

On February 21, 03:26 GMT an SM-3 missile was fired from the Ticonderoga class missile cruiser USS Lake Erie, and intercepted USA-193 about 133 nautical miles (247 kilometers)[25] above the Pacific Ocean. The satellite was travelling with a velocity of about 17,500 mph (around 28,000 km/h or 7.8 km/s). The velocity of the impact was about 22,000 mph. The Department of Defense expressed a "high degree of confidence" that the fuel tank was hit and destroyed.[27] The satellite's remnants were expected to burn up over the course of the next 40 days, with most of the satellite's mass re-entering the atmosphere 24 to 48 hours after the missile strike.[25][28]

U.S. officials denied that the action was intended to prevent sensitive technology falling into foreign hands,[1] and also denied that it was a response to the 2007 Chinese anti-satellite missile test.[29] This was not the first time the United States shot down one of its own satellites; the Air Force had shot down a satellite as early as 1985.[30]

Break up of USA-193 following interception by the SM-3 missile.

Although the U.S. had objected to the earlier Chinese test of an anti-satellite (or ASAT) weapon, U.S. officials said there was "no parallel" with that test. The Chinese test destroyed a target in a high, stable orbit, leaving a large amount of space debris in orbit, while the destruction of USA-193 in a much lower orbit would create debris that would likely deorbit within weeks.[1][31]

Controversy

The Russian government claimed that this exercise was a test of the U.S. missile defense program.[32] The defense ministry of Russia accused the U.S. of using hydrazine as a cover for the test of an ASAT. It also noted that extraordinary measures had never before been needed to deal with the many spacecraft that had fallen to Earth.[31] Indeed, the New York Times had paraphrased Gordon Johndroe, spokesman for the United States National Security Council, as stating that 328 objects had deorbited (controlled and uncontrolled) in the previous 5-year period.[33] However, U.S. officials maintained that the large quantity of hydrazine on board made USA-193 a special case.[1] According to General Kevin P. Chilton, when President Bush was briefed on the situation, the danger that shooting down the satellite would be perceived as an ASAT test was brought up, and President Bush made his decision based on the dangers of an uncontrolled reentry.[34]

Other observers dismiss the threat of the hydrazine, suggesting that the effect of the cloud, when diluted over a large area, would likely be mild: "The hydrazine tank is a 1-meter sphere containing about 400 liters of hydrazine. The stated hazard area is about 2 hectares, something like 1/10,000,000,000 of the area under the orbit. The potential for actual harm is unbelievably small."[35] Other analyses, such as those cited by Yousaf Butt, show the hydrazine tank burning up in the upper atmosphere.[36]

Two examples of uncontrolled atmospheric re-entries causing (or almost causing) damage are the 1978 re-entry of Cosmos 954, a Soviet satellite, which landed in Canada and spread dangerous amounts of nuclear fuel from its onboard reactor over large tracts of land, and Skylab's 1979 re-entry, which rattled windows and dropped small pieces of debris onto buildings in Esperance, Western Australia (no significant monetary damage resulted, but the U.S. was symbolically fined $400 for littering).[37] No weapon existed in 1978 to bring down Cosmos 954, and a Soviet anti-satellite weapon (Istrebitel Sputnik), the first of its kind, was declared operational only ten days before Skylab re-entered the atmosphere, and was not capable of directing the space station's descent.

Before the destruction of USA-193, Pentagon officials repeatedly denied that it was meant to bolster the U.S. missile defense program. Six days after USA-193's destruction, Defense Secretary Robert M. Gates said, "the mission's success shows that U.S. plans for a missile-defense system are realistic" though in the same statement it was confirmed that the weapons and systems used for this mission will not retain their ASAT capability, and will be reconfigured back to their original purpose as tactical missiles.[38]

Debris

The destruction of USA 193 created 174 pieces of orbital debris that were cataloged by the U.S. military.[39] While most of this debris re-entered the Earth's atmosphere within a few months, a few pieces lasted quite a bit longer due to the fact that they were thrown into much higher orbits. The final piece of USA 193 debris did not re-enter until October 28, 2009.[39]

The launch of at least one other satellite was postponed to avoid space debris from USA-193. An Atlas V launch hot line recording indicated the debris would delay the launch of a different National Reconnaissance Office satellite (NRO L-28) as "a precautionary measure."[40]

Catalogue IDs

Gallery

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Pentagon news briefing of February 14, 2008 (video, transcript): although no name for the satellite is given, the launch date of 2006-12-14 is stated
  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. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  18. 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.[dead link]
  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.[dead link]
  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. 25.0 25.1 25.2 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  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. 31.0 31.1 BBC: US spy satellite plan 'a cover'
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. New York Times: Satellite Spotters Glimpse Secrets, and Tell Them
  34. Lua error in package.lua at line 80: module 'strict' not found. A shorter version of this article was published as 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. Also Lua error in package.lua at line 80: module 'strict' not found. The NASA study was Atmospheric Reentry of a Hydrazine Tank by Robert L. Kelley and William C. Rochelle.
  37. Hannah Siemer. "[1]". The Esperance Express, 17 April 2009.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Data retrieved from the U.S. military's public satellite catalog maintained at Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 CelesTrak: SATCAT search

External links