BVLOS Operational Authorisation UK 2026

What Is an Operational Authorisation?

An Operational Authorisation is the formal permission issued by the CAA allowing a specific UAS operation within the Specific Category. For BVLOS flights, it is the only legal pathway. The OA defines the precise scope of what the operator is authorised to do — including the type of operation, the geographical area, the airspace, the UAS platform, and the conditions under which flights may take place.

The OA is not a blanket licence. It is tied to a specific operation described in the application. If the operator wishes to conduct a materially different operation — for example, using a different drone, flying in a different area, or changing the nature of the mission — a new or amended OA may be required.

Before You Apply: Pre-Application Engagement

The CAA strongly encourages applicants to engage in pre-application discussions before submitting a formal OA application. This step is not mandatory, but it is highly valuable.

During a pre-application meeting, the CAA's UAS team can provide guidance on the level of detail expected in the submission, flag potential issues with the proposed operation, and clarify how specific regulatory requirements apply. Operators who skip this step often find their applications returned with requests for additional information, which delays the process significantly.

To arrange a pre-application discussion, contact the CAA's UAS team through the official channels listed on the CAA website. Prepare a preliminary outline of your operation — even if it is not yet complete — so the discussion is productive.

Required Application Documents

A complete BVLOS OA application typically includes the following components:

1. Concept of Operations (ConOps): The central document describing the operation. It should cover the operational environment, the UAS and its systems, crew roles and responsibilities, normal and abnormal procedures, and the geographical and airspace boundaries of the operation.
2. SORA risk assessment: A completed Specific Operations Risk Assessment following the JARUS methodology as adopted by the CAA. This must include Ground Risk Class determination, Air Risk Class determination, final SAIL level, and the applicable Operational Safety Objectives with evidence of how each is met.
3. Technical file: Documentation about the UAS platform, including its flight performance, reliability data, command-and-control link specifications, and any detect-and-avoid systems fitted.
4. Competency evidence: Records of remote pilot qualifications, training, and experience. For BVLOS operations, the CAA expects a level of competency beyond the standard GVC (General VLOS Certificate).
5. Operations manual: Standard operating procedures, emergency procedures, maintenance schedules, and quality management documentation.
6. Insurance documentation: Evidence of third-party liability insurance adequate for the proposed operation.

The Assessment Process

Once the application is submitted, the CAA assigns it to a UAS specialist for assessment. The process typically involves several stages:

First, the application is checked for completeness. If any required documents are missing or insufficient, the CAA will request additional information before proceeding. Incomplete applications are the most common cause of delays.

Next, the CAA assesses the SORA and ConOps in detail. This includes evaluating whether the identified risks are comprehensive, whether the proposed mitigations are adequate, and whether the Operational Safety Objectives are met to the required level of robustness.

The CAA may ask questions, request amendments, or propose additional conditions. This is a normal part of the process and should not be viewed as a negative outcome. Constructive dialogue between the applicant and the CAA often strengthens the final authorisation.

If the CAA is satisfied that the operation can be conducted safely, it issues the Operational Authorisation with any conditions deemed necessary.

Common Reasons Applications Are Delayed or Rejected

Understanding why applications fail helps applicants avoid the same pitfalls:

• Incomplete SORA: Missing steps, unjustified mitigation claims, or incorrect SAIL determination.
• Vague ConOps: Failing to describe the operation in sufficient detail for the CAA to assess it.
• Inadequate detect-and-avoid strategy: Not explaining how the drone will detect and avoid other airspace users.
• Insufficient crew competency evidence: Providing only basic qualifications when the complexity of the operation demands additional training or experience.
• Poorly defined emergency procedures: Not covering lost-link scenarios, fly-away events, or forced landings in sufficient detail.

After Receiving Your OA

Receiving the Operational Authorisation is the beginning, not the end. Operators must comply with all conditions attached to the OA throughout the life of the authorisation. This includes maintaining crew competencies, keeping the UAS in the condition described in the technical file, and operating strictly within the authorised parameters.

The CAA may conduct compliance audits at any point. Operators are also required to report any occurrences that affect or could affect the safety of the operation. The OA will have a defined validity period, after which it must be renewed through a process similar to the original application.