...

Clocks in Orbit: Rate Budget Map and Offset Timeline (2D)

Top-down map of an orbit with the clock-rate budget drawn as bars: speed slows the satellite clock, weaker gravity speeds it up. Move the orbit and read the net drift and the ranging error.
Altitude / orbital radius-
Orbital speed / period-
Speed effect (SR)-
Gravity effect (GR)-
Net drift vs ground-
Offset after the chosen time-
Ranging error if uncorrected-
Satellite clock-
μs per day vs altitude (km, log): blue speed, red gravity, green net. Crosses zero near 3,170 km. Dot: current orbit.
Accumulated offset (μs) vs days since sync: orange chosen orbit; grey ISS, green GPS, blue GEO. Offset times c = ranging error.
Independent numerical checks
Each line compares two separate calculations; a FAIL would show here.
The science

Rate of a clock. In the Schwarzschild metric a clock moving at speed v at radius r runs at dτ/dt = √(1 − 2GM/(rc²) − v²/c²) relative to far-away coordinate time. For a circular orbit v² = GM/r, so dτ/dt = √(1 − 3GM/(rc²)). A clock on the ground sits on the geoid, where the combined gravitational and centrifugal potential is W0 = 6.2636856×10&sup7; m²/s² (a typical IERS value), so dτ/dt = √(1 − 2W0/c²).

Budget. To first order: speed effect −GM/(2rc²) (clock slower), gravity effect +(W0 − GM/r)/c² (clock faster). For GPS (r = 26,562 km) this gives roughly −7.2 and +45.7, net about +38.6 μs per day. Multiplying by c gives the ranging error: about 11.6 km per day if the effect were ignored. Real GPS satellite clocks are pre-set slightly slow to cancel the average offset, and receivers also correct for orbit eccentricity.

Simplifications. Circular orbit, spherical point-mass Earth for the satellite (J2 and tides ignored), Moon's pull and the Sun's potential neglected, no Sagnac or atmospheric delays. The "Moon distance" preset places a satellite on a circular orbit at the Moon's mean distance for comparison only; a real lunar clock would also feel the Moon's and Sun's potentials. Orbit radii in the 3D view are visually compressed; the clock arithmetic uses true distances.

2D view: top-down / diagram rendering with sprites rendered in Blender (Cycles) from the 3D page's model parts; all numbers come from the same solver as the 3D page.

Made with 🟠 Blender