Scheduled route, operator request, alarm, sensor event or emergency dispatch.
Start With the Operational Outcome
Remote flight matters when faster access, repeatability or centralized oversight improves the result.
Define what should trigger a mission, how quickly the aircraft must respond, what the sensor must capture, who supervises the flight and what happens after the data arrives.
Rapid Response
Launch from a prepared site to provide live scene intelligence for public safety, security or urgent asset events.
Build a Response PackageRecurring Inspection
Repeat visual, thermal and zoom routes over utilities, plants, rooftops, solar assets and industrial infrastructure.
Plan an Inspection ProgramConstruction & Mining
Schedule progress capture, mapping, inventory records and site documentation from consistent positions.
Configure Site MonitoringCorridor Monitoring
Design connected operations for roads, rail, pipelines, powerlines and distributed infrastructure.
Request a Coverage ReviewEnvironmental Change
Repeat approved routes over forests, shorelines, restoration areas and remote sites to track change over time.
Discuss the MissionMulti-Site Fleet Oversight
Centralize aircraft status, users, mission records, media and operating visibility across locations.
Design a Fleet WorkflowRemote Operations Solution Packages
Compare software-led fleet management, fixed-site autonomy and alternative enterprise ecosystems.
These are starting directions, not one-size-fits-all bundles. Final configuration depends on the mission, sensor, launch model, network, data policy, aircraft eligibility, operating environment and Canadian authorization.
DJI FlightHub 2
Cloud-based operations management for mission planning, remote control, live information sharing, fleet oversight, media handling and supported third-party integrations.
- Remote Control
- Fleet Oversight
- Cloud Workspace
Dock 3 + Matrice 4D Series
A current DJI remote-operations package supporting fixed installation or vehicle-mounted deployment with Matrice 4D or 4TD and FlightHub 2.
- Fixed or Mobile
- Visual or Thermal
- FlightHub 2
Dock 2 + Matrice 3D Series
A compact fixed-site direction for recurring mapping, visual inspection or thermal monitoring with Matrice 3D or 3TD and DJI’s cloud workflow.
- Compact Dock
- Mapping or Thermal
- Scheduled Routes
Remote Ops + Dock for X10
A remote-flight ecosystem combining Skydio X10 autonomy, browser-based Remote Ops and a field dock for scheduled missions or rapid response.
- Browser Flight
- X10 Autonomy
- Rapid Launch
Command System + EVO Nest
An alternative remote-operation direction combining compatible Autel aircraft, EVO Nest and centralized task, equipment, live-video and mission management.
- Task Management
- Live Video
- Networked Nests
AIM + Air + Base
An industrial inspection ecosystem linking remote aircraft management, rugged field infrastructure, automated capture and asset-focused analytics.
- Industrial Sites
- AIM Analytics
- Remote Insights
The permitted operating model depends on the aircraft, airspace, people, location, command-and-control links, supervision, procedures and Canadian regulatory pathway. Design the operation before committing to hardware.
Build the Complete Remote-Operations System
Value comes from the connected workflow—not one product.
Every layer should be tested together under normal conditions, degraded conditions and documented contingency procedures.
Aircraft, Sensor & Launch Method
Choose handheld launch, fixed dock or mobile dock with the visual, thermal, mapping or specialized sensor required.
Command & Fleet Software
Plan remote control, missions, users, alerts, media, audit records and integrations.
Connectivity & Site Infrastructure
Validate primary and backup networks, latency, power, security, weather and maintenance access.
People, Procedures & Authorization
Define remote-pilot roles, launch authority, supervision, airspace, lost-link response and approvals.
Data, Integration & Support
Route useful outputs to stakeholders and maintain software, aircraft, batteries, docks, networks and training.
Choose the Right Operating Model
Remote operations can begin before a fully docked multi-site program.
Select the least complex model that reliably achieves the business outcome, then add automation and scale when the workflow is proven.
| Operating Model | How It Works | Best Fit | Confirm Before Purchase |
|---|---|---|---|
| Connected Field Pilot | An on-site pilot flies while remote stakeholders receive live information and centralized records. | First-stage digital operations, inspections and incident support. | Aircraft compatibility, network, user permissions, data storage and live-sharing needs. |
| Remote Flight From a Prepared Site | A field team prepares or launches the aircraft while an approved remote operator supervises the mission. | Repeatable work where a dock is not yet justified. | Handover procedure, visual-observer model, command link, site access and authorization. |
| Fixed Dock Program | A dock keeps a compatible aircraft protected, charged and ready for scheduled or requested missions. | Recurring inspection, monitoring, security and response coverage. | Coverage, sensor, power, network, weather, site work, maintenance and regulatory path. |
| Mobile Dock Deployment | A supported dock and aircraft deploy from a vehicle or temporary operating location. | Incident response, changing work sites and mobile field teams. | Mounting, setup controls, route planning, connectivity, procedures and permitted use. |
| Multi-Site Remote Fleet | A central team oversees multiple aircraft or docks through a shared command and data platform. | Utilities, industrial networks, public safety and distributed assets. | Staffing ratio, roles, alerts, airspace, data governance, maintenance and escalation. |
From Concept to Dependable Remote Operation
Prove the mission and operating workflow before scaling the fleet.
A phased deployment exposes coverage, network, staffing, data and approval issues while changes remain manageable.
Define the Outcome
Document the trigger, response time, route, sensor, deliverable, frequency and success criteria.
Assess the Site
Review coverage, airspace, people, terrain, obstacles, weather, security, power and network.
Design the System
Select the aircraft, dock or launch method, command platform, connectivity, data flow and support plan.
Pilot & Validate
Train the team, test representative missions, degraded conditions and contingency procedures.
Measure & Scale
Confirm reliability, response, data value, operating cost and compliance before adding sites or aircraft.
Plan the Canadian Operating Path Early
Remote-control capability does not decide which flight privileges apply.
The operating category depends on what you fly, how you fly and where you fly. Some lower-risk BVLOS operations may fit Level 1 Complex when all applicable conditions are met; pilots must hold the required certificate and fly under an RPAS Operator Certificate. Operations beyond Basic, Advanced or Level 1 Complex rules may require an SFOC-RPAS.
- Pilot certificate and operator requirements
- Aircraft registration and safety assurances
- VLOS, EVLOS or BVLOS operating model
- Airspace and aerodrome proximity
- People, population and ground-risk controls
- Command link and lost-link procedures
- Remote supervision and staffing
- Privacy, security and data governance
Remote Operations FAQ
Important questions before buying software, aircraft or field infrastructure.
What is a remote drone operation?
It is an operation in which command, supervision, mission management or data access occurs away from the aircraft’s launch site. The exact arrangement can range from an on-site pilot sharing live information to an approved remote team supervising docked aircraft across multiple locations.
Do remote operations always require a drone dock?
No. A program may begin with handheld aircraft, an on-site launch team and remote command or information sharing. A dock becomes valuable when the aircraft must remain protected, charged and ready at a recurring site.
Can one operator supervise several drones?
Some platforms support multi-aircraft or multi-site management, but the permitted staffing model depends on the system, procedures, workload, operating environment and authorization. Do not assume software capability alone makes a one-to-many operation legal or safe.
What connectivity does a remote site need?
Requirements vary by platform and workflow. Live control and video typically need stable bandwidth, acceptable latency and a documented response to network degradation or loss. Test primary and backup connections at the exact site.
Can remote operations work in winter or isolated locations?
Potentially, but aircraft, dock, power, network and maintenance plans must fit the real temperature, wind, precipitation, icing, snow, access and seasonal conditions. Published environmental ratings are only one part of site readiness.
Do remote operations automatically allow BVLOS flight?
No. Remote-control capability and regulatory authority are separate. The operation must fit the applicable Canadian category and conditions, including pilot, operator, aircraft, airspace, location and procedural requirements.
What should be included in a remote-operations quote?
Include the aircraft and sensor, dock or launch equipment, command software, licenses, connectivity, site work, installation, training, regulatory preparation, data integrations, protection plans, spares, maintenance and ongoing support.
Can Unmanned Canada help design the full program?
Yes. Start with the mission, sites, response or inspection objective, sensor, network, data users and timeline. The solution can then be narrowed to the appropriate platform, deployment path and support scope.
