BVLOS ConOps Writing Guide UK 2026

Purpose of the ConOps

The Concept of Operations serves two functions. First, it is the foundation of your SORA risk assessment. Every parameter in the SORA — from the Ground Risk Class to the Air Risk Class to the applicable Operational Safety Objectives — derives from the operation as described in the ConOps. If the ConOps is vague, the SORA cannot be accurate.

Second, the ConOps is the primary document the CAA uses to understand your proposed operation. The assessor reading your application must be able to form a clear mental picture of what will happen, where, when, how, and by whom. If the ConOps leaves significant questions unanswered, the application will be returned for additional information.

Think of the ConOps as the single document that, if read in isolation, would allow a competent aviation professional to understand your entire operation.

Essential Sections of a BVLOS ConOps

While there is no rigid template mandated by the CAA, a well-structured ConOps for BVLOS operations typically includes the following sections:

1. Operation Description

A clear, concise summary of what the operation involves. State the purpose (inspection, survey, delivery, etc.), the typical mission profile (take-off, transit, task, return), and the expected frequency and duration of flights. Avoid marketing language — the CAA wants facts, not promotional material.

2. UAS Platform and Systems

Describe the drone itself, including its type designation, maximum take-off mass, characteristic dimension, propulsion type, and endurance. Detail the command-and-control (C2) link — its type, frequency, range, and redundancy provisions. If the UAS is equipped with detect-and-avoid technology, describe its capabilities, limitations, and the evidence supporting its performance claims.

3. Operational Environment

Define the geographical area of operations. Include maps showing the planned flight corridors, take-off and landing sites, and any areas to be avoided. Describe the terrain, the population density of the overflown area, and any significant obstacles. Identify the airspace classification and any nearby aerodromes, restricted areas, or danger areas.

4. Crew Roles and Competencies

Specify who will be involved in the operation and what their roles are. At minimum, this includes the remote pilot, but BVLOS operations often require additional personnel — observers, payload operators, or a mission commander. For each role, describe the required qualifications, training, and experience. State how competency is assessed and maintained over time.

5. Normal Operating Procedures

Walk through the operation from start to finish under normal conditions. Cover pre-flight checks, launch procedures, in-flight monitoring, mission execution, and recovery. Be specific — the CAA wants to see that you have thought through every stage of the flight, not just the airborne phase.

6. Abnormal and Emergency Procedures

This section is critical for BVLOS applications. Describe how the crew will respond to foreseeable abnormal situations, including:

• Loss of command-and-control link (lost link procedure)
• Loss of GPS or navigation failure
• Detect-and-avoid system failure
• Engine or power failure
• Unplanned entry into restricted airspace
• Medical incapacitation of the remote pilot

For each scenario, state the expected behaviour of the UAS (e.g., automated return-to-home, hover-in-place, controlled descent) and the actions the crew will take. Define the criteria for aborting a mission and the procedure for doing so safely.

Writing Quality That the CAA Expects

The CAA does not require literary excellence, but it does require precision. Avoid ambiguity. Where numbers are relevant — altitudes, distances, speeds, masses — provide them. Where procedures are described, use clear, sequential steps rather than narrative prose.

Use consistent terminology throughout the document. If you refer to the remote pilot as the "PIC" (pilot in command), use that term everywhere — do not switch between "PIC", "pilot", "operator", and "controller" interchangeably.

Include diagrams, maps, and tables where they add clarity. A well-annotated map of the operational area communicates more than several paragraphs of text describing the same geography.

Linking the ConOps to the SORA

The ConOps and the SORA are inseparable. Every input to the SORA must be traceable back to the ConOps. If the SORA assumes a sparsely populated area, the ConOps must define and justify that classification. If the SORA claims a mitigation, the ConOps must describe the procedure or system that implements it.

The CAA will cross-reference the two documents. Inconsistencies between the ConOps and the SORA are among the most common reasons for applications being returned. Before submitting, review both documents side by side and verify that every SORA input matches the corresponding ConOps description.

Practical Tips for a Stronger ConOps

• Start writing early: The ConOps should be drafted at the beginning of your planning, not as an afterthought before submission.
• Engage with the CAA: Use pre-application discussions to understand what level of detail is expected for your specific type of operation.
• Version control: The ConOps will evolve through multiple drafts. Maintain version control so you can track changes and ensure the final version is consistent.
• Peer review: Have someone unfamiliar with the operation read the ConOps. If they cannot understand what you intend to do, the document needs more work.
• Be honest about limitations: If your detect-and-avoid system has limitations in certain conditions, state them. The CAA responds far better to transparency than to overstatement.