If you're at high altitude, it's helpful to address which radio sector you're trying to reach, e.g. When I am on the radios, all I want on the initial call is the call sign, approximate location, altitude, and, if calling on 122.1, which VOR you're listening over. In the enroute portion, a check-in with altitude is all that's needed, super simple. If it is known to be IFR, then it's extremely helpful to check in with the type of approach you're requesting. Many controllers will just assign a visual approach if not stated and as long as it's VFR. If an IFR pilot is checking on and destined for an airport within 50 to 100 miles, then an initial call should include altitude, ATIS code they're going to a towered airport, and they're going to a non-towered airport, the weather, NOTAMs, and type of approach requesting. The position is extremely helpful to know if we are the right person to provide service. With this scenario, just a call sign and stating they have a VFR request with their position and destination is preferred. By the time the pilot has finished talking, another plane is calling. We are trying to find that aircraft on our scope, and then realize we aren't currently working the aircraft, so then we'll start typing in the callsign to get a code to start the process. Most controllers can't remember all of that, especially on an initial call. For VFR flight following, most pilots call up in their first call with everything: call sign, type plane, destination and route of flight along with their position. We get calls from pilots in many different environments. And if I'm not able to get your information into the computer right away, I may not remember it. At Phoenix at least, we don't have paper and a pen to write things down, so that means I'm limited to what I can type into the computer. The biggest difference between approach and tower is paper. If you give me all that on initial call and block my frequency, chances are I'm just waiting for you to stop talking so I can make my transmission to the higher priority aircraft, and not actually listening to what you're saying. This is especially important in satellite sectors where you're running multiple approaches to multiple airports. I prefer this because if you make a call and give me all the info initially, I may not be ready to type it in, or more importantly, I have a higher level priority coming up that I need to make sure the radio is clear of. Some people want them to say it all, but I personally want someone to just say "Phoenix approach, N12345 VFR request". How To Call An Approach Controller (TRACON) When we are busy, that puts us behind very quickly. That means we have to issue traffic for those 40 miles. If you tune in to 118.6 and we are dead silent, go ahead and give us all the information at once.Īs a side note related to this question, most of us (tower controllers) have our radar zoomed out to only about 12 miles, so a good distance to call us would be about 8-12 miles out from the airport, and I wouldn't call any earlier than 15 miles out.Ĭalling us from 40 miles out is too early. How can you tell if we're busy? If you're trying to call the tower and you can't get a word in edgewise, we are busy. When we address you, then you can give us your location, ATIS, and request. This tells us someone wants something so we can at least write down your callsign. When we are busy, simply say "Metro Tower, Cessna 833PB". That way we can avoid asking a lot of follow-up questions. As long as we aren't busy, it's preferred to call up with everything all at once "Metro Tower, Cessna 833PB, 10 miles north with Delta inbound for (request)".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |