BVLOS Technology Requirements UK 2026

Command and Control (C2) Link Requirements

The C2 link is the lifeline of any BVLOS operation. It provides the ground-based pilot with real-time telemetry data — position, altitude, speed, battery status, sensor health — and enables the transmission of commands to the aircraft. For BVLOS operations, the CAA requires operators to demonstrate that the C2 link is reliable throughout the entire operating volume, with appropriate redundancy for link degradation or loss.

Primary C2 technologies: Direct radio frequency (RF) links operating on licensed or unlicensed spectrum remain the most common primary C2 solution. For shorter-range BVLOS operations (up to approximately 10-15 km), direct RF links using frequencies in the 900 MHz, 2.4 GHz, or 5.8 GHz bands can provide adequate coverage. Range is affected by terrain, antenna configuration, and electromagnetic interference.

Extended-range solutions: For operations beyond direct RF range, operators employ cellular network-based C2 (4G/5G), satellite communications (SATCOM), or relay station architectures. Cellular C2 offers low latency and high bandwidth but depends on network coverage, which can be patchy in rural areas where many BVLOS operations take place. SATCOM provides truly beyond-horizon capability but introduces higher latency.

Redundancy requirements: The CAA expects BVLOS operators to demonstrate C2 link redundancy proportionate to the risk of the operation. This typically means a backup communication path that activates automatically if the primary link degrades below acceptable parameters. Common redundancy architectures include dual-band RF links (e.g. 900 MHz primary with 2.4 GHz backup) or RF primary with cellular backup.

Link loss procedures: Every BVLOS operation must define what the aircraft does if all C2 links are lost. The standard response hierarchy is: attempt to re-establish communication, execute a pre-programmed loiter at a safe altitude, then perform an automated return-to-home (RTH) or controlled landing at a designated emergency site. The specific response must be documented in the Operational Safety Case.

Electronic Conspicuity and Transponders

Making the drone visible to other airspace users is a fundamental requirement for BVLOS safety. Electronic conspicuity devices broadcast the drone's position, altitude, and identification to nearby aircraft, air traffic control, and other drone operators. The CAA recognises several technologies:

• ADS-B (Automatic Dependent Surveillance — Broadcast): Transmits the drone's GPS-derived position on 1090 MHz. Many manned aircraft carry ADS-B receivers, making this an effective cooperative surveillance system. ADS-B OUT transmitters for drones are compact and lightweight. Some operators also fit ADS-B IN receivers to detect nearby manned aircraft, providing a cooperative detect-and-avoid layer.
• Mode S transponders: Respond to secondary surveillance radar interrogation from air traffic control. Mode S transponders are heavier and more power-hungry than ADS-B transmitters, but they integrate with established air traffic management infrastructure. The CAA may require Mode S for BVLOS operations in or near controlled airspace.
• Remote ID: UK Remote ID requirements broadcast the drone's identity, position, and operator location. While primarily a regulatory compliance measure, Remote ID data contributes to the overall electronic conspicuity picture and supports law enforcement identification.
• FLARM: A lightweight collision avoidance system widely used in general aviation, particularly gliders. FLARM-equipped drones can detect and be detected by FLARM-equipped aircraft, providing mutual awareness. This is particularly relevant for operations near gliding sites or in areas with high general aviation activity.

Detect and Avoid (DAA) Systems

The most technically challenging requirement for BVLOS operations is providing a detect-and-avoid capability that offers equivalent safety to visual observation by a pilot. The CAA does not prescribe specific DAA technology but requires operators to demonstrate that their solution is effective in the operating environment. Current DAA approaches include:

Cooperative detection: Systems that rely on electronic signals from other aircraft (ADS-B IN, FLARM, Mode S interrogation). These are effective against equipped traffic but cannot detect non-cooperative targets such as gliders without transponders, microlight aircraft, or other drones.

Non-cooperative detection: Radar, optical cameras, acoustic sensors, and LiDAR that can detect objects regardless of whether they carry electronic equipment. Ground-based radar systems provide wide-area surveillance but are expensive and fixed in location. Onboard cameras with AI-based object detection are improving rapidly but face challenges with small targets at distance, varying lighting conditions, and processing latency.

Layered approach: The most robust DAA solutions combine multiple detection methods. A typical layered system might use ADS-B IN for cooperative detection of equipped traffic, ground-based radar for non-cooperative detection of larger aircraft, and onboard cameras for close-range avoidance. The CAA views layered approaches favourably because they address the limitations inherent in any single technology.

Procedural mitigation: In lower-risk environments (very low-level operations over sparsely populated areas, segregated airspace), procedural mitigations may supplement or partially replace technological DAA. These include NOTAM publication, radio calls on relevant frequencies, coordination with local airfields, and use of visual observers at critical points along the route.

Failsafe and Contingency Systems

BVLOS platforms must incorporate multiple layers of failsafe systems that activate automatically when anomalies are detected. The CAA expects the Operational Safety Case to address every foreseeable failure mode and define the system response:

• Automated return-to-home (RTH): Triggered by C2 link loss, low battery, or pilot command. The RTH altitude must be set above all obstacles along the return path, and the system must handle GPS degradation gracefully.
• Geofencing: Virtual boundaries that prevent the aircraft from entering prohibited airspace, restricted areas, or departing the approved operating volume. Hard geofences should trigger immediate RTH or landing if breached.
• Flight termination system (FTS): A last-resort mechanism that cuts power to motors and, where fitted, deploys a parachute recovery system. The FTS is typically commanded by an independent link or triggered by onboard logic when the aircraft detects an unrecoverable situation.
• Redundant navigation: Dual GPS receivers with integrity monitoring (RAIM or equivalent) protect against GPS failure or spoofing. Some platforms incorporate inertial navigation units (INUs) that provide short-term navigation capability independent of satellite signals.
• Battery management: Intelligent battery monitoring that accounts for wind conditions, distance to home, and planned flight profile to provide accurate remaining endurance estimates. Conservative energy reserves should be mandated in the operating procedures.

Platform Selection for BVLOS Operations

Not every drone is suitable for BVLOS operations. The platform must be designed or adapted for the reliability and endurance demands of extended-range flight. Key selection criteria include sufficient flight endurance to complete the mission with appropriate reserves, redundant propulsion where practical (hexacopter or octocopter configurations for multirotors, twin-engine for fixed-wing), proven reliability across a documented flight history, and the ability to carry the required avionics payload (C2 equipment, transponder, DAA sensors) without compromising flight performance.

Fixed-wing and hybrid VTOL platforms dominate longer-range BVLOS operations due to their endurance advantages. Multirotor platforms remain suitable for shorter-range BVLOS work, particularly inspection tasks that require hover capability. The choice of platform should be driven by the operational requirement, not the other way around.

Demonstrating Compliance to the CAA

When applying for an Operational Authorisation, the CAA expects detailed documentation of all technology systems, including specifications, test results, maintenance schedules, and firmware management procedures. Operators should be prepared to demonstrate their systems in flight if requested, and to provide evidence of reliability from their operational history. The technology assessment is not a one-time event — the CAA may impose conditions requiring ongoing reporting of system performance and any anomalies encountered during operations.