Unmanned Canada helps organizations screen the likely Canadian operating pathway, structure a defensible concept of operations, identify evidence gaps and prepare the documentation needed for complex RPAS and BVLOS projects.
Important: Unmanned Canada provides operational planning and documentation support. It does not issue SFOC-RPAS approvals, RPOCs, pilot certificates or airspace authorizations, and this service does not guarantee approval. Transport Canada, NAV CANADA and other responsible authorities make final decisions.
Canada’s framework now includes lower-risk BVLOS under Level 1 Complex operations. Missions outside that framework may still require an SFOC-RPAS. A proper review tests the complete operation before selecting the application path.
Some projects can be redesigned to remain within an applicable VLOS, sheltered or EVLOS pathway instead of proceeding directly to an SFOC.
Applicable lower-risk BVLOS operations require the correct pilot privileges, an RPAS Operator Certificate and an eligible aircraft/system.
Operations outside the applicable Basic, Advanced or Level 1 Complex rules may require a project-specific SFOC-RPAS and supporting evidence.
An SFOC does not automatically replace airspace, site, landowner, airport, DND, Parks Canada or other permissions that may apply.
Choosing the wrong route can create unnecessary work, missing evidence or an application that does not match the mission. The pathway should be reconfirmed whenever the route, aircraft, population, airspace, altitude, payload, crew model or operating method changes.
The result identifies a useful review starting point. It is not a legal classification, operational permission or substitute for the current regulations, standards, advisory circulars or authority direction.
Test whether the complete mission may fit the current lower-risk BVLOS framework before preparing an SFOC application.
Define why the mission sits outside an applicable lower-risk pathway and identify the operational and technical evidence needed for review.
Separate the SFOC-RPAS workstream from air-navigation, aerodrome, airport, DND, site or other permissions that may also be required.
Screen advertised events, foreign operators or aircraft, unusual payloads, high-altitude work and other missions that may trigger a distinct SFOC-RPAS route.
The engagement can cover one missing document or coordinate a complete readiness package. Scope, deliverables and responsibilities are confirmed before work begins.
Review the mission against the likely current operating and application pathway.
Describe what will happen, where, with which system, under whose control and within which limits.
Organize hazards, assumptions, controls and evidence around the intended operation.
Prepare and align applicant-owned forms, manuals, procedures, supporting records and attachments.
Help organize responses, revisions and supporting evidence requested during an authority review.
Translate conditions and approved procedures into a controlled operational deployment.
A strong package connects the stated operating model to the people, aircraft, procedures and proof that support it. Exact requirements depend on the mission and official application route.
Purpose, route, altitude, duration, locations, airspace, population, terrain, weather and operating frequency.
Aircraft configuration, payload, C2 link, navigation, containment, detect-and-avoid approach and supporting equipment.
Pilot and crew qualifications, operator roles, supervision, training, recency and decision authority.
Planning, site setup, launch, route management, monitoring, recovery, deviations and abnormal-event response.
Lost-link, navigation, weather, traffic, landing, fly-away, communications and escalation planning.
Configuration control, inspection, defects, maintenance, software, batteries, flight records and corrective action.
Airspace, aerodrome, landowner, municipal, provincial, federal, client and other coordination dependencies.
Validation, rehearsal, audit, incident reporting, performance review and control of changes after approval.
Changes to the route, aircraft, crew model or operational limits can affect the application. The process uses controlled decisions and clear evidence owners.
The certificate or operator pathway is only one part of readiness. The deployed system must remain supportable, repeatable and aligned with every applicable condition.
Role-specific certification, training, competency, recency and supervision.
Aircraft, payload, C2, navigation, detect-and-avoid or observer model and supporting equipment.
Usable procedures, checklists, limits, abnormal actions and emergency response.
Current permissions, operating-area knowledge, stakeholder coordination and local constraints.
Maintenance, configuration, software, batteries, defects, spares and records.
Review changes before they invalidate assumptions, documents, permissions or conditions.
Requirements and processing depend on the complete operation and the quality of the submitted information.
No. Some lower-risk BVLOS operations may fit the Level 1 Complex framework when the operator, pilot, aircraft and operating conditions meet all applicable requirements. Other BVLOS operations may still require an SFOC-RPAS.
Level 1 Complex provides a defined pathway for applicable lower-risk BVLOS operations and works with an RPAS Operator Certificate. An SFOC-RPAS is used for special operations outside the applicable Basic, Advanced or Level 1 Complex rules. The mission facts determine which route should be reviewed.
Unmanned Canada can support planning, drafting, evidence organization and readiness review. The applicant controls and remains responsible for the submission. Transport Canada controls its review and decision, so approval cannot be guaranteed.
Not automatically. NAV CANADA, DND or another controlling authority may require a separate airspace process. Other airport, aerodrome, site, landowner or agency permissions may also apply.
Transport Canada publishes service standards by application complexity, but actual timing can vary with completeness, complexity, fees and responses to information requests. Project planning should allow time for preparation, official review, revisions and other permissions.
Yes. The scope can address the remote operating concept, aircraft and Dock system, communications, supervision, procedures, site, airspace, maintenance, cybersecurity responsibilities and application evidence. Exact requirements depend on the deployment.
They can be scoped separately. Unmanned Canada can help align the application assumptions with a suitable enterprise platform, payloads, software, communications, training and lifecycle-support plan.
Provide the mission purpose, proposed route and locations, aircraft, payload, altitude, distance, population and airspace context, crew model, current certifications, target timing and existing documentation. Do not send credentials or protected files through the website form.
Share enough operational context to support an initial pathway and scope review. Exact application requirements will be confirmed against the current official framework.
Complex missions succeed when the application assumptions match the system and the team that will operate it.
