PilotEdge Forums

I'm a little confused on switching to ground after turning off the runway. I know the rule is basically wait until tower says to switch to ground, but I do remember one lesson where the controllers were so busy that my CFI said to just switch. Everything seemed fine.

So moving up to a couple days ago when I rejoined PE.. Every time I turn off the runway, I've been waiting a long time. I'd finally say "Tower, 21C for ground". The tower controller would tell me to taxi on his frequency, but he would speak as "ground".

Now tonight, I turned off the runway and was again waiting. I decided to switch to ground because my impression from the last few interactions were that it really didn't matter which frequency you were tuned in to for post-flight taxi on PE. Well, I was wrong and was told I shouldn't have done that.

Thinking that may not be clear, sorry..

Before tonight:

21C: "Tower, 21C off the runway for ground."
???: "Cherokee 21C, Ground, taxi to parking via A."

So tonight I just switched to ground so it would make sense to me, but that was bad

On landing, if not provided with instructions by TWR to contact ground after xxxxxx, or to taxi via xxxxx and mointor xxx.xx, then cross back over the hold short line, and STOP (you are safe here), and indicate to tower "21C, clear Rwy nn on XXXXX" and wait. This is a very dangerous environment, always be safe, don't move without specific instruction.

If no response after a bit, still monitor TWR if you can, and contact ground with your location. Worst thing that will happen is that you get sent back to TWR, which you might if there was for example another runway to cross before the apron.

At a small airport, it is often the same controller handling both, so the frequency you use (practically speaking) in the end is not critical, not so at larger airports.

* Orest

Yeah, I understand all of those points, and I know there's no way I would have done this in real life. I just thought from my last few interactions with controllers that it was ok. (Mostly hearing "say intentions" instead of "contact ground")

I guess I'll treat it like the real world. If a controller messes up, I won't use it as the right to do the same.

Colin Payette wrote:Yeah, I understand all of those points, and I know there's no way I would have done this in real life. I just thought from my last few interactions with controllers that it was ok. (Mostly hearing "say intentions" instead of "contact ground")

We mainly just want to see where you are parking.

Colin,

There's no need to wait for a long time prior to telling tower you're clear of the runway. In real life, tower will normally be proactive, because they're only monitoring 1 airport and they can watch it like a hawk. The reality is, our tower guy is serving the role at 39 airports, and isn't able to proactively monitor your progress. Realistically, when you're issued the landing clearance, we've verified the runway environment is going to be clear and then we move on to another aircraft. For that reason, you may not hear back from tower promptly upon coming to a stop.

The solution, though, is not to break from real world procedure...the solution is simply to prompt the tower. What happens next WILL vary from controller to controller, based on how they elect to simulate it at the time. If there's a separate ground controller, you may be handed to them. If not, you might be told to taxi to the ramp and "remain this frequency", or you might be told to taxi to the ramp and "monitor ground". Sometimes, we'll actually have you contact ground (even though it might be the same physical controller). All of those are valid cases that occur in the real world, so we do them all here, too.

Thanks Keith, that makes sense. I guess I've been a little timid to prompt tower in this situation, but I'll just go for it.

Colin, then hopefully this is a valuable lesson in and of itself. Don't be afraid to speak up.