SpaceX Calls for Better Orbital Coordination After Starlink Near-Misses

SpaceX is calling for stronger coordination among satellite operators after repeated near-miss incidents involving Starlink spacecraft. The company’s position reflects a growing challenge in low Earth orbit: collision avoidance depends not only on tracking satellites, but also on accurate data-sharing and timely communication between the organizations operating them. Source 1

Reports say SpaceX wants operators to exchange more information about spacecraft positions and projected paths. Another report says Starlink experiences hundreds of near-misses annually, although the meaning of “near miss” depends on the distance threshold, tracking accuracy and reporting method. Source 3

The issue extends beyond Starlink. Low Earth orbit contains communications satellites, Earth-observation spacecraft, scientific missions, crew vehicles, rocket bodies and debris. As more objects use similar orbital regions, collision avoidance requires shared systems rather than isolated company procedures.

What SpaceX Is Asking Operators to Do

Improve Information-Sharing

SpaceX’s reported request is straightforward: satellite operators should share better information about where their spacecraft are and where they are expected to travel. The goal is to give operators more time and confidence when assessing potential conjunctions, the term used for close approaches between objects in space. Source 7

Collision avoidance cannot depend on one company acting alone. A Starlink satellite may encounter another Starlink spacecraft, a competitor’s satellite, a government vehicle or debris. Each encounter can involve separate tracking systems, communication channels and operational rules.

Effective coordination may require participation from commercial satellite companies, government agencies, military and civil tracking organizations, launch providers, scientific missions and independent space-surveillance networks.

The available reports support a broad call for improved coordination and data-sharing. They do not provide a complete policy proposal, implementation schedule or governance structure.

Share More Precise Trajectory Data

A satellite’s current position is only a snapshot. Operators also need to estimate where it will be at a specific future time. This requires trajectory data describing movement, altitude, direction, speed and the uncertainty around each prediction.

Useful information may include:

• Current spacecraft position
• Predicted future position
• Orbital altitude and velocity
• Expected uncertainty range
• Planned maneuvers
• Recent orbital changes
• Operational information that could affect the spacecraft’s path

Outdated or incomplete information can make an encounter difficult to assess. Two projected paths may appear to intersect, while updated maneuver data shows that the spacecraft will pass safely. The opposite can also occur: an apparently safe approach may become more concerning after a maneuver or tracking update.

Support Coordinated Collision Avoidance

Detecting a possible conjunction is only the first step. Operators must decide whether a maneuver is necessary and, if so, which spacecraft should move. They may need to determine:

1. Whether the predicted encounter presents a meaningful risk.
2. Which spacecraft has the greater ability to maneuver.
3. When a maneuver should occur.
4. Whether the maneuver could create another conflict.
5. How the decision will be communicated to other operators.

Without communication, two operators could initiate avoidance maneuvers that create a new approach or increase uncertainty. Consistent procedures can reduce that risk by establishing how warnings are exchanged and decisions are recorded.

What Starlink Near-Misses Reveal

Starlink operates a large satellite network in low Earth orbit. A larger constellation naturally creates more opportunities for close approaches, both within the network and with spacecraft operated by other organizations.

Potential encounters may involve commercial communications satellites, Earth-observation spacecraft, government vehicles, rocket stages, inactive satellites and orbital debris. This does not mean every close approach represents an imminent collision. It means a large constellation must process many potential encounters and respond quickly when predictions indicate elevated risk.

A report from Aerospace Global News says Starlink satellites experience hundreds of near-misses each year. Source 3

That figure requires careful interpretation. Near-miss totals can vary according to separation distance, tracking accuracy, inclusion of debris, object status, reporting methodology and whether multiple alerts concern the same event.

A high number of alerts does not mean every event was close to an unavoidable collision. Some encounters may have substantial uncertainty, while others may be resolved through routine maneuvering or improved tracking data. The figure does show the scale of the management challenge: operators must distinguish low-risk alerts from serious threats and coordinate actions across organizational boundaries.

Near misses are warnings, not proof of a collision crisis. They reveal where tracking, communication or decision-making systems face pressure. Prevention is preferable because a collision can destroy spacecraft and generate debris that threatens other missions.

What Is Ephemeris Sharing?

Ephemeris data describes and predicts an object’s position and movement in space. A satellite’s current location provides a single point in time; an ephemeris provides a model for estimating where the satellite will be along its orbit.

Operators use this information to compare projected paths, identify possible close approaches and assess uncertainty. Ephemeris data is related to, but different from, other operational information:

• Position data identifies where a spacecraft is now.
• Trajectory data predicts where it will travel.
• Maneuver data indicates planned orbital changes.
• Operational status may show whether the spacecraft can respond.

The Register reports that Starlink plans to reduce orbital near-misses through ephemeris sharing. [Source 5](https://news.google.com/rss/articles/CBMitwFBVV95cUxQTTRLRGF2YTVmMVBYcFB3dkVxZnRyZnkyM2htWjVIbzN4NUJF cVc2SU56blhOdFkzemxPazRLVWh4SW9DRFNrOEMtRXZTV2pwby01N3RWZ3dkR0tGbW5nSHNHTlJHRXNmbEE4WW5YVEV0UzgyN2xPTnlBZTE4VVFfN01sUjFiSTYxOW5zQklUdE5fcjlMQy1HeDJDRF85OVQ3Nmk4WmJiMGxLNHl5NWdJeU82akZoanM?oc=5)

A shared system could work as follows:

1. Operators provide updated spacecraft-position data.
2. Tracking systems compare projected trajectories.
3. Potentially dangerous approaches are identified.
4. Operators exchange additional information.
5. One or both spacecraft adjust their paths when necessary.
6. Updated predictions confirm whether the risk has been reduced.

More complete information could improve conjunction assessments, increase warning time and reduce uncertainty during maneuver planning. It could also help operators identify approaches that do not require action, preventing unnecessary maneuvers.

Data-sharing cannot eliminate risk. Predictions are models, spacecraft can maneuver unexpectedly, atmospheric drag affects low-orbit satellites and tracking sensors have limitations. Data becomes less useful when it is delayed, incomplete or inconsistent. Effective information-sharing requires frequent updates during maneuvers, accurate orbital models, clear uncertainty estimates, consistent formats, rapid communication and reliable authentication and access controls.

The available reporting does not specify the technical standard, data format or access rules for the proposed system.

The Need for Orbital Traffic Management

Low Earth orbit is a shared environment, not a collection of completely isolated operating zones. Broadband satellites, Earth-imaging spacecraft, weather and science missions, crewed vehicles, cargo vehicles, rocket bodies, defunct spacecraft and debris may occupy or cross similar regions.

Orbital traffic management includes systems and procedures used to track objects, assess close approaches and coordinate responses. Its functions include:

• Tracking active and inactive objects
• Predicting conjunctions
• Sharing warnings
• Coordinating maneuvers
• Recording operational information
• Establishing decision-making responsibilities
• Reviewing events after they occur

Space traffic management is not identical to air traffic control. Spacecraft operate in three dimensions, can remain in orbit for long periods and are subject to tracking uncertainty and communication delays. No single global controller manages every object in orbit.

Obstacles to Better Coordination

Operators may use different data formats, tracking sources, risk thresholds, maneuver procedures and communication channels. These differences can delay decisions or require manual interpretation.

Every orbital prediction also includes uncertainty. Atmospheric drag, spacecraft maneuvers, sensor limitations, delayed updates, incomplete models and poorly tracked debris can affect accuracy. Operators need uncertainty ranges, not only a single predicted path.

Responsibility is another challenge. When two spacecraft approach one another, operators need to know who should maneuver. Possible principles include assigning action to the more maneuverable spacecraft, allowing the more predictable mission to maintain course or applying pre-agreed rules. No single principle suits every encounter.

Operators may also hesitate to share detailed spacecraft information because it could reveal mission plans, capabilities or limitations. Safeguards could include standardized minimum data requirements, controlled access, trusted third-party coordination, secure communications, tiered access and auditable records.

What Better Coordination Could Mean for Starlink

Improved data could help operators distinguish genuinely risky approaches from low-risk encounters. More accurate predictions may reduce unnecessary maneuvers, fuel consumption, service interruptions and the risk of creating new conflicts.

A practical orbital safety framework could include:

• Common trajectory-data standards
• Near-real-time ephemeris updates
• Shared conjunction alerts
• Clear maneuver responsibilities
• Independent oversight
• Secure communication channels
• Post-event reporting

The available reports do not show that SpaceX’s proposal already includes every element. They support a narrower conclusion: SpaceX is calling for better coordination and more effective exchange of spacecraft-position information.

Shared Responsibility for Space Sustainability

Orbital safety affects every organization using the same environment. A collision involving one operator can create debris that threatens spacecraft owned by many others.

Responsible operations include avoiding collisions, sharing reliable tracking information, conducting timely avoidance maneuvers, limiting unnecessary maneuvers, deorbiting spacecraft when appropriate and reporting relevant operational events.

Space sustainability depends on treating orbital space as shared infrastructure. Better coordination is not only a Starlink issue; it is part of the safety system required for a growing space economy.

Conclusion

SpaceX’s call for better coordination reflects the growing complexity of low Earth orbit. Starlink near-misses demonstrate the number of potential encounters that large constellations must manage, while broader orbital incidents show that risk involves many types of spacecraft and debris.

The reported solution centers on better trajectory and ephemeris sharing. More timely and precise information could improve conjunction assessments, increase warning time and help operators coordinate collision-avoidance decisions.

Near-miss figures do not prove that a collision is imminent or unavoidable. They do show that orbital traffic management is becoming more demanding. As the number of satellites rises, safety will depend on collective action, shared standards and reliable communication.

The available source summaries provide limited technical detail about the proposed system, its timeline and its governance. The next stage will require clearer information about data formats, access rules, maneuver responsibility and oversight. The central principle is established: safer orbital operations require operators to share enough information to make coordinated decisions.

FAQ

How many near-misses do Starlink satellites experience?

A cited report says Starlink satellites experience hundreds of near-misses annually. The exact figure depends on the definition of a near miss, the separation threshold and the tracking methodology. Source 3

What is ephemeris sharing?

Ephemeris sharing involves exchanging data that describes and predicts a spacecraft’s position and movement. Operators can compare projected trajectories, identify close approaches and coordinate collision-avoidance maneuvers.

Why does SpaceX want operators to share trajectory data?

Satellites from different operators may occupy or cross similar orbital regions. More accurate and timely trajectory data can improve conjunction warnings and help operators coordinate safe responses. [Source 1](https://news.google.com/rss/articles/CBMitwFBVV95cUxPbUJxdmI4YjVhMkZVUjNDMF9xMkZpN2J0UDdDVlFQU3V3eHpHYm16bWdVMnN1YUZqSzdYTndKTGctbGpOT245N2ZrQm11MFlfQUFaa0dYSXFfVnBTbERuWk k5RnVfLTBlQTNERkFtNGxUUWNGYlNlUElhSFdoODFMdGJfNXZ0bHQ3MTdIcE03WDBrTC1Fb3BaYzZqc2xvNi04eDJpTnQ1TVFjR3lCaVRpbmNyQzdLOEE?oc=5)

Are Starlink near-misses the same as satellite collisions?

No. A near miss is a close approach in which the objects do not collide. It indicates potential risk but does not necessarily mean a collision was imminent or unavoidable.

Who is responsible for avoiding a collision in space?

Responsibility depends on the spacecraft involved, available data, maneuverability and applicable procedures. Clear communication and pre-agreed coordination rules are therefore important.

Can better data-sharing eliminate collision risks?

No. Data-sharing can improve prediction and decision-making, but tracking errors, atmospheric effects, unexpected maneuvers, debris and communication delays can still create uncertainty.