conops
What is a ConOps for drone-in-a-box systems and how to develop one?
For professional and emerging drone operators in the United Kingdom deploying drone-in-a-box systems—for instance, for parcel delivery—a Concept of Operations (ConOps) is indispensable. A ConOps describes the operational context, processes, responsibilities, and safety measures, serving as a foundational document for applications or notifications to the UK Civil Aviation Authority (CAA). This document also aids in determining the appropriate risk assessment (such as the Specific Operations Risk Assessment, SORA) and in establishing an effective Emergency Response Plan (ERP).
What is a ConOps exactly?
A Concept of Operations (ConOps) presents a clear and comprehensive overview of the intended drone activities. It specifies what is done, how the operation is conducted, who is involved, and which techniques and procedures are used.
The ConOps acts as a communication document between the drone operator, the competent authority (such as the UK CAA), and other relevant parties. For drone-in-a-box system operations, it is essential that the plan covers all phases: preparation, launch, flight, landing, and post-operation management.
- Purpose and scope of the drone-in-a-box system operation
- Locations and flight areas
- Types of drones and systems used (e.g., drone-in-a-box system model and payload)
- Roles and responsibilities of the operational team
- Key operational procedures and safety measures
Why is a ConOps important for drone-in-a-box system operations in the UK?
In the UK, operations in the Specific category normally require a ConOps or an equivalent functional document as part of the application for an Operational Authorisation. This document enables the UK CAA to assess operational risks, often alongside a SORA (Specific Operations Risk Assessment).
Additionally, a thoroughly prepared ConOps supports the structure of the operational manual, helps prevent misunderstandings within the operational team, and promotes adherence to safety procedures and regulatory compliance.
Key components of a ConOps for a drone-in-a-box system
A ConOps for drone-in-a-box system operations should include detailed information on the following elements:
Each element must be described clearly and concisely to demonstrate the practical feasibility and safety of the operation.
- Description of the drone-in-a-box system and drones used
- Operational scenarios, including flight profiles and flight areas (with air traffic information and any restrictions)
- Notification and coordination procedures with air traffic control and other relevant aviation stakeholders
- Communication and command structure during flight operations
- Emergency procedures and Emergency Response Plan (ERP)
- Training and qualifications of the operational drone team
- Maintenance and inspection procedures
How to develop a ConOps for your drone-in-a-box system operation
To develop a ConOps, begin by documenting the operation and intended outcomes in detail. Involve all team members who have operational or technical roles related to the drone-in-a-box system.
Use a structured format and reference any available Pre-Defined Risk Assessments (PDRAs) or, where applicable, standard scenarios (note: UK CAA currently does not use STS as an operational route). Prepare a draft and consult the UK CAA to obtain feedback, especially for novel or complex operations.
- Start with a summary of the operational objectives
- Describe the equipment and systems employed, including technical specifications
- Detail step-by-step operational workflows
- Include risk assessments per SORA or PDRA methodologies
- Develop emergency and incident procedures within an ERP
- Document roles and competencies of the team members
- Keep the ConOps current by updating regularly with operational experience
Practical tips and common mistakes in ConOps documentation
Ensure that the ConOps is consistent and easy to understand, avoiding technical jargon where possible. The document should be useful to staff at all levels, from policy makers to operational personnel.
Common errors include missing detailed emergency procedures, unclear allocation of responsibilities, and lack of coordination with relevant stakeholders such as air traffic control.
- Be precise about flight areas to prevent airspace conflicts
- Clearly address procedures for BVLOS (Beyond Visual Line of Sight) operations
- Verify that the ConOps aligns with the operational manual and ERP
- Explicitly document communication protocols
- Regularly test and practise the procedures described in the ConOps
Frequently asked questions
Is a ConOps mandatory for every drone-in-a-box system operation in the UK?
For drone-in-a-box system operations in the Specific category, a ConOps or equivalent document is almost always required by the UK CAA as part of the application for an Operational Authorisation or specific flight approval.
Can I use a standard PDRA instead of creating my own ConOps?
If your drone-in-a-box operation fits entirely within a Pre-Defined Risk Assessment (PDRA) approved by the UK CAA, you may use that. However, bespoke operations require a tailored ConOps.
How does a ConOps support a SORA risk assessment?
The ConOps provides the operational details essential for assessing risks using the SORA method, including flight area, profiles, mitigations and emergency planning.
Should the ConOps also cover safety measures beyond just the drone flight?
Yes, a comprehensive ConOps also includes procedures related to loading and unloading drones in the drone-in-a-box system, securing equipment, and maintaining safe communication with the surrounding environment.
How frequently must the ConOps be updated?
A ConOps is a living document that must be updated following any changes in operational procedures, technology, regulations, or after incidents to ensure ongoing safety.