Complex Operations · Feasibility
BVLOS and complex mission feasibility
Site → airspace → ground environment → aircraft → mission design → regulatory pathway → deployment strategy.
An honest answer before capital is committed.
- Operator
- Issued RPOC
- Pilot
- Level 1 Complex
- Assessment
- Mission specific
- Outcome
- Go · Modify · Escalate · Stop
Mission first
“Can we fly BVLOS?” is usually the wrong first question.
The better question is what operational problem the organization is actually trying to solve. These are the pains that make a complex operating model worth considering.
- Distance
- The asset extends beyond efficient VLOS acquisition.
- Access
- Pilot repositioning requires substantial road, ATV, rail or remote travel.
- Frequency
- The same site has to be monitored repeatedly.
- Safety
- Ground access creates avoidable exposure.
- Staffing
- The current deployment model consumes too many people or too much specialist time.
- Response
- The organization needs current information without waiting for a full field mobilization.
If BVLOS does not materially improve the operating model, it may not be worth using.
Mission gates
A complex operation is only as feasible as its weakest constraint.
Eight gates are worked in sequence. Any one of them can change the operating model, the aircraft requirement, or the answer.
Gate 01 · MISSION NEED
Assessed per mission
Mission
- What needs to be captured
- How far
- How often
- What sensor
- What business outcome
Canadian operating framework
Level 1 Complex creates a pathway for lower-risk BVLOS — not universal BVLOS.
Transport Canada’s current Level 1 Complex framework permits certain lower-risk BVLOS operations when the operator, pilot, aircraft and operating environment meet the applicable requirements.
Missions beyond that framework may require an SFOC-RPAS or another regulatory pathway.
The credential establishes an operating framework. The mission determines what is actually permitted.
Requirements change. Each project is assessed against the rules applicable at the time of operation.
- Operator
- Issued RPOC.
- Pilot
- Level 1 Complex certificate.
- Aircraft
- Must satisfy the safety requirements applicable to the intended operation.
- Airspace
- Mission-specific and subject to the applicable Level 1 Complex operating limitations.
- Ground environment
- Population and site conditions materially affect eligibility.
- Mission
- Must remain within the applicable operating framework.
Feasibility outcome
A useful assessment does not always end with “yes.”
Outcome
Go
A practical operating path appears available.
Next step: detailed mission planning and deployment scope.
Outcome
Modify
The concept may work with changes.
Shorter mission segments · different aircraft · different operating area · modified route · adjusted frequency · different launch site · revised sensing requirement.
Outcome
Escalate
The mission may require more than the routine pathway.
Additional regulatory approval · SFOC pathway · additional technical systems · specialized partners · further detailed analysis.
Outcome
Stop
The technical, regulatory or economic burden currently outweighs the value.
The concept is documented so the decision does not get re-litigated every quarter.
Finding out that a project should not proceed can be a successful feasibility outcome.
Start here
Complex RPAS Feasibility Assessment
Before committing to aircraft, docks, communications infrastructure or a long-term operating model, Elev8 can assess whether the proposed mission has a realistic pathway — and what would have to be true to make it work.
The deliverable is decision clarity, not paperwork volume.
Potential assessment scope
- Project AOI
- Mission objective
- Operating frequency
- Site environment
- Preliminary airspace review
- Aerodrome considerations
- Population environment
- Aircraft requirements
- Safety-assurance / declaration considerations
- Air-risk considerations
- DAA implications where relevant
- C2 / connectivity
- Remote-site infrastructure
- VLOS vs BVLOS comparison
- Autonomous suitability
- Potential SFOC pathway
- High-level operating concept
- Major constraints
- Recommended next step
Scope is set per project. Not every assessment needs every line.
Output
A decision path — not a pile of regulations.
- Mission summary
- What the operation is trying to accomplish.
- Site / operating environment review
- Major location constraints.
- Regulatory path
- Likely operating category or approval route.
- Aircraft requirements
- What characteristics the aircraft or system would need.
- C2 / connectivity
- High-level communications requirement.
- Major risks / blockers
- What could stop or materially alter the concept.
- Operating model
- VLOS, Level 1 Complex, SFOC, remote or another pathway as appropriate.
- Next step
- Proceed, modify, investigate further, or stop.
A high-level CONOPS framework can be included where scoped. This is operational planning support, not engineering design.
Operating model
Complex does not automatically mean better.
Conventional VLOS
Often stronger when
- Site is compact
- Access is easy
- Launch locations are available
- Capture is infrequent
- Repositioning cost is low
Simpler, lower regulatory burden, easier equipment selection, lower operational complexity.
BVLOS / complex
May become attractive when
- Asset is linear
- Access is poor
- Repeated repositioning is expensive
- Site is remote
- Acquisition is frequent
- Mission scale creates meaningful efficiency
Higher planning, aircraft and regulatory burden. It has to be earned by the operating problem.
Use the simplest compliant operating model that solves the problem.
Linear infrastructure
Distance is where the business case can change.
Traditional field workflow
- Drive
- Setup
- Capture
- Land
- Reposition
- Repeat
Potential complex workflow
- Plan
- Larger acquisition segment
- Verify
- Next segment
On rail, utility and other linear projects, the benefit usually comes from reducing unproductive field repositioning — not from flight speed itself. Whether that changes the economics is a project-specific calculation, not a published percentage.
Assess a Corridor Mission
Remote deployment
A dock is not a monitoring strategy.
Installing a remote aircraft system only makes sense when the site, mission frequency, connectivity, airspace, ground environment, regulation and operating economics work together. Each of those is checked before hardware is recommended.
- Mission frequency
- How often must data actually be captured?
- Value
- What decision follows each mission?
- Site
- Can the system be safely installed and operated?
- Connectivity
- Can reliable C2 and data communications be maintained?
- Airspace
- What aviation constraints exist at this location?
- People
- Who is normally present around the operation?
- Aircraft / dock
- Does the selected system support the required mission and regulatory pathway?
- Economics
- Is recurring mobilization expensive enough to justify infrastructure?
Buy the dock after the operating model works on paper.
Beyond routine operations
Some missions require a different regulatory path.
Operations that fall outside the applicable Basic, Advanced or Level 1 Complex framework may require a Special Flight Operations Certificate — RPAS. That generally applies where the complexity or operating environment sits outside the routine regulatory framework.
Elev8 can identify when a proposed concept appears likely to require an SFOC pathway and help determine the next operational planning step. Approval itself is determined by Transport Canada.
Discuss an SFOC-Path Mission
Clear scope
Feasibility is not approval.
- Not a TC approval
- Only the relevant authority can issue required approvals.
- Not engineering certification
- Elev8 does not provide professional engineering through this assessment.
- Not a guarantee
- Airspace, regulation, equipment and project conditions may change.
- Not a hardware sales pitch
- The assessment may conclude that the system should not be purchased.
The purpose is to make the next decision better.
Best fit
The strongest feasibility projects have an expensive operating problem.
- Long corridor
- Remote site
- Repeated mobilization
- High monitoring frequency
- Difficult ground access
- Autonomous concept
- BVLOS requirement
- Capital purchase being considered
- Complex airspace / site
- Multiple dispersed assets
- High-value infrastructure
- Unclear regulatory path
A small, accessible site where normal VLOS acquisition already works efficiently may not justify complex operations. We will say so early.
Applications
Where complex feasibility becomes valuable.
Rail
Long ROW, remote infrastructure, difficult repositioning.
ViewUtilities
Transmission corridors, remote substations, distributed assets.
ViewRemote industrial & mining
Large sites, isolated facilities, recurring monitoring.
ViewEnvironmental / corridors
Long linear project areas under repeat observation.
ViewRemote monitoring
High-frequency observation of isolated high-value assets where appropriate.
ViewWhy Elev8
The assessment is informed by the operator who may eventually have to execute it.
We evaluate the concept from the perspective of whether it can actually become a workable field operation — crews, access, weather, connectivity, aircraft and data, not just a regulatory summary.
- Issued RPOC
- Level 1 Complex capability
- Field acquisition experience
- Remote operations mindset
- Infrastructure focus
- Geospatial workflows
- Equipment-agnostic planning
Elev8 does not guarantee regulatory approval and does not represent Transport Canada.
Equipment strategy
Do not design the mission around equipment you already bought.
Aircraft, docks, sensors, communications and supporting systems should be selected after the mission requirement and the regulatory path are understood.
- Use existing equipment
- Rent
- Partner
- Purchase
- Change platform
- Remain VLOS
- Defer deployment
Mission → regulatory path → operating model → equipment.
Equipment → find a mission.
Engagement
From concept to go/no-go.
01
Submit
Location, AOI, mission concept.
02
Screen
Major obvious constraints.
03
Assess
Operational, regulatory and technical pathway.
04
Recommend
Go / Modify / Escalate / Stop.
05
Scope
If viable, define the next phase.
Possible next phases
- Pilot mission
- Detailed CONOPS
- SFOC planning
- Corridor pilot
- Equipment validation
- Autonomous-site design
- Full deployment
Field proof
Related technical work
No published project record exists in this category yet. These are real acquisitions that demonstrate the relevant capability.
PROJECT / 001 · Real project · Dataset available
New Ontario School — Reality Capture & Existing Conditions
An aerial reality-capture acquisition producing a 3D digital record of the school site.
Reality Capture · Mapping · 3D
View projectPROJECT / 002 · Real project · Dataset available
Hospital Site — Orthomosaic & 3D Existing-Conditions Capture
One acquisition produced both a top-down spatial record and a 3D visual record of the hospital site.
Reality Capture · Mapping · 3D · Orthomosaic
View projectQuestions
BVLOS and complex operations FAQ
No. An RPOC is part of the required framework for Level 1 Complex operations. Individual missions remain subject to pilot, aircraft, airspace, ground environment and other applicable requirements.
Mission intake
Send us the mission before you buy the hardware.
Send the site, corridor, proposed operating model or monitoring requirement. Elev8 will assess the major operational and regulatory constraints before recommending the next step.
Site · Corridor · AOI · Frequency · Aircraft · Operating concept