L1 - Facilities25-11-2005 | |
|
L1 - Facilities25-11-2005 | |
|
|
|
When logging with Pro Controller, you have to choose the facility you are going to work in. You are considered as an active controller if using one of the following extensions (GND, TWR etc...). If not, or if connected as an observer (OBS extension), you have no access to the ATC channel and can communicate on 199.999 only (text mode). xxxx_GND Ground Controller - Controls the movement of aircraft on the ground at an airport, however only the taxiways and bays... not the active runways. Whenever a plane needs to cross an active runway, has to coordinate that with the Tower. For departures, transfers aircraft to TWR when they reach the holding point. For arrivals, is given aircraft from TWR when vacating the runway. xxxx_TWR Tower Controller - 'Owns' the runways and the airspace until about 10 NM (nautical miles) from the airport. Clears planes for takeoff and landing and manages the VFR patterns. For departure, transfers aircraft to DEP or APP when airborne (IFR) or when leaving area (VFR). For arrivals, is given aircraft from DEP or APP when established on final (about 10 NM, IFR) or when entering TWR area of responsibility for VFR pattern (VFR). xxxx_APP Approach Controller - Controls the airspace up to 30NM or more away from the airport, up to 12,000 ft to 18,000 ft (usually, depending on local rules). Handles all aircraft leaving or arriving at one or several airports. For departures, transfers climbing IFR aircraft to CTR before reaching the upper limit of APP area (12,000 to 18,000 ft) and VFR aircraft to adjacent controller when leaving APP area. For arrivals, is given descending IFR aircraft from CTR before reaching same limit as above and VFR aircraft from adjacent controller when entering APP area. xxxx_DEP Departure Controller - A position rarely used except at busy airports in the real world which relieves the work-load of the approach controller by handling all the departures, and getting them away from arrivals as quickly as possible, leaving the approach controller free to handle arrivals (the hard bit). xxxx_CTR Center Controller - Centers own all airspace not controlled by APP or TWR and all airspace above 18,000ft or FL 195 or FL 240 (according to national rules). They control the plane while en route, and get it from A to B safely, until it can be descended and given to the approach controller. For departures, is given IFR aircraft from DEP or APP before reaching upper limit of APP/DEP area (usually between 12,000 and 18,000 ft). For arrivals, transfers IFR aircraft to APP before reaching the same limit as above. Particularity : center controllers often have to deal with GND/TWR/APP control for airfields located into their area of responsability but with no active controller logged there. This could be difficult to manage properly and cause students to be quickly overloaded. xxxx_FSS Flight Service Station - Air traffic facilities covering large areas (eg: Europe) which provide pilot briefing, en route communications and VFR search and rescue services, assist lost aircraft and aircraft in emergency situations, relay ATC clearances, originate Notices to Airmen, broadcast aviation weather and NAS information, receive and process IFR flight plans, and monitor NAVAID's. In addition, at selected locations, FSS's provide En Route Flight Advisory Service (Flight Watch), take weather observations, issue airport advisories, and advise Customs and Immigration of transborder flights. xxxx_DEL Clearence Delivery - Clearence Delivery is rarely used in IVAO. In the real world, a controller would relay the clearence (which explains where the plane is allowed to fly) to all planes. The 'xxxx' in the table replace a code used to identify the area that controller is using. These are known as ICAO codes, and can be found on the IVAO web-site. For example, Heathrow is 'EGLL' so a Heathrow Tower Controller would log-in as EGLL_TWR. Centers and flight service stations also have ICAO identifiers, but they are not for one airport, but for a larger area. For example, LFFF_CTR is Paris Center covering about a fifth of France, and EUR_FSS is the Europe Flight Service Station. When logging for training purposes, insert a T like this EGLL_T_TWR or LFFF_T_CTR. This will indicate a training session is in progress; your position is activated to train pilots and/or controllers, some pauses may be requested to aircraft and the RW channels may be used for explanations instead of standard phraseology. It could also indicate you are learning how to manage the position with a monitor. Any pilots looking for "real" procedures shouldn't fly at those airports where people are handling training sessions which may lack realism.This is established : - to avoid experienced pilots to complain about low performance and enable unexperienced pilots to learn with a controller dedicated to training. - to enable training controllers to deal with a smooth traffic, maybe dedicated to to training too. The rule concerning the insertion of a V when using Teamspeak is cancelled. Do not use the V anymore in order to avoid double log (EGLL_V_TWR and EGLL_TWR; only one Heathrow active TWR controller should be logged). You may also see the callsigns xxxx_SUP and xxxx_OBS. These are used only in the virtual world and represent, respectively, a supervisor and an observer (someone who isn't controlling). IVAO staff members may also log-in with their IVAO staff name, for example IVAO-FOD, IVAO-TD or just FOD, TD inserted after their name. |
|
|
