Operational structure & compliance
HighCloud is a certified drone operator (RPAS), active since 2016, compliant with Transport Canada requirements. Operations are based on ROC, SFOCs, a documented SGS-type approach, an operations manual and up-to-date procedures.
The following sections describe our operational structure and the pillars of our compliance.
HighCloud Remotely Piloted Solutions Inc.
The corporate mission is to provide specialized services in areas where RPAS can outperform traditional methods, under standardized operating procedures and policies — an efficient, reliable, safe and regulation-compliant company. HighCloud is recognized as an ATP pilot training unit that has declared compliance with Transport Canada technical publication TP 15263.
- Security, photography, thermography, electronic design, radiocommunication
- Flight training (professional and recreational), visual inspection, data collection
- Aerial imaging, agricultural spraying, magnetometric surveys
Operator: HighCloud Remotely Piloted Solutions Inc.
106, Place Todoro, Cowansville (Quebec) J2K 0R2
Accountable Executive and Operations Manager: David Leblanc
RPAS operated
DJI Matrice 300 RTK (including DRS M300), DJI Matrice 400, Skydio 2, DJI Inspire 2 (Standard, Parazero, Indemnis)
DJI Phantom 4 (Standard, Professional, Parazero SafeAir), DJI M210 / M210 RTK, DJI Mavic Pro
Dock 2, Dock 3; DJI Agras T25, T50, T100
RPAS approved with manufacturer declaration of compliance (standard 922). RPAS flight manual SATP-MV.
Operational structure
Risk-based: risk assessment and management, personnel qualification, training program, operation specifications, operational control of flights (authorization, planning, monitoring, completion), maintenance control, quality assurance and safety management system.
Governance
Roles and the decision chain are defined in the operations manual and ensure mission reproducibility.
- Accountable Executive and Operations Manager
- Chief Pilot, Pilot-in-Command (PIC)
- Ground observers, system maintainer and other documented roles
Reporting chain
Accountable Executive → Operations Manager → Chief Pilot → Pilot-in-Command and flight crew.
Mission authorization
Each mission is covered by prior authorization, within the ROC, SFOCs where applicable and internal procedures.
Mission planning
Definition of objectives and constraints
Risk assessment
Quick, normal or in-depth depending on the mission
Authorization
Validation by the operations manager or delegate
Execution
Execution according to procedures
Debrief
Traceability and documentation
Operation specifications
HighCloud's operational structure includes the use of operation specifications addressing operational and regulatory requirements specific to advanced RPAS operations. The operations manager or delegate approves the content after ensuring it does not conflict with the operations manual policies. Specifications take into account manufacturer instructions when provided. All involved personnel must familiarize themselves with and comply with them when applicable.
- Operational and regulatory requirements specific to advanced RPAS operations
- Approval by the operations manager after verification of compliance with operations manual policies
- Consideration of manufacturer instructions when provided
- Updates when necessary or upon Transport Canada request
- Distribution, amendment and control process so personnel have access to the current version
- Master list of holders; revision and distribution controlled by the operations manager or delegate
- Rigorous management of the capabilities list for RPAS operations
Risk management
HighCloud has implemented and maintains a risk management process. Every mission begins with a documented assessment — quick on arrival at the site, normal or in-depth — the results of which determine the qualification level of personnel and the type of RPAS.
Assessments are carried out by the operations manager or delegate, or by a designated team. The process is described in the operations manual and associated procedures.
- Identification of mission-related hazards and associated risks
- Assessment of risk level and determination of control measures
- Implementation of control measures and post-mission follow-up
- Quick, normal or in-depth assessment depending on mission type (including BVLOS / EROS JARUS)
Traceability
Missions, authorizations, deviations and document revisions are recorded. Records are retained and can be presented for audits or legitimate client requests.
- Missions and authorizations recorded
- Deviations and incidents documented
- Document revisions retained
- Accessibility for audits
Maintenance control
HighCloud has implemented and maintains an RPAS maintenance control system. It ensures all RPAS are in airworthy condition before being assigned to a mission. The system applies to RPAS with or without manufacturer declaration of compliance; airworthiness maintenance instructions come from the manufacturer or are created in-house as applicable.
- Maintenance schedules and component life limits
- Journey log books (airworthiness status, available at mission sites)
- Technical records (work reports, retained for at least 24 months)
- Maintenance tracking and technical defect control
- Work orders and maintenance agreements (external maintenance)
- Technical return to service by the operations manager or delegate
Elementary work and routine maintenance
HighCloud authorizes certain pre-approved persons to perform maintenance operations considered elementary work or routine maintenance. The system maintainer determines which operations fall into this category. The operations manager establishes the list and issues authorizations when the person has demonstrated competency under the maintainer’s supervision. Parts and tools must be compliant; a journey log entry is made after the work, without technical return to service.
- List of operations considered elementary work or routine maintenance, established by the operations manager; the system maintainer determines which operations are included
- Eligibility criteria: no test other than a simple operational test, no structural component of the RPA, no soldering or connector crimping, no specific torque, no firmware update, no pneumatic/hydraulic disconnection (except quick-disconnect), no bulk component removal/reinstallation
- Competencies: the maintainer ensures the person can find technical instructions, verify parts and tools, and perform the operation to standard; authorization issued after demonstration under supervision and maintainer declaration
- Parts and materials recommended by the manufacturer or assessed by the maintainer; inspection before installation; non-compliant or damaged parts: non-conformity report and segregation
- Journey log entry after work; no technical return to service required following elementary work or routine maintenance
Emergency preparedness and response
HighCloud has implemented and maintains an emergency preparedness and response structure for RPAS operations. The operations manager or delegate ensures it is effective and up to date. The pilot-in-command ensures the crew knows the location and use of emergency equipment before each flight, and that the emergency plan is accessible and activated when needed.
- Emergency response plan: procedures for emergency or contingency
- List of contact information required in an emergency
- Emergency response plan validation exercises
- Periodic plan review (annual or biennial depending on activity)
- Plan easily accessible at mission sites; activation by pilot-in-command in an emergency
- Emergency equipment: location and use known to the crew before each flight
Competency maintenance
HighCloud has implemented and maintains a training program for all personnel who perform functions in RPAS flight activities. The operations manager or delegate establishes and maintains a training and competency validation cycle (initial and recurrent training). Pilots-in-command hold an RPAS pilot training attestation from a unit whose curriculum meets the recommendations of Transport Canada document TP 15263. Training may be delivered in-house or by an external organization compliant with the program; all training is evaluated and documented.
- Training plan: ground theory training and practical training (ground and flight)
- Course plans and assessment methods (written tests, interview or documented practical exercises)
- Training and qualification control and follow-up process
- Training records retained for at least 24 months (operations manager and trainee)
- drone pilot training attestation compliant with TP 15263 recommendations (Transport Canada)
- Initial and recurrent training; additional training if identified by quality assurance or SMS
- Training delivered in-house or by external organization compliant with the training program
Qualification structure
HighCloud has implemented and maintains a qualification structure for its pilots, ground observers and ground station operators involved in RPAS operations. It is based on Transport Canada TP 15263, the training program, RPAS types and approved operation specifications. The operations manager or delegate ensures qualification control and follow-up.
- Structure based on TP 15263 (Transport Canada), HighCloud training program, RPAS types used and approved operation specifications
- Qualification control and follow-up by the operations manager or delegate
- VLOS basic operations qualification: certificate recognized for crew member in basic operations (Class G, outside specifications or per hazard register / approval); maintenance: exam, flight review or knowledge update within 24 months before a flight
- VLOS advanced operations qualification: certificate recognized for basic and advanced operations; same 24-month maintenance principle
- BVLOS qualification: operations beyond line of sight; per operation specifications and applicable assessment process
- TP 15530 Complex Level 1: recognized complexity level for advanced operations (training and flight evaluation per current requirements)
- Ground observers and ground station operators: privilege for those holding at minimum the basic VLOS operations certificate; training per applicable HighCloud program recognized for basic qualification
- Flight evaluators: pilot holding VLOS advanced operations with evaluator endorsement may ask HighCloud to submit their application to Transport Canada
- Exam or flight review retake: not permitted within 24 hours of a failure
Quality assurance
HighCloud has implemented and maintains a quality assurance program to ensure operations are always carried out in accordance with the operations manual and regulatory requirements. An internal verification process at prescribed intervals identifies and corrects non-compliances. The program manager establishes a verification schedule (signed by the operations manager); all activity sectors related to RPAS operations are verified.
- Internal verification schedule (initial cycle 12 months, may be extended up to 36 months depending on risk assessment)
- Checklists for all activity sectors related to RPAS operations
- Non-conformity report form (root cause, corrective actions and follow-up)
- Report submission and processing procedure: findings, root cause analysis, corrective actions and follow-up
- Communication of results to the operations manager; systemic failure reported to the Accountable Executive
- Internal verifications at prescribed intervals; auditors do not verify a sector where they have responsibilities
Safety management
HighCloud has implemented and maintains a Safety Management System (SMS) to continuously and effectively monitor the safety level of its operations. While quality assurance focuses on compliance with operating rules, the SMS directly monitors the safety level. The Accountable Executive and the SMS manager are its pillars; all personnel have a role in safety management.
- Safety management plan: safety policy, non-punitive reporting policy, roles and responsibilities, communication plan, planning, performance measurement, management reviews
- Documentation management: regulatory requirements (e.g. CAR), SMS documentation, records management
- Safety oversight: reactive and proactive reports, investigation and analysis, risk management
- Training, quality assurance and emergency preparedness (described elsewhere in the operational structure)
- Policies signed by the Accountable Executive; quarterly reviews and management reviews; records retained for at least 12 months
