Notice: Undefined index: ivaocalang in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czeg/index.php on line 2

Warning: Cannot modify header information - headers already sent by (output started at /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czeg/index.php:2) in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czeg/index.php on line 8
IVAO Canada - Edmonton FIR

IVAO Canada > Controllers > Edmonton FIR

Notice: Use of undefined constant page - assumed 'page' in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czeg/path.inc.php on line 3
> Edmonton City-Centre Operating Procedures

Edmonton City Centre airport procedures



Airspace

Edmonton City Centre airport is a class C airport with a 5nm control zone up to but excluding 4 600 ft ASL. The north part of the CZ is class E airspace up to 3 400 ft ASL. See CFS.

Frequencies

Sector ID Radio Callsign Frequency Airspace
CYXD_TWR City Centre Tower 119.10 5nm Control zone to but excluding 4600ft ASL. See CFS for proper CZ shape.
CYXD_GND City Centre Ground 121.90 All taxiways, excluding the aprons.
CYXD_DEL City Centre Clearance 121.30 None.

Clearance

Clearances must be requested from Edmonton TCU or Edmonton ACC (if TCU offline) if that controller is online. Use the "ATC clears" prefix before the clearance as you have to relay it. If the controller is not online, issue the clearance yourself and drop the prefix.

No specific routing restrictions exist in City Centre, though preferred routes exist and should be used whenever possible. See CFS for more info.

All IFR flights are to be cleared via the Edmonton City 4 (X3) Standard Instrument departure.

Squawk codes

  • Internal flights (flights remaining in the Edmonton FIR): 4260-4277
  • External flights (flights leaving the Edmonton FIR): 2160-2177
  • VFR Remaining within the Edmonton TCA: 1260-1277

Ground

Standard ground procedures apply.

Tower

Runway configurations

All runways are available for arrival and departures, but only runway 34 is equipped with an ILS approach, and runway 12/30 has no IFR approach. NOISE ABATEMENT PROCEDURES exist in City Centre. See CAP.

Departures

Edmonton TCU / ACC, when online, is responsible for separation between departures and a release MUST be requested before issuing takeoff clearance. If Edmonton is not online, use standard separations for departures and take that responsability.

Besides providing the radar/wake turbulence separation between departures, the Tower controller must ensure that the initial separation between aircraft does not decrease. Factors such as aircraft performance and pilot technique vary even in the real world so be wary when attempting to run departures with minimum spacing, especially when departing a jet behind a prop, even if their wake category are the same.

IFR traffic is handed off to "Departures" (Edmonton Terminal 119.50) with the take-off clearance.

Arrivals

Though it is a responsibility of the TCU/ACC to provide the appropriate separation between successive arrivals on final approach, responsibility for spacing between arriving aircraft may be transferred to the Tower once the aircraft crosses the Final Approach Fix (FAF).
With the use of radar the Tower assumes control of arrivals at the FAF regardless of the weather conditions. See MANOPS section 362.5 for the proper control transfer procedures.

If using IvAi in conjunction with FS to operate a visual tower viewpoint you may decrease the 3 nm separation of aircraft on final provided both aircraft are in sight. Aircraft conducting visual approaches in accordance with MANOPS section 566 and 567 are responsible for maintaining their own separation.

On Arrival traffic will be handed off to Tower once established on the approach (or any leg for visual approaches) prior to entering the control zone. If TCU/ACC is offline, make sure the aircraft calls you in advance so you can start managing separation between other traffic as needed.

VFR traffic

Arrivals
VFR traffic will be transferred to tower approximately prior to entering the control zone.

Departures
Restrictions should only be applied for separation with other IFR traffic. There are no pre-defined guidelines.