Conditional commands should not be given by ATC.
This may be true in the US, but it isn’t true in a lot of other places I am afraid. I am happy whichever route IF takes in terms of how ATC works, but lets not fall in to the trap of thinking these are not used anywhere just because one country doesn’t use them.
Thanks @Tristan_Hensley .
As I said I personally don’t mind whichever of the two routes is taken on IF. Both using and not using them are equally valid in terms of realism.
This instruction is used at a daily basis at my local airport (ESGG).
To give extra clarity controllers specify as follows:
“Scandinavian 441 behind traffic on final line up and wait behind”.
In case of missed approach, tower should be able to say the following:
“Execute missed approach, fly runway heading, climb and maintain 5000”
Go arounds and missed approaches cause a bit of chaos in IF, because of immediate turns into downwinds and traffic gets clustered up. Real life procedure is normally always to fly runway heading.
After level off: “Contact XX Approach”
Those are all fair points. I probably should’ve been more specific- those commands are barred in the U.S. Good examples, though!
Just used to U.S procedures over here. ;)
I hear this ATC command all the time at KPHL.
“American 2001 fly heading 260, cleared for takeoff.”
They do that because of a noise abatement area
I think that a good addition would be (this is an example from KBOS): [call sign], taxi runway 22R, taxi via (this is an example: Alpha, November, Cross 15R, hold short 15L. Taxiway names would be AWESOME! except maybe only on advanced. Some people on PG, and/or ESPECIALLY free flight might not understand it.
I wish we could request aircraft to follow another aircraft on ground frequency
“American 282, cross runway 22L, follow the JetBlue a320 on taxiway alpha whiskey.”
That would also be a great idea, however maybe just on advanced, same with my idea.
I wish, but we will need to have a inset airport map in the left hand corner too
I wish this simple message was added to the misc messages section: “Please be patient” or “aircraft on final, please be patient” for use when someone is impatient when told to hold short for arriving traffic. I know there is a “frequency is busy, please be patient” but it’s not the same. This message I’m requesting is for the people who request takeoff, are told to hold short, and then 10 seconds later request takeoff again. It would be handy for me.
Here’s another command idea: “Please disregard last” in case you accidentally hit a button or the command you say becomes moot afterwards. In these cases there isn’t a “correction” that needs to be made, so “Correction, Stand By” doesn’t quite work.
And one more: “Turn onto downwind.” Same as turn base, to help in spacing traffic
Follow company:
-Left to right
-Right to left
Hahaha this is so FAA
“Attention all aircraft, please allow enough space between traffic on final approach”
That fully gets my vote
Holding aircraft in stacks like around London Heathrow (EGLL)
Confirmed in the next update 👍🏻