IRELAND · ConOps

Understanding ConOps for Dronebox Operations in Ireland

For professional and emerging drone operators in Ireland utilizing droneboxes—such as for parcel delivery—a Concept of Operations (ConOps) is essential. A ConOps details the operational context, processes, responsibilities, and safety measures, serving as a foundational document for applications or notifications to the Irish Aviation Authority (IAA). It also aids in determining the appropriate risk assessment (e.g., via SORA) and establishing an effective Emergency Response Plan (ERP).

What is a ConOps?

A Concept of Operations (ConOps) provides a clear and comprehensive overview of the planned drone activities. It details what tasks will be completed, how the operation will be conducted, who is involved, and the equipment and procedures in use.

The ConOps acts as a key communication document between the UAS operator, the competent authority (the IAA in Ireland), and other stakeholders. For dronebox operations, it is vital that the ConOps covers all operational phases: preparation, launch, flight, landing, and post-flight activities.

  • Purpose and scope of the dronebox operation
  • Geographical locations and applicable flight areas
  • Technical details of drones and dronebox systems employed
  • Roles and responsibilities of the operations team
  • Core operational processes and safety controls

Why is a ConOps Important for Dronebox Operations in Ireland?

In the Specific category, presenting a ConOps or an equivalent operational document is typically required by the IAA when applying for an operational authorization or permission for the intended flight activity. The ConOps supports the risk evaluation, frequently conducted via the Specific Operations Risk Assessment (SORA) methodology.

Beyond risk assessment, a well-prepared ConOps provides a structured framework supporting the UAS operator’s operational manual as mandated by European regulations. It helps prevent operational misunderstandings and enhances adherence to safety procedures.

    Key Components of a ConOps for Dronebox Operations

    A ConOps tailored for dronebox operations should include detailed information on the following elements to demonstrate both operational feasibility and safety.

    Each part should be succinct, clear, and tailored to the specific operation’s requirements.

    • Description of the dronebox system and drone platforms used
    • Operational scenarios including flight profiles, defined flight areas, and airspace considerations
    • Procedures for notification and coordination with Irish air traffic control and other relevant authorities
    • Communication protocols and command structure throughout the mission
    • Emergency procedures and a comprehensive Emergency Response Plan (ERP)
    • Training, qualifications, and competencies of all operational personnel
    • Maintenance schedules and inspection routines for all equipment

    How to Develop a ConOps for Your Dronebox Operation

    Begin creating your ConOps by thoroughly mapping out your operation and its objectives, involving all technical and operational team members engaged with the dronebox activity.

    Adopt a structured document format and, where relevant, align your ConOps with any applicable EASA-approved Pre-Defined Risk Assessments (PDRA) or Standard Scenarios (STS). Early consultation with the IAA is strongly encouraged for novel or complex operations to ensure regulatory expectations are addressed.

    • Summarise the operational aims in clear terms
    • Detail technical specifications of the drones and payload systems used
    • Describe step-by-step operational workflows
    • Incorporate risk assessment data based on SORA methodology or PDRA
    • Develop comprehensive emergency and incident response procedures within the ERP
    • Document clearly the roles, responsibilities, and qualifications of your crew
    • Maintain your ConOps as a living document with updates based on operational experience and regulatory changes

    Practical Tips and Common Mistakes in ConOps Documentation

    Ensure your ConOps document remains consistent, clear, and free of unnecessary jargon, making it accessible to both regulatory reviewers and operational team members.

    Common pitfalls include insufficient detail in emergency procedures, unclear allocation of responsibilities, and failure to engage with stakeholders such as air traffic controllers or local authorities.

    • Define flight areas precisely to prevent airspace conflicts
    • Explicitly address procedures for Beyond Visual Line of Sight (BVLOS) operations
    • Ensure alignment between the ConOps, operational manual, and Emergency Response Plan
    • Clearly document communication and coordination protocols
    • Regularly test and rehearse procedures described in the ConOps

    Frequently asked questions

    Is a ConOps mandatory for every dronebox operation in Ireland?

    For dronebox operations within the Specific category, the IAA generally requires a ConOps or an equivalent document as part of the application for an operational licence or permission.

    Can I use a standard PDRA instead of producing my own ConOps?

    If your dronebox operation fits entirely within an EASA-approved Pre-Defined Risk Assessment (PDRA) or Standard Scenario (STS), you may rely on these. For bespoke operations outside of these frameworks, a unique ConOps is necessary.

    How does a ConOps assist in creating a SORA risk assessment?

    By detailing operational specifics—such as flight profiles, geographic scope, risk mitigations, and emergency planning—a ConOps provides the essential data required for performing a comprehensive SORA risk assessment.

    Should the ConOps also include safety measures beyond the drone flight itself?

    Yes, an effective ConOps covers procedures for safe loading and unloading of droneboxes, security of equipment, and communications with the surrounding environment to maintain overall operation safety.

    How often should I review and update the ConOps?

    The ConOps should be maintained as a living document, updated after any changes to operational procedures, drone technology, regulatory requirements, or following any incidents, to ensure ongoing safety and compliance.