What is a ConOps for Drone Operators?

What is a ConOps?

A Concept of Operations (ConOps) is a comprehensive document describing the operational approach for a specific drone mission. It provides detailed information about the flight type, equipment and UAS technology used, the operational environment including airspace classification, safety measures, and organisational procedures. This clarity supports both the UAS operator and the IAA to understand and assess the planned activities and the approach to risk management.

For drone operations in the EASA Specific category requiring an Operational Risk Assessment (SORA), a ConOps is typically a mandatory part of the application dossier. The ConOps is also important when operating under predefined frameworks such as Standard Scenarios (STS) or Pre-Defined Risk Assessments (PDRA), where it clarifies operational details and ensures compliance with safety requirements.

• Defines the objectives, processes, and conditions for a drone operation.
• Enables consistent and transparent safety risk assessments.
• In Ireland, required by the IAA for operations outside the Open category.
• Supports preparation of operational manuals and Emergency Response Plans (ERP).

Key Components of a ConOps

A well-prepared ConOps addresses both operational and regulatory aspects necessary for approval and safe execution:

It outlines the mission specifics, flight location, involved airspace classification, the UAS and technology employed, and required communication and coordination methods. Planned flight procedures, safety mitigations and emergency protocols are described in detail. The ConOps also evidences compliance with applicable European (EASA) regulations and Irish national rules administered by the IAA.

• Operation description and flight objectives
• Details of the UAS, systems, and supporting technologies
• Operational environment and classification of the airspace
• Safety risk analysis and mitigation measures (SORA related)
• Emergency procedures and Emergency Response Plan (ERP)
• Training requirements and qualifications for operators and crew
• Coordination with air traffic control and relevant authorities
• Documentation, reporting, and post-operation evaluation processes

ConOps within EASA and Irish Regulatory Framework

Within the EASA framework, the ConOps is a core part of operational authorisations in the Specific category. Risk assessments following the SORA methodology rely on the ConOps to document operational risk and its mitigation.

In Ireland, the IAA reviews the ConOps as an essential element of permission requests or the Light UAS Operator Certificate (LUC) application. The document can also be integrated into the operator’s broader operational manual, a required element for many operations outside the Open category.

Operators must verify with the IAA if additional national requirements or templates apply for ConOps submission.

• Included in the application dossier for Specific category operations.
• IBA assesses the ConOps to demonstrate safe operational risk management.
• Must be kept current and updated following any changes in operation or equipment.
• Standard ConOps templates may be used for Standard Scenarios (STS) and PDRAs.

Practical Tips for Drafting a ConOps

For new and experienced drone operators alike, the ConOps should be precise, well-structured, and sufficiently comprehensive to facilitate a clear safety assessment. It is recommended to use a consistent format and avoid unnecessary detail while ensuring all critical information is present. Using examples, checklists and templates can improve completeness and usability.

Operators should confirm that their ConOps complies with both the IAA’s and EASA’s expectations. DroneManual offers support in producing and maintaining a compliant, professional ConOps as part of the overall operational dossier.

• Begin with a clear table of contents and the operation’s purpose.
• Specify the operational area and risk mitigations concretely.
• Develop the ConOps alongside the Operational Manual and ERP.
• Review and update regularly, especially when operational details change.
• Use official IAA and EASA guidance and checklists where available.
• Coordinate with relevant stakeholders, including ATC, early in the process.

Common ConOps Mistakes and How to Avoid Them

Common errors include vague or incomplete descriptions of operational details, which can cause the IAA to consider the document insufficient. Missing elements such as emergency procedures or communication protocols are frequently noted.

Another frequent issue is failure to update the ConOps to reflect changes in procedures, equipment or regulatory requirements. This can hinder permission renewals or inspections. Embedding the ConOps into the operator’s quality and safety management systems helps ensure it stays relevant and accurate.

• Avoid generic descriptions lacking detailed risk assessments.
• Include all emergency response plans and clear procedural instructions.
• Keep the ConOps and Operational Manual current and consistent.
• Incorporate findings from audits and incident reviews.
• Seek expert or authority feedback on the ConOps when possible.