4.2 Heliports, Control Zones & Uncontrolled Aerodromes

4.2 Heliports, Control Zones & Uncontrolled Aerodromes

Quick Answer: Without authorization, stay at least 1.9 km (1 NM) from a heliport. Control zones around many towered airports are often Class D and often about 5 NM radius in textbook examples—verify charts, do not treat 5 NM as universal law. Uncontrolled aerodromes, water aerodromes (CWAS), and MF/ATF areas still carry low-level traffic risk in Class G. CAR 901.47 governs RPAS at/in the vicinity of aerodromes/airports/heliports; use CAR 602.96 crewed vicinity concepts to build traffic awareness.

Certified airports get the headline 5.6 km number, but Advanced pilots lose marks—and create incidents—when they ignore heliports, control zones, and uncontrolled landing sites. Helicopter emergency medical services, floatplanes, and circuit traffic at small aerodromes operate precisely where drone operators like to fly: low, local, and near infrastructure.

Heliport standoff: 1.9 km (1 NM)

Transport Canada Advanced operations materials pair a second numeric standoff with heliports:

Why heliports get their own (smaller) ring

Helicopters do not need a 10,000-foot runway. They arrive and depart steeply, hover-taxi, and land on rooftops, hospital pads, and industrial pads with little warning to a drone pilot watching only the nearest paved airport. Air ambulance and other HEMS flights prioritize patient outcome over giving a drone crew five minutes of radio courtesy. That combination—low altitude, high urgency, unpredictable approach paths—is why a dedicated heliport buffer exists.

Operational implications:

• A hospital helipad on a city block can put you inside 1.9 km while you are still far outside the 5.6 km ring of the regional certified airport.
• Roof-top and industrial heliports may not look like "airports" on consumer maps—check CFS/chart symbology and local knowledge.
• Authorization pathways for closer heliport work follow the same philosophy as airports: Advanced + rules + procedures/authorizations, not casual approach.

Conversion and mix-up traps

• 1 NM ≈ 1.9 km (1 × 1.852 ≈ 1.852 km, taught as 1.9 km)
• Do not apply 1.9 km to a certified airport scenario
• Do not apply 5.6 km to a pure heliport scenario when the question isolates heliport distance
• Sites near both a heliport and an airport must satisfy both applicable constraints and any controlling airspace rules

Control zones: typical Class D, often ~5 NM—not universal

A control zone (CZ) is controlled airspace established around certain aerodromes to protect IFR and managing VFR traffic in the immediate aerodrome environment. In Canadian teaching materials, many towered airports are associated with Class D control zones, and a common textbook radius is about 5 NM from the aerodrome—often from the surface to a specified altitude.

Teach carefully:

How this interacts with the 5.6 km rule:

• The airport standoff is a Part IX proximity teaching number from the centre.
• The control zone is an airspace classification/geometry problem on the chart.
• You can be outside 5.6 km yet still under other controlled airspace, or inside complex shelves and transition areas.
• Conversely, close-in operations inside a CZ always demand the controlled-airspace Advanced pathway (authorization, procedures, communication as required)—not merely "I am Advanced so the tower will figure it out."

Exam skill: when a scenario mentions a towered airport, check both (1) distance from centre vs 5.6 km / 3 NM, and (2) whether the site sits inside the charted control zone / controlled airspace requiring authorization.

Uncontrolled aerodromes: Class G is not empty sky

Many Canadian aerodromes have no control tower. They may sit in Class G (uncontrolled) airspace yet still host training circuits, agricultural flights, medevac, private IFR practice approaches under IFR rules in the system, and weekend recreational traffic. Advanced candidates sometimes assume "uncontrolled = free drone zone." That assumption fails both the exam and a Saturday afternoon at a busy training field.

Risk factors at uncontrolled aerodromes:

• Circuit altitude traffic joining downwind, base, and final near the ground
• Non-standard join procedures and conflicting left/right circuits
• Radio optional / radio recommended cultures that vary by aerodrome and traffic
• Gliders, ultralights, and helicopters mixed with fixed-wing traffic
• No ATC deconfliction—see-and-avoid and local procedures carry more of the safety load

For RPAS, treat vicinity of an uncontrolled aerodrome as a high situational-awareness environment. Even when no 5.6 km certified-airport rule is triggered, 901.47 vicinity concepts and general operating rules still demand that you not create a hazard to aviation.

Water aerodromes and CWAS

Water aerodromes support floatplane and amphibious operations. Identifiers and entries in aeronautical products may include water-aerodrome indicators; teaching materials often reference water sites in the same family of "real aerodrome, real traffic" awareness. CWAS-style designators in Canadian products flag water aerodrome contexts candidates should recognize as aviation sites—not empty lakes.

Why drones fail near water aerodromes:

• Floatplanes operate low over water on approach and departure
• Shoreline photography and surveying put RPAS exactly on the approach path
• Glass-water days encourage scenic flying by both communities at the same altitudes
• There may be no tower and limited radio infrastructure

Site survey: if the lake appears in CFS/chart aerodrome listings as a water aerodrome, plan for crewed low-level traffic, not only for bird activity and wind.

MF and ATF areas: radio environments without a control tower

Mandatory Frequency (MF) and Aerodrome Traffic Frequency (ATF) areas establish radio procedures for crewed aircraft operating near certain aerodromes—especially uncontrolled ones. You do not need to become a full radiotelephony examiner in this section, but you must understand the risk signal:

• MF: crewed aircraft are expected to make mandatory radio reports on the designated frequency in the MF area—traffic is organized enough that radio is required, yet there is still no tower controlling every movement the way Class D ATC does.
• ATF: a published frequency for traffic information at the aerodrome; pilots broadcast positions and intentions. Traffic density can still be high.

For RPAS Advanced pilots:

• MF/ATF presence means expect active low-level traffic even in Class G.
• Monitor applicable frequencies when equipped and authorized to do so as part of professional ops practice; never assume silence means empty airspace.
• Do not park a drone on final because "nobody is talking right now."

CAR 602.96 — vicinity of an aerodrome (crewed context → RPAS awareness)

CAR 602.96 addresses operations of aircraft in the vicinity of an aerodrome for the crewed world: fitting into the circuit, avoiding collisions, and conducting operations in a manner that does not endanger other traffic. RPAS candidates study it as context for what crewed pilots are doing around aerodromes—not as a free pass to copy manned circuit joining with a multirotor.

Awareness takeaways for drone pilots:

1. Crewed traffic will be concentrated near runways, helipads, and water lanes.
2. Pilots may be task-saturated (checklist, radio, configuration) on short final.
3. "Right of way" and collision-avoidance culture expect predictable behaviour; a hovering drone on base leg is not predictable.
4. Even when RPAS rules use different section numbers, the physical traffic pattern is the same sky.

CAR 901.47 — RPAS at or in the vicinity of an aerodrome / airport / heliport

CAR 901.47 is the Part IX anchor for RPAS operations at or in the vicinity of an aerodrome, airport, or heliport. Read it as the rule family that says: when you share the aerodrome environment, you must operate under the applicable conditions—including distance rules, airspace authorization, procedures, and any facility-specific requirements.

Link the pieces:

Integrated site-survey questions

Before launching near any aviation site, answer:

1. Is there a certified airport within 5.6 km of centre?
2. Is there a heliport within 1.9 km?
3. Is there a military aerodrome within 5.6 km?
4. What airspace class and control zone geometry cover the site on the chart?
5. Is the aerodrome controlled, uncontrolled, water, MF, or ATF?
6. What NOTAMs and local procedures affect today?
7. Does 901.47 vicinity apply such that special procedures or authorizations are required?
8. Where will a lost-link or flyaway path go relative to final approach and the helipad?

Exam traps for Section 4.2

• Swapping 1.9 km and 5.6 km
• Declaring control zones always 5 NM Class D without chart verification language
• Believing Class G uncontrolled aerodrome means no traffic risk
• Ignoring hospital helipads while checking only the regional jet airport
• Treating MF/ATF as irrelevant to RPAS because drones "don't need a radio licence for every flight" (risk awareness still applies)
• Forgetting 901.47 as the RPAS vicinity rule family while only memorizing numbers

Combine the heliport 1.9 km / 1 NM number with honest control-zone chart reading and uncontrolled-field humility, and you will handle the aerodrome-proximity questions that sit between pure airspace class theory and pure airport standoff memorization.