VFR in Airspace C/D
When a VFR aircraft requests to cross Class C or Class D airspace, the following conditions must be met:
- Aircraft Identification: The aircraft must be assigned a squawk code.
- Routing & Altitude Considerations: The aircraft's flight path should avoid direct passage through arrival and departure sectors.
- Clearance Requirements: The pilot must receive explicit entry and exit clearances for the controlled airspace.
Separation Requirements:
- Class C: IFR-VFR separation is required. VFR flights receive traffic information about IFR and other VFR aircraft. Traffic avoidance is provided upon request.
- Class D: Traffic information is provided to both IFR and VFR flights; separation is not provided for VFR aircraft.
Traffic Management in the CTR
Managing traffic within the Control Zone (CTR) is a routine task for ATC. Although the CTR may appear small on radar, it provides ample space for maneuvering. By issuing timely and accurate traffic information, further ATC intervention is rarely needed.
Opposing-direction VFR traffic may be cleared at the same altitude (e.g., "Maintain 2000 feet or below VFR") if appropriate traffic information is issued to ensure situational awareness.
While no minimum vertical separation is mandated when separation is not required, a 400-500 ft margin is recommended where feasible. Single-engine aircraft should not be forced too low due to emergency landing considerations. Always consider terrain and weather conditions when assigning altitude restrictions.
Crossing an airport overhead or extended centerline should be managed similarly to a runway crossing on the ground. Aircraft in takeoff and landing phases are in high-workload situations, making their trajectories less predictable. To enhance situational awareness, controllers should use "Report in sight" before issuing crossing clearances.
Overhead Crossings
If circuit traffic is light, directing aircraft to cross overhead simplifies coordination, keeping them above wake turbulence and on a predictable flight path. If circuits are busy, alternative routes should be used:
CNBOB, maintain VFR between 1500 and 2000 feet, cross runway 35 overhead direct KOSAD.
CNBOB, route south, remain east of the centerline and right-hand circuit for runway 35.
Approach Path Crossings
Crossing near the extended centerline further from the airport requires additional caution:
CNBOB, traffic A320 five miles final, report in sight.
CNBOB, cross runway 35 centerline behind the A320. Caution wake turbulence.
Notify the landing aircraft:
RAM123, traffic information: Light aircraft three miles east, crossing centerline behind you. They have you in sight.
Operations Below the Glide Path
For aircraft needing to cross beyond 4-5NM from the airport, staying below the approach path may be an option:
CNBOB, cleared to operate south of Berrechid, five miles out or greater, maintain 1700 feet or below VFR. Traffic: continuous IFR arrivals on the ILS 35, caution wake turbulence.
Notify IFR arrivals:
RAM123, traffic information: Light aircraft operating at least 500 feet below the glide path, continue approach, runway 35L cleared to land.
Maintaining a 500 ft buffer below the glide path generally prevents TCAS Resolution Advisories (RA). However, pilots should receive frequent traffic updates to ensure situational awareness and a safe operating environment.
VFR Phraseology for Airspace Clearance
| Clearance Type | French | English |
|---|---|---|
| Crossing Clearance | TRAVERSÉE [DE L'ESPACE AÉRIEN CHARLIE (ou DELTA)] AUTORISÉE VIA (route) (altitude) | CROSSING [OF AIRSPACE CHARLIE (or DELTA)] APPROVED VIA (route) (altitude). |
| Proceeding on a Radial | PROCEDEZ SUR LE RADIAL (trois chiffres) DE (nom du VOR) JUSQU’À (point significatif) | PROCEED ON RADIAL (three digits) OF (name of VOR) TO (significant point). |
| Exiting Controlled Airspace | QUITTER L’ESPACE AÉRIEN CHARLIE (ou DELTA) DIRECTION (ou CAP (trois chiffres), ou À (altitude)) [(raison)] | LEAVE AIRSPACE CHARLIE (or DELTA) DIRECTION (or HEADING (three digits), or AT (altitude)) [(reason)]. |
Class C Airspace Crossing Example
Pilot: Approach, [Callsign], 5 miles north of [VFR waypoint], VFR at 3400 feet, request crossing Class C airspace via [route], 4000 feet.
ATC: [Callsign], squawk 4133.
Pilot: Squawk 4133, [Callsign].
ATC: [Callsign], identified at 3400 feet. Crossing approved via [route], maintain flight level 60.
Pilot: Crossing approved via [route], maintaining flight level 60, [Callsign].
ATC: [Callsign], you are entering Class C airspace.
Pilot: Roger, [Callsign].
ATC: [Callsign], you are leaving Class C airspace. Frequency change approved, squawk VFR, goodbye.
Pilot: Frequency change approved, squawk VFR, [Callsign].
Class D Airspace Crossing Example (Non-CTR)
Pilot: Approach, [Callsign], 5 miles west of [VFR waypoint], VFR at 3400 feet, request crossing Class D airspace southbound via [waypoints], 5000 feet.
ATC: [Callsign], squawk 4133.
Pilot: Squawk 4133, [Callsign].
ATC: [Callsign], identified at 3400 feet. Crossing approved via [waypoints], maintain block flight level 60 to flight level 70.
Pilot: Crossing approved via [waypoints], maintaining block flight level 60 to 70, [Callsign].
ATC: [Callsign], you are entering Class D airspace.
Pilot: Roger, [Callsign].
ATC: [Callsign], you are leaving Class D airspace. Frequency change approved, squawk VFR, goodbye.
Pilot: Frequency change approved, squawk VFR, [Callsign].
Explicit Airspace Exit Instruction (Due to Traffic)
ATC: [Callsign], leave Class C airspace heading 180 at 2500 feet or below due to traffic.
Pilot: Leaving Class C airspace heading 180, at 2500 feet or below, [Callsign].