Complex Operations · RPOC
Operational capability and standards
An issued Transport Canada RPOC reflects documented operating procedures, organizational accountability, maintenance, training and risk management.
It is the discipline behind complex operations — not a blanket authorization.
- Operator
- RPOC issued
- Pilot
- Level 1 Complex
- Control
- Formal operating system
- Missions
- Site specific
The operator
A certificate reflects an organization — not just a pilot.
A Transport Canada RPAS Operator Certificate establishes the operator as the organization responsible for conducting applicable complex RPAS operations under a documented operating system.
- Accountability
- Defined organizational responsibility.
- Operating procedures
- Controlled processes for planning and executing missions.
- Personnel
- Training, competency and role requirements.
- Aircraft
- Acceptance, maintenance and operational status.
- Safety
- Hazard identification, risk management and corrective action.
- Records
- Traceability of operations, aircraft, training and relevant events.
The RPOC is the framework. Operational discipline is what makes the framework useful.
Behind the aircraft
The mission is controlled before it becomes airborne.
- Operational control
- Who can authorize, conduct and stop a mission?
- Mission planning
- What is being captured, where and under what operating model?
- Airspace review
- What aviation environment surrounds the operation?
- Aircraft acceptance
- Is the aircraft appropriate and eligible for the intended mission?
- Pilot competency
- Are the assigned personnel qualified for their roles?
- Maintenance control
- Is the aircraft maintained and operationally fit?
- Safety / risk
- What hazards exist and what controls are required?
- Emergency response
- What happens when the plan stops working?
- Recordkeeping
- Can important operational decisions be traced afterward?
The systems exist to control the operation. Internal manual content and procedures are not published.
Mission readiness
Before launch, the operation has to pass more than a battery check.
- 01Defined
Requirement
What information is actually needed?
- 02Reviewed
Site
What terrain, access, people and infrastructure are present?
- 03Reviewed
Airspace
What aviation constraints apply?
- 04Verified
Aircraft
Is the aircraft appropriate and eligible?
- 05Assigned
Crew
Are required roles qualified and assigned?
- 06Assessed
Risk
Are hazards understood and controlled?
- 07Assessed
Weather / environment
Are conditions within operating limits?
- 08Defined
Contingency
What happens if something changes?
- 09Ready
Go / hold
Proceed only when the operation remains acceptable.
Status language above describes the planning sequence. It is not a live operational feed.
Pilot capability
Level 1 Complex expands capability — it does not remove mission constraints.
Elev8 has Level 1 Complex pilot capability, supporting eligible complex RPAS operations where the operator, aircraft, site, airspace and other applicable requirements are satisfied.
- Pilot
- Level 1 Complex
- Operator
- RPOC issued
- BVLOS
- Mission dependent
- Aircraft
- Mission specific
- Airspace
- Site specific
- Ground environment
- Site specific
Level 1 Complex is not blanket BVLOS authority.
Aircraft
Model name alone does not determine mission eligibility.
Elev8 evaluates the aircraft against the intended mission rather than assuming that every aircraft or payload is suitable for every operation.
Aircraft eligibility is verified against the intended operation.
- Aircraft category
- Required safety assurance
- Declaration status where applicable
- Mission profile
- Payload
- Endurance
- Environmental limits
- C2 capability
- Maintenance status
- Software / firmware configuration where relevant
People
The operating system still depends on competent people.
Pilot certificates are one component of operational competency. Company training, mission-specific familiarity and clearly assigned responsibilities also matter.
- Company indoctrination
- Regulatory knowledge
- Aircraft familiarity
- Emergency procedures
- Mission-specific briefing
- Remote and field readiness
- Complex-operation competency
- Recurring competency where applicable
Airworthiness & maintenance
An aircraft should not become “ready” because the app says 100%.
Elev8 maintains a controlled process for aircraft status, maintenance, defects, inspections and return-to-service decisions.
- Status
- Current operational state of the aircraft and payload.
- Maintenance
- Scheduled and unscheduled work recorded against the airframe.
- Defect
- Reported issues captured rather than carried informally.
- Corrective action
- The work required before the aircraft is used again.
- Return to service
- A deliberate decision, not an app percentage.
Safety system
A successful mission is one that never needed to become exciting.
- Identify
- Understand hazards before launch.
- Assess
- Evaluate operational risk.
- Control
- Apply practical mitigations.
- Monitor
- Watch for changing conditions.
- Correct
- Address occurrences and recurring issues.
- Record
- Important safety decisions remain traceable.
Risk is managed, not eliminated. Elev8 does not publish safety statistics or claim risk-free operations.
Controlled operations
The operation changes when the conditions change.
Site conditions, weather, airspace, equipment and project requirements can all move away from the original plan.
- 01
Plan
The mission is built against the stated requirement and known conditions.
- 02
Verify
Conditions are confirmed on site, not assumed from the plan.
- 03
Monitor
Conditions are watched while the operation is underway.
- 04
Hold / modify
The operation is adjusted or paused when conditions move outside limits.
Schedule pressure does not override operating judgement.
Operating philosophy
More complex is not automatically more capable.
Elev8’s objective is to use the simplest compliant operating model that solves the information requirement.
- 01
VLOS
Use when efficient and appropriate.
- 02
Advanced / specialized VLOS
Add sensing, control or field capability when needed.
- 03
Level 1 Complex
Use where the mission and applicable framework justify it.
- 04
SFOC / other pathway
Where the mission falls outside routine operating rules.
Complexity should solve an operating problem — not become the product.
Clear limitations
An issued RPOC is capability, not permission to ignore the mission environment.
- Not fly anywhere
- Airspace and site restrictions still apply.
- Not blanket BVLOS
- Individual missions remain subject to applicable requirements.
- Not automatic aerodrome access
- Aerodrome and airspace considerations remain site specific.
- Not universal autonomy
- Dock-based and remote operations require separate feasibility.
- Not universal aircraft eligibility
- Aircraft requirements depend on the operation.
Good operators understand where their authority ends.
Where this capability matters
Operational discipline matters most when the project gets harder.
Rail
Long corridors, operating environments and remote access.
Utilities
Transmission, remote substations and distributed infrastructure.
Remote industrial & mining
Large sites and difficult field logistics.
Environmental / corridors
Linear terrain and remote acquisition.
Autonomous / remote
High-frequency site-specific monitoring.
BVLOS feasibility
Mission-specific advanced operations.
Partner capability
Add a regulated RPAS operating layer without building one internally.
Engineering, geomatics, environmental and infrastructure firms may only require complex RPAS capability on selected projects.
The professional team retains
- Engineering
- Surveying
- Professional interpretation
- Client authority
- Certification
Operational discipline
The important systems are usually the least visible.
- Operations manual
- Controlled
- Maintenance control
- Established
- Training
- Defined
- Safety / risk
- Established
- Regulatory records
- Maintained
- Emergency procedures
- Defined
The purpose is to show that these systems exist — not to publish their contents.
Vendor qualification
Serious clients should ask how an RPAS operator is controlled.
Ask your RPAS operator:
- 01
Who is responsible for operational control?
- 02
Is an RPOC required for the proposed operation?
- 03
Are assigned pilots properly qualified?
- 04
How is aircraft suitability verified?
- 05
How are maintenance and defects tracked?
- 06
How is mission risk assessed?
- 07
What happens when conditions change?
- 08
How are incidents and occurrences managed?
- 09
What evidence exists behind complex-operation claims?
Elev8 welcomes technical due diligence around the operating requirements relevant to the project.
Execution
Structure should reduce uncertainty — not create bureaucracy.
A controlled operating system should make routine decisions repeatable and complex decisions easier to evaluate.
- Clearer mission requirements
- Faster feasibility screening
- Repeatable field planning
- Defined responsibility
- Fewer assumptions
- Better handoff
Field proof
Standards matter when they survive contact with the field.
Planning discipline is only useful if it holds up on a remote site, in Canadian weather, with real access constraints. Project records — not badges — are the evidence.
Questions
RPOC and operational standards FAQ
An RPAS Operator Certificate is part of Transport Canada's framework for operators conducting applicable complex RPAS operations. It reflects organizational requirements beyond an individual pilot certificate.
Project qualification
Have a project where the operating environment matters as much as the sensor?
Send the site, corridor or mission requirement. Elev8 will assess the acquisition and operating model before recommending the next step.
Site · Airspace · Aircraft · Mission · Risk · Data