RC Plane Long-Range Flying: Antennas, Telemetry and Legal Limits

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Ask long-range pilots what limits their range and most will start talking about milliwatts. They are half right. Antennas, packet rate and failsafe setup decide whether a flight is repeatable, and two federal rules decide what is legal: an FCC power ceiling on the radio link, and an FAA requirement to keep the aircraft in sight.

A note on method: this page is built from maker manuals, the ExpressLRS project documentation, the autopilot documentation for iNav and ArduPilot, and the text of US regulations. It is not based on our own flying, and it is not legal advice. Every speed, range and power figure that comes from a manufacturer is labelled as a claim. The rules discussed are US rules; other countries differ.

Range is a link budget, not a power number

Every long-range setup comes down to three questions: how much signal leaves the transmitter, how much survives the trip, and how weak a signal the receiver can still understand. The last one is sensitivity, and it changes with packet rate.

ExpressLRS publishes sensitivity figures for each rate. A lower number (more negative) means the receiver can work with a weaker signal:

On 900 MHz the same documentation lists -123 dBm at 25 Hz and -117 dBm at 100 Hz. The pattern is the useful part: slower packet rates hear weaker signals, at the cost of how often the plane receives fresh stick positions.

Two more points from the documentation are worth keeping in your head:

• Link quality (LQ) matters more than signal strength alone. ExpressLRS explains that RSSI must sit above the sensitivity limit for packets to be understood, and that LQ is the percentage of packets getting through. If you can only watch one number, the project's advice is to pick LQ. It also suggests setting an RSSI warning 5 to 10 dB above the sensitivity limit for your packet rate.
• Doubling transmit power does not double range. ExpressLRS points readers to the inverse-square law to explain why a 1 W module does not double the range of a 500 mW one. TBS makes the same point in its Crossfire manual: every 6 dB increase in output power doubles the theoretical achievable distance.

What the record table does and does not say

The ExpressLRS long-range leaderboard is a useful reality check, as long as you read its caveats. It is a self-reported table with video links, and the project notes that not every flight ended in a failsafe at maximum range, so the link could sometimes go further. A few rows, all wings on 2.4 GHz:

Look at the 25 mW row next to the 2000 mW row: both are over 40 km, and both used 50 Hz. Packet rate and setup clearly matter alongside raw power. The second takeaway is a legal one: a 2 W entry sits above the 1 W ceilings discussed later in this guide, so it is a record, not a template.

The ExpressLRS hardware guide itself says a ceramic-antenna receiver with no amplifiers can reach 5 km at 250 Hz and 100 mW with a clear line of sight, which is already far beyond where most people can see a model.

Antennas: the cheap part that fails first

The ExpressLRS hardware guide ranks common receiver antennas by range: ceramic antenna, then mini dipole, then sleeved dipole, then half-wave dipole. The ceramic chip on a tiny receiver is the one that saves weight, and the guide warns that tucking it behind carbon or into a crowded stack hurts performance.

Points that follow from the documentation:

• Keep antennas clear of carbon. The documentation warns that tucking a tiny receiver's ceramic antenna deep inside a stack behind carbon reduces its performance.
• Know what diversity actually is. Per ExpressLRS, antenna diversity uses two antennas and a switch to route the signal from one or the other. True diversity uses two radio chips, each wired to a different antenna, and picks the strongest reception at any moment. The second gives more redundancy, particularly when an antenna null points at the pilot.
• Amplifiers have a job. A low noise amplifier adds to the incoming signal and, the project puts typical gains in the ballpark of +12 dB on the RSSI reading. A power amplifier on the receiver extends the telemetry range back to the transmitter, which otherwise tops out around 20 mW from the radio chip itself.

There is one regulatory twist here. Under 47 CFR 15.247(b)(4), the output-power limits assume antennas with a directional gain of no more than 6 dBi. Use a higher-gain antenna and the conducted power must come down by the amount of gain above 6 dBi. A relaxed 1 dB per 3 dB rule exists for 2.4 GHz, but it applies only to fixed point-to-point systems and expressly excludes omnidirectional applications, so it does not describe a moving aircraft. Fitting a big directional antenna and leaving the power untouched is not a loophole.

The control links, compared on their own documentation

ExpressLRS

ExpressLRS is a fully open-source link built around LoRa and related modulation, with support across both 900 MHz and 2.4 GHz and, per the project, over 50 manufacturers and hundreds of devices. For new users it recommends 2.4 GHz hardware unless you plan to fly hundreds of kilometres or in a high-noise environment. It notes 2.4 GHz gives the fastest packet rates, while 900 MHz is the original long-range frequency and can handle crowded Wi-Fi environments slightly better thanks to better penetration.

Setup points:

• Arming convention. The switch-configuration page carries a warning: if you arm using channel 5, put the arm switch on AUX1 and set it so roughly 1000 is disarmed and 2000 is armed. Plan your channel map around that.
• MAVLink telemetry. The project supports bidirectional MAVLink over the link, which is how ArduPilot users get telemetry to a ground station. Enabling it forces Hybrid or 16ch/2 switch mode (Wide mode is not supported) and a telemetry ratio of 1:2, and the docs recommend 2.4 GHz or dual-band LR1121 hardware for it.
• Gemini. Gemini transmits each packet on two frequencies at once: about 40 MHz apart on 2.4 GHz and roughly 10 MHz apart on 900 MHz. Gemini Xrossband sends on 2.4 GHz and 900 MHz at the same time using two LR1121 chips and needs a matching receiver. The project is direct about what this does: it does not extend range. Sensitivity stays the same for a given packet rate, but link quality stays higher up to the point of failsafe. It is an interference tool, not a range tool.
• Power. Most ELRS transmitter modules cap at 250 or 500 mW; a few 1 W modules exist.

One dual-band option is the Radiomaster DBR4 Gemini Xrossband ExpressLRS receiver. For a basic receiver, browse a search for an ExpressLRS 2.4 GHz receiver and match it to your transmitter module. Our transmitter and receiver guide covers bays, protocols and binding.

TBS Crossfire

Crossfire runs on 868 MHz in Europe and 915 MHz in the Americas. Per the manual, the link normally switches between 150 Hz and 50 Hz depending on link quality. The manual lists selectable transmitter power from 10 mW up to 2 W on the standard transmitter, a receiver sensitivity of up to -130 dBm, and a claim of 15 km of safe range in rural conditions at 100 mW.

Details worth knowing:

• Region settings matter. The FCC region limits the system to 915 MHz and 1 W and locks the setting. The CE region limits it to 868 MHz with listen-before-talk and 25 mW. An "Open" setting has no limit, which is a configuration choice, not permission.
• Dynamic power is recommended. TBS suggests letting the system run at low power and raise it automatically when the link is about to be lost.
• Diversity receivers have a recovery feature. The spec sheet lists a beacon mode and a backup LiPo battery on the (Nano) diversity receivers, giving roughly two days of operating time for recovery.

The manual's failsafe section is the part to read twice. Crossfire offers a cut mode and a failsafe-position mode. If a flight controller handles return-to-home, TBS says to use cut, so the receiver outputs no signal and the flight controller detects the loss. If you choose failsafe position but never teach one, the receiver outputs the last position before the link broke. To check what is currently listed, try a search for the TBS Crossfire Nano RX.

TBS Tracer

Tracer is a 2.4 GHz system with a constant 250 Hz uplink and downlink rate, 25 mW to 100 mW selectable power, and a claimed operating range of 15 miles plus (25 km plus). Each receiver has two antennas for antenna-based diversity. TBS markets it on low latency, so it suits fast, close-in flying more than distance work.

FrSky R9

FrSky describes R9 as its first 900 MHz long-range system. The R9M page claims an operating range up to 10 km and above, offers several switchable power outputs, and supports Smart Port telemetry. FrSky also claims its 2.4 GHz L9R has about twice the range of its X-series receivers. R9 remains a sensible path for flyers who already own the radio ecosystem. ExpressLRS's hardware guide also points existing R9 owners to its 900 MHz receivers, which is one route for people who want to move over later.

Spektrum DSMX

Spektrum's DSMX receivers are 2.4 GHz and designed for line-of-sight flying, not distance flying. The AR620 is a six-channel sport receiver with an internal antenna and telemetry for flight-log information that Spektrum says displays at fly-by range, typically 300 to 400 feet. The AR637T+ is a six-channel AS3X+ and SAFE receiver with integrated telemetry, an optional SRXL2 remote receiver port, and Smart Throttle support for compatible ESCs. Per Horizon, the AR620 is listed as in stock and the AR637T+ as on backorder at the time of checking.

For warbirds and scale models flown conventionally, this is the right category; our warbird guide covers suitable aircraft. See the Spektrum AR620 6-channel sport receiver. For the stabilised one, search for the Spektrum AR637T+.

GPS, flight controller and return-to-home

A long-range link is half the safety story. The other half is a flight controller that can bring the plane home when the link goes. Our flight controller guide covers general setup.

Failsafe: make the receiver say nothing

This is where planes get lost, and it is usually a settings problem rather than a hardware one. Three separate sources agree on the key idea:

• INAV triggers failsafe when any flight channel sends no pulses, when a channel is out of range, or when a failsafe switch is flipped.
• ArduPilot says setting the receiver to send "no pulses" on signal loss is much preferred, and that having the receiver send a preset throttle value is not recommended.
• TBS says to use "cut" when a flight controller handles return-to-home.

The common thread: a receiver that holds its last stick positions tells the flight controller nothing is wrong, so return-to-home may never start. Set the receiver to output nothing, then prove it on the bench. ArduPilot suggests turning the transmitter off and watching the flight mode change on the ground station.

What the autopilots do next

ArduPilot Plane has two phases. A short failsafe starts after RC_FS_TIMEOUT (one second by default) and, by default, puts the plane in CIRCLE mode, in case the changing orientation recovers the signal. If the loss persists beyond a set time, the long failsafe runs, which defaults to RTL. A GPS lock before arming is described as very important, and in RTL the plane flies to the arming location and loiters at a configured altitude.

INAV has failsafe procedures called DROP, LAND, RTH and NONE. Its notes include several useful warnings:

• If a required navigation sensor drops out during return-to-home, such as losing a GPS fix, the system performs an emergency landing after a short timeout.
• Return-to-home has an abort threshold meant to avoid flyaways caused by navigation problems such as strong winds.
• A guard-time setting (failsafe_delay) controls how long the controller waits before failsafe activates, and a stick threshold keeps return-to-home active after a sporadic link returns until the pilot moves the sticks, which the docs say happens a lot with long-range pilots.
• When failsafe ends, the current stick positions are enforced immediately, so be ready.

Do you need a compass on a plane? The two INAV documents disagree. The failsafe page says return-to-home requires GPS for any craft, plus compass and barometer for multicopters, while the navigation page lists the accelerometer, compass and GPS as requirements. This guide cannot settle that, so read the documentation for the exact firmware version you run before deciding what hardware to buy.

Matek boards and the end-of-life problem

Many guides still point to the Matek F405-WING V2 flight controller and the M10Q-5883 GPS and compass module. Both are marked "(EOL)" on Matek's own site, and the GPS module page carries a warning that counterfeits are circulating. Their specifications still work as a checklist for any fixed-wing board: an ICM42688-P IMU and DPS310 barometer, six UARTs, a microSD slot for blackbox logging, a current sensor rated for 100 A continuous, and firmware targets of INAV 6.0 or newer and ArduPlane 4.4 or newer. On the GPS side, Matek's module pairs a u-blox M10 receiver tracking four satellite systems with a QMC5883L compass, and Matek advises keeping the compass 10 cm from power lines, ESCs and motors. Matek also says to disable the softserial port in INAV when using a CRSF receiver such as TBS or ELRS. Both also showed as unavailable on the retail listings this guide checked, so the practical advice is to buy a currently sold board from a reputable maker and match it to the firmware you plan to run.

The legal ceiling

FCC power limits

Under 47 CFR 15.247, the output-power ceiling depends on how the radio works:

The 6 dBi antenna gain condition applies on top of those figures. Equipment sold for this use also has to be certified before marketing under 47 CFR 15.201, so look for FCC certification on any module or video transmitter you buy.

What about modules rated at 2 W? They exceed the Part 15 figures above. Amateur radio rules are a separate framework with their own requirements, such as station identification at least every 10 minutes under 47 CFR 97.119. Part 97 also has a specific section on model craft: identification is not required for transmissions directed only to the model if the transmitter carries a label with the call sign and the licensee's name and address, but that same section caps transmitter power at 1 W (47 CFR 97.215). A licence is therefore not a shortcut to unlimited power. Read the rules for the band you intend to use before running anything over the Part 15 limits.

FAA rules for recreational flights

For recreational flyers, 49 U.S.C. 44809 requires, among other conditions, that the aircraft stays within visual line of sight of the operator or of a visual observer who is co-located and in direct communication. Altitude is limited to 400 feet above ground level in Class G airspace, subject to the statute's exceptions. The statute also requires following a community-based organization's safety guidelines, passing TRUST, and registration and marking, all covered in our registration and TRUST guide.

For the commercial rules, 14 CFR 107.31 defines visual line of sight as seeing the aircraft with vision unaided by anything other than corrective lenses. The FAA's waiver page says a waiver is needed to fly beyond that ability.

For FPV, AMA Document 550 spells out practice:

• All FPV flights need a spotter next to the pilot who keeps the aircraft in line of sight throughout. AMA defines line of sight as being without enhancements other than corrective lenses.
• The spotter is briefed beforehand and must be ready to take the transmitter.
• If there is a safety issue that is not a brief glitch, the pilot abandons FPV and flies by line of sight.
• After installing or changing FPV or essential flight systems, an RC test flight without FPV is required.
• Novices should first be capable of flying without FPV. AMA also recommends a simulator and a programmable autopilot with return-to-launch or failsafe landing.

Our FPV camera guide and FPV aircraft roundup are the natural next stops.

Remote ID applies to aircraft that are registered or required to be registered, and the FAA's rules for broadcast modules and FRIAs are summarised in the registration guide.

Rules elsewhere

Other countries set their own power limits and band rules. TBS's CE region setting is one example: 868 MHz, listen-before-talk and 25 mW. Check your national authorities before importing a US setup.

Matching a setup to the flying

Across every row, antenna placement, a verified failsafe and a legal power setting matter more than the protocol badge.

Frequently asked questions