ATC Commands Wishlist (Comprehensive List)

One of my favorite parts of listening to live ATC in the real world, is the respect and etiquette between the professionals. There rarely is a time when handing off a pilot or a pilot departing a controllers airspace when the two don’t say things like “good day, so long, bye-bye, etc.”. Currently it’s available when only requesting a frequency change and the controller approves the change without specifying another frequency. The camaraderie is one of my favorite aspects of this industry 🤙🏾

It would be awesome to hear those when all frequencies issue a handoff command to a pilot.

“NF208J Contact tower on 121.87, good day”. “Contacting tower on 121.87, NF208J, bye-bye.”

1 Like

“See ya’”, is more common than you may realize.


Absolutely, that’s another common one heard over liveATC. It’s not that I didn’t realize the commonality of “see ya”, it’s more that it didn’t come to the top of my mind when typing my reply lol. But you feel what I’m sayin 👊🏾

1 Like

Maybe we could have different small goodbye phrases like some mentioned above, and it picks one at random when we give aircraft a frequency change.

Even though that’s low on the priority list, it adds realism.

Would like to see more beneficial commands before this though.


Here is one for the approach controller:

A plane requests an ILS/GPS/whatever approach for a particular runway. That specific runway is not in use.

How about a command that says something like “######, requested runway is unavailable, expect vectors for runway ## approach.”


We don’t need that. Telling them to expect vectors for the runway they are given is all they need to know. The reasoning is irrelevant. Whether it’s unavailable, not-in-use, they’re in a plane with slow approach speeds, the runway isn’t long enough, it’s all superfluous. The runway to expect is all that’s needed.

And if they can’t tell they’re the only one inbound for 09 at KSAN while 20 others are headed to 27 and need some sort of extra explanation, this won’t help them much.


Well, they need some way to tell them that the requested runway is unavailable. Maybe not on Expert, but definitely on the Training Server.

The commands don’t differ from server to server. I see what you’re aiming at, but understand also that they really don’t need to tell them it’s unavailable. That may not even be the case.

All the pilot needs to know is where they’re going.

If pilots on the Training Server need a 3 page dissertation before they listen, that’ll never change, but negative training isn’t the answer. They need to hear one thing: “Expect vectors for runway 27”.

That tells them not to land 09. End of story.


Could you make this a wiki? That would be very useful

I see what you mean.

There should be ‘upwind’ (Heading away the runway you want to land on. Please correct me if i’m wrong) position so we can inform ATC controllers better so they can assist us more easily. (That’s what I think).

The groud thing may not be possible, but they may implement emergency ATC commands and they can probably add engine failures.

Nice topic, I think this commands are needed on IF… also happy birthday!!!

Then they should implement some of these to advanced only and people shouldn’t fly if they don’t yet understand, plus taxi way names and instructions aren’t all that hard to use. Chances are, if we had NATS (Charts) then it’d be really easy

I’m not quite sure what you’re asking for here.

If you’re asking for pattern entry on upwind, well, that just doesn’t happen, so it would never make sense to issue that command.

If you’re talking about telling a pilot who has just taken off to continue flying runway heading (away, obviously), we already have it. That’s what “extend upwind” means.

If you’re asking for a way to report your position on upwind, that, too, wouldn’t make any sense at all. If you’re at an actively controlled field, believe me, ATC knows you’re on upwind. They certainly don’t need to be told of it.

What are you after here, it’s kind of unclear?

I think the solution is a server which is really advanced, though the problem would clearly be that ATC would need to be retested, though it is doable.

1 Like


“######, you were instructed to taxi to runway ##. Turn left/right onto next taxiway, resume taxi to runway ##.”

Something like that? Idk.


“######, please exit the runway before contacting ground.”

MaxSez: interesting @AR_AR 11/15 list is now at 197 comment after the bump. Lotta work here, great comments over the years. Note few of the command that relate to Pilot specific request have yet to be implemented.
Oh My…

1 Like

I’d rather see… You were instructed to taxi to runway ##. You now have 7 days to think about your decisions. Good day.

But now seriously… I am not in favor of adding commands like that, pilots should follow instructions. A “please follow instructions” should suffice if a pilot is taxing to the wrong runway.


The problem is that they may not know what they have done wrong.