Idea 6 — Communications and navigation availability planner
15 November 2026. One of six ideas; read 00-overview.md
first. Source numbers refer to its section 8. Compiled with AI (Claude);
not re-checked by a person. "Judgement" marks an assessment.
This is the weakest of the six on uniqueness. It is kept so that the reason is on file.
Product in one line
For a surface site and a time window, the tool returns when a user can reach Earth directly and through each relay provider, and how many navigation satellites it sees, with local terrain masking, in one comparison across providers.
Decision it supports
A payload or rover team decides which relay service to buy, where to park for a contact, and how much data it can return per day.
Why now
- NASA's analysis of South Pole landing sites gives 17% to 43% coverage with DTE links only, and 80% to 86% with lunar relays [23].
- Several providers are planned: NASA's relays built by Intuitive Machines [24]; ESA's Lunar Pathfinder and Moonlight, with South Pole priority [28]; relay satellites of ispace [8]; communications satellites that SpaceX will launch to cislunar space in 2028 for NASA [1].
- VIPER has no relay and plans its traverse around periods without Earth contact [37].
What exists
- SSTL published a web application in 2021 that estimates the service a mission would get from Lunar Pathfinder (news) [25].
- JPL's Line of Sight tool computes contact windows between surface points, orbiters and Earth stations, with terrain from elevation models [26].
- A university toolbox plans rover paths with communication windows and data uncertainty [27].
- NASA and ESA publish their own coverage and navigation performance analyses [23][28].
- A provider-neutral comparison tool: not found (one search).
Data basis and checks
- Geometry: LOLA terrain and SPICE (B findings 1 and 5). Earth visibility can be checked against NASA's published average maps at 60 to 240 m (B finding 6).
- Relay orbits: published only in part. Provider orbit data would be needed.
- Radio propagation on the surface: measured data were not searched.
Type A slice (TRL 3)
| CF | Function | Check |
|---|---|---|
| CF1 | DTE availability at a site with terrain uncertainty | NASA average Earth-visibility maps (B finding 6) |
| CF2 | Relay contact windows for two published orbits | Comparison with the provider's own published figures; not measured data |
| CF3 | Navigation satellite visibility and geometry at the site | Comparison with published ESA or NASA analyses; not measured data |
Users outside ESA (candidates; none contacted)
Payload and rover teams on CLPS, ispace and Argonaut flights; relay operators that want an independent figure for their customers.
Four tests (judgement)
- Unique: weak. A European tool exists for one provider, and the agencies publish their own analyses.
- Feasible: pass for geometry; weak for link quality.
- Needed: pass.
- Fits Type A: weak. Two of three checks are comparisons with other analyses. ESA runs Moonlight itself, so the duplication rule of the cover letter (point 6) is a risk.
Recommendation (judgement)
Do not lead with this idea. Keep CF1 as a derived layer inside idea 1, 3 or 4, where Earth visibility is one of several constraints.
Risks and unknowns
- Radio engineering experience is not shown in the CV on file.
- Provider orbit and service data may not be available to a third party.
- Whether SSTL's application is still online: not checked.