At 04:05 UTC on July 26, 2026, a Starlink satellite and an operational U.S. spacecraft designated MONOLITH passed within a predicted 6 meters of each other in low Earth orbit. The Starlink-5262 MONOLITH conjunction had been flagged at maximum modeled collision probability for days. No collision happened. But the event puts a name and a timestamp on a pattern FODNews documented nine days earlier: the average interval between significant conjunction events in LEO has compressed to just 2.5 days.
What the Tracking Data Showed
Orbital monitoring platforms began flagging the encounter on July 23 — three days ahead of the predicted closest approach. The conjunction data was unambiguous: a minimum range of 0.006 km at a relative velocity of 5.794 km/s. Maximum collision probability was listed at 1.0, the ceiling of the modeled risk estimate.
In practice, that figure reflects positional uncertainty in orbital tracking, not a certainty of impact. Nevertheless, the event was classified as critical. Both operators required immediate monitoring and potential mitigation.
No collision occurred, consistent with the autonomous avoidance behavior SpaceX has built into the Starlink constellation. Starlink satellites execute maneuvers automatically when conjunction risk crosses defined thresholds, without waiting for ground intervention.
A Near-Miss in a Crowded Orbital Band
The July 26 event did not occur in isolation. Weeks earlier, the Zhuque-2E upper stage fragmented in LEO. That second stage — from a Chinese LandSpace rocket launched June 9 — scattered an estimated 100 to 150 new trackable debris pieces through the same altitude band. The debris field spans roughly 335 to 424 km at a 54.5-degree inclination, overlapping with newer Starlink satellites.
Starlink satellites executed nearly 50,000 collision-avoidance maneuvers in a single six-month window in 2023–2024 — double the prior rate, according to Nexi.fund Labs. SpaceX’s Stargaze platform launched in January 2026. It repurposes star tracker cameras across the constellation as a surveillance network. That generates roughly 30 million object transits per day, cutting conjunction detection latency from hours to minutes.
The July 26 outcome likely reflected that system working as designed. MONOLITH’s operational status — listed as “Operational” in tracking records — meant both spacecraft had autonomous mitigation pathways available. Had either been uncontrolled, no such option would have existed.
The Starlink-5262 MONOLITH Conjunction and the CRASH Clock
On July 21, FODNews reported on peer-reviewed research in Acta Astronautica that established the CRASH Clock — Collision Realization And Significant Harm Clock — as a measure of orbital fragility. As of May 2026, that clock stands at 2.5 days. That is the modeled time to a major collision if all LEO spacecraft simultaneously lost the ability to maneuver.
The CRASH Clock stood at 164 days in January 2018. It compressed to 62 days by early 2021 and fell to 11 days by early 2023. By this spring, it reached 2.5 days. The Starlink-5262 and MONOLITH near-miss is therefore not exceptional — it is a routine entry in a queue that turns over in under three days.
Tracking and Regulatory Gaps Remain
Autonomous avoidance mitigates risk; it does not resolve the underlying structural problem. The European Space Agency estimates more than one million pieces of potentially lethal debris orbit Earth. These objects are smaller than 10 centimeters — too small to track reliably, yet capable of destroying a satellite on impact.
Sensor development is progressing. A NASA/JAXA debris sensing system recently passed a critical design review aimed at better characterizing objects below 10 centimeters. Meanwhile, the FCC’s Part 100 satellite tracking mandate is pushing operators toward more rigorous conjunction data sharing. Passive removal concepts — including systems under development at UTEP — address the hardware already in orbit.
Regulatory requirements for responsible disposal, however, remain inconsistently enforced across operators and jurisdictions. The Zhuque-2E fragmentation illustrated that gap in June. The Starlink-5262 and MONOLITH conjunction illustrated it again in July.
The 2.5-day CRASH Clock was a statistical abstraction on July 21. The July 26 conjunction was a real event, with a real miss distance, in the same orbital environment the research describes. Both are telling the same story.
Subscribe to FODNews for independent coverage of orbital debris, airspace safety, and FOD incidents worldwide.
Sources
- KeepTrack.space — SpaceX Conjunction Brief, July 26, 2026
- Nexi.fund Labs — AI-Driven Autonomous Space Traffic Coordination, 2026
- FODNews — ‘CRASH Clock’ Research Puts LEO Collision-Risk Interval at 2.5 Days, July 21, 2026
- FODNews — Zhuque-2E Debris Scatters Near Starlink, ISS, June 17, 2026
- Ars Technica — A Chinese Rocket Breaks Apart Dangerously Close to the Starlink Constellation, June 2026
