Beyond Visual Line of Sight (BVLOS) | UK CAA

How the UK CAA Regulates BVLOS Operations

The UK retained the EU's three-tier risk classification — Open, Specific, Certified — after the transition period ended, and the CAA administers it through the Air Navigation Order 2016 as amended and its associated policy framework. BVLOS operations cannot be conducted under the Open category, which is capped at visual line of sight and carries a 120 m altitude ceiling. Any flight where the remote pilot cannot maintain unaided direct visual contact with the UAS falls into the Specific category at minimum.

Within the Specific category, operators must submit a SORA-based risk assessment to the CAA and obtain an Operational Authorisation before flying. The SORA methodology evaluates ground risk class (GRC) and air risk class (ARC) to produce a specific assurance and integrity level (SAIL), which in turn drives the operational safety objectives (OSOs) the operator must demonstrate. Insurers use SAIL level as a proxy for operational complexity — higher SAIL typically means more demanding technical and procedural mitigations, which underwriters will want evidenced.

The CAA has also published a small number of standard scenarios and is developing a UK-specific equivalent of the EU's predefined risk assessments (PDRAs). Where an operator's BVLOS activity fits a published standard scenario, the authorisation pathway is faster, but the insurance requirements attached to that scenario still need to be met before the CAA will issue the authorisation. Brokers should request a copy of the Operational Authorisation and the accepted SORA submission as part of their pre-bind documentation checklist.

What BVLOS Authorisation Means for Underwriting

Underwriters treating BVLOS as a binary yes/no risk are underpricing complexity. The relevant variables are the approved operational volume, the GRC and ARC assigned in the accepted SORA, whether the operation is conducted over a controlled or uncontrolled environment, and whether observers or detect-and-avoid technology are part of the approved mitigations. Each of these factors affects both the probability of a loss event and the potential severity.

Hull cover for BVLOS platforms scales with hull value, payload value, and the degree of autonomous or automated operation. Fully autonomous BVLOS missions — where the remote pilot is monitoring rather than actively controlling — attract higher deductibles and may require specific exclusions to be negotiated out. Liability limits are quoted in GBP and must at minimum satisfy the CAA's mandatory third-party liability requirements under UK Regulation (EU) 2019/947 as retained; operators carrying commercial payloads or flying over populated areas will typically need limits materially above the regulatory floor.

Aggregated fleet programmes covering multiple BVLOS-authorised aircraft require careful scheduling. Each aircraft's registration, CAA UAS operator ID, and the specific Operational Authorisation reference should appear on the schedule. Mid-term changes to the authorisation — for example, an expansion of the approved operational volume — are a material change that must be notified to insurers promptly.

Coverage Scope: What a BVLOS Programme Should Include

A well-structured BVLOS programme addresses hull, liability, and the operational dependencies that sit between them. Hull cover should respond to in-flight loss, crash, fire, and — for higher-value platforms — ground risk while the aircraft is in transit or storage. Payload cover is often written separately or as an endorsement; confirm whether the payload is owned by the operator or a third party, as this affects both the insurable interest and the liability exposure if the payload causes harm.

Third-party liability is the coverage most directly shaped by the CAA authorisation. The policy wording must not exclude the specific type of BVLOS operation being conducted. Common exclusions to check include: autonomous flight, flights beyond a stated radius, operations over crowds or congested areas, and carriage of hazardous goods. If the Operational Authorisation permits any of these, the policy must be endorsed accordingly before the authorisation is relied upon.

Operators conducting BVLOS for infrastructure inspection, precision agriculture, or logistics should also consider: loss of licence cover for the remote pilot, cyber and data liability where sensor data is transmitted in real time, and contractual liability arising from service-level agreements with end clients. These are not mandatory under CAA rules but are increasingly expected by enterprise customers and public-sector contracting authorities.

• Hull and total loss — in-flight and ground risk
• Third-party bodily injury and property damage liability
• Payload cover (owned and third-party payloads)
• Autonomous and automated flight endorsement where applicable
• Cyber and data liability for sensor-data operations
• Loss of licence for named remote pilots

Broker Workflow: Placing a BVLOS Programme in the UK Market

Start with the regulatory documents, not the aircraft spec sheet. Obtain the operator's CAA UAS operator ID, the accepted SORA submission, the current Operational Authorisation (including any conditions or limitations), and the operator's operations manual. Underwriters will decline or heavily qualify submissions that arrive without these. If the authorisation is pending, some markets will offer a conditional quote subject to authorisation being granted before inception — confirm this in writing.

Prepare a structured submission that maps the SORA outputs to the underwriting questions. State the SAIL level, the approved operational volume (maximum height, lateral boundary, and environment type), the detect-and-avoid or observer mitigation used, and the operator's incident and near-miss history. If the operator holds a CAA-approved Remote Pilot Competency scheme qualification relevant to BVLOS, include it — it is a positive underwriting signal.

At renewal, the most common gap is a change in operational scope that was not notified mid-term. Build a renewal checklist that asks whether the Operational Authorisation has been varied, whether new aircraft have been added to the fleet, and whether the operator has commenced any new contract types (for example, moving from infrastructure inspection to urban logistics). Each of these may require a mid-term endorsement or a fresh submission.

• CAA UAS operator ID and registration certificates
• Accepted SORA submission and SAIL level
• Current Operational Authorisation with all conditions
• Operations manual (current version)
• Remote pilot competency evidence
• Incident and near-miss log for the preceding 12 months

Regulatory Triggers That Affect Cover Mid-Term

The CAA can vary, suspend, or revoke an Operational Authorisation if the operator fails to maintain the safety mitigations on which the authorisation was granted. A suspension does not automatically void the insurance policy, but it does mean the operator cannot legally fly BVLOS — any flight conducted during a suspension period would likely be an unlawful operation and could trigger a policy exclusion for breach of regulation. Brokers should ensure clients understand this linkage.

Changes to the UK's retained regulatory framework — including any future CAA standard scenarios or changes to the SORA methodology — can alter the authorisation requirements for existing operations. The CAA publishes guidance and consultations through its website and the UK Official Journal equivalent; monitoring these is part of the compliance function for any serious BVLOS operator. Insurers may also update policy wordings in response to regulatory change, so check endorsement language at each renewal.

For operators with cross-border ambitions — flying in EU member states as well as GB — note that the UK framework and the EU framework under EASA Regulation (EU) 2019/947 are now separate regimes. An operator holding a UK CAA Operational Authorisation does not automatically have permission to fly BVLOS in EU airspace; they will need to satisfy the relevant national competent authority in each EU state, and their insurance programme must respond to operations in each jurisdiction. This is a material underwriting consideration for any operator with European contracts.

Frequently asked questions

Does a standard commercial drone policy automatically cover BVLOS operations?

No. Most standard commercial UAS policies are written for visual line of sight (VLOS) operations and contain explicit exclusions for BVLOS or autonomous flight. A BVLOS programme requires a policy that has been specifically endorsed or underwritten to respond to the approved operational scope set out in the CAA Operational Authorisation. Always check the exclusions section against the conditions of the authorisation before binding.

What CAA documents does an operator need before they can be insured for BVLOS?

At minimum: a valid CAA UAS operator ID, an accepted SORA submission, and a current Operational Authorisation that explicitly permits BVLOS flight. The operations manual referenced in the authorisation should also be current and available. Some insurers will also require evidence of remote pilot competency for BVLOS operations. Submissions without these documents are routinely declined or deferred by specialist underwriters.

How does the SAIL level from the SORA affect the insurance programme?

SAIL level is the SORA's output measure of operational risk and the mitigations required to manage it. Underwriters use it as a structured indicator of complexity: higher SAIL levels imply more demanding operational safety objectives, more sophisticated aircraft and ground infrastructure, and potentially greater liability exposure. A higher SAIL level will typically result in more detailed underwriting questions, requests for evidence of specific mitigations, and may influence deductible levels and the scope of autonomous flight endorsements.

What happens to the insurance if the CAA varies or suspends the Operational Authorisation?

A variation to the authorisation is a material change that must be notified to insurers promptly. If the variation expands the operational scope — for example, adding a new environment type or increasing the operational volume — cover for the new scope will not attach until insurers have agreed to extend the policy. A suspension means the operator cannot legally conduct BVLOS flights; any flight during a suspension period may constitute an unlawful operation and could trigger a regulatory breach exclusion in the policy wording.

Can a UK CAA BVLOS authorisation be used to fly in EU member states?

No. The UK and EU now operate separate UAS regulatory frameworks. A UK CAA Operational Authorisation does not confer rights to fly BVLOS in EU airspace. Operators wishing to fly in EU member states must satisfy the relevant national competent authority under the EASA framework (Regulation (EU) 2019/947) in each state. Insurance programmes for operators with European contracts must be structured to respond to operations in each relevant jurisdiction, which requires explicit confirmation from underwriters.

At what point in the CAA authorisation process should a broker approach the insurance market?

Ideally, once the SORA submission has been accepted by the CAA and the operator has a draft or issued Operational Authorisation. Some markets will provide a conditional indication earlier — for example, once the SORA has been submitted and the SAIL level is known — but cover will not bind until the authorisation is granted. Approaching the market before the SORA is complete is unlikely to produce a usable quote and may create unrealistic expectations for the operator on premium and terms.