THIS STORY HAS BEEN FORMATTED FOR EASY PRINTING

Back on Earth, satellite collision kicks up some dust

By Seth Borenstein and Douglas Birch
Associated Press / February 13, 2009
  • Email|
  • Print|
  • Single Page|
  • |
Text size +

MOSCOW - US and Russian officials traded shots yesterday over who was to blame for a huge satellite collision this week that spewed speeding clouds of debris into space, threatening other unmanned spacecraft in nearby orbits.

The smashup 500 miles over Siberia on Tuesday involved a derelict Russian spacecraft designed for military communications and a working satellite owned by US-based Iridium, which served commercial customers as well as the US Department of Defense.

A prominent Russian space specialist suggested NASA fell down on the job by not warning of the collision. But US space specialists said the Russian blamed the wrong agency.

The US military tracks the 18,000 objects in orbit, monitoring only certain threats because it lacks the resources to do everything, said Major Regina Winchester, spokeswoman for the US Strategic Command, which oversees the military's Space Surveillance Network.

Iridium spokeswoman Elizabeth Mailander said the company can move any of its 65 satellites out of the way if it gets a precise warning ahead of a crash. Such a warning was not made Tuesday, Mailander said.

But the company has never redirected a satellite before because the warnings they get aren't precise enough and there are just too many satellites to be constantly rejiggering their orbit, she said.

"Ours was where it was supposed to be and it was functioning," Mailander said. She said Iridium hasn't talked with Russian space officials.

No one has any idea yet how many pieces of space junk were generated by the collision or how big they might be. But the crash scattered space junk in orbits 300 to 800 miles above Earth, according to Major General Alexander Yakushin, chief of staff for the Russian military's Space Forces.

Specialists in space debris will meet next week in Vienna at a UN seminar to devise better ways to prevent crashes, said NASA orbital debris program manager Nicholas Johnson.

Igor Lisov, a prominent Russian space specialist, said yesterday he did not understand why NASA's debris specialists and Iridium had failed to prevent the collision, since the Iridium satellite was active and its orbit could be adjusted.

"It could have been a computer failure or a human error," he said. "It also could be that they only were paying attention to smaller debris and ignoring the defunct satellites."

But that job belongs to the US Department of Defense's Space Surveillance Network, which was created with NASA's help.

The network's top priority is protecting astronauts - and warning them if there is a threat to the International Space Station or manned spacecraft. And it gives NASA precise warnings for about a dozen satellites that could be maneuvered out of the way, something that happens once in a while, Johnson said.

There are 800 to 1,000 active satellites in orbit and about 17,000 pieces of debris and dead satellites, like the Russian one, that can't be controlled, he said. The US space tracking network doesn't have the resources to warn all satellite operators of every possible close call, Johnson and Winchester said.

"It's unfortunate that we cannot predict all of the collisions all of the time," said Winchester.

Lisov said the debris may threaten a large number of earth-tracking and weather satellites in similar orbits.

  • Email
  • Email
  • Print
  • Print
  • Single page
  • Single page
  • Reprints
  • Reprints
  • Share
  • Share
  • Comment
  • Comment
 
  • Share on DiggShare on Digg
  • Tag with Del.icio.us Save this article
  • powered by Del.icio.us
Your Name Your e-mail address (for return address purposes) E-mail address of recipients (separate multiple addresses with commas) Name and both e-mail fields are required.
Message (optional)
Disclaimer: Boston.com does not share this information or keep it permanently, as it is for the sole purpose of sending this one time e-mail.