Self-guided rehearsal · Diplo Space

The Conjunction Nobody Owns.

September 2019, replayed from the public record: a European science satellite and a satellite from a large commercial constellation converge, with no traffic rule that says who moves and no channel between the two operators but email. You hold the maneuver watch. Four decisions, about ten minutes, every fact sourced. No login, no score.

This is a rehearsal, not a forecast. The situation is constructed. The mechanism is not: in 2009 an active satellite and a defunct one met at 11.7 km/s, and no rule obliged anyone to move, to warn, or to answer for it. Watch that one on the real catalogue

Self-guided decision rehearsal · ~10 minutes · no login

Take the watch.

September 2019, replayed from the public record. An Earth-science satellite operated by the European Space Agency and a satellite in a large commercial constellation are on converging paths, days out. There is no traffic rule that says who moves, and no channel between the two operators except email. You hold the maneuver watch on the European side. Your choices here are yours; what actually happened is shown at the end, and it is not a grade.

Sources: European Space Agency · Diplo Space, Inc.

Your seat: collision-avoidance duty officer

You monitor conjunction warnings for the science mission and you can plan and command avoidance burns on your own spacecraft. What you cannot do is order anyone else to move. ESA, describing this event, put it plainly: in the absence of traffic rules and communication protocols, collision avoidance depends entirely on the pragmatism of the operators involved.

Sources: European Space Agency

Ground rules
  • This is an open, low-stress, no-fault rehearsal. There are no wrong answers, only decisions and what they cost.
  • Choosing not to act is a real option, and it is recorded as a finding, not a failure.
  • There are no hidden materials and no trick options.
  • The scenario clock supplies the urgency. There is no countdown and no score: discussion exercises are examined, never graded.
Assumptions & artificialities
  • The timeline and probabilities follow the documented event; sources are listed under every step and in the panel below.
  • Your choices don't change orbital mechanics. They change who carries the decision, and when.
  • Consequence notes describe what the record shows and what your call trades away. They never declare a policy correct.
▸ Every source in this rehearsal (10), with retrieval dates
  • European Space Agency · “ESA spacecraft dodges large constellation,” Space Safety, September 3, 2019. Verified against the loaded source, July 20, 2026. Open it ↗
  • Diplo Space, Inc. · Diplo Space, Field Note 04, “Who Owns the Traffic Lane?” (September 2026), section 6: when coordination fails (our own publication, used for framing). Verified against the loaded source, July 20, 2026. Open it ↗
  • Forbes · Jonathan O’Callaghan, “SpaceX Declined To Move A Starlink Satellite At Risk Of Collision With A European Satellite,” September 2, 2019 (the early probability estimate and the pre-maneuver exchange; the report describes the emailed reply as “the first contact that had been made with SpaceX, despite repeated attempts by Krag and his team to get in touch since Starlink launched”). Verified against the loaded source, July 20, 2026. Open it ↗
  • SpaceNews · Jeff Foust, “ESA spacecraft dodges potential collision with Starlink satellite,” September 2, 2019 [subscription required; ESA's own account of the maneuver is cited above]. Verified against the loaded source, July 20, 2026. Open it ↗
  • European Space Agency · ESA Space Debris Office, “Collision Avoidance Challenge” (teams alerted about two days before a close approach; final decision typically one day prior). Verified against the loaded source, July 20, 2026. Open it ↗
  • Forbes · Jonathan O’Callaghan, “SpaceX Says A ‘Bug’ Prevented Its Starlink Satellite Avoiding A Collision With A European Satellite,” September 3, 2019 (SpaceX’s statement on the paging bug). Verified against the loaded source, July 20, 2026. Open it ↗
  • European Space Agency · “Automating collision avoidance,” Space Safety / Space Debris. Verified against the loaded source, July 20, 2026. Open it ↗
  • UN Office for Outer Space Affairs · UN Satellite Operator Contact Hub, soch.unoosa.org — landing page, disclaimer and operator registration form (self-described as “a restricted coordination directory maintained by” the Office; “is not a real-time tracking system”); announced on the Office’s LinkedIn page, September 2026, with no launch date stated and no participation figure published. Verified against the loaded source, September 10, 2026. Open it ↗
  • United Nations (COPUOS) · Guidelines for the Long-term Sustainability of Outer Space Activities (ST/SPACE/79), Guideline B.1, “Provide updated contact information and share information on space objects and orbital events” — adopted by COPUOS June 2019 (A/74/20, annex II), welcomed by General Assembly resolution 74/82; routes updated contact information for conjunction-assessment entities through the Office (voluntary, non-binding). Verified against the loaded source, September 10, 2026.
  • United Nations (UNOOSA) · A/AC.105/C.1/2025/CRP.24, “United Nations Space Bridge on Global Space Traffic Coordination,” conference room paper submitted by UNOOSA, February 4, 2025, para. 7 (the Office has kept such a contact list since 2019; an October 2024 dialogue urged it to “explore how to operationalize the existing list”). Verified against the loaded source, September 10, 2026.

The event itself is in the record, with sources.

▸ About this rehearsal: type, scope, and what it doesn’t do

Type: a self-guided, single-seat decision rehearsal built on one documented event. In strict HSEEP terms (HSEEP is the U.S. government’s standard for emergency-management exercises), a branching web exercise sits closer to a “game” than a tabletop. We say so because precision about exercise types is part of doing this credibly.

Scope: one seat, four decisions, policy- and coordination-level choices only, ~10 minutes. The timeline and probabilities follow the documented September 2019 event; your choices and notes stay on your device.

What it deliberately isn’t: there is no score, because discussion exercises are examined, never graded. No countdown timer, because tabletops are low-stress by design; the scenario clock supplies the urgency. And no simulated collision on the “hold” path: the record shows what actually happened, and holding is written up as a finding about the system, never a failure of yours.

Want the two-seat version, both operators live on one clock, with a facilitator pushing back? See formats and pricing. Pilot sessions run 90 minutes, $5K–$20K, and you keep the after-action record.