Skip to main content

LEO contact scheduling

A low Earth orbit satellite is in view of a given ground station for minutes at a time, a few times a day. Contact scheduling chooses which of those passes to book, on which antenna, so the data and commands you need get through. A good contact plan ranks passes by what they will deliver, not just by when they happen.

1. Predict the passes​

A pass runs from acquisition of signal (AOS), when the satellite rises above the antenna's elevation mask, to loss of signal (LOS), when it sets below it.

  • Orbit. Constellation propagates each satellite with SGP4, from the newest element set in its orbit catalog or from the TLE you give the satellite. See Satellite.
  • Mask. Set each antenna's min_elevation_deg to its real horizon. See Antenna.
curl --fail-with-body -sS -G \
-H "x-api-key: $CONSTELLATION_API_KEY" \
"https://api.constellation.space/topology/passes" \
--data-urlencode "from=2026-11-10T00:00:00Z" \
--data-urlencode "to=2026-11-11T00:00:00Z" \
--data-urlencode "step_s=60"

Each pass has its AOS, LOS, duration, peak elevation and a pass_id that stays the same across windows. A read over more satellites x antennas x steps than one listing computes is refused with 422 too_many_link_steps: split it by antenna or by time, as the Platform does for you. See Passes.

2. Rank them by what they deliver​

Two passes of the same length can deliver very different amounts. Rank on:

SignalSource
Expected GB, p10 to p90The pass-yield workflow. See Predict pass data volume.
Contention at the stationThe Satellite demand model
Weather riskThe rain-fade-swap workflow, which also names a backup pass

3. Keep the plan current​

Weather moves and element sets age, so a plan made yesterday drifts. Run the workflow again as the window approaches: results are keyed by pass, so a connector updates what it wrote in Yamcs, COSMOS or Lattice instead of adding a copy. A forecast pass is never written as a scheduled contact: the operator books.

Contact planning with forecasts is measured in our post on contact planning.

Common questions​

How long is a LEO satellite pass?

It depends on the orbit altitude and how close the ground track runs to the station. For a satellite a few hundred kilometres up, an overhead pass lasts on the order of ten minutes above a low mask, and low passes much less. The passes route returns each pass AOS, LOS, duration and peak elevation.

Which propagator do Constellation pass times come from?

Standard SGP4, from the satellite current element set or the TLE you gave it. Propagate the same element set with SGP4 and your pass times should line up.

Why do predicted pass times drift from real ones?

Element sets age. The further a time is from the set epoch, the larger the along-track error. Send a newer TLE whenever you have one.

Next: see the passes of the demo fleet ranked by expected GB, before you describe your own.