How Does Satellite Tracking Software Work and How Do You Start Tracking?
Satellite tracking software predicts where a satellite is at any moment and when it will pass within range of your location, so you can point an antenna, schedule a contact, or just watch it cross the sky. The core inputs are simple: your observer coordinates and a current set of orbital data (TLEs). Gpredict is a free, real-time satellite tracking and orbit prediction program for Linux, Mac OS X, and Windows, and it is a useful concrete example of how these tools work. This explainer covers the mechanism, the setup steps, and the problems that most often break a tracking session.
What satellite tracking actually means
Tracking has two related meanings, and it helps to keep them apart:
- Position tracking — knowing where a satellite is right now, usually shown on a world map with its ground track and footprint (the area of Earth from which it is visible).
- Pass prediction — knowing when that satellite will rise above your local horizon, how high it will get (maximum elevation), and when it will set.
For radio work, a third layer matters: Doppler shift. As a satellite moves toward you and then away, the frequency you hear drifts. Tracking software calculates this offset so you can retune during a pass.
Why orbit data (TLEs) drives everything
Tracking software does not measure the satellite directly. It propagates an orbital model forward in time. The standard input is a TLE — a Two-Line Element set, a compact text description of a satellite's orbit at a given epoch.
Key consequences:
- TLEs go stale. Atmospheric drag and other forces make the real orbit drift from the prediction. A TLE a few days old may be fine for a rough look; for precise antenna pointing or Doppler tuning, fresher data is better.
- You need a current source. Most trackers can download TLEs automatically from a catalog such as Celestrak or Space-Track. The update interval is a setting worth checking.
- The epoch matters. If your software is using an old element set, your pass times will be off even if your clock and coordinates are perfect.
Core features to expect
| Feature | What it does | Why you care |
|---|---|---|
| Real-time map | Shows satellite position and ground track | Situational awareness, spotting the footprint |
| Pass prediction | Lists upcoming passes with start, max elevation, end | Planning when to be outside or at the radio |
| Doppler correction | Computes frequency offset during a pass | Keeps a narrowband signal in tune |
| Multiple satellites | Tracks many objects at once | Choosing the best pass among several |
| Rotator control | Sends azimuth/elevation to an antenna rotator | Automated pointing |
Setting up a tracker like Gpredict
The general workflow is the same across most tracking programs:
- Set your observer location. Enter latitude, longitude, and altitude. This is the single most common source of wrong results — a sign error or a swapped lat/long puts you on the other side of the planet.
- Check your clock and time zone. Predictions are time-sensitive. Make sure the system clock is accurate and the time zone is correct, especially if you compare pass times with other people.
- Load or download TLEs. Add the satellites you want and point the software at a current TLE source, or import a file you downloaded.
- Refresh the elements. Set an update interval, or manually re-download before an important session.
- Read the pass list. Look at start time, maximum elevation, and duration. Higher maximum elevation generally means a better, longer contact.
- Optionally connect hardware. If you have a rotator or radio, configure the interface so the software can point the antenna and apply Doppler correction.
Expected result: a list of upcoming passes for your location, and a map showing the satellite's current position and footprint.
Common problems and how to spot them
- Stale TLEs — pass times drift by minutes. Symptom: the satellite is not where the software says. Fix: refresh the elements.
- Wrong observer coordinates — every pass looks wrong or the satellite never rises. Symptom: predictions that make no sense for your area. Fix: re-check latitude, longitude, and sign conventions.
- Time-zone or clock errors — pass times are offset by whole hours. Symptom: consistent shift between your software and a reference. Fix: verify system time and zone.
- Confusing UTC with local time — most tracking tools display UTC. Symptom: you show up an hour or more early or late. Fix: convert deliberately.
- Elevation mask too high or low — you either miss low passes or get unusable ones. Fix: adjust the minimum elevation setting to match your horizon and antenna.
A note on the source
The site at oz9aec.dk, which describes Gpredict as free, real-time satellite tracking and orbit prediction software for Linux, Mac OS X, and Windows, currently shows only an "under construction" page. Treat the description as the project's stated purpose rather than a live download or documentation source; for current files and instructions, look for the project's own distribution channel.