Operation Classification
Define the intended mission, visual-line-of-sight model, environment, airspace, proximity, altitude and other conditions that influence the pathway.
Unmanned Canada helps organizations review an intended RPAS operation, identify the likely Canadian compliance pathway, organize supporting documentation and build practical procedures around the way the program will actually operate.
Advisory scope: Unmanned Canada provides operational planning and documentation support. This service is not legal advice or government authorization. Transport Canada, NAV CANADA and other applicable authorities make final decisions on certificates, permissions and approvals.
A useful compliance review starts with the real mission. It then connects the operating category, people, aircraft, airspace, site conditions and records into one defensible way of working.
Define the intended mission, visual-line-of-sight model, environment, airspace, proximity, altitude and other conditions that influence the pathway.
Review pilot certificates, crew roles, supervision, training, recency and the competencies needed for the intended operation.
Confirm registration, declarations or technical eligibility where applicable, plus configuration, maintenance and supporting equipment.
Build procedures, checklists, emergency planning, authorizations and records that support consistent decisions before, during and after flight.
This planner identifies a sensible review starting point. It does not determine legal eligibility or replace the current Canadian Aviation Regulations, standards, advisory material or authority direction.
Define the mission, proposed aircraft, people, sites and deliverables before deciding which operating category, permissions and internal controls need deeper review.
Compare the new site and mission profile with the team’s existing privileges, aircraft eligibility, local constraints and required coordination.
Screen whether the concept may fit an applicable Level 1 Complex pathway or requires SFOC-RPAS planning, then map operator, pilot, aircraft and evidence requirements.
Compare current practice with documented procedures, qualifications, aircraft records, approvals and the latest requirements affecting the operation.
The scope can focus on one application or support a broader enterprise program from initial classification through recurring governance.
Map the mission and current capabilities to a preliminary Canadian operating pathway.
Turn the operating model into usable procedures, responsibilities and controlled records.
Help organize the operational concept, evidence, forms and supporting material for an applicant-led submission.
Prepare governance, personnel, system and documentation workstreams for applicable complex operations.
Organize the information and internal decisions needed before official airspace or site coordination.
Check whether the documented program still reflects current operations, equipment, roles and requirements.
Every engagement is scoped around the operation and the decisions still outstanding. Deliverables vary, but the review logic stays consistent.
The final document set depends on the pathway and scope. These are common workstreams—not a universal application checklist.
Mission purpose, operating environment, system, roles, locations, limits and expected frequency.
Planning, site assessment, weather, airspace, pre-flight, flight, post-flight and abnormal procedures.
Response logic, escalation, contacts, lost-link or system-event actions and post-event reporting.
Required qualifications, role training, platform skills, recency, assessment and records.
Registration, applicable declarations, configuration, maintenance, defects and service history.
Flight logs, site reviews, authorizations, incidents, changes, audits and corrective actions.
Depending on the facts, a program may need to consider Basic, Advanced, Level 1 Complex/RPOC or SFOC-RPAS requirements, together with airspace, site, aircraft and organizational controls.
Review the mission against the privileges, limits, aircraft and pilot requirements that apply.
Assess lower-risk complex-operation planning, pilot, operator and aircraft workstreams where applicable.
Organize operator responsibilities, policies, procedures, records and operational assurance.
Prepare applicant-owned information for operations outside other applicable categories.
Plan the information, timing and internal controls required before seeking official permission.
Connect Dock, BVLOS, multi-site and remote-supervision concepts to governance and authorization planning.
Regulations, standards, guidance, forms and service requirements can change. The applicable official sources must be checked for every engagement and before operation.
A strong review makes requirements, gaps and responsibilities clearer. It does not replace regulator or air-navigation decisions.
No. This is operational and documentation support for RPAS programs. Obtain qualified legal advice when the matter requires a legal opinion or interpretation.
No. Transport Canada, NAV CANADA and other applicable authorities control their own certificates, permissions, assessments and processing decisions.
Unmanned Canada can review the facts and identify a likely pathway and gaps. The conclusion must be checked against the current regulations, standards, official guidance and any direction from the responsible authority.
Yes, the scope can include planning, document development, evidence organization and a completeness review. The applicant remains responsible for the submission and the authority makes the decision.
Not automatically. Training and qualification needs can be identified, then scoped through the appropriate training service. Certificate and flight-review requirements depend on the intended operation.
Yes. A review can compare documented procedures with current practice, qualifications, fleet records, approvals, operational records and the requirements affecting the program.
Yes. The service can address the operating concept, governance, people, technical system, procedures and readiness evidence. The exact authorization path depends on the operation and current framework.
Provide the mission, proposed aircraft, operating locations, airspace context, people, timing, current qualifications and a list of existing documents. Do not send credentials, protected data or controlled project files through the web form.
Share the mission, aircraft, location, team and current stage. Unmanned Canada can recommend a practical starting scope.
A defensible program needs qualified people, suitable aircraft, usable procedures and an operating model that stays current.