So how do you read that back anyway? ("Change to my frequency")

bikert

Ejection Handle Pulled
Joined
Dec 7, 2015
Messages
346
Display Name

Display name:
bikert
When you're told "change to my frequency"... Should you change to the new frequency and THEN read it back on the new frequency, or do you read it back and then change?
 
I say "Wilco Cessna345" and then change.

Check in "Cessna345 on 125.1."
 
Last edited:
I believe that is addressed in the AIM Communications sections. Don't have time to look for it at the moment.
 
I read back the frequency with my tail number, to make sure I heard it correctly and so the controller knows the correct aircraft heard it. I get enough pause in while dialing in the new frequency for them to correct me if I'm wrong.

"134.55, N855WH". Dial. Flip. Talk.
 
"Over to 123.45, N123BB."
"ATC Name, N123BB, level, 8500"

Seems excessive? Sure. But its correct, IMHO.
 
ATC: November one two three switch to my frequency one two three point four five.
Me: twenty three forty five Skylane one two three
...one thousand and one, one thousand and two,one thousand and three...
Me: Skylane one two three on one two three point four five.
ATC: November one two three roger.
 
When he says "MY frequency" I'm going to be talking to the same controller. Most times I already have it dialed in and reply with "Already there, 7DS" or if I don't, "Now on 123.45, 7DS"
 
ATC: November one two three switch to my frequency one two three point four five.
Me: twenty three forty five Skylane one two three
...one thousand and one, one thousand and two,one thousand and three...
Me: Skylane one two three WITH YOU on one two three point four five.
ATC: November one two three roger.
FTFY :)

dtuuri
 
ATC: November one two three switch to my frequency one two three point four five.
Me: twenty three forty five Skylane one two three
...one thousand and one, one thousand and two,one thousand and three...
Me: Skylane one two three on one two three point four five.
ATC: November one two three roger.

This. (Except I only count to thousand and two. :) )
 
Freq and tail number. Check in with tail number and altitude.
 
From the AIM 4-2-3 d (2):

At times, a controller/specialist may be working a sector with multiple frequency assign- ments. In order to eliminate unnecessary verbiage and to free the controller/specialist for higher priority transmissions, the controller/specialist may request the pilot “(Identification), change to my frequency 123.4.” This phrase should alert the pilot that the controller/specialist is only changing frequencies, not controller/specialist, and that initial callup phraseolo- gy may be abbreviated.
EXAMPLE−

“United Two Twenty−Two on one two three point four” or “one two three point four, United Two Twenty−Two.”

In a nutshell...

Just let the controller know the new frequency, or come up on the new frequency and state your callsign. All other initial call up information should be omitted.

We do this in many low altitude enroute and/or terminal areas where frequency coverage becomes unreliable as aircraft traverse a controller's sector. It also happens during combining/de-combining of positions to alleviate frequency congestion.
 
I always make the change and then announce that I've made the switch. I skip the step stating I got the instruction as it seems redundant.
 
"Over to 123.45, N123BB."
"ATC Name, N123BB, level, 8500"

Seems excessive? Sure. But its correct, IMHO.

Basically what I do too, I just abbreviate it a bit



"BB over to 23.45" (as all our VHF comm freqs start in one)

"BB level 8.5"

If there are any restrictions or heading or altitudes assigned I'll repeat that.

"BB checking 8.5, on a runway heading"
Or
"BB checking in 8.5 for 10.5"
 
When he says "MY frequency" I'm going to be talking to the same controller. Most times I already have it dialed in and reply with "Already there, 7DS" or if I don't, "Now on 123.45, 7DS"


When they say that, they could be monitoring more than one sector. OR it could be that something went wrong with the radio and he's using a back up freq. Lots of reasons why they would say that.
 
Post #6 @SkyHog is what I do as well. Even if it's the same person I'll check in with an altitude (and heading/direct to fix) if applicable.

Could it ever happen that a shift change happens at that EXACT moment? Switch to my frequency results in a new voice? In that case the new controller might not know what's going on?
 
Post #6 @SkyHog is what I do as well. Even if it's the same person I'll check in with an altitude (and heading/direct to fix) if applicable.

Could it ever happen that a shift change happens at that EXACT moment? Switch to my frequency results in a new voice? In that case the new controller might not know what's going on?

That wouldn't happen. Controller's have to give a brief to the oncoming controller to let them know who is where and what they're doing. They would wait that second and a half it takes for you to come up on the other frequency before they'd hand off the position to the next controller.
 
That wouldn't happen. Controller's have to give a brief to the oncoming controller to let them know who is where and what they're doing. They would wait that second and a half it takes for you to come up on the other frequency before they'd hand off the position to the next controller.

Cool..next time I get that request maybe I'll try to save some oxygen and reduce my readback length :)
 
No need to give the altitude on the new frequency. It's the same controller working the same position, there is no need to verify the Mode C readout.

"123.45 for N0JH"
*switch freqs*
"N0JH made the switch."
 
I always acknowledge on the original freq: "change to 132.25 Cirrus22G". Then on the new freq: Cirrus 22G on 124.9.
 
When you're told "change to my frequency"... Should you change to the new frequency and THEN read it back on the new frequency, or do you read it back and then change?

Say nothing before changing frequencies, say on the new frequency "Belchfire 34 Alpha made the switch" or "Belchfire 34 Alpha on [new frequency]".
 
When people check in using "with you" on PilotEdge, I usually include "...and also with you" in my response.

If you're religious, it's hilarious.
 
I've always considered flying a spiritual experience.
 
I always make the change and then announce that I've made the switch. I skip the step stating I got the instruction as it seems redundant.

The reason for reading back before switching isn't redundant, it's to verify that you've heard the correct frequency. If you switch, and it's the wrong frequency now you may be lost. I know most of us have dual radios, and most of them flip-flop channels so going back to the original frequency is easy, but simply making sure you have it right the first time is better and more efficient. I have recently flown a plane where Comm2 was inop and Comm1 was an old school dial radio with no flip flop, so if you switch to the wrong freq and forget the original one, you've now screwed yourself.
 
When he says "MY frequency" I'm going to be talking to the same controller. Most times I already have it dialed in and reply with "Already there, 7DS" or if I don't, "Now on 123.45, 7DS"

This. If I'm really on top of things and already have the new freq dialed in, or if I can dial it in fast enough while it's being read to me by the controller, I just flip-flop and check in on the new freq.

Interesting that the AIM excerpt MarkZ posted doesn't say anything about whether or not to read back the instruction on the original frequency.
 
When people check in using "with you" on PilotEdge, I usually include "...and also with you" in my response.

If you're religious, it's hilarious.

You've been away from the Catholic Church for a few years. The response as of 2008 is now "...and with your spirit" although I still can't stop saying "...and also with you"
 
The reason for reading back before switching isn't redundant, it's to verify that you've heard the correct frequency. If you switch, and it's the wrong frequency now you may be lost. I know most of us have dual radios, and most of them flip-flop channels so going back to the original frequency is easy, but simply making sure you have it right the first time is better and more efficient. I have recently flown a plane where Comm2 was inop and Comm1 was an old school dial radio with no flip flop, so if you switch to the wrong freq and forget the original one, you've now screwed yourself.

There is a controller on this thread telling you to do what I outlined. I see your point if you're turning dials, but with flip/flop so common it seems moot. Personal preference there, but I still submit that you taking the controller time to verify the freq when you have a flip flop is not the most efficient use of their precious time.
 
Say nothing before changing frequencies, say on the new frequency "Belchfire 34 Alpha made the switch" or "Belchfire 34 Alpha on [new frequency]".

It takes me five or ten seconds to set the new frequency in, so I at least acknowledge with my call sign before doing that.
 
There is a controller on this thread telling you to do what I outlined. I see your point if you're turning dials, but with flip/flop so common it seems moot. Personal preference there, but I still submit that you taking the controller time to verify the freq when you have a flip flop is not the most efficient use of their precious time.

I submit that doing the frequency changes as described in the AIM IS the most efficient use of the controllers precious time.
 
Back
Top