Long-Range FPV Antenna Tracking: Ground Station Setup for 50km+ Range
When your quad crosses the 10km mark, a fixed directional antenna on a tripod stops being a luxury and starts being a necessity. Beyond 20km, it becomes the single point of failure that separates a successful long-range mission from a failsafe into a cornfield. Antenna tracking — keeping a high-gain directional antenna locked onto your aircraft as it moves — is the difference between a grainy, barely-flyable video feed and a clean image at 50km. Here’s how to build one that actually works.
Why Fixed Antennas Fail at Long Range
A typical 14dBi patch antenna has a beamwidth of roughly 30-40 degrees. At 5km, that covers a patch of sky about 2.5km wide — plenty of margin if you’re vaguely pointing in the right direction. At 30km, that same beamwidth covers a much narrower effective corridor, and your quad’s angular movement from the ground station perspective becomes tiny. A few hundred meters of drift at 30km can put you in the antenna’s null zone, where gain drops by 15-20dB — effectively the same as switching from a high-gain patch to a dipole. Antenna tracking solves this by keeping the antenna’s main lobe pointed directly at the aircraft regardless of position.
Tracker Architecture: The Three Approaches
There are three viable architectures for FPV antenna tracking, ranked from simplest to most capable:
- Mavlink telemetry-based: The aircraft sends GPS position via Mavlink telemetry (usually over the same RC link or a separate 433/868/915MHz modem). A ground-side Arduino or Raspberry Pi reads the telemetry stream, calculates the azimuth and elevation angles, and commands servo motors to point the antenna. This is the most common approach and works with ArduPilot, INAV, and PX4.
- Video RSSI-based: An array of antennas or a mechanically scanned antenna measures RSSI (signal strength) and steers toward the strongest signal. Rare in FPV because Mavlink telemetry is more reliable and doesn’t require additional RF hardware.
- GPS-on-both-ends: Both the aircraft and the ground station have GPS modules. The ground station calculates the bearing from its own position to the aircraft’s reported position. This is the simplest to implement but the least reliable because it depends on a working telemetry link to get the aircraft’s GPS data.
For most FPV pilots, the Mavlink telemetry approach is the gold standard. It’s well-supported by flight controllers and tracker firmware, and the telemetry link is usually more robust than the video link — meaning your tracker stays locked even when video gets sketchy.
Hardware Selection
Pan/Tilt Mechanism: You need a pan servo with at least 270 degrees of travel (360 is better) and a tilt servo with 90 degrees. The GWS S125 1T is the go-to pan servo for trackers — it’s a sail winch servo modified for 360-degree continuous rotation with position feedback. For tilt, a standard full-size servo with metal gears works. Avoid plastic-gear servos; they strip under the weight of a helical antenna in wind.
Controller: The Arduino-based open-source options dominate: – u360GTS (formerly Open360Tracker): The most mature firmware, supports Mavlink, Bluetooth configuration, and multiple antenna types. – ESP32-based trackers: Newer, with built-in WiFi and Bluetooth for wireless configuration. The ESP32-Antenna-Tracker project on GitHub is actively maintained.
Antenna choice for tracking: A tracker is only as good as the antenna it carries. For 5.8GHz: – Pepperbox (13-14dBi): Excellent balance of gain and beamwidth for tracking. The TrueRC X-Air and VAS Pepperbox are the standards. – Helical (10-15 turns, 13-16dBi): Narrower beamwidth but higher gain potential. Requires more precise tracking. – Patch array (16-20dBi): Very narrow beamwidth, only for serious long-range with precise tracking.
For 1.2/1.3GHz video (the long-range standard beyond 30km), a Yagi or crosshair antenna on the tracker is the way to go.
Mavlink Telemetry Integration
The tracker needs the aircraft’s GPS position in real-time. There are two ways to get it:
- Via the RC link: ExpressLRS and Crossfire both support Mavlink passthrough. On ELRS, enable “Mavlink” in the receiver output configuration. On Crossfire, set the output channel to Mavlink. The tracker connects to a spare UART on the transmitter module or to the radio’s Bluetooth serial output.
- Via a separate telemetry radio: A pair of 433MHz or 915MHz SiK radios (Holybro, RFD900x) provides a dedicated telemetry link that’s independent of the RC link. This is more reliable for extreme range but adds weight and complexity.
The tracker firmware reads the GLOBAL_POSITION_INT Mavlink message (message ID 33), which contains latitude, longitude, and altitude. Combined with the ground station’s own GPS position, it calculates the bearing and elevation angle using the Haversine formula.
Ground Station Power and Portability
A long-range ground station is not something you throw in a backpack. Plan for:
- Power: A 12V LiFePO4 battery (20-30Ah) runs the tracker, VRX, monitor, and DVR for 4-6 hours. Lead-acid batteries work too but are heavy. Avoid LiPo for the ground station — LiFePO4 is safer and holds voltage better in the field.
- Tripod: The tracker assembly plus antenna weighs 2-4kg. A solid video tripod with a fluid head (Manfrotto MVH500AH or similar) makes aiming and setup much easier than a cheap photo tripod.
- Cable management: You’ll have power cables, video cables, telemetry cables, and possibly an HDMI cable to a monitor. A cable loom with labeled connectors saves 15 minutes of troubleshooting at the field.
Real-World Lessons from 50km+ Flights
After building and flying multiple tracker setups, here’s what actually matters versus what the internet obsesses over:
- GPS lock on the ground station matters. If your ground station GPS is drifting or has poor satellite visibility (under trees, near buildings), your tracker will point slightly wrong. A few degrees error at 30km means your antenna is aimed hundreds of meters off-target. Use a GPS with a good ground plane and wait for 10+ satellites before flying.
- Servo jitter kills signal. Cheap servos oscillate around the target position, especially under wind load. This micro-movement causes signal fluctuation. Use quality servos with deadband of 2 microseconds or less.
- Elevation tracking is often unnecessary below 10km. At typical FPV altitudes (100-500m), the elevation angle at 10km is only 0.5-3 degrees. A fixed tilt angle works fine. Add elevation tracking for flights above 1km altitude or beyond 20km range.
- Telemetry packet rate matters more than you think. At 1Hz GPS update rate, the tracker receives a new position once per second. At 100km/h, the aircraft moves 28 meters between updates — enough to cause noticeable jitter in the tracker if it’s interpolating poorly. Increase Mavlink telemetry rate to 5-10Hz (set SR1_EXTRA1 to 5 or higher in ArduPilot) for smoother tracking.
Testing Your Setup
Do NOT test your tracker by flying far away and hoping it works. The first test should be with the aircraft on the ground, walking it in a large circle around the ground station while watching the tracker. Verify the antenna points directly at the aircraft throughout the full 360 degrees. Then do a short-range flight (under 2km) and verify the video quality is better with the tracker than without. Only then push the range.
Antenna tracking transforms the long-range FPV experience from a nerve-wracking exercise in signal anxiety to a confident, predictable flight where you can focus on the view instead of the RSSI number. The build takes a weekend and costs $150-300 — less than a single crashed long-range quad. There’s no excuse not to have one if you fly past 10km.