How to Prepare a Complete SFOC Application for Transport Canada

What Is an SFOC?

A Special Flight Operations Certificate (SFOC) is a Transport Canada authorization that permits drone operations that fall outside the standard rules for certified pilots. It's not a certificate you hold - it's a permit for a specific operation or class of operations.

Think of it as Transport Canada's way of saying: "This operation is complex enough that we want to review it before it happens."

Your pilot certificate must be valid for the full duration of any SFOC operation. If your 24-month recency period ends during the operation, complete a qualifying activity before you submit. See our guide on keeping your RPAS certificate current for the recency options.

When Do You Need an SFOC?

You need an SFOC for operations that exceed normal Advanced certificate permissions, including:

• Drones over 150kg - since November 4, 2025, medium drones (25–150kg) can fly within visual line of sight without an SFOC if they meet Transport Canada's medium category requirements. Above 150kg still requires an SFOC.
• Beyond Visual Line of Sight (BVLOS) - any BVLOS operation that falls outside the lower-risk BVLOS rules introduced in November 2025 (for example over populated areas or in controlled airspace)
• Flying over crowds or assemblies - events with large numbers of people where standard rules don't provide adequate separation
• Night operations in certain airspace classes
• Certain classified airspace where standing authorization isn't available
• Operations near aerodromes in ways not covered by Nav Canada's RPAS authorization systems

Many commercial operators dealing with infrastructure inspection, search and rescue, or large-scale aerial surveys will encounter SFOC requirements regularly.

Types of SFOC

Transport Canada issues two main types:

• Single-event SFOC: Covers one specific operation at a defined location and time. Issued for one-off projects.
• Standing SFOC: Covers a class of recurring operations (e.g., regular pipeline inspection corridors). More complex to obtain but eliminates the need to reapply for every flight.

Standing SFOCs require demonstrated operational history and a robust safety management system. Most operators start with single-event SFOCs and apply for standing authorization once they've built a track record.

What TC Looks For in a Complete Application

Transport Canada evaluates SFOC applications on risk - the goal of your application is to demonstrate that you've identified the risks and have credible mitigations for each. A complete submission typically includes:

1. Operation Description

A precise description of what you're doing: location, altitude, duration, frequency, purpose. Vague descriptions slow the review. Include GPS coordinates or a map if the location is specific.

2. Aircraft and Equipment Information

• Drone make, model, registration number
• Maximum takeoff weight
• Propulsion type, endurance, failsafe modes
• Any payload (camera, sensor, cargo) and its weight

3. Pilot Information

• RPAS certificate number and proof of recency
• Flight hours on this aircraft type
• Any previous SFOC history

4. Risk Assessment

This is the most important section. Identify each hazard (airspace conflicts, loss of control, communication failure, weather, ground risk) and describe your mitigation. TC reviewers are looking for proportionality - the mitigation should match the severity and likelihood of the risk.

The SORA framework: TC increasingly expects SFOC applications for complex operations - particularly BVLOS - to align with the Specific Operations Risk Assessment (SORA) methodology. SORA, developed by JARUS (Joint Authorities for Rulemaking on Unmanned Systems), provides a structured approach for quantifying drone operation risk. Even if TC does not explicitly require SORA for your application, aligning your risk assessment with its structure demonstrates professional rigor and typically results in faster review.

SORA evaluates two dimensions:

• Ground Risk Class (GRC): Based on population density below the intended flight path. A flight over open farmland has a lower GRC than one over a suburban neighbourhood. TC reviewers look at the density of people and structures in the operational area and buffer zone. Documenting the population density of your operating area - not just its GPS coordinates - strengthens your application.
• Air Risk Class (ARC): Based on the airspace class and traffic intensity at the operating altitude. Class G airspace with minimal manned traffic has a lower ARC than Class D near a controlled aerodrome. Cross-referencing Nav Canada traffic data for the area during your planned operation window is advisable for any SFOC near an aerodrome.

Risk assessment mini-template structure:

1. Hazard identification: Name the specific hazard (e.g., loss of command-and-control link)
2. Likelihood: Assess how probable the hazard is given your equipment, environment, and procedures
3. Severity: Assess the consequence if the hazard occurs (minor, serious, catastrophic)
4. Mitigation: Describe the specific procedure, equipment feature, or protocol that reduces either likelihood or severity
5. Residual risk: Confirm the risk level after mitigation is acceptable for the operation

Repeat this structure for each significant hazard. Generic hazard lists copied from templates are the most common reason TC requests supplementary information, adding weeks to your timeline.

5. Emergency and Contingency Procedures

What happens if the drone malfunctions, loses comms, or needs to land immediately? Who is the emergency contact? What's the recovery procedure?

6. Airspace Coordination

Evidence that you've coordinated with Nav Canada, the relevant airport control, and any other parties who manage the airspace you'll operate in.

Near aerodromes: For operations within or near an aerodrome's zone, you need to contact both the airport authority (the organization managing the airport) and Nav Canada's NOTAMs office. These are separate steps. The airport authority manages the physical infrastructure and may have site-specific restrictions. Nav Canada manages airspace and issues NOTAMs that inform other airspace users of your operation. Do both, and document both with timestamps and reference numbers.

For BVLOS specifically: BVLOS operations near active airspace require more than a NOTAM - you may need to coordinate directly with ATC, not just notify them. ATC coordination means establishing a communication protocol for your operation, confirming how your crew will remain informed of relevant air traffic, and potentially receiving real-time traffic advisories during your flight. Document this coordination in your application. Notification is not the same as coordination; TC reviewers know the difference.

Document everything: Keep email records of all coordination, including timestamps, the names and roles of people you contacted, and any reference numbers assigned. If TC questions your airspace coordination, you need to produce a clear paper trail. Screenshots of emails and logged phone calls (date, time, person contacted, outcome) are both acceptable.

7. Liability Insurance

Insurance is not required for standard operations, but Transport Canada may ask for proof of insurance with an SFOC application. Commercial operations typically carry $1M–$5M in third-party liability. Include your certificate of insurance.

BVLOS SFOC: Special Considerations

A BVLOS SFOC is in a different category of complexity from a standard SFOC. If you're planning to pursue BVLOS authorization, the following applies:

Technical documentation requirements: TC expects BVLOS applications to include documentation of your detect-and-avoid capability - how your system detects other aircraft and takes action to avoid collision. This typically requires technical specifications from the manufacturer and, in some cases, test data. TC also expects command-and-control link reliability data: what is the link's effective range, what happens when it degrades, and what are the automatic failsafe behaviors? These are not soft requirements - applications that omit them will receive information requests.

Crew coordination procedures: A BVLOS operation requires documented crew roles. Who is the Remote Pilot in Command? Who are visual observers, and what are their handoff procedures? How does the crew communicate? What are the go/no-go decision authority rules? These must be in writing in your application, not described informally.

Timeline for first-time BVLOS SFOC: Allow 3–6 months for a first-time BVLOS SFOC application. This is not a reflection of TC being slow - it reflects the volume of documentation required and the number of information requests that are normal for first-time applicants. Build the timeline into your project planning before committing to a client delivery date.

Standing BVLOS SFOC requires demonstrated history: TC will not issue a standing BVLOS authorization without documented evidence of prior successful BVLOS operations. The typical pathway is to conduct 25 or more documented BVLOS flights under single-event SFOCs first, then apply for standing authorization with those flight records as supporting evidence. "Documented" means detailed flight logs with dates, locations, duration, and conditions - not just a general claim of experience.

Common Mistakes That Delay Applications

• Incomplete aircraft data: Missing the registration number or failsafe documentation
• Generic risk assessments: Copying a template without adapting it to the actual site and operation
• No airspace coordination: Forgetting to contact Nav Canada or the local airport authority before submitting
• Submitting too close to the operation date: TC recommends 20 business days for standard applications. Complex BVLOS operations can take significantly longer.
• Expired pilot credentials: Your RPAS certificate must be valid for the duration of the operation

What Happens After You Submit

The period between submission and decision is not passive waiting - it's an active phase that requires your attention.

File number assignment: When TC receives your application, the regional office assigns a file number. Always ask for this number in your submission or follow-up. The file number is your reference for all future communication about the application. Without it, tracking your application's status becomes significantly harder.

Supplementary information requests: TC may come back with requests for additional information - clarification on your risk assessment, additional equipment documentation, or confirmation of airspace coordination. Respond within 5 business days. Delays in your response reset TC's review timeline, not just pause it. Prompt, thorough responses are the single biggest factor in application processing speed that you control.

SFOC conditions: Most SFOCs are issued with conditions. These conditions are legally binding - operating outside them voids your authorization. Common conditions include maximum altitude limits, weather minimums (wind speed, visibility, ceiling), crew requirements (minimum crew size, mandatory observer positions), and equipment requirements (specific failsafe settings). Read the conditions carefully and build them into your operational briefing. Many enforcement actions arise from pilots who received an SFOC but flew outside its stated conditions.

Amendment process: If your operation changes after the SFOC is issued - different dates, different location, different aircraft - you may need an amendment. Do not assume the original SFOC covers the modified operation. Contact TC proactively, explain the change, and request an amendment in writing. Amendments are typically faster to process than new applications, but they require TC's explicit approval before you proceed with the modified operation.

Record-Keeping Requirements

Compliance doesn't end when the SFOC is issued - it continues through and after the operation.

On-site availability: The SFOC must be available on-site or digitally accessible during the operation. If a TC inspector or law enforcement officer asks to see your authorization during a flight, you must produce it. A digital copy on your phone or tablet is acceptable - a claim that "it's in the office" is not.

Flight log references: Your flight logs for SFOC operations should reference the SFOC number on each entry. This creates a traceable record linking your logged flights to the authorization that covered them. If TC ever audits your operations, this documentation demonstrates that your flights were authorized and conducted within the SFOC's conditions.

Incident reporting obligations: If anything goes wrong during an SFOC operation - a drone crash, a near-miss with manned aircraft, a loss of control - you have reporting obligations to Transport Canada under the Aeronautics Act. Reporting timelines are tight (some incidents require immediate notification). Failure to report a reportable occurrence is itself a violation, separate from the incident that triggered the reporting requirement. Know TC's reportable occurrence criteria before you fly.

Timeline and Process

1. Prepare your full package (use the TC SFOC application form available at tc.canada.ca)
2. Submit by email to the Transport Canada regional office responsible for your operating area
3. TC may request clarification - respond promptly; delays in your response add to the timeline
4. SFOC is issued (or denied) with conditions - read conditions carefully before flying
5. Keep the SFOC on-site or readily available during the operation
6. Retain flight logs referencing the SFOC number post-operation

If your operation is near a national park or protected area, Parks Canada may also require a Special Use Permit in addition to your SFOC. These are separate authorizations from separate agencies - neither substitutes for the other. Read our complete guide to flying near Canadian national parks for the Parks Canada permit process.

Tracking Your SFOCs

If you're managing multiple operations across different sites and time windows, keeping track of which SFOC covers which operation - and when each expires - becomes a real administrative challenge. Complifly's compliance tracking lets you log SFOCs alongside your other certifications, with expiry alerts so nothing lapses mid-project.

Summary

• SFOCs are required for drones over 25kg, BVLOS, crowd operations, and other high-risk scenarios
• Apply at least 20 business days before your operation - 3–6 months for complex BVLOS projects
• The risk assessment is the core of your application - use SORA-aligned structure: hazard, likelihood, severity, mitigation, residual risk
• Coordinate with Nav Canada (NOTAMs) and local airport authority separately - document both with timestamps
• After submission: ask for a file number, respond to TC information requests within 5 business days, read SFOC conditions carefully before flying
• Keep the SFOC on-site, reference the SFOC number in flight logs, and know your incident reporting obligations
• Your RPAS pilot certificate must be valid for the full duration of the operation