Talking to ATC

[time builder]

I've been working on this a lot lately.

Here's a couple pointers:
1. Know what you have to read back (altitudes, restrictions, headings, clearances, in particular), you don't necessarily have to read back things like altimeter settings, ident requests, or radar contact, but do let them know you got the message by giving them at least some response.
2. If you're talking back and forth with a controller, don't keep dragging out your transmissions with your call sign included, if they know your voice, and what you're talking about, keep things moving.
3. I've noticed my local controllers working hard not to slur words while they're talking fast, like V-O-R, it sounds funny to break between the syllables, but its effective.
4. Most of us know this, but know the routines, anticipate their needs, if you have traffic in sight, for instance, you will like likey be asked to maintain visual separation so they can relieve you or the other aircraft of an altitude or heading restriction for collision avoidance, anticipate these things.
5. Give them the information up front in a clear and concise manner (ie, don't make them play 20 questions).

 

[Ridgewoodpilot]

Say "with you" whenever you contact ATC.

Hey AC I thought its only proper to say "with you" when you're handed off to the next controller. At least thats what I was told by an old instructor, I wonder if that still holds true as opposed to the standard intro for your initial contact.

 

[GravityHater]

Find the Pilot Controller glossary too.

 

[southernpilot]

Never say, "With You".

 

[Dustin H]

Good info here

http://www.austincollins.com/radio.pdf

 

[hawk16e]

Before you call clearance, look over the sid, if applicable,for transitions you will likely get. Same with sids inbound. It'll take about a minute each, and you'll be looking at them anyway in a few minutes to get atis and such. Knowing what fix they're talking about will help your comm, and give you an idea of what's going on.