132.6 sectorisation
Hi Rage...tks 4 the inputs. We'll b great if pilots start lobbying 4 controllers about airports. That will be a win-win 4 Pilots n Atc. I have personally used the "reduce g/s by xxx" it worked until Flow Controller wanted something else. In Area Control all we need is 10nm separation (on Radar). In Approach it is 5nm.
Actually flow does a good job...until the Ipoh/Johore/Kuantan/ guys get a/borne suddenly. U have a string of them coming in from the East...all well arranged by Flow n out of the blues the 737's get a/borne from this nearby airfields n that's where all the speed and vectoring begins.B4 we hand over to Approach, there must b a min of 10NM. Yes we cud keep them on ground but it's not good for ATC as we wud be blamed 4 every delay. Someone said it is better to delay on ground than in the air...what's ur opinion? How about the 737's opinion? Priority is given to the PK inbound inorder to reduce the workload of the 132.6 ATCer. A lot of coordination takes place between Area Controller n Flow/Approach especially in bad wx. We'll start looking into ur inputs n c how we can smoothen up things. After the unilateral routes for PK, we are going to split the 132.6 into two sectors, hopefully by the end of 2006. That will greatly reduce Controller workload as now one Controller has to monitor tfc over PK/VKB/IGARI(inbound and outbound from Penang) via VKB and also tfc climbing out of SIN to BKK n vice-versa.ATS is working on it and we are glad to c some progress now.So when can we have the teh-tarik session?Cheers