3.2 Class C, D & E Entry and Transponder Context

3.2 Class C, D & E Entry and Transponder Context

Quick Answer: Crewed aircraft enter Class C and Class D under CAR 601.08/601.09 themes that emphasize two-way communication and ATC clearance. RPAS pilots do not “self-clear” into that same volume. CAR 901.14 requires controlled-airspace RPAS operations to meet the prescribed conditions (including authorization), CAR 901.15 addresses inadvertent entry, and transponder/Mode C airspace (601.03 context, with RPAS equipment themes in 901.46 when applicable) explains why major-airport environments are surveillance-dense and high-risk for unauthorized drones.

Section 3.1 taught you what the classes are. This section teaches how entry works in the classes where Advanced RPAS work most often collides with manned traffic: C, D, and E, plus the transponder context that surrounds busy terminal airspace.

Crewed VFR Entry: Class C and Class D (CAR 601.08 / 601.09 Themes)

For aeroplanes and helicopters operating VFR, Class C and Class D are not “enter and hope.” The regulatory themes in CAR 601.08 (Class C) and CAR 601.09 (Class D) require the pilot to establish two-way radio communication with the appropriate ATC unit and to obtain an ATC clearance before entering the airspace (subject to the detailed wording and any exceptions in the regulations). ATC uses those communications to sequence traffic, protect IFR operations, manage the circuit, and maintain situational awareness.

Why this matters for drone pilots:

• The same physical volume may contain training aircraft in the circuit, IFR arrivals on final, helicopters transitioning low, and medical flights—all coordinating with ATC.
• A drone without authorization, without a clearance pathway comparable to crewed VFR, and often without a transponder is an unannounced conflict. ATC cannot sequence what it cannot see or did not authorize.
• “I stayed below the circuit altitude” is not a legal theory of entry. Control zones and Class C terminals are controlled from the surface (or from charted floors) up through published ceilings and shelves.

Class E differs in service detail from C/D, but it remains controlled. Do not confuse “VFR may not need the same Class C-style clearance ritual in every Class E situation” with “RPAS may freely enter Class E.” For Part IX advanced controlled-airspace operations, Class E still triggers controlled-airspace discipline and authorization expectations.

RPAS in Controlled Airspace: CAR 901.14

CAR 901.14 is the RPAS-specific gate for operations in controlled airspace. In exam language: you may operate a remotely piloted aircraft in controlled airspace only if the conditions set out for that operation are met—including the authorization and any other requirements Transport Canada and the CARs prescribe for Advanced controlled-airspace flight.

Translate that into field practice:

1. Confirm the volume is controlled (Class C/D/E, etc.) using charts and planning tools.
2. Hold Pilot Certificate – Advanced Operations with applicable recency.
3. Ensure the RPAS has the required safety assurance declaration pathway for controlled airspace (Standard 922.04 themes for small VLOS controlled-airspace accuracy, covered in Chapter 2).
4. Obtain written RPAS Flight Authorization (NAV Drone / NAV CANADA process—Section 3.3) covering the site, times, altitudes, and conditions.
5. Fly only within those written limits; treat the authorization as the operational envelope, not a suggestion.

901.14 is not satisfied by “I have Advanced on my wallet.” Certificate + declaration + site-specific written authorization (when required) work together.

Inadvertent Entry: CAR 901.15

CAR 901.15 addresses inadvertent entry into controlled airspace. The regulatory intent is twofold:

• Prevention through competent planning—know the boundaries, use geofencing/planning tools wisely (without treating them as a substitute for chart knowledge), brief contingency altitudes, and set conservative buffers inside Class G when working near a control zone.
• Immediate corrective action if entry still occurs—stop penetrating deeper, leave the controlled volume as safely and promptly as the situation allows, and follow any communications or reporting expectations that apply to the event.

Exam scenarios often contrast a pilot who planned poorly (boundary unknown, wind drift ignored, RTH climbing into a shelf) with a pilot who planned buffers and still had a brief GPS glitch. Both may face compliance scrutiny, but willful unplanned operations in controlled airspace and careless boundary management are treated as serious. Inadvertent entry rules are not a loophole to “try the shot and apologize.”

Control Zone Geometry Basics

Many Canadian control zones associated with towered aerodromes are taught using a baseline geometry of approximately 5 NM radius and a vertical dimension on the order of 3,000 feet above aerodrome elevation, often shaped as a cylinder (sometimes with extensions). Reality is messier:

• Boundaries can be non-circular or extended along approach paths.
• Class C terminals may have multiple shelves and rings.
• Class E may begin at the surface or at a published altitude over the surrounding area.
• Heliports, water aerodromes, and military fields add special proximity rules (later aerodrome chapters).

Site-survey discipline:

• Measure lateral distance from the aerodrome reference point / charted zone boundary to your pad and to your maximum planned offset (inspection route, mapping grid, contingency).
• Check vertical limits: a job at 200 ft AGL can still be inside a surface-based zone.
• Include wind drift and flyaway distance in the buffer; lost-link climb profiles that pierce controlled airspace convert a Class G pad into a 901.15 event.

Transponder / Mode C Airspace Context (CAR 601.03 Themes)

Transponder airspace and Mode C requirements (CAR 601.03 themes) exist so ATC and airborne collision-avoidance systems can detect and identify crewed aircraft in busy or strategically important airspace. Mode C provides altitude reporting in addition to identification.

Implications for RPAS Advanced pilots:

• Near major airports and in associated terminal airspace, the crewed traffic picture is surveillance-rich. Controllers and equipped aircraft operate with the assumption that participating traffic is visible and predictable.
• Most small consumer/professional RPAS used for VLOS do not carry a civil Mode C transponder as crewed aircraft do. That is one reason unauthorized drones near major airports create disproportionate risk: they are hard to see on ATC displays and hard to sequence.
• CAR 901.46 themes address transponder equipment for RPAS when the regulations require carriage/use for a particular operation or airspace context. On the exam, connect 901.46 to “when the rules require RPAS transponder capability, you must meet equipment and operating expectations”—not to “drones may ignore Mode C airspace because they are small.”

High-risk takeaway: operations near major Class C airports are high-risk not only because of traffic density, but because the entire system is built around authorized, equipped, communicating participants. An unauthorized RPAS is a system failure from ATC’s perspective even if the pilot “felt” visual separation was easy.

Integrating C, D, E, and Transponder Awareness into Pre-Flight

Before launch near any controlled volume:

1. Classify the airspace (VNC/VTA + digital tools as aids).
2. Map geometry (lateral + vertical + buffer).
3. Apply 901.14 — do you have written authorization covering this exact operation?
4. Plan 901.15 prevention — geofence, altitude cap, observer roles, lost-link profile that stays outside controlled airspace if that is the plan.
5. Respect surveillance context — assume crewed aircraft may appear on short final, on base, or in a helicopter corridor with little time for you to react; give way and cease if safety demands it.

Master these rules and the authorization and ATC sections that follow become procedural rather than mysterious.