Short answer: size a satellite dish from the link budget, not the frequency band alone. Calculate the receive gain needed to meet the modem threshold after path losses and availability margin, then convert that gain to diameter with D = (λ/π) × √(G/η), using linear gain G and aperture efficiency η. Select a standard size that meets that requirement and, for a two-way terminal, also passes the uplink budget. The 12 GHz example below needs about 1.3 m before rain margin; it is not a universal Ku-band size. Free-space loss is the starting point, not the complete budget [1].

What Sets the Dish Size You Need

Start with frequency, satellite EIRP at the site, data rate and modem threshold, receiver noise, availability target, path geometry, and operating constraints. At fixed frequency and efficiency, an extra 3 dB of antenna gain requires about 41% more diameter. Band and data rate alone are not enough to select a dish.

Frequency band

At an assumed 60% aperture efficiency, a 1.2 m dish has a calculated gain of about 41.4 dBi at 12 GHz and 45.8 dBi at 20 GHz. Free-space loss also rises by about 4.4 dB between those frequencies. Higher gain alone therefore does not establish a smaller required dish. Evaluate the actual EIRP, receiver noise and propagation conditions on each link; use Earth-space prediction methods for the site-specific atmospheric effects [2].

Satellite and coverage

Use the operator’s EIRP contour at your coordinates, for the relevant beam and carrier operating conditions, rather than the beam-peak brochure value. A 3 dB reduction in available EIRP requires 3 dB more receive gain if everything else stays fixed. That correction can change the selected diameter even though the service and frequency have not changed.

Service and data rate

With the same modulation, coding and required energy per bit relative to noise density, doubling bit rate requires about 3 dB more carrier power if noise density is unchanged. A change of modulation or coding can change that requirement. Use the modem’s specified threshold, bandwidth and implementation allowance rather than assuming every faster service needs the same gain increase.

Availability target

On a 365-day basis, 99.9% availability allows about 8.8 hours of outage per year; 99.5% allows 43.8 hours. These are outage allowances, not predictions of actual downtime. Decide how much of the service outage budget belongs to propagation rather than equipment or network failures, then calculate the atmospheric allowance for that target [2].

Path geometry

For a GEO geometry calculation with a spherical Earth radius of 6,378 km and orbital radius of 42,164 km, the overhead distance is 35,786 km. Slant range is about 38,612 km at 30° elevation, 40,586 km at 10°, and 41,127 km at 5°. Those distances add approximately 0.66, 1.09 and 1.21 dB of free-space loss relative to overhead. Atmospheric effects must be calculated separately; these distance-only penalties do not describe the full low-elevation link [2].

Regulatory limits

A transmit antenna must meet the applicable radiation-pattern requirements as well as its on-axis gain target. For example, U.S. 47 CFR 25.209 specifies earth-station antenna performance envelopes for defined services and bands; the 2025 annual edition documents those requirements. It is not a universal minimum-diameter rule. Confirm the current rules, authorization and operator acceptance requirements for the proposed terminal before ordering [3].

The Sizing Workflow

Define the service requirement

List carrier bandwidth, modulation and coding, the needed carrier-to-noise ratio, and the uptime target (99.5% or 99.9% across the year serve as common examples). The modem specification and the service contract supply them.

Collect satellite, site and receiver data

Record satellite EIRP at the site, uplink and downlink frequencies, polarization, coordinates, altitude, elevation angle, and receiver system noise temperature or noise figure. For a two-way budget, also obtain satellite receive G/T and the terminal amplifier’s usable output power. Frequency and polarization affect the specific rain attenuation coefficients; those coefficients are inputs to a path prediction, not the complete rain fade by themselves [4].

Calculate path and hardware losses

Work from free-space loss first [1]:

FSPL = 20log10(4πd/λ)

where d is the path distance and λ is the wavelength in the same units. With distance in km and frequency in GHz the working form reads:

FSPL = 20log10(d) + 20log10(f) + 92.45 (dB)

Add the remaining terms from models and measured hardware data:

• Rain attenuation and relevant scintillation effects, combined according to the applicable prediction method rather than by adding unrelated worst cases [2].
• Gaseous absorption and cloud attenuation [5] [6].
• Feed and waveguide losses
• Pointing and polarization mismatch losses

Record the value, source and reference plane of each loss. Do not subtract a feed loss separately if it is already included in the antenna gain or receiver specification being used.

Find the required antenna gain

Received power = EIRP − path losses + receive antenna gain

Use dBW for both power terms, dB for losses and dBi for gain, all at consistent reference planes. Rearranging gives:

Required gain (dBi) = required received carrier power (dBW) − EIRP (dBW) + total losses (dB) + any separately allocated reserve (dB).

If the modem specifies C/N rather than received power, first calculate receiver noise over the stated noise bandwidth. Alternatively, use a consistent G/T-based budget, where G/T is antenna gain relative to system noise temperature. Include the availability-related attenuation once, and keep any additional implementation or aging reserve explicit. A larger dish does not remedy every source of service outage.

Convert gain to diameter

A parabolic reflector obeys:

G = η × (πD/λ)² (linear), or in decibels: GdBi = 10log10(G)

Here D and λ use the same length units. For this circular-aperture sizing model, η is aperture efficiency; 0.60 is an assumption used in the calculations below, not a guaranteed product specification. Obtain the antenna’s actual gain or efficiency at the operating frequency. Other aperture shapes and scanned arrays need their own effective-area and scan-loss treatment.

D = (λ/π) × √(G/η)

If the budget result is in dBi, convert it first: G = 10^(GdBi/10). Substituting a dBi number directly into the square root produces the wrong diameter.

Select a standard size and verify it

Select the next available size that meets the fully margined requirement, then repeat the budget with its specified gain. Product families such as 1.2 m quick-deploy terminals and larger earth-station antennas serve different installation needs; diameter alone does not establish compatibility. Check the relevant band and configuration within the SATCOM antenna range, then verify:

• Does the transmit side still meet its EIRP with your available amplifier?
• Do the mount and foundation suit the wind load?
• Can your pointing accuracy hold a beam that narrows as the dish grows?

A Ku-Band Worked Example

This is a calculation example with stated assumptions, not a measurement or a guarantee for any site.

Consider a GEO downlink at 12 GHz directly beneath the satellite. Distance equals the standard 35,786 km and λ stands near 0.025 m. Free-space loss becomes:

FSPL = 20log10(35,786) + 20log10(12) + 92.45 ≈ 91.08 + 21.58 + 92.45 ≈ 205.1 dB [1]

Assume 50 dBW satellite EIRP at the site, a required carrier power of −115 dBW at a defined receiver input, and 2 dB of combined clear-sky atmospheric and hardware losses to that input. The carrier threshold is an assumed input, not a modem specification. The 2 dB excludes rain attenuation and additional reserve. The clear-sky requirement becomes:

Required gain = −115 − 50 + 205.1 + 2 ≈ 42.1 dBi.

The linear gain is about 16,200. At 60% efficiency, D = (0.025/π) × √(16,200/0.60) ≈ 1.3 m before rain margin.

What changes when margin is added?

Suppose the same illustrative budget requires another 3 dB in total for rain attenuation and reserve. This is an assumed sensitivity check, not a weather prediction. The gain target becomes about 45.1 dBi and the calculated diameter about 1.85 m. Under the same efficiency assumption, a 1.8 m dish gives 44.9 dBi and falls short; a 2.4 m dish gives 47.4 dBi and exceeds the target by about 2.3 dB. This is why rounding the clear-sky result to 1.8 m is not enough to approve the link.

For an actual purchase, replace the assumed 3 dB with the site’s propagation result and allocated reserve, use the candidate antenna’s specified gain, and check the uplink separately. Keep the EIRP contour, modem threshold, loss allocation and antenna specification with the calculation so another engineer can reproduce the selection.

How Band Choice Changes the Size You Need

Read the table below as a sizing warning: it assumes the standard 35,786 km GEO distance with 60% efficiency [1]:

For fixed satellite EIRP, distance, receive diameter and efficiency, the frequency-dependent gain increase cancels the free-space-loss increase in this simplified comparison. The table does not prove that Ka-band always needs a larger dish or that the highest frequency sets the size. Actual beam EIRP, noise, service threshold, atmospheric attenuation and transmit constraints decide which budget is limiting [2].

What Size Matches Your Gain Target at 12 GHz

These are calculated gains at 12 GHz and 60% efficiency, not measured product data. Choose a row at or above your fully margined gain target, then verify the candidate’s specified performance. The gain difference is relative to a 1.2 m dish, not a site-specific rain allowance.

Doubling diameter adds about 6 dB at unchanged efficiency. That is a gain increase, not a guarantee of a particular availability level.

Sizing Checks Buyers Often Skip

A rough full half-power beamwidth estimate is 70λ/D degrees; the coefficient depends on illumination. At 12 GHz it gives about 1.5° for a 1.2 m dish and 0.7° for a 2.4 m dish. This is beamwidth, not an allowable pointing error. Compare the actual pattern with installation accuracy, wind deflection and any tracking requirement.

The feed horn affects illumination and aperture efficiency, while losses in the waveguide chain depend on the hardware and reference plane. Check those specifications separately. For custom antenna feed systems, confirm feed-to-reflector compatibility rather than assuming a matching change will recover a fixed number of decibels.

C-band smoothness does not guarantee Ka-band service. Small surface errors scatter power from the main beam at short wavelengths. Rate the antenna by its specified band as well as diameter, or the dish underperforms its nameplate size.

On a two-way link, check usable amplifier power, transmit feeder loss and antenna gain together against the uplink requirement and applicable limits. If future capacity matters, budget that future service explicitly; an arbitrary extra size is not a substitute for calculating the requirement.

The Short Answer to Keep

Choose the smallest standard dish that meets the fully margined receive and transmit budgets, required antenna patterns, and installation constraints. Keep the assumptions with the result: without the site EIRP, receiver threshold, propagation allowance and actual antenna gain, a diameter is only a preliminary estimate.

[1] ITU-R P.525, Calculation of free-space attenuation (P.525-5 in force).

[2] ITU-R P.618, Propagation data and prediction methods for Earth-space systems (P.618-14 in force).

[3] U.S. Government Publishing Office, 47 CFR 25.209, Earth station antenna performance standards, 2025 annual edition.

[4] ITU-R P.838, Specific attenuation model for rain (P.838-3).

[5] ITU-R P.676, Attenuation by atmospheric gases and related effects (P.676-13).

[6] ITU-R P.840, Attenuation due to clouds and fog (P.840-9).

The post How Do You Size a Dish for a Satellite Link? appeared first on DOLPH MICROWAVE.

For a fixed site using a geostationary satellite, start with a fixed parabolic dish. For broadband while moving, or a directional link to LEO/MEO satellites, use an operator-approved electronically steered panel or a mechanically tracking dish. Large gateways often use dual-reflector dishes; handheld and low-rate services may use compact patch, helical, or omnidirectional antennas. The right choice depends on the service first, then motion, required link performance, and installation limits—not the antenna shape alone.

Five Fit Decisions

1. Separate site motion from satellite motion. A fixed GEO site can retain one alignment. A fixed LEO/MEO site may still need tracking; a moving platform also needs motion compensation for a narrow-beam link. Broad-beam low-rate terminals do not necessarily need continuous antenna steering.
2. Identify the orbit. Geostationary satellites orbit above the equator at about 35,786 km and appear stationary to a ground observer. NASA places LEO at approximately 160–2,000 km and MEO at approximately 2,000–35,500 km. [1] Geostationary orbit is a special case of geosynchronous orbit; an inclined geosynchronous satellite does not stay at a fixed point in the sky. [2]
3. Use exact operating frequencies. ESA lists broad letter-band ranges including C at 4–8 GHz, Ku at 12–18 GHz, and Ka at 26–40 GHz. These names are not substitutes for the service’s licensed receive and transmit ranges. Higher-frequency services typically offer wider bandwidth but are more susceptible to rain fade. [3] Use site rainfall, elevation angle, frequency, and polarization with an Earth-space propagation method such as ITU-R P.618-14 to estimate attenuation and the required fade margin. [4]
4. Size for the link budget. Compare warranted receive performance, transmit performance, and beamwidth at the actual operating frequencies. The calculated examples below show how diameter and frequency affect gain; they are not product specifications.
5. Check installation and interference limits. Include height, weight, power, cooling, wind loading, and mounting constraints. In the US, 47 CFR 25.209 sets earth-station antenna performance requirements that depend on the applicable band, polarization, and angular region; one envelope term is 29 − 25 log₁₀(θ), with θ in degrees. It is not a universal mask for every antenna. [5]

Antenna Types Compared

Fixed parabolic dish

A fixed parabolic dish fits stationary GEO television, broadband, and enterprise links. An offset-fed design keeps the feed out of the main aperture. Select its diameter from the operator’s approved options and the site link budget, rather than assuming every home or VSAT link needs the same size. The mount must retain alignment under the specified environmental conditions.

Dual-reflector dish

Cassegrain and Gregorian layouts use a sub-reflector and are candidates for gateways and teleports requiring high gain and carefully controlled patterns. Dolph’s catalogue includes an 11.3 m earth-station antenna within its SATCOM antenna range. Diameter and reflector layout alone do not establish noise performance, sidelobe compliance, or suitability for a particular operator.

VSAT system

VSAT—very small aperture terminal—is a terminal class, not a separate reflector shape. A two-way installation needs an antenna, compatible feed, mount, transmit and receive RF equipment, and modem. For a stationary GEO service, a fixed dish is a natural starting point. Confirm the complete terminal configuration with the operator, including frequencies and polarization, before comparing aperture sizes.

Electronically steered flat panel

An electronically steered panel changes beam direction without rotating the whole antenna. It fits applications where profile, retargeting, or motion compensation matter, provided the network supports that terminal. Compare warranted equivalent isotropically radiated power (EIRP) and receive gain-to-noise-temperature ratio (G/T) across the required scan range, not just broadside gain. Include power draw, cooling, obstructions, and radome losses.

Mechanically tracking and stabilized dishes

A mechanically tracking reflector follows a moving satellite; a stabilized installation also compensates for platform motion. Those are distinct requirements. For fixed-site non-GEO work, X/Y-axis LEO/MEO tracking antennas are one configuration to investigate. A ship or aircraft needs an installation specifically rated for its motion environment. Confirm tracking rate, pointing accuracy, acquisition, and network handover behavior separately.

Horn feed and reference

Horns illuminate reflectors and serve as test sources or standard-gain references. For the broadband ground-terminal applications discussed here, a horn is normally a feed or measurement component rather than an alternative to the complete dish or panel. Whether any antenna can close a particular satellite link remains a link-budget question.

Compact low-rate antennas

Compact patches, helices, and omnidirectional antennas can suit handheld or low-rate services when their coverage and polarization match the network. Directional helices and Yagis can provide more gain, but may need pointing or tracking; they should not all be treated as broad-beam antennas. Choose the pattern to suit the link’s pointing constraints, rather than grouping every portable antenna under one rule.

Application Match

Find your application in the left column, then read across for the fit and the reason. If two rows seem to fit, the orbit and motion rows decide before size does.

Orbit and Tracking

A stationary building does not imply a stationary beam: a directional LEO/MEO terminal must follow the satellite even when its mount never moves geographically. Conversely, a vehicle used only after parking may use a deployable GEO dish rather than a communications-on-the-move system. Dolph’s driveaway product description explicitly distinguishes deployment after transport from operation while driving.

Free-space basic transmission loss between isotropic antennas is Lbf = 20 log₁₀(4πd/λ), with distance d and wavelength λ in the same units. [6] For a calculated 12 GHz comparison, assume a satellite directly overhead: the path is about 35,786 km for GEO and 550 km for a hypothetical LEO satellite at that altitude. Losses are approximately 205.1 and 168.8 dB, a 36.3 dB difference. These are idealized overhead paths, not general slant ranges; lower-elevation paths are longer. Rain, atmosphere, antenna gains, and network performance are excluded.

Band, Size, Gain

Wavelength follows λ = c / f, with c = 299,792,458 m/s. These examples provide inputs to gain and beamwidth calculations; they are not licensed service allocations.

For a circular aperture, the model is G = η(πD/λ)² in linear units, or 10 log₁₀(G) in dBi. NASA’s reflector analysis gives the equivalent relationship G = η × 4πA/λ²; substituting the circular area A = πD²/4 gives this expression. [7] The following calculations assume aperture efficiency η = 0.6 at every listed frequency. They do not include additional downstream feeder, mismatch, radome, or pointing losses. Real efficiency and the measurement reference plane must be established for the selected antenna.

As a sensitivity calculation—not a claimed production range—a 1.2 m dish at 12 GHz gives about 41.0 dBi at η = 0.55 and 42.0 dBi at η = 0.70. Ask which losses a supplier’s efficiency or gain figure already includes so that the link budget does not count them twice.

For calculated gain, request the efficiency assumption. For measured gain, request the test frequency, reference plane, and measurement conditions.

At the same frequency and efficiency, doubling diameter adds approximately 6.0 dB of gain. It also approximately halves beamwidth, so the mount and pointing system must support a narrower beam. Surface accuracy must be assessed against operating wavelength and the allowable efficiency loss, not diameter alone.

For an illustrative dish beamwidth estimate, use 70λ/D degrees, with λ and D in the same units. The coefficient already yields degrees. It gives approximately 1.5° for a 1.2 m dish at 12 GHz, 0.7° for 2.4 m at 12 GHz, and 0.6° for 1.2 m at 30 GHz. Actual half-power beamwidth depends on illumination and antenna design. Estimate site attenuation separately with ITU-R P.618-14; beamwidth is not a rain-margin calculation. [4]

Gain, Noise, Pointing

G/T expresses receive gain relative to system noise temperature, usually in dB/K. EIRP combines transmitter power and antenna gain, with losses referred to a consistent point. At 12 GHz and equal efficiency, a 1.2 m dish needs approximately four times the transmit power of a 2.4 m dish to produce the same EIRP, if all other losses are equal. Moving to the larger dish reverses that trade-off; it does not require four times the power.

For an idealized flat aperture, projected area scales as cos θ away from broadside. The calculated area-only loss −10 log₁₀(cos θ) is about 1.5 dB at 45° and 3.0 dB at 60°. This is a geometric illustration, not a prediction of a particular panel’s scan performance. Element patterns, coupling, mismatch, polarization, and radome effects require actual EIRP and G/T curves across scan.

Beyond raw gain, neighboring satellites impose sidelobe envelopes, and the US earth-station rule cited above gives one enforceable example. [5] ITU-R S.465-6 gives the companion international reference pattern for coordination and interference assessment from 2 to 31 GHz. [8]

Mistakes

• A larger dish can lose its expected advantage if mount deflection or pointing error consumes the extra link margin. Check those errors before reusing the old mount.
• Panel thickness says little; panels of equal size differ in EIRP across scan, handover behavior, modem pairing, and power draw.
• Motorized acquisition is not proof of in-motion stabilization. A driveaway terminal that acquires GEO after parking is not automatically suitable for transmitting while the vehicle moves.
• Tracking can be unnecessary at a stationary GEO site, but remains useful or necessary for directional non-GEO links from the same site.
• Feed or waveguide loss before the receiver can degrade G/T; transmit-path loss reduces radiated power. Establish the RF reference planes before comparing complete terminals.
• An unapproved terminal can fail on frequency use, EIRP density, sidelobe behavior, or certification; the approved list comes before gain comparison. Off-axis EIRP-density envelopes for FSS earth stations in the covered bands are specified in 47 CFR 25.218. [9]

Worked Selection Scenarios

Parked emergency vehicle or broadband on the move?

Consider an emergency team that needs a link only after parking. A driveaway or flyaway GEO dish is a candidate: compare deployment clearance, roof or ground support, power, acquisition, and the approved RF chain. If the requirement changes to broadband while driving, reopen the selection around a motion-rated terminal. The driveaway label and automatic acquisition alone do not satisfy that new requirement. This is a selection scenario, not a reported customer deployment.

Same dish size, different pointing budget

Using the calculated 1.2 m examples above, a 0.3° pointing error is about one-fifth of the estimated 12 GHz beamwidth, but about one-half of the 30 GHz beamwidth. A mount acceptable for the first design therefore cannot be accepted for the second without checking its error budget and the measured antenna pattern. Those fractions compare angle with beamwidth; they are not calculated pointing losses in dB, and the examples are not field-test results.

Specification Checklist

A useful request specifies the satellite service, site location, exact receive and transmit ranges, polarization, data-rate and availability targets, whether operation is parked or in motion, mounting limits, and the required RF chain. A reflector diameter alone cannot define that configuration.

• Which satellite system and orbit is this terminal approved for?
• What are warranted EIRP and G/T, over which band and scan or tracking range?
• How does it acquire and hand over satellites, and how long does traffic pause?
• What are pointing accuracy, stabilization range, power, cooling, weight, and mounting envelope?
• What sidelobe, EIRP-density, and certification limits does it meet?

If the answer is only a broadside gain number or a panel thickness, ask for the sweep data, scan plots, and test conditions.

Choose the simplest operator-supported antenna that meets the link budget over the full operating range. That may be a fixed GEO dish, a parked deployable terminal, a stabilized or tracking broadband terminal, a gateway reflector, or a compact low-rate antenna. Final selection depends on documented performance and service compatibility, not a single gain figure.

References

1. NASA Earthdata, Orbits. https://www.earthdata.nasa.gov/learn/earth-observation-data-basics/orbits
2. European Space Agency, Types of orbits. https://www.esa.int/Enabling_Support/Space_Transportation/Types_of_orbits
3. European Space Agency, Satellite frequency bands. https://www.esa.int/Applications/Connectivity_and_secure_communications/Satellite_frequency_bands
4. Recommendation ITU-R P.618-14 (08/2023), Propagation data and prediction methods required for the design of Earth-space telecommunication systems. https://www.itu.int/dms_pubrec/itu-r/rec/p/R-REC-P.618-14-202308-I!!PDF-E.pdf
5. 47 CFR 25.209, Earth station antenna performance standards, Federal Communications Commission, eCFR. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25/subpart-C/section-25.209
6. Recommendation ITU-R P.525-5 (11/2024), Calculation of free-space attenuation. https://www.itu.int/dms_pubrec/itu-r/rec/p/R-REC-P.525-5-202411-I!!PDF-E.pdf
7. NASA/TM—2011-217110, The Effect of Boundary Support and Reflector Dimensions on Inflatable Parabolic Antenna Performance, Equation (10). https://ntrs.nasa.gov/api/citations/20110023748/downloads/20110023748.pdf
8. Recommendation ITU-R S.465-6 (01/2010), Reference radiation pattern of earth station antennas in the fixed-satellite service for use in coordination and interference assessment in the frequency range from 2 to 31 GHz. https://www.itu.int/rec/R-REC-S.465-6-201001-I/en
9. 47 CFR 25.218, Off-axis EIRP density envelopes for FSS earth stations transmitting in certain frequency bands, Federal Communications Commission, eCFR. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-25/subpart-C/section-25.218

The post Which Satellite Antenna Type Fits Your Application? appeared first on DOLPH MICROWAVE.

A satellite dish focuses radio waves by reflecting them from a parabolic surface toward a feed horn. For waves arriving along the dish’s axis from a distant satellite, the total paths from a common incoming wavefront, via different parts of the reflector, to the focus are equal. The reflected waves therefore arrive in phase and reinforce one another, allowing the feed to collect energy intercepted across the dish’s opening [1] [2].

Why a parabolic reflector brings waves together

A dish is a three-dimensional paraboloid, or an offset section of one. Its conductive surface reflects radio waves, while its curvature determines where they go. A flat metal sheet can reflect a wave, but it does not bring parallel incoming rays to a common focus. A paraboloid does [2].

The geometry works like a flashlight in reverse: a light source at a reflector’s focus produces a directed beam; a receiving dish gathers an incoming beam toward its feed. NASA describes the same parabolic geometry as useful for both capturing and transmitting signals [3].

How equal path lengths keep the waves in phase

Because the satellite is far away compared with the dish’s diameter, its wavefront is approximately flat across the aperture. Imagine two rays leaving that same wavefront: one strikes near the middle of a centered dish, and another strikes near the rim. Their distances before reflection differ, as do their distances after reflection. The parabolic shape makes the two total distances equal [2].

Equal path length means the entire journey from a common incoming wavefront to the focus—not equal distances from every point on the reflector to the feed.

This lets contributions from across the reflector add coherently. The focus is not an infinitely small point: diffraction gives a real antenna a finite focal region and a finite beamwidth. A pointing error reduces the response as the satellite moves away from the antenna’s beam center; it does not make reception disappear at every nonzero angle [2].

What the feed horn and LNB do

The reflector gathers and redirects energy; it does not supply electronic amplification. The feed horn couples the focused field into the receiver. On a typical home satellite-TV installation, the feed is combined with a low-noise block downconverter, or LNB, on the support arm.

1. The reflector concentrates the incoming field near the focus.
2. The feed couples that field into the receiver’s waveguide or probe.
3. The LNB amplifies the received signal and converts it to a lower frequency for the cable.
4. The indoor receiver processes the selected signal.

The correct feed depends on more than the band name. Its radiation pattern must match the reflector geometry. Dolph’s microwave feedhorn range, for example, includes configurations for prime-focus, offset, and Cassegrain systems. Where a separate waveguide interface is needed, a waveguide-to-coaxial adapter provides the transition between those transmission-line types; it is not what focuses the dish.

Feed positioning concerns the horn’s electrical phase center, not simply the visible end of its housing. An NRAO feed-horn study reports a phase center located inside the horn and changing with frequency. That is why sighting along an LNB arm cannot establish the exact focal position [4].

How offset and two-reflector dishes arrange the feed

A centered prime-focus antenna places the feed in front of the main reflector, where the feed and its supports block part of the aperture. An offset reflector uses an off-axis section of a parent paraboloid, allowing the feed to sit clear of the main incoming beam. Two-reflector systems instead relay the field to a secondary focus [2].

Some large antennas use a beam-waveguide arrangement: additional mirrors guide the signal toward equipment below the antenna [3]. These optical paths should not be confused with a feed network, which combines components such as horns, filters, and polarization devices.

How wavelength, diameter, and surface accuracy affect reception

Wavelength sets the scale

The wavelengths below are calculated using λ = c / f, with the exact vacuum light speed c = 299,792,458 m/s. Frequency ranges use NASA’s listed radar-band convention; they are broad labels, not a statement that every frequency in each band is allocated to satellite links [5] [3].

Band boundaries vary by convention: ESA’s satellite-band overview lists Ka as 26–40 GHz. Use the actual operating frequency when selecting hardware or calculating wavelength. ESA also notes the greater rain-fade susceptibility of higher-frequency satellite links [6].

Dish diameter changes collecting area and beamwidth

For a circular projected aperture, geometric area is A = πD² / 4. These calculated examples describe the opening, not the effective receiving area:

Doubling the diameter quadruples geometric area. Effective receiving area is smaller because aperture efficiency accounts for illumination, spillover, blockage, and other antenna losses. At a fixed wavelength and with comparable illumination, a larger aperture also produces a narrower beam, making accurate pointing more important [2].

Surface errors disturb coherent focusing

Dents and warping change the reflected path lengths. The same physical surface error is generally more significant at shorter wavelengths, so a dish that works acceptably at a lower frequency may not meet a higher-frequency requirement. This is a matter of surface accuracy and the affected area, not a universal dent-depth pass/fail rule [1] [2].

Practical checks: what you can establish and what you cannot

Consider an existing offset TV dish with weak reception. Its feed arm and housing show where the feed assembly is mounted, but they do not prove that its electrical phase center is correctly positioned. Start with the specified feed and mounting dimensions for that reflector rather than treating the LNB’s plastic cap as a focal-point marker [4].

A wavelength comparison can help explain a damaged reflector without pretending to test it. For illustration, λ is about 25 mm at 12 GHz and 10 mm at 30 GHz. A hypothetical 5 mm surface displacement is therefore about one-fifth and one-half of those wavelengths, respectively. These are calculated ratios, not measured gain losses. A local displacement is not the same as the dish’s overall RMS surface error, and the ratios alone cannot establish whether either installation passes its requirements [5] [2].

For a mesh reflector, comparing openings with wavelength is only a preliminary check. A ruler measurement does not certify Ku-band performance: the reflector still needs suitable electrical construction and surface accuracy. Check its specified operating band rather than assuming that any mesh with millimeter-sized openings will work.

Separate focusing problems from other faults before replacing a dish. Incorrect pointing, an incompatible feed, or a distorted reflector can reduce antenna response; a blocked sightline or rain fade can weaken the link without moving the geometrical focus. A visual inspection can identify obvious obstructions or damage, but confirming RF performance requires signal measurements.

Does the same dish focus transmitted waves?

Yes. In reverse, a feed at the appropriate focus illuminates the reflector, which forms a directed outgoing beam. The same reciprocity principle connects an antenna’s transmitting and receiving patterns [2]. A feed pattern that is too broad spills energy beyond the reflector; one that is too narrow under-illuminates its outer area.

In a dual-polarized system, an orthomode transducer can separate or combine the orthogonal polarization paths. It manages polarization channels; the reflector remains responsible for focusing. Whether the antenna is a fixed earth station or a portable flyaway terminal, the essential match is between reflector geometry, feed position, feed pattern, and operating frequency.

The post How Does a Satellite Dish Focus Radio Waves? appeared first on DOLPH MICROWAVE.

Yes. Two satellites can transmit on the same frequency at the same time if each receiver can recover its intended signal despite the other transmission. Frequency reuse works through directional antennas, geographic separation, orthogonal polarization, or compatible signal codes. Operators must also meet the applicable coordination and authorization requirements. Using the same frequency does not automatically cause harmful interference, but sharing a frequency band alone does not prove that two links are compatible.

What Does Sharing the Same Frequency Actually Mean?

Two satellites using the same band may occupy different channels and never overlap. True co-frequency reuse means their occupied frequencies overlap. Whether they interfere depends on how much unwanted energy reaches each receiver and how that receiver processes the signals.

Simultaneous reuse and time sharing are different arrangements. Directional antennas, separate coverage areas, polarization, and code separation can support simultaneous use. Scheduling transmissions at different times avoids simultaneous use of the channel.

Which Satellite Links Can Reuse a Frequency?

These are engineering possibilities, not permissions to transmit. A working configuration must protect the affected receivers as well as deliver its own service.

Who Coordinates and Authorizes Frequency Reuse?

The ITU provides the international framework for coordinating satellite spectrum and orbital resources through national administrations. An international filing is not a substitute for the authorizations required by the relevant national regulator. [1]

For example, U.S. rules require space-station and earth-station transmissions to operate under an appropriate FCC authorization. A receive-only user and an earth-station operator transmitting an uplink do not necessarily have the same licensing obligations. Check the requirements for the station and activity involved rather than assuming every receiver needs an individual transmit license. [2]

How Far Apart Must Two Satellites Be?

There is no single minimum separation that guarantees reuse for every link. For geostationary satellites, the relevant geometry includes their apparent angular separation from the earth station. The antenna’s response toward the unwanted satellite, together with the interfering signal level, determines how much isolation that geometry provides.

For comparable antenna designs, a larger reflector at the same frequency generally gives a narrower main beam. At a fixed reflector size, a higher frequency also generally narrows the beam. Neither relationship replaces the actual sidelobe pattern or a pointing check. Orbital separation can help both reception and transmission: the receiving dish rejects off-axis signals, while the transmitting dish limits energy sent toward other satellites.

As one specific U.S. example, 47 CFR 25.209(a)(2) gives a conventional Ku-band co-polar transmit-gain envelope of 29 − 25 log10(θ) dBi for 1.5° ≤ θ ≤ 7° in the plane tangent to the geostationary orbit arc. Here θ is the off-axis angle in degrees. The provision concerns FSS earth stations transmitting to GSO satellites and is subject to the rule’s exceptions and allowances. It is an antenna-performance requirement, not a universal satellite-spacing rule. [3]

Can Opposite Polarizations Separate Two Links?

Yes, orthogonal polarization can provide substantial isolation between co-frequency links. Examples include horizontal and vertical linear polarization, or the two opposite senses of circular polarization. Whether that isolation is sufficient must be established for the complete link, rather than inferred from the polarization labels.

Orthomode transducers separate orthogonal polarization paths in a feed assembly; polarizers support the required polarization conversion. These functions do not make cross-polar leakage disappear. Antenna alignment, feed performance, and propagation conditions all affect the isolation available at the receiver.

Rain-related depolarization can reduce cross-polar discrimination. ITU-R P.618 provides propagation prediction methods for Earth-space system design, including relevant cross-polarization effects. Use the applicable method and site conditions rather than treating a nominal hardware specification as an all-weather guarantee. [4]

How Do Spot Beams Reuse Frequencies?

A multi-beam satellite can reuse frequencies in spatially separated beams. This is reuse within one system, whereas two different satellites may require coordination between separate networks. In either case, the useful question is how much energy from a co-frequency beam reaches an affected receiver.

Beam edges are not hard walls. Signals extend beyond the main coverage area, so non-overlapping coverage outlines alone do not establish compatibility. A frequency-and-polarization reuse pattern assigns resources to beams while accounting for their interference into other beams.

How Can GPS Satellites Use the Same Carrier?

GPS provides a concrete example of co-frequency signals separated by design. Its L1 C/A signals use satellite-specific pseudorandom-noise sequences. A receiver uses the appropriate code to distinguish a wanted satellite’s signal from other signals on the shared carrier. IS-GPS-200N specifies the L1/L2 interfaces and C/A-code assignments. [5]

Code separation is a property of the signal system and receiver. Two unrelated satellite communications links do not become compatible simply because their data streams differ. The GPS example also should not be generalized to every navigation signal or constellation.

Does Sharing a Downlink Also Permit Sharing the Uplink?

No. Uplink and downlink compatibility require separate assessments. On the downlink, a ground receiver may receive unwanted energy from another satellite. On the uplink, a transmission intended for one satellite may also reach another satellite’s receiver. Power, antenna patterns, frequencies, and authorization conditions differ between the paths.

What Do C-Band and Ku-Band Definitions Tell You?

The following are U.S. FCC conventional fixed-satellite band definitions, not a list of frequencies available to every operator or location. They illustrate paired transmission directions, not two satellites reusing one channel. [6]

The derived values are simple edge subtractions: 6,425 − 5,925 = 500 MHz and 5,925 − 4,200 = 1,725 MHz for the C-band example; 14,500 − 14,000 = 500 MHz and 14,000 − 12,200 = 1,800 MHz for Ku-band. The downlink spans are also 500 MHz. None of these figures represents an assigned customer channel or interference-free guard spectrum.

Why Is a Frequency Comparison Not a Reuse Test?

ITU-R P.525 gives the free-space attenuation relationship. At equal distance, comparing rounded frequencies produces 20 log10(6/4) = 3.52 dB and 20 log10(14/12) = 1.34 dB differences in the free-space loss term. These are calculations, not measurements. They exclude antenna gains and other link-budget terms, and they say nothing by themselves about co-channel isolation. [7]

What Would a Practical Shared-Frequency Review Check?

Consider a hypothetical receive-only installation pointed at one geostationary satellite, with a second satellite using an overlapping downlink channel. Before accepting a replacement dish or feed, compare the proposed hardware against the assumptions in the interference assessment.

• Identify the overlap. Record the wanted and unwanted satellites, occupied channels, polarization, and proposed station location. A common band name is not enough.
• Check the unwanted direction. Obtain antenna gain patterns at the operating frequency and the apparent satellite separation. Do not approve a smaller dish solely because its on-axis gain can support the wanted link.
• Check the polarization path. Match feed ports, polarization settings, and specified cross-polar performance to the link plan, including the relevant propagation allowance.
• Assess the receiver. Compare the predicted wanted and aggregate unwanted signals with the receiver’s required performance, including operating and weather conditions.
• Confirm the operating conditions. For a transmitting station, check the permitted satellite, power density, bandwidth, antenna performance, and authorization before transmitting.

If the replacement hardware lacks the off-axis or cross-polar data used in the assessment, compatibility remains unproven. That is a reason to request evidence or recalculate, not proof that the link must fail. This scenario is a review workflow, not a reported customer installation or field test.

Which Ground Components Matter Most?

The antenna and reflector provide directional discrimination. The feedhorn, polarization components, and their alignment affect the complete antenna pattern and polarization performance.

Filters and waveguide diplexers separate frequency paths, such as paired transmit and receive bands. They generally cannot remove another signal occupying the same passband just because it comes from a different satellite. A waveguide run also introduces loss; it is not a substitute for spatial or polarization isolation.

When comparing components from Dolph Microwave, match the operating band, flange interface, power handling, polarization function, and documented performance to the coordinated system design.

So, Can Two Satellites Reuse the Same Frequency?

Yes. The deciding issue is whether the system provides enough isolation or signal separation for each receiver to operate as required. Check both transmission directions, the actual antenna and receiver performance, and the applicable authorizations. Neither a shared band label nor a different polarization label establishes compatibility on its own.

References

1. ITU Radiocommunication Bureau, Space Services. International satellite spectrum and orbital-resource framework. Accessed November 6, 2026.
2. 47 CFR 25.102, Station authorization required. U.S. authorization requirement for space-station and earth-station transmissions. Accessed November 6, 2026.
3. 47 CFR 25.209, Earth station antenna performance standards. Paragraph (a)(2), conventional Ku-band co-polar transmit-gain envelope; apply the full rule and its exceptions. Accessed November 6, 2026.
4. ITU-R P.618-14, Propagation data and prediction methods required for the design of Earth-space telecommunication systems. Propagation and cross-polarization prediction methods. Accessed November 6, 2026.
5. IS-GPS-200N, NAVSTAR GPS Space Segment/Navigation User Segment Interfaces, August 22, 2022. Sections 3.2.1.3 and 3.3.1.1, C/A-code assignments and carrier frequencies. Accessed November 6, 2026.
6. 47 CFR 25.103, Definitions. U.S. conventional C-band and Ku-band definitions; table spans and separations calculated from the defined edges. Accessed November 6, 2026.
7. ITU-R P.525-5, Calculation of free-space attenuation. Equal-distance, rounded-frequency calculation method; not a complete link budget. Accessed November 6, 2026.

The post Can Two Satellites Reuse the Same Frequency? appeared first on DOLPH MICROWAVE.

Satellite transponder bandwidth is the frequency width of a transponder channel, measured in megahertz (MHz). A 36 MHz transponder provides a nominal 36 MHz-wide channel for one carrier or a group of narrower carriers; it does not mean 36 Mbps. The channel width and available power constrain the signals it can carry [1]. Other documented widths include 27, 54 and 72 MHz [2]. In four ITU broadcast examples, the same nominal 36 MHz channel supports useful bit rates from 33.8 to 58.8 Mbps under different modulation and coding conditions—not a universal minimum or maximum [3].

Common transponder bandwidths

Channel width is a property of the satellite and its frequency plan, not a fixed value determined by the band name. Coordination records include 27, 36, 54 and 72 MHz assignments [2]. ITU sharing-study tables also include 120 and 250 MHz examples for 20/30 GHz systems [4].

Nominal width and channel spacing

Nominal transponder bandwidth, carrier occupied bandwidth and channel spacing describe different things. The first describes the channel; the second describes the transmitted signal; the third is the distance between adjacent channel centers. DVB reference scenarios distinguish a 36 MHz transponder from its 40 MHz spacing [5].

As a calculated example, a nominal 36 MHz channel centered at 11,550 MHz has nominal edges at 11,550 ± 18 MHz, or 11,532–11,568 MHz. These are not brick-wall filter boundaries. The channel response and filter roll-off matter when assessing a carrier near those edges; spacing alone does not establish that the carrier will pass without distortion or interference [3] [5].

How MHz relates to Mbps

For ideal raised-cosine shaping, signal bandwidth depends on symbol rate and roll-off. DVB-S2 specifies roll-off factors of 0.35, 0.25 and 0.20; DVB-S2X supports smaller values as well [5] [6].

Ideal shaped-signal bandwidth (MHz) = symbol rate (Mbaud) × (1 + roll-off)

This relation estimates spectrum width, not useful data rate. Modulation, error correction and framing also affect useful Mbps. Table 1 of ITU-R Report BO.2101 (2007) compares these four configurations through a nominal 36 MHz satellite channel that includes an amplifier and output-multiplexer filter [3].

These are published comparison points, not guaranteed customer throughput or a limit on every 36 MHz system. A workable configuration also needs sufficient link margin. ITU-R P.618 provides Earth-space propagation prediction methods, including rain attenuation, for that assessment [3] [7].

Two worked bandwidth checks

For the HDTV contribution example in BO.2101, the reported symbol rate is 27.7456 Mbaud and roll-off is 25%. Recalculating gives 27.7456 × 1.25 = 34.682 MHz, matching the report’s rounded 34.68 MHz inside a 36 MHz allocation. The difference is 1.318 MHz in total; it is not an automatic allowance for another carrier [3].

The QPSK 3/4 table row gives a different result: 30.9 × 1.20 = 37.08 MHz. That exceeds the nominal 36 MHz width. BO.2101 uses symbol rates approximately equal to 1.03 × nominal bandwidth ÷ (1 + roll-off) in this comparison. This is a channel-specific test configuration, not permission to exceed a booked allocation. Even if the shaped signal is narrower than 40 MHz spacing, filter distortion, adjacent-channel interference and the operator’s permitted carrier plan still require evaluation [3] [5].

Bandwidth and power limits

A carrier can satisfy the bandwidth limit and still need a different power setting. Attachment 1 to Annex 1 of ITU-R S.2049 gives estimated high-power-amplifier (HPA) outputs of 221.4 W for a 1.2 m dish and 98.4 W for a 1.8 m dish, for a 36 MHz carrier in the 13–14 GHz FSS uplink band. Its assumptions include a 36 MHz GSO transponder and 3 dB loss from the HPA to the antenna flange [1].

Those figures are guidelines, not equipment-sizing requirements for every link. The recommendation requires a link-budget analysis for every transmission and verification with the satellite access centre. Both assigned bandwidth and power must be respected [1].

Reading a transponder specification

Aggregate bandwidth needs its own definition. In a calculated 500 MHz block example, twelve channels on 40 MHz spacing use a 480 MHz planning allowance per polarization. Dual-polarization reuse allows that frequency plan to be reused on a second polarization. DVB’s reference table lists 24 transponders and 960 MHz aggregate on this spacing-based basis. The sum of their nominal channel widths is instead 24 × 36 = 864 MHz; neither sum means 960 MHz of distinct, contiguous RF spectrum [5].

• Identify the satellite, beam, polarization and uplink or downlink frequency before interpreting the quoted MHz [2].
• Check nominal channel width, center spacing and the allowed carrier plan separately; a bandwidth calculation alone is not an access approval [1] [5].
• Specify symbol rate, roll-off, modulation and coding alongside the requested useful data rate [3].
• Confirm the power allocation and link margin for the target availability, rather than choosing bandwidth from Mbps alone [1] [7].

For the ground feed chain, a microwave feedhorn, orthogonal mode transducer and waveguide diplexer have separate component specifications. Their passbands should not be confused with the satellite’s assigned transponder channel.

The post What Is a Satellite Transponder Bandwidth? appeared first on DOLPH MICROWAVE.

GNSS satellites transmit most navigation signals in L-band, the 1–2 GHz range identified by ESA for satellite navigation [1]. GPS uses L1, L2 and L5; Galileo uses E1, E5 and E6; GLONASS uses channelised G1/G2 and newer CDMA signals; BeiDou uses B1, B2 and B3 signal families. QZSS shares GPS navigation frequencies and also broadcasts L6 augmentation signals. NavIC specifies L1 and L5 signals plus an S-band signal at 2492.028 MHz.

The frequencies below are nominal carrier centres, not antenna passband edges. They describe the principal navigation signals and the QZSS L6 augmentation downlink, not every restricted-service signal or satellite communications link. A constellation’s signal plan does not mean that every satellite transmits every listed signal.

GPS frequency bands

GPS has three navigation carriers: L1 at 1575.42 MHz, L2 at 1227.60 MHz and L5 at 1176.45 MHz. The GPS Standard Positioning Service Performance Standard specifies right-hand circular polarisation (RHCP) for these signals. L1 C/A uses a 1,023-chip code at 1.023 megachips per second (Mcps). The composite L2C sequence has 1,534,500 chips at 1.023 Mcps; its underlying CM and CL codes each run at 0.5115 Mcps. L5 I5 and Q5 each use 10,230-chip primary codes at 10.23 Mcps [2].

L1 C/A and L1C are different signals on the same 1575.42 MHz carrier. GPS.gov describes L1C as designed for interoperability with other navigation systems. It also explains that receiving L1 and L2C together enables ionospheric correction; the benefit comes from measuring two frequencies, not simply tracking more satellites at one frequency [3].

Galileo frequency bands

Galileo uses E1 at 1575.42 MHz, E6 at 1278.75 MHz and the E5 signal group. E5 is centred at 1191.795 MHz; its E5a and E5b components are centred at 1176.45 and 1207.14 MHz. E5a and E5b can be processed independently, so these are not five unrelated bands. The E5a and E5b I/Q ranging codes run at 10.230 Mcps [4].

The Galileo ICD specifies receiver reference bandwidths of 24.552 MHz for E1, 40.920 MHz for E6, 51.150 MHz for the complete E5 signal, and 20.460 MHz each for E5a and E5b. These are reference bandwidths for receiver performance calculations, not interchangeable definitions of occupied spectrum or regulatory allocations [4]. ESA explains that compatible modulation allows GPS and Galileo to share frequencies while avoiding mutual interference. That compatibility does not make a receiver immune to external interference [5].

GLONASS frequency bands

Legacy GLONASS uses frequency-division multiple access (FDMA), with carrier frequency set by channel number k: G1 = 1602.0 + 0.5625k MHz and G2 = 1246.0 + 0.4375k MHz. For the channel interval k = −7 to +6, the carrier centres span 1598.0625–1605.375 MHz for G1 and 1242.9375–1248.625 MHz for G2. These are centre-frequency ranges, not the full widths of the transmitted signals [6].

The newer code-division multiple access (CDMA) signal plan includes L3OC at 1202.025 MHz and, for GLONASS-K2, L1OC at 1600.995 MHz and L2OC at 1248.06 MHz. Availability depends on the satellite and payload generation; these additions do not replace every legacy FDMA signal [7].

BeiDou frequency bands

The principal BeiDou open-service centres are B1I at 1561.098 MHz, B1C at 1575.42 MHz, B2a at 1176.45 MHz, B2b at 1207.14 MHz and B3I at 1268.52 MHz. The Open Service Performance Standard lists bandwidths of 4.092 MHz for B1I, 32.736 MHz for B1C, and 20.46 MHz each for B2a, B2b and B3I [8].

B2a and B2b must not be confused: they are at 1176.45 and 1207.14 MHz respectively. The 1207.14 MHz centre belongs to B2b in this open-service signal list, not to B2a [8].

QZSS and NavIC frequency bands

QZSS navigation signals use L1 at 1575.42 MHz, L2 at 1227.60 MHz and L5 at 1176.45 MHz, as specified in its positioning, navigation and timing interface document [9]. Its L6 augmentation signals use a separate centre at 1278.75 MHz. The L6 specification gives a 42.0 MHz bandwidth for Block II and III; this correction-data downlink should not be confused with the L1/L2/L5 ranging signals [10].

NavIC’s L1 interface document specifies L1 at 1575.42 MHz, L5 at 1176.45 MHz and S-band at 2492.028 MHz. Its frequency-band table gives 1563.42–1587.42 MHz for L1, 1164.45–1188.45 MHz for L5, and 2483.5–2500 MHz for S-band. These correspond to bandwidths of 24, 24 and 16.5 MHz respectively. A receiver intended for NavIC S-band therefore needs coverage outside L-band; support for NavIC L1 or L5 alone does not imply S-band support [11].

Which GNSS signals share the same frequency?

A worked frequency-plan check

Consider a receiver required to track GPS L1/L5 and Galileo E1/E5a. Comparing their ICDs reduces four signal names to two carrier centres: 1575.42 and 1176.45 MHz. This is a useful first check when preparing an antenna specification, but it does not reduce the receiver’s need to process four distinct signals [2][4].

Using Galileo’s receiver reference bandwidths as the design assumption, E1 spans 1575.42 ± 12.276 MHz, or 1563.144–1587.696 MHz. E5a spans 1176.45 ± 10.230 MHz, or 1166.220–1186.680 MHz. These calculated intervals are a reference-bandwidth check, not a complete antenna acceptance specification: they do not establish gain, matching, axial ratio or performance at the band edges [4].

Now add legacy GLONASS G1. At k = −7, the centre is 1602.0 − 7 × 0.5625 = 1598.0625 MHz, already above the E1 reference interval. Thus, coverage specified only for that E1 interval would not cover even the lowest G1 carrier in the selected channel range. At k = +6, G1 reaches 1605.375 MHz; the signal bandwidth must be allowed for beyond the carrier centres [6].

What multiple frequencies can and cannot improve

Dual-frequency measurements enable ionospheric correction. GPS.gov also describes the wider L5 signal design as improving jam resistance and providing redundancy when combined with L1. These are design benefits, not a guarantee that a three-band receiver keeps working through any interference or achieves a particular accuracy. The source describes sub-metre performance through three-frequency techniques as a possibility, not an automatic result [3].

For equipment selection, distinguish multi-constellation from multi-frequency. GPS L1 and Galileo E1 give access to two constellations at one nominal centre. GPS L1 and L5 provide two frequencies within one constellation. A receiver’s specification must identify both the systems and the signals it can actually track [3][4].

Which bands must the antenna and RF chain cover?

Start with the required signals, then specify bandwidth around each centre. Do not assume that every installation needs every GNSS band or one continuous passband from L5 to G1. Adding GPS L2, BeiDou B1I/B3I, Galileo E6, QZSS L6 or NavIC S-band changes the frequency plan. Matching a carrier list is only the first step; antenna polarisation and the receiver’s signal support must also match.

For GPS’s RHCP signals, an ideal linearly polarised antenna has a polarisation mismatch loss of approximately 3 dB, equivalent to receiving half the power available with a matched circular polarisation. This is the ideal polarisation loss, not the total loss of an installed antenna and cable system [12].

For a specialised ground-station feed, review antenna feeder networks and tracking antenna platforms against the actual frequency plan rather than assuming that a product-family label establishes GNSS compatibility. Where the design uses waveguide hardware, check the operating range and interfaces of waveguide-to-coaxial adapters and orthomode transducers separately. Their presence in a catalogue is not evidence that a particular assembly supports the required GNSS bands.

Sources

1. ESA: Satellite frequency bands.
2. GPS Standard Positioning Service Performance Standard, fifth edition, April 2020, sections 2.2.1.1–2.2.1.3.
3. GPS.gov: New Civil Signals.
4. Galileo Open Service Signal-in-Space Interface Control Document, issue 2.2, November 2025, frequency plan, receiver reference bandwidths and E5 chip rates.
5. ESA: Galileo navigation signals and frequencies.
6. GLONASS Interface Control Document, version 5.0, 2002, legacy FDMA signal definitions.
7. eoPortal: GLONASS mission and signal evolution.
8. BeiDou Navigation Satellite System Open Service Performance Standard, version 3.0, May 2021, signal-in-space RF characteristics.
9. QZSS positioning, navigation and timing interface specification, IS-QZSS-PNT-006.
10. QZSS L6 interface specification, IS-QZSS-L6-007, section 3.1.2, frequency and bandwidth.
11. ISRO: NavIC Signal-in-Space ICD for SPS in L1 Frequency, version 1.0, August 2023, sections 3.1–3.3.
12. ITU-R Recommendation F.1245-3, polarisation considerations.

The post Which Frequency Bands Do GNSS Satellites Use? appeared first on DOLPH MICROWAVE.

Satellite frequency allocations vary by ITU Region in the frequency ranges allocated to a service, its primary or secondary status, and country-specific footnotes. National rules then determine how those allocations apply at a particular site [1]. For example, the planned broadcasting-satellite service (BSS) downlink bands are 11.7–12.5 GHz in Region 1, 12.2–12.7 GHz in Region 2, and 11.7–12.2 GHz in Region 3 [2]. These are service-specific plan bands, not the complete satellite spectrum available in each Region.

Which Region Is Your Country In

Region 1 broadly covers Europe, Africa, much of the Middle East, and the whole territories of Russia, Turkey, Mongolia, and the Central Asian states named in the regional definition. Region 2 broadly covers the Americas. Region 3 covers much of Asia and the Pacific, including Iran. Iran is entirely in Region 3, not split between Regions 1 and 3. The formal boundaries follow Lines A, B, and C with named territorial exceptions, so continent labels alone are not enough [1].

The Same Service on Different Frequencies

The BSS comparison above shows both a change in band edges and a change in total span. Subtracting the edges gives 800 MHz for Region 1 and 500 MHz each for Regions 2 and 3. A plan’s total span is not bandwidth available to one customer: the plans reserve resources for countries, and not every planned resource is in operation [2].

Feeder links use separate bands from the consumer downlink. ITU’s 2024 overview lists 17.3–18.1 GHz feeder-link plans for Regions 1 and 3 and 14.5–14.8 GHz for those Regions except Europe [2]. A downlink frequency therefore does not identify the matching uplink.

Letter-band names are broader than these service bands. ESA’s general guide calls Ku 12–18 GHz and Ka 26–40 GHz [3]. Yet the FCC’s conventional Ku definition includes an 11.7–12.2 GHz downlink, and its conventional Ka definition includes downlinks below 26 GHz. Use the stated frequencies and service definition, not the letter alone [4].

US Band Definitions Within Region 2

The FCC definitions below show how one country’s satellite terminology divides Ku and Ka. They describe service bands; they are not a complete national allocation table or permission to operate [4].

Conventional Ku fixed-satellite service and DBS are different service categories, even though both use frequencies commonly described as Ku-band. In the United States, transmitting space or earth stations must operate under an appropriate FCC authorization. A frequency appearing in a definition does not grant that authorization [5].

When Satellite Frequencies Stay the Same Across Regions

Not every satellite signal changes frequency at an ITU boundary. GPS L1C uses the same L1 frequency as the legacy L1 C/A signal, described by GPS.gov as approximately 1575 MHz. Its design supports interoperability with other navigation systems, including Galileo [6]. GPS illustrates a shared signal frequency across Regions, not a rule that all satellite navigation systems use identical signals.

Why C-Band Needs a Country-Level Check

The FCC defines conventional C-band fixed-satellite service as 3700–4200 MHz down and 5925–6425 MHz up [4]. But the full defined range is not a reliable guide to present-day availability at a particular US site.

The FCC’s July 2026 C-band order records that the earlier lower-band transition moved satellite operations into 4.0–4.2 GHz in the contiguous United States. It also establishes a further Upper C-band reconfiguration and transition framework. The order distinguishes the contiguous United States from areas outside it [7]. Do not assume the new transition is already complete, or apply the contiguous-US outcome to every Region 2 location.

Why Regions Get Different Allocations

The allocation framework allows differences at several levels.

• Regional columns. A service may appear in one Region’s column but not another’s. Primary services appear in capitals; secondary services must not cause harmful interference to primary services and cannot claim protection from them [1].
• Footnotes. A footnote can add a service in one country or replace the entry for that country [1].
• Planned resources. BSS and feeder-link plans reserve resources for ITU Member States to support equitable access, including future use. A planned resource is not necessarily an operating network [2].

What Regional Gaps Mean for Antennas

For a worked comparison, assume a receive chain is specified only for 11.7–12.5 GHz and a target DBS service requires 12.2–12.7 GHz. These ranges share 12.2–12.5 GHz, a span of 300 MHz. The target’s remaining 12.5–12.7 GHz, or 200 MHz, lies outside the assumed equipment specification. The band edges come from the regional BSS plans; the equipment specification is an illustrative assumption, not a measured product result [2].

In that scenario, a shared Ku-band label is not enough to approve reuse. Check the specified operating range of each feedhorn, OMT, diplexer, and LNB in the receive path. Compare the waveguide size and interfaces as well. Published options in Dolph Microwave’s SATCOM antenna range provide a starting point for a specification check, not proof that a particular configuration is suitable or authorized.

Buying Checklist

• Ask the operator for the actual receive and transmit ranges and polarization, not just a band name.
• Check the LNB local oscillator and receiver IF range against the required downlink frequencies. RF coverage alone does not establish receiver compatibility.
• For a reused terminal, record which components cover the new service and which need replacement. Check transmit-path specifications separately from receive-path specifications.

How to Check Your Region’s Allocation

Start with the site’s country and its ITU Region. In the international table, compare the relevant frequency row across the three regional columns, then read its service status and footnotes. An entry spanning all three columns indicates a worldwide allocation; one confined to particular columns indicates a regional allocation [1].

Next, check the national regulator’s table and applicable authorization requirements. Compare those conditions with the operator’s frequency plan and the equipment specifications. In the United States, the requirement for an appropriate transmitting-station authorization is separate from the band definitions [5]. If the documents conflict, resolve the discrepancy with the regulator and operator before transmitting. An operator plan is not regulatory clearance.

References

1. International Table of Frequency Allocations and ITU Region definitions, 47 CFR § 2.104 — https://www.law.cornell.edu/cfr/text/47/2.104
2. ITU, Introduction to BSS & FSS Plans, World Radiocommunication Seminar 2024 — Regional BSS and feeder-link plan bands and planned resources
3. ESA, Satellite frequency bands — General letter-band ranges
4. FCC satellite band definitions: conventional and extended C/Ku/Ka-band and 12.2–12.7 GHz DBS, 47 CFR § 25.103 — https://www.law.cornell.edu/cfr/text/47/25.103
5. FCC, 47 CFR § 25.102, via Cornell Legal Information Institute — Station authorization required
6. GPS.gov, New Civil Signals — L1C frequency and interoperability
7. FCC, Upper C-Band order, published July 31, 2026, 91 FR 48700 — Earlier lower-band transition and further Upper C-band framework

The post How Do Satellite Frequency Allocations Vary by Region? appeared first on DOLPH MICROWAVE.

Extended C-band and extended Ku-band are additional satellite frequency ranges alongside the conventional C-band and Ku-band ranges. Under the U.S. FCC definitions, extended C-band uses 3600–3700 MHz for downlink and 5850–5925 MHz plus 6425–6725 MHz for uplink. Extended Ku-band uses 10.95–11.2 GHz plus 11.45–11.7 GHz for downlink and 13.75–14.0 GHz for uplink [1].

The important distinction is the actual frequency range, not simply the word “extended.” These FCC definitions provide the reference for the comparison below; they are not a worldwide operating authorization. For equipment selection, confirm the satellite operator’s frequency plan and the authorization applicable to the earth station.

Extended and Conventional Frequency Ranges

Downlink means space to Earth; uplink means Earth to space. The FCC defines the conventional and extended ranges separately, so a component described only as “C-band” or “Ku-band” does not establish which of these ranges it covers [1].

Calculated as upper frequency minus lower frequency, extended C-band adds 100 MHz of downlink spectrum and 375 MHz of uplink spectrum, split into 75 MHz and 300 MHz sections. Extended Ku-band adds two 250 MHz downlink sections, totaling 500 MHz, and a 250 MHz uplink section. These are frequency-width calculations from the table, not guaranteed channel capacity or throughput [1].

What Changes in Extended C-Band

The FCC extended C-band downlink sits immediately below the conventional 3700–4200 MHz downlink. A receive-chain specification that starts at 3700 MHz therefore leaves performance across 3600–3700 MHz unverified. That does not prove the hardware stops working at the boundary; it means the stated specification does not cover the required range.

On the transmit side, the lower extension is below the conventional uplink and the upper extension is above it. Together, all three listed uplink sections span 5850–6725 MHz, an arithmetic width of 875 MHz. This combined span is not a claim that one terminal can transmit across it or that the whole range is authorized for a particular station [1].

Why Extended Ku-Band Is Not Continuous

The FCC extended Ku-band downlink comprises two separate sections. The 11.2–11.45 GHz interval between them is outside that specific definition. It should not be silently included by shortening the description to “10.95–11.7 GHz” [1].

This is a distinction between a regulatory label and hardware coverage. A broadband receiver may cover the intervening interval as well as both extended sections. That extra coverage is not itself a reason to reject the receiver, nor does receiver coverage establish permission to use a frequency.

The extended Ku uplink at 13.75–14.0 GHz adjoins the conventional 14.0–14.5 GHz uplink. Their combined arithmetic span is 750 MHz, but usable coverage still depends on the equipment specification and station authorization [1].

Why Band Names Vary

Broad engineering labels and satellite-service definitions serve different purposes. ESA lists C-band as 4–8 GHz and Ku-band as 12–18 GHz, while the FCC satellite definitions above include downlinks below those broad lower limits. Use the numerical frequency pair when comparing a regulation, an operator plan, and a datasheet rather than assuming the letter-band name resolves the difference [2].

There are also different satellite planning arrangements. ITU Appendix 30B workshop material identifies a 6/4 GHz FSS plan using 4500–4800 MHz for downlink and 6725–7025 MHz for uplink. Those frequencies are distinct from the FCC extended C-band definition used here [3].

Wavelength and Practical Trade-Offs

For an illustrative free-space calculation, wavelength equals c divided by frequency, with c exactly 299,792,458 m/s. NIST gives that constant, and the BIPM metre definition fixes its numerical value [4] [5].

These conversions are not dish-diameter recommendations. ESA describes C-band as valued for low rain fade and wide coverage, and Ku-band as supporting services with smaller antennas, including direct-to-home television and mobility applications. It also notes that higher-frequency bands are generally more susceptible to rain fade. Selecting a SATCOM antenna still requires the link’s performance and availability requirements, not wavelength alone [2].

Checking Hardware Compatibility

Start with separate receive and transmit requirements. For a feedhorn, orthomode transducer, or antenna feed network, ask for documented performance across the intended frequencies. A product-family name is not a substitute for the specification of the selected model.

• List each required downlink and uplink interval, including whether operation is receive-only or transmit/receive.
• Check the frequency range of each component in the signal path, including filters and frequency converters, rather than checking only the antenna.
• Request relevant specifications such as insertion loss, return loss or VSWR, polarization isolation, and transmit power handling under the intended operating conditions.
• Confirm the interfaces between components, including the chosen waveguide and flanges, before approving an assembly.

Standards must also be checked against their stated scope. CEPT’s EN 301 428 entry describes transmit-only, transmit/receive, and receive-only earth stations in the 11/12/14 GHz bands, with listed VSAT ranges of 10.7–11.7, 12.5–12.75, and 14.0–14.5 GHz. Those listed ranges do not include the 13.75–14.0 GHz extended Ku uplink. The entry alone therefore does not establish compliance or applicability for an entire extended-band terminal; confirm the relevant standard version and requirements for the installation [6].

A Worked Equipment-Screening Example

Consider a hypothetical receive-only requirement covering both FCC extended Ku downlink sections: 10.95–11.2 GHz and 11.45–11.7 GHz. This is a calculation-based specification check, not a report of a tested installation. Each section is 0.25 GHz wide, so the two sections total 500 MHz; the intervening 250 MHz is outside the extended Ku definition [1].

Suppose candidate A’s datasheet lists only 11.7–12.2 GHz. Its documented range does not establish coverage of either required extended section. Hold it for clarification or a revised specification rather than assuming it is suitable—or asserting that it physically cannot receive below 11.7 GHz.

Suppose candidate B’s datasheet lists 10.7–12.75 GHz. Both required sections fall inside that stated range. It passes the frequency-range screen, and coverage of 11.2–11.45 GHz is not a disqualifier. It has not yet passed a complete equipment review: the rest of the receive chain and the required performance limits still need confirmation.

The useful output of this check is a requirements sheet identifying the two receive intervals, polarization, interfaces, and acceptance limits to be confirmed. Send that sheet when discussing components with Dolph Microwave or another supplier. It makes an unanswered specification visible without pretending that a paper comparison is a laboratory test.

Common Questions

Can One Front End Cover Conventional and Extended Bands

Yes, if its documented operating range and performance meet all the required sections. A conventional-only specification is insufficient evidence of extended-band coverage, but the band labels do not make shared hardware impossible. Check the full signal path and distinguish receive coverage from transmit capability.

Does Extended Band Mean Faster Service

Not by itself. “Extended” identifies frequency ranges; it is not a throughput rating. Adding the widths of separate uplink and downlink sections does not produce a single usable channel. Ask the operator which frequencies and channel bandwidths are actually available for the intended service.

Does an FCC Definition Permit Operation Everywhere

No. The frequency table is a reference to U.S. FCC terminology, not a global permission to operate. Before transmitting, confirm the applicable national requirements, operator frequency plan, and earth-station authorization.

References

1. FCC, 47 CFR 25.103 — Definitions. Conventional and extended C-band and Ku-band frequency ranges.
2. ESA — Satellite frequency bands. Broad band labels, applications, and general propagation trade-offs.
3. ITU — BSS and FSS Plans workshop material. Appendix 30B planning frequencies.
4. NIST — Speed of light in vacuum. Exact constant used in the wavelength calculations.
5. BIPM — The metre. SI definition fixing the numerical value of the speed of light.
6. CEPT ECO — EN 301 428 entry. Earth-station description and listed VSAT frequency ranges.

The post What Are Extended C-Band and Extended Ku-Band? appeared first on DOLPH MICROWAVE.

X-band and Ka-band carry high-volume Earth observation imagery and science data. L-band carries weather broadcasts and rebroadcasts, while VHF near 137 MHz has been used for lower-rate weather pictures. S-band commonly handles tracking, telemetry and command, although its role depends on the mission. NASA lists Earth-exploration downlinks at 8025–8400 MHz and near-Earth Ka-band downlinks at 25.5–27 GHz. ESA’s published Sentinel-2 configuration illustrates the split: X-band for imagery, S-band for spacecraft control and health information. [1][2]

These are communication bands, not the bands used to observe Earth. Sentinel-1, for example, senses with C-band radar at 5.405 GHz but returns payload data through X-band and an optical relay link. An instrument’s sensing frequency does not identify the receiver needed to download its images. [3]

Earth Observation Downlink Bands at a Glance

The examples above describe different systems, not interchangeable channels. Service status matters as much as frequency: NOAA’s POES constellation was decommissioned, and its status page is preserved as an archive of operations ending on August 19, 2025. [7]

X-Band for Bulk Imagery

X-band is a common direct-to-Earth choice for large imagery files. NASA’s Near Space Network table lists 8025–8400 MHz for Earth-exploration downlinks and, separately, 8450–8500 MHz for space-research downlinks. The first range spans 375 MHz, calculated by subtracting its endpoints. That is the width of the listed range, not bandwidth available to every satellite or permission to transmit anywhere within it. [1]

Mission documentation must take precedence over a letter-band label. WMO lists Metop-B’s global data service at 7800 MHz and 70 Mbit/s, below the nominal 8 GHz lower edge of X-band in NASA’s general band table. A receiver specified only for 8025–8400 MHz would therefore miss that carrier. [4][1]

For a moving low-orbit satellite, the receive antenna must maintain the required pointing through the pass. With LEO/MEO tracking antennas, the usable frequency range must extend through the complete receive chain, including the antenna feed network, filters and receiver. A suitable reflector alone does not establish compatibility.

Ka-Band for High-Volume Links

Ka-band provides another route for high-volume science data; it is not merely a backup used after an X-band link fills up. NASA lists 25.5–27 GHz for near-Earth direct downlinks and gives a 3.5 Gbit/s NISAR example in its network capability table. That example is mission-specific, not a rate guaranteed by the band. [1]

The relay architecture is different. ESA describes Sentinel spacecraft sending data optically to EDRS, which then relays it to Earth over Ka-band. A Ka-band ground receiver in that arrangement receives the relay satellite, not the Sentinel’s optical transmission. The frequencies for a direct link and a relay link must be checked separately. [2]

NASA’s general table labels Ka as 27–40 GHz, while its service table calls the 25.5–27 GHz near-Earth downlink Ka-band. This difference in naming is another reason to specify numerical coverage rather than buying equipment by band name alone. [1]

S-Band for Control and Telemetry

In the Sentinel examples, S-band carries tracking, telemetry and command rather than the main imagery stream. S-band is not restricted to this role: NASA’s network documentation also includes S-band data-return services. The payload-versus-control split must be established from the mission specification. [2][3][1]

Direction also matters. WMO lists Metop-B telecommand and ranging at 2053.4583 MHz Earth-to-space, with telemetry at 2230 MHz space-to-Earth. These are different links, not two alternative receive channels. A shared reflector can use multiband microwave feedhorns, but each frequency, polarization and transmit/receive interface still needs a matching specification. [4]

L-Band and VHF for Weather Data

GOES Rebroadcast and Sensor Relays

GOES Rebroadcast (GRB) distributes weather products at 1686.6 MHz in L-band. NOAA specifies two 15.5 Mbit/s streams, totaling 31 Mbit/s, using dual polarization and 9.8 or 10.9 MHz per polarization. A dual-polarized feed uses polarization-separation components such as an orthomode transducer; the complete feed must support the required polarization arrangement, not just the center frequency. [5]

GOES also relays measurements from surface platforms through its Data Collection System (DCS). This is a separate service from GRB imagery. NOAA documents the GOES-R-era DCS downlink change from 1696 to 1679 MHz and platform data rates of 300 and 1200 bit/s. A receiver configured for GRB is not automatically a DCS receiver. [5]

Polar Direct Broadcast and Legacy VHF

WMO lists Metop-B AHRPT at 1701.3 MHz, 3.5 Mbit/s and right-hand circular polarization, with a backup carrier at 1707 MHz. Its data-access description identifies AHRPT as a direct-broadcast service. The same page tabulates a 137.1 MHz, 72 kbit/s LRPT design entry but explicitly says LRPT is not available. A frequency table alone is therefore not evidence that a service is transmitting. [4]

NOAA’s older POES documentation describes VHF APT and L-band HRPT, including HRPT at 1698 or 1707 MHz and 665.4 kbit/s. These remain useful examples of weather-link design, but the constellation’s retirement means they should not be presented as currently available NOAA reception services. [6][7]

Where Ku-Band Fits

Ku-band also appears in NASA’s space-relay forward and return services. It is relevant when the selected mission uses that relay architecture, but it is not the direct imagery downlink in the Sentinel examples above. Identify the endpoints of the particular link before assigning it a band. [1][2]

A Worked Reception-Planning Example

Suppose a receive system is being sized for the published Sentinel-2 X-band rate of 560 Mbit/s. For an assumed uninterrupted 10-minute transfer at that rate, the arithmetic is 560 million bit/s × 600 s ÷ 8 = 42 GB, using decimal gigabytes. At the published 2 Mbit/s S-band rate, the same interval represents only 0.15 GB, a 280:1 rate ratio. This is a rate-times-duration illustration, not a measured pass, a prediction of usable image volume or a claim that imagery is available over the S-band link. Acquisition time, interruptions, framing and processing can change the usable result. [2]

Two documented operational details help turn that calculation into a sensible equipment check. First, ESA describes Sentinel-2 as capable of operating on stored commands for 15 days in a nominal scenario. A receiving station does not need to establish its own S-band command uplink before every imagery pass. Second, the Metop-B LRPT entry shows why service availability must be checked before hardware is bought: a receiver can match a published frequency perfectly yet receive nothing from an unavailable service. [2][4]

• Define the station’s role: receive imagery, receive a weather broadcast, or provide authorized spacecraft control. Do not add a transmitter merely because the mission also has an uplink.
• Confirm the actual service: satellite, carrier, current availability, polarization, modulation and coding. Record spacecraft-to-ground and ground-to-space directions separately.
• Check the entire data path: feed and receiver coverage, tracking requirements, decoding support, storage and onward network capacity.
• Check authorization and access: a listed frequency range is not a transmission license, and a technically receivable signal does not by itself establish access rights. NASA treats frequency licensing as a separate ground-system design requirement. [1]

Bottom Line

For bulk Earth observation imagery, start with X-band and Ka-band. For weather distribution, examine L-band and the mission’s direct-broadcast or rebroadcast service; treat older VHF examples as historical unless a live service is confirmed. S-band commonly supports spacecraft control, while Ku-band can serve relay links. The final receiver specification must name the satellite and service, not just the letter band.

References

1. NASA: Ground Data Systems and Mission Operations. General band definitions, Near Space Network frequency and capability tables, link design and licensing.
2. ESA: Sentinel-2 operations. Archived mission configuration, communication rates, EDRS link architecture and autonomous operation.
3. Copernicus SentiWiki: Sentinel-1 Mission. Radar sensing frequency and payload/control communication paths.
4. WMO OSCAR: Metop-B. Telecommand, telemetry, global data and direct-broadcast frequencies; LRPT availability restriction.
5. NOAA NESDIS: GOES-R Data Access and Unique Payload Services. GRB frequencies, rates and polarization bandwidths; DCS service changes.
6. NOAA: Polar-orbiting Operational Environmental Satellites booklet. Historical APT and HRPT service descriptions.
7. NOAA OSPO: POES Instrument and Subsystem Performance Status. Archival notice and constellation decommissioning status.

The post Which Bands Carry Earth Observation Data? appeared first on DOLPH MICROWAVE.

L-band is used for mobile satellite links because it combines low rain attenuation with antenna designs that can cover a wide angle without precise mechanical pointing. That combination suits moving terminals carrying voice, position reports, and other modest-data-rate traffic. The benefit is practical reliability rather than maximum throughput: ESA identifies the 1–2 GHz band with mobile satellite services and weather-resistant, low-data-rate communications [1].

It is not a guarantee of reception. The terminal still needs satellite visibility, adequate link margin, compatible polarization, and access to an authorized service. Understanding the tradeoff means separating three questions: how much antenna pointing is needed, how much propagation loss occurs, and how much data the service can actually deliver.

Which L-Band Frequencies Are Used for Mobile Satellite Links?

L-band is a broad frequency label, not a single satellite network or worldwide operating permission. One important pairing is the U.S. regulatory definition of the 1.5/1.6 GHz mobile-satellite service bands: 1525–1559 MHz space-to-Earth and 1626.5–1660.5 MHz Earth-to-space. These ranges do not describe every L-band mobile satellite system, and the definition itself does not authorize a terminal to transmit [2].

NTIA documents the same downlink/uplink pairing. Each range spans 34 MHz, calculated by subtracting its band edges. That is the width of the defined range, not 34 MHz of exclusive capacity for a customer, carrier, or operator [3].

There is also documented safety-service use. NTIA’s May 2015 compendium describes Coast Guard and FAA mobile terminals for emergency communications, and NOAA SARSAT ground stations receiving distress-relay signals at 1544–1545 MHz. This is a dated example of how the spectrum was used, not confirmation of a current operating configuration or approval for a particular terminal [4].

Why Does L-Band Reduce Antenna Pointing Demands?

A moving platform benefits from an antenna pattern wide enough to accommodate changes in orientation. For comparable aperture designs, lowering frequency makes the beam wider at the same physical diameter, but also reduces gain. Conversely, higher frequencies provide more gain from a given aperture and generally require more accurate pointing. NASA discusses the corresponding trades among antenna gain, aperture, data rate, and power [5].

For a numerical comparison, assume a circular aperture 0.5 m in diameter with 60% aperture efficiency at both frequencies. Using G = efficiency × (pi × diameter / wavelength)², then converting to dBi, gives approximately 16.2 dBi at 1.6 GHz and 35.1 dBi at 14 GHz. These are idealized aperture-model estimates, not measurements of a handheld antenna or a product. Actual gain and beam shape depend on the antenna design and installation.

The tradeoff is essential: a broad beam eases pointing, but it spreads energy over a wider angle. A low-gain terminal can work only if the satellite system and the rest of the link budget support it. L-band does not make a small antenna simultaneously broad-beam and high-gain.

How Much Less Rain Attenuation Does L-Band Have?

ITU-R P.838-3 models specific rain attenuation as gamma = k × R^alpha, where gamma is in dB/km and R is rainfall rate in mm/h. Its coefficients depend on frequency and polarization. The following calculations use the horizontal-polarization coefficients in Table 5, with R = 25 mm/h; they are a coefficient comparison, not a complete slant-path availability prediction [6].

Under these assumptions, the 12 GHz value is about 910 times the 1.5 GHz value. That explains why rain absorption is usually a much smaller budget item at L-band. The comparison does not mean that a real L-band link is 910 times more reliable: total attenuation depends on rain-path geometry, polarization, and rainfall conditions, while availability also depends on the remaining link margin [6].

Low rain attenuation should not be confused with immunity to blockage. A roof, terrain, or foliage can obstruct the satellite direction. For installation planning, evaluate the antenna’s view of the satellite instead of assuming that a weather-resistant band will work through an obstruction.

Does Lower Free-Space Loss Mean Less Transmit Power?

Only when the comparison holds the relevant antenna gains and other link conditions constant. ITU-R P.525-5 gives free-space attenuation as 20 log10(4 pi × distance / wavelength). At the same distance, the difference between 14 GHz and 1.6 GHz is 20 log10(14 / 1.6), or about 18.84 dB [7].

On an illustrative 1,000 km free-space path, the losses are 156.53 dB at 1.6 GHz and 175.37 dB at 14 GHz. With equal antenna gains at both ends and all other terms unchanged, compensating for the difference with transmit power alone would require about 76.6 times the power at 14 GHz. This calculation excludes atmospheric, feeder, polarization, pointing, and obstruction losses; it is not a terminal power specification [7].

Do not combine that equal-gain result with a same-size-antenna comparison as though they were independent benefits. In the aperture example above, the same 0.5 m aperture has approximately 18.84 dB more gain at 14 GHz. At one end of the link, that idealized gain increase cancels the frequency-related free-space penalty. Real terminal comparisons therefore need actual antenna patterns, transmit power, receiver performance, bandwidth, and losses—not frequency alone [5].

How Does Motion Affect L-Band Doppler Shift?

For the same relative radial velocity, Doppler shift in hertz is proportional to carrier frequency. Using the first-order relationship shift = radial velocity × frequency / c, an illustrative 250 m/s closing speed produces approximately 1,334 Hz at 1.6 GHz and 11,675 Hz at 14 GHz. The L-band offset is about one-ninth as large.

These are calculated examples, not measured receiver results. Radial velocity means motion along the line of sight between transmitter and receiver; it is not necessarily the vehicle’s ground speed. Satellite motion also contributes. A smaller absolute frequency shift does not establish that a particular receiver can acquire or track the signal: waveform bandwidth and tracking-loop design still matter.

What Are the Bandwidth and Capacity Tradeoffs?

L-band is often a useful match for voice, messaging, tracking, and telemetry, but the frequency label does not impose one universal data-rate ceiling. ESA contrasts L-band’s low-data-rate mobile uses with the larger bandwidths available at higher satellite bands [1].

For the 1.5/1.6 GHz pairing discussed here, the 34 MHz span in each direction is a spectrum boundary, not an individual user’s channel width. Actual throughput depends on channel assignment, modulation, coding, terminal capability, network loading, and the subscribed service. Higher-throughput requirements should be compared against real service specifications rather than a blanket rule that L-band cannot carry video or that every megabit-class link must use Ku/Ka.

There is a hardware cost to lower frequency as well. At equal aperture efficiency and gain, diameter scales inversely with frequency. An idealized 1.6 GHz aperture would need 8.75 times the diameter of a 14 GHz aperture for equal gain. This scaling illustrates why high-gain L-band antennas can become physically large; it does not describe a particular spacecraft or terminal.

A Worked Check for a Moving-Terminal Installation

Consider a vehicle sending position reports and short voice calls over an authorized satellite service. This is a planning scenario, not a field trial. Start with the actual service coverage and antenna pattern, then check the proposed roof location against the satellite direction over the intended route.

• Check visibility and orientation. Identify roof equipment, nearby structures, and route obstructions that could block the satellite. Confirm the antenna’s permitted mounting orientation and polarization with the terminal documentation.
• Keep the budget assumptions consistent. The 1,000 km example above yields an 18.84 dB frequency-only difference at equal gains. If you substitute a same-size higher-frequency aperture, recalculate its gain instead of retaining the equal-gain assumption.
• Check the service requirement. Compare message size, required voice capability, latency, and minimum throughput with the service specification. A short-message application and a continuous video stream need different capacity assessments.
• Account for installation losses. Use the specified cable, connector, and RF-path losses and the required receiver threshold before deciding whether sufficient margin remains.

The reproducible calculations in this article show the scale of the frequency tradeoffs; they do not establish route coverage or a guaranteed connection. That requires the selected terminal’s specifications and an installation assessment. NASA’s link-budget discussion likewise evaluates antenna size, RF power, data rate, attenuation, modulation, and coding together [5].

For a reflector-based RF assembly, a feed horn, an orthogonal mode transducer, and a waveguide diplexer address different feed, polarization, and frequency-separation functions. They are not a universal parts list for an L-band mobile terminal. When reviewing a SATCOM antenna or feed assembly, obtain model-specific frequency coverage, insertion loss, isolation, power limits, and interfaces; a category name alone does not establish compatibility with the 1.5/1.6 GHz pair.

Bottom Line

L-band is attractive for mobile satellite links because low rain attenuation and manageable antenna pointing can support communication from moving terminals. Those benefits come with antenna-gain, spectrum, and service-capacity tradeoffs. Choose it when the actual network and terminal meet the application’s coverage and data needs, and verify the complete link budget rather than treating the band itself as a promise of connectivity.

References

1. ESA — Satellite frequency bands. Band definitions and typical satellite applications.
2. 47 CFR 25.103 via Cornell LII. Definition of the 1.5/1.6 GHz mobile-satellite service bands.
3. NTIA — 1525–1535 MHz Spectrum Compendium, May 2015. MSS band pairing and spectrum use.
4. NTIA — 1535–1559 MHz Spectrum Compendium, May 2015. Historical emergency-communications and SARSAT use.
5. NASA — State-of-the-Art Small Spacecraft Technology, Communications. Antenna, power, data-rate, and link-budget trades.
6. ITU-R P.838-3 — Specific attenuation model for rain for use in prediction methods. Equation 1 and Table 5 coefficients.
7. ITU-R P.525-5 — Calculation of free-space attenuation. Free-space propagation model.

The post Why Is L-Band Used for Mobile Satellite Links? appeared first on DOLPH MICROWAVE.