Design, deliver, and run enterprise blockchain workloads quickly and easily.
All servers and systems
Space junk rarely makes the news. It usually stays in space, orbiting the planet, and we only notice when things fall out of the sky.
Recently, for example, there was much scientific hubbub because an uncontrolled Chinese space lab crashed into the earth. If the 8.5-ton Chinese Tiangong had broken apart or run into another orbiting spacecraft, it would have significantly added to the debris in low Earth orbit (LEO)—a place that doesn’t need any more junk. (The Pacific Ocean, where many decommissioned spacecraft are directed, doesn’t need any more junk either.)
Ultimately, the Chinese Tiangong 1 had no impact on Earth or in space. However, it is an important reminder for the critical need for a strategic plan to deal with space junk. Everything floating around up there threatens to damage active communications satellites, the International Space Station (ISS), and other space systems.
The good news is that a lot of work and research is being done to try to address the problem. And a big problem it is: NASA reports more than 100 million pieces of orbital debris measuring smaller than 1 centimeter and more than 21,000 pieces of orbital debris larger than 10 cm. The estimated population of particles between 1 and 10 cm in diameter is approximately 500,000, and the number of particles smaller than 1 cm exceeds 100 million. Most of this junk is in Earth’s LEO, typically defined as at an altitude of between 160 to 2,000 kilometers (or 99 to 1,200 miles) above Earth's surface. Most satellites, the ISS, and the Hubble Space Telescope reside in LEO.
According to NASA, orbital debris is the primary threat to spacecraft, satellites, and astronauts. In the best-case scenario, collisions with orbital debris can pit or damage spacecraft; in the worst case, they can cause catastrophic failures. Averaging speeds of 10 km per second (22,000 mph), a 1-cm paint fleck is capable of inflicting the same damage as a 550-pound object traveling 60 miles per hour on earth. A 10-cm projectile would be comparable to 7 kilograms of TNT. (See NASA's Space debris sensor video for inspiration.)
So where, specifically, is all this debris coming from? NASA's Orbital Debris Program Office says that as of 2016 (the last time it posted a top 10 space junk missions account), by far the source of the greatest amount of orbital debris remains the Fengyun-1C spacecraft, which was the target of a People’s Republic of China anti-satellite test in January 2007. “This satellite alone now accounts for 3,428 cataloged fragments or almost 20 percent of the entire population of catalogued manmade objects in orbit about the planet. Additional debris from this test and other events are currently being tracked by the U.S. Space Surveillance Network (SSN) and are officially cataloged on a routine basis,” NASA states. In 2010, there were 2,841 pieces of junk from this spacecraft.
Image credit: NASA, Orbital Debris, Quarterly News. See complete chart here.
Orbital debris can include all manner of space system parts from derelict spacecraft and upper stages of launch vehicles. That includes debris intentionally released during spacecraft separation from its launch vehicle or during mission operations, and tiny flecks of paint from small particle hits on existing spacecraft, NASA says.
The second and fourth most significant satellite debris-makers were the Cosmos 2251 and Iridium 33 spacecraft, which were involved in the first-ever accidental satellite collision in February 2009. More than 68 percent of the Cosmos debris cloud remains on orbit, and only 58 percent of the Iridium cloud is on orbit, due in part to the higher area-to-mass ratio bias of the latter cloud. Because of their relatively high altitude, these clouds will continue to present a hazard for decades to come, according to NASA.
NASA also notes that 10 out of the 5,160 space missions that have launched since 1957 account for approximately one-third of all cataloged objects now in Earth orbit.
High-performance computing in space takes a giant leap as NASA runs the HPE Spaceborne Computer on the ISS to test potential technologies for future missions to Mars.
With the potential increase of space debris comes one of the scariest scenarios, say space experts. Known as the Kessler syndrome, after NASA scientist Donald Kessler wrote a paper on the subject in 1978, it defines a scenario in which the density of debris in LEO is high enough that collisions between objects could set off a cascade of disastrous collisions between the debris and orbiting spacecraft or satellites. That would create more debris and kill even more satellites and other spacecraft. If you saw the movie “Gravity,” you witnessed a depiction of the Kessler Syndrome on screen.
According to NASA, “Kessler demonstrated that once the amount of debris in a particular orbit reaches critical mass, collision cascading begins even if no more objects are launched into the orbit. Once collisional cascading begins, the risk to satellites and spacecraft increases until the orbit is no longer usable. Kessler proposed it would take 30 to 40 years for such a threshold to be reached, and today, some experts think we are already at critical mass in LEO.”
NASA says its role in the space debris arena is to ensure that it researches and develops future spacecraft that don’t add to the debris field. "Orbital debris poses a risk to continued reliable use of space-based services and operations and to the safety of persons and property in space and on Earth. The United States shall seek to minimize the creation of orbital debris by government and non-government operations in space in order to preserve the space environment for future generations," the agency wrote.
Other space agencies across the globe have their own orbital debris prevention components, but there is no formal global agreement on how to reduce the debris problem.
There is a ton of ongoing work to discover and perhaps one day remediate the problem. Projects include the following:
This article/content was written by the individual writer identified and does not necessarily reflect the view of Hewlett Packard Enterprise Company.