Apply for a PDRA01 Operational Authorisation

What PDRA-S01 Covers and Why It Matters

The UK Open / Specific / Certified framework, administered by the Civil Aviation Authority, places most commercial drone operations in the Specific category once they exceed the parameters of the Open category — for example, when the operational scenario involves flights over or near people in ways that Open category subcategories do not permit, or when the aircraft or operational concept falls outside Open category conditions. PDRA-S01 is one of several pre-defined risk assessments the CAA has published to give operators a faster route through the Specific category without conducting a full bespoke SORA.

PDRA-S01 is explicitly a VLOS scenario. The CAA's published PDRA-S01 document defines the operational envelope: operations are conducted at a maximum height of 120 metres above ground level, within ground risk classes GRC-1 to GRC-3 (broadly corresponding to sparsely populated and controlled ground environments), and the scenario does not extend to flights over dense urban areas or congested assemblies of people. Operators must confirm that every element of their planned operation sits within these published parameters before applying. Any deviation — including any BVLOS element — pushes the operation outside PDRA-S01 and into a bespoke SORA.

Because the risk has already been assessed at a regulatory level, operators who fit entirely within the PDRA-S01 envelope can apply for an operational authorisation without producing their own full SORA documentation. This significantly reduces the administrative burden compared to a bespoke Specific category authorisation, but it does not reduce the operator's responsibility to ensure their actual operations remain within the authorised scope at all times.

Eligibility: Who Can Apply

To apply for a PDRA01 operational authorisation, the operator must hold a valid CAA Operator Registration and the remote pilot must hold a General Visual Line of Sight Certificate (GVC) or an equivalent qualification issued by a CAA-recognised National Qualified Entity (NQE). In the UK, NQEs are organisations approved under the CAA's DMARES (Declared and Approved) scheme — examples include bodies such as ARPAS-UK-affiliated training providers and other CAA-listed NQEs. Operators relying solely on an Open category A2 Certificate of Competency are not eligible for PDRA-S01; the GVC is the minimum competency standard.

The aircraft must meet the technical and performance requirements specified within the PDRA-S01 document. Operators should verify that UAS manufacturer documentation, maintenance records, and any relevant Declaration of Conformity align with those requirements before submission. Gaps in technical documentation are a common reason for CAA requests for further information, which extend processing time.

Commercial operators — including those conducting aerial survey, infrastructure inspection, and media production — must also confirm that their operations manual reflects the PDRA-S01 scenario specifically. The CAA expects the operations manual submitted with the application to describe procedures, emergency protocols, and crew responsibilities consistent with the pre-defined risk envelope, not a generic template adapted from a different operational category.

• Valid CAA Operator Registration number
• Remote pilot holds a GVC issued by a CAA DMARES-approved NQE, or a CAA-recognised equivalent
• Aircraft technical documentation aligned to PDRA-S01 parameters
• Operations manual specific to the PDRA-S01 VLOS scenario
• Evidence of crew competency and recency

The Application Process Step by Step

Applications are submitted through the CAA's Drone Registration and Education Service (DRES), accessible via the CAA UAS hub at the CAA website. Before starting, operators should download the current PDRA-S01 document from the CAA website and complete a self-assessment against each published parameter. The self-assessment is not submitted to the CAA but forms the evidential basis for the declarations made in the application form. The PDRA-S01 document itself is publicly available and should be treated as the definitive reference — not third-party summaries.

The application requires the operator to declare conformity with the PDRA-S01 conditions, upload the operations manual, and provide evidence of remote pilot competency. The CAA publishes a target processing time of 30 working days for PDRA operational authorisation applications, though this can vary with application volume and the completeness of the submission. Operators with time-sensitive contract start dates should apply well in advance and ensure their submission is complete at the first attempt to avoid requests for further information that reset the clock.

Once granted, a PDRA01 operational authorisation is valid for a period of up to two years from the date of issue. Renewal requires a fresh application through DRES before the authorisation expires; the CAA does not issue automatic renewals. Brokers should record the authorisation expiry date at inception and initiate renewal conversations with operators at least 60 days before expiry to allow time for both the regulatory renewal and any insurance programme adjustments.

Operators must retain a copy of the granted authorisation and its conditions on site during every operation covered by it, and must notify the CAA if any material change occurs — including a change of aircraft type, operational area, or crew — that could take the operation outside the PDRA-S01 parameters. Failure to notify constitutes a regulatory breach and can invalidate both the authorisation and any associated insurance cover.

• Download and self-assess against the current PDRA-S01 document from the CAA website
• Prepare and finalise the operations manual specific to the PDRA-S01 VLOS scenario
• Gather remote pilot GVC evidence from a CAA DMARES-approved NQE
• Submit via the CAA Drone Registration and Education Service (DRES) with all supporting documents
• Allow for the CAA's published 30-working-day target processing time
• Retain the granted authorisation and conditions on site during operations
• Notify the CAA of any material operational change before it occurs

Insurance Requirements and the PDRA01 Authorisation

UK drone operators conducting commercial operations are required to hold third-party liability insurance under UK Regulation 785/2004 (as retained in UK law post-Brexit). The CAA does not require proof of insurance to be submitted as part of the PDRA01 application itself; insurance is a separate regulatory obligation that runs in parallel with the operational authorisation. However, operating without compliant insurance while holding a PDRA01 authorisation remains a breach of UK Regulation 785/2004 (as retained in UK law post-Brexit), and brokers should ensure cover is in place before the operator commences any authorised flight.

For Specific category operations, insurers and brokers treat the operational authorisation as a primary underwriting document. The scope of cover must align with the authorised operational scenario; a policy written for Open category VLOS operations will not respond to a Specific category PDRA-S01 flight. Premiums scale with hull value, the nature of the payload, and the ground risk environment described in the authorisation. Deductibles and sub-limits are typically structured to reflect the specific risk class rather than a generic drone policy.

Hull cover for the UAS itself is not mandated by regulation but is strongly advisable for commercial operators whose aircraft represent significant capital. Underwriters will assess the aircraft's maintenance regime, storage arrangements, and the operator's claims history. Operators who have held a PDRA01 authorisation for multiple renewal cycles and can demonstrate a clean loss record are generally viewed more favourably at renewal.

Brokers placing programmes for operators who subsequently wish to expand beyond PDRA-S01 — for example, into BVLOS operations or flights over populated areas requiring a bespoke SORA — should flag this to underwriters early. BVLOS operations fall entirely outside the PDRA-S01 envelope and require a separate bespoke SORA submission to the CAA. Mid-term endorsements to extend cover to a materially different operational scope require fresh underwriting information and, in some cases, a new policy.

Broker Document Checklist for Placing a PDRA01 Programme

When presenting a PDRA01 risk to underwriters, the quality and completeness of the submission file directly affects both the speed of response and the breadth of cover available. Underwriters writing Specific category programmes need to assess the authorised operational scope, the aircraft schedule, and the operator's competency and loss record before quoting. A partial submission invariably results in referral queries that delay binding.

The following documents should be assembled in submission order. Brokers who review the operations manual before submission — even informally — can identify mismatches between the declared operation and the insurance programme being placed, reducing the risk of a coverage gap at the point of claim.

Operators sometimes assume that holding a PDRA01 authorisation automatically extends their existing Open category insurance. It does not. The policy must be specifically endorsed or rewritten to cover Specific category operations, and the wording should explicitly reference the operational authorisation number and the PDRA-S01 scenario.

• 1. Copy of the granted PDRA01 operational authorisation (including all conditions)
• 2. Current operations manual specific to the PDRA-S01 VLOS scenario
• 3. Aircraft schedule (make, model, MTOM, serial numbers, hull values)
• 4. Remote pilot competency certificates (GVC from a CAA DMARES-approved NQE, plus any type-specific training evidence)
• 5. Full claims history for the preceding three years (or since inception if shorter)
• 6. Any planned operational changes that may affect the authorised scope before the next renewal

Common Pitfalls and How Brokers Can Help

The most frequent application errors involve operations manuals that describe a broader operational scope than PDRA-S01 permits — for example, referencing BVLOS contingencies or ground risk environments above GRC-3 — or that omit required emergency procedures. These mismatches are also underwriting red flags: a manual that does not match the declared authorisation scope creates ambiguity about what the policy is actually covering.

Renewal of the operational authorisation is a natural review point for the insurance programme. Because PDRA01 authorisations are granted for up to two years, brokers should build expiry dates into their diary management systems and initiate renewal conversations early enough to allow both the CAA application and the underwriting process to complete before the current authorisation lapses. An operator flying on an expired authorisation is uninsured for Specific category operations regardless of what the policy schedule says.

Operators who outgrow the PDRA-S01 envelope — whether through fleet expansion, new client requirements, or a move into BVLOS work — need both a new regulatory pathway and a revised insurance programme. Brokers who maintain an active dialogue with operators about their operational development are better placed to anticipate these changes and avoid the coverage gaps that arise when regulatory and insurance timelines fall out of step.

Frequently asked questions

What does a PDRA01 operational authorisation actually permit?

A PDRA01 authorisation permits the holder to conduct drone operations that fall within the CAA's published PDRA-S01 parameters: VLOS flights at a maximum height of 120 metres AGL, within ground risk classes GRC-1 to GRC-3, and in population density environments consistent with the pre-defined scenario. It is a Specific category authorisation and does not extend to BVLOS operations or to ground environments above GRC-3. Any operation outside those parameters requires either a separate authorisation or a bespoke SORA submitted to the CAA.

Is proof of insurance required when submitting the PDRA01 application to the CAA?

No. The CAA does not require proof of insurance as part of the PDRA01 application submission. Insurance is a separate regulatory obligation under UK Regulation 785/2004 (as retained in UK law post-Brexit) that runs in parallel with the operational authorisation. Operators must hold compliant third-party liability cover before commencing any authorised flight, but the insurance document is not a submission requirement for the authorisation itself. Brokers should ensure cover is bound and in force before the operator's first flight under the authorisation.

Where do operators submit a PDRA01 application and how long does it take?

Applications are submitted through the CAA's Drone Registration and Education Service (DRES), accessible via the CAA UAS hub on the CAA website. The CAA publishes a target processing time of 30 working days for PDRA operational authorisation applications. Incomplete submissions or requests for further information will extend this timeline. Operators with fixed contract start dates should apply well in advance and ensure their submission — including the operations manual and competency evidence — is complete at the first attempt.

How long is a PDRA01 authorisation valid and how is it renewed?

A PDRA01 operational authorisation is granted for a period of up to two years from the date of issue. There is no automatic renewal; operators must submit a fresh application through DRES before the authorisation expires. Brokers should record the expiry date at inception and initiate renewal conversations at least 60 days before expiry to allow time for both the regulatory renewal and any insurance programme adjustments. Operating on an expired authorisation is a regulatory breach and will affect the validity of any associated insurance cover.

What competency evidence does the CAA require with the application?

The remote pilot must hold a General Visual Line of Sight Certificate (GVC) issued by a CAA DMARES-approved National Qualified Entity (NQE), or a CAA-recognised equivalent. The application should include evidence of the certificate, its issue date, and any recency requirements the operator has set in their operations manual. The CAA may also ask for evidence of type-specific training if the aircraft or operational scenario warrants it. A list of CAA-approved NQEs is published on the CAA website.

What triggers the need to move from PDRA-S01 to a bespoke SORA?

Any element of the planned operation that falls outside the PDRA-S01 envelope triggers the need for a bespoke SORA. Common triggers include BVLOS operations (which are entirely outside PDRA-S01), flights in ground risk environments above GRC-3, operations over or near dense assemblies of people, use of aircraft that do not meet the PDRA-S01 technical parameters, or any operational concept that exceeds the 120-metre AGL height limit. Brokers should treat a move to bespoke SORA as a material change requiring fresh underwriting information and, in most cases, a revised or new policy.

Does the insurance policy need to reference the PDRA01 authorisation specifically?

Yes. Underwriters write Specific category cover against the declared operational scope. The policy should reference the operational authorisation number and the PDRA-S01 scenario to ensure there is no ambiguity about what operations are covered. A generic drone liability policy written for Open category VLOS work will not respond to a Specific category claim. Brokers should confirm the wording at inception and at each renewal, and notify underwriters immediately if the authorisation is varied, suspended, or revoked.