Drone Insurance Additional Insured Endorsement GCC Projects

What an Additional Insured Endorsement Actually Does on a Drone Policy

An additional insured (AI) endorsement extends the liability section of your drone insurance policy to protect a named third party — typically a project owner, joint-venture entity, or government authority — against claims arising from your drone operations. It is not a separate policy; it is a contractual amendment to yours. The additional insured gains the right to be defended and indemnified under your policy limits, but only within the scope of your own covered operations.

On a drone-specific programme, the endorsement must be drafted to reflect the operational scope filed with the GCAA. The UAE's General Civil Aviation Authority regulates commercial UAS operations under a risk-classification framework derived from SORA (Specific Operations Risk Assessment) principles. The GCAA publishes its own operational category labels — operators and brokers should reference GCAA terminology directly in submissions rather than mapping to any other regulatory framework. If your approved scope covers VLOS operations over a construction site, the AI endorsement cannot silently extend cover to BVLOS sorties or night operations unless those categories are already on your GCAA operational authorisation and reflected in the policy schedule.

A poorly worded AI endorsement — one copied from a general-liability template — will often grant the additional insured broader rights than the named insured actually holds. Underwriters in the specialty drone market will push back on 'blanket additional insured' language that does not tie the extension to a specific project, location, or operational category. Brokers should expect to provide the underlying contract or at minimum a scope-of-work summary at endorsement stage.

GCC Contract Structures and Why They Drive Endorsement Complexity

Major GCC infrastructure programmes — oil and gas inspection in Abu Dhabi, utility corridor surveys in Saudi Arabia, smart-city construction in Qatar — typically operate under multi-tier contracting structures. A drone operator may be engaged by a specialist survey subcontractor, who sits under a Tier-1 EPC contractor, who is contracted to a government-linked project owner. Each tier commonly requires the drone operator's policy to name entities above them in the chain as additional insureds.

This creates a cascade of AI requests, sometimes arriving in sequence as the operator moves up the approval chain. Underwriters will want to see the full contractual hierarchy before agreeing to endorse multiple parties, because each additional insured added to a liability policy is a potential claimant against that same policy. Where the project involves a UAE federal authority or an Abu Dhabi or Dubai government entity, the endorsement wording may also need to satisfy that authority's own insurance specifications, which can differ from standard market language.

Cross-border GCC projects add a further layer. An operator based in the UAE conducting surveys in Saudi Arabia operates under GACA (General Authority of Civil Aviation, KSA) jurisdiction for the flight itself, while the policy may be placed in the UAE market. Similarly, operations in Qatar fall under QCAA (Qatar Civil Aviation Authority). Both GACA and QCAA require UAE-based operators to obtain a separate local operational permit before conducting commercial flights in their respective jurisdictions — operators should apply directly through each authority's official permit portal and allow sufficient lead time, as permit processing sits outside the insurance placement timeline. Brokers must confirm with underwriters that the territorial scope of the policy — and therefore the AI endorsement — covers operations in the relevant GCC state, and that the liability limit currency is acceptable to the contracting party.

GCAA Compliance, Risk Categories, and Regulatory Triggers for Endorsement

The GCAA's UAS regulatory framework requires commercial operators to hold third-party liability insurance as a condition of their operational authorisation. The GCAA publishes minimum third-party liability thresholds tied to the aircraft's maximum take-off mass (MTOM). For sub-25 kg commercial VLOS operations, the GCAA specifies a minimum third-party liability limit expressed in AED — operators and brokers should verify the current published figure directly in the GCAA UAS regulations, as thresholds are subject to regulatory revision. Limits are quoted in AED or USD depending on the insurer and the contract requirement.

The GCAA formally distinguishes between VLOS and BVLOS operational authorisations as separate permit classes. A BVLOS authorisation requires a distinct application, a more detailed risk assessment, and typically carries a higher minimum liability threshold than an equivalent VLOS operation at the same MTOM. This distinction is operationally significant for AI endorsements: an endorsement issued against a VLOS authorisation does not automatically extend to BVLOS sorties. If a project scope evolves to require BVLOS flights — for example, a long-linear pipeline inspection — the operator must obtain a revised GCAA authorisation before the AI endorsement can be updated to reflect that expanded scope.

Operators working on projects near UAE aerodromes or within restricted airspace will have additional GCAA permit conditions. Those conditions should be referenced in the policy schedule so that the AI endorsement is clearly bounded by them. Failure to align the endorsement with the permit conditions is one of the most common grounds for a coverage dispute when a claim arises on a GCC project site.

Broker Submission Checklist and Cost-Shape Factors

Specialty drone underwriters in the UAE and London markets require a defined set of documents before issuing an AI endorsement on a GCC project programme. The following is the standard submission checklist brokers should assemble before approaching underwriters. Submissions should be directed to the underwriter's dedicated UAS or aviation liability team — confirm the correct submission channel with your underwriting contact, as routing to a general inbox consistently extends turnaround times.

Once the checklist documents are in hand, underwriters will assess whether the AI request requires a premium adjustment. Several factors materially shape the cost of an AI endorsement and brokers should be prepared to discuss each with the underwriter: the number of named AI parties (each additional party increases aggregate exposure); whether the contract requires primary-and-non-contributory wording (a material change to the contribution clause that underwriters price separately); whether a waiver of subrogation is requested (particularly significant where the AI party's own ground operations could contribute to a drone incident); the BVLOS uplift where the authorisation covers beyond-visual-line-of-sight operations; and whether a cross-border territorial extension is needed to cover operations in Saudi Arabia, Qatar, or another GCC state. A single named project owner on a bounded VLOS infrastructure survey carries a different exposure profile than a multi-party, BVLOS-enabled, cross-border endorsement — and premium will reflect that difference accordingly.

Deductibles on AI-endorsed policies typically remain the responsibility of the named insured, not the additional insured, but this should be confirmed in the endorsement wording. Turnaround times vary with documentation completeness and underwriter capacity — brokers who submit AI requests without the underlying contract or scope of work consistently experience the longest delays. Multi-party endorsements on new programmes, or those involving government authorities with bespoke wording requirements, should be allowed a longer lead time than straightforward single-party extensions on existing in-force policies.

• 1. A copy of the relevant contract clause or insurance specification that triggers the AI requirement
• 2. The full legal name and jurisdiction of each entity to be added as an additional insured
• 3. The project name, location (including emirate or GCC state), and operational period
• 4. The operator's current GCAA operational authorisation — specifying whether it covers VLOS, BVLOS, or both — or the equivalent permit issued by GACA or QCAA for cross-border operations
• 5. A description of the UAS equipment to be used, MTOM of each aircraft type, and the operational categories as defined in the GCAA authorisation
• 6. Confirmation of the liability limit required by the contract, the currency in which it must be expressed, and whether primary-and-non-contributory wording or a waiver of subrogation is required

Certificate of Insurance and Wording Pitfalls to Avoid

The certificate of insurance (COI) issued to the additional insured is not the endorsement itself — it is evidence that the endorsement exists. Brokers should ensure the COI accurately references the endorsement number and does not contain language that expands or restricts cover beyond what the endorsement actually grants. In the GCC market, project owners and government authorities frequently request certificates that include 'primary and non-contributory' language, meaning your client's policy responds first before any insurance held by the additional insured.

Primary and non-contributory wording is a significant underwriting consideration. Not all drone liability policies are structured to accommodate it, and adding it mid-term can affect the policy's relationship with any excess or umbrella layers. Brokers should raise this requirement at inception, not at the certificate-request stage.

Another common pitfall is the 'waiver of subrogation' request, which often accompanies AI endorsements on GCC construction projects. A waiver of subrogation prevents your insurer from recovering against the additional insured after paying a claim. Underwriters will assess this against the overall risk profile of the programme. Where the additional insured is also the entity most likely to cause or contribute to a drone incident — for example, a main contractor whose ground crews operate near the flight zone — underwriters may decline the waiver or price it accordingly.

Broker Workflow: Placing AI Endorsements Efficiently on GCC Drone Programmes

The most efficient placements start with a pre-submission conversation between the broker and the underwriter before the operator signs the project contract. At that stage, the AI requirements are often still negotiable, and the broker can flag any wording that the drone insurance market is unlikely to accept — saving the operator from committing to contractual insurance obligations that cannot be fulfilled.

For fleet operators running multiple concurrent GCC projects, a master policy with project-specific endorsement schedules is generally more efficient than placing individual policies per project. The master policy establishes the core hull and liability terms; each project endorsement then layers on the AI parties, territorial scope, and any project-specific limit requirements. This structure also simplifies GCAA compliance documentation, since the operator maintains a single authorisation file that references the master policy.

Brokers should maintain a tracker of AI endorsement expiry dates, particularly on long-duration infrastructure projects where the drone operational period may extend beyond the annual policy term. An AI endorsement that lapses mid-project because the policy renewed without carrying forward the endorsement is a common and avoidable error. Renewal instructions should explicitly confirm which AI endorsements are to be maintained.

Frequently asked questions

Does an additional insured endorsement on a UAE drone policy cover liability arising anywhere in the GCC?

Not automatically. The territorial scope of the underlying policy governs where cover applies. If your GCAA-authorised operations extend into Saudi Arabia or Qatar, the policy's territorial clause must explicitly include those jurisdictions, and the AI endorsement inherits that scope. Additionally, both GACA in Saudi Arabia and QCAA in Qatar require UAE-based operators to hold a separate local operational permit before conducting commercial flights in their territory — this is a regulatory requirement independent of the insurance placement. Brokers should confirm territorial coverage with the underwriter and verify local permit status before the operator mobilises cross-border.

What GCAA operational categories are relevant when scoping an AI endorsement?

The GCAA publishes its own operational category labels under its SORA-derived UAS framework, and brokers should reference those labels directly in submissions rather than using terminology from other regulatory systems. Critically, the GCAA treats VLOS and BVLOS as distinct authorisation classes — a BVLOS permit requires a separate application and risk assessment. An AI endorsement issued against a VLOS authorisation does not extend to BVLOS operations. If a project scope requires BVLOS flights, the operator must hold the appropriate GCAA BVLOS authorisation before the endorsement can reflect that scope, and the premium will be assessed accordingly.

Can a government authority or Abu Dhabi/Dubai entity be named as an additional insured on a commercial drone policy?

Yes, and it is common on UAE infrastructure and smart-city projects. However, government and quasi-government entities often have their own insurance specifications that require specific wording, minimum limits expressed in AED or USD, and sometimes a waiver of subrogation in their favour. Brokers should obtain the authority's insurance requirements document early in the placement process, as bespoke wording requests can extend endorsement turnaround times and may require underwriter sign-off at a senior level.

At what point in the GCAA authorisation process should an operator arrange the AI endorsement?

The AI endorsement should be arranged before the operator submits the final insurance certificate to the project owner or main contractor, and ideally before the GCAA operational authorisation is finalised for the specific project. This is because the GCAA authorisation defines the operational scope — VLOS or BVLOS, risk class, geographic boundaries — and the AI endorsement must be consistent with that scope. Arranging the endorsement after the authorisation is issued but before mobilisation is the standard workflow; arranging it after mobilisation has begun creates a coverage gap.

How does 'primary and non-contributory' language affect a drone liability policy placed in the UAE market?

Primary and non-contributory wording means the drone operator's policy responds first to a covered claim, without seeking contribution from any insurance held by the additional insured. This is a material change to the policy's contribution clause and must be agreed by the underwriter — it cannot be added unilaterally on a certificate. It affects how the policy interacts with any excess or umbrella layers the operator holds, and underwriters will assess it against the overall exposure of the programme. Brokers should raise this requirement at inception or at the earliest possible stage of the placement.

What eligibility criteria do underwriters apply before agreeing to add multiple additional insureds on a GCC drone programme?

Underwriters will assess the operator's GCAA authorisation status and operational track record, the nature and risk profile of each project, the contractual relationship between the named insured and each AI party, and whether any AI party's own activities could contribute to a drone-related loss. Operators with a current GCAA operational authorisation, documented safety management procedures, and a clean claims history will generally find AI endorsements straightforward to place. Operators seeking blanket AI coverage across an undefined client list, or those with unresolved claims, will face more scrutiny and may be asked to provide additional risk information before endorsements are bound.