ECSS Communications — Mission Orbits (space-systems/ecss/e50-orbits)
Use when the task is clause 5.6.5 of ECSS-E-ST-50C Rev.2: naming the orbit
flown in each mission phase, and deriving from it the range, delay, Doppler
and visibility the communication system then has to live with.
Domain quick reference
- Two obligations, graded apart. One is that every phase has an orbit; the
other is that the communication consequences of those orbits are worked
out. A mission can derive beautiful numbers for the phases it declared and
still have a phase with no orbit at all, and a single verdict hides it.
- The orbit is the input to the link budget, not a context note. Slant range
at the mask elevation sets the path loss and the delay; the orbital speed
sets the Doppler; the period and the mask set how long the pass lasts.
None of those can be inherited from a similar mission.
- Range is taken at the mask, not at the sub-satellite point. The worst
geometry a station will work is the lowest elevation it is allowed to
work, and the altitude alone understates the path by a large factor at low
masks.
- Doppler is a receiver requirement before it is a link one. The shift the
orbit imposes has to sit inside the pull-in range of the receiver at each
end, and a shift outside it is not a margin shortfall but a receiver that
never acquires.
- Pass duration decides whether the data volume is deliverable at all. A
link that closes with margin for six hundred seconds a day still fails a
phase that needs twenty minutes of contact.
- An orbit declared for a phase the mission does not have is as much a
declaration defect as a phase with no orbit. It usually means a phase was
renamed and one of the two documents did not follow.
- The pass model is a bound and has to be labelled as one. Taking the pass
through the zenith over a non-rotating Earth is the longest pass the
geometry allows; near synchronous altitude the neglected rotation
dominates and the number understates real visibility.
Workflow
- Take the phase list once into a fixed order, refusing a repeat or a blank
name, so the declaration and implication checks see the same phases.
- Difference the phase list against the declared orbits both ways: phases
with no orbit, and orbits belonging to no phase.
- For each declared orbit, validate the altitude and the mask elevation,
refusing a mask at or above ninety degrees.
- Derive the slant range at the mask, then the one way and round trip
propagation delays from it.
- Derive the orbital speed and the largest line of sight rate, then the
Doppler shift that rate imposes on the declared carrier.
- Derive the pass duration from the period and the mask, and report it as
the bound it is.
- Compare each derived term against its allowance with a relative
tolerance, and close with a ranked disposition: a declaration gap first,
an allowance breach second, compliant only when neither stands.
Pitfalls
- Using the altitude as the range. At a five degree mask the slant range is
several times the altitude, and a budget built on the altitude closes on
paper and not in the pass.
- Deriving Doppler from the orbital speed directly. Only the line of sight
component shifts the carrier, and the full orbital speed overstates the
shift by a factor that grows with altitude.
- Carrying one orbit for the whole mission. Transfer, operational and
disposal orbits differ enough that the link that closes in one will not
close in another.
- Treating a short pass as a margin problem. Contact time multiplies the
data rate into a volume, and no amount of margin buys a pass that ends.
- Reading the bounding pass as the pass a station gets. It ignores Earth
rotation and assumes the satellite goes through the zenith, so scheduling
against it over-promises on every real pass.
- Comparing a derived value with a bare inequality at its limit. An orbit
sized to sit exactly on a stated delay budget then passes or fails by
which machine ran the check.
Behavior contract (gate 3)
Altitude, elevation, carrier and phase list validation, the slant range,
period, range rate, Doppler and bounding pass duration against independently
computed reference values, both directions of the phase-to-orbit difference,
allowance comparison at the exact bound and the ranked disposition are
exercised by the gate 3 contract test: scripts/test_e50_orbits.py against
scripts/e50_orbits_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e50_orbits.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e50-orbits3description: "Derive what a mission's orbits do to its communication links, and check every phase actually declared one, per ECSS-E-ST-50C Rev.2 clause 5.6.5. Use when slant range, propagation delay, Doppler shift and pass duration have to come out of the orbit rather than out of a heritage table: the two normative items are graded apart, so a phase that reaches the link budget with no orbit behind it is reported as a declaration gap and not folded into a margin. Doppler is compared against receiver pull-in, delay and pass length against the phase allowance. Trigger: ecss, e-st-50c-clause-5-6-5, mission-orbit-declaration, space-link-slant-range, orbit-doppler-shift, ground-station-pass-duration, propagation-delay-allowance."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/e50-orbits15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-50-communications-scope, e50-orbits, e-st-50c-clause-5-6-5, mission-orbit-declaration, space-link-slant-range, orbit-doppler-shift, ground-station-pass-duration, propagation-delay-allowance]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Communications — Mission Orbits (space-systems/ecss/e50-orbits)2324Use when the task is clause 5.6.5 of ECSS-E-ST-50C Rev.2: naming the orbit25flown in each mission phase, and deriving from it the range, delay, Doppler26and visibility the communication system then has to live with.2728## Domain quick reference2930- Two obligations, graded apart. One is that every phase has an orbit; the31 other is that the communication consequences of those orbits are worked32 out. A mission can derive beautiful numbers for the phases it declared and33 still have a phase with no orbit at all, and a single verdict hides it.34- The orbit is the input to the link budget, not a context note. Slant range35 at the mask elevation sets the path loss and the delay; the orbital speed36 sets the Doppler; the period and the mask set how long the pass lasts.37 None of those can be inherited from a similar mission.38- Range is taken at the mask, not at the sub-satellite point. The worst39 geometry a station will work is the lowest elevation it is allowed to40 work, and the altitude alone understates the path by a large factor at low41 masks.42- Doppler is a receiver requirement before it is a link one. The shift the43 orbit imposes has to sit inside the pull-in range of the receiver at each44 end, and a shift outside it is not a margin shortfall but a receiver that45 never acquires.46- Pass duration decides whether the data volume is deliverable at all. A47 link that closes with margin for six hundred seconds a day still fails a48 phase that needs twenty minutes of contact.49- An orbit declared for a phase the mission does not have is as much a50 declaration defect as a phase with no orbit. It usually means a phase was51 renamed and one of the two documents did not follow.52- The pass model is a bound and has to be labelled as one. Taking the pass53 through the zenith over a non-rotating Earth is the longest pass the54 geometry allows; near synchronous altitude the neglected rotation55 dominates and the number understates real visibility.5657## Workflow58591. Take the phase list once into a fixed order, refusing a repeat or a blank60 name, so the declaration and implication checks see the same phases.612. Difference the phase list against the declared orbits both ways: phases62 with no orbit, and orbits belonging to no phase.633. For each declared orbit, validate the altitude and the mask elevation,64 refusing a mask at or above ninety degrees.654. Derive the slant range at the mask, then the one way and round trip66 propagation delays from it.675. Derive the orbital speed and the largest line of sight rate, then the68 Doppler shift that rate imposes on the declared carrier.696. Derive the pass duration from the period and the mask, and report it as70 the bound it is.717. Compare each derived term against its allowance with a relative72 tolerance, and close with a ranked disposition: a declaration gap first,73 an allowance breach second, compliant only when neither stands.7475## Pitfalls7677- Using the altitude as the range. At a five degree mask the slant range is78 several times the altitude, and a budget built on the altitude closes on79 paper and not in the pass.80- Deriving Doppler from the orbital speed directly. Only the line of sight81 component shifts the carrier, and the full orbital speed overstates the82 shift by a factor that grows with altitude.83- Carrying one orbit for the whole mission. Transfer, operational and84 disposal orbits differ enough that the link that closes in one will not85 close in another.86- Treating a short pass as a margin problem. Contact time multiplies the87 data rate into a volume, and no amount of margin buys a pass that ends.88- Reading the bounding pass as the pass a station gets. It ignores Earth89 rotation and assumes the satellite goes through the zenith, so scheduling90 against it over-promises on every real pass.91- Comparing a derived value with a bare inequality at its limit. An orbit92 sized to sit exactly on a stated delay budget then passes or fails by93 which machine ran the check.9495## Behavior contract (gate 3)9697Altitude, elevation, carrier and phase list validation, the slant range,98period, range rate, Doppler and bounding pass duration against independently99computed reference values, both directions of the phase-to-orbit difference,100allowance comparison at the exact bound and the ranked disposition are101exercised by the gate 3 contract test: scripts/test_e50_orbits.py against102scripts/e50_orbits_logic.py (stdlib unittest, offline). Run:103python3 scripts/test_e50_orbits.py104105## Compliance106107- ECSS standards are freely downloadable (ESA); cite the source and108 paraphrase per standards-map.yaml.109- compliance: STANDARDS-REF, gated: false.