8.3 Manufacturer Declarations & Modified RPAS

8.3 Manufacturer Declarations & Modified RPAS

Quick Answer: CAR 901.69 lets you use advanced privileges only with a Safety Assurance Declaration (or Pre-Validated Declaration where required) against the correct Standard 922 section for that operation. Confirm the exact model on Transport Canada’s declared-drone list. CAR 901.70: modifications can void the declaration. Ops outside standard privileges may need an SFOC (903.x). Pick the aircraft from TC’s list—not from ads.

Chapter 2 introduced Standard 922 and 901.69 as the privilege matrix. This section is the hardware and configuration chapter: how manufacturers declare, how pilots prove the match, what happens when you modify the aircraft, and when you must leave the standard Advanced envelope for a Special Flight Operations Certificate.

How manufacturer declarations enable 901.69 operations

Transport Canada separates:

1. Pilot privilege — Pilot Certificate – Advanced Operations (knowledge + flight review pathway).
2. Aircraft privilege — the RPAS model has a declaration (and acceptance where required) that it meets the technical safety requirements for the intended advanced operation.

CAR 901.69 is the operational link: for listed advanced operations, a declaration must have been made (per the declaration rules, including CAR 901.194 themes) for that model against each applicable Standard 922 requirement. Without the matching declaration, Advanced pilot status alone does not lawfully unlock that privilege.

Who declares?

Typically the manufacturer/designer (or another party that can substantiate compliance for a build or major modification) submits the safety assurance declaration. Pilots do not invent a declaration on the morning of a job by self-certifying a hobby kit. Your job as pilot/operator is to select and configure an already-declared system and operate it within the declared limits.

Declaration types (recap for configuration control)

Matching model / serial / configuration to the declared standard

“We own a Brand X enterprise drone” is not enough. You must match:

1. Operation type — controlled airspace vs near people vs over people vs medium away/near/over vs sheltered-in-controlled-airspace, etc.
2. Standard 922 section(s) — e.g., small controlled airspace → 922.04; small near → 922.05; small over → 922.06; medium near/over → 922.07 PVD; medium away → 922.08; medium controlled airspace → 922.04 + 922.08 as mapped in 901.69.
3. Exact model designation on Transport Canada’s published list of drones with safety assurance declarations.
4. Configuration assumptions — firmware family, take-off mass, approved payloads, and any manufacturer limitations published with the declaration pathway.

Controlled airspace vs near people vs over people vs medium

Use the operation to drive the list check:

Serial numbers: where manufacturers or TC materials identify specific variants, hardware revisions, or serial ranges, operate only aircraft that fall inside the declared population. A visually similar airframe with a different internal flight controller revision may not be the declared article.

Exam trap: using a drone declared only for 922.04 on an over-people job, or a 922.05 airframe inside the 5 m over-people band. Declarations are privilege-specific, not “one sticker unlocks all Advanced.”

CAR 901.70 — Operation of modified RPAS

CAR 901.70 addresses operation of a modified RPAS. Teaching focus for Advanced candidates:

• A modification is any change to the system that can affect compliance with the basis of the declaration or safe flight characteristics—structural alterations, non-approved propulsion, major wiring changes, alternate flight controllers, unapproved firmware branches, homemade flight-termination, or payloads outside the declared configuration.
• Operating a modified RPAS as if it still carried the original manufacturer declaration is a classic failure mode: the declaration applied to a defined configuration; once you change that configuration, you may have voided the pathway that 901.69 relies on.
• Some manufacturer-approved kits (OEM payload options, OEM upgrade packages) remain inside the declared configuration when installed exactly as approved. “OEM-looking” third-party parts are not automatically approved.
• After any modification, you must determine whether you still have a valid declaration for the intended privilege, whether the manufacturer has a revised declaration covering the new config, or whether you need another legal path (often SFOC).

Practical modification decision tree

1. Is the change a manufacturer-approved option for this exact model/declaration?
2. If yes → install per manual, log the change (Section 8.1), confirm still on TC list for the privilege.
3. If no → treat declaration as potentially void for advanced privileges that depended on it.
4. Either revert to the declared configuration, obtain a new declaration/PVD covering the modified system (specialized, manufacturer-led), or pursue SFOC / other authority for the specific operation.
5. Do not invent a hybrid: modified airframe + old declaration PDF + hope.

When the SFOC (903.x) path applies

The Special Flight Operations Certificate (SFOC) framework under CAR 903.x is the regulatory path for RPAS operations that fall outside the standard Basic/Advanced privilege sets, standard declared configurations, or other routine Part IX pathways.

Typical teaching examples of when SFOC (or analogous special authority) thinking applies:

• Operations beyond what Advanced + declared aircraft + normal authorizations allow
• Certain complex, experimental, or non-standard systems and procedures
• Activities that regulations channel into special flight operations rather than standard advanced VLOS
• Modified aircraft that no longer fit a published declaration but still have a safety case acceptable under special authority

Key exam contrast:

An SFOC is operation-specific (conditions, locations, altitudes, equipment, crew). It is not a lifetime “modify anything” licence. Always read the certificate conditions.

Choosing the right drone from Transport Canada’s list

Transport Canada publishes guidance and a list of drones with safety assurance declarations (commonly referenced from the “choosing the right drone for advanced and complex operations” materials). Professional selection workflow:

1. Define the mission privilege (airspace class, people proximity, size class).
2. Map to Standard 922 / 901.69 requirements.
3. Open the current TC declared list and filter for models covering that standard.
4. Confirm your exact model name/version appears—not a cousin model.
5. Confirm your configuration (payload, MTOM, software) remains inside manufacturer and declaration assumptions.
6. Confirm pilot certificate, registration/marking, and any NAV CANADA / DND authorizations still required on top of the declaration.
7. If no listed aircraft fits, change the mission, change the aircraft, or start an SFOC planning process—do not fly undeclared.

Penalties for flying without the required declaration remain a high-yield memory pair from Chapter 2: up to $1,000 individual / $5,000 corporation on TC’s Advanced operations penalty list for that offence family—separate from other fines.

Linking maintenance, payloads, and declarations

Sections 8.1–8.3 form one system:

• Unserviceable declared aircraft → ground (901.29), do not rely on the declaration while broken.
• Firmware and critical repairs → log them; wrong software can break configuration control.
• Payloads and CG changes → may exit the declared configuration even if the airframe name is unchanged.
• Modifications (901.70) → can void 901.69 privileges until re-declared or re-authorized.
• Outside the envelope → SFOC 903.x, not improvisation.

Exam traps for Section 8.3

• “Advanced certificate = all drones allowed for all advanced ops”
• Using the wrong 922 section for the people/airspace scenario
• Assuming a modified aircraft keeps its old declaration automatically
• Trusting retail marketing over the TC declared list
• Treating SFOC as optional paperwork when the operation is clearly outside standard privileges
• Ignoring configuration (payload/firmware) when the model name matches the list

If you can reverse-map operation → Standard 922 → declared model → unmodified configuration, and you know 901.70 voids and 903.x escapes for true outliers, you own the hardware side of Advanced privileges.