As operations scale beyond recreational flying, regulators demand an "operations manual"โa document proving that you've thought through every operational safety detail. However, "operations manual" means different things across countries. Some require nothing; others mandate 50+ pages. This guide details when operations manuals are required, what they must include, and how to manage version control globally.
Operations Manual Requirement Summary
| Requirement | UK | Germany | France | Netherlands | Sweden | Australia | New Zealand | Canada | Japan |
|---|---|---|---|---|---|---|---|---|---|
| When Required | Operational Auth (PfCO) | Specific Ops (A2+) | Specific Ops | Specific Ops | Specific Ops | ReOC (Commercial) | Part 102 (Commercial) | Approved Operator | Specific scenario dependent |
| Trigger Threshold | Commercial or BVLOS | A2 CofC + BVLOS/Complex | A2 CofC + Specific Ops | A2 CofC + Specific Ops | A2 CofC + Specific Ops | Commercial > 2kg or fleet | Part 102 commercial | Commercial or RPIC team | Commercial > stated threshold |
| Typical Length | 20โ50 pages | 30โ80 pages | 30โ60 pages | 30โ60 pages | 30โ60 pages | 50โ100 pages (org manual) | 30โ50 pages | 20โ40 pages | 50โ80 pages |
| Template Available | CAP 2606 (guideline) | EASA guidance | EASA guidance | EASA guidance | EASA guidance | CASA guidelines | CAA guidelines | Transport Canada template | NAA guidelines |
| Review Frequency | Annually + per change | Annually + per change | Annually + per change | Annually + per change | Annually + per change | Annually + per change | Annually + per change | Annually + per change | Annually + per change |
| Authority Approval | CAA (for PfCO) | LBA (for approval) | DGAC (if Specific Ops) | ILT (if Specific Ops) | Transportstyrelsen | CASA (ReOC) | CAA (Part 102) | Transport Canada | NAA |
| Enforceable | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) | Yes (binding) |
United Kingdom (CAA Operations Manual Requirements)
When Required
Operational Authorisation (PfCO) Trigger:- Commercial operation (any revenue-generating flight)
- BVLOS operation (even recreational)
- Flying over people (unless Category 1 <7kg exception)
- Night flights
- Flying above 120m AGL
- Flyer ID operations (small < 250g, VLOS, no people, no complex operations)
What Must Be Included
Core Manual Sections (CAP 2606 guidance):- Organization & Management
- Company details (registered address, contact)
- Key personnel (accountable manager, remote pilots, observers)
- Organizational structure
- Responsibilities/roles
- General Policies
- Insurance details (policy number, coverage limit)
- Safety policy statement
- Risk management framework
- Maintenance procedures
- Operations
- Aircraft types approved
- Operational limits (altitude, distance, weight)
- VLOS procedures (observer responsibilities)
- BVLOS procedures (chase aircraft, observer team, contingency)
- Night operation procedures (if applicable)
- Weather minimums
- Airspace restrictions
- Personnel
- Pilot roster (with license numbers, expiry dates)
- Training procedures (pilot currency)
- Medical requirements (if relevant)
- Safety briefing procedures
- Incident Reporting
- Procedure for reporting accidents/incidents
- Notification timeline (CAA: within 10 days for serious incidents)
- Record retention (5 years)
- Flight Log & Records
- Format required (date, time, location, pilot, incident notes)
- Retention period (2 years)
- Archival procedures
- Maintenance & Servicing
- Maintenance schedule (pre-flight, post-flight, periodic)
- Maintenance log format
- Defect recording and resolution
Template & Guidance
Official Source: CAA CAP 2606 (Small Unmanned Aircraft Operator's Manual)- Available free via CAA website
- Not mandatory to follow exactly, but provides reference framework
- CAA expects compliance with spirit of guidance
- Annual review (end of operational year)
- Immediate update for any operational change (e.g., new aircraft type, new pilot)
- Change log required (dated entries showing what changed + when)
- CAA may request updated manual during audit
Version Control & Change Management
MmowW Best Practice:- Manual stored as PDF + editable master (Word/Google Docs)
- Version number: V1.0, V1.1, V1.2 (track minor revisions)
- Change log at front: "V1.1 (2026-04-10): Added night flight procedures"
- Dated signatures: Key personnel sign off on versions
- Archive old versions (for audit trail): "V1.0_archived_2025-09-01.pdf"
- A2 CofC + any of:
- BVLOS beyond 1 km
- Flight over populated areas
- Flight above 120m altitude
- Night operations
- Research/experimental flights
- Commercial operations (any revenue)
- A1 operations (small < 250g, VLOS, no people, no complex)
- General Operations
- Company information
- Certification details (Operational Authorization reference)
- Key contacts (pilot, observer, accountable manager)
- Risk Management (SORA-based)
- Specific risk assessment per operation type
- Mitigation measures (e.g., BVLOS = chase aircraft + observer team)
- Contingency procedures (e.g., loss of signal โ immediate land)
- Safety margins (altitude buffers, distance limits)
- Procedures Manual
- Pre-flight checklist
- Flight planning (route, airspace, weather)
- VLOS procedures
- BVLOS procedures (if applicable)
- Night ops procedures (if applicable)
- Emergency procedures (loss of signal, weather degradation, power loss)
- Post-flight procedures (aircraft inspection, log update)
- Personnel & Training
- Pilot roster (with A1/A2 certification details)
- Observer roster (if BVLOS)
- Training requirements (initial + recurrent)
- Currency standards (e.g., 5 flights per month to maintain currency)
- Competency assessment records
- Aircraft Management
- Aircraft register (all approved drone types)
- Maintenance schedule
- Maintenance log format
- Inspection frequency
- Defect/repair procedures
- Airworthiness status tracking
- Flight Records
- Flight log format (date, time, location, pilot, observer, incidents)
- Retention period (3 years, EASA-harmonized)
- Electronic logging system (if used)
- Incident/Accident Reporting
- Definition of incident vs accident
- Reporting timeline (EASA: immediate for serious)
- Record retention (5 years)
- Investigation procedure
- Airspace & Navigation
- Airspace classification (Class A/B/C/D/E/F/G understanding)
- Coordination procedures (who to contact for airspace clearance)
- Restricted/danger areas awareness
- Procedures for flying near airports (proximity rules)
- EASA publishes example manuals + standardized format
- Member states (LBA, DGAC, ILT, Transportstyrelsen) may have country-specific addenda
- Mandatory: Follow EASA structure + member state requirements
- Germany (LBA): Most detailed (includes detailed SORA templates)
- France (DGAC): Flexible format (less rigid than Germany)
- Netherlands (ILT): Moderate detail (balanced)
- Sweden (Transportstyrelsen): Moderate detail (streamlined)
- Manual submitted to authority during approval process
- Authority approves specific version
- Any change requires:
- Update manual
- Submit change notice to authority (formal amendment form)
- Authority approves change (can take 1โ2 weeks)
- Only approved version is legally operable
- Minor: Personnel change, new aircraft (same model) โ 2 weeks approval
- Major: New operation type, new procedure โ 4โ6 weeks approval
- Critical: Safety-affecting changes โ Immediate notice required
- Commercial operation with multiple aircraft (fleet)
- Complex operations (BVLOS, over populated areas)
- Aircraft > 25kg MTOW
- Operations beyond Part 101 scope
- Organization
- Company registration
- Accountable manager (nominated person)
- Key personnel (pilot, observer, maintenance)
- Contact details
- Safety Management System (SMS)
- Safety policy
- Hazard register
- Risk mitigation procedures
- Safety metrics/KPIs
- Operations Manual Sections
- Authorized aircraft types (with MTOW, sensor limits)
- Approved operational areas (geofenced locations)
- Weather minimums (wind speed, visibility, cloud base)
- Altitude limits
- VLOS procedures (observer qualifications, visual range)
- BVLOS procedures (observer team, chase aircraft, communications)
- Night operations (if approved)
- Emergency procedures (signal loss, weather, mechanical)
- Personnel Management
- Pilot roster (with Remote Pilot License numbers)
- Observer roster (if applicable)
- Maintenance personnel (if in-house)
- Training syllabus (initial + recurrent)
- Currency/proficiency standards
- Medical/fitness requirements
- Aircraft Management
- Aircraft register (serial numbers, airworthiness status)
- Maintenance schedule (CASA-aligned, often 50-100 hours between inspections)
- Maintenance log format
- Inspection procedures
- Airworthiness certification (what qualifies as airworthy)
- Defect procedures (how to handle/repair/re-certify)
- Flight Operations
- Flight planning process (airspace check, weather, NOTAMs)
- Flight briefing procedure
- Flight execution (crew roles, communications)
- Flight log requirements (CASA-mandated format)
- Post-flight procedures (aircraft inspection, log submission)
- Quality Assurance
- Audit procedures (internal checks, flight audits)
- Training effectiveness (how to measure if training worked)
- Incident/accident investigation
- Record-keeping audit
- Record Management
- Flight log retention (7 years for ReOC)
- Maintenance record retention (7 years)
- Personnel record retention (5 years post-employment)
- Incident record retention (permanent, or per AAIB requirement)
- Detailed checklist of required manual contents
- Provides example procedures
- Not a template (CASA wants customization to your operation)
- Operator drafts manual
- Submits to CASA for review (via online portal)
- CASA reviews (can take 4โ8 weeks)
- CASA approves specific version or requests changes
- Only approved version is operable
- Minor changes (personnel, minor procedures): Notify CASA within 5 days (approval usually automatic)
- Major changes (new operation type, new airspace, safety procedures): Submit as amendment (4โ8 weeks)
- Archive: All versions kept (audit trail)
- Commercial operation or approved operator category
- Aircraft > 25kg MTOW
- Operations beyond Part 101 scope (BVLOS, over people, night, etc.)
- Organization
- Company details
- Accountable manager
- Key personnel
- Approval/certification details
- Operations Manual
- Approved aircraft types
- Operational limits
- Weather minimums
- VLOS/BVLOS procedures
- Emergency procedures
- Night ops (if approved)
- Personnel
- Pilot roster
- Observer roster (if BVLOS)
- Training procedures
- Currency standards
- Aircraft Management
- Aircraft register
- Maintenance schedule
- Maintenance logs
- Airworthiness procedures
- Flight Records & Incident Reporting
- Flight log format
- Retention (3 years typical)
- Incident procedures
- Provides framework (less rigid than CASA)
- Customization expected
- Typical length: 40โ60 pages
- Operator submits manual to CAA
- CAA reviews (typically 2โ4 weeks)
- Approval granted or changes requested
- Only approved version operable
- Changes submitted as amendments
- Minor changes: 1โ2 week approval
- Major changes: 2โ4 week approval
- Commercial operation (any revenue)
- Multiple aircraft operations
- Complex operations (BVLOS, night, etc.)
- Advanced RPIC team operations
- Organization & Personnel
- Company information
- Responsible person (accountable manager)
- Pilot roster
- Observer roster (if BVLOS)
- Training procedures
- Operations Procedures
- Authorized aircraft
- Operational limits
- Weather minimums
- VLOS/BVLOS procedures
- Emergency procedures
- Night ops (if applicable)
- Aircraft & Maintenance
- Aircraft register
- Maintenance schedule
- Maintenance logs
- Airworthiness procedures
- Flight Operations & Records
- Flight planning
- Flight log format (2-year retention)
- Incident reporting
- Streamlined compared to EASA/CASA
- Less prescriptive (more operator flexibility)
- Typical length: 30โ50 pages
- Operator submits manual to Transport Canada
- Approval timeline: 2โ4 weeks
- Changes submitted as amendments (1โ2 week approval)
- Any commercial operation
- Operations beyond basic registration (most commercial ops trigger)
- Large aircraft (> 25kg)
- Complex operations (BVLOS, night, over people)
- Organization
- Company registration (in Japanese)
- Accountable manager (nominated person)
- Key personnel
- Organizational chart
- Safety Management System (Japanese-specific)
- Safety policy
- Risk management procedures
- Hazard identification
- Mitigation measures
- Safety metrics
- Operations Manual
- Approved aircraft types (with Japanese model names)
- Operational boundaries (altitude, distance, time)
- Weather minimums (wind, visibility, cloud)
- VLOS procedures (visual range requirements)
- BVLOS procedures (chase aircraft, observer, communication systems)
- Night ops procedures (lighting requirements, observer responsibilities)
- Emergency procedures (signal loss, weather, mechanical failure, abort procedures)
- Airspace restrictions (Tokyo area, military zones, helicopter routes)
- Personnel Management
- Pilot roster (with National License numbers)
- Observer roster
- Maintenance personnel
- Initial training requirements (40โ60 hours typical flight training before certification)
- Recurrent training (annual)
- Currency standards (minimum flights per month)
- Medical/fitness certification
- Aircraft Management
- Aircraft register (all aircraft by serial number, registration number)
- Airworthiness certification procedure
- Maintenance schedule (often 10โ25 flight hours between inspections)
- Maintenance log format
- Inspection procedures (pre-flight, post-flight, periodic)
- Defect/repair/re-certification procedures
- Propeller inspection intervals
- Battery management procedures
- Flight Operations
- Flight planning (airspace check, weather, NOTAMs, restricted area coordination)
- Flight briefing procedure
- Crew roles (pilot, observer, crew chief)
- Flight execution procedures
- Flight log requirements (date, time, location, pilot, observer, maintenance notes)
- Post-flight procedures
- Maintenance schedule coordination (aircraft not flown if maintenance overdue)
- Record Management
- Flight log retention (2 years)
- Maintenance record retention (2 years)
- Personnel record retention (1 year post-employment)
- Incident record retention (per operation duration + 2 years)
- Quality Assurance & Audits
- Internal audit procedures (self-audit)
- Training effectiveness metrics
- Incident investigation procedures
- Corrective action procedures
- Language Requirements
- Entire manual in Japanese (English translations optional, but Japanese is official)
- Technical terms: Japanese equivalents required
- Highly detailed (most prescriptive of all 9 countries)
- Provides example procedures + mandatory format
- Typical length: 80โ150 pages
- Operator submits manual (in Japanese) to NAA
- NAA reviews (can take 4โ8 weeks)
- NAA may request Japanese cultural/legal adjustments
- Approval granted or revisions requested
- Resubmission cycle can extend timeline to 8โ12 weeks
- Any significant change requires amendment submission
- NAA approval required before implementing change
- Timeline: 2โ4 weeks per amendment (slower than other countries)
- Organization & Personnel: Company info, key roles, personnel roster
- Operations Procedures: Aircraft types, operational limits, VLOS/BVLOS, weather minimums, emergency procedures
- Aircraft & Maintenance: Aircraft register, maintenance schedule, logs, airworthiness procedures
- Flight Records: Flight log format, retention period, incident procedures
- Incident Reporting: Procedure, timeline, record retention
- Detail level: Minimal (Canada, NZ) โ Moderate (UK, EU, Australia) โ Extreme (Japan)
- Authority approval: Not required (some Part 101 ops) โ Required (most commercial)
- Flexibility: Flexible format (Canada, France) โ Standardized format (Germany, Australia, Japan)
- Change management: Self-managed (Canada) โ Authority-approved (EASA, Australia, Japan)
- General Operations
- Risk Management
- Personnel roster updates (new pilot, observer departure)
- Contact information changes
- Weather minimum updates (non-safety-critical)
- Approval: Usually automatic or notification-only
- New aircraft type added
- New operational area/airspace
- New operational procedure (e.g., BVLOS procedures added)
- Approval: Authority review required
- New operation type (e.g., flight over populated area)
- Safety procedure revision
- Emergency procedure overhaul
- Approval: Full authority review + possible inspection
- Keep all versions (v1.0, v1.1, v1.2, etc.)
- Archive in date-stamped folder: "OperationsManual_v1.0_archived_2025-01-15.pdf"
- Maintain change log (above)
- Audit trail: Show evolution + what changed when
- User selects country โ MmowW generates template
- UK: CAP 2606 structure
- EU: EASA Specific Operations format
- AU: CASA ReOC format
- NZ: CAA Part 102 format
- CA: Transport Canada format
- JP: NAA format
- Company information (from MmowW profile)
- Pilot roster (auto-imported from MmowW pilot database)
- Aircraft register (auto-imported from aircraft register)
- Flight log format (country-specific, auto-inserted)
- Incident procedures (country-specific template)
- Version numbering (v1.0, v1.1, etc.)
- Change log management (timestamp every change)
- Draft mode (edit safely before approval)
- Authority submission workflow (generate submission form per country)
- Approval status tracking ("Awaiting LBA approval," "CASA approved 2026-03-15")
- Pilot roster matches actual pilot certifications (expiration check)
- Aircraft register matches actual aircraft (serial numbers, airworthiness status)
- Procedures align with approved operations (can't approve BVLOS if pilot doesn't have BVLOS training)
- Flags: "Procedure references pilot John Smith (expired 2026-02-01) - update roster"
- Operations Manual PDF (with version number, approval status, change log)
- Attachment: Current pilot roster (with license verification)
- Attachment: Current aircraft register (with airworthiness status)
- Attachment: Latest flight logs (past 6 months, for auditor review)
- Audit checklist: "Does this operation comply with {country} rules?"
- v1.0 (2025-01-15): Approved with DJI Air 3 only
- Add new aircraft: DJI Matrice 300 (25kg MTOW, thermal camera)
- Update Manual (new section on Matrice 300):
- MTOW: 25 kg
- Camera: Thermal + RGB
- Max flight time: 45 minutes
- Maintenance intervals: 25 flight hours
- New pilot training: Required (thermal operations specific)
- Rename to v1.1 (2026-04-10)
- Add to change log: "v1.1 (2026-04-10): Added DJI Matrice 300 (thermal operations)"
- Re-submit to CAA for approval
- CAA reviews (typically 2โ3 weeks): Approves or requests changes
- If approved: v1.1 becomes operable manual
- v2.3 (2025-06-01): Approved with basic BVLOS procedure
- EASA issues new Special Condition for BVLOS in urban areas (hypothetical)
- Operator updates chase aircraft requirements, observer team composition
- Update Manual (BVLOS procedures section)
- Rename to v2.4 (2026-04-10)
- Change log: "v2.4 (2026-04-10): Updated BVLOS procedures per new EASA SC X.2026"
- Submit amendment to LBA (formal amendment form)
- LBA review (typically 4โ6 weeks)
- LBA approves or requests safety clarifications
- If approved: v2.4 operable
- v3.2 (2025-03-15): Approved
- Pilot roster: 1 pilot expired license (John Smith, expired 2026-02-01)
- New pilot added: Jane Doe (Advanced RPIC, qualified)
- Maintenance hours: Aircraft A accumulated 342 hours (vs 300-hour limit between inspections)
- Action: Update maintenance schedule documentation
- Update manual (personnel + maintenance sections)
- Rename to v3.3 (2026-04-10)
- Change log: "v3.3 (2026-04-10): Removed J. Smith (expired), added J. Doe; updated maintenance tracking"
- Notify CASA (minor change notification, not full re-approval)
- CASA usually responds within 1 week (automatic approval or minor clarification)
- v3.3 operable
- Operations Manual Required: Not for every operator, but mandatory for commercial/complex operations in all 9 countries
- Country-Specific Requirements:
- UK: CAP 2606 guidance (flexible)
- EU: EASA format (harmonized across member states)
- AU: CASA MOS (most detailed)
- NZ: CAA guidelines (moderate)
- CA: Transport Canada template (streamlined)
- JP: NAA guidelines (most prescriptive, Japanese language)
- Core Sections Universal: Organization, procedures, personnel, aircraft, flight records, incident reporting (all required everywhere)
- Version Control Critical: Every change requires tracking + authority approval (timeline: 1โ8 weeks depending on change criticality)
- Archive All Versions: Audit trail required (authority reviews change history)
- MmowW Management: Template generation per country, automated consistency checks, version control, audit-ready export
EU-EASA (Germany, France, Netherlands, Sweden) Operations Manual
When Required
Specific Operations (Category):What Must Be Included (EASA Spec)
Standard Manual Sections (EASA-harmonized across EU):EASA Template
Official Source: EASA Special Conditions documentation (free, per member state)Version Control (EU-EASA)
Standard Practice:Australia (CASA Operations Manual)
When Required
Remote Operator Certificate (ReOC) Trigger:What Must Be Included
CASA Manual Requirements (Detailed):CASA Guidelines
Official Source: CASA Manual of Standards (MOS) Section 02.051 (Remote Operator Certificate)Version Control (CASA)
Approval Process:New Zealand (CAA Part 102 Operations Manual)
When Required
Part 102 Approval Trigger:What Must Be Included
NZ CAA Requirements (Moderate Detail):NZ CAA Guidelines
Official Source: CAA guidance documents (Part 102 Manual template)Version Control (NZ)
Approval Process:Canada (Transport Canada Operations Manual)
When Required
Approved Operator Trigger:What Must Be Included
Transport Canada Requirements (Streamlined):Transport Canada Template
Official Source: Transport Canada website provides template/guidelinesVersion Control (Canada)
Approval Process:Japan (NAA Operations Manual Requirements)
When Required
Specific Operation Trigger:What Must Be Included
NAA Requirements (Most Detailed Globally):NAA Guidelines
Official Source: NAA guidance (Yusoki Un'yo Shishin) - Operations Guidelines for Unmanned AircraftVersion Control (Japan)
Approval Process:Universal Operations Manual Components
Sections Found in ALL 9 Countries:Version Control & Change Management Best Practices
Document Structure
Recommended Format:`` OPERATIONS MANUAL v1.5 (2026-04-10) [Company Name] Table of Contents