Reading back instructions

troopernflight

Well-Known Member
I was curious what input controllers had on this. I notice a lot of pilots read back altitude assignments in a certain way. For example, "NABC12, climb and maintain flight level 360", in which they respond "360 for NABC12" or "up to 360 for NABC12". I've always read back the full "Climb and maintain flight level 360, NABC12". Do you want to the full read back, or if busy, would you rather have the shortened version? I figured you would want the whole thing since it could be confused with a heading assignment. Thanks.
 
I figured you would want the whole thing since it could be confused with a heading assignment. Thanks.

This would be correct. It would take longer to double check that you understood correctly than to just read it back correctly the first time. On a similar note, I gave a foreign pilot a frequency change this morning. He read it back incorrectly, so I responded with ,"Negative, flip the switch, XXXX." Next thing I know, he's changed his squawk code to XXXX and still on my frequency. I should have known better than to use non-standard phraseology (in this case, especially since he was foreign!), but it did give us a little chuckle. If it had been busy, it would not have been funny, though, due to the added workload I created for myself.
 
He read it back incorrectly, so I responded with ,"Negative, flip the switch, XXXX." quote]

I meant to say, he then checked on, thinking he had changed frequencies but still on my frequency, so I responded, "Flip the switch, XXXX."
 
you could just say something along the lines of "flight level 360, callsign" no ambiguity and less words.
 
If you at least use your callsign with the readback, that's the first step toward controller-pilot bliss.

Had a couple guys today who didn't use their callsign with the first readback, so they got "Verify that was XXX." Didn't learn though; didn't use their callsign for the next transmission either.

"Well, at least we know it's him. He's the one that doesn't use his callsign." :p
 
Do controllers prefer altimeter updates to be read back? I usually confirm it with the callsign, ie,

Controller - "Bowling Green altimeter, 3006"
Me - "3006, Skyblaster Yada yada yada"

I can't remember if it's even required though...
 
Do controllers prefer altimeter updates to be read back? I usually confirm it with the callsign, ie,

Controller - "Bowling Green altimeter, 3006"
Me - "3006, Skyblaster Yada yada yada"

I can't remember if it's even required though...

There was another thread about this I believe. It's not required; "Roger" is good enough for me (with callsign of course).
 
I always just give the "SkyGod 123 (example ) out of 240 climbing to maintain 360". No one has ever complained and it really doesn't add to congestion.
 
Aren't you supposed to actually say altitude leaving when you get a new altitude assignment? Though nobody does it because of the freq congestion problems.
 
You don't have to read the altimeter back. The only time I would suggest reading it back is if you're not 100% positive you heard it correctly.

With reference to the altitude. The only time you have to read an altitude you're leaving is when you're non-radar, or checking on with a new controller. You could possibly be thinking of when you check on with a new controller and you say the altitude you're leaving (or level at) for your assigned altitude. Once your altitude is verified with that controller you don't have to necessarily report the altitude leaving when you're giving a new altitude. And the process begins all over once you talk to the next controller with the assumption that the previous controller never verified the altitude.
 
I just make sure you say something that indicates altitude (Not Heading or Speed) when giving that readback...

Lets say the clearance was "Climb and Maintain FL360", Possibilities for readback include:

-Climb and maintain FL360
-Up to FL360
-Leaving XXX For FL360

Just don't say "Roger 3-6-0" because for all I know you thought it was a heading. Same thing goes for heading or speed, something that tells me you understand what the clearance is. I could care less that you readback word for word the clearance, I just want to know you heard me correctly and understand it. I have had foreign carriers readback something vaguely and when I ask them to confirm it, they did not understand or misunderstood it......... We just want to know you understand the instruction..... Because a heading change instead of altitude or vice versa can be a big thing....... and don't forget the callsign even if you haven't heard another plane on the frequency for quite some time......
 
Aren't you supposed to actually say altitude leaving when you get a new altitude assignment? Though nobody does it because of the freq congestion problems.
Yes. A few reasons why.

Doing so occasionally generates weird looks from Captains, I've found.

Radio: "BrandX 3168 Regional Approach roger descend and maintain one one thousand DFW altimeter three zero one zero."
FO mic: "Leaving FL 185 descending one one thousand BrandX 3168."
Captain's interphone: "Boy, nobody says that."
I believe you only need to state your altitude leaving if you're under procedural control.
Negative. "At all times." See AIM 5-3-3 a (1) a.
 
I'm willing to accept that I'm wrong on this, but I'm not convinced that you need to state the altitude you're vacating while under radar control.

http://www.faa.gov/air_traffic/publications/ATpubs/AIM/aim0503.html#aim0503.html.4

(a) When vacating any previously assigned altitude or flight level for a newly assigned altitude or flight level.

Does that mean you need to report your new level, or report your current level as well as the new level?

I've never heard anybody do that, but that doesn't mean much these days...
 
if you are under radar contact you need not tell atc your alt (unless requested) except when checking on with a new controller.
 
Back
Top