SFOC-RPAS Service Standards: What 20, 30, and 60 Business Days Mean for Your Field Season

Transport Canada's published SFOC-RPAS service standards turn approval timing into a planning input. The agency lists targets of 20 business days for special aviation events, 30 business days for very low and low complexity applications or minor amendments, and 60 business days for medium and high complexity applications.

Those are service standards, not promises for every project. Transport Canada says timing depends on the complexity and completeness of the application, and the clock starts after the department has a complete application and the required fees.

Use the published standard as a minimum planning input

A 20, 30, or 60 business-day target should be placed on the project schedule before crews, travel, and client commitments are locked. The longest category can span roughly twelve working weeks before holidays or additional coordination are considered. Treat that as a planning estimate, then add room for internal review and client decisions.

The point is not to delay every project. It is to identify early whether the intended operation needs an SFOC-RPAS and whether the project plan can support a complete submission.

Completeness is part of the schedule

Transport Canada's Advisory Circular 903-002 explains the application process and the information operators should prepare. Build a completeness review into the internal schedule: operating area, dates, aircraft information, pilot qualifications, procedures, emergency planning, supporting permissions, and the material needed for the type of operation proposed.

A team that sends an incomplete package has not started a reliable clock. Assign one person to confirm that the narrative, attachments, and client-provided site information tell the same operational story.

Plan the field season backward from the operation

Start with the first day the operation needs to occur, then work backward through client approvals, site access, internal safety review, SFOC-RPAS preparation, and the published service standard. Revisit that plan when the location, aircraft, altitude, dates, or operational concept changes.

This discipline also makes client conversations easier. Instead of offering a vague approval estimate, the team can explain which pieces of the application are ready, what remains open, and how those items affect the planned field window.

Keep the current sources close

The Drone Zone service-standard notice and AC 903-002 should be part of the project file. They will not replace a case-specific review, but they provide a better planning baseline than treating approvals as a last-minute administrative task.

Sources: Transport Canada Drone Zone Issue 7 and Advisory Circular 903-002.