If you're operating drones commercially in the UK, you need an Operations Manual. But what goes in it? How detailed should it be? And what does the CAA actually expect? This guide walks through CAP 2606—the Civil Aviation Publication that defines the UK standard—and shows you how to build a manual that passes CAA scrutiny.

What Is a Drone Operations Manual?

A drone operations manual is a living document that describes how your organisation operates drones safely. It covers:

  • Pilot roles and responsibilities
  • Aircraft maintenance schedules
  • Weather limits and decision trees
  • Emergency procedures
  • Incident reporting protocols
  • Airspace usage and restrictions
  • Safety risk assessments
  • Crew training and currency

Think of it as your drone company's safety rulebook. The CAA uses it to assess whether you understand your risks and have controls in place to manage them. A weak manual suggests sloppy operations; a strong manual shows professionalism and reduces your liability.

Why You Need One

Regulatory requirement:
  • A2 Certificate holders flying beyond low-risk zones must have a documented safety case
  • GVC (General Visual Certificate) operators absolutely require a detailed operations manual
  • BVLOS (beyond visual line of sight) operations require CAA approval based on your manual

Practical benefit:
  • Protects your pilots by standardising procedures
  • Reduces insurance claims by showing due diligence
  • Provides legal defence in case of incident or accident
  • Demonstrates competence to clients and regulators

Common misconception: "I only fly simple stuff—do I need a manual?" Answer: If you're A2 or GVC-qualified and operating commercially, yes. Even if your flights are routine, documenting your processes is mandatory.

🦉
Poppo 🦉 (Compliance Expert)

Poppo: "I've seen operators with one-page manuals. That's dangerous."

Piyo: "What's the minimum?" Poppo: "For A2: 10–15 pages covering the essentials. For GVC: 50+ pages with detailed risk analysis, emergency procedures, and recurrent training plans. The CAA won't accept vague platitudes." Moo: "What if I don't have a manual and the CAA inspects me?" Poppo: "You'll get a compliance notice. Then you have 30 days to submit one. If you don't, you lose your qualification."

:::

CAP 2606 Structure: What CAA Expects

CAP 2606 is the CAA's civil aviation publication for drone operations manuals. It's not prescriptive—you don't have to copy it verbatim—but it provides a template. Here's the standard structure:

Section 1: Operator Information

  • Operator name, address, registration number (if limited company)
  • Key personnel (accountable manager, operations manager, safety officer)
  • Scope of operations (e.g., "aerial photography within 500m of operator, open category")
  • Declaration of conformity with regulations

Section 2: Organisational Structure

  • Roles and responsibilities (who signs off operations, who investigates incidents, who maintains aircraft)
  • Accountability chain (who reports to whom)
  • Crew resource management (how pilots communicate, decision-making hierarchy)

Section 3: Aircraft & Equipment

  • List of all drones (make, model, serial number, weight, maximum flight duration)
  • Maintenance schedules and responsibility assignment
  • Pre-flight checklist (specific to each aircraft type)
  • Equipment limitations (max altitude, max speed, weather limits, battery life)

Section 4: Personnel & Training

  • Pilot qualifications required (Flyer ID, A2, GVC, experience hours)
  • Training plan (initial and recurrent)
  • Currency requirements (e.g., "minimum 5 hours per 3 months to maintain proficiency")
  • Medical fitness standards
  • Fatigue and duty limitations

Section 5: Flight Operations

  • Operating areas (maps, coordinates, altitude limits)
  • Weather minimums (wind, visibility, precipitation, temperature)
  • Fuel/battery management
  • Take-off and landing procedures
  • Normal flight procedures (climb, cruise, descent)
  • Navigation and communication (if applicable)

Section 6: Safety Risk Assessment

  • Hazard identification (bird strike, loss of signal, loss of control, system failure)
  • Risk evaluation (probability × severity)
  • Mitigation measures (detection, recovery, avoidance)
  • Residual risk statement

Section 7: Emergency Procedures

  • Loss of signal (radio frequency interference, GPS loss)
  • Loss of propeller/rotor failure
  • Uncontrolled descent
  • Mid-air collision avoidance
  • Emergency landing procedures

Section 8: Airspace & Compliance

  • Airspace classification awareness (Class A, B, C, D, E, F, G)
  • Restriction Zones (FRZ) and danger areas
  • Notification procedures (who to contact, when, how)
  • NOTAMs (Notices to Airmen) and air traffic coordination

Section 9: Incident & Accident Reporting

  • Definition of reportable incidents (injury, property damage, near-miss, system failure)
  • Incident investigation process (immediate steps, root cause analysis, corrective action)
  • Reporting timeline (24 hours to CAA for serious incidents)
  • Record retention (minimum 2 years)

Section 10: Quality Management

  • Document control (version numbers, review dates, approval signatures)
  • Amendment procedure (who can change what, with what approval)
  • Safety performance monitoring (quarterly review of incidents/trends)
  • Continuous improvement plan

Practical Tips for Writing Your Manual

1. Keep It Realistic

Write procedures you actually follow. If your manual says "daily battery inspection" but you never do it, you're creating liability, not protection.

2. Use Decision Trees

For weather minimums, use a flowchart: `` Is wind speed > 12 m/s? → NO FLY Is visibility < 1 km? → NO FLY Is rain forecast? → DELAY FLIGHT Is temperature < 0°C? → OPERATE WITH CAUTION (check battery specs) ``

3. Be Specific About Aircraft Limits

Instead of: "Operate drone within manufacturer limits" Write: "DJI Air 3S maximum altitude 4,000m, maximum speed 21 m/s, battery endurance 37 minutes, maximum wind resistance 15 m/s"

4. Document Recurrent Training

For GVC holders, show how you'll keep pilots current. Example:

  • Theoretical refresher (annually): review weather, airspace, emergency procedures
  • Practical flying assessment (annually): demonstrate control in challenging conditions
  • Simulator training (if applicable): practice emergency scenarios

5. Include Real Emergency Procedures

Example for "Loss of Signal":

  • Pilot action: Immediately reduce altitude to establish visual reference
  • Aircraft response: (your specific drone model) will RTH (return to home) after 10 seconds signal loss
  • Recovery: If drone returns safely, land and investigate transmitter/signal blocker
  • If drone doesn't return: Search designated area, contact CAA if airspace interference suspected

🐮
Moo 🐮 (MmowW Founder)

Moo: "How detailed does safety risk assessment need to be?"

Poppo: "For a simple operation: 1–2 pages per major hazard. For complex work: multiple pages with mathematical risk scoring (probability 1–5, severity 1–5, mitigation effectiveness)." Piyo: "Can I copy another operator's manual?" Poppo: "Legally? Yes, templates exist online. Practically? The CAA will spot generic copy-paste manuals. Your manual must reflect YOUR operations, YOUR aircraft, YOUR risks." Moo: "What if I don't know how to assess risk properly?" Poppo: "Hire a drone safety consultant for £500–£2,000. They'll audit your operation and write a proper manual. It's cheaper than getting fined or losing your qualification."

:::

Common Mistakes to Avoid

Mistake Why It's Bad How to Fix
Vague language ("follow best practices") Unenforceable; shows lack of detail Be specific: "maintain 50m distance from persons unless A2 CofC permits 30m")
Unrealistic procedures ("daily 2-hour inspection") Creates liability; shows non-compliance Document what you actually do; be honest
Missing emergency procedures CAA sees unpreparedness Add specific procedures for each aircraft type
No risk assessment Core compliance failure Identify 5–10 key hazards and mitigation per operation
Outdated information Regulatory non-compliance Review quarterly; update with regulation changes
No signature approval Invalid document Have accountable manager and operations manager sign/date every edition

FAQ: Drone Operations Manual UK

Q: Do I need a separate manual for each drone model I operate?

A: No. One manual can cover multiple aircraft types, but include specific limitations and checklists for each. Example: "Section 3.2 – DJI Mini 3 Limitations" with max altitude, wind resistance, battery life.

Q: How long should a manual be?

A: A2 operators: 10–20 pages. GVC operators: 40–80 pages depending on complexity. The CAA prefers thorough over brief. Include appendices (checklists, risk matrix, incident log template).

Q: Who approves the manual?

A: Your accountable manager (usually the company owner/director) and operations manager (could be a senior pilot). Both sign and date it.

Q: Can I update my manual without CAA approval?

A: Yes, for operational changes (new aircraft, new airspace restrictions). But for changes affecting safety (new emergency procedures, risk mitigation), notify CAA within 30 days. For GVC holders, CAA must approve major changes.

Q: How often should I review my manual?

A: Minimum quarterly. After every incident. After regulation changes. After new aircraft acquisition. Keep a document control log showing review dates.

Q: What if I have multiple locations/countries?

Compliance with MmowW

At MmowW (£5.29/drone/month), our Operations Manual toolkit includes:

  • CAP 2606 template (UK-specific)
  • Risk assessment matrix builder
  • Incident log tracking (auto-uploaded for audit)
  • Document version control with approval workflows
  • Regulatory change alerts (updated quarterly)

This keeps your manual current, audit-ready, and legally compliant without constant manual labour.

Last updated: 8 April 2026. Information reflects CAP 2606 and current CAA expectations. Consult CAA (caa.co.uk) for the latest template.