Designing a ground station for a low Earth orbit constellation is nothing like the old-school approach of pointing a big dish at a single geostationary bird. With LEO, you’re dealing with a swarm of satellites that scream across the sky in minutes, and you have to hand off signals from one to the next without dropping the ball. I’ve been in the trenches on this—from early Iridium backup sites to modern Ka-band tracking arrays—and the lessons stick with you. Here’s what you actually need to know to get a station from a patch of dirt to a working node in a global network.
Getting to Grips with the LEO Challenge
LEO satellites whip around at altitudes between 300 and 2,000 kilometres. A typical shell at 550 km gives you a pass that lasts maybe 10 or 15 minutes, and the bird is only above your horizon for a fraction of its orbit. You’re not just receiving a signal; you’re chasing it. The Doppler shift on a Ku-band downlink can swing by hundreds of kilohertz, and the path loss changes constantly as the range varies. Forget the luxury of a fixed dish and a steady link—this is a dynamic, high-stakes handover game.
And then there’s the environment. Wind, rain, ice, and even the sun’s heat mess with your gear. A dish that works perfectly in a lab can become a liability on a rooftop in a storm. You need to think about the site as a whole, not just the shiny antenna.
Picking the Right Spot
Location is everything. You want a clear view down to the horizon—ideally 5° elevation or lower. Hills, buildings, and even a line of trees will carve chunks out of your pass windows. But a remote hilltop with perfect sightlines might have lousy power and no fibre. Urban sites have connectivity but are swimming in RF noise. For a constellation, you’ll likely scatter several stations geographically. A site up north catches polar-orbit birds on every pass; an equatorial station sees them far less often.
Weather is a silent killer. High winds mean you need a radome or a seriously beefy pedestal. Snow and ice on a dish detune it and add weight. I once watched a tracking pedestal lock solid at -40°C because the factory grease turned to candle wax. Use low-temp lubricants and heated enclosures for anything critical. And lightning protection isn’t a checkbox—it’s survival. A direct hit can vaporise years of work in a flash.
Antenna Choices: Dishes, Arrays, or Both
For a single LEO satellite, a parabolic dish on a two-axis mount is the classic answer. For a constellation, you’ve got options: multiple dishes, phased arrays, or a mix. Each has its own headaches and payoffs.
Parabolic Dishes and Fast Pedestals
A 3.7-metre dish with a high-speed az-el pedestal can track LEO targets if the motors are up to it. You need azimuth speeds of at least 10°/s and elevation around 5°/s, with acceleration in the 5°/s² range. The controller needs fresh pointing data—either from the satellite’s broadcast ephemeris or a closed-loop system that peaks on the signal. Open-loop tracking with TLEs is common, but TLEs go stale fast. Most constellations push proprietary ephemeris updates over the internet.
One dish per satellite isn’t practical for a big fleet. Instead, you schedule passes: a dish tracks one bird, then whips around to catch the next as the first one sets. That slew time eats into your contact window, so lightweight carbon-fibre reflectors and fast motors are worth the money. If you’ve got two dishes, you can do a “make-before-break” handover—one acquires the rising satellite while the other finishes the setting one. It keeps the data flowing.
Phased-Array Antennas
Electronically steered arrays are the modern fix. No moving parts, beam switching in microseconds, and the ability to track several satellites at once with multiple beams. The catch? Cost and complexity. A Ku-band array with a few hundred elements can set you back as much as a decent house. Ka-band is even pricier. But for a high-throughput gateway serving a broadband constellation, the lack of mechanical wear and the multi-beam capability are hard to ignore.
Phased arrays give you a wide field of view—typically ±60° from boresight—so you can cover a big chunk of sky without moving. Gain drops off at the edges, though, and you have to watch out for grating lobes. A fixed installation might be tilted to favour a specific orbital plane. Some operators run a hybrid: a phased array for the main traffic and a small dish for telemetry and control.
Feed and RF Front-End
Whether you go dish or array, the feed and LNA make or break the link. For a dish, you need a feed that lights up the reflector efficiently without spilling energy onto the ground. Dual-polarised feeds double your capacity. The LNA should have a noise figure below 1 dB at Ku-band; at Ka-band, 1.5 dB is okay. Mount it as close to the feed as you can—waveguide losses add up fast. If you’re using a radome, factor in its loss. A wet radome can slap an extra 1 dB or more onto your budget.
Link Budgets and Data Throughput
A LEO link budget is a moving target. Path loss swings from about 2,000 km at 10° elevation to 550 km at zenith. You design for the worst case—usually the lowest elevation you’ll operate at—and build in margin. At 12 GHz, free-space path loss at 2,000 km is roughly 180 dB. With a 3.7-metre dish (gain ~51 dBi), a satellite EIRP of 40 dBW, and a 1 dB noise figure LNA, you might see a carrier-to-noise ratio of 15 dB at the receiver. That’s fine for QPSK with some coding, but 64QAM will struggle. Higher data rates demand a bigger dish or more power from the satellite.
Doppler shift needs active compensation. Modern modems track the frequency offset automatically, but you have to set the acquisition range wide enough—±500 kHz is typical for Ku-band LEO. The rate of change matters too; the modem’s carrier recovery loop has to lock fast and hold on as the frequency sweeps. Lab-test this with a channel simulator before you deploy, or you’ll be chasing your tail on site.
Atmospheric losses bite, especially at Ka-band. A heavy downpour can add 10 dB of attenuation. If you need 99.9% availability, your link margin has to cover the worst rain stats for your location. That often means a larger antenna or site diversity—two stations far enough apart that the same storm doesn’t clobber both.
Tracking and Control Systems
The antenna control unit is the brains. For a dish, it turns ephemeris data into pointing angles, correcting for your station’s lat, long, and altitude, plus a bit of atmospheric refraction at low elevations. The ACU should handle program track (from ephemeris), step track (peaking on signal strength), and monopulse if the feed supports it. For LEO, program track is the workhorse—step track can’t keep up with the speed.
For a phased array, the beam-steering computer calculates phase shifts for every element based on the look angle. It’s number-crunching heavy but well understood. The real pain is calibration: you need to measure each element’s phase and amplitude response across frequency and temperature, then store correction tables. Skip this, and your beam pattern goes soft—lower gain, higher sidelobes.
Time sync is non-negotiable. The station has to know the exact time to match the satellite’s ephemeris. A GPS-disciplined oscillator gives you precise time and a stable 10 MHz reference for downconverters and modems. Without it, you’ll point at the right spot at the wrong moment and miss the pass entirely.
Networking and Data Handling
A LEO ground station is a node in a global network, not just an antenna. Data from the satellite has to hit the constellation’s core network with minimal delay. That usually means a fibre connection to a PoP. If the site is remote, you might use microwave backhaul or even another satellite link—though backhauling satellite data over a satellite adds delay and complexity.
Inside the station, the LAN has to swallow the peak data rate. If your antenna spits out 1 Gbps, your switches and routers can’t be the bottleneck. Handovers are tricky: packets from the setting satellite have to be forwarded while the new link comes up. This needs tight coordination between the antenna controller, modem, and router. Some operators use SDN to reroute traffic on the fly based on pass schedules.
Security gets overlooked too often. A ground station is a juicy target for jamming or cyberattack. Encrypt the telecommand links, put firewalls in place, and lock the door. If your station is a gateway to the whole space segment, a breach could be a disaster.
Power and Infrastructure
Ground stations are power-hungry beasts. A 3.7-metre dish with tracking motors, HPAs for uplink, and racks of gear can pull 10 kW or more. Phased arrays are even thirstier because of all those active elements. You need reliable power: commercial mains with a UPS and a backup generator. In the middle of nowhere, solar panels and batteries might be your primary source, but size them for the worst insolation and enough storage to run through the night.
Cooling is another big deal. Indoor racks pump out heat, and outdoor electronics bake in the sun. Air conditioning or liquid cooling for indoor kit is standard. For outdoor phased arrays, passive cooling fins might work, but in hot climates you’ll likely need forced air.
Testing and Commissioning
You can’t just bolt a station together and expect it to work with a LEO constellation on day one. Start with a full system test using a satellite simulator. Inject a signal that mimics the Doppler profile, power variation, and data pattern of the real bird. Check that the antenna tracks, the modem locks, and data flows through the network. Then, if you can, test with a live satellite—maybe a single test bird in a lower orbit.
During commissioning, measure the antenna’s G/T using a radio star or a calibrated beacon. Compare it to the theoretical value. If you’re 2 dB short, hunt down the cause: misaligned feed, a dodgy LNA, or a radome issue. Write everything down. When the full constellation lights up, you won’t have time to debug.
Operational Realities
Once you’re live, the station needs 24/7 monitoring. Watch the received signal level, modem lock status, bit error rate, equipment temperatures, and power supply voltages. Set up automated alerts so someone can react before a pass is lost. Keep spares on site—LNAs, cables, power supplies—because a failure during a critical pass can mean lost revenue or worse.
Regular maintenance keeps you out of trouble. Check the pedestal for mechanical wear, clean the radome, and recalibrate pointing every year. For phased arrays, run a built-in test to check element health. Software updates for the ACU and modems should be tested offline first; a bug can send the antenna pointing at the ground instead of the sky.
Frequently Asked Questions
What’s the smallest dish I can use for LEO tracking?
It depends on the frequency and data rate. For Ku-band telemetry at a few Mbps, a 1.2-metre dish can work if the satellite has enough EIRP. For high-throughput Ka-band links, you’re usually looking at 2.4 metres or larger. Phased arrays are specced by EIRP and G/T rather than physical size.
How do you deal with multiple satellites passing at once?
With a single dish, you schedule passes and accept that you can only track one at a time. A multi-beam phased array can handle several simultaneously if they’re within its field of view. Some stations use multiple independent dishes, each assigned to a different satellite, with a central scheduler keeping order.
What’s the biggest mistake people make in ground station design?
Ignoring the environment. I’ve seen stations built in flood zones, stations with no real lightning protection, and stations where the air conditioning died because the outside air intake was clogged with dust. The RF design gets all the glory, but the civil and electrical engineering are just as make-or-break.