Why identical clocks need a different time system on the Moon

Lunar navigation · Tech

Two accurate clocks can gradually disagree

The Moon’s timing problem becomes clearer when three different measurements stop sharing one headline.

1. Clock rate is one questionA modeled lunar surface clock gains about 56 microseconds per Earth day relative to an Earth surface clock.
2. Signal delay is anotherA transmitted reading also takes time to arrive. Correcting its journey does not remove the clocks’ different rates.
3. A common reference connects the measurementsBetter clocks still need agreed rules for comparing timestamps across locations and missions.

Imagine two excellent atomic clocks, one on Earth and one on the Moon. Engineers account for the journey and arrange for their readings to agree at a chosen moment. Neither clock breaks. Neither develops a faulty battery or a loose component. Yet their readings will gradually separate.

This thought experiment exposes the awkward part of lunar timekeeping. A clock can measure its own local passage of time faithfully without staying aligned with a distant clock. Buying a more accurate instrument does not make that distinction disappear.

NIST’s explanation of lunar time gives the memorable scale: roughly 56 microseconds gained per day by clocks on the lunar surface compared with those on Earth. The interesting question is what that number allows us to say. It is easy to turn a correct physical result into the wrong story about radio messages, navigation or a new time zone.

A timestamp has a journey as well as a clock

Suppose a lunar instrument transmits a timestamp to Earth. There are two separate questions. What did its clock read when it sent the message? How long did the message spend travelling before the receiver recorded it?

The first involves a clock and its reference. The second involves a path through space. Even if the clock rates had no difference at all, the signal would still take time to arrive. Conversely, subtracting the signal’s travel time would not make a persistent rate difference vanish. Repeating the same comparison tomorrow requires both effects to be handled again.

That is why “the Moon is 56 microseconds ahead” is incomplete. Ahead of which reference, at which location, and after how long? A rate difference needs an interval over which to accumulate. A timestamp offset is the accumulated result at a specified moment. Neither quantity is automatically the latency of a radio link.

There is a useful habit here even for Earthbound engineering: ask what a displayed time actually measures. Our explanation of why a short DNS TTL does not prove that an address is fresh encounters a different mechanism but the same need to name the quantity before interpreting it.

The 56 microsecond result comes with a location

Neil Ashby and Bijunath Patla’s 2024 paper on lunar clock rates calculates approximately 56.02 microseconds per day for a clock near the Moon’s selenoid compared with one near Earth’s geoid. These are reference surfaces for the comparison, not a promise that every clock anywhere near the Moon follows one exact adjustment.

The calculation accounts for gravitational and motional effects. It also includes variation associated with the orbit. The headline figure is an average, useful for understanding the scale of the problem; it is not a complete navigation model that can be pasted into every spacecraft.

The same paper discusses a different figure,58.721 microseconds per day, for an Earth-satellite approximation at the Moon’s distance that excludes the Moon’s own gravitational potential. That is a different setup. Encountering both numbers should prompt a check of the assumptions, rather than an attempt to average them or declare one a typo.

How a tiny time difference becomes 16.8 kilometres

Radio navigation makes small timing differences consequential because signals travel so quickly. NASA’s atomic-clock explainer describes ranging by timing a signal sent to a spacecraft and returned to Earth. Knowing the signal speed lets navigators relate elapsed time to distance.

For a deliberately simplified one-way light-distance equivalent, multiply a time discrepancy by the speed of light in vacuum. Using the rounded headline value gives:

299,792,458 metres/second × 0.000056 seconds = 16,788.38 metres, or about 16.8 km.

Worked calculation

Light-distance equivalents of timing discrepancies

Timing discrepancy	One-way equivalent	Interpretation
1 microsecond	About 300 m	A unit conversion, not a measured position error
56 microseconds	About 16.8 km	The rounded daily drift treated as an uncorrected timing bias
1 millisecond	About 300 km	Why the scale of the timing unit matters

Calculated using the vacuum speed of light. These examples do not model a mission, its geometry or its clock corrections.

The calculation is a sensitivity illustration. It does not establish that a real lander will miss its destination by 16.8 km after a day. Navigation combines observations, reference models and estimates of clock error. A round-trip range measurement also needs its two-way geometry accounted for; the simple one-way multiplication is not the whole ranging equation.

Consider a hypothetical receiver that mistakes an uncorrected clock offset for extra signal travel time. It has assigned the discrepancy to distance when some of it belongs to the clocks. Improving the precision of that mistaken calculation merely gives a more precise wrong answer. The missing ingredient is the model that keeps those quantities separate.

The common reference is bigger than one excellent clock

In its September 2024 description of Coordinated Lunar Time, NASA outlined a weighted average of atomic clocks at the Moon. A timing system therefore involves more than choosing a particularly good box and declaring it the official clock. Measurements must be compared and related to a shared reference.

This becomes especially important when equipment comes from different missions. An observation timestamp is useful to another operator only if that operator can interpret it. More lunar activity increases the importance of that quiet agreement beneath the hardware. It is one practical layer underneath the broader competition to build space infrastructure.

The IAU’s adopted 2024 resolutions make an instructive distinction. Resolution II addresses a Lunar Celestial Reference System and Lunar Coordinate Time. Resolution III addresses a coordinated lunar time standard established by international agreement. A mathematical reference and the organization of a shared standard are related tasks, but their separate treatment is meaningful.

NASA was still explaining the engineering of lunar timing in its April 2026 interview with SCaN leader Kevin Coggins. This article explains the underlying problem; it does not treat an earlier development plan as evidence of a completed service today.

Three questions make the next Moon-time headline more useful

1. Which clocks are being compared? A surface, an orbit and a mathematical reference are not interchangeable locations.
2. Is the number a rate, an offset or a travel time? “Per day” changes the meaning. So does stating when two clocks were aligned.
3. What does a distance comparison assume? Multiplying by light speed is a useful illustration, not a substitute for a navigation solution.

The most revealing part of lunar time is that precision creates a coordination problem rather than ending one. Two clocks can work beautifully. To use their readings together, somebody must still say what those readings mean.

Questions about clocks on the Moon

Primary research and official timing sources

Checked 9 September 2026. Calculations and hypothetical receiver examples are explanatory, not mission test results.

• Ashby and Patla — A Relativistic Framework to Estimate Clock Rates on the Moon
• NIST — What Time Is It on the Moon?
• NASA — What Is an Atomic Clock?
• NASA — NASA to Develop Lunar Time Standard for Exploration Initiatives
• IAU — Adopted resolutions,2024 II and III
• NASA — Telling Time on Other Worlds,24 April 2026