Aerospace Blog Blog

Aerospace Blog

The Aerospace Blog is the place for conversation and discussion about aeronautics, astronautics, fixed-wing aircraft, future space travel, satellites, NASA, and much more.

Previous in Blog: Let’s Shoot Down a Satellite: An In-Depth Review (Part 1)   Next in Blog: Let’s Shoot Down a Satellite: An In-Depth Review (Part 3)
Close
Close
Close
5 comments
Rate Comments: Nested

Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

Posted February 26, 2008 12:00 AM by M&M_aero

There were many reasons why U.S. Defense Secretary Robert Gates gave the order to shoot down spy satellite USA-193 (NROL-21). First, the American spacecraft could have killed or injured many people had it re-entered Earth's atmosphere. There was also sufficient evidence that the fuel tank would withstand re-entry because the space shuttle Columbia had a similar tank which survived and struck the ground after its tragic loss in 2003. Still, MIT physicist and space expert Geoffrey Forden calculated that there was only a 3.5 % chance that the spy satellite's fuel tank would kill or injure a human if it survived atmospheric re-entry.

Another reason for the Pentagon's "go" decision was concern that hydrazine fuel poses an unacceptable risk to humans and the environment. Any person who breathed the toxic fuel would need immediate medical attention and, because of the airborne nature of fumes, the fuel could spread quickly depending on the wind and weather conditions. Many experts, including former Assistant Secretary of Defense Philip Coyle, did not accept this argument. Instead, they believed that that the National Reconnaissance Office (NRO) did not want some part of the satellite falling into the wrong hands. According to these critics, the NRO had its own reasons for the satellite needing to be shot down, and could not (or would not) share this information with the general public.

On February 20, 2008 at 9:07 AM, the space shuttle Atlantis landed safely at Cape Canaveral, Florida. With the space shuttle and its crew safely on the ground, U.S. Defense Department officials said that the window of opportunity was now open. The U.S. Navy positioned three ships, the cruiser USS Lake Erie and the destroyers USS Decatur and USS Russell, in the Pacific Ocean, waiting for the optimal launch time. They waited for all factors to be in their favor before shooting. Steady seas were needed around the Navy cruiser that would fire the missile, optimum positioning of the spy satellite was required as it passed in polar orbit, and space and ground sensors needed to be ready to track the results.

Early Wednesday morning, a senior military officer said that the weather wasn't good enough for an ASAT launch. Hours later, however, another officer said that the weather was improving and that a launch might be possible by Wednesday night. The next obstacle the Navy faced was high seas in the North Pacific. Rough seas could interfere with the cruiser's launch procedures, and positioning could become problematic.

The U.S. government had put several precautionary and safety procedures in place. Operating under the code name "Burnt Frost", hazardous materials teams were ready to be deployed immediately anywhere in the world, to the site of dangerous or sensitive debris. Authorities had also dispatched six Federal Emergency Management Agency (FEMA) teams across the country for a worst-case scenario. The U.S. government also made worldwide notifications to mariners and aviators, warning them to stay clear of a large area in the Pacific Ocean where the most debris might fall. At the same time, however, experts agreed that the risk which falling debris posted to commercial aircraft was low enough that planes would not need to be rerouted around the area.

Yet risks remained. If the Navy missile struck the spy satellite, there was only a 30% chance that the fuel tank would be destroyed completely by flying shrapnel. At the same time, the U.S. military was concerned about the possibility of missing the satellite completely due to the incredibly high closing speeds and long distance involved. They were also concerned about the political and military fallout if such a failure occurred.

Editors Note: Part 1 can be found here on CR4 and Part 3 will run tomorrow.

CR4 Aerospace Blog

Reply

Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.
Anonymous Poster
#1

Re: Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

02/26/2008 9:05 AM

Good thing FEMA didn't have to get involved. Just read that they're trying to get rid of their formaldehyde filled trailers in Tennessee. Would FEMA have done a better job with hydrazine than it did with Hurricane Katrina? Good thing we didn't have to be the farm o on that one.

Reply Score 1 for Off Topic
Power-User

Join Date: Sep 2006
Location: Houston Texas
Posts: 282
Good Answers: 16
#2

Re: Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

02/26/2008 10:55 PM

I still wonder if the satellite could have been repaired instead of bring shot down. It was launched in 2006 and the only problem is it lost communications.

Could we not have replaced the communications electronics by using the Space Shuttle? It certainly worked to replace the incorrectly ground mirror in the Hubble Telescope.

__________________
Specializing in Dynamic Weighing Systems for Powder and Bulk Solids Handling
Reply
Participant

Join Date: Aug 2007
Posts: 2
#3
In reply to #2

Re: Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

02/27/2008 12:04 AM

The Hubble Telescope had more of a scientific purpose than NROL-21. There may be some basis for Secretary Coyle's belief. If the NROL-21 was, or may have been, collecting intelligence for 14 months then a tacticle reason may have overridden a practical reason for the decision to destroy rather than repair. It also may have accomplished its purpose if only the control communications degraded while the intelligence gathering and/or delivery system was still functional. The hydrazine threat may have only been a small part of the overall threat of re-entry. Placing such a satellite in the Space Shuttle may have exceeded the clearance of people running the mission. Finally, the expected re-entry time of the first week in March gave little time for a recovery/repair mission to be planned and executed.

Reply
Commentator

Join Date: Apr 2007
Posts: 55
#4
In reply to #2

Re: Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

02/27/2008 3:54 AM

Delmar said:- ;I still wonder if the satellite could ;have been repaired instead of bring shot down. It was ;launched in 2006 and the only problem is it lost ;communications<snip>

Having the eyes of the world on a secret military bird is not the the spooks what. The things it takes to fix the problem and the places they come from are hard to hide.

We also have a policy of not flying a shuttle mission unless there is a back up to bail us out. We don't have any thing ready and I don;t think we want to farm this one out to Russia.

Besides that we never shot down a satellite before and doing it with a quick rigged missile not made for the job demises the Chinese accomplishment a few moths ago and we can claim with a straight face it was for safety.

Seldom does the Navy get to make so many people happy so cheap. gc

Reply
Anonymous Poster
#5
In reply to #4

Re: Let’s Shoot Down a Satellite: An In-Depth Review (Part 2)

02/27/2008 6:21 AM

Would it have been possible to tow it father out into space? Would that have given us more time to get a chance to fix it? Just seems like a waste of time and money to blow it up.

Reply
Reply to Blog Entry 5 comments
Copy to Clipboard

Users who posted comments:

Anonymous Poster (2); Delmar (1); Gordon Couger (1); n1tck (1)

Previous in Blog: Let’s Shoot Down a Satellite: An In-Depth Review (Part 1)   Next in Blog: Let’s Shoot Down a Satellite: An In-Depth Review (Part 3)

Advertisement