View Full Version : "Expedite vacating and enter the taxiway..."
breakdip
8th May 2021, 20:06
On one of the major international airports (EHAM) we operate into the ATIS message contains the following instruction: "Expedite vacating and enter the taxiway".
The airport charts provides additional information regarding taxiing: "Pilots shall contact Ground (without ATC instructions) immediately after vacating the landing runway".
Does this ATIS instruction wants me:
A) to enter the taxiway and continue taxiing while establishing two-way communication with a ground controller; or
B) to enter the taxiway and hold until two-way communication is established with a ground controller?
Most of the time we adhere to A, just because traffic density is low right now and we almost instantly establish good two-way communication. However, a colleague recently stated that B is the correct way to interpret the instruction. Any thoughts? Would this ATIS instruction be omitted when conducting Low Visibility Procedures?
It's poorly phrased in my opinion.
They should say: ""Expedite vacating and enter the taxiway. Once established on the taxiway centreline, hold position until contact with Ground is established".
I can't imagine they'd be happy to have aircraft taxying around without being in contact.
Might be worth a quick phone call or ASR to highlight ther issue to them?
Nightstop
9th May 2021, 08:37
EHAM has standard inbound/outbound taxi routings. Pretty daft stopping on the taxiway after vacating the runway when you know the published route and your approximate parking position. Conflict with other aircraft on crossing taxiways can be mitigated by adhering to basic Rules of the Air (on the ground). In the event that contact with Ground ATC can’t be established, just stop and wait for a follow-me.
Then they should say “Expedite vacating and enter the taxiway, continue following the published taxiway routes until contact with Ground is established”, and not leave it as ambiguous as it is.
breakdip
9th May 2021, 11:09
Agree, to both. Applying general rules of the air is always sensible, nevertheless, I do agree to Gonzo that the message is now rather ambiguous. That’s the point my colleague tried to bring across.
Do you both agree they can either:
A) omit the message as they are confident their standardized instructions are adhered to by all aircrew - both foreign and national; or
B) implement Gonzo’s suggestion?
Both solutions work for me. And indeed, a ring is always a good idea.
An airport ‘having’ standard taxi routes is a long way from aircraft being expected and encouraged to follow them without an ATC taxi clearance. Are they published? Replicated in Jepp etc? Is it clear they are to be followed at all times? Or are they more ‘this is what you can expect’?
Big airplanes don’t stop on a dime and passenger comfort is definitely something to consider.
After vacating from a high speed turn off, contact GND as you are clearing the hold short line while slowing down.
If they reply on your first call then continue at appropriate taxi speed for the conditions.
If they don’t then you slowly roll to a stop.
This is not “continuing” this is still in the process of “stopping”.
chevvron
9th May 2021, 15:45
Then they should say “Expedite vacating and enter the taxiway, continue following the published taxiway routes until contact with Ground is established”, and not leave it as ambiguous as it is.
Why even mention the taxiway; any professional pilot would use a marked turnoff onto a taxiway rather than across the grass; simply say 'Expedite vacating the runway and contact ground asap'.
Why even mention the taxiway; any professional pilot would use a marked turnoff onto a taxiway rather than across the grass; simply say 'Expedite vacating the runway and contact ground asap'.
Taxiway v RET, not taxiway v grass.
Your suggestion is what is causing the confusion. Some crews think they can continue to taxi without having 2-way with Ground, others that they should stop (and if they stop then where they stop can cause problems if they’re still on the exit).
For info we have this in the AIP entry at LHR:
Aircraft lands but cannot contact Heathrow Ground due to RTF congestion: In this case the pilot should completely vacate the landing runway and taxi into the first taxiway available. The pilot should then hold position until contact with GMC can be established
Expired chart but read the notes top right:
”Aircraft vacating contact Ground immediately”
Which means you’re still in the process of vacating the runway. Which means you’re still in motion. Otherwise it would have stated “after” vacating.
https://cimg2.ibsrv.net/gimg/pprune.org-vbulletin/1482x1899/image_9cddae763d174f1da013a741b1419f679b2f523d.png
simmple
9th May 2021, 19:07
It’s been a while and things could have changed but the answer is A.
When it’s busy you can get onto stand without talking to them, if you tuned into ground frequency and they need you they will call.
Easy when you go there often but......
Nightstop
9th May 2021, 19:57
EHAM ATC are the slickest on the Planet, believe me. If you can’t grasp that, don’t go there 😂.
https://cimg5.ibsrv.net/gimg/pprune.org-vbulletin/580x326/image_2483e660781667aeb9f1a080c80235041039fb1f.jpeg
breakdip
10th May 2021, 20:58
Great contribution all, thanks! Dropped this question in the crewroom today and was getting some good discussions going. I'll give them a ring and come back with their answer just for the sake of us all learning and contributing.
breakdip
11th May 2021, 21:54
...I'll give them a ring and come back with their answer...
The implementation of this message has its origin in several incidents where aircraft did not vacate the main landing runway in an expeditious manner - i.e. hampering traffic flow. The normal procedure would be to stop after completely vacating the runway and contact ground, but in this occasion ATC expects you to enter the taxiway, adhere to the standard taxi routes (i.a.w. AIP) while contacting ground frequency. This is only valid for the main landing runway, not for their 04/22 runway which is mainly used by biz jets, GA etc.