Autel EVO Insurance UK | Hull & Liability Cover

Regulatory Starting Point: CAA Open and Specific Category

All commercial Autel EVO operations in Great Britain are governed by the UK Civil Aviation Authority under the Air Navigation Order 2016 (as amended) and the separate statutory instruments establishing the Drone and Model Aircraft Registration and Operator Identification Scheme. These are distinct pieces of legislation; conflating them creates compliance confusion. Your insurance obligations differ materially depending on which sub-category applies to your operations.

UK CAA Open Category divides into three sub-categories with distinct competency and operating requirements. A1 permits flight with C0 or C1-class aircraft over but not intentionally over uninvolved persons. A2 requires an A2 Certificate of Competency (A2 CofC) and mandates a minimum 50-metre horizontal distance from uninvolved persons when operating C2-class aircraft, reducible to 5 metres in low-speed mode. A3 is reserved for C3 and C4-class aircraft flown away from people in sparsely populated areas. EVO Lite variants operating commercially will typically sit in A2 or A3 depending on configuration and environment; EVO II airframes, given their all-up weights in the one-to-two kilogram range depending on payload, map to A2 or Specific Category for most commercial missions.

EVO II Pro and EVO II Enterprise operations over uninvolved persons, in congested areas, or beyond visual line of sight (BVLOS) will typically require a Specific Category Operational Authorisation (OA) from the CAA. The standard competency qualification for Specific Category OA applications is the General VLOS Certificate (GVC). Operators who have not yet obtained a GVC should factor the qualification timeline into their operational planning — underwriters will ask for evidence of pilot competency at submission.

For common Specific Category mission profiles, operators may qualify for a Pre-Defined Risk Assessment (PDRA) rather than commissioning a bespoke SORA. A PDRA is a CAA-published risk assessment covering a defined set of operating conditions; if your EVO II missions fall within those conditions, a PDRA-based OA is faster to obtain than a full SORA. Where a full SORA is required, the process produces a SAIL — Specific Assurance and Integrity Level, expressed as a Roman numeral from I to VI — which determines the robustness of operational safety objectives the operator must demonstrate. Underwriters ask for the SAIL, not a generic 'risk class'; submitting documentation that clearly states the SAIL level accelerates the binding process.

Hull Cover for the Autel EVO Range

Hull insurance covers physical loss or damage to the aircraft itself, including rotors, cameras, gimbals, and integrated sensors. For the EVO II series, the interchangeable payload system means the insured value must be declared per configuration — a bare airframe value differs from the same unit fitted with a thermal or multispectral sensor. Underwriters will ask for itemised schedules; a single lump-sum declaration is rarely adequate for multi-payload fleets.

Agreed value versus market value is a meaningful choice for Autel EVO operators. Because Autel releases firmware and hardware revisions at pace, market value can depreciate faster than operators expect. Agreed value policies fix the settlement figure at inception, removing depreciation disputes after a total loss. For high-utilisation commercial operators this is generally the preferable basis.

Deductibles on hull claims typically rise where the aircraft is operating autonomously, beyond visual line of sight, or in degraded-visibility conditions — all scenarios the EVO II's obstacle-avoidance and RTK modules are designed to enable. Operators should confirm with their broker whether autonomous or BVLOS missions require a policy endorsement and whether the deductible structure changes as a result.

Several exclusions commonly found in drone policies catch EVO operators off guard. Wear-and-tear on rotors and gimbals is almost universally excluded; these are consumable components and should be budgeted separately. Flyaways caused by a firmware update are frequently excluded or disputed, particularly where the operator cannot demonstrate the update was applied in accordance with the manufacturer's guidance. Payload data liability — claims arising from errors in survey data, thermal readings, or inspection imagery — is typically excluded from standard hull and liability wordings and requires a specific endorsement. War and terrorism exclusions apply across virtually all drone policies. Review each of these with your broker before binding.

Third-Party Liability: Scope and Regulatory Context

Third-party liability (TPL) cover pays for bodily injury or property damage caused to third parties. For commercial UAS operations in Great Britain, the Air Navigation Order establishes liability requirements that apply to commercial operators; the applicable thresholds relate to the aircraft's MTOM. EVO II Pro and Enterprise airframes, with all-up weights typically in the one-to-two kilogram range depending on battery and payload, sit well within the sub-25 kg commercial UAS band — the 25 kg threshold is not a relevant ceiling for any current EVO II configuration. Operators should verify the all-up weight of their specific configuration — airframe plus battery plus payload — and confirm the correct liability band with their broker rather than assuming a worst-case figure.

Beyond the regulatory floor, commercial clients — survey firms, infrastructure inspectors, film production companies — routinely require contractual liability limits that exceed the minimum. A specialist MGA can structure excess liability layers or combined single-limit policies to meet client contract requirements without duplicating coverage unnecessarily.

Premium cost shape for TPL is driven by several qualitative factors: operating environment (congested urban areas carry higher exposure than open rural sites), annual flight hours, pilot experience and claims history, payload value and type, and whether BVLOS or autonomous operations are included in scope. None of these factors has a fixed multiplier that can be quoted in advance; the broker's role is to present the risk accurately so the underwriter can price it correctly.

What a Complete Autel EVO Policy Schedule Should Cover

A well-drafted policy for an Autel EVO commercial operator should address the following coverage elements explicitly. Generic drone policies often contain exclusions that catch EVO-specific features — particularly the swappable payload system and the aircraft's BVLOS-capable avionics.

Operators and brokers should confirm each of the following is either included or consciously excluded with a clear reason:

• Hull — agreed value, all-risk basis, covering airframe, battery, gimbal and declared sensor payloads per configuration
• Third-party liability — limit at or above the ANO statutory minimum for the aircraft's MTOM band, and at or above any contractual minimum required by the operator's clients
• Payload data liability — coverage for claims arising from errors in sensor data output (survey, inspection, thermal); excluded by default in most standard wordings and requires specific endorsement
• BVLOS endorsement — if the operator holds or intends to apply for a BVLOS OA from the CAA
• Autonomous operations clause — confirming cover is not voided when the aircraft executes a pre-programmed mission without continuous pilot input
• Wear-and-tear and firmware exclusion acknowledgement — operators should understand these are standard exclusions and plan maintenance budgets accordingly
• Ground equipment and accessories — GCS, RTK base stations, spare batteries
• Grounding extension — costs incurred if the CAA or a third party grounds the aircraft pending investigation

Broker Submission: Document Checklist and Turnaround

Specialist MGA placement for Autel EVO insurance differs from standard commercial lines in one important respect: the underwriter needs operational context, not just asset values. A complete submission binds faster and at better terms than a bare asset schedule. For Specific Category risks where the operator provides a complete SORA with SAIL clearly stated and a copy of the current OA, specialist MGAs can typically indicate terms within the same day to 48 hours. Incomplete submissions — missing OA references, undeclared payload configurations, or absent pilot competency evidence — extend the process and may result in restrictive terms.

Brokers should gather the following before approaching the market:

Renewal is the point at which coverage gaps most often emerge. If the operator has added payload configurations, obtained a new OA, begun BVLOS trials, or changed primary operating environment since the last renewal, those changes are material facts that must be disclosed. A specialist MGA will prompt for these at renewal; a generalist insurer may not, leaving the operator exposed.

• Aircraft serial number and declared all-up weight per configuration (airframe, battery, payload)
• CAA Operator ID number — must be displayed on the aircraft; required at submission
• CAA Flyer ID for each remote pilot — commercial operators need both Operator ID and Flyer ID; these are distinct credentials issued separately by the CAA
• A2 CofC certificate reference for Open Category A2 operations, or GVC certificate reference for Specific Category
• OA reference number and expiry date, or PDRA reference if applicable
• SORA document with SAIL clearly stated, for Specific Category risks not covered by a PDRA
• Annual flight hours or cycles per aircraft
• Primary operating environments (urban, rural, coastal, congested areas)
• Claims history on prior drone policies

Fleet Programmes and Multi-Aircraft Scheduling

Survey companies and inspection contractors frequently operate mixed fleets that include multiple EVO II units alongside aircraft from other manufacturers. A fleet policy consolidates hull and liability into a single programme, typically with a blanket limit structure rather than per-aircraft scheduling. Premium cost shape scales with hull value, operating environment, pilot experience across the team, and the proportion of BVLOS or autonomous missions in the programme — accurate asset registers and mission logs are the most effective tools for managing renewal costs.

Adding or removing aircraft mid-term is straightforward on a properly structured fleet programme — the MGA issues an endorsement adjusting the schedule and pro-rates the premium accordingly. Operators who fail to notify mid-term additions risk flying uninsured hull value and, more critically, operating without the liability cover required by their OA conditions.

For brokers placing fleet risks, the underwriting submission should include a current asset register with serial numbers and declared values per configuration, a copy of each relevant CAA OA or Open Category declaration, a description of primary mission types, and details of any BVLOS or autonomous operations planned in the policy period. Where the fleet spans multiple SAIL levels — for example, some aircraft operating under a PDRA and others under a bespoke SORA — each OA should be listed separately.

Frequently asked questions

Does standard commercial drone insurance automatically cover all Autel EVO payload configurations?

Not automatically. Many policies schedule the insured aircraft by serial number and declared value at inception. If you swap to a higher-value thermal or multispectral sensor after the policy starts, that payload may not be covered unless you notify the insurer and obtain an endorsement. Always declare each payload configuration separately and confirm the policy wording covers interchangeable sensor systems. Payload data liability — claims arising from errors in the data the sensor produces — is a separate coverage question and is typically excluded unless specifically endorsed.

Which Autel EVO variants require a CAA Specific Category Operational Authorisation?

The requirement depends on the mission profile, not solely the aircraft model. EVO II Pro and EVO II Enterprise operations over uninvolved persons, in congested areas, or beyond visual line of sight will typically require a Specific Category OA. The standard competency qualification for Specific Category OA applications is the General VLOS Certificate (GVC). For common mission profiles, a Pre-Defined Risk Assessment (PDRA) may provide a faster route to an OA than a bespoke SORA. Lighter variants such as the EVO Lite may remain in Open Category A2 for many commercial missions, requiring an A2 Certificate of Competency rather than a GVC. Confirm your specific scenario with a CAA-recognised competency assessor before flying.

What is a SAIL and why do underwriters ask for it?

SAIL stands for Specific Assurance and Integrity Level, expressed as a Roman numeral from I to VI. It is the output of the SORA (Specific Operations Risk Assessment) process required for Specific Category OA applications. The SAIL determines the robustness of operational safety objectives the operator must demonstrate to the CAA. Underwriters use the SAIL to assess the risk profile of the operation: a higher SAIL indicates more complex mitigations are required, which affects how the risk is priced and what endorsements may be needed. Submitting your SORA with the SAIL clearly stated is one of the most effective ways to accelerate the binding process.

What documents does an underwriter need to bind Autel EVO insurance?

At minimum: the aircraft serial number and declared all-up weight per configuration, your CAA Operator ID number (which must also be displayed on the aircraft) and each pilot's Flyer ID, a copy of your Operational Authorisation or PDRA reference, your GVC or A2 CofC certificate reference as applicable, a description of primary mission types and operating environments, and any prior claims history. For Specific Category risks, include the SORA document with SAIL clearly stated. Complete submissions from specialist brokers typically receive indicative terms from an MGA within the same day to 48 hours; incomplete submissions take longer and may attract restrictive conditions.

Is BVLOS cover included as standard, or does it require a separate endorsement?

BVLOS operations are excluded from most standard drone policies and require a specific endorsement. The endorsement will typically reference your CAA BVLOS OA, restrict cover to the geographic area and mission profile described in that authorisation, and may carry a higher deductible than VLOS operations. Do not assume BVLOS cover is in place until you have written confirmation from the insurer.

What triggers a coverage gap at renewal for commercial EVO operators?

The most common triggers are: failure to disclose a new payload configuration or increased declared value; an expired or lapsed CAA OA that was not renewed before the policy anniversary; commencement of BVLOS or autonomous operations without a policy endorsement; changes to primary operating environment such as moving from rural survey work to urban infrastructure inspection; and changes to the pilot team that affect the competency evidence on file. Each of these is a material fact. Disclose changes to your broker before the renewal date, not after a claim arises.