ECSS E-ST-10C — Time Scales and Epochs (space-systems/ecss/e1009-time)
Use when the task is to select and verify the time scale and epoch
associated with each reference frame in a space mission, following
ECSS E-ST-10C §5.4.4. This leaf covers the eight standard time
scales (TAI, UTC, UT1, TT, TDB, TCB, TCG, GPS), the standard
epochs (J2000.0, J1950.0, B1950.0, MJD epoch), and the rules
binding each frame to its recommended scale.
Domain quick reference
- TAI (International Atomic Time) is the primary uniform atomic
scale. All other scales are derived from or referred to TAI.
- TT (Terrestrial Time) equals TAI + 32.184 s exactly. It is the
scale used for geocentric ephemerides and is the defining scale for
the J2000.0 epoch.
- UTC (Coordinated Universal Time) equals TAI minus an integer
count of leap seconds broadcast by IERS. It is the civil broadcast
time and is used with Earth-rotating frames (ECEF, ITRS) whose
orientation depends on Earth rotation angle.
- UT1 (Universal Time 1) tracks the actual angle of Earth's
rotation. It differs from UTC by DUT1, which stays within ±0.9 s
by IERS convention. UT1 is required when converting Earth-rotating
frame orientations to inertial frames at high precision.
- TDB (Barycentric Dynamical Time) is used for solar-system
ephemerides and barycentric frames (BCRS, HCI). Its mean rate
matches TT; the periodic difference stays within ±2 ms.
- TCB and TCG are SI-second coordinate time scales at the
solar-system barycentre and Earth geocentre respectively. They
drift from TT/TDB by a secular rate (~1.48 × 10⁻⁸) and are used
when relativistic rigour is required.
- GPS time equals TAI − 19 s, a constant offset established at
the GPS epoch (1980-01-06). GNSS receiver outputs must be converted
to TAI or UTC before ingestion into frame computations.
- J2000.0 is defined as 2000 January 1, 12:00:00 TT
(JD 2451545.0 TT). It is the standard reference epoch for modern
inertial frames. J1950.0 (JD 2433282.5 TT) and B1950.0
(Besselian) are legacy epochs retained for historical catalogues.
- Modified Julian Date (MJD) equals JD − 2 400 000.5 and is
commonly used in AOCS and GNSS systems to avoid large integers.
Frame–time-scale pairing rules
Each reference frame requires a specific time scale for its
orientation or position computation. The table below is paraphrased
from §5.4.4 of ECSS E-ST-10C; use it as the selection guide.
| Frame |
Recommended scale(s) |
Notes |
| ECI |
TT, TAI |
Inertial; avoids leap-second discontinuities |
| GCRS |
TT, TCG |
Geocentric relativistic RS |
| ECEF / ITRS |
UTC, UT1 |
Orientation tied to Earth rotation angle |
| TEME |
UTC, TAI |
Two-Line Element propagation convention |
| BCRS |
TDB, TCB |
Solar-system barycentre |
| HCI |
TDB, TCB |
Heliocentric inertial |
| RTN / LVLH |
UTC, TAI, TT |
Relative frames; inherits from parent inertial or rotating |
Using a rotating-frame scale (UTC/UT1) with an inertial frame (ECI,
GCRS) or a barycentric scale (TDB) with an Earth-fixed frame is a
procedural error that will produce incorrect frame-to-frame rotation
matrices.
Workflow
Identify every reference frame used in the mission (ECI, ECEF,
BCRS, etc.) and record each frame's motion description (inertial,
Earth-rotating, barycentric).
For each frame, select the recommended time scale from the pairing
table above. Reject any scale that is not in the recommended set
for that frame; flag the pairing as inconsistent and require
engineering justification to proceed.
Assign a standard epoch to each frame definition. Prefer J2000.0
for modern inertial and barycentric frames. State the epoch's
Julian Date and its reference time scale (J2000.0 is defined in TT).
For any data source using GPS time or UTC: convert to TAI first
(GPS → TAI: add 19 s; UTC → TAI: add the current leap-second count
from the IERS bulletin), then propagate to TT or TDB as required
by the target frame.
When computing frame-orientation matrices (e.g. GMST, GAST, or
precession–nutation for ECI↔ECEF), confirm the time argument is
in the scale required by the transformation algorithm (GMST uses
UT1; precession–nutation models use TT).
Document the time scale and epoch for every state vector, attitude
quaternion, and ephemeris product in the mission data dictionary;
leave no product with an unspecified or assumed time tag.
Pitfalls
- Supplying UTC seconds to an algorithm that expects TT seconds
without converting through TAI. The error accumulates by one second
per leap-second event and is invisible until a leap second occurs
in-flight.
- Treating TDB and TT as interchangeable in orbit propagation. The
periodic TDB–TT difference (up to ~1.6 ms) is negligible for most
mission phases but reaches tens of metres in position error for
high-precision interplanetary trajectories.
- Applying the GPS–TAI offset of 19 s to a UTC-tagged timestamp
instead of the current leap-second count. UTC and GPS diverge
because UTC accumulates leap seconds while the GPS offset does not.
- Leaving the epoch scale implicit. J2000.0 is defined in TT; if a
tool internally uses TCB and labels its epoch "J2000.0", the
secular drift between TT and TCB will cause position errors that
grow with mission duration.
- Mixing MJD (which truncates the JD integer) with JD in arithmetic
without accounting for the 2 400 000.5 day offset, causing
single-day or half-day biases in time-tagged products.
Behavior contract (gate 3)
The time-scale validation, epoch lookup, frame–time-scale
compatibility, and conversion logic are exercised by the gate 3
contract test: scripts/test_e1009_time.py against
scripts/e1009_time_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1009_time.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1009-time3description: "Use when define the time scale and epoch for each spacecraft reference frame under ECSS E-ST-10C §5.4.4: select from TAI, UTC, UT1, TT, TDB, TCB, TCG, or GPS for inertial (ECI, GCRS), Earth-rotating (ECEF, ITRS), or barycentric (BCRS, HCI) frames; identify the standard epoch (J2000.0, J1950.0, B1950.0, or MJD) used as the time origin; verify each frame–time-scale pairing is consistent with its motion description; and convert between time scales using the TAI–TT constant offset or a supplied leap-second count for UTC. Trigger: ecss, e-st-10-system-scope, time-scales, epochs, tai, utc, tt, tdb, j2000, reference-frames."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e1009-time15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, time-scales, epochs, tai, utc, tt, tdb, j2000, reference-frames]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS E-ST-10C — Time Scales and Epochs (space-systems/ecss/e1009-time)2324Use when the task is to select and verify the time scale and epoch25associated with each reference frame in a space mission, following26ECSS E-ST-10C §5.4.4. This leaf covers the eight standard time27scales (TAI, UTC, UT1, TT, TDB, TCB, TCG, GPS), the standard28epochs (J2000.0, J1950.0, B1950.0, MJD epoch), and the rules29binding each frame to its recommended scale.3031## Domain quick reference3233- **TAI** (International Atomic Time) is the primary uniform atomic34 scale. All other scales are derived from or referred to TAI.35- **TT** (Terrestrial Time) equals TAI + 32.184 s exactly. It is the36 scale used for geocentric ephemerides and is the defining scale for37 the J2000.0 epoch.38- **UTC** (Coordinated Universal Time) equals TAI minus an integer39 count of leap seconds broadcast by IERS. It is the civil broadcast40 time and is used with Earth-rotating frames (ECEF, ITRS) whose41 orientation depends on Earth rotation angle.42- **UT1** (Universal Time 1) tracks the actual angle of Earth's43 rotation. It differs from UTC by DUT1, which stays within ±0.9 s44 by IERS convention. UT1 is required when converting Earth-rotating45 frame orientations to inertial frames at high precision.46- **TDB** (Barycentric Dynamical Time) is used for solar-system47 ephemerides and barycentric frames (BCRS, HCI). Its mean rate48 matches TT; the periodic difference stays within ±2 ms.49- **TCB** and **TCG** are SI-second coordinate time scales at the50 solar-system barycentre and Earth geocentre respectively. They51 drift from TT/TDB by a secular rate (~1.48 × 10⁻⁸) and are used52 when relativistic rigour is required.53- **GPS time** equals TAI − 19 s, a constant offset established at54 the GPS epoch (1980-01-06). GNSS receiver outputs must be converted55 to TAI or UTC before ingestion into frame computations.56- **J2000.0** is defined as 2000 January 1, 12:00:00 TT57 (JD 2451545.0 TT). It is the standard reference epoch for modern58 inertial frames. J1950.0 (JD 2433282.5 TT) and B1950.059 (Besselian) are legacy epochs retained for historical catalogues.60- **Modified Julian Date (MJD)** equals JD − 2 400 000.5 and is61 commonly used in AOCS and GNSS systems to avoid large integers.6263## Frame–time-scale pairing rules6465Each reference frame requires a specific time scale for its66orientation or position computation. The table below is paraphrased67from §5.4.4 of ECSS E-ST-10C; use it as the selection guide.6869| Frame | Recommended scale(s) | Notes |70|-------|----------------------|-------|71| ECI | TT, TAI | Inertial; avoids leap-second discontinuities |72| GCRS | TT, TCG | Geocentric relativistic RS |73| ECEF / ITRS | UTC, UT1 | Orientation tied to Earth rotation angle |74| TEME | UTC, TAI | Two-Line Element propagation convention |75| BCRS | TDB, TCB | Solar-system barycentre |76| HCI | TDB, TCB | Heliocentric inertial |77| RTN / LVLH | UTC, TAI, TT | Relative frames; inherits from parent inertial or rotating |7879Using a rotating-frame scale (UTC/UT1) with an inertial frame (ECI,80GCRS) or a barycentric scale (TDB) with an Earth-fixed frame is a81procedural error that will produce incorrect frame-to-frame rotation82matrices.8384## Workflow85861. Identify every reference frame used in the mission (ECI, ECEF,87 BCRS, etc.) and record each frame's motion description (inertial,88 Earth-rotating, barycentric).89902. For each frame, select the recommended time scale from the pairing91 table above. Reject any scale that is not in the recommended set92 for that frame; flag the pairing as inconsistent and require93 engineering justification to proceed.94953. Assign a standard epoch to each frame definition. Prefer J2000.096 for modern inertial and barycentric frames. State the epoch's97 Julian Date and its reference time scale (J2000.0 is defined in TT).98994. For any data source using GPS time or UTC: convert to TAI first100 (GPS → TAI: add 19 s; UTC → TAI: add the current leap-second count101 from the IERS bulletin), then propagate to TT or TDB as required102 by the target frame.1031045. When computing frame-orientation matrices (e.g. GMST, GAST, or105 precession–nutation for ECI↔ECEF), confirm the time argument is106 in the scale required by the transformation algorithm (GMST uses107 UT1; precession–nutation models use TT).1081096. Document the time scale and epoch for every state vector, attitude110 quaternion, and ephemeris product in the mission data dictionary;111 leave no product with an unspecified or assumed time tag.112113## Pitfalls114115- Supplying UTC seconds to an algorithm that expects TT seconds116 without converting through TAI. The error accumulates by one second117 per leap-second event and is invisible until a leap second occurs118 in-flight.119- Treating TDB and TT as interchangeable in orbit propagation. The120 periodic TDB–TT difference (up to ~1.6 ms) is negligible for most121 mission phases but reaches tens of metres in position error for122 high-precision interplanetary trajectories.123- Applying the GPS–TAI offset of 19 s to a UTC-tagged timestamp124 instead of the current leap-second count. UTC and GPS diverge125 because UTC accumulates leap seconds while the GPS offset does not.126- Leaving the epoch scale implicit. J2000.0 is defined in TT; if a127 tool internally uses TCB and labels its epoch "J2000.0", the128 secular drift between TT and TCB will cause position errors that129 grow with mission duration.130- Mixing MJD (which truncates the JD integer) with JD in arithmetic131 without accounting for the 2 400 000.5 day offset, causing132 single-day or half-day biases in time-tagged products.133134## Behavior contract (gate 3)135136The time-scale validation, epoch lookup, frame–time-scale137compatibility, and conversion logic are exercised by the gate 3138contract test: scripts/test_e1009_time.py against139scripts/e1009_time_logic.py (stdlib unittest, offline). Run:140141```142python3 scripts/test_e1009_time.py143```144145## Compliance146147- ECSS standards are freely downloadable (ESA); cite the source and148 paraphrase per standards-map.yaml.149- compliance: STANDARDS-REF, gated: false.