A ground station network earns its keep in the ten minutes a satellite is overhead. Everything else is preparation or postmortem. When a pass starts going sideways, the warning signs are short. Pointing drifts before lock is lost. Link margin erodes before bit errors spike. An HPA twitches off setpoint before it trips. Teams that wait for the postmortem are already working from data that’s a customer escalation.

These are the ten KPIs that decide whether a ground station network runs ahead of trouble or behind it.

Pass Success Rate

• Why it Matters: Every missed pass is unrecoverable revenue and a customer escalation. This number is what your largest accounts measure you against.
• What it Measures: The percentage of scheduled passes that delivered all telemetry, command, and mission data within contracted quality thresholds.
• What Happens if Missed: SLA penalties stack, customers re-evaluate provider mix, and your network reputation takes hits that take quarters to repair.
• Formula: (Successful Passes / Total Scheduled Passes) × 100
• Indicator Type: Lagging. Reflects what already happened, but trended over rolling windows it exposes systemic degradation early.
• Unit of Measure: Percent (%)
• Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking ground stations by failed-pass count
• Frequency: Every pass, rolled up hourly and daily
• Data Required: Pass schedule, pass completion status, data quality flags, customer acceptance status
• Pro Tip: Slice by satellite operator, antenna, and time of day. The averages always look fine; the slices tell the truth.
• Red Flag: A station hitting target on rate but failing a single customer disproportionately. Aggregate KPIs hide concentrated SLA risk.

Link Margin (Eb/No)

• Why it Matters: Link margin is your headroom against rain, interference, and pointing drift. When it collapses, the data goes with it.
• What it Measures: The difference between received energy-per-bit-to-noise ratio and the threshold required for the modulation and coding scheme in use.
• What Happens if Missed: BER climbs, retransmits multiply, and high-rate downlinks degrade or drop entirely. Mission data arrives late or corrupted.
• Formula: Eb/No_measured – Eb/No_required (in dB)
• Indicator Type: Current. A real-time view of how much link you have to spare before quality collapses.
• Unit of Measure: Decibels (dB)
• Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart against required threshold
• Frequency: Real-time, sub-second sampling
• Data Required: Received Eb/No, modulation scheme, coding rate, required Eb/No for current configuration
• Pro Tip: Plot margin against elevation angle for each pass. Sudden margin dips at high elevation usually mean the antenna, not the weather.
• Red Flag: Margin trending down across multiple satellites and stations simultaneously. That’s not weather, that’s a calibration or reference drift.

Antenna Pointing Error

• Why it Matters: A few millidegrees of pointing error at S-band is annoying. At Ka-band it costs you the pass.
• What it Measures: The angular distance between commanded antenna position and actual position during active tracking, in both azimuth and elevation.
• What Happens if Missed: Link margin erodes, autotrack falls off the satellite, and high-frequency missions become unworkable in marginal conditions.
• Formula: sqrt((Az_actual – Az_commanded)² + (El_actual – El_commanded)²)
• Indicator Type: Leading. Pointing degrades before link margin and bit error rate do, so it warns ahead of the failure.
• Unit of Measure: Millidegrees (m°)
• Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Pareto chart when ranking antennas by tracking error
• Frequency: Real-time, every servo cycle
• Data Required: Commanded azimuth, commanded elevation, encoder azimuth, encoder elevation, frequency band, tracking mode
• Pro Tip: Tracking error grows with wind. Correlate pointing residuals with anemometer data and you’ll predict pass risk hours ahead.
• Red Flag: Asymmetric error in azimuth versus elevation. Often points to a gear, encoder, or counterweight issue rather than wind.

Bit Error Rate (BER)

• Why it Matters: BER is the closest thing you have to ground truth on data quality. Everything downstream is hostage to it.
• What it Measures: The fraction of received bits in error after demodulation but before forward error correction, on a given link.
• What Happens if Missed: Retransmits eat throughput, mission products fail integrity checks, and customers stop trusting the data they’re paying for.
• Formula: Bit Errors / Total Bits Received
• Indicator Type: Current. Updates continuously during a pass and reflects the live state of the demodulation chain.
• Unit of Measure: Errors per bit (e.g., 1E-6)
• Ideal Visualization(s): KPI trend with real-time alerts, Histogram of BER across passes
• Frequency: Real-time, second-by-second during active pass
• Data Required: Demodulator error count, total received bits, modulation, FEC configuration
• Pro Tip: Pre-FEC BER tells you the real story. Post-FEC looks clean right up until it doesn’t, and by then the data is gone.
• Red Flag: BER good but frame sync repeatedly drops. Usually a clock recovery or AGC issue, not noise.

Acquisition of Signal (AOS) Timeliness

• Why it Matters: Every second late on AOS is a second of telemetry and command opportunity you can’t get back this orbit.
• What it Measures: The time difference between predicted AOS and actual carrier lock on the satellite during a scheduled pass.
• What Happens if Missed: Short LEO passes lose meaningful capacity, command queues run long, and critical commanding slips to the next contact.
• Formula: T_lock_actual – T_AOS_predicted
• Indicator Type: Lagging per pass. Trended across the network it signals scheduling, TLE, or RF chain warm-up problems.
• Unit of Measure: Seconds (s)
• Ideal Visualization(s): KPI trend with real-time alerts, Histogram of acquisition delays, Pareto chart when ranking stations by late-AOS frequency
• Frequency: Every pass
• Data Required: Predicted AOS time, actual carrier lock time, TLE epoch, antenna pre-position status, RF chain ready status
• Pro Tip: Persistent five-second late AOS across a station usually means stale TLEs or a slow handoff between scheduling and the antenna controller.
• Red Flag: Late AOS that improves mid-pass with autotrack means you’re acquiring on signal, not on prediction. Your ephemeris pipeline is drifting.

Gain over Temperature (G/T)

• Why it Matters: G/T defines the smallest signal your station can pull out of noise. It caps every link budget you build.
• What it Measures: Antenna gain divided by system noise temperature, expressed as a single figure of merit for receive sensitivity.
• What Happens if Missed: Low elevation and weak-satellite passes start failing first. You’ll discover the degradation only when customers complain.
• Formula: G/T = Gain (dBi) – 10·log10(Tsys) (dB/K)
• Indicator Type: Leading. Degrades slowly with LNA aging, feed contamination, or cooling failures, well before link metrics react.
• Unit of Measure: Decibels per Kelvin (dB/K)
• Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Pareto chart when ranking antennas by G/T degradation
• Frequency: Daily measurement during noise-figure check, continuous when noise calibration is active
• Data Required: Antenna gain calibration, LNA noise temperature, feed and waveguide losses, ambient temperature
• Pro Tip: Run noise-figure checks on a fixed schedule with the antenna at zenith. Drift here is the earliest warning of LNA failure.
• Red Flag: G/T drops correlate with rain or wind. Weather is reaching your feed or LNA enclosure where it shouldn’t.

Antenna Availability

• Why it Matters: A booked antenna that won’t track is worse than no antenna at all. The schedule already promised it.
• What it Measures: The percentage of scheduled antenna time that the system was fully ready and capable of executing a pass.
• What Happens if Missed: Passes get reassigned in panic, customers absorb hits to their own missions, and SLA credits start eating margin.
• Formula: (Available Antenna Hours / Scheduled Antenna Hours) × 100
• Indicator Type: Lagging. Reports actual delivered capacity, and the breakdown by cause is what drives the maintenance plan.
• Unit of Measure: Percent (%)
• Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking antennas by downtime cause, Status history trends
• Frequency: Continuous, rolled up daily and weekly
• Data Required: Scheduled antenna time, actual ready time, fault state, maintenance windows
• Pro Tip: Track planned versus unplanned downtime separately. The blended number always looks acceptable; only the unplanned slice exposes real reliability.
• Red Flag: Same antennas appearing repeatedly in unplanned downtime. Concentration in one or two assets points to a systemic fault no one is owning.

Schedule Utilization Rate

• Why it Matters: Antennas are capital that depreciates whether they’re tracking or sitting idle. Empty minutes are money you’ve already spent.
• What it Measures: The percentage of available antenna minutes booked against demonstrated capacity, after maintenance and reserve windows are excluded.
• What Happens if Missed: Capacity planning loses credibility, new customer onboarding stalls, and the network grows in the wrong places at the wrong time.
• Formula: (Booked Minutes / Available Minutes) × 100
• Indicator Type: Current. Tells you in near real-time how full the network is and where there’s headroom to sell.
• Unit of Measure: Percent (%)
• Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart, Pareto chart when ranking stations by utilization
• Frequency: Hourly, with daily and weekly rollups
• Data Required: Schedule database, antenna availability, maintenance calendar, contractual reservations
• Pro Tip: Watch the gap between booked and executed minutes. Cancellations and reschedules quietly burn capacity that the booking number says is full.
• Red Flag: High utilization with rising last-minute cancellations. The schedule looks full, but executed minutes are quietly draining and capacity planning is wrong.

Doppler Tracking Error

• Why it Matters: LEO satellites move at orbital velocity. Bad Doppler tracking means lost lock and a useless pass.
• What it Measures: The frequency offset between the predicted Doppler-compensated carrier and the actual received carrier during a tracked pass.
• What Happens if Missed: Modems lose lock mid-pass, telemetry frames drop, and high-rate downlinks fail to close even when geometry is favorable.
• Formula: |f_received – f_predicted|
• Indicator Type: Leading. Tracking error climbs before lock is lost, giving you a short window to react.
• Unit of Measure: Hertz (Hz)
• Ideal Visualization(s): KPI trend with real-time alerts, XY scatter plot of error versus elevation, SPC trend
• Frequency: Real-time, every second during pass
• Data Required: Predicted Doppler, measured received frequency, reference oscillator status, modem lock status
• Pro Tip: Compare Doppler error across passes for the same satellite. Persistent bias points to your reference, not the satellite.
• Red Flag: Doppler error spikes only on specific satellites. Often your TLE source for that constellation is stale or low-priority in the pipeline.

HPA Forward Power Stability

• Why it Matters: Unstable HPA output kills uplink quality and risks the amplifier itself. Both outcomes are expensive and visible.
• What it Measures: The deviation of high-power amplifier forward output power from setpoint during active uplink, over a defined window.
• What Happens if Missed: Uplink BER degrades, command rejections rise, and at the extreme you damage the HPA or the feed.
• Formula: |P_forward – P_setpoint| / P_setpoint × 100
• Indicator Type: Current. Live measurement of the transmit chain, with deviations almost always preceding a hard fault.
• Unit of Measure: Watts (W) or percent deviation (%)
• Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Bullet chart
• Frequency: Real-time during transmit
• Data Required: Forward power, reflected power, setpoint, HPA temperature, drive level
• Pro Tip: Pair forward power with reflected power on one view. Swings without VSWR change usually mean the drive chain, not the antenna.
• Red Flag: Forward power steady but reflected power climbing. That’s the antenna or waveguide telling you something cracked, iced, or shifted.

Why Real-Time Visibility Matters

Ground station operations live or die on what you can see during the pass, not after. A late AOS, a millidegree of pointing drift, an HPA twitching off setpoint: each one has minutes of warning before it costs you a customer minute. The teams that catch them in time are the ones with eyes on every link, every antenna, and every schedule slot, at the rate the satellites actually move.

The cost of operating blind isn’t theoretical. It’s a missed weather observation, a delayed Earth-observation tasking, a constellation operator looking at downtime credits and wondering whether your network is still the right one. The KPIs above are what turn a ground station from a reactive bottleneck into a predictable, sellable piece of capacity.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us