Drone Operations Manual Netherlands: ILT Requirements for OA Holders
If you hold an Operational Authority (OA) from the ILT, you need an Operations Manual—a comprehensive document that proves you can manage your drone fleet safely and legally. The ILT won't issue (or renew) an OA without reviewing your manual. This guide covers what sections the ILT requires, how to structure them, and how to pass audit scrutiny.
Piyo (Regulatory Expert): "OA holders who skip the operations manual think they can wing it. Then the ILT demands the manual during audit, and they scramble for weeks."
Poppo (Compliance Officer): "An operations manual isn't just paperwork—it's your operational DNA. Every procedure, every risk, every rule."
What Is an Operational Authority (OA)?
An Operational Authority is ILT permission to conduct commercial drone operations beyond standard rules (VLOS, restricted airspace, payload operations). OA holders operate under their own risk management framework, not generic rules.
Who needs an OA:- Commercial BVLOS operators (beyond visual line of sight)
- Operations near critical infrastructure (airports, power lines, hospitals)
- Payload operations (surveying, LiDAR, thermal imaging)
- Fleet operations (5+ aircraft simultaneously)
- Operations during twilight/darkness
The Operations Manual is your passport to OA approval.
Moo (Drone Operator): "What if we apply for OA but don't get approved?"
Piyo: "ILT will list deficiencies in your manual. Fix them and resubmit. Most rejections come from incomplete risk assessments or vague procedures."
Mandatory Manual Sections (ILT Checklist)
1. General Policies & Scope
- Company name, registration (KVK number), principal place of business
- OA holder name, contact information, legal representative
- Effective date & version control (Version 1.0, Date: Jan 2026)
- Scope of operations (e.g., "BVLOS commercial surveying in populated areas, daytime only, 300m AGL max")
- Constraints & limitations (e.g., "Not applicable during precipitation, winds >8 m/s, or emergency situations")
2. Organization & Management
- Organizational chart showing roles/responsibilities
- Remote Pilot in Command (RPIC) designation & qualifications
- Safety Officer appointment (required for OA)
- Maintenance Officer (or outsourced facility name)
- Training Officer (responsible for crew competency)
- Emergency response coordinator
3. Aircraft Management & Maintenance
- Fleet inventory (serial numbers, weight class, certifications)
- Maintenance schedule (pre-flight, 50-hour, annual, major overhaul)
- Maintenance logbook procedures (MmowW-integrated or spreadsheet—but detailed)
- Airworthiness certification process
- Parts management & traceability
- Defect reporting & resolution
4. Crew Competency & Training
- Pilot certification requirements (minimum A2 or higher)
- Recurrent training schedule (10 hours/year minimum)
- Medical fitness standards
- Type-rating training (if multi-aircraft fleet)
- Emergency procedure drills (quarterly minimum)
- Training records retention (3 years minimum)
5. Operational Procedures (Standard Operating Procedures—SOPs)
- Pre-flight briefing format
- Flight planning & route approval
- Airspace coordination (Schiphol, military ranges, other OA ops)
- Weather briefing protocol (wind, precipitation, visibility)
- GPS/RTK loss procedures (fallback to manual control)
- Lost-link recovery procedures (default action if signal lost)
- Emergency landing procedures
- Communication protocols (radio, ground crew, emergency services)
`` SOP-001: Pre-Flight Briefing
- Gather team: RPIC, Safety Officer, Ground Crew
- Review flight plan (route, AGL, duration)
- Check weather (wind, precipitation, visibility, turbulence)
- Confirm airspace status (NOTAMs, military activity, other traffic)
- Verify aircraft systems (battery, propellers, gimbal, RTK)
- Identify contingency landing zones
- Brief emergency procedures
- RPIC sign-off (signature + date/time)
6. Risk Assessment & Mitigation
- Risk Register (table of identified hazards)
- Mitigation strategies (how you reduce each risk)
- Residual risk tolerance (which risks you accept, which you reject)
- Example risks:
- Hazard: GPS signal loss in urban canyon
- Mitigation: Operator retrained quarterly on manual recovery; aircraft limited to 100m AGL when GPS unavailable
- Residual risk: Acceptable (weekly operations, zero incidents over 50 flights)
ILT expectation: Systematic thinking. Don't just say "weather bad." Say "Wind >8 m/s creates lateral drift >15m over 500m distance; we mitigate by reducing max AGL to 200m and increasing buffer zones to 100m; residual risk acceptable for non-critical operations."
7. Safety Management System (SMS)
- Incident & accident reporting procedures
- Root cause analysis methodology
- Corrective action tracking
- Safety performance metrics (flight hours, incidents, near-misses)
- SMS review frequency (annual minimum)
Example incident log entry:
` Incident #2026-005: GPS Loss Date: Mar 12 2026, 14:30 UTC Aircraft: DJI M350 (SN: ABC123) Description: RTK signal lost for 8 seconds during BVLOS survey near Schiphol Response: Pilot recovered to manual mode, descended to 150m, aborted mission Root cause: Multipath interference from nearby cellular tower (known area constraint) Corrective action: Updated flight plan template to flag this zone; added pre-flight verification of signal strength Status: Closed (no further action required; risk acceptable at reduced AGL) ``
8. Security & Cyber Measures
- Aircraft encryption standards (GPS spoofing detection, secure comms)
- Operator credential management (password, 2FA)
- Data protection (flight logs, customer data, aircraft telemetry)
- Cyber incident reporting (to ILT within 48 hours)
9. Insurance & Liability
- Certificate of Insurance (reference or attachment)
- Coverage limits (€500k–€1M third-party liability, depending on risk)
- Named insured entity
- Proof of renewal tracking
10. Appendices
- Aircraft type specifications (weight, max speed, endurance, battery)
- Crew certifications (copies of EASA remote pilot cards)
- Insurance certificates
- Maintenance facility partnerships (if outsourced)
- Blank checklists (pre-flight, post-flight, emergency procedures)
- Contact list (emergency services, airport control, backup crew)
- 30–60 pages typical for single-aircraft OA
- 100+ pages for multi-aircraft fleet OA
- Digital or printed (preferably both; store PDF in MmowW)
- Version control (e.g., "v1.3, updated Jan 2026")
- Table of contents + index
- Regulatory tone (formal, precise)
- Active voice ("Pilot verifies battery voltage" not "Battery voltage should be checked")
- Numbered procedures (SOP-001, SOP-002, etc.)
- Clear owners/sign-off (Who approves this? Date?)
- Digital: MmowW + cloud backup (Google Drive, Dropbox)
- Physical: Office copy + aircraft backup copy
- Accessibility: All crew must have current copy; updates distributed within 7 days
- [ ] Manual scope clearly defines all authorized operations
- [ ] All crew roles assigned to named individuals with verification
- [ ] Maintenance schedules realistic for aircraft type (not generic)
- [ ] Training records current & complete (last 3 years)
- [ ] Risk Register demonstrates systematic hazard identification
- [ ] Mitigation strategies credible (not "hope for the best")
- [ ] SOPs detailed enough for crew to follow independently
- [ ] Emergency procedures practiced & documented
- [ ] Incident log shows learning & corrective action (not stagnant)
- [ ] Insurance active & coverage limits adequate
- [ ] Cyber measures documented (post-2025 requirement)
- [ ] Crew demonstrates knowledge of manual (spot interviews)
- Download ILT template. Visit www.ilta.nl for official OA Operations Manual structure.
- Assign manual owner. Designate one person (usually Safety Officer) responsible for maintenance.
- Draft scope section. Define exactly what your OA covers (operation type, airspace, crew, aircraft).
- Develop risk register. Identify 10+ hazards; design mitigations.
- Write SOPs. At least 5 core procedures (pre-flight, flight planning, emergency, incident reporting, training).
- Assign crew roles. Name your RPIC, Safety Officer, Maintenance Officer with qualifications.
- Create training plan. Schedule annual recurrent training & document completion.
- Review insurance. Verify OA-level coverage (€500k–€1M liability).
- Store in MmowW. Upload manual & all supporting docs for easy audit access.
- Submit to ILT. Include cover letter, manual, crew CVs, insurance certificate.
- — Initial publication
Operations Manual Structure: Best Practices
Format:
Poppo's Note: ILT inspectors test procedures by asking random crew members about specific SOPs. If your Safety Officer says "SOP-005? Never heard of it," you fail. Training on the manual is as important as writing it.
ILT Audit Checklist: Operations Manual Review
During an audit, the ILT checks:
Common Rejections & How to Avoid Them
| Rejection Reason | Fix |
|---|---|
| "Scope too vague" | Specify operation type, max AGL, weather limits, airspace, crew count |
| "Risk Register incomplete" | Identify at least 10 hazards; show mitigation for each |
| "Crew untrained on manual" | Document training sessions; require annual recertification |
| "No maintenance schedule detail" | Link schedule to manufacturer specs; show inspection intervals |
| "Emergency procedures unrealistic" | Test procedures in simulations; document results |
| "Insurance certificate missing" | Submit active COI; ensure coverage limits match operation scope |
| "Cyber security ignored" | Document GPS spoofing detection; outline data protection protocol |
| "No incident logging" | Maintain active incident log; show closed-loop corrective action |
FAQ: Operations Manual & OA Compliance
Q: Do we need separate manuals for each aircraft type?A: No, one manual can cover multiple aircraft if they share procedures (e.g., DJI M350 + DJI M300, similar systems). Create appendices for type-specific quirks.
Q: How often must the manual be updated?A: Annually minimum. After incidents, major procedure changes, or crew changes, update immediately & notify ILT.
Q: Can we use a generic template from an online source?A: Yes, as a starting point. But the ILT rejects boilerplate manuals. Customize every section to your actual operations.
Q: Does the manual need to be in Dutch?A: No, English is acceptable (MmowW templates are English). But provide a Dutch summary for ILT review.
Q: What if our manual is rejected? Can we reapply?Action Plan: Build Your Manual Now
Update History
Was this helpful?
📮 Feedback Box — Coming Soon
Your feedback helps us improve. Our AI team (Poppo 🦉) reviews every submission.
This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulations change frequently — always verify with the relevant aviation authority (ILT) for the most current requirements. MmowW automates compliance tracking but does not replace professional consultation where required by law.