Starlink's plan to avoid orbital near-misses: Ephemeris sharing

SpaceX said Starlink encountered conjunctions with about 650 unique maneuvering third-party satellites in 2026, with only about half sharing ephemeris; over six months, it observed roughly 164,000 conjunctions within four hours of an unannounced maneuver. The company is urging operators to share trajectory data and promote collision avoidance, while critics note its applications to operate 100,000 Starlink and up to 1 million Starmind AI satellites could add to orbital congestion. Neuraspace CEO Chiara Manfletti called for a federated, interoperable system for sharing trusted trajectory and maneuver-intent information across operators. The article highlights safety risks and cooperation needs but reports no new regulatory decision or market reaction.

Analysis

The investable issue is not the headline count of close approaches; it is whether orbital safety becomes a binding constraint on constellation deployment and utilization. If regulators or insurers require higher-quality trajectory sharing, maneuverability, or debris controls, the cost lands disproportionately on operators seeking rapid fleet growth: more coordination, onboard autonomy, replacement capacity, and potentially slower authorization. That could weaken the economics of expansion before it materially affects current service revenue. Conversely, safety infrastructure could become a competitive advantage for operators with reliable maneuvering and integrated monitoring, while independent traffic-management providers such as Neuraspace could benefit if customers and governments resist dependence on a single operator’s platform.

Near term, treat the company’s incident statistics as advocacy, not independently verified evidence of collision probability or financial exposure. The key 1–3 month catalysts are regulatory responses, licensing conditions, and evidence that operators adopt interoperable data standards; absent these, this is primarily a reputational and policy risk, not an earnings signal. Over 6–18 months, rising coordination requirements could raise marginal costs and constrain fleet additions, but the article does not establish the scale or timing.

Contrarian point: the safety push may strengthen the case for incumbent scale if integrated monitoring and maneuvering lower per-satellite operating risk. Do not assume that more conjunction alerts translate linearly into collisions, losses, or regulatory limits. For SPCX, verify independent conjunction data, insurance terms, and any change to deployment approvals before pricing a material impairment.

Key Decisions for Investors

• No immediate directional trade on SPCX from this report alone. Put the name on a regulatory-risk watchlist; escalate only if deployment approvals acquire measurable safety conditions or deployment cadence is delayed.
• Track independent indicators over the next 1–3 months: regulator filings, insurer language or premiums, and adoption of cross-platform trajectory-sharing standards. A binding requirement or documented restriction on launches would strengthen the downside thesis; voluntary coordination without operating constraints would weaken it.
• Treat Neuraspace and other independent space-traffic providers as potential beneficiaries, not established earnings winners. Seek evidence of customer contracts, recurring revenue, and interoperability adoption before taking exposure; the article supplies none of these.
• Falsification for the longer-term cost thesis: SPCX maintains its planned deployment pace and service metrics while independent safety data show no deterioration in risk or insurance terms. Conversely, verified deployment limits, material insurance repricing, or collision-related service disruption would warrant reassessing SPCX exposure.