Drone Insurance Certificate of Insurance: Dubai Municipality Requirements

Why Dubai Municipality Requires a COI — and What Triggers the Obligation

Dubai Municipality acts as the permitting authority for drone operations conducted over or near municipal assets, public spaces, construction sites, and infrastructure corridors within its jurisdiction. Before any commercial operator can receive a site-specific access permit or a project-level NOC, the Municipality requires documentary proof that a valid third-party liability insurance policy is in force. A policy schedule alone is not sufficient — the COI must be a standalone, named document that can be verified independently of the full policy wording.

The obligation is layered. At the federal level, the UAE General Civil Aviation Authority (GCAA) mandates that all Remotely Piloted Aircraft Systems (RPAS) operating commercially hold third-party liability coverage as a condition of RPAS operator registration. Dubai Municipality then adds its own site-level requirement on top of that federal baseline, often specifying minimum liability limits, named additional insureds, and notice-of-cancellation clauses that go beyond the GCAA's minimum registration threshold.

Operators who hold a GCAA RPAS Operator Certificate (ROC) but have not structured their COI to meet the Municipality's specific endorsement requirements will still face permit rejection. The two frameworks are complementary, not interchangeable, and your broker must be familiar with both when placing the programme.

What a Compliant COI Must Contain for Dubai Municipality

Dubai Municipality's permit desk typically requires the COI to confirm, at minimum, the named insured (matching the GCAA-registered operator entity exactly), the policy number, the insurer's name and jurisdiction of authorisation, the class of RPAS covered, the territorial scope (UAE, or UAE including international waters where relevant), and the policy period. Any mismatch between the entity name on the COI and the name on the GCAA ROC is a common cause of rejection.

Beyond the core fields, the Municipality frequently requires the COI to name Dubai Municipality — and in some project contexts the site owner or main contractor — as an Additional Insured. This is a material change to the policy structure, not a cosmetic addition to the certificate, and it must be agreed with the insurer in advance. Operators who request this endorsement after binding often face delays because not all insurers will add municipal bodies as additional insureds without underwriting review.

A cancellation notice clause is standard practice: the COI must state that the insurer will provide written notice to the certificate holder (Dubai Municipality or the named project authority) if the policy is cancelled or materially amended before its expiry date. The required notice period varies by project; confirm this with the permitting desk before binding.

• Named insured must match the GCAA ROC entity name exactly
• Insurer must be authorised to write insurance in the UAE (check UAE Insurance Authority / Central Bank of UAE registration)
• Territorial scope must explicitly include the UAE
• Additional Insured endorsement for Dubai Municipality where required by the permit
• Cancellation notice clause with the notice period specified
• Policy period must cover the full duration of the permitted operation, not just the application date
• Class and maximum take-off weight (MTOW) of RPAS must be stated or referenced

GCAA RPAS Risk Classification and Its Effect on Coverage Structure

The GCAA applies a risk-based classification framework to RPAS operations that draws on ICAO's SORA (Specific Operations Risk Assessment) methodology. Operations are assessed across categories that consider MTOW, operational environment (populated vs. unpopulated), BVLOS vs. VLOS, and proximity to controlled airspace. The risk class assigned directly influences the liability limit that an underwriter will consider adequate — and, by extension, the limit that Dubai Municipality may require on the COI.

For operations in the GCAA's higher-risk categories — BVLOS corridors, operations over crowds, or flights near Dubai International Airport's controlled zones — underwriters will typically require a more detailed risk submission before quoting. Hull coverage for higher-value platforms and third-party liability limits both scale with the assessed risk class. Operators should not assume that a COI issued for a lower-risk VLOS operation will satisfy the Municipality's requirements for a more complex project.

Where an operator holds a fleet of RPAS under a single ROC, the policy can be structured on a fleet basis, but the COI issued for a specific project must still reference the specific aircraft type(s) deployed, or confirm that all aircraft under the ROC are covered. A blanket fleet COI that does not identify the relevant aircraft class may be queried by the permit desk.

The Broker Workflow: From Programme Placement to COI Issuance

Commercial drone brokers placing UAE programmes should build the COI requirements into the submission stage, not the post-bind stage. Obtain the Municipality's permit application checklist — or the site owner's insurance schedule — before approaching underwriters. This allows you to present a complete set of COI endorsement requirements to the market and avoid post-bind amendments that delay permit issuance.

The submission to underwriters should include the GCAA ROC number, the operator's operational manual or CONOPS summary, the specific project location and operational parameters (MTOW, VLOS/BVLOS, altitude, proximity to people and infrastructure), and the full list of additional insured and notice requirements from the Municipality or project owner. Underwriters writing UAE RPAS business will expect this level of detail; submissions without it will attract longer turnaround times or declinations.

Once the policy is bound, request the COI in the exact format required by the permit desk. Some Municipality departments and free zone authorities have their own COI templates; if so, the insurer or their UAE-authorised representative must complete that template rather than issuing a standard market certificate. Confirm this requirement before binding — not all insurers will complete third-party templates, and this can be a deal-breaker on time-sensitive projects.

Common Rejection Reasons and How to Avoid Them

The most frequent causes of COI rejection at Dubai Municipality are entity name mismatches, an insurer not registered with the UAE Central Bank or Insurance Authority, a territorial scope that excludes the UAE or is ambiguous, and a missing or incorrectly worded additional insured endorsement. Each of these is avoidable at the placement stage if the broker has the permit checklist in hand before going to market.

Operators sometimes present a COI issued under a policy placed in another jurisdiction — for example, a UK or EU policy covering global operations. While some international insurers do write UAE-territorial coverage, the COI must still confirm UAE territorial scope explicitly, and the insurer must be able to demonstrate authorisation to write insurance in the UAE or be fronted by a locally authorised carrier. A globally worded policy that does not name the UAE is unlikely to satisfy the Municipality's desk.

Expiry timing is a recurring practical issue. If a project runs across a policy renewal date, the operator must either obtain a multi-year policy or provide a renewal COI before the existing one expires. Dubai Municipality will not accept a COI that expires mid-project without a confirmed renewal in place. Build renewal management into the project timeline from the outset.

• Entity name mismatch between COI and GCAA ROC
• Insurer not registered with UAE Central Bank / Insurance Authority
• Territorial scope does not explicitly include UAE
• Additional insured endorsement missing or incorrectly worded
• COI expiry date does not cover full project duration
• Certificate issued on a non-approved template where a specific format is required

Frequently asked questions

Does a GCAA RPAS Operator Certificate automatically satisfy Dubai Municipality's insurance requirement?

No. The GCAA ROC confirms that you hold the required third-party liability coverage at the federal registration level, but Dubai Municipality applies its own site-level COI requirements on top of that baseline. These typically include additional insured endorsements, specific cancellation notice clauses, and sometimes minimum liability limits that go beyond the GCAA's registration threshold. You need both: a GCAA-compliant policy and a COI structured to meet the Municipality's permit conditions.

What classes of RPAS operation are eligible for commercial hull and liability coverage in the UAE?

Most commercial RPAS operations registered under a GCAA ROC are eligible, from light VLOS platforms used for photography and inspection through to heavier BVLOS systems used in infrastructure and logistics. Eligibility and the scope of coverage available will depend on the aircraft's MTOW, the operational environment, whether the operation is VLOS or BVLOS, and the operator's documented safety management and maintenance records. Operations in higher GCAA risk categories require a more detailed underwriting submission but are not automatically uninsurable.

Can an international policy cover UAE operations, or does the insurer need to be UAE-registered?

An international policy can provide UAE-territorial coverage, but the insurer must either be registered with the UAE Central Bank and Insurance Authority or be fronting through a locally authorised carrier. The COI must explicitly state UAE territorial scope. A globally worded certificate that does not name the UAE, or that is issued by an insurer with no UAE authorisation, is likely to be rejected by Dubai Municipality's permit desk and may not satisfy GCAA registration requirements.

How should a broker handle a project where Dubai Municipality requires its own COI template?

Obtain the Municipality's required template before approaching underwriters and include it in your submission. Confirm with the insurer at the quoting stage — not after binding — that they will complete a third-party template. Some insurers will only issue their own standard market certificates; if the Municipality requires a specific format, you need an insurer or their UAE-authorised representative who will comply. Raising this after binding can cause significant delays on time-sensitive permit applications.

What happens to the COI if the policy is cancelled or the operator changes aircraft mid-project?

If the policy is cancelled, the insurer is typically required under the COI's cancellation notice clause to notify Dubai Municipality or the named certificate holder within the agreed notice period. The operator must arrange replacement coverage immediately to avoid permit suspension. If the operator deploys a different aircraft class not referenced on the original COI, a revised or supplementary COI confirming coverage for the new aircraft should be obtained before that aircraft is used on the permitted site.

What information does a broker need from the operator to place a UAE RPAS programme efficiently?

A complete submission should include the GCAA ROC number and registered entity name, the aircraft inventory with MTOW for each type, a summary of planned operations (VLOS or BVLOS, operational environment, proximity to people and infrastructure), the specific project location and duration, and the full COI requirements from Dubai Municipality or the project owner including any additional insured and notice-of-cancellation specifications. Submissions with this information in hand at the outset receive faster turnaround and more accurate terms from underwriters.