Start with intended operations and architecture. Identify where commands originate, how they reach the aircraft, what information returns to the operator, and which functions remain onboard. Then examine normal, degraded and failed states. Lost-link behaviour is a designed and evaluated response, not a universal assumption that the aircraft will safely return home. Consider link degradation, erroneous commands, latency, handovers and misleading indications. The safety assessment should connect hazards to requirements, implementation and evidence. Different RPAS categories and approval conditions can change the applicable approach.
Why this case matters
RPAS adds interest because it makes a familiar airworthiness principle impossible to ignore: the system boundary matters. The air vehicle is visible, but the command link, control station, software, launch or recovery equipment and supporting interfaces can affect its safe operation. The relevant military guidance and category must be checked. Civil small-drone procedures cannot simply be transplanted into a Canadian military acquisition.
Follow the evidence
A link failure is a sequence, not a label
Write down the trigger, detection, transition and end condition for a lost-link response. A delayed indication can matter even when the aircraft’s automatic response is correct. A handover can fail because the receiving station has a different configuration or because crews interpret state information differently. These are examples for analysis, not mandatory findings for every RPAS. The technical reviewer needs the system architecture, intended operations and applicable requirements before deciding which cases require demonstration. An impressive range demonstration does not necessarily substantiate degraded communications or a different station build.
Configuration reaches across the system
A configuration record that identifies only the air vehicle can hide flight-relevant station software and communications changes. Define the approved boundary and identify which elements and versions the evidence covers. Then ask how a change is assessed and how compatibility is maintained. The correct response is proportionate review of affected functions and assumptions, rather than an automatic demand to certify every item identically. Continuing airworthiness also needs usable information about defects, maintenance, updates and the relationship between configurations.
Human and technical evidence meet at the interface
Operator training can help crews understand indications and procedures, but it cannot compensate for every design hazard. Likewise, technically compliant equipment alone does not establish that a crew is prepared for the intended mission. Keep the system safety argument and the operational preparation connected while preserving their distinct purposes. When reviewing a demonstration, ask who operated the system, which procedures were used, what cues were visible and whether these match the proposed operation. Record assumptions explicitly instead of letting them disappear into the word demonstrated.
Twelve-minute project workshop
Training scenario — not an actual project decision
A fictional RPAS has completed a demonstration using one control station and a local test range. A new mission would use a revised station software build, a different communications route and handover between two crews. The contract team proposes accepting the earlier demonstration as proof that the new operating concept is ready. The aircraft hardware is unchanged. Your task is to explain why that fact alone does not close the technical questions.
- Spend three minutes drawing the whole system: vehicle, station, links, operators and support interfaces. Mark the three proposed changes.
- Spend four minutes writing normal, degraded and lost-link sequences. Identify what the operator sees, what the aircraft does and the assumptions each response relies on.
- Spend three minutes linking two hazards to requirements and evidence. Include a case where an earlier demonstration remains useful and a case where changed assumptions create a gap.
- Spend two minutes separating technical approval, operating procedures, crew training and contractual acceptance in your project recommendation.
Compare your reasoning
The strongest answer explains how a ground-side change can alter a flight-relevant function without claiming that every ground component has the same approval treatment. Configuration and interfaces determine what needs assessment. Earlier test data may remain useful for unchanged functions, while station software, communications performance and handover behaviour need an applicability review. A qualification or acceptance demonstration may contribute evidence but is not automatically a Canadian airworthiness approval. Consult TAA Advisories 2013-05 and 2014-02 for the applicable system, category and conditions.
Keep your worksheet as an optional learning aid. It is not submitted or graded. The practice below has no pass mark and does not affect core course completion.
Sources and further reference
- Technical Airworthiness Manual
TAM — current manual and structure
- Continuing airworthiness of uncrewed aircraft systems
TAA Advisory 2013-05 — UAS system boundaries and in-service requirements
- Certification of uncrewed aircraft systems
TAA Advisory 2014-02 — consult applicable category and conditions
RPAS: think in systems, not just aircraft
Assess flight-relevant functions, interfaces and failure behaviour across the defined system. This is a generic learning model, not a specific fleet architecture.
Air vehicle
Flight functions and configuration
Consider the airborne equipment, software, control functions and their interfaces within the defined system.
Control station
Commands, indications and human interaction
Ground-based functions can affect safe flight. Define the station’s configuration and flight-relevant interfaces.
Command and control link
Connectivity and failure behaviour
Identify the role of the link, its dependencies and the consequences of degraded or unavailable connectivity.
Operating context
Procedures, environment and lost link
Connect intended use and procedures to the design assumptions, including defined lost-link behaviour and recovery provisions.
The air vehicle and control station share the safety argument
The flight-relevant system includes more than the air vehicle. Use the infographic to examine its functions and interfaces.
