ATC contributed to 15% of flight delays in December
The obvious solution is to roster the overtime the same way as other shifts. The EBA stipulates that reasonable overtime should be completed, I don't see why controllers should not do 1-2 additional shifts every 2-3 weeks. This is normal in other companies and it only seems to be the controllers that have a problem with it. ASA has a robust fatigue management system and therefor the constant complaining about fatigue is absolute rubbish.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The ASA fatigue risk management system was designed to find someone to sign off the residual risk potential
Lower Fatigue Risk for ATCs can be signed off by Shift Managers and System Supervisors (or higher)
Lower Medium Fatigue Risk can only be signed off by Unit Manager, Unit Tower Supervisor, ATC Line Manager and Operations Room Manager (or higher)
Higher Medium Fatigue Risk can only be signed off by Service Managers (or higher)
Higher Fatigue Potential can only be signed off by Northern / Southern Operations Managers (or higher).
[perhaps some older position titles but you and others will get the picture].
Someone will sign it off the risk to avoid a service continuity issue, or because their individual KPI's are affected.
The only thing that stops an ATC working every day of the year is a clause from the ATC Enterprise Agreement that says:
The maximum number of consecutive shifts worked, inclusive of additional duty or emergency duty, will be ten (10) shifts.
The maximum number of consecutive shifts worked, inclusive of additional duty or emergency duty, will be ten (10) shifts.
The only thing that stops an ATC working double or triple shifts is a clause from the ATC Enterprise Agreement that says:
With an employee’s consent, a rostered shift may be extended prior to the scheduled commencement time and/or beyond the nominal finishing time, provided that the total hours acquitted for the shift do not exceed ten (10) hours.
With an employee’s consent, a rostered shift may be extended prior to the scheduled commencement time and/or beyond the nominal finishing time, provided that the total hours acquitted for the shift do not exceed ten (10) hours.
And the BTW, it is my understanding that CASA, as aviation regulator, didn't accept ASA's arguments that ASA had "robust fatigue management system".
Last edited by missy; 14th Jan 2024 at 05:17. Reason: formatting, punctuation, grammar
The obvious solution is to roster the overtime the same way as other shifts. The EBA stipulates that reasonable overtime should be completed, I don't see why controllers should not do 1-2 additional shifts every 2-3 weeks. This is normal in other companies and it only seems to be the controllers that have a problem with it. ASA has a robust fatigue management system and therefor the constant complaining about fatigue is absolute rubbish.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
Being a bean-counter must be such a doddle.
We spend money on things but we want to spend less on those things (except us…) and get the same or better output. Some of those things are humans.
So, we need to get fewer humans to produce the same output as the current group of humans, or pay the current group of humans less to produce the same output. The ideal outcome is that we pay fewer humans, less, to get a better output. (Let’s be honest: The ideal outcome is that we pay them nothing.)
Fatigue is an impediment to the achievement of our ideal outcome. So, we’ll just spin it into an industrial relations bargaining chip used by the greedy and unscrupulous rather than a substantive risk to safety. Manoeuvre arrangements so that fatigue becomes a matter to be dealt with internally and privately, on an individual case-by-case basis, rather than having generally applicable and objective limits.
Come the year 1990, when we have pilot-less cockpits and controller-less ATC, we’ll shift our focus to the humans who maintain the equipment. There’s another bunch of greedy and unscrupulous workers who use fatigue as an industrial relations bargaining chip.
Eventually we’ll achieve nirvana, where the only thing we spend money on is us bean-counters.
Job done!
We spend money on things but we want to spend less on those things (except us…) and get the same or better output. Some of those things are humans.
So, we need to get fewer humans to produce the same output as the current group of humans, or pay the current group of humans less to produce the same output. The ideal outcome is that we pay fewer humans, less, to get a better output. (Let’s be honest: The ideal outcome is that we pay them nothing.)
Fatigue is an impediment to the achievement of our ideal outcome. So, we’ll just spin it into an industrial relations bargaining chip used by the greedy and unscrupulous rather than a substantive risk to safety. Manoeuvre arrangements so that fatigue becomes a matter to be dealt with internally and privately, on an individual case-by-case basis, rather than having generally applicable and objective limits.
Come the year 1990, when we have pilot-less cockpits and controller-less ATC, we’ll shift our focus to the humans who maintain the equipment. There’s another bunch of greedy and unscrupulous workers who use fatigue as an industrial relations bargaining chip.
Eventually we’ll achieve nirvana, where the only thing we spend money on is us bean-counters.
Job done!
The following 2 users liked this post by Lead Balloon:
The obvious solution is to roster the overtime the same way as other shifts. The EBA stipulates that reasonable overtime should be completed, I don't see why controllers should not do 1-2 additional shifts every 2-3 weeks. This is normal in other companies and it only seems to be the controllers that have a problem with it. ASA has a robust fatigue management system and therefor the constant complaining about fatigue is absolute rubbish.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The obvious solution is to roster the overtime the same way as other shifts. The EBA stipulates that reasonable overtime should be completed, I don't see why controllers should not do 1-2 additional shifts every 2-3 weeks. This is normal in other companies and it only seems to be the controllers that have a problem with it. ASA has a robust fatigue management system and therefor the constant complaining about fatigue is absolute rubbish.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
The airlines and customers should not have to face delays just because the controllers don't want to play their part in the system. We need a clean out and those who don't want to support the company should just go.
CityRail tried that bollocks on in Sydney in 2004 and again later years when they were in a similar boat - completely and utterly reliant on their crew working overtime to staff the normal roster. Crews were burning out and come EBA time, they said "You can stick your OT up your asre!". CityRail took them to court arguing they had to do reasonable OT and the courts found there was no acceptable definition of 'reasonable OT', the crew were contracted for 38H a week, and that was all they had to do. It wasn't their fault the network would collapse if they didn't work OT...
To the ASA guys and girls, I say this - Don't put your health or your relationship at risk trying to cover ASA's shortfall. You're no different to anyone else, you're just a number, and while I get that you take pride in what you do and want to keep us moving, if you choose to spend your RDO's at the beach with your family, and as a result I get "Clearance not available", I wouldn't care in the slightest. Your family comes first.
The following 12 users liked this post by KRviator:
The obvious solution is to roster the overtime the same way as other shifts. The EBA stipulates that reasonable overtime should be completed, I don't see why controllers should not do 1-2 additional shifts every 2-3 weeks. This is normal in other companies and it only seems to be the controllers that have a problem with it.
Originally Posted by airdualbleedfault ..."you give us x amount of controllers, we will handle x amount of aircraft" ...
The following 7 users liked this post by le Pingouin:
What makes Australian infrastructure so inefficient vs other countries with the same runway configurations?
The money, or the will to improve the situation in YMML apparently doesn't exist.
I believe you would discover that at other airports around the world with a similar configuration they would also have to wait for a landing aircraft to pass through the RWY intersection before they could depart an aircraft on the crossing RWY.
It's that simple I'm afraid.
The following 4 users liked this post by Done and done:
Delays are awesome. It means people spend more time and money in the terminal where the real money is made in retail. Which is what the airport owners want. If you look at Perth, the government is running billion dollar surpluses so could easily sort out the infrastructure except the airport is privately owned. It's all very laborious and time consuming.
The following users liked this post:
Perhaps you could provide us the solution
Last edited by Done and done; 20th Jan 2024 at 08:38.
The following users liked this post:
LGW 26L and 08R have a displaced threshold and taxiways that enter the runway prior to the landing threshold, so the departing is able to line up sooner than would be the case at eg MEL 16 B, or SYD 16R A1/B1/B2. Simple maths really as the aircraft is in position to roll as soon as the lander is vacating via the suitably spaced RETs. Gatwick has a declared capacity of 55 movements per hour and has effective ATFM tools to more easily switch between ARR and DEP biases.
BOM 27 also has a displaced threshold. Both 27 and 32 have a short distance to the runway intersection, this will give you higher movement rates than a 09/14 configuration.
Locations of the runways relative to the terminals is a factor. Another important consideration is the SID's. Do the departures have a left and right split? The application NAP can limit the movement rate as the spacing between successive departures needs to be increased. Rather than 1800m metres and airborne it becomes 2NM or more.
I recall getting a commendation for doing 55 movements per an hour on a single runway (16 before it became 16R), left for BN/CG, right for pretty much everything else.
Sydney gets unfairly compared to other parallel runway airports, give me 2 four thousand metre runways and terminals between the runways and see how well we do?
Last edited by missy; 20th Jan 2024 at 08:52. Reason: r
The following 3 users liked this post by missy:
Apples and Oranges. The debate has been going for 30 years. Investment in some good tools (reduced wake turbulence monitoring) , as well as having enough people for all the positions needed to be opened separately (no joining of APP/DEP/DIR etc )
How about artificial barriers to efficiencies? Sydney Cap - tie one hand behind your back!
How about artificial barriers to efficiencies? Sydney Cap - tie one hand behind your back!
The following 2 users liked this post by DROPS:
We know most of you are doing the best you can within the constraints.
The result (unnecessary delays) are NOT good enough for me.
Which airports do better?
Manila for one. 06/24 the main 13/31 the cross, haven’t googled the movements but it really is amazing.
Bali & Phuket also do a pretty good job considering 1 runway and mix of small to supers.
Then just look at the efficiency of controlling in places like Jakarta and many places around SE Asia (just not Singapore).
Manila for one. 06/24 the main 13/31 the cross, haven’t googled the movements but it really is amazing.
Bali & Phuket also do a pretty good job considering 1 runway and mix of small to supers.
Then just look at the efficiency of controlling in places like Jakarta and many places around SE Asia (just not Singapore).
Yes, I understand the rules are the constraint. We need to change the rules to increase capacity and throughput. The 80 aircraft per hour cap at YSSY is a good example of an easy fix.
We know most of you are doing the best you can within the constraints.
The result (unnecessary delays) are NOT good enough for me.
We know most of you are doing the best you can within the constraints.
The result (unnecessary delays) are NOT good enough for me.
The following users liked this post:
The headline of the article should really have been: "Airport privatisation and pretending ATC is a commercial business were really bad ideas for Australians." Subtitle: "(Unless you're milking airports and Airservices for millions.)"
The following 3 users liked this post by Lead Balloon: