IFR Radio Communication

Jjames

New Member
I'll first apologize for being new and asking what some might think as stupid questions. Besides the Pilot Controller glossary is there a document to review what the proper exchange should be between pilot and controller during IFR operations? I realize that every scenario is different, just looking to build a base knowledge to handle different situations. Listening to the radios I've heard alot of pilots interjecting their own "flare". I just want to know whats right before I start training. Thanks in advance.
 
When the controller asks if you have the current weather at a non-tower, read to them the entire asos. (10 miles, ovc 1000, 29.92.........)
 
Where's that recording of the guy in the Cherokee who tells the ATC'er that his instruments are super duper precise and that she doesn't know what she's talking about and that she should stop bothering him? That's a great one to learn good radio procedures from.
 
Make sure you have a fish finder on board....



In all seriousness though, no apology necessary for being new, we all start somewhere. Welcome to JC!
 
If you have your PPL then you have already talked to a controller on a few occasions. It is more of the same, just throughout the entire flight. Listen for your tail number, read back instructions with tail number and comply.

Good idea trying to be prepared, but you will pick it up after your first flight or two in the system. Don't worry about making a mistake or not knowing exactly what to say, keep it simple and to the point. It's not the huge deal that some make it out to be.

Spend more time focusing on the actual requirements of the flight and less on how to respond to ATC. You can't get violated for stumbling your read back or not being as quick in your reply as a 20 year captain, but you can get violated for not knowing what is and isn't acceptable while under IFR.

Have fun!
 
I'd strongly recommend in general that if the controller says something you aren't familiar with, don't hesitate to ask for clarification. There is no such thing as a stupid question, stupid emergency or stupid request for assistance. Especially when you're airborne.

One thing I'd stress that will help the controllers help you, is they call traffic, you reply traffic in sight and they respond maintain visual separation from that traffic. Please respond "will maintain visual separation from that traffic/aircraft type". Please don't say I won't hit em or something to that effect. If you do, I can't really use visual separation. If you want to look like the most awesome aviator on the radios in that situation, reply traffic in sight and will maintain visual separation. You've said less than the first way and all the controller has to do is say approved as requested. That'll make you a controllers best friend. Actually, if you do that they'll probably assume you're a controller and bend over backwards to shortcut you, because to my knowledge, that exchange is only found in our controller guide book.
 
I'd strongly recommend in general that if the controller says something you aren't familiar with, don't hesitate to ask for clarification. There is no such thing as a stupid question, stupid emergency or stupid request for assistance. Especially when you're airborne.

One thing I'd stress that will help the controllers help you, is they call traffic, you reply traffic in sight and they respond maintain visual separation from that traffic. Please respond "will maintain visual separation from that traffic/aircraft type". Please don't say I won't hit em or something to that effect. If you do, I can't really use visual separation. If you want to look like the most awesome aviator on the radios in that situation, reply traffic in sight and will maintain visual separation. You've said less than the first way and all the controller has to do is say approved as requested. That'll make you a controllers best friend. Actually, if you do that they'll probably assume you're a controller and bend over backwards to shortcut you, because to my knowledge, that exchange is only found in our controller guide book.
Anyone that flies much should know, "in sight, maintain visual separation" go together.
 
Not sure which part specifically you are responding to. Conservatively 25% of the time it is issued at my facility there is no proper read back. Airline, Cargo, Charter, GA you name it. I had a Challenger pilot who presumably would meet your standards of should know fail to give a proper read back 3 times in a row when issued visual with an approach clearance. IIRC I got an approach clearance read back, a roger, a sixty second long angry tirade which included everything except his call sign and finally a good read back. It may seem like something everyone knows, but when you're in my shoes restating and coaching one out of every four clearances, its not so clear that they do.

Now if you're saying anyone who flies much should know to say in sight and will maintain visual when they see traffic, that's something I hear once a year at best. Might very well just be me though.
 
Must be your area or something. Those two go together because I don't want to have another radio transmission, and yes... it's on me to maintain separation. Most traffic calls are a complete no factor, so it's almost a way to get the control to just leave me alone so we can both go on to something more important. More than 500' vertical and more than a mile, I could care less. What I'd like to read back without sounding like a butt, is "In sight, no factor, maintain visual."
 
For an introductory rate of 99.95/hr I will offer you one on one controller pilot exchanges, via ICQ
 
Back
Top