It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by TeslaandLyne
We know whats going on in orbit, yeah sure we do.
Looks like the old Russian satellite had move down in orbit.
The debris objects shown in the images are an artist's impression based on actual density data. However, the debris objects are shown at an exaggerated size to make them visible at the scale shown.
Public Information Statement
Issued by NWS Jackson, KY
Home | Current Version | Previous Version | Text Only | Print | Product List | Glossary On
Versions: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
000
NOUS43 KJKL 140445
PNSJKL
KYZ044-050>052-058>060-068-069-079-080-083>088-104-106>120-141030-
PUBLIC INFORMATION STATEMENT
NATIONAL WEATHER SERVICE JACKSON KY
1145 PM EST FRI FEB 13 2009
...POSSIBLE SATELLITE DEBRIS FALLING ACROSS THE REGION...
The national weather service in jackson has received calls this evening from the public concerning possible explosions and...or earthquakes across the area. The federal aviation administration has reported to local law enforcement that these events are being caused by falling satellite debris. These pieces of debris have been causing sonic booms...resulting in the vibrations being felt by some residents...as well as flashes of light across the sky. The cloud of debris is likely the result of the recent in orbit collision of two satellites on tuesday...february 10th when kosmos 2251 crashed intoiridium 33.
'DODGEBALL' TO AVOID DEBRIS
Marine Corps General James Cartwright, vice chairman of the Joint Chiefs of Staff and a former head of the command that runs U.S. military space operations, said countries with satellites in space will have to play "dodgeball" for decades to avoid debris from the collision. It occurred about 485 miles
Originally posted by TeslaandLyne
That is in between Perigee: 778 km (483 mi) and Apogee: 803 km (498 mi).
So one Iridium was purposely moved into the Russian military
satellite to cause an incident.
Iridium 33
* *Owner:* Iridium LLC
* *Technical operator:* The Boeing Co. under
subcontract
* *Manufacturer: *Motorola, Inc.
* *Launched: *14 September 1997
* *Orbit:* near-circular 776 km x 86.4 degrees polar orbit
Iridium 33, an operational spacecraft in the Iridium phone satellite
constellation, and Kosmos 2251, a defunct Russian military satellite,
have collided in low-Earth orbit. The crash took place on 10 February
2009 at 1656 UTC over northern Siberia, resulting in the destruction of
both spacecraft.
Kosmos 2251, a Strela store-and-dump communications satellite, was
launched in June 1993 aboard a Kosmos 3M rocket from Plesetsk, Russia.
The 900-kg satellite was placed in a 778 km x 803 km x 74 degrees orbit.
It is likely to have operated for no more than a few years.
"While this is an extremely unusual, very low-probability event, the
Iridium constellation is uniquely designed to withstand such an event,
and the company is taking the necessary steps to replace the lost
satellite with one of its in-orbit spare satellites," Iridium stated.
But that's not the real problem.
Using a computer model, British space debris expert Hugh Lewis predicted
10,000 tennis-ball-sized debris shards - more than triple the number
created in China's anti-satellite weapon test in January 2007. "There
was more energy here than in the Chinese ASAT test so we'll see more
debris," he was quoted as saying by New Scientist.
Iridium spokeswoman Liz DeCastro said the company had had no advance
warning of an impending collision. "If the organisations that monitor
space had that information available, we are confident they would have
shared it with us." The company (or its subcontractor Boeing) apparently
did not perform own analyses.
Retired U.S. Air Force General John Campbell, Iridium's executive vice
president for government programmes, in 2007 told a forum
hosted by the George C.
Marshall Institute that Iridium had been receiving a weekly average of
400 conjunction reports from the U.S. Strategic Command's Joint Space
Operations Center.
"The ability actually to do anything with all the information is pretty
limited," he said, describing a kind of data overload. The conjunction
reports were issued every time a potential threat object was to pass
within five kilometers of a commercial satellite, he said.
It has been pointed out that Russia was also to blame for the incident.
Certainly Russian officials could have warned Iridium or its
subcontractor Boeing of the possibility of an impending collision.
However, we will never know whether Iridium or Boeing would have reacted
to such a warning -- or ignored it like the warnings from USSTRATCOM.
Iridium spokeswoman Elizabeth Mailander confirmed that the company never
performed a single collision avoidance manoeuvre in the entire history
of its satellite constellation.
/Last updated: 16 February 2009/
The resulting "unprecedented" debris field, says Lewis, is still being analysed by space agencies. But he expects it to create an extra 10,000 debris shards varying in size from centimetres to tennis-ball sized – more than triple the number created in the ASAT test.
"There was more energy here than in the Chinese ASAT test so it's possible we'll see more debris," Lewis says.
Nicholas Johnson, chief scientist for orbital debris at NASA's Johnson Space Center in Houston, Texas, says the exact amount of debris generated in the collision depends on the geometry of the smashup, which is not yet known.
Originally posted by Anonymous ATS
reply to post by Alxandro
the most sophisticated systems monitor these satellites and with the use of space geometry, gravitational laws, copernicus, kepler and Isaac Newton, they can plot the trajectory of all these space objects and make adjustments using their retro rockets.. I would surmise that if one satellite hit another I would say it was done deliberately......
Originally posted by GriffinRD
I'd have to agree, NORAD does not make these kinds of mistakes in tracking, the 5km collision report would have been issued, notifications would have occured.
If DoD and other dark agencies have access to the Iridium network then they also have controls.
It looks more like they did not have time to react to the change, but to admit that, would be to admit something or someone changed one or both of the Sat's orbital trajectories. Furthermore, you would need some kind of ridiculous accuracy to plan this, far beyond what you could do just by observing and plotting from the ground. Minor variations in atmospheric drag would throw off any attempt to deliberately do this without terminal guidance.
Richard Hoagland put out his hyper dimensional theory of Sat #"33" and its true nature,
NASA was concerned enough by the lack of accurate tracking data on the debris field caused by the recent collision to postopone the Shuttle launch. But that is what is being said publicly.
Originally posted by ngchunter
How do we know notifications didn't occur? The relative inclination was so high that the window for impact had to be infintesimaly small.
Originally posted at CASTOR
Iridium alleged that NORAD did not warn them of the imminent threat of a collision between Iridium 33 and Cosmos 2251. The Pentagon stated that NORAD cannot keep an eye on everything at all times. This might be construed as a partial admission that NORAD is stretched to the limit as far as space surveillance is concerned. Wouldn't you be if you had to keep track of (at least) 14,000 individual objects and prevent any of them from hitting something active? The Russians have stated that Cosmos 2251 has been a dead satellite since 1995 and therefore could not be manoeuvred.
What if NORAD had indeed warned Iridium of an imminent collision and Iridium simply ignored it? It is certain that NORAD must have proof if this is indeed the case. Iridium claims that the collision reports were not accurate enough, saying that if they manoeuvre their satellite, they might actually cause the collision they are trying to avoid. The truth depends on the accuracy of the collision reports.
NORAD did not have the ability to manoeuvre the Iridium 33 satellite. Iridium did not have the ability to accurately predict collisions, although they could have access to the TLEs generated by NORAD (on SpaceTrack). Using the TLE's they could have designed their own collision avoidance software. CASTOR used the TLEs from both Iridium 33 and Cosmos 2251 generated before the collision, and found that at the time of collision, the two satellites were predicted to be less than 100 metres apart! if CASTOR can do this after the fact, then Iridium theoretically could have done this before the fact and might have prevented the collision.
Originally posted by ngchunter
Why would they control the satellites if they're a customer? Put another way, why would they bother being customer if they control the satellites? They don't.
Originally posted by ngchunter
To me it looks like they didn't bother to react because the risk of impact was fairly low given the extreme relative speed involved. If the orbit had suddenly changed for one of the satellites someone would have noticed. In fact, you could find out for yourself by requesting the information out of the archives:
Originally posted by ngchunter
It's a comm sat, it handles communication for satellite phones, my wife knows this for a fact from first hand experience with Iridium.