Does PDRA-02 Require Third Party Liability Insurance?

PDRA-02 Within the UK Specific Category Framework

The UK Civil Aviation Authority divides drone operations into three categories: Open, Specific, and Certified. PDRA-02 sits firmly in the Specific category. Unlike Open category flights, which carry no mandatory insurance requirement under CAA rules (though EU-derived liability principles still apply), Specific category operations require the operator to hold a valid Operational Authorisation — and insurance is a documented condition of that authorisation.

PDRA-02 is designed for beyond visual line of sight (BVLOS) operations conducted over controlled ground areas with low population density. The risk profile is materially higher than standard VLOS commercial work: the aircraft is further from the remote pilot, ground risk buffers are narrower, and third party exposure — to persons, property, and other airspace users — is correspondingly elevated.

Because PDRA-02 uses a pre-defined risk assessment rather than a bespoke SORA, the CAA has already determined the residual risk level. Operators benefit from a streamlined authorisation route, but they must still satisfy each operational safety objective, and adequate third party liability cover is one of those objectives that must be evidenced at application stage.

What the CAA Requires: Third Party Liability Under PDRA-02

The CAA's Operational Authorisation process for Specific category operations, including PDRA-02, requires operators to demonstrate that they hold third party liability insurance appropriate to the operation. This is not a soft recommendation — it is a hard prerequisite. An operator submitting an Operational Authorisation application without evidence of compliant insurance will not receive approval.

The liability cover must respond to third party bodily injury and property damage arising from the UAS operation. For PDRA-02 specifically, the insurer must be comfortable underwriting BVLOS exposure, which means standard hobby or Open category policies are almost always inadequate. The policy wording needs to explicitly cover BVLOS operations and should not contain exclusions that would void cover the moment the aircraft passes beyond the remote pilot's unaided visual line of sight.

Limits are quoted in GBP and must be proportionate to the risk. The CAA does not prescribe a single minimum limit for PDRA-02 in the way that EU Regulation 2019/947 (as retained in UK law) sets out liability minima by maximum take-off mass — but the operator's risk assessment and the insurer's underwriting must align. Brokers should ensure the limit of indemnity reflects the operational environment, the aircraft's maximum take-off mass, and the nature of the payload being carried.

• Cover must explicitly include BVLOS operations — check the policy schedule and wording, not just the certificate.
• Third party bodily injury and property damage must both be covered within a single limit or clearly separated sub-limits.
• The policy must be in force for the entire duration of the Operational Authorisation period, not just individual flight days.
• Any endorsements or conditions that restrict autonomous or automated flight modes should be reviewed if the PDRA-02 operation uses automated flight planning.

Hull Cover and PDRA-02: Separate but Linked

Third party liability is the regulatory trigger, but most commercial operators running PDRA-02 programmes also carry hull insurance. The aircraft used for BVLOS operations tend to be higher-value platforms — often purpose-built fixed-wing or hybrid VTOL aircraft — and the cost of a hull loss in a remote area, including recovery and data loss, can be significant.

Hull and liability are typically placed together on a combined UAS policy, which simplifies the Operational Authorisation evidence pack. Premiums scale with hull value and BVLOS exposure; deductibles typically rise on autonomous operations where the remote pilot has reduced ability to intervene. Brokers should discuss the operator's contingency procedures — what happens if the datalink is lost — because insurers will ask, and a well-documented lost-link procedure materially affects underwriting appetite.

Where an operator runs a mixed fleet — some aircraft on PDRA-02 authorisations, others on standard VLOS Operational Authorisations — the fleet policy must be structured so that each aircraft's cover matches its specific authorisation type. A blanket VLOS policy will not extend to BVLOS exposures without explicit endorsement.

Broker Workflow: Placing PDRA-02 Cover Correctly

Brokers placing PDRA-02 programmes should gather the operator's draft or approved Operational Authorisation, the operations manual, and the aircraft's airworthiness documentation before approaching the market. Underwriters in the specialty UAS space will want to see the operational risk assessment, the ground risk buffer methodology, and the emergency response procedures. The more complete the submission, the faster the indicative terms.

The policy inception date must precede the Operational Authorisation start date. CAA reviewers will check the insurance certificate date, and a policy that starts after the authorisation period opens creates a compliance gap. Brokers should build a renewal calendar that accounts for the CAA's authorisation renewal cycle, which does not always align with standard annual insurance renewal dates.

Certificates of insurance for PDRA-02 should state the operation type clearly. A generic 'commercial drone operations' certificate may not satisfy a CAA reviewer who is specifically checking for BVLOS cover. Work with the insurer to ensure the certificate wording reflects the authorisation scope — including the geographic area, aircraft type, and BVLOS nature of the operation.

• Submission pack: Operational Authorisation (draft or approved), operations manual, aircraft specs, remote pilot competency evidence.
• Confirm the policy wording contains no BVLOS exclusion and no exclusion for automated flight modes used in the operation.
• Align policy inception and expiry with the Operational Authorisation period.
• Request a certificate that names the operation type and confirms BVLOS cover is included.
• Review annually: PDRA-02 conditions may be updated by the CAA, and policy terms must keep pace.

Regulatory Context: UK Rules Post-Transition

Following the UK's departure from the EU, the CAA retained the substance of EU Regulation 2019/947 and 2019/945 into UK law, with modifications. The Open / Specific / Certified framework remains, and the PDRA concept — including PDRA-02 — is recognised within the UK Specific category. Operators should not assume that an EASA-issued authorisation or an EU member state authorisation is automatically valid for UK operations; a separate CAA Operational Authorisation is required.

For operators with cross-border programmes — for example, a survey company operating in both Great Britain and EU member states — the insurance programme must satisfy both the CAA and the relevant EASA national competent authority. EASA's framework also uses the Open / Specific / Certified structure, but the specific PDRA conditions and insurance evidence requirements may differ between jurisdictions. Brokers placing multinational programmes should confirm that the policy wording is acceptable to each relevant authority.

The CAA publishes guidance on Operational Authorisation requirements, and the UK PDRA-02 standard scenario document sets out the specific conditions operators must meet. Brokers and operators should read the current version of that document — not a summary — because the insurance condition is stated explicitly within it, and any future CAA revisions will be reflected there first.

Frequently asked questions

Does PDRA-02 legally require third party liability insurance in the UK?

Yes. PDRA-02 falls within the CAA's Specific category, and Specific category Operational Authorisations require the operator to hold third party liability insurance as a condition of approval. Operating without compliant insurance invalidates the authorisation and exposes the operator to regulatory enforcement.

Will a standard commercial drone policy cover PDRA-02 operations?

Not automatically. Many commercial drone policies are written for VLOS operations and contain exclusions for BVLOS flight. Before relying on an existing policy for PDRA-02, check the wording for BVLOS exclusions, automated flight mode exclusions, and any geographic or operational scope restrictions. If any of these apply, the policy must be endorsed or replaced before the Operational Authorisation is submitted.

What information does an underwriter need to quote PDRA-02 liability cover?

Underwriters will typically require the aircraft make, model, and maximum take-off mass; the operator's draft or approved Operational Authorisation; the operations manual including lost-link and emergency procedures; evidence of remote pilot competency; the geographic area of operations; and the nature of any payload. The more complete the submission, the more accurately the underwriter can assess the risk and provide firm terms.

Does the insurance certificate need to mention BVLOS or PDRA-02 specifically?

Best practice — and increasingly a CAA reviewer expectation — is that the certificate reflects the scope of the authorisation. A generic certificate stating only 'commercial drone operations' may not satisfy a reviewer checking for BVLOS cover. Request a certificate that confirms BVLOS operations are covered and, where possible, references the PDRA-02 authorisation type.

What happens if the Operational Authorisation is renewed but the insurance lapses?

A lapse in insurance cover during an active Operational Authorisation period means the operator is no longer compliant with the conditions of that authorisation. Flights conducted during the lapse period are unauthorised and uninsured. Brokers should align renewal dates and build reminder workflows so that insurance renewal precedes — not follows — the authorisation renewal date.

Does PDRA-02 insurance differ from cover needed for a bespoke SORA-based authorisation?

The core requirement — third party liability cover appropriate to the operation — is the same. The difference lies in how the risk is assessed. PDRA-02 uses a pre-defined risk assessment, so the operational parameters are standardised and underwriters have a clearer risk profile to work from. A bespoke SORA authorisation may involve higher or more unusual risk levels, which can require more detailed underwriting information and potentially broader policy conditions.