Home  /  Destinations  /  Mercury  /  Communications at 28 degrees

Communications at 28 degrees

Elongation 17.9–27.8° · conjunction every 116 days · optical, not radio

Mercury’s hardest single requirement is not thermal and not radiological. Every link, every day, forever, points within 28 degrees of the Sun, and no other body in the solar system shares that property.

Max elongation
17.9–27.8°
Venus, for comparison
47°
Radio standdown
below ~5°
Degraded
below 15°
Light time
4.3–12.1 min
Confidence
Measured

The geometry

An orbit inside Earth’s, and never far from the Sun.

Solar elongation is the angle between the Sun and a target as seen from Earth, and it is what decides whether a radio link passes through the solar corona. Mercury’s maximum elongation runs 17.9 to 27.8 degrees, varying with where in its eccentric orbit greatest elongation happens to fall.

Every other body spends part of its cycle at large elongation and can be talked to comfortably. Venus reaches 47 degrees. Mars, the belt and everything outward reach opposition, directly away from the Sun, once a synodic period. Mercury never does. Each 116-day synodic cycle also contains conjunctions — passages behind or in front of the Sun — during which radio is unusable outright.

Why radio fails

Solar plasma scintillation, permanently.

Deep-space radio links degrade sharply at small Sun–Earth–probe angles. Charged particles streaming out of the corona scatter and broaden the signal, spreading its spectrum and destroying phase coherence. Missions routinely stand down below about five degrees and accept degraded rates below 15.

Mercury never leaves that regime. This is not a link-budget adjustment to be solved with a larger dish or more transmit power, because the noise arrives with the signal and scales with it. Every Mercury mission flown has simply accepted low rates and stored data through conjunction, which is tolerable for a science orbiter returning a few gigabits and not tolerable for an industrial installation running a mass driver and a beam array.

Why optical works

A tiny field of view and a narrow filter.

Optical communications tolerates small Sun angles far better than radio, for two reasons that compound. The receiving field of view is tiny, so very little sky — and therefore very little scattered sunlight — enters the detector. And the received light can be spectrally filtered to a fraction of a nanometer, rejecting essentially all of the broadband solar background while passing the signal.

Mercury is the destination where laser communications stops being an upgrade and becomes the enabling technology. Everywhere else optical links buy data rate. Here they buy availability, which is a different kind of argument and a much stronger one.

And the industrial base being built at Mercury is, of all things, a high-power phased optical array program. The comms terminal and the export product are the same technology class: the same gain media, the same pointing metrology, the same thermal problem on the same optics. That is a rare case where a destination’s hardest requirement and its reason for existing are solved by one competence.

A failure category of its own

Distinct from link budget and from shielding.

Even with optical links there will be outages, so the requirement is a communications-availability failure category distinct from link budget and from shielding. It is the same category the outer-system pages identify for the radio frequency noise floor at Jupiter, arriving by a completely different mechanism: there the noise is Jovian synchrotron emission, here it is the corona, and in both cases the system has to be designed to keep working while it cannot be told anything.

Measured

This is a constraint, not a hazard. It does not accumulate, it has no return period, and nothing is damaged by it. It is a fixed property of Mercury’s orbit that has to be designed around, which is what puts it on the constraint fingerprint rather than the hazard one.

Local decision authority

Not because of light lag.

Light time to Mercury is 4.3 to 12.1 minutes, comparable to Mars and well inside the range where a supervised autonomous installation works normally. That is not the problem.

Mercury requires local decision authority because of link availability, not because of light lag. An installation that is unreachable for stretches of every synodic cycle has to be able to start, stop, degrade and protect itself without being asked, and it has to be able to do so for weeks. That is a different specification from a Mars outpost, which is always reachable and sometimes slow.

It also interacts with the beam. An array that cannot be commanded is an array that cannot be retargeted, which is a safety property and an operational liability at the same time, and it is one more reason the design rule on the departure corridor page exists: no vehicle files a profile it cannot complete on its own propellant.

↑