Rodger's Sat Tracker
Engineering View Of A Standalone Satellite Tracker
The app is approachable for any satellite user. This site presents the engineering layer underneath it: live SGP4 propagation, NORAD TLE refresh, Doppler correction, GPS-derived QTH, orbital ground tracks, and space-weather decision support.
Orbital Dynamics Core
Rodger's Sat Tracker tracks satellites from current NORAD two-line elements through SGP4, then converts the propagated state into the operator quantities that matter during a pass: subpoint, altitude, footprint, slant range, elevation, azimuth, and live RF Doppler.
Live CelesTrak TLEs create the satellite record, then SGP4 propagates the ECI state for the selected NORAD object. That position becomes the source for every map, pass, and RF calculation. It also keeps every visible label tied to the current epoch and selected satellite.
Observer latitude, longitude, altitude, and satellite range resolve into local azimuth and elevation. The interface uses that geometry to mark above-horizon tracks, pass windows, and pointing decisions. That station frame keeps pass visibility and antenna motion physically grounded.
Relative range-rate from the propagated pass becomes a live Doppler estimate for receive and transmit planning. The RF pane keeps frequency offset tied to the current spacecraft geometry. This prevents tuning decisions from drifting away from the pass geometry.
Orbital altitude determines the visibility cone and footprint radius on Earth. The map turns that geometry into a practical coverage, acquisition, and station-in-range decision tool. Operators can quickly see whether the ground site sits inside the usable pass footprint.
Operations Console
The application combines pass prediction, live telemetry, antenna pointing, Doppler, local QTH, solar flux, Kp index, X-ray flux, HF band state, DX cluster, and AMSAT news in the same workflow. This page exposes those engineering relationships for a technical audience.
Switch between a textured Earth globe and a ground-track map with footprints, day/night shading, trails, and selected satellite labels.
AOS, LOS, maximum elevation, current state, and countdowns are surfaced where an operator can act on them quickly.
GPS/manual QTH feeds latitude, longitude, altitude, and grid square calculations for accurate local tracking geometry.
Application Screens
These are actual Rodger's Sat Tracker application views. Each one is tied to the calculation, signal decision, or orbital-control problem it helps an operator solve.
The screen combines the propagated orbit, observer geometry, and RF state so the operator does not have to cross-check separate tools during a live pass.
2D Map / Ground Track / Footprint
The 2D map is where Rodger's Sat Tracker makes the SGP4 state visible: current subpoint, future path, footprint rings, day/night context, pass table, Doppler status, and sky-view pointing all sit in one operator frame.
Why it matters: the operator can see where the spacecraft is, where it is going, whether the ground station is inside the visibility footprint, and whether the pass is actionable right now. The map also keeps pass timing, footprint geometry, sky-view pointing, and Doppler state tied to the same propagated object instead of forcing separate cross-checks.
The globe view makes frame rotation, orbital plane, illumination, and moving subpoint geometry visible at the same time. It keeps Earth-fixed context, orbit arc direction, and sun geometry in one spatial readout.
3D Globe / Earth Frame / Sun Marker
The 3D globe view makes inclination, orbital plane, subpoint motion, Earth rotation, and sunlight geometry easier to understand than a flat map alone. It is especially useful for explaining why the same spacecraft can appear rapidly changing in azimuth and elevation during a LEO pass.
Why it matters: the 3D view gives engineers an immediate mental model of orbit plane, Earth-fixed projection, lighting, and relative motion. It also shows why ground-track motion and sky-view motion can change quickly during the same LEO pass. That makes the display useful for explaining why a satellite can look smooth on the map while sweeping rapidly across the local sky. The same view helps compare orbit arc, Earth rotation, illumination, sun marker placement, and moving subpoint geometry in one operator-readable frame.
Tools / Mission Workflow
The tools menu is not filler. It is a structured entry point into setup, tracking, ground track detail, station reference, propagation weather, band condition, and source-reference views.
Why it matters: engineers can audit each input to the final contact decision instead of treating the tracker as a single opaque display. The tools menu keeps setup, station geometry, propagation weather, RF planning, and reference checks separated enough to verify before a live pass.
The dialog creates the identity link that keeps every later map, pass, Doppler, and mode calculation attached to the correct spacecraft. The NORAD ID selects the TLE source, the name keeps the operator label readable, and the category preserves RF context for the rest of the workflow.
This prevents a visual label, RF mode, pass table, and propagated state from drifting into separate meanings. One clean catalog binding becomes the shared key for map labels, Doppler calculations, sky-view pointing, and operator notes.
NORAD ID / TLE Binding
Adding a satellite by NORAD catalog number lets Rodger's Sat Tracker bind a human-readable satellite entry to the two-line element set used by SGP4. The category also drives RF and operator context such as crewed, FM, linear, weather, and APRS tracking modes, so the selected object carries both orbital state and mission meaning.
Why it matters: the catalog number is what keeps pass prediction, map labeling, Doppler, and satellite-specific workflow tied to the correct object. Without that binding, an operator could trust a clean-looking track while using the wrong spacecraft identity, RF category, or TLE epoch.
This is the operator-facing reduction of the full orbital solve: where to point, what frequency offset to expect, and how much pass time remains.
Track Status / Az-El / Range / Doppler
This dashboard translates propagated position into the numbers an operator needs while the pass is happening: azimuth, elevation, range, subpoint, uplink/downlink frequency, mode, and time to LOS or AOS.
Why it matters: LEO passes move fast. If azimuth, elevation, and Doppler are not presented together, the operator is forced to stitch together time-critical decisions manually.
The graph is a time-indexed orbit trace, not a static picture. It shows how the pass approaches, peaks, and exits the station footprint.
Ground Track Detail / Past-Future Sampling
Rodger's Sat Tracker samples the selected satellite backward and forward in time around the current instant. The result is a past track and future track that explain where the satellite came from, where it is going, and when it crosses the local horizon.
Why it matters: the operator sees whether the pass is rising, peaking, or falling, and can understand the sky movement before it becomes urgent.
Every pass calculation is local to the observer. This screen exposes the station frame before azimuth, elevation, range, and Doppler are trusted.
GPS Detail / QTH / Maidenhead Grid
All azimuth, elevation, range, and Doppler values depend on the observer position. The GPS/QTH screen makes that input explicit: source, latitude, longitude, altitude, grid square, enabled satellite count, and sky plot.
Why it matters: a small QTH error becomes a real antenna-pointing and timing error during low-elevation passes.
The app keeps space-weather context near the pass data so failed contacts can be diagnosed as geometry, RF setup, or propagation conditions.
Space Weather / Kp / Solar Flux / X-Ray Flux
The space weather screen gives operators solar flux, sunspot count, Kp, X-ray class, and HF outlook in the same workstation. It helps explain whether link conditions are being shaped by the satellite pass or by the propagation environment.
Why it matters: when a contact fails, the operator needs to separate geometry, station setup, and propagation conditions instead of guessing.
The bars turn solar-flux thresholds into a quick planning layer while the formulas show the scoring logic behind the visual result.
Band Conditions / SFI Scoring
Rodger's Sat Tracker uses observed solar flux and band-specific thresholds to label bands as POOR, FAIR, or GOOD with a percentage-style readout. The exact score is intentionally operator-facing: it compresses propagation context into something usable during planning.
Why it matters: engineers can see the threshold logic behind the visual bars instead of reading a black-box propagation label.
Why The Features Matter
Fresh two-line elements keep the state vector aligned with the catalog.
The predicted orbit becomes latitude, longitude, altitude, ground track, and orbital trail.
Station coordinates determine whether the satellite is usable and where antennas must point.
Frequency offset and AOS/LOS timing keep the operator synchronized with fast-moving LEO passes.
Engineering References
Rodger's Sat Tracker sits at the intersection of orbital mechanics, amateur satellite operations, RF Doppler correction, ground-station practice, and space-weather interpretation. These links and books are included as engineering context, not decorative filler.
Best fit for SGP4, ECI/ECEF transforms, perturbation thinking, and practical implementation details.
Strong background for conics, two-body motion, state vectors, orbital elements, and time-of-flight reasoning.
Useful systems context for why tracking, ground station geometry, communications, and operations constraints matter together.
Practical bridge between the equations, antennas, radios, Doppler correction, FM/linear satellites, and real operator workflow.
Accessible App / Technical Website
Rodger's Sat Tracker is a standalone Windows application for practical satellite work. The app stays approachable for everyday operators, while this website explains the technical layer behind each operator decision.
Refreshed NORAD TLEs stay tied to the selected catalog identity while SGP4 propagates the spacecraft state forward in UTC. The interface turns that state into position, velocity, ground track, subpoint, altitude, and coverage footprint geometry. That same state drives visibility, timing, map labels, and pass decisions.
The 2D map, 3D globe, sky-view pointing, AOS/LOS timing, visible-pass state, and pass tables stay in one operator frame so antenna direction, pass timing, and spacecraft motion remain readable together. Engineers can check current visibility, future motion, and operator action without leaving the tracking view.
Range-rate is translated into live Doppler correction for receive and transmit planning. FM, linear, weather, APRS, and crewed categories preserve operating context beyond raw orbital position. Tuning decisions stay tied to pass geometry, elevation, and mode category as range changes through the contact.
GPS QTH, Maidenhead grid, space weather, HF band conditions, DX cluster context, AMSAT news, and reference sources keep propagation and operating decisions close to the pass workflow. The operator can see whether a pass issue is orbital, station-location, radio, or propagation related.
