Flight links are the invisible infrastructure that connects an RC transmitter to an aircraft. For FPV pilots, UAV operators, and RC hobbyists, the flight link determines range, reliability, latency, telemetry capability, and ultimately the level of operational confidence. Despite its importance, the flight link is often reduced to marketing shorthand such as “ELRS,” “ACCST,” or “Multiprotocol.” To properly evaluate modern radio systems, it is essential to break down the three independent components of a flight link:
- RF modulation and transport
- Telemetry subsystem
- Bind protocol and device identity
Each layer solves a different problem, and not all systems implement all features equally. This article explains each layer, how they interact, and how platform ecosystems such as ExpressLRS (ELRS), FrSky, Futaba, Spektrum, and Multiprotocol modules combine these layers into a usable control system.
1. RF Modulation Layer
The RF layer is responsible for physically transporting control and telemetry packets through the air across a defined frequency band. Key parameters of this layer include:
- Frequency band (2.4 GHz, 900 MHz, 433 MHz, 868 MHz)
- Modulation scheme (LoRa, FLRC, DSSS, FHSS, GFSK)
- Transmit power
- Packet rates
- Latency
- Interference tolerance
Different modulation schemes favor different outcomes:
- LoRa: extremely long range, robust, lower throughput, higher latency
- FLRC/GFSK: higher throughput, lower latency, less range than LoRa
- DSSS/FHSS (legacy): moderate range, moderate latency, legacy standards
Modern FPV links such as ELRS run both LoRa and FLRC modes depending on the use case. Racing pilots choose FLRC-based 250–500 Hz packet rates, while long-range pilots choose LoRa-based 50 Hz or 100 Hz profiles for multi-kilometer flights.
Legacy systems such as FrSky ACCST, Futaba FHSS, and Spektrum DSMX operate proprietary FHSS (Frequency Hopping Spread Spectrum) systems that balance interference robustness and moderate range but lack the extreme margins of LoRa modulation.
The RF layer is also where regulatory constraints are enforced. For example:
- 2.4 GHz maximum EIRP varies by region
- 915/868/433 MHz use ISM band rules for LBT (Listen-Before-Transmit) or duty cycle limits
Different countries enforce different RF rules, which affects commercial viability and user adoption.
2. Telemetry Layer
Telemetry is the reverse data channel traveling from aircraft to transmitter. In modern systems, telemetry informs the pilot about link health, battery status, GPS information, and flight system conditions.
Telemetry can operate through:
- A unified bidirectional protocol (ELRS, CRSF, SRXL2)
- Proprietary sensor buses (FrSky S.Port, Futaba S.BUS2)
- Partial feedback (RSSI-only on legacy systems)
Telemetry value is judged by:
- Update rate (Hz)
- Type of data supported
- Integration with flight controllers
- Integration with OSD
- Logging ability
Open telemetry systems (ELRS via CRSF) allow direct data transportation from Betaflight, INAV, ArduPilot, ESCs, GPS modules, and battery sensors. Proprietary ecosystems (FrSky, Futaba, Spektrum) require purchasing matching sensors, though the data is often cleaner and vendor-supported.
Systems lacking telemetry altogether (older CC2500 and basic multiprotocol use cases) limit situational awareness and range safety.
3. Bind and Device Identity Layer
The bind protocol defines how the transmitter identifies and associates with the receiver. It also defines:
- Receiver addressing
- Key exchange
- Model matching (if supported)
- Failsafe configuration method
- Multi-receiver fleets and model IDs
There are two philosophies in binding design:
- Static binding with stored IDs (FrSky, Futaba, Spektrum)
The receiver stores a transmitter ID once and reuses it, often with model matching. Good for multi-model users. - Dynamic binding and provisioning (ELRS)
ELRS can provision receivers via Wi-Fi or Lua scripts, allowing batch configuration for entire fleets. This is attractive for UAV operators with many airframes.
Bind protocols also govern failsafe behavior. In aviation terms, failsafe is the defined action when the link is lost:
- Hold last command
- Cut throttle
- Trigger RTH (Return to Home)
- Maintain attitude for glider recovery
Long-range builds require deterministic failsafe handling to avoid unrecovered flyaways.
Flight Link Stacks: How Ecosystems Position Themselves
Different brands combine these layers into stacks with different goals:
- ELRS (open-source performance stack)
RF: LoRa/FLRC digital
Telemetry: CRSF bidirectional
Binding: Key-based provisioning
Focus: Range, latency, open ecosystem - FrSky (ecosystem lock-in sensor stack)
RF: ACCST/ACCESS proprietary FHSS
Telemetry: S.Port ecosystem
Binding: Model match + secure ID
Focus: Hardware ecosystem monetization - Spektrum (aircraft heritage + SRXL2)
RF: DSMX FHSS
Telemetry: SRXL2 bus + sensors
Focus: Traditional RC markets (planes, helis) - Multiprotocol Modules (compatibility stack)
RF: CC2500/CYRF6936/A7105 etc.
Telemetry: Partial or none depending on target protocol
Focus: Compatibility > performance
Multiprotocol modules exist to unify legacy receivers, not to compete on performance or telemetry capability.
Interplay With Flight Controllers and OSD
Flight controllers such as Betaflight, INAV, and ArduPilot treat the flight link as just one of multiple I/O interfaces. They exchange data using serial protocols:
- CRSF (TBS + ELRS + ArduPilot + INAV ecosystems)
- SBUS (FrSky, Futaba legacy)
- SRXL2 (Spektrum)
- iBus (FlySky)
- PPM (legacy, analog-coded)
CRSF currently enjoys the broadest open-source adoption because it transports both control and telemetry in a single serial link and exposes GPS data for OSD.
Failsafe and Link Health Monitoring
Modern links employ two sets of metrics:
- Forward link: latency and packet success
- Reverse link: telemetry quality and feedback
Common metrics include:
- RSSI (strength)
- SNR (signal-to-noise ratio)
- LQ (link quality, % of successful packets)
- RF power level
- Distance and navigation data (if GPS available)
A robust flight link is not defined purely by theoretical range on a spec sheet; it is defined by how early it informs the pilot of degradation.
Future Trends
The flight link space is evolving quickly. Key industry trends include:
- Unified digital flight buses
- High-rate bidirectional telemetry
- Integration with ground stations and mission tools
- OTA provisioning of receivers
- Fleet management for UAV operators
- Expanded 900 MHz support for UGV/USV/UAV robotics
- More open-source standards replacing proprietary lock-in models
As FPV shifts into UAV, robotics, surveying, cinematography, and educational STEM, the flight link becomes a critical infrastructure component instead of a hobby accessory.
Conclusion
A flight link is more than frequency and range. It is a three-layer technology stack comprising:
- RF transport layer
- Telemetry data layer
- Binding and identity layer
Understanding these layers allows pilots and buyers to compare ELRS, FrSky, Spektrum, Futaba, and Multiprotocol equipment on objective criteria rather than marketing terminology. For modern FPV and UAV operations, the most compelling platforms are those with open telemetry, deterministic RF performance, and flexible provisioning.
Guide to Modern FPV Radio Ecosystems: ELRS, CC2500, Multiprotocol & EdgeTX