Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Ask ten long-range pilots what limits their range and nine will start talking about milliwatts and antenna gain. They're only half right. The actual ceiling on how far you can legally fly an RC plane in the US has almost nothing to do with your transmitter and receiver and everything to do with two federal rules most builders never read: an FCC power cap on the radio link itself, and an FAA requirement that you keep the aircraft in sight the entire time. Everything else — protocol choice, antenna polarization, GPS return-to-home — is about making the flying you're already allowed to do more reliable, not about pushing past a line that was never there to begin with.
This guide separates the three things that actually determine your range and safety margin: the physical antenna layer that most people get wrong first, the control-link protocol that gets all the marketing attention, and the legal ceiling that quietly caps all of it. It also covers the piece that turns a long-range flight from a gamble into a repeatable habit — GPS, a proper flight controller, and a return-to-home failsafe that's configured correctly for a fixed-wing, not copy-pasted from multirotor advice.
The community numbers thrown around online are real, but they're rarely the numbers you should plan a flight around. ExpressLRS holds a leaderboard entry of 101.3 km on a 2.4 GHz link — flown at 2 watts, on a wing running ArduPilot, by ExpressLRS developer Wezley Varty. That flight also got him a AU$2,750 fine from Australia's Civil Aviation Safety Authority after the record video surfaced. The lesson isn't "don't fly far." It's that the link itself is almost never the bottleneck for a pilot flying within the rules — and understanding why changes how you should spend your money and your setup time.
This is a technical, hardware-heavy guide aimed at pilots already comfortable with a flight controller and basic FPV setup. If you're still choosing your first FPV plane or adding a camera system, start there first — the antenna and legal details below will make more sense once the basic airframe and radio link are sorted.
Quick Reference — Control Link Protocols at a Glance
| Protocol | Frequency | Max refresh rate | Typical latency | Telemetry | Best for |
|---|---|---|---|---|---|
| ExpressLRS (ELRS) | 2.4 GHz or 900 MHz | up to 1000 Hz | ~4 ms @ 500 Hz | Full (VBAT, LQ, RSSI, GPS, MAVLink) | Best value, open-source, most tunable |
| TBS Crossfire | 868/915 MHz | 150 Hz | ~14 ms | Full (S.Port-style + MAVLink passthrough) | Obstacle penetration, graceful degradation |
| TBS Tracer | 2.4 GHz | 250 Hz constant | ~3 ms | Full | Racing / low latency, not long range |
| FrSky R9/R9M | 900/868 MHz | Variable | Moderate | Smart Port | Existing Taranis/Horus ecosystem |
| Spektrum DSMX (AR637T etc.) | 2.4 GHz | Standard | Low | Basic (fly-by telemetry) | Traditional LOS scale/warbird flying, not FPV long range |
How Long-Range Control Links Actually Work
Every long-range setup is a link budget problem: how much signal leaves the transmitter, how much of it survives the trip through air and obstacles, and how sensitive the receiver is at picking out what's left. Three variables move that budget more than anything else — transmit power, antenna gain and orientation, and packet/refresh rate — and pilots consistently overweight the first one and underweight the other two.
Power matters least of the three for most flying. ExpressLRS running at just 100 mW on 2.4 GHz has demonstrated roughly 33 km in testing — far beyond where an FAA-compliant visual-line-of-sight flight would ever go. Refresh rate is a trade-off, not a free upgrade: dropping to 50 Hz on ELRS pushes receiver sensitivity down to roughly -117 dBm, buying enormous range at the cost of control resolution, which is exactly why long-range pilots run different rate profiles than racers. Antenna gain and polarization move the needle more than either of those, and it's the piece builders skip most often because it doesn't show up as a spec on a product page — it shows up as a mismatch you don't notice until the plane failsafes closer than it should.
The practical takeaway: a 900 MHz Crossfire link with a bad antenna setup will underperform a well-matched ELRS 2.4 GHz link running stock power. Protocol choice gets the attention; antenna work gets the results.
Antennas — The Layer Everyone Underrates
Polarization: Linear vs Circular
Antennas broadcast in one of two polarization styles. Linear antennas — the small rubber "dipole" or "monopole" sticks that ship on most stock hardware — radiate in a single plane. Circular antennas — cloverleaf, Pagoda, skew-planar, helical designs — radiate in a rotating pattern and, critically, reject multipath interference, because a signal that bounces off a building or the ground reverses its circular polarity and gets filtered out by a matched circular receiver antenna.
The number that matters here: a polarization mismatch between a vertically-oriented transmit antenna and a horizontally-oriented receive antenna can cost more than 20 dB of link budget. That's not a rounding error — it's the difference between solid control at 5 km and an unexpected failsafe at 2 km, with identical hardware and identical transmit power. Before touching protocol settings or upgrading a module, check that transmitter and receiver antennas are actually matched in polarization and type.
Gain and Directionality
- Omnidirectional (cloverleaf/Pagoda-style): roughly 1.5–2.5 dBi, radiates in a full 360° "donut" pattern. This is what belongs on the aircraft itself, since the plane's orientation relative to the pilot changes constantly.
- Directional patch: roughly 5–8 dBi across a ~120° cone. This belongs on the ground, pointed toward the flying area.
- Helical: roughly 9–14 dBi across a tighter 30–60° cone, for the longest predictable ranges when you know roughly where the aircraft will be.
Every 3 dB of additional gain roughly doubles effective range in the direction the antenna is pointed — but only in that direction, which is exactly why a highly directional antenna makes sense on a ground station (where a human can aim it) and a poor choice on the aircraft (which is constantly changing heading).
Diversity: Two Antennas, Two Approaches
"Diversity" receivers use two antennas to hedge against a single antenna's blind spots, but the two implementations aren't equivalent. Antenna diversity uses one receiver chip with an RF switch flipping between two antennas, introducing a small switching delay of roughly 50–100 microseconds. True diversity uses two independent receiver chips listening simultaneously, with no switching delay at all. TBS Crossfire's Diversity Nano receiver and ExpressLRS true-diversity receivers both use the two-chip approach for a reason: at long range, that switching delay is exactly the kind of small inefficiency that compounds.
The Mistake That Costs the Most Range
The single most common antenna error isn't a cheap antenna — it's running two identical omnidirectional antennas on a diversity setup. A diversity receiver with two omnis has nothing meaningfully different to switch between; it's paying diversity's overhead for none of diversity's benefit. The fix is simple and cheap: one omnidirectional antenna for general coverage, one patch or helical antenna on the ground station pointed at the flying area. That single change, done correctly, typically outperforms swapping to a more expensive protocol.
One more field habit worth adopting: circular-polarized antennas are more fragile than they look, with cracked internal solder joints causing gradual, easy-to-miss range degradation over months of use. If range quietly gets worse on a setup that used to work fine, the antenna — not the protocol or the flight controller — is the first thing to check.
Control Link Protocols Compared
ExpressLRS (ELRS)
ExpressLRS is the open-source option, built on LoRa modulation (Semtech SX127x for 900 MHz, SX1280 for 2.4 GHz, with newer LR1121 hardware enabling dual-band designs). It scales from 50 Hz up to 1000 Hz on 2.4 GHz, with latency as low as roughly 4 ms at 500 Hz, and it runs on selectable transmit power from 25 mW up through 1 W on standard hardware (2 W on some modules — more on why that matters in the legal section below). Telemetry is comprehensive: battery voltage, current, uplink/downlink link quality, RSSI, GPS position, and full MAVLink pass-through for autopilot integration.
The tuning detail that matters for a fixed-wing build specifically: ELRS uses channel 5 to track armed/flying state, so builders coming from a quadcopter background need to reserve that channel deliberately rather than assuming default settings carry over. Long-range profiles should run 100 Hz or lower with the switch mode set to wide for full channel resolution — the 500–1000 Hz racing profiles are the wrong tool here.
A receiver sits at the budget end of the category, with transmitter modules a step up from there. For pilots wanting extra interference resistance rather than raw range, ExpressLRS Gemini and Gemini-X (Xrossband) transmit each packet twice across two frequencies — 40 MHz apart on 2.4 GHz, roughly 10 MHz apart on 900 MHz — or, on Gemini-X hardware, simultaneously across both 2.4 GHz and 900 MHz using dual LR1121 chips. It's worth being clear about what this does and doesn't do: it does not extend maximum failsafe distance, it improves link quality and rejects interference along the way. A dual-band diversity receiver is the premium tier of this category, and mostly worth it in high-interference or urban-fringe flying environments rather than open fields.
TBS Crossfire
Crossfire runs on 868/915 MHz LoRa and tops out at 150 Hz refresh, with roughly 14 ms latency — slower on paper than ELRS, but Crossfire's real advantage is how it fails. Rather than dropping out abruptly, it steps down gracefully through lower refresh rates as signal weakens, giving a pilot warning before an actual loss of control rather than a hard cliff edge. Its Diversity Nano receiver uses genuine two-chip diversity, includes a LiPo backup for the receiver itself, and can broadcast a beacon with GPS coordinates in the event of a lost model.
Crossfire's 900 MHz band penetrates obstacles — trees, terrain, buildings — better than 2.4 GHz, which is the actual reason experienced long-range pilots reach for it, not because it has a higher raw range ceiling than a well-tuned ELRS setup. Community range reports around 5 miles at 250 mW line up with that obstacle-penetration advantage rather than a fundamentally longer link budget. One field habit worth knowing: Crossfire transmitters default to maximum power on power-up, which is a real consideration if you're flying near other pilots also on 900 MHz. Crossfire hardware sits mostly outside Amazon's catalog — specialty retailers are the more consistent source.
TBS Tracer
Tracer is a 2.4 GHz protocol built for racing, running a constant 250 Hz refresh with roughly 3 ms latency — the lowest-latency option here by a clear margin. But it can't step down its refresh rate gracefully the way Crossfire does, which shows up directly in range testing: one head-to-head test recorded Tracer failsafing at roughly 1.7 km against ExpressLRS failsafing at roughly 4 km, both running 25 mW. Tracer is the right tool for tight, fast, low-latency racing circuits. It is not the long-range option, and treating it as one is a common and avoidable mistake.
FrSky R9/R9M
FrSky's R9 system runs 900 MHz (868 MHz in the EU) with a range FrSky itself describes as "up to 10 km and above" on the R9M module, and its L9R non-telemetry receiver claims roughly double the range of FrSky's standard X-series receivers. Smart Port gives single-wire digital telemetry, and the system integrates cleanly with ArduPilot and iNav through passthrough telemetry and the Yaapu telemetry script — a real advantage for pilots already invested in a Taranis or Horus radio. That said, community sentiment has cooled since FrSky's ACCST-to-ACCESS protocol fragmentation, and a meaningful share of long-range flyers have migrated to ExpressLRS since. It remains a reasonable choice mainly where the radio ecosystem is already in place.
Spektrum DSMX
Spektrum's DSMX receivers — the AR637T, AR631, AR620 family — are 2.4 GHz only, with no sub-GHz long-range mode. That's not a shortcoming so much as a different design goal: these are built for traditional line-of-sight scale and warbird flying, with AS3X and SAFE stabilization baked in and genuinely plug-and-play setup. The AR637T adds an integrated barometer, Smart ESC telemetry, and an SRXL2 port for RF redundancy. Telemetry here is "fly-by" range — enough to monitor battery voltage and basic flight data — not a long-range FPV data link. If your plane is a warbird or scale build flown conventionally rather than FPV, this is still the right category of receiver; it's simply not part of the long-range conversation. A DSMX receiver covers that use case well.
GPS, Flight Controllers and Return-to-Home for Fixed-Wing
A long-range control link is only half the safety story. The other half is a flight controller that can actually navigate the plane home if the link drops — and fixed-wing return-to-home behaves differently enough from multirotor GPS-rescue that copying quadcopter defaults is one of the more common ways builders lose a plane.
The Flight Controller
For sub-1 kg FPV wings, the Matek F405-Wing V2 has become close to a de-facto standard, and it's worth understanding why: an STM32F405 processor, an ICM42688-P IMU, a DPS310 barometer, six UARTs, onboard blackbox logging, and a current sensor rated for 100 A continuous. It runs iNav (target MATEKF405SE, firmware 6.0+) or ArduPilot (4.4+) — and that firmware choice matters more than the board itself. Betaflight lacks the navigation and RTH functionality a long-range wing needs; iNav or ArduPilot are the correct firmware families for fixed-wing autopilot behavior, full stop.
GPS and Compass
A GPS module alone isn't enough on a fixed-wing — you need a compass too, and the reason is specific to how planes fly. A multirotor can infer heading from its GPS ground track even sitting nearly still. A wing moving slowly into a headwind can't reliably do the same, so iNav's return-to-home logic on a fixed-wing depends on the compass to know which way the nose is actually pointed. A module like the Matek M10Q-5883, built around the u-blox M10 chipset with an integrated QMC5883L magnetometer, locks satellites in well under 30 seconds — faster than the older M8-generation modules — and should be mounted at least 10 cm away from ESCs, motors, and other sources of magnetic interference to keep compass readings clean.
Getting Failsafe and RTH Actually Right
This is where planes get lost, and it's almost always a configuration error rather than a hardware failure. The receiver's failsafe behavior needs to be set to "No Pulses" or "Cut" — not "Hold Last Position." If the receiver simply holds the last known stick position when the link drops, the flight controller never actually detects a loss of signal, and return-to-home never triggers. The plane just keeps flying whatever the last command was, in whatever direction that happens to be.
A few more configuration details worth locking in before any long-range flight: set the throttle failsafe delay appropriately to avoid a mid-air disarm on a brief signal hiccup, and verify RTH altitude is set safely above terrain and obstacles along the expected return path, not just above the launch point. iNav has documented behavioral quirks worth testing for yourself before trusting them blind — reports of RTH loitering instead of returning, and of unstable turning behavior in strong upwind conditions on some configurations. None of this replaces testing RTH deliberately, at safe altitude, before relying on it during an actual long-range flight.
The community consensus on this is close to universal: fly with GPS and a configured RTH failsafe on every long-range flight, even if you're a confident manual pilot who doesn't expect to need it. It's a safety net, not a crutch, and the plane that comes home because RTH caught a link drop is worth infinitely more than the plane that becomes a permanent donation to a tree line. For a deeper walkthrough of flight controller setup and tuning specifics beyond long-range use, see the dedicated flight controller guide.
The Legal Ceiling — FCC Power Limits and FAA Flight Rules
This is the section most long-range content skips, and it's the one that actually caps what any of the hardware above can legally do.
FCC Power Limits
Under FCC Part 15.247(b)(3), digital modulation devices operating in the 902–928 MHz, 2400–2483.5 MHz, and 5725–5850 MHz bands — which covers essentially every RC control link and FPV video transmitter on the market — are capped at 1 watt of conducted output power without a license. That single number is the reason a 2 W ExpressLRS module exceeds what's legally permitted under Part 15; running one legally requires an amateur (HAM) radio license under Part 97 instead. The rule also scales with antenna gain: above 6 dBi of antenna gain, conducted power has to be reduced roughly dB-for-dB to keep total effective radiated power within the same ceiling (2.4 GHz fixed point-to-point links get a slightly more generous exception of 1 dB reduction per 3 dBi of gain).
A detail worth knowing even if you never plan to run 2 W: most FPV video transmitters on the market are not Part 15 certified at all, which technically puts them in Part 97 territory requiring an amateur license regardless of power level. The Technician-class amateur license — the entry tier — is a 35-question test and is genuinely achievable in an evening of study for anyone who's already comfortable with RC electronics. It's a low-effort way to fly with real legal footing rather than hoping nobody's monitoring the band.
FAA Flight Rules
Power output is only one half of the legal picture — the other is where and how you're allowed to fly at all. Recreational flyers operate under 49 USC 44809, which requires the aircraft to remain within visual line of sight throughout the flight. For FPV flying specifically, that means a co-located visual observer watching the aircraft directly, not just watching a video feed. Part 107 is the default commercial framework, and 44809 is a recreational exception that requires meeting all nine of its conditions plus passing the TRUST safety test — it's not a blanket pass to fly however far a link will reach.
Beyond visual line of sight (BVLOS) flight is prohibited under Part 107.31 without a specific waiver, and Remote ID broadcast requirements apply to drones requiring registration (generally aircraft at or above 250 g), with narrow exceptions for flying at FAA-Recognized Identification Areas. None of this is a suggestion layered on top of the hardware conversation — it's the actual boundary. The ExpressLRS leaderboard's headline 101.3 km flight is a genuinely impressive engineering result and also, under US-equivalent rules, not a legal flight profile to replicate.
One more point worth flagging without diving deep into it: these rules aren't uniform globally. The UK and EU operate different Open Category subcategories with their own VLOS and registration requirements, EU ExpressLRS firmware runs LBT (listen-before-talk) restrictions capped at 100 mW on 868 MHz versus the US FCC allowance up to 1 W on 915 MHz, and Australia's CASA has shown it will actively fine record-chasing flights. If you're flying outside the US, check your own aviation authority's rules rather than assuming the FCC/FAA framework above applies.
Which Long-Range Setup Should You Choose?
Flying line-of-sight scale or warbird models, want a more reliable stabilized link: Spektrum DSMX (AR620 or AR637T) is the right category entirely — this isn't a long-range FPV question for you, it's a reliability and stabilization question, and DSMX plus AS3X/SAFE answers it well.
Building a first long-range FPV wing on a reasonable budget: ExpressLRS on 2.4 GHz, paired with a Matek F405-Wing V2 running iNav and an M10-series GPS/compass module. This is the setup with the widest community support, the most tunable range/latency trade-off, and the lowest cost of entry.
Flying in wooded, hilly, or obstacle-heavy terrain where penetration matters more than raw distance: TBS Crossfire on 900 MHz. The graceful failsafe degradation and obstacle penetration are worth the higher receiver cost for that specific flying environment.
Flying in a high-interference area — near other pilots, urban fringe, competing 2.4 GHz traffic: ExpressLRS Gemini or Gemini-X dual-band hardware. It won't extend your maximum range, but it meaningfully improves link stability where interference, not distance, is the actual problem.
Racing or tight, fast circuits where latency matters more than distance: TBS Tracer. Don't bring this to a long-range flight — it's the wrong tool for that job specifically.
Already invested in a FrSky Taranis/Horus radio ecosystem: R9/R9M remains a workable path, particularly if Yaapu telemetry integration on an existing radio matters to you. New builds without that existing investment are better served by ExpressLRS today.
Across every one of these paths, the antenna setup — matched polarization, one omni plus one directional ground antenna, genuine diversity rather than two identical antennas — moves the needle more than the protocol choice itself. Spend the effort there first.
Frequently Asked Questions
Q: What's the actual legal range limit for flying an RC plane in the US?
There isn't a distance limit written into the rules directly — the limit comes from two other requirements. The FCC caps most control links and FPV video transmitters at 1 watt of conducted power without a HAM license, and the FAA requires recreational flyers to keep the aircraft within visual line of sight, with FPV flight requiring a co-located visual observer. In practice, those two rules together keep a legal recreational flight well short of the multi-kilometer distances hardware alone is capable of.
Q: Do I need a HAM radio license for FPV flying?
If your video transmitter isn't Part 15 certified — which describes most FPV VTXs on the market — or if your control link module runs above 1 watt, yes, a Technician-class amateur radio license is the legal path. It's a 35-question test and achievable with modest study, and it's the difference between flying with real legal footing and hoping nobody checks.
Q: Is ExpressLRS or TBS Crossfire better for long range?
Neither wins outright — they solve slightly different problems. ExpressLRS on 2.4 GHz has demonstrated roughly 33 km of range at just 100 mW in testing and offers the most tunable, lowest-cost path into long-range flying. TBS Crossfire's 900 MHz band penetrates obstacles like trees and terrain better, and its refresh rate degrades gracefully as signal weakens rather than failing abruptly. Open-field flying favors ExpressLRS on value and tunability; wooded or obstacle-heavy terrain is where Crossfire earns its higher price.
Q: Do I need GPS and return-to-home if I only fly within visual line of sight?
It's not required by the rules, but the long-range community treats it as standard practice regardless of how you fly. A GPS and correctly configured RTH failsafe is a safety net for the flights where something goes wrong unexpectedly — a control surface failure, a sudden battery issue, a link glitch — not just a tool for pilots deliberately flying to the edge of their link's range.
Q: Why does my plane failsafe well before the range my hardware is supposed to reach?
The most common cause isn't the protocol — it's the antenna. Two identical omnidirectional antennas on a diversity receiver, or a polarization mismatch between transmitter and receiver antennas, can cost more than 20 dB of link budget, which shows up as a failsafe at a fraction of the distance the hardware should otherwise support. Check antenna matching and diversity setup before assuming you need a different protocol or more power.
Conclusion
Long-range RC flying rewards getting three layers right in the correct order: an antenna setup with matched polarization and genuine diversity, a control link protocol matched to your actual flying environment rather than the biggest number on a spec sheet, and a legally compliant flight profile that respects the FCC's power ceiling and the FAA's visual-line-of-sight requirement. The protocol choice — ExpressLRS, Crossfire, Tracer, FrSky, or Spektrum — matters less than most builders assume; the antenna work and the GPS/RTH safety net underneath it matter more.
If you're building this system out from scratch, start with the flight controller guide for the autopilot side of the setup, the transmitter and receiver guide for the radio system fundamentals, and the FPV camera guide if you're adding a video link alongside the control link covered here. For airframe options built with this kind of flying in mind, the best FPV RC planes roundup is the right next stop.
The pilots who fly reliably at distance aren't the ones chasing leaderboard numbers — they're the ones who fixed their antenna polarization, configured RTH correctly, and stayed inside a legal power and altitude envelope every single flight. That's a far more repeatable win than a record that ends with a fine.
