Drone Flight Log Requirements Canada: RPOC & Advanced Operator Guide

:::

:::

Transport Canada Requirements: Flight Logs as Core SMS Documentation

When you hold an RPOC (Remote Pilot Operator Certificate) or operate as an Advanced Operator in Canada, you must maintain a Safety Management System (SMS). Flight logs are a mandatory part of that SMS. Transport Canada recognizes two operator categories:

• RPOC Operators – Certified professionals running commercial operations
• Advanced Operators – Non-certified operators flying advanced flights (BVLOS, night, etc.) under exemption

Both must keep equivalent records.

What Must Be Recorded in Every Flight

Transport Canada's Appendix A of the Drone Regulations specifies mandatory flight record elements. Here's what you must capture:

1. Pilot Information

• Remote Pilot in Command (PIC) name
• Pilot Certificate number (shows you're current and authorized)
• Visual Observer (VO) name and role (if you use a VO)
• Date pilot conducted the operation

1. Aircraft Details

• Aircraft registration (tail number or serial if registered)
• Aircraft model and manufacturer
• Serial number of the platform
• Total flight time on that aircraft (cumulative)

1. Operation Identification

• Date of operation (YYYY-MM-DD format, ISO 8601)
• Start time and end time (24-hour format, UTC or local timezone consistently)
• Duration of flight (total airtime)
• Number of flights/sorties if multiple takeoffs that day

1. Flight Details

• Takeoff location (GPS coordinates, address, or grid reference)
• Landing location (where you returned to)
• Maximum altitude achieved (in feet or metres, state which)
• Operational area (describe the geography or airspace)

1. Operation Type & Purpose

• Operation category (VLOS, BVLOS, night, advanced, etc.)
• What the flight was for (inspection, surveying, training, testing, etc.)
• Client name (if commercial operation)
• Project identifier (helps track multiple flights for one client)

1. Weather & Environmental Conditions

• Wind speed and direction at takeoff and landing
• Visibility (meters or feet)
• Precipitation (rain, snow, etc.)
• Temperature (optional but recommended)
• Ceiling/cloud base (if relevant to your operation)
• Demonstrates you operated within your SMS weather minimums

1. Airspace & Restrictions

• Airspace class (Class A, B, C, D, E, F, G)
• Distance from nearest airport or controlled airspace
• If near an airport, note any ATC coordination (clearance number, frequency)
• Notam (Notice to Airmen) if filed—include reference number

1. Safety & Operational Issues

• Any incidents, accidents, or near-misses
• Equipment malfunctions or warnings
• Loss of control or signal
• Any deviation from planned operation
• Corrective actions taken in response

1. Maintenance & Equipment Status

• Battery condition (cycles, voltage, any issues)
• Any maintenance performed or noted issues
• Equipment failures or limitations affecting the flight

:::

SMS Integration: Why Flight Logs Matter

Your Safety Management System (SMS) is the umbrella that covers all your operations. Flight logs feed directly into it:

• Continuous improvement: Logs show patterns (e.g., "We frequently lose GPS signal near this location—we need to adjust procedures")
• Risk assessment: Logs document hazards encountered and how you mitigated them
• Training needs: Logs identify gaps (e.g., "Pilots struggled with crosswind landings")
• Audit trail: When Transport Canada inspects you, logs prove your SMS is active and working

Your SMS documentation should include:

• [ ] Mandatory flight log template (ensure it captures all required fields above)
• [ ] Instructions on when/how to complete logs (within 24 hours recommended)
• [ ] Procedures for reporting incidents from flight logs
• [ ] Retention schedule (minimum periods are below)
• [ ] Training requirements for staff on log accuracy

:::

:::

Retention Period: How Long to Keep Records

Transport Canada requires:

• Active records: 24 months minimum (must be retrievable within hours if requested)
• Archive records: Keep indefinitely for incident-related flights
• Safety case records: Maintain for the life of your business (they support your SMS)

Practical retention schedule:

• Year 1: Keep in active system (easy access)
• Years 2-3: Archive (cloud storage, backed up)
• Year 4+: Long-term archive (if involved in incident history)

If you're ever involved in a complaint, incident, or regulatory inquiry, retain those records indefinitely.

How Transport Canada Inspects Flight Records

Transport Canada conducts compliance audits and surveillance of drone operators through Civil Aviation Medicine (CAM) and Regional offices.

Inspection Triggers

Transport Canada may request to inspect your flight records if:

• Routine audits (RPOC holders are audited periodically)
• Incident or accident involving your aircraft
• Safety complaint from public or manned aviator
• Certificate renewal (you must provide audited records as part of application)
• Advanced operation approval (BVLOS, night, beyond-VLOS-distance for Ops)
• Insurance claim related to drone operations

What Inspectors Look For

When Transport Canada reviews your flight records, they verify: ✓ Completeness: All required fields filled in for each operation ✓ Accuracy: Dates, times, aircraft details align across logs ✓ Consistency: Pattern of operations matches your SMS and Certificate scope ✓ Incident Reporting: Any incidents documented and reported to Transport Canada ✓ Pilot Authorization: All flights conducted by certificated remote pilots ✓ SMS Alignment: Operations stay within your approved limits (altitudes, airspace, etc.) ✓ Weather Compliance: Operations logged within your SMS weather minimums

Red Flags During Inspection

• Missing logs for operational periods (suggests records aren't maintained)
• Blank or incomplete entries (shows lack of diligence)
• Backdated entries (indicates logs weren't contemporaneous)
• Operations outside SMS scope (e.g., flying BVLOS when not approved, or in restricted airspace without clearance)
• Incidents not reported (demonstrates non-compliance with incident notification rules)
• Inconsistent data (e.g., logged 50 flights but only 40 battery charges)

:::

Digital vs Paper: Best Practices for Canadian Operators

Digital Systems (Recommended)

Advantages:

• Automatic timestamps (proves contemporaneous recording)
• Searchable and organized
• Easy to backup
• Rapid export for Transport Canada requests

Tools:

• Spreadsheets (Excel, Google Sheets) – Free, flexible
• Dedicated flight log apps (DJI FlySafe, custom SMS software)
• Cloud-based SMS systems (best for multi-pilot, multi-aircraft operations)

Paper Logs

Acceptable but risky:

• Portable (good for field operations)
• Can be lost or damaged
• Difficult to search quickly during audits
• Must photograph/scan monthly as backup

Best practice if using paper:

• Use bound logbook (harder to claim pages are missing)
• Photograph every page monthly
• Store scans in cloud backup (Google Drive, Dropbox, OneDrive)
• Include cross-references (page numbers, date indexes)

Building a Compliant Flight Log System

Step 1: Design Your Template

Include all required fields plus any SMS-specific fields:

Required (Transport Canada):

• [ ] Pilot name and cert number
• [ ] Aircraft model and serial
• [ ] Date, start/end time
• [ ] Location (takeoff and landing)
• [ ] Max altitude
• [ ] Weather (wind, visibility)
• [ ] Purpose/operation type
• [ ] Any incidents

Recommended (SMS/best practice):

• [ ] Visual Observer (if used)
• [ ] Battery cycles
• [ ] Maintenance notes
• [ ] Airspace class
• [ ] ATC coordination
• [ ] Corrective actions taken

Step 2: Establish Recording Procedures

Document how and when logs are completed:

• [ ] Pilot completes essential info during/immediately after flight
• [ ] Supervisor reviews logs for completeness within 24 hours
• [ ] Any gaps or errors are corrected with notes explaining why
• [ ] Digital backup occurs automatically (cloud) or manually (weekly for paper)

Step 3: Train Your Team

• [ ] Every pilot understands what fields are required
• [ ] All staff know the incident reporting threshold
• [ ] Someone is designated as "SMS record keeper" (maintains backups and archives)
• [ ] Annual refresher on record-keeping standards

Step 4: Monthly Audit Check

• [ ] Verify 100% of flights are logged
• [ ] Check for obvious errors (date typos, missing times, etc.)
• [ ] Review incidents for completeness
• [ ] Test backup system (retrieve archived logs to ensure they're accessible)

Incident Reporting Integration

Flight logs connect directly to your incident reporting obligations:

Minor incidents (logged in flight records):

• Equipment warning lights (recoverable)
• Brief GPS signal loss (momentary)
• Minor battery anomaly (resolved before landing)

Reportable incidents (must report to Transport Canada):

• Loss of control / inability to recover
• Injury or property damage
• Near-miss with manned aircraft
• Damage to the drone requiring major repair

Your procedure:

1. Log the incident in flight records with full details
2. If reportable, file an incident report to Transport Canada within 24-72 hours (check your SMS for specifics)
3. Document corrective actions taken to prevent recurrence
4. Update training if the incident reveals a safety gap

FAQ

Q: Do I need Transport Canada approval for my log template?

A: No, but your SMS document should describe your log template. If Transport Canada audits you, they'll review it for completeness. Standard templates covering the required fields are fine.

Q: What if I discover a gap in logs weeks later?

A: Add the missing information with a note: "Flight on [date] reconstructed from [source evidence]. Log entry created [date]." Honesty is better than nothing, and it's better than pretending the flight never happened.

Q: How quickly must I respond to a Transport Canada records request?

A: Typically, you have 5 working days to provide records. This is why digital backup is critical—you need to be able to export and send within hours, not days.

Q: If I have multiple pilots, do I track them separately?

A: Yes. Each flight should identify the pilot in command. Over time, this helps you spot patterns (e.g., one pilot takes longer to complete operations) and supports competency management.

Q: What happens if Transport Canada finds incomplete records?

A: They issue findings in an audit report. Minor gaps might be "observations" (no action required). Systematic incompleteness is a "non-conformance" requiring a corrective action plan within 30 days.

Q: Can I use a app like Foreflight or other aviation apps for drone logs?

A: You can use aviation apps if they capture all required fields. However, ensure they're specifically designed for drones (some general aviation apps don't include drone-specific fields). Dedicated drone logging is more reliable.

Q: Do training flights need to be logged?

A: Yes, any airborne operation is a flight and should be logged. Note the purpose as "training" so context is clear.

Q: Can I outsource flight log management?

MmowW for Canadian Operators: At just CA$7.70 per drone per month (less than a poutine), MmowW integrates flight logs directly into your SMS. Automatic timestamps, mandatory field enforcement, and instant backup mean your Transport Canada compliance is audit-ready in seconds. When inspectors arrive, export your records and demonstrate professionalism. Build trust with Transport Canada. Keep records that tell the story of safe, professional operations. Let MmowW automate the compliance work.