UTC, UT1, TT, and Delta T: A Source-Reviewed Guide
UTC follows atomic time with leap seconds, UT1 tracks Earth rotation, and TT supports ephemeris dynamics. Scope and limits are explicit.
Overview
Civil UTC, Earth-rotation UT1, ephemeris-oriented TT, leap seconds, DUT1, and ΔT serve different roles and must not be collapsed into one generic universal time. The page shows exactly what to verify, how to repeat the method, where a plausible near miss fails, which variants change the result, and what the evidence cannot establish.
At a glance
- Direct scope
- Reviewed finding — UTC follows atomic time with leap seconds, UT1 tracks Earth rotation, and TT supports ephemeris dynamics. Delta T approximates TT minus UT1 and becomes increasingly uncertain for remote historical dates.
- Evidence to verify
- Method checkpoint — Convert civil input to UTC, obtain DUT1 or a documented UT1 estimate, derive TT using the declared leap-second and Delta-T data, label every intermediate scale, and preserve the table or model version.
- Repeatable method
- Worked-case result — For a modern fixture, the receipt shows UTC for the recorded instant, UT1 for sidereal rotation, and TT for the planetary ephemeris. Replacing UT1 with UTC exposes the small angle difference.
- Worked example
- Failure condition — Calling every timestamp “UTC” while feeding the same number to rotation and dynamical algorithms hides scale conversions. Matching formatted clock text does not mean the underlying time arguments are equivalent.
- Near miss
- Documented variant — For many contemporary chart displays, simplified choices change only tiny fractions; eclipses, historical angles, and high-precision comparison can be more sensitive. Precision policy should match the stated use.
- Limits and safety
- Use boundary — Time-scale precision does not compensate for uncertain civil input or validate interpretation. Historical Delta-T estimates remain model-dependent and must not be presented as exact recovered clock time.
Definition and Scope
Civil UTC, Earth-rotation UT1, ephemeris-oriented TT, leap seconds, DUT1, and ΔT serve different roles and must not be collapsed into one generic universal time.
UTC follows atomic time with leap seconds, UT1 tracks Earth rotation, and TT supports ephemeris dynamics. Delta T approximates TT minus UT1 and becomes increasingly uncertain for remote historical dates.
Evidence and Repeatable Method
Convert civil input to UTC, obtain DUT1 or a documented UT1 estimate, derive TT using the declared leap-second and Delta-T data, label every intermediate scale, and preserve the table or model version.
Worked Example and Near Miss
For a modern fixture, the receipt shows UTC for the recorded instant, UT1 for sidereal rotation, and TT for the planetary ephemeris. Replacing UT1 with UTC exposes the small angle difference.
Calling every timestamp “UTC” while feeding the same number to rotation and dynamical algorithms hides scale conversions. Matching formatted clock text does not mean the underlying time arguments are equivalent.
Variants and Disagreement
For many contemporary chart displays, simplified choices change only tiny fractions; eclipses, historical angles, and high-precision comparison can be more sensitive. Precision policy should match the stated use.
Limits and Safe Use
Time-scale precision does not compensate for uncertain civil input or validate interpretation. Historical Delta-T estimates remain model-dependent and must not be presented as exact recovered clock time.
Sources and editorial basis
- IERS Conventions (2010), Technical Note 36IERS Technical Note 36, chapters 4–5 celestial reference systems and transformation, and chapter 10 general-relativistic time transformationsThe international technical conventions for terrestrial and celestial reference systems, Earth orientation, precession-nutation, and time transformations.
- US Naval Observatory: Terrestrial TimeUSNO FAQ “Terrestrial Time (TT)”, definition paragraphs and the J2000.0 = JD 2451545.0 TT exampleAn official explanation of Terrestrial Time, its relation to atomic time, and the J2000.0 epoch.