In the context of professional and enterprise drone operations, where safety and compliance are non-negotiable, developing a robust framework for safe and compliant operations is essential. One of the most critical steps in achieving this is developing a robust and detailed Concept of Operations (ConOps). ConOps is not just a regulatory requirement under the Specific Operations Risk Assessment (SORA) framework; it serves as the cornerstone for assessing and mitigating risks in drone operations. This blog will guide you through Step 1 of the SORA process: defining your ConOps.

What is a ConOps?

A Concept of Operations (ConOps) provides a comprehensive description of the intended UAS operation. It includes the technical, operational, and system details necessary to assess risks and ensure safe execution. According to EASA, the ConOps forms the foundation for all subsequent SORA steps and reflects the operator’s safety culture.

The ConOps is not a static document. As risk assessments progress and additional mitigations or limitations are identified, the ConOps may need to be updated to remain accurate and comprehensive.

Key Elements of a ConOps

A ConOps is essentially a description of the mental picture of the intended operation. At AirHub Consultancy, we identify four key points that form the foundation of any ConOps. These points are expanded below while integrating additional details to fully describe what constitutes a robust ConOps:

1. Man

• This refers to the crew involved in the operation, including the remote pilot, observer(s), and any other roles such as payload operators.

• 
  

  
  

• Responsibilities, training, and qualifications of each crew member must be clearly defined to ensure competence and readiness.

2. Machine

• Includes the UAS itself along with any external systems and services used during the operation, such as navigation systems, communication links, geo-awareness tools, and payload equipment.

• 
  

  
  

• Details should cover the technical specifications, maintenance procedures, and operational capabilities of the equipment to ensure reliability and compliance.

3. Organisation

• The organization responsible for the operation must establish a robust governance structure and operational framework.

• 
  

  
  

• This includes Standard Operating Procedures (SOPs) for normal, abnormal, and emergency scenarios, as well as an Emergency Response Plan (ERP).

• 
  

  
  

• The organization must also ensure personnel meet training requirements, maintain operational safety culture, and comply with all technical and procedural standards.

4. Environment

• Refers to the operational volume, encompassing the flight geography, contingency volume, and ground risk buffer.

• 
  

  
  

• External stakeholders, such as Air Traffic Control (ATC) or U-space service providers, should be considered, along with population density, airspace type, and environmental factors like weather conditions.

• 
  

  
  

• Relevant charts, diagrams, and data visualizations should be included to provide a clear picture of the environment in which the operation will take place.

Each of these components contributes to a comprehensive understanding of the operation, ensuring that all technical, procedural, environmental, and organizational aspects are considered. This integrated approach provides a solid foundation for risk assessment and compliance with regulatory standards.

Iterative Nature of the ConOps

Developing the ConOps is an iterative process. During the SORA process, additional risk mitigations and operational limitations may emerge, requiring the ConOps to be revised. For example:

• If additional technical specifications are needed to address risks identified in Step 2 or beyond, these must be incorporated.

• 
  

  
  

• Any procedural updates resulting from operational safety objectives (OSOs) should be reflected in the ConOps.

Key Definitions to Understand the ConOps

The following definitions provide essential context for creating a comprehensive ConOps:

• Flight Geography: The volume of airspace where the UAS is planned to operate under normal conditions.

• 
  

  
  

• Contingency Volume: The volume of airspace outside the flight geography where contingency procedures are applied.

• 
  

  
  

• Operational Volume: The combination of the flight geography and contingency volume.

• 
  

  
  

• Ground Risk Buffer: An area on the surface surrounding the operational volume to minimize risk to third parties.

• 
  

  
  

• Emergency Response Plan (ERP): Procedures for addressing loss of control, crashes, or containment breaches.

• 
  

  
  

• Occurrence Reporting: The process of reporting damage, collisions, or injuries to the relevant authorities.

Conclusion

Defining a detailed ConOps is the first and most crucial step in the SORA process. It lays the groundwork for identifying risks, implementing mitigations, and ensuring safe and compliant drone operations. Whether you are an experienced operator or new to professional UAS operations, investing the time to develop a thorough ConOps will pay dividends in operational safety and regulatory compliance.

At AirHub Consultancy, we specialize in helping operators navigate the complexities of the SORA process, including defining a robust ConOps. Contact us to learn more about how we can support your drone operations.