IVAO-TH internal FIR Rules 

1. Minimum Ratings 

All controllers will be expected to have charts for the position they are taking and to be familiar with their area. 

2. Frequencies 

The following normal frequencies shall be used: 

Transmission on the Guard-Frequency 121.50 IS NOT ALLOWED – except in emergencies. 

Instruction of how to set the frequency in PC, can be found the manual before going on-line Transmitting on 121.50 may mercilessly be killed out from online session by supervisor after the second warning. 

3. Language 

All communication HAS TO BE IN ENGLISH. 
That means the controller gives instructions in English and the pilot replies in English and vice versa. This applies for text and voice. 

Exception: Thai language will be accepted for instructions during training sessions, or when asking for advice. 
Advice by voice on the ATC frequency should be kept as short as possible. If longer discussions are required, please create another RW-channel and continue communications with ATC by text. 

4. ATC-Positions 

Of course, basically anyone can take any position for which he is qualified (see “Minimum Ratings above). 
It is practical that the first controller with a S3 or higher rating who comes on-line will take the VTBB_CTR position. 
Any other controller would then take a position (like VTBD_APP or VTCC_APP, VTBD_TWR, etc.) below VTBB_CTR according to her/his qualification. 
The _CTR controller will take care of approaches and departures from airports that do not have _APP. 
However, in the past we have found that due to the geographical situation – Thailand is a large country, especially from N to S – it is very difficult for the CTR controller to simultaneously take care of Approach- and Departure-traffic both in the N and in the S of the country. This is also due to a limitation in the maximum range of PC. If we look at the real world charts we will find that there are actually 7 sectors for VTBB_CTR, all on different frequencies (go here to see this). 
For times with higher traffic therefore the following rule will apply (until we find a better solution or until we have more qualified controllers, who can cover all the _APP positions): If there are more than 2 controllers on-line who are qualified to work on a _CTR position, they shall split the airspace into TWO _CTR sectors, North and South. The split shall be just S of VTBD-Approach airspace. 
The callsigns and frequencies will be VTBB_N_CTR (Bangkok North Control) on frequency 120.50 MHz and VTBB_S_CTR (Bangkok South Control) on frequency 126.60 MHz 
In order to avoid discussions about who will be who, the first controller shall decide which position he wants to take and the second controller shall accept this. 

4.1 Areas of responsibility 

(VTBB_N_CTR / VTBB_S_CTR): 

VTBB__N_CTR (120.50): all airports N of Bangkok, including VTBD, if there is no VTBD_APP 

VTBB_S_CTR (126.60): all airports S of Bangkok 

Handover procedure for traffic to VTBD from the S: 
VTBB_S_CTR shall hand over to VTBB_N_CTR or VTBD_APP when approaching FL130 on the descent inbound on the STAR to either PAULA or HELEN. 

Handover procedure for traffic from VTBD to the S: 
VTBB_N_CTR or VTBD_APP shall hand-over to VTBB_S_CTR when approaching 11000 ft on the SID routes to the S or SE 

4.2 Frequency and ATIS – Change: 

After both controllers have agreed on their positions they shall: 

4.3 Sector File 

No change in sector file is required, both controllers will use the same file. 

4.4 Miscellaneous 

All this of course, shall not apply when we have the following approach controllers: - VTBD_APP - VTCT_APP - VTSP_APP 
When all of these 3 approach positions are available, there is no real need to split the _CTR airspace.

Even though all frequencies and codes SHOULD be real,
they are only for use with ProController, SquawkBox and Flight Simulators,
and should NOT be used for real life aviation.

© 2001-2002 - IVAO TH - All Rights Reserved