Tuesday, November 10, 2026

Did Russia need SpaceX's help to catch X36?

As of November 10, 2026

Bottom line: Russia's Cosmos 2612 approach to ICEYE-X36 on Oct 15–18, 2026 is real, and the U.S. has called it out at the UN. The claim that SpaceX enabled it is not supported: its key legal premise misreads the FCC license, and Russia set up the approach before the Starlink alert existed.

The report's thesis

The Pirrong / R.A.B. report argues that SpaceX posted a misleading 401 m Starlink collision alert on Oct 15. Under FCC "Condition 16," the authors say, that alert legally froze X36, letting Cosmos 2612 sprint in and hold within about 640 m for more than 40 hours. They tie this to the Oct 13–14 Starshield speed cap in Ukraine and a White House push for a deal with Putin.

What holds up: the close approach, the speed cap, Putin's Oct 28 "Mr. Musk" remark, Hegseth's "terms of service" comment, and the Oct 15 Ryazan refinery strike all happened. What doesn't: the causal chain linking them to SpaceX.

The decisive questions

1. Did Russia need SpaceX's help to catch X36?

Probably not. Russia began the approach before the alert, and X36's orbit is published in the public U.S. satellite catalog. A target that isn't dodging can be reached with public data.

Date (2026)Event
Sept 30Cosmos 2612 starts maneuvering toward X36 (Vantor)
Oct 12~27.9 m/s burn matches X36's altitude, inclination and plane (Defense News)
Oct 13Trailing X36 in the same orbit, ~475 km behind (Le Grand Continent)
Oct 15, 04:15 UTCStarlink 401 m collision alert against X36 (per the report)
Oct 16Final close-approach burn; holds within ~5 km, later closer

2. Did the Starlink alert legally freeze X36?

No. Condition 16 of FCC Order DA 23-797 requires ICEYE to assess collision risk and mitigate it if necessary: contact the other operator, share trajectory data, or modify its attitude or operations. Nothing bars maneuvering or puts ICEYE under SpaceX's control. This is the report's central error.

3. Was the 401 m alert abnormal?

Unknown. The claim that SpaceX's internal data showed a ~2 km miss is the authors' reconstruction, not independently confirmed. Alerts are routine and conservative: SpaceX logged about 164,000 potential collision events in six months, most not imminent (Aerospace Global News).

Who can settle it: the U.S. Space Force's own warning for the pair, and SpaceX's and ICEYE's alert logs.

4. Did X36 deliberately hold still, and why?

Open — the decisive question. ICEYE has dodged before: after a pass within ~2.5 km on May 26, its CEO said it maneuvered (United24). For October, ICEYE said only that it was tracking the situation and that its constellation is built for resilience (Boston Globe).

There are innocent reasons not to dodge: X36 weighs about 90 kg, and escape burns spend scarce propellant and shorten its life (Scientific American). Only ICEYE can settle this.

5. Is there evidence SpaceX coordinated with Russia?

None public. Independent tracking documents the Russian maneuvers but not SpaceX involvement (Runtimewire). Putin's Oct 28 remark was a general comment about not interfering with each other in orbit, made while touring an exhibition (Euronews).

Who can settle it: congressional or Inspector General access to communications records.

6. Was X36 harmed, and what did Russia gain?

No physical harm seen; intelligence gain unknown. ICEYE says X36 remains productive (Aerospace Global News), and tracker Marco Langbroek saw no orbital disturbance (X). Jamming or signals collection would not show in orbital data (Diplomacy and Law). The U.S. told the UN First Committee the behavior was consistent with on-orbit weapons operations. The report's "radar fingerprint" theft is physically plausible but unverified.

7. Who ordered the Starshield speed cap, and is it linked?

Disputed; no link beyond timing. Reuters, citing U.S. officials, said the directive came from the White House; Musk said speed limits are a U.S. military and presidential decision (Tech Insider). Musk and Trump both deny ordering it (The Next Web). Hegseth pointed to Starlink's terms of service (Devdiscourse).

8. Is ICEYE-X37 next?

Partly corroborated. Analyst Greg Gillinger flagged Cosmos 2611 and 2613 moving toward X37's orbital plane (Diario Bitcoin). The report's precise lock-on figures are unverified.

What would close the case

One answer from ICEYE would decide most of it. If the alert played no role in its decision, the SpaceX thesis collapses; if it did, questions 3 and 5 become urgent.

  1. ICEYE states whether it received the Oct 15 alert and whether it held its orbit because of it.
  2. The Space Force releases its own conjunction warning for X36 and STARLINK-35856, to compare with SpaceX's 401 m figure.
  3. Investigators obtain any SpaceX–Russia contact records for October 2026.

Sources

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)