A Drone Operations Manual (DOM) isn't a suggestion—it's a legal requirement for any commercial drone operation in Sweden. Transportstyrelsen mandates it before granting operational approvals, and inspectors examine it closely during audits. This guide covers what must be in your DOM, the approval process, common gaps, and how to avoid expensive delays.

What Is a Drone Operations Manual?

Piyo (Beginner Pilot)

Piyo: "We're launching commercial drone services next month. Someone mentioned we need an 'operations manual,' but we're not an airline." Poppo: "For regulatory purposes, you are. Transportstyrelsen treats commercial drone operations the same way: policies, procedures, safety protocols—all documented in a operations manual."

::: A Drone Operations Manual (DOM) is the master document describing:

  • Your company's organizational structure and roles
  • Every procedure for safe drone operations
  • Safety policies and risk management
  • Personnel qualifications and training requirements
  • Equipment specifications and maintenance
  • Emergency procedures
  • Record-keeping practices
  • Compliance with EASA and Transportstyrelsen regulations

It's your proof that you take compliance seriously and operate with established procedures—not ad-hoc improvisation.

Core Sections Transportstyrelsen Requires

1. General (Organizational Information)
  • Company legal name, registration number, VAT ID
  • Responsible manager and safety officer names/qualifications
  • Contact details for Transportstyrelsen coordination
  • Organizational chart showing chain of command
  • Locations where operations occur (Sweden-wide? Specific cities?)

2. Personnel & Training
  • Pilot qualifications (A1/A2/A3 certificates, training records)
  • Maintenance technician certifications
  • Observer/spotter training requirements
  • Recurrent training schedule (annual minimum)
  • Incident reporting responsibilities

3. Aircraft Information
  • Aircraft type, model, serial numbers
  • EASA classifications (small UAS, light UAS, etc.)
  • Performance specifications (max altitude, endurance, payload capacity)
  • Maintenance intervals and procedures
  • Limitations and operating restrictions

4. Operating Procedures
  • Pre-flight safety checks (written checklist)
  • Flight planning and airspace coordination
  • Weather minimums (wind speed, visibility, precipitation)
  • Night operations (if approved) and associated procedures
  • Beyond-visual-line-of-sight (BVLOS) procedures (if applicable)
  • Emergency and contingency procedures

5. Safety Management
  • Risk assessment process for each operation
  • Incident/accident reporting procedure
  • Insurance requirements and verification
  • Safety audit schedule
  • Environmental compliance (noise, privacy, data protection)

6. Records & Documentation
  • Flight logs format and retention (minimum 3 years)
  • Maintenance records and component tracking
  • Training and currency records
  • Incident reports and corrective actions
  • Audit trail requirements

Template Structure: What a Complete DOM Looks Like

A typical DOM structure follows EASA guidance: ``

  1. General Information (5–10 pages)

1.1 Organization 1.2 Responsible Manager 1.3 Safety Management System

  1. Personnel (8–12 pages)

2.1 Pilot Qualifications 2.2 Maintenance Personnel 2.3 Training Records 2.4 Competency Requirements

  1. Aircraft & Equipment (10–15 pages)

3.1 Aircraft Registry 3.2 Technical Specifications 3.3 Maintenance Plan 3.4 Equipment Limitations

  1. Operating Procedures (15–25 pages)

4.1 Standard Operating Procedures 4.2 Pre-flight Checklist 4.3 Flight Planning 4.4 Airspace Coordination 4.5 Emergency Procedures

  1. Safety (8–12 pages)

5.1 Risk Assessment 5.2 Incident Reporting 5.3 Insurance Verification

  1. Records Management (3–5 pages)

6.1 Documentation Format 6.2 Retention Policy 6.3 Audit Procedures `` Total length: typically 50–100 pages for a small-to-medium operation.

The Approval Process: What Transportstyrelsen Expects

Moo (MmowW Founder)

Moo: "How long does it take to get a DOM approved?" Piyo: "First submission usually comes back with comments. You revise, resubmit. Most operators see approval in 4–8 weeks." Moo: "What makes Transportstyrelsen approve it?" Piyo: "Completeness, clarity, and proof you actually live these procedures. They'll eventually conduct a site audit to verify."

::: Transportstyrelsen's approval timeline:

Week 1–2: Preparation
  • Draft your DOM using EASA templates
  • Internal review for completeness
  • Submit to Transportstyrelsen online portal

Week 3–4: Initial Review
  • Transportstyrelsen checks for obvious gaps
  • Requests clarifications or additions (very common)
  • Communicates via email with specific revision requests

Week 5–6: Revision & Resubmission
  • You address comments
  • Resubmit revised version
  • Transportstyrelsen re-reviews

Week 7–8: Approval or Final Requests
  • If satisfactory: Approval issued (written letter)
  • If gaps remain: Additional revision cycles

Post-Approval: Compliance Audits
  • Transportstyrelsen conducts initial audit (typically 1–2 months post-approval)
  • They verify your operations actually match the DOM
  • No surprise findings = you're good for 2–3 years

Common resubmission reasons:

  • Incomplete personnel qualifications section
  • Missing risk assessment procedures for specific operation types
  • Vague emergency procedures (too generic)
  • No clear data protection/privacy procedures
  • Maintenance intervals not aligned with manufacturer specs

Key Content Pitfalls to Avoid

Pitfall 1: Generic Copy-Paste from Templates

Transportstyrelsen can tell when a DOM is boilerplate. They look for company-specific details: your exact aircraft, your specific airspace, your team's actual qualifications.

Pitfall 2: No Integration of EASA Risk Categories

Your procedures must explicitly address A1, A2, or A3 operations you intend. A DOM that doesn't mention your planned operation type is incomplete.

Pitfall 3: Vague Emergency Procedures

"In an emergency, the pilot will take appropriate action" is useless. Specify: "If motor failure occurs above 50m altitude, pilot will activate parachute system and glide to designated emergency zone" (or equivalent for your platform).

Pitfall 4: No Data Security/Privacy Procedures

Modern operations collect sensitive data (building inspections, agricultural analysis, etc.). DOM must address data storage, access control, retention, and GDPR compliance.

Pitfall 5: Missing Third-Party Coordination

If you use external technicians, maintenance services, or data processors, the DOM must name them and describe their procedures. This assures Transportstyrelsen you've vetted vendors.

MmowW's Operations Manual Support

Poppo (Compliance Expert)

Poppo: "Building a DOM from scratch is 40–60 hours of writing and coordination. Then keeping it current as regulations shift and your operations expand." Moo: "Does MmowW handle that?" Poppo: "It generates template DOMs pre-loaded with Swedish regulatory requirements. You customize it with your details, get Transportstyrelsen-ready docs in days instead of weeks."

::: MmowW includes:

  • DOM templates — EASA/Transportstyrelsen-compliant starting point with Swedish-specific sections
  • Auto-population — Pull aircraft specs, pilot credentials, maintenance schedules from your MmowW database
  • Audit trail — Changes tracked with timestamps, ready for version control reviews
  • Update management — When Transportstyrelsen guidance changes, MmowW templates automatically refresh
  • Multi-language support — Export in English or Swedish as needed

For Swedish operators, this cuts DOM preparation from 8 weeks to 2–3 weeks, reducing approval delays significantly.

FAQ

Q: Do I need a DOM if I only operate A1 drones?

A: Transportstyrelsen doesn't require a formal DOM for simple A1 operations. But best practices dictate documenting basic procedures. If you plan to scale or add A2 operations later, build your DOM now.

Q: How often must I update my DOM?

A: Annually at minimum. More frequently if operations change significantly (new aircraft, new airspace categories, personnel changes). Transportstyrelsen treats a stale DOM as noncompliance.

Q: Can I use a DOM template from another EU country?

A: Templates help, but you must customize to Swedish requirements. Transportstyrelsen will reject a DOM written for German or French regulations—it won't address Transportstyrelsen-specific procedures.

Q: What if my operation is very small (just me, one drone)?

A: Even solo operations need a DOM. It can be concise (15–20 pages), but it must cover your qualifications, aircraft specs, procedures, and safety practices.

Q: Does the DOM approval expire?

Stop DOM delays. Get Transportstyrelsen-ready operations manuals fast. MmowW simplifies compliance documentation at kr67/drone/month. Build Your DOM Now