|
|
|
|
|
|
by vishnugupta
4122 days ago
|
|
|
Thank for providing these insights! I used to play a neat little terminal game named "atc" in Linux (it's a part of "bsdgames") which I thought simulated air traffic controller's job to a decent level of accuracy. It was fun to start off with but I just couldn't cope up for more than 30 minutes. There were just way too many variables to hold in my working memory. E.g., an incoming plan that could potentially miss landing; a plane which is low on fuel, collisions and what not! Given the amount of stress levels I'd imagine ATC operators are rotated frequently; say once every hour or so? |
|
|
1. senior tower controller. 2. approach/dep controller (sorry its been about 25 years since I did the job, I think its a diff title, but basically its his job to say 'clear to land/take off' and really mean it - it really is 'clear'). 3. coord - link man between everyone in the tower and most people on phone 4. ground controller - moves the planes from the apron to the runway. Does not control apron - sometimes that a separate controller (surface movement controller), who lives in the little tower you might see on the terminal itself. 5. flight data - transcribes all the incoming plans into manual 'flight strips' - dull job but essential, if radar etc go away, the accuracy of the flight strips is essential. Most junior operator sits here.
In the ACC (Area Control Centre) there could be 100 controllers, some on shift, some just finished, some on breaks, most in teams of at least 2, a dozen flight data operators, and 5-6 seniors - big boss is the SAC - senior area controller (in Australia). Next boss is the SADC - senior app/dep controller, in charge of the team that generally operates exclusively within 30 miles - could be 15 people doing that all up.