Notice: Undefined index: ivaocalang in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czqx/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/czqx/index.php:2) in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czqx/index.php on line 8
IVAO Canada - Gander FIR

IVAO Canada > Controllers > Gander FIR

Notice: Use of undefined constant page - assumed 'page' in /Volumes/dune/www-servers/www.ivao.ca/htdocs/atc/czqx/path.inc.php on line 3
> CFB Goose Bay Operating Procedures

CFB Goose Bay airport procedures



Airspace

CFB Goose Bay airport is a class D military airport with a 10nm control zone up to 4 000 ft ASL.

Frequencies

Sector ID Radio Callsign Frequency Airspace
CYYR_APP Goose Bay Terminal 119.50 TCA airspace. See ACC diagram for airspace.
CYYR_TWR Goose Bay Tower 119.10 10nm Control zone to 4000ft ASL.
CYYR_GND Goose Bay Ground 121.90 All taxiways, excluding the aprons.

Clearance

Clearances must be requested from Goose Bay Terminal, or Gander ACC 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.

Routing restrictions exist in Goose Bay area due multiple restricted airspace around. Make sure you check your charts showing those areas. They are also visible in the sector file. Knowledge of these areas is a requirement.

All IFR flights are to be cleared via the Goose Bay 2 (G3) Standard Instrument departure.

Squawk codes

  • Internal flights (flights remaining within the Gander FIR): 4301-4377
  • External flights (flights leaving the Gander FIR): 7201-7277

Ground

Standard ground procedures apply.

Tower

Runway configurations

All runways are available for arrival and departures.

Departures

Goose Bay Terminal, or Gander Domestic, when online, is responsible for separation between departures and a release MUST be requested before issuing takeoff clearance. If TCU/ACC 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" 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.