It's official: Europe turns to the Falcon 9 to launch its navigation satellites
Europe’s decision to launch new Galileo navigation satellites on SpaceX’s Falcon 9 highlights a temporary loss of independent access to space after Ariane 5’s retirement and delays to Ariane 6. Commenters weigh the trade-offs between relying on a US private launch provider and maintaining European “strategic autonomy,” while noting that Falcon 9’s reliability and price make it hard to ignore. The thread also explores how global navigation satellite systems work, why multiple constellations exist, and what more satellites or LEO swarms could realistically add in terms of positioning accuracy.
Use of Falcon 9 for Galileo / Cost and Security
- EU is turning to Falcon 9 because Ariane 5 is retired, Ariane 6 is delayed, and alternatives are limited.
- Some see it as ironic/undesirable that a “strategic autonomy” program now depends on a US launcher; others call it pragmatic stop‑gap.
- Clarification that the ~$100M figure discussed is largely launch cost, not spacecraft cost; SpaceX’s baseline is noted around $67M, with a premium attributed to security/handling of military‑sensitive payloads.
- Comparison with extremely high US government engine costs (e.g., RS‑25 refurbishment) to show $100M/launch is not extraordinary.
Are These Satellites “Spies”?
- One commenter suggests they must be spy satellites given cost and debris‑recovery arrangements.
- Others push back: GNSS orbits (~20,000–22,000 km) are unsuitable for high‑resolution spying, and EU as such has no unified military/espionage agency; Galileo’s extra features (high accuracy, SAR) and government overhead better explain cost.
European Launch Gap and Ariane 6
- Europe currently lacks a heavy launcher: Ariane 5 retired before Ariane 6 was ready; Vega only covers small payloads.
- Some argue Ariane 5 should have been kept alive until Ariane 6 flew, as many space customers pay heavily to avoid change.
- Ariane 6 is criticized as a politically designed “white elephant,” with workshare politics (France vs Germany) and insufficient demand to justify reusability.
Why Not Use Other Providers (ISRO, etc.)?
- Question raised about using Indian rockets.
- One view: ISRO is more expensive and capacity‑limited; most of its foreign satellites are tiny cubesats.
- Counterpoint: ISRO has launched many satellites for numerous countries with high success; the main concern for high‑value payloads is proven reliability and track record.
SpaceX vs Europe / US vs EU Industrial Models
- SpaceX seen as an outlier compared to both EU and traditional US government rockets (ULA, SLS); without it, the US would be in a similar bind.
- Several comments argue US policy “buys products” via fixed‑price commercial contracts, creating volume and scale, whereas EU tends to “fund research” without guaranteeing demand.
- European space firms (Arianespace, Airbus) are formally private but heavily state‑directed; this is blamed for slow, politicized decision‑making and lack of risk‑taking.
- Debate over culture: some say the US rewards big risk more, while Europe has stronger safety nets but weaker investment culture; others counter that real outcomes are more mixed and often overstated.
GNSS Precision, Multi‑Constellation, and “Swarm” Ideas
- More satellites generally improve positioning (better geometry, faster/more reliable fixes), but gains have diminishing returns and hit noise/multipath limits.
- Multi‑constellation receivers can combine GPS, Galileo, GLONASS, BeiDou, etc., but must reconcile different time bases and reference frames; cheap devices may solve each separately then fuse results.
- Sovereignty is a core driver of separate constellations: militaries don’t want to rely on foreign systems that can be degraded or jammed selectively.
- LEO “swarm” GNSS (e.g., Starlink as navigation) is considered technically feasible and has been publicly hinted at, but would require a powerful ground segment to manage clocks and frequent orbit changes.
- Older TRANSIT‑style Doppler systems and Japan’s QZSS (possibly ground‑synchronized clocks) are discussed as alternative architectures with trade‑offs in coverage and update rate.