Low Earth orbit used to offer satellite operators a comfortable buffer; it now resembles a countdown timer with very little slack. A recent preprint study proposes a new yardstick for how quickly things can unravel if large numbers of satellites suddenly stop responding to commands. The metric, called the Collision Realization And Significant Harm (CRASH) Clock, estimates the time between a widespread loss of satellite control and the first collision likely to create dangerous debris. By the end of 2025, the study places that clock at about 2.8 days, with a 30% chance of a collision within 24 hours under the same “everyone goes dark” assumption.
The number is attention-grabbing, but the trend line is the real story. The same framework estimates that a comparable scenario in 2018 would have allowed roughly 128 days before a first major collision became statistically likely. The rapid compression of that window tracks with a much denser orbital neighborhood: by May 2025, there were at least 11,700 active satellites around Earth, concentrated heavily in LEO, and representing a 485% increase from the end of 2018.
In everyday operations, conjunction warnings, tracking networks, and routine maneuvers keep most satellites out of each other’s way. The CRASH Clock is aimed at the scenario where those safeguards fail at once through a technical malfunction, cyber disruption, or, most plausibly, severe space weather. Study co-author Aaron Boley described it as “a statistical measure of the timescale expected for a close approach that could give rise to a collision,” adding that it can function as “an environmental indicator that helps to evaluate the overall health of the orbital region while enabling people to conceptualize just how much or how little room there is for error.”
Space weather earns special scrutiny because it can degrade navigation and communications while simultaneously changing the atmosphere satellites fly through. Solar activity can heat Earth’s upper atmosphere, increasing drag and making orbital predictions noisier, while radiation can interfere with onboard systems. That coupling higher uncertainty, less control turns “traffic management” from careful planning into a race against time, especially when many spacecraft share similar altitude shells.
That is where the downstream risk becomes less about a single impact and more about compounding consequences. A first debris-generating collision can scatter fragments across busy lanes, raising the probability of follow-on strikes and nudging the system toward the Kessler Syndrome threshold, where cascading collisions can make LEO difficult to use safely for long periods. The preprint avoids claiming a precise tipping point, because the cascade depends on variables such as debris distribution, impact energies, and how quickly operators can resume coordinated maneuvering.
Outside the modeling, the broader engineering problem looks increasingly like governance and operations as much as physics. An analysis of space traffic norms has noted an absence of actual “Rules-of-the-Road” at the operational level in current international instruments, even as orbits grow more complex with large constellations and more frequent maneuvering. Meanwhile, guidance designed to protect astronomy can introduce trade-offs: research modeling constellation operations found that lowering satellites to below 600 km can reduce optical interference, while increasing collision pressure by compressing more spacecraft into a smaller orbital volume.
CRASH Clock numbers may shift as the work is refined, but the lesson remains stubbornly practical: in a crowded LEO, resilience is measured not only by how well satellites avoid each other on good days, but by how quickly the entire system can recover on the bad ones.
