Perth - speed up - slow down
Thread Starter
Perth - speed up - slow down
I can’t help but ask F100 drivers and tonight I’ll include the Network A320 drivers, what the story is with their lack of ability to reach Beverly or Julim, on time.
Forever in a day we fly into perth, reach the fix (up to 30 seconds early, but not late) do our 250 knots then get told to vector off to rejoin final, yep, behind an F100. Tonight we had speed cancelled and a time to make Beverly, made it fine, then got told to slow down, vector off but this time, it was behind a Network A320.... who earlier was given direct to Rolob as ATC could see they had no idea of space or time.
I know it’s not just me who suffers this daily, is it lack of technology on the F100 that makes it difficult? Can you guys uplink the latest winds prior to decent? Curious to know what it is, it’s becoming frustrating.
Forever in a day we fly into perth, reach the fix (up to 30 seconds early, but not late) do our 250 knots then get told to vector off to rejoin final, yep, behind an F100. Tonight we had speed cancelled and a time to make Beverly, made it fine, then got told to slow down, vector off but this time, it was behind a Network A320.... who earlier was given direct to Rolob as ATC could see they had no idea of space or time.
I know it’s not just me who suffers this daily, is it lack of technology on the F100 that makes it difficult? Can you guys uplink the latest winds prior to decent? Curious to know what it is, it’s becoming frustrating.
I fly an elderly jet and making fixes at a particular time isnt sonething that we can do easily. ATC know this and "Slow to 210 for spacing" or "maintain 250" is as good as they can make it for us. Its ATC's job to manage traffic flow and they should know which aircraft can do what.
In saying that an A320 should be perfectly capable of time at fix. If crews of a particular airline are showing poor airmanship then a quick phone call to the CP should fix it.
In saying that an A320 should be perfectly capable of time at fix. If crews of a particular airline are showing poor airmanship then a quick phone call to the CP should fix it.
Lack of technology would be my guess for the F100. We're talking about an airplane that was made in the 1980's. I reckon an iPad running Ozrunways is more advanced. Use that to get your JULIM / BEVLY estimates!
Why be so anal?
I am told also that the ATC computer program has to bear some of the blame for the whole Feeder Fix problems in this country
Join Date: Apr 1999
Location: Sydney, N.S.W. Australia
Posts: 149
Likes: 0
Received 0 Likes
on
0 Posts
Odd the Network A320 was tracking via ROLOB as they don’t generally arrive from the east on the BEVLY arrival. Are you sure about your recollection of space and time?
Lack of technology would be my guess for the F100. We're talking about an airplane that was made in the 1980's. I reckon an iPad running Ozrunways is more advanced. Use that to get your JULIM / BEVLY estimates!
Regardless of type, any professional pilot who can’t make good a time over a fix should be sent back to school.
Because they subtract 2 minutes from their estimate to ensure a limited slowdown.
Ive been overtaking one like he’s standing still and his estimate was way ahead of ours. We advised atc and got sequenced ahead.
Damn annoying to be stuck behind those Fokkers.
Then there’s the Fokker100 reported undershoot sheer on final....
Ive been overtaking one like he’s standing still and his estimate was way ahead of ours. We advised atc and got sequenced ahead.
Damn annoying to be stuck behind those Fokkers.
Then there’s the Fokker100 reported undershoot sheer on final....
Yes, I heard (rumour only) they (Network) have been advised from above (chief pilot) to subtract from their true estimate.
Is this true?
It frustrates me too.
Maybe we should all do the same.
Is this true?
It frustrates me too.
Maybe we should all do the same.
Australia is the only country in the world that imposes this “cross WAYPT at XX”, with the “up to 30 secs early, but not late” thrown in for good measure. I fly what would be considered a modern aircraft and the FMS has no function to readily assist with achieving these requirements - in fact, it actually throws you under the bus because the FMS displayed estimated time over a waypoint is usually about 3-4 mins later than the time you actually end up flying over it - the discrepancy appears to magically fix itself when you’ve got about 3-4 mins to run and no chance to fix it. This is not a case of unaccounted descent winds. Of course, we are aware of this and I usually just get the old whizwheel out to sort it out and achieve the requirement.
Everywhere else the the world, even where it is actually busy (eg New York), ATC just tell you what speed to fly and it all works out. What is especially frustrating is flying across the Bight at max chickens for 3.5 hours to then be required to “reduce speed to cross BVRLY at XX” - we’ve got ADSB/CPDLC - you can see where we are and what we’re doing...
By the way, I blame the system, NOT the controllers.
So, long story short, even relatively modern aircraft don’t necessarily have a function that assists with this issue.
(Other than distance to run and ground speed!)
Everywhere else the the world, even where it is actually busy (eg New York), ATC just tell you what speed to fly and it all works out. What is especially frustrating is flying across the Bight at max chickens for 3.5 hours to then be required to “reduce speed to cross BVRLY at XX” - we’ve got ADSB/CPDLC - you can see where we are and what we’re doing...
By the way, I blame the system, NOT the controllers.
So, long story short, even relatively modern aircraft don’t necessarily have a function that assists with this issue.
(Other than distance to run and ground speed!)
The system is well and truley broken - the whole idea of COBT (In my mind) would be to eliminate enroute delays, and yet I lose count of the number of times we taxi off exactly on time and still cop a slow down enroute. Not to mention the "reduce... reduce... reduce... oh, uhhh max speed cancel speed restrictions" trick (or vice versa) that the turboprops always seem to cop in the terminal area.
Join Date: Nov 2017
Location: Perth
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
many elements
A number of other places use ETT (estimated take-off time) as the COBT equivalent, with each port factoring in taxi time based on dept runway and time of day (obviously a simplified description). Usually its ETT plus/minus 5 minutes. COBT AND GDP does none of this.
COBT and GDP is a dinosaur of a measure because its strictly airline schedule dependent, only refreshed twice a day, often very poor at re-active measures when something goes wrong (ie wx, single rwy ops). Its basically got a disconnect between whats happening on paper versus reality.
From a ‘bus perspective, all we can do is adjust cruise and descent speeds to make the crossing time, and its usually quite a ‘bastardised’ process, just as it is with departing a hold at a specified time. Don’t even get me started with CTA steps.
As a side note, OZ runways is ridiculously accurate for referencing crossing times..beats Jepp any day of the week.
COBT and GDP is a dinosaur of a measure because its strictly airline schedule dependent, only refreshed twice a day, often very poor at re-active measures when something goes wrong (ie wx, single rwy ops). Its basically got a disconnect between whats happening on paper versus reality.
From a ‘bus perspective, all we can do is adjust cruise and descent speeds to make the crossing time, and its usually quite a ‘bastardised’ process, just as it is with departing a hold at a specified time. Don’t even get me started with CTA steps.
As a side note, OZ runways is ridiculously accurate for referencing crossing times..beats Jepp any day of the week.
Australia is the only country in the world that imposes this “cross WAYPT at XX”, with the “up to 30 secs early, but not late” thrown in for good measure. I fly what would be considered a modern aircraft and the FMS has no function to readily assist with achieving these requirements - in fact, it actually throws you under the bus because the FMS displayed estimated time over a waypoint is usually about 3-4 mins later than the time you actually end up flying over it - the discrepancy appears to magically fix itself when you’ve got about 3-4 mins to run and no chance to fix it. This is not a case of unaccounted descent winds. Of course, we are aware of this and I usually just get the old whizwheel out to sort it out and achieve the requirement.
Everywhere else the the world, even where it is actually busy (eg New York), ATC just tell you what speed to fly and it all works out. What is especially frustrating is flying across the Bight at max chickens for 3.5 hours to then be required to “reduce speed to cross BVRLY at XX” - we’ve got ADSB/CPDLC - you can see where we are and what we’re doing...
By the way, I blame the system, NOT the controllers.
So, long story short, even relatively modern aircraft don’t necessarily have a function that assists with this issue.
(Other than distance to run and ground speed!)
Everywhere else the the world, even where it is actually busy (eg New York), ATC just tell you what speed to fly and it all works out. What is especially frustrating is flying across the Bight at max chickens for 3.5 hours to then be required to “reduce speed to cross BVRLY at XX” - we’ve got ADSB/CPDLC - you can see where we are and what we’re doing...
By the way, I blame the system, NOT the controllers.
So, long story short, even relatively modern aircraft don’t necessarily have a function that assists with this issue.
(Other than distance to run and ground speed!)
Don’t know what you’re flying, but the Honeywell FMS that’s standard in most Australian buses will give you an estimate based on the current conditions to the second in which you will pass overhead the feeder fix. It’ll need a bit of managing as the conditions change, especially on the way down, but if you can’t cross the waypoint within 5 seconds of what you require, you shouldn’t be sitting in the seat.
From a ‘bus perspective, all we can do is adjust cruise and descent speeds to make the crossing time, and its usually quite a ‘bastardised’ process
However you often have to tweak it during descent if you really want to meet the exact time.
This is not a system flaw but perhaps just because the descent winds might be different to forecast.
Also once on descent, the FMS gives priority to maintaining descent profile compared to meeting a fix at a certain time.
I have flown with old school pilots who openly crunch numbers on the way down (ground speeds, time and distance, miles per minute etc ..without a calculator or a whizz wheel....geeze they really are so smart) as they think out aloud (or to show me how smart they can be be without the FMS) but it really is not necessary.
The people who say it (the RTA function) doesn't work just don't know how to use it.
Fair enough, whatever works best for you.
The bus actually has an RTA function which works quite well in my opinion. (Within 30 seconds, and designed to keep you within 30 seconds I think).
However you often have to tweak it during descent if you really want to meet the exact time.
This is not a system flaw but perhaps just because the descent winds might be different to forecast.
Also once on descent, the FMS gives priority to maintaining descent profile compared to meeting a fix at a certain time.
I have flown with old school pilots who openly crunch numbers on the way down (ground speeds, time and distance, miles per minute etc ..without a calculator or a whizz wheel....geeze they really are so smart) as they think out aloud (or to show me how smart they can be be without the FMS) but it really is not necessary.
The people who say it (the RTA function) doesn't work just don't know how to use it.
Fair enough, whatever works best for you.
However you often have to tweak it during descent if you really want to meet the exact time.
This is not a system flaw but perhaps just because the descent winds might be different to forecast.
Also once on descent, the FMS gives priority to maintaining descent profile compared to meeting a fix at a certain time.
I have flown with old school pilots who openly crunch numbers on the way down (ground speeds, time and distance, miles per minute etc ..without a calculator or a whizz wheel....geeze they really are so smart) as they think out aloud (or to show me how smart they can be be without the FMS) but it really is not necessary.
The people who say it (the RTA function) doesn't work just don't know how to use it.
Fair enough, whatever works best for you.
It it really is a piece of cake. If you can’t make the time at this point, you advise ATC and they give you vectors. Or you drop to a lower level and slow up. Green dot is a knot higher for every 1000 feet over 20. So you can get some good speed reductions down low. Especially east bound out of the jet.
Anyway, stick with it son.
From a ‘bus perspective, all we can do is adjust cruise and descent speeds