Skip to main content
You're offline. Cached data shown.
Guides9 min read

Understanding Satellite Link Budgets: A Practical Engineering Guide

A link budget is the fundamental accounting exercise that determines whether your satellite communication system will work. From transmit power to receiver noise floor, every dB matters. This guide explains the methodology that RF engineers use to close satellite links.

By SpaceNexus TeamMarch 22, 2026

A link budget is a systematic accounting of all the gains and losses in a radio frequency communication path, from the transmitter through the medium to the receiver. For satellite systems, where signal levels are at the edge of detectability and system margins determine mission success or failure, link budget analysis is not optional — it is foundational. This guide walks through the standard methodology, explains what each term means, and discusses the practical decisions that link budgets drive.

The Basic Link Budget Equation

The received signal-to-noise ratio (expressed as carrier-to-noise density, C/N₀) is the central result of a link budget. The simplified form is:

C/N₀ [dB-Hz] = EIRP [dBW] − FSPL [dB] + G/T [dB/K] − k [dBW/K/Hz]

Where:

  • EIRP — Effective Isotropic Radiated Power of the transmitter: transmit power plus antenna gain, minus cable/feed losses
  • FSPL — Free Space Path Loss: the geometric spreading of the signal over distance
  • G/T — Receive system figure of merit: receive antenna gain divided by system noise temperature
  • k — Boltzmann's constant: −228.6 dBW/K/Hz

From C/N₀, you derive Eb/N₀ (energy per bit to noise density) by subtracting the data rate in dB-Hz. Eb/N₀ is compared to the required Eb/N₀ for your chosen modulation and coding scheme (MODCOD) at the desired bit error rate (BER). The difference is your link margin — the safety buffer against real-world degradations.

Computing EIRP

EIRP is the product of transmitter power and antenna gain, referenced to an isotropic radiator. In dB terms:

EIRP [dBW] = P_tx [dBW] + G_tx [dBi] − L_feed [dB]

For a satellite downlink, P_tx is the transponder HPA (High Power Amplifier) output power — typically specified at saturation, with an output backoff (OBO) applied to reduce intermodulation for multi-carrier operation. A 100W TWTA operating at 6 dB OBO contributes only 25W (~14 dBW) of effective power.

Transmit antenna gain depends on aperture size and efficiency. A 1-meter parabolic reflector at Ku-band (12 GHz) achieves roughly 42 dBi gain with 60% efficiency. Phased array antennas offer electronic beam steering but introduce additional complexity in gain vs. scan angle performance.

Free Space Path Loss

FSPL in dB is computed as:

FSPL [dB] = 20 log₁₀(d) + 20 log₁₀(f) + 92.4

Where d is in km and f is in GHz. For representative cases:

  • LEO at 550 km, Ku-band (12 GHz): ~179 dB
  • GEO at 35,786 km, Ku-band (12 GHz): ~205 dB
  • GEO at 35,786 km, Ka-band (20 GHz): ~209 dB

The 26 dB difference between LEO and GEO is enormous — it is what allows LEO systems to use smaller ground terminals for equivalent data rates, or the same terminal to achieve dramatically higher throughput.

Receive System Noise: G/T

The receive figure of merit G/T combines the receive antenna gain with the total system noise temperature. System noise temperature (T_sys) includes contributions from:

  • Antenna noise temperature: Thermal emission from the ground (for satellite receive antennas) or sky (for ground terminal antennas); a ground-pointing satellite antenna at Ka-band sees ~290 K from the warm Earth
  • LNA noise temperature: The first amplifier in the receive chain; modern LNAs achieve 30–100 K at microwave frequencies
  • Feed loss: Ohmic losses between the antenna and LNA contribute noise equal to the physical temperature multiplied by the loss factor
  • Other receive chain components

G/T is maximized by high antenna gain and low noise temperature — both drive cost upward. Ground terminal G/T requirements directly set dish size and LNA specifications.

Atmospheric and Environmental Losses

Beyond FSPL, several additional loss mechanisms must be budgeted:

  • Rain attenuation: The dominant impairment above 10 GHz. At Ku-band, a 1% of time availability target typically requires 3–8 dB of rain fade margin for mid-latitude locations. Ka-band systems may require 8–15 dB. ITU-R P.618 provides the standard methodology.
  • Cloud and gaseous absorption: Oxygen and water vapor absorb at specific frequencies; a 0.5–2 dB allocation is typical for humid climates at Ku/Ka-band
  • Scintillation: Rapid signal fluctuations due to ionospheric and tropospheric irregularities; more significant at low elevation angles and high frequencies
  • Pointing losses: Antenna misalignment from satellite attitude errors or ground terminal mechanical tolerance; typically 0.1–0.5 dB allocated
  • Polarization mismatch: Cross-polarization isolation and polarization rotation effects; 0.1–0.5 dB typical

Required Eb/N₀ and Link Margin

The required Eb/N₀ depends on the modulation, forward error correction coding, and target BER. For DVB-S2 — the standard for satellite broadband — typical required Eb/N₀ ranges from approximately −2 dB (QPSK, 1/4 code rate) to 16 dB (32APSK, 9/10 code rate). ACM (adaptive coding and modulation) systems automatically select the highest-efficiency MODCOD that the current link can support, effectively using available SNR headroom to increase throughput rather than providing fixed margin.

A link margin of 3 dB for clear-sky conditions and system uncertainties is a minimum starting point; missions with high availability requirements or operation in harsh rain climates budget considerably more.

Practical Tips

  • Build your link budget in a spreadsheet with clear dB accounting — every term should be traceable to its source
  • Compute both uplink and downlink separately; the weaker link determines system performance
  • Check sensitivity to assumptions — vary G/T, rain margin, and pointing loss to understand which parameters most constrain your system
  • Use link budget results to drive antenna sizing, transmit power, and data rate requirements early in the design cycle, before hardware commitments are made

For orbital parameters needed to compute slant range and elevation angles for your link budget, see the SpaceNexus Orbital Calculator.

Share this article

Share:

Get space intelligence delivered weekly

Join 500+ space professionals who get our free weekly intelligence brief.

Get space industry intelligence delivered

Join SpaceNexus for real-time data, market intelligence, and expert insights.

Get Started Free