Lots of flights last night in LAX, as EVA016, tower told me vacated runway and cross RWY 24L also contact GND while I decelerating on RWY 24R. Once I was on first contact with GND on high speed taxiway Y, they told me to hold “06L/24R”? However the time I received the instruction, I’d almost cross the holding line for “RWY24L”, but I still tried my best to stop immediately (100% of brake) even I’ve pass the line.
I’m curious whether will you ignore weird holding instruction or like me stop nervously?
In my opinion, ATC evidently just forgot to remove the HOLD marker from the taxi route. You were told to cross in the exit message so I would say its fine to cross the runway, particularly given that you were then sent “already cleared to cross”.
This is most probably the cause of you not being fully across the first hold short line, so drag&taxi puts a hold in the message (which the controller did not realize). Especially considering you got a cross clearance before, it’s usually safe to cross. However if the hold instruction is on the line closer to the parallel runway, it’s better to hold.
This sign states that you must obtain permission to pass the track, as stated in the guide, pilots must obtain a pass permit (did not get permission) when passing each track.
Conclusion: it would be very good to get permission
The command was “exit runway, cross runway … and contact ground”. So:
Exit runway
Cross runway immediately without another request or stopping the planes
Contact ground after you are clear of all runways
If you contact ground before crossing the other runway and ask for a specific gate, you create this unnecessary hold by your own. If the IFATC gives you a taxi instruction with specific taxiways, runway crossings are always preset with hold. And if busy he won’t correct this. In the end you even give him more workload cause you need to request to cross again but you was already cleared to cross right at the exit.
But beware! If he only gave you exit, than hold short at the line, means nothing of your plane crosses this line. Not the tip of your nose or anything else!
This is because you requested taxi before exiting the runway. This is a system/controller error as they must unselect erroneous holds like that. You can’t hold short of a runway you’re currently occupying.
As others have said, it seems contacting ground early lead to this confusion. One of the shortcomings of not having voice ATC. To answer your original question, I can say that irl we always listen to what the most recent ATC instruction was. And if we are ever confused, clarify the instruction.
Requested a specific gate while rolling out towards HST
For drag and taxi to initiate this instruction, they were most likely on the runway or within the runway safety zone. The hold auto-generates based on position of the aircraft, meaning it appears they were still on the active arrival runway.
Following the instruction as issued – exit → cross → and contact ground from taxiway would provide a taxi route from their position (after fully crossing the runway) to requested gate.
Additionally, by switching to ground prior the runway crossing, tower is unable to send additional instruction to the pilot.
