People who follow spaceflight news hear the phrase "Kessler syndrome" more often every year. It sounds technical, and the full science is. The basic idea, though, is simple enough to explain over a kitchen table, and it is worth understanding, because it shapes whether the orbits we rely on stay usable.

This page is a plain-English guide. It explains what the debris cascade is, where the idea came from, one real event that shows how it works, and why many people now argue that the large, dead objects already in orbit need to be removed, not just avoided. At the end, there is a short note on where The Incognito, John Arwood's spacecraft concept, might fit. We have tried to keep that part modest and to stick to what the sources actually say.

What Kessler syndrome means

Kessler syndrome is the name for a chain reaction in orbit. When two objects collide in space, they don't simply bump and bounce. They break into many pieces. Each of those pieces is now another object that could hit something else, and each new hit makes more pieces. Past a certain point, the debris can keep multiplying from collisions alone, even if nobody launches anything new.

The European Space Agency describes it this way in its 2025 Space Environment Report: even without any additional launches, the number of space debris objects would keep growing, because fragmentation events add new debris faster than debris can naturally re-enter the atmosphere. ESA calls that runaway chain reaction Kessler syndrome, and warns that it can make certain orbits unsafe and unusable over time as debris collides and fragments again and again.

A useful way to picture it is a busy highway where every crash leaves debris in the lanes, and nobody ever comes to clear it. The road does not shut down after one accident. But each accident raises the odds of the next one, and the cleanup crew never arrives on its own.

Where the idea came from: Kessler and Cour-Palais, 1978

The idea is named for Donald J. Kessler. In June 1978, he and Burton G. Cour-Palais, both at NASA's Johnson Space Center in Houston, published a paper in the Journal of Geophysical Research titled "Collision Frequency of Artificial Satellites: The Creation of a Debris Belt."

Their argument, in their own summary, went like this. As the number of artificial satellites in Earth orbit increases, the probability of collisions between them also increases. Collisions would produce orbiting fragments, each of which would increase the probability of further collisions, leading to the growth of a belt of debris around the Earth. They noted that this process parallels certain theories about how the asteroid belt grew, but on a much shorter time scale, because satellites occupy a far smaller volume of space than asteroids do.

Using a mathematical model, they concluded that under certain conditions such a belt could begin to form within the twentieth century and could be a significant problem during the twenty-first. They also offered a hopeful point that is easy to forget: early action, through specialized launch constraints and operational procedures, could significantly delay the formation of the belt.

The paper itself does not use the phrase "Kessler syndrome." That name came into use later. But the core idea, collisions breeding more collisions, is right there in the 1978 abstract.

A real example: the 2009 collision over Siberia

For about three decades, the debris cascade was mostly a matter of models and careful warnings. On February 10, 2009, it became something people could point to.

According to NASA's Orbital Debris Program Office, that day Iridium 33, an operating U.S. communications satellite, and Cosmos 2251, a decommissioned Russian communications satellite, collided over extreme northern Siberia at an altitude of 790 kilometers. Their orbits crossed at nearly a right angle, and the collision speed was more than 11 kilometers per second. NASA described it as the first accidental hypervelocity collision of two intact spacecraft.

The first sign anything had happened was that one of the satellites stopped sending signals. Soon after, the U.S. Space Surveillance Network began detecting new objects along the paths of both spacecraft. By the end of March 2009, 823 of the larger debris pieces had been identified and cataloged, with more being tracked, and ground observations confirmed that a much greater number of smaller fragments had also been created. NASA's newsletter noted that the two clouds of debris extended through much of low Earth orbit.

Two details in that account are worth slowing down on. First, one of the two satellites was already retired. A spacecraft that had finished its job was still a large, fast-moving object sharing space with working satellites. Second, no one intended for this to happen. It was an accident between two objects that simply ended up in the same place at the same time. That is exactly the kind of event Kessler and Cour-Palais were describing in 1978.

How crowded is it now?

ESA's 2025 report gives a sense of scale. About 40,000 objects are now tracked by space surveillance networks, of which about 11,000 are active payloads. ESA estimates that more than 1.2 million debris objects larger than 1 centimeter are in orbit, large enough to cause catastrophic damage, with more than 50,000 of those larger than 10 centimeters.

ESA also reports that 2024 saw several major fragmentation events, along with smaller ones, adding at least 3,000 tracked objects in a single year. And in certain heavily used low-Earth orbit altitude bands, the number of debris objects is now the same order of magnitude as the number of active satellites.

Those numbers belong to ESA, not to us, and they will change from year to year. We include them only to show why the agencies that track this problem have become more direct in how they talk about it.

Why removing large derelicts matters

There are two broad ways to deal with orbital debris. One is mitigation: designing and flying missions so they leave less mess behind. That includes venting leftover fuel and batteries so dead hardware does not later break apart, and moving satellites out of busy orbits when their work is done. ESA reports that compliance with these practices is slowly improving, especially in the commercial sector.

The other is remediation: actually removing objects that are already up there. ESA's conclusion on this point is plain. Its report states that not adding new debris is no longer enough, and that to prevent the runaway chain reaction from escalating and making certain orbits unusable, active debris removal is required.

Why focus on large derelicts, such as dead satellites and spent rocket bodies? The 2009 collision helps answer that. When two big, intact objects meet, the result is not one new piece of debris but hundreds of cataloged fragments and far more small ones. ESA notes that satellites left in their operational orbit at the end of their mission are at risk of fragmenting into clouds of debris that linger for many years. A large derelict is, in a sense, a future debris cloud waiting for the wrong moment. Removing it before that moment comes takes away many possible fragments at once.

None of this is easy. Getting close to an object that was never designed to be approached, taking hold of it, and moving it somewhere safe is hard engineering, and it costs money. But the direction of expert opinion is clear enough: prevention by itself will not hold the line.

Where The Incognito concept fits

The Incognito is John Arwood's idea for a garbage truck in the sky: a self-sustaining orbital spacecraft concept for collecting and disposing of debris. It comes from a career spent in waste collection on the ground. It is a concept, not a flying prototype, and the design is patent pending.

As described on The Concept and Our Specs, the craft would use ion thrusters for efficient in-space travel, with an onboard nuclear reactor as its main power source and solar cells around the exterior as backup. It is meant to haul large debris, including objects larger than its own body, and the site describes it as capable of hauling satellites twice its size over a longer-than-average time and distance. Thrusters across its exterior are intended to give it the agility needed to approach uncooperative objects, and modular add-ons would let the same vehicle take on different tools for different jobs.

The proposed concept of operations is straightforward: launch to orbit on a conventional rocket, use low-refuel ion transit to reach a target, locate and capture the debris, then lower its orbit so it burns up in the atmosphere, and move on to the next object.

In other words, the concept is aimed at exactly the category of object that matters most in a debris cascade: large, dead hardware. We don't claim it is the answer, or the only answer. ESA's own report describes active debris removal and in-orbit servicing demonstrations in development, and others are working on the problem too. The Incognito is one proposal, from someone who has spent a working life hauling material away so places stay usable. If you have questions about how it would work, the FAQ is a good place to start.

If you want to talk

John Arwood is looking for serious partners to help take The Incognito from concept toward reality, whether through acquisition, licensing, or a development partnership. If your organization works on space sustainability, launch, or in-space services, please read For Partners & Acquirers and reach out through Direct Communications.

Sources

  • Donald J. Kessler and Burton G. Cour-Palais, "Collision Frequency of Artificial Satellites: The Creation of a Debris Belt," Journal of Geophysical Research, Vol. 83, No. A6, June 1, 1978. Scanned copy: Internet Archive.
  • NASA Orbital Debris Program Office, "Satellite Collision Leaves Significant Debris Clouds," Orbital Debris Quarterly News, Vol. 13, Issue 2, April 2009: orbitaldebris.jsc.nasa.gov.
  • European Space Agency, "ESA Space Environment Report 2025": esa.int.