In February 2022, SpaceX launched 49 Starlink satellites into low Earth orbit. Within 48 hours, a geomagnetic storm that barely registered as moderate on the NOAA space weather scale (G1 to G2) swelled the upper atmosphere enough to drag 38 of them back down. The satellites never had a chance to reach their operational altitude. They burned up.
That episode was expensive but contained. A new preprint, posted in June 2025, asks what happens when a similar storm hits an orbit packed not with 49 freshly deployed satellites but with thousands of active ones flying in close formation, all relying on continuous ground-commanded maneuvers to avoid each other. The answer, according to the researchers’ model: the first catastrophic collision would arrive in roughly 2.8 days.
The CRASH Clock: measuring the margin that keeps satellites apart
The metric at the center of the study is called the CRASH Clock, short for Collision Realization And Significant Harm. It works by taking a snapshot of every tracked object in low Earth orbit, calculating all the close approaches between them, and then asking: if every active satellite simultaneously lost the ability to dodge, how long before two of them meet at orbital speed?
Using a catalog snapshot from June 25, 2025, the researchers found that window has shrunk to about 2.8 days. When they ran the same method against 2018 data, before SpaceX, OneWeb, and other operators began filling low Earth orbit with megaconstellation hardware, the margin was substantially wider. The difference reflects a simple reality: more satellites in similar orbital shells means more potential collisions, and the gap between “everything is fine” and “something hits something” gets thinner every year.
The preprint has not yet undergone formal peer review, and the 2.8-day figure is a modeled estimate tied to one catalog epoch, not a stopwatch running in mission control. But the orbital mechanics underneath it are standard, and the foundational research it builds on, including the 1978 Kessler and Cour-Palais paper that first described how a collision cascade could render an orbital band unusable, has been cited in debris policy for decades.
Why a moderate storm is enough to start the clock
The February 2022 Starlink loss demonstrated the mechanism. A geomagnetic storm heats and expands the thermosphere, the thin upper layer of atmosphere where low-orbit satellites fly. That expansion increases drag on every object in the affected altitude band. Satellites slow down, their orbits decay, and crucially, their predicted positions shift in ways that ground-based tracking systems struggle to keep up with in real time.
A NOAA-hosted technical analysis of the 2022 event confirmed that thermospheric density enhancement was the direct cause of the satellite losses. A separate NASA-hosted report framed the episode as a warning: storms of that magnitude are not rare, and their capacity to degrade orbital predictability across an entire altitude shell poses a systemic risk as satellite populations grow.
What makes this relevant to the CRASH Clock is that collision avoidance depends on two things operators must have simultaneously: accurate knowledge of where every nearby object is, and the ability to fire thrusters to move out of the way. A geomagnetic storm can degrade both. Atmospheric drag shifts orbits faster than tracking updates can follow, and if the storm also disrupts ground-station communications or GPS signals that satellites use for navigation, operators may lose the ability to command maneuvers precisely when those maneuvers matter most.
A Kessler-style problem at megaconstellation scale
In 1978, NASA scientists Donald Kessler and Burton Cour-Palais described a feedback loop: one collision in orbit produces debris, that debris causes more collisions, and the cascade eventually makes an entire altitude band too dangerous to use. For decades, the scenario was treated as a long-term concern, something that might unfold over years or decades if derelict rockets and dead satellites accumulated unchecked.
The CRASH Clock reframes the timeline. It suggests that in today’s congested low Earth orbit, the trigger for a Kessler-style cascade is not a slow buildup of junk but a short-duration event that temporarily disables the active management keeping everything safe. A moderate solar storm lasting a day or two could be that trigger.
The numbers underscore the shift. As of early 2025, more than 10,000 active satellites occupy low Earth orbit, a figure that has roughly tripled since 2020, driven largely by SpaceX’s Starlink constellation. SpaceX has regulatory approval to eventually operate up to 12,000 satellites and has applied for as many as 42,000. Amazon’s Project Kuiper plans to deploy more than 3,200. Each addition tightens the geometry that the CRASH Clock measures.
ESA’s 2025 Space Environment Report documents the trend from the institutional side: rising object counts, more frequent fragmentation events, and a growing volume of collision-avoidance maneuvers across all operators. The report does not calculate a collision timeline, but its data on conjunction frequency supports the same conclusion the CRASH Clock reaches from a different angle. Operators are maneuvering more often because they have to, and the system’s tolerance for any interruption in that activity is shrinking.
What operators have not said
No major satellite operator has publicly disclosed a contingency plan for a scenario in which a geomagnetic storm simultaneously degrades tracking accuracy and disrupts maneuver commanding across a large constellation. SpaceX, which operates the largest fleet in low Earth orbit, has described its autonomous collision-avoidance system in general terms but has not published details about how that system performs when the orbital catalog it relies on becomes unreliable due to atmospheric disturbances.
Some satellites may carry onboard logic that triggers safe-mode altitude changes during severe space-weather alerts. Others might retain limited autonomous maneuvering even if ground contact is lost. But because no operator has described such capabilities in detail, outside analysts cannot assess how much these measures would extend the 2.8-day window. The gap between what operators may be doing internally and what the public record shows is wide enough that the CRASH Clock’s worst-case assumption, total loss of avoidance capability, cannot be confidently ruled out or confirmed.
The February 2022 event illustrates the transparency problem. SpaceX publicly acknowledged losing satellites but never released detailed maneuver logs, onboard telemetry, or a timeline of decision points during the storm. Analysts can confirm the scale of the failure from external tracking data, but they cannot reconstruct how SpaceX’s systems responded in real time or identify where specific decisions broke down. Without that operational detail, lessons from the event remain incomplete.
What a collision would actually disrupt
A catastrophic collision between two satellites in a densely populated orbital shell would not just destroy the spacecraft involved. At closing speeds that can exceed 14 kilometers per second, the impact would produce thousands of trackable debris fragments and potentially millions of smaller pieces, each capable of damaging or destroying another satellite. In a shell already packed with active hardware, some of that debris would cross the orbits of other constellation members within hours.
The services at risk are not abstract. Starlink provides broadband internet to more than four million subscribers across dozens of countries, including in conflict zones and disaster areas where it may be the only connectivity available. Other low-orbit constellations support maritime tracking, aviation surveillance, weather observation, and military communications. A debris cascade that forced operators to deorbit satellites or abandon an altitude band would degrade or eliminate those services, with recovery timelines measured in years, not weeks.
Where the science stands as of June 2025
The CRASH Clock is a new metric, and its 2.8-day estimate will need to survive peer review, replication with different catalog epochs, and stress-testing against varying assumptions about maneuver rates and storm intensities before it can be treated as a definitive threshold. The researchers have been transparent about its limitations: it uses a single catalog snapshot, it assumes total and simultaneous loss of avoidance capability, and it does not account for partial or autonomous responses that some satellites might execute independently.
But the physical mechanisms behind the warning are not speculative. Geomagnetic storms measurably alter drag profiles in low Earth orbit. Dense constellations measurably increase conjunction rates. And the loss of maneuvering capability measurably removes the primary tool operators use to manage those conjunctions. Each of those statements is supported by peer-reviewed research and operational data stretching back years.
What the CRASH Clock adds is a way to quantify how those factors interact at current population levels, and the number it produces is uncomfortable. A margin of 2.8 days means that any disruption lasting longer than a long weekend, whether from a solar storm, a cyberattack on ground infrastructure, or a cascading software failure across a constellation’s flight control system, could push the orbital environment past the point where passive safety is enough. The question facing operators and regulators is no longer whether such a disruption is possible, but whether the plans to survive one actually exist.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
