GCAA Class 1A 1B 1C Drone Insurance UAE

Class 1A / 1B / 1C and the GCAA CAR-RPAS Framework: Reconciling the Terminology

The 'Class 1A, 1B, 1C' labels circulating in the UAE drone market do not correspond to a defined sub-classification table in the current published CAR-RPAS text. Brokers should verify directly against the current CAR-RPAS document whether any official sub-class designations exist, as regulatory amendments are issued periodically and the GCAA may introduce or formalise sub-classifications in future revisions. Until such designations are confirmed in a published CAR-RPAS article, underwriters will assess risk and bind policies against the official three-tier Open / Specific / Certified framework—the classification that appears on Operational Authorisation letters and GCAA registration records.

For practical broker purposes, the informal '1A / 1B / 1C' labels can be treated as approximate proxies: Class 1A broadly corresponds to lower-risk Open category operations; Class 1B to higher-complexity Open or lower-risk Specific operations; Class 1C to Specific or Certified operations involving BVLOS, higher MTOW, or flight over populated areas. However, the insurer will always underwrite against the GCAA-issued category, not the informal label. A policy bound on a '1B' description that does not match the operator's actual GCAA Operational Authorisation category creates a material misrepresentation risk. Brokers must confirm the operator's GCAA-issued category before quoting and ensure the policy schedule references the CAR-RPAS category explicitly.

GCAA CAR-RPAS Thresholds: Regulatory Triggers for Underwriting

CAR-RPAS establishes a maximum take-off weight ceiling for Open category operations. Brokers should verify this threshold directly against the current CAR-RPAS Part and section that defines Open category eligibility—the GCAA publishes CAR-RPAS on its official website and updates it periodically. Aircraft approaching the Open category MTOW ceiling should be weighed with all payload attached, because payload mass counts toward MTOW for both regulatory and underwriting purposes. Any aircraft exceeding the Open category MTOW ceiling requires a Specific or Certified Operational Authorisation before commercial flight.

CAR-RPAS also establishes a maximum operating altitude for Open category VLOS operations. Brokers should verify this altitude ceiling directly against the specific CAR-RPAS Part and section that defines Open category altitude limits, as the GCAA figure may differ from thresholds published by other regulators such as EASA or the FAA. Exceeding the Open category altitude ceiling in VLOS, or conducting any BVLOS operation regardless of altitude, moves the operation into Specific category territory and requires a GCAA Operational Authorisation. Altitude is an underwriting trigger because it correlates directly with airspace conflict risk and recovery difficulty.

Proximity to people and populated areas is the third threshold separating Open from Specific category. CAR-RPAS restricts Open category operations from flight over assemblies of people and imposes minimum separation distances from uninvolved persons. Operations requiring flight over crowds, dense urban areas, or within the controlled airspace of Dubai or Abu Dhabi airports require Specific or Certified authorisation. Underwriters treat proximity-to-people exposure as a direct multiplier on third-party liability limits. Brokers should cite the relevant CAR-RPAS Part and section when confirming these thresholds with operators, so that both parties are working from the same verified regulatory text.

• MTOW at or below the CAR-RPAS Open category ceiling (verify current figure in the relevant CAR-RPAS Part): Open category eligible
• MTOW above the Open category ceiling: Specific or Certified OA required
• Altitude at or below the CAR-RPAS Open category VLOS ceiling (verify current figure in the relevant CAR-RPAS Part), VLOS: Open category eligible
• Altitude above the Open category ceiling or any BVLOS mode: Specific OA required
• Flight over assemblies of people or in controlled airspace: Specific or Certified OA required

Open Category: Coverage Scope, Eligibility, and DCAA Overlay

Open category operations—MTOW within the CAR-RPAS ceiling, VLOS, within the approved altitude limit, clear of assemblies of people—carry the lowest third-party risk profile in the UAE RPAS framework. Insurance for this category is structured around hull coverage for aircraft loss or damage and third-party liability for property damage or bodily injury to uninvolved parties. CAR-RPAS mandates a minimum third-party liability limit for commercial RPAS operators; brokers must verify the current mandated minimum by consulting the specific CAR-RPAS article that sets this requirement, as this figure establishes the compliance floor below which no policy may be bound. The GCAA publishes CAR-RPAS on its official website and the relevant article should be cited in the broker's submission notes.

Eligibility for Open category placement requires: confirmed GCAA operator registration via the DroneZone portal; proof that the aircraft MTOW does not exceed the Open category ceiling with payload attached; a valid GCAA Remote Pilot Licence (RPL) at the level required for the aircraft weight sub-class as defined in CAR-RPAS; and a flight plan that does not exceed the approved altitude ceiling or enter controlled airspace without a GCAA No Objection Certificate. Premium for Open category scales with hull value, payload type, and frequency of commercial operations—a high-frequency survey operator flying a platform near the MTOW ceiling daily presents a materially different risk than an occasional inspection operator flying a lighter aircraft.

Operators based in Dubai must satisfy both GCAA CAR-RPAS requirements and DCAA requirements for operations within Dubai airspace. The DCAA operates as the emirate-level civil aviation authority for Dubai and may impose additional registration, notification, or operational approval steps beyond those required by GCAA. Brokers placing cover for Dubai-based operators should confirm with the operator whether DCAA approval has been obtained in addition to GCAA registration, and should note any DCAA conditions in the underwriting submission. Failure to hold required DCAA approvals alongside GCAA authorisation may affect coverage validity for Dubai operations.

Operators must register their aircraft and operator entity through the GCAA's official online drone registration and authorisation portal. The GCAA refers to this portal as DroneZone in its official communications; brokers should verify the current portal URL directly at gcaa.gov.ae, as portal addresses can change with system updates. DroneZone is the single GCAA submission channel for operator registration, aircraft registration, and Operational Authorisation applications. Brokers should ask operators to provide their DroneZone registration reference as part of every underwriting submission.

Specific Category: Elevated Thresholds, BVLOS, and OA Requirements

Specific category covers operations that exceed one or more Open category parameters: MTOW above the CAR-RPAS Open category ceiling, altitude above the approved VLOS limit, BVLOS mode, or flight in proximity to populated areas or controlled airspace. Each of these factors increases accident probability and third-party exposure, which is why GCAA requires a formal Operational Authorisation before any Specific category commercial flight. The OA application is submitted through DroneZone and must include a risk mitigation plan, crew qualification records, aircraft specifications, maintenance procedures, and a detailed description of the intended operational scope.

GCAA CAR-RPAS requires Specific category remote pilots to hold a GCAA Remote Pilot Licence at the tier appropriate to the operation. CAR-RPAS defines RPL tier designations—brokers should verify the exact tier names or category designations as they appear in the current CAR-RPAS text, rather than relying on generic descriptions, to ensure the pilot's licence record matches the regulatory requirement for the intended operation. For BVLOS operations, the operator must additionally demonstrate real-time ground monitoring capability, approved contingency and emergency procedures, and compliance with GCAA-specified operational boundaries. Underwriters require a copy of the GCAA OA approval letter before binding; the letter specifies the approved category, altitude ceiling, operational area, and any conditions. Any operation outside the approved scope is uninsured.

For operations in or near controlled airspace—including the airspace around Dubai International Airport, Abu Dhabi International Airport, and other controlled zones—the operator must obtain a No Objection Certificate (NOC) from the relevant authority before flight. For Dubai airspace, the NOC process involves both GCAA and DCAA; operators should confirm the current NOC application channel with both authorities, as the process may be managed through DroneZone, through DCAA's own portal, or through direct coordination with air traffic control depending on the airspace class and operation type. Brokers should include the NOC reference in the underwriting submission for any Specific category operation in or near controlled airspace.

Brokers should not accept a submission that presents an OA application as a substitute for an OA approval letter. A policy cannot be bound for Specific category operations until the GCAA OA is issued. Operators should be advised to submit OA applications well in advance of intended operations; the GCAA does not publish a fixed processing timeline on its public-facing pages, so operators should contact the GCAA directly for current processing expectations rather than relying on third-party estimates. Liability limits for Specific category are higher than Open category because the third-party exposure is greater, and premiums scale with MTOW, operational altitude, BVLOS exposure, proximity to populated areas, and the operator's claims history.

Certified Category: Airworthiness, Autonomous Ops, and Specialist Placement

Certified category encompasses the highest-risk RPAS operations under CAR-RPAS: autonomous flight, operations requiring full airworthiness certification, flight over populated areas at scale, or operations that exceed Specific category parameters. GCAA Certified category requires a comprehensive OA application including a full safety case, airworthiness documentation, crew licensing records at the highest GCAA RPL tier as defined in CAR-RPAS, and detailed operational procedures. The GCAA conducts a thorough technical review and may request additional information before issuing approval.

Insurance for Certified category is placed on a case-by-case basis. Underwriters conduct detailed reviews of the operator's safety management system, crew qualifications, maintenance protocols, and contingency procedures. Liability limits are negotiated to reflect the specific mission profile and third-party exposure; hull limits are tied to the certified aircraft's replacement value. Exclusions are tailored to the approved operational scope and may address specific airspace, weather minima, or monitoring requirements. Brokers should expect longer underwriting timelines and must provide technical documentation—safety case summaries, crew CVs, maintenance records, and flight-test data where available—to support placement.

Certified category placement almost always requires specialist underwriters with experience in advanced air mobility or industrial RPAS programmes. Brokers should identify specialist carriers early and engage them during the GCAA OA application process, not after approval, so that underwriting review and OA review can proceed in parallel. This parallel-track approach reduces the gap between OA approval and policy binding, which is critical for operators with fixed project start dates. For Dubai-based Certified category operations, DCAA involvement should be confirmed at the outset, as emirate-level requirements may add procedural steps to both the regulatory and underwriting timelines.

Broker Workflow: Document Checklist and Submission Steps

Confirm the operator's GCAA category before any other step. Ask for the operator's DroneZone registration reference, the aircraft MTOW with maximum payload, the intended operating altitude, and whether any operations are BVLOS or over populated areas. For Dubai-based operators, also confirm whether DCAA approval has been obtained. These data points determine category and direct the rest of the submission.

Compile the underwriting document pack aligned to category. Open category requires: DroneZone operator and aircraft registration confirmation; proof of GCAA Remote Pilot Licence or recognised qualification at the tier required by CAR-RPAS for the aircraft weight sub-class; aircraft specifications including MTOW with payload; description of operational scope including altitude, airspace, VLOS mode, and mission type; and, where applicable, DCAA approval confirmation for Dubai operations. Specific and Certified categories require all of the above plus: GCAA Operational Authorisation approval letter specifying category and approved parameters; risk mitigation plan or safety case summary; maintenance records or maintenance plan; crew CVs and licence records at the CAR-RPAS-specified RPL tier; and GCAA NOC (and DCAA NOC where applicable) if operations are in or near controlled airspace.

Select underwriters with appetite for the confirmed category and mission type. Open category programmes are available from a broad range of carriers. Specific category may require specialist placement depending on BVLOS exposure and proximity to controlled airspace. Certified category requires specialist underwriters. Structure the proposal to highlight risk mitigation: crew qualifications, maintenance schedules, safety procedures, and GCAA approval status. Monitor for mid-policy category upgrades—if the operator later obtains a higher-category OA, notify the insurer immediately and request policy amendment or new quotation to avoid coverage gaps.

• Step 1: Confirm GCAA category via DroneZone registration reference and OA letter
• Step 2: Verify MTOW with payload against the Open category ceiling in the relevant CAR-RPAS Part
• Step 3: Confirm operating altitude against the Open category VLOS ceiling in the relevant CAR-RPAS Part
• Step 4: Identify BVLOS, populated-area, or controlled-airspace exposure
• Step 5: For Dubai operations, confirm DCAA approval status alongside GCAA registration
• Step 6: Compile document pack aligned to category including NOC references where required
• Step 7: Select carrier tier (standard market / specialist) matched to category
• Step 8: Submit proposal with GCAA documentation, DCAA documentation if applicable, and mission description
• Step 9: Notify insurer of any mid-policy category upgrade immediately

Frequently asked questions

Does GCAA use 'Class 1A, 1B, 1C' as official regulatory categories?

These sub-class labels do not appear as defined designations in the current published CAR-RPAS text. Brokers should verify directly against the current CAR-RPAS document whether any official sub-class designations exist, as the GCAA issues amendments periodically. The operative classification that underwriters apply is the three-tier Open / Specific / Certified framework, which is the structure that appears on GCAA Operational Authorisation letters and registration records.

How do I verify the MTOW and altitude thresholds that separate Open from Specific category?

Consult the current CAR-RPAS document published on the GCAA's official website (gcaa.gov.ae) and locate the Part and section that defines Open category eligibility criteria. The GCAA updates CAR-RPAS periodically, so brokers should check the current version rather than relying on third-party summaries. Cite the specific CAR-RPAS Part and section in your underwriting submission notes so both the operator and underwriter are working from the same verified regulatory text.

What documents must a broker obtain before binding a Specific category policy?

At minimum: the operator's GCAA Operational Authorisation approval letter from DroneZone, DroneZone operator and aircraft registration confirmation, proof of the remote pilot's GCAA Remote Pilot Licence at the tier required by CAR-RPAS for the operation type, a description of the approved operational scope including altitude and BVLOS status, and a GCAA NOC (and DCAA NOC where applicable) for any operations in or near controlled airspace. A policy cannot be bound on the basis of an OA application alone — the approval letter must be in hand.

Where do operators register and submit Operational Authorisation applications in the UAE?

Through DroneZone, the GCAA's official online drone registration and authorisation portal. Brokers should verify the current portal URL directly at gcaa.gov.ae, as portal addresses can change with system updates. DroneZone handles operator registration, aircraft registration, and OA applications. Brokers should request the operator's DroneZone reference number as a standard part of every underwriting submission.

Do Dubai-based operators need approvals beyond GCAA CAR-RPAS?

Yes. The Dubai Civil Aviation Authority (DCAA) is the emirate-level civil aviation authority for Dubai and imposes additional requirements for operations within Dubai airspace, layered on top of GCAA CAR-RPAS obligations. Operators must confirm whether DCAA registration, notification, or operational approval is required for their specific mission, and brokers should include DCAA approval documentation in the underwriting submission for any Dubai-based operation. For controlled airspace operations in Dubai, a NOC may be required from both GCAA and DCAA.

What is the GCAA-mandated minimum third-party liability limit for commercial RPAS?

CAR-RPAS mandates a minimum third-party liability limit for commercial RPAS operators, and no compliant policy may be bound below this floor. Brokers must verify the current mandated minimum by consulting the specific CAR-RPAS article that sets this requirement, as the figure is subject to regulatory revision. The GCAA publishes CAR-RPAS on its official website; the relevant article should be cited in the broker's submission notes to confirm the compliance floor applied to the placement.