Should I switch the transponder to STBY or not while changing codes?
I´m now reading Bob Gardner’s book “Say again, please” and there is this instruction on page 54:
Do not turn the transponder function switch to STBY while changing codes.
What is the reason for this? I’m a PPL student and my instructor told me the opposite.
transponder
add a comment |
I´m now reading Bob Gardner’s book “Say again, please” and there is this instruction on page 54:
Do not turn the transponder function switch to STBY while changing codes.
What is the reason for this? I’m a PPL student and my instructor told me the opposite.
transponder
add a comment |
I´m now reading Bob Gardner’s book “Say again, please” and there is this instruction on page 54:
Do not turn the transponder function switch to STBY while changing codes.
What is the reason for this? I’m a PPL student and my instructor told me the opposite.
transponder
I´m now reading Bob Gardner’s book “Say again, please” and there is this instruction on page 54:
Do not turn the transponder function switch to STBY while changing codes.
What is the reason for this? I’m a PPL student and my instructor told me the opposite.
transponder
transponder
edited Dec 3 '18 at 14:00
Machavity
2,1602529
2,1602529
asked Dec 2 '18 at 21:05
Hask Somatotoian
1958
1958
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The FAA started advocating not selecting standby for code changes after it was found that more often than one would expect, the transponder doesn't always come back on after standby. Seems they uncovered a number of switch failures.
I figure that someone decided that for TCAS it was better to have a transponder squawking any code than not squawking. But that is my own conjecture.
So for quite a few years the guidance has been to not turn to standby when selecting codes.
I have had the folks at Flight Safety lecture me after sim sessions, with pretty much the same story.
So I now teach students to just switch the codes, and not standby the transponder. And I suggest caution when dialing through "7xxx" although controllers I have talked to say it's not a big deal.
So the idea is to keep the transponder squawking, even though numbers are being changed. There is continuity in that they will continue to have returns while you are playing with the knobs. And if you ever have a switch failure, it will likely be on the ground.
Addendum: Also, with ADS-B, one is supposed to keep the transponder on at all times, when on the airport surface in a movement area. So I can see that the philosophy of managing the standby position will continue to change.
Also note that Bob Gardner's book was from the mid-1990's and things change. Both the transponder technology, the technology, such as ADS-B, TCAS (which also relies on transponders, as well as processing algorithms, which decide how to display transitioning codes.
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
|
show 1 more comment
The AIM implies that you should leave the transponder on ALT when changing codes—since if you are in standby you won’t be transmitting:
4−1−20. Transponder Operation
e. Code Changes
- When making routine code changes, pilots should avoid inadvertent selection of Codes 7500, 7600 or 7700 thereby causing momentary false
alarms at automated ground facilities. For example, when switching
from Code 2700 to Code 7200, switch first to 2200 then to 7200, NOT to
7700 and then 7200. This procedure applies to nondiscrete Code 7500
and all discrete codes in the 7600 and 7700 series (i.e., 7600−7677,
7700−7777) which will trigger special indicators in automated
facilities. Only nondiscrete Code 7500 will be decoded as the hijack
code.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "528"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faviation.stackexchange.com%2fquestions%2f57651%2fshould-i-switch-the-transponder-to-stby-or-not-while-changing-codes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The FAA started advocating not selecting standby for code changes after it was found that more often than one would expect, the transponder doesn't always come back on after standby. Seems they uncovered a number of switch failures.
I figure that someone decided that for TCAS it was better to have a transponder squawking any code than not squawking. But that is my own conjecture.
So for quite a few years the guidance has been to not turn to standby when selecting codes.
I have had the folks at Flight Safety lecture me after sim sessions, with pretty much the same story.
So I now teach students to just switch the codes, and not standby the transponder. And I suggest caution when dialing through "7xxx" although controllers I have talked to say it's not a big deal.
So the idea is to keep the transponder squawking, even though numbers are being changed. There is continuity in that they will continue to have returns while you are playing with the knobs. And if you ever have a switch failure, it will likely be on the ground.
Addendum: Also, with ADS-B, one is supposed to keep the transponder on at all times, when on the airport surface in a movement area. So I can see that the philosophy of managing the standby position will continue to change.
Also note that Bob Gardner's book was from the mid-1990's and things change. Both the transponder technology, the technology, such as ADS-B, TCAS (which also relies on transponders, as well as processing algorithms, which decide how to display transitioning codes.
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
|
show 1 more comment
The FAA started advocating not selecting standby for code changes after it was found that more often than one would expect, the transponder doesn't always come back on after standby. Seems they uncovered a number of switch failures.
I figure that someone decided that for TCAS it was better to have a transponder squawking any code than not squawking. But that is my own conjecture.
So for quite a few years the guidance has been to not turn to standby when selecting codes.
I have had the folks at Flight Safety lecture me after sim sessions, with pretty much the same story.
So I now teach students to just switch the codes, and not standby the transponder. And I suggest caution when dialing through "7xxx" although controllers I have talked to say it's not a big deal.
So the idea is to keep the transponder squawking, even though numbers are being changed. There is continuity in that they will continue to have returns while you are playing with the knobs. And if you ever have a switch failure, it will likely be on the ground.
Addendum: Also, with ADS-B, one is supposed to keep the transponder on at all times, when on the airport surface in a movement area. So I can see that the philosophy of managing the standby position will continue to change.
Also note that Bob Gardner's book was from the mid-1990's and things change. Both the transponder technology, the technology, such as ADS-B, TCAS (which also relies on transponders, as well as processing algorithms, which decide how to display transitioning codes.
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
|
show 1 more comment
The FAA started advocating not selecting standby for code changes after it was found that more often than one would expect, the transponder doesn't always come back on after standby. Seems they uncovered a number of switch failures.
I figure that someone decided that for TCAS it was better to have a transponder squawking any code than not squawking. But that is my own conjecture.
So for quite a few years the guidance has been to not turn to standby when selecting codes.
I have had the folks at Flight Safety lecture me after sim sessions, with pretty much the same story.
So I now teach students to just switch the codes, and not standby the transponder. And I suggest caution when dialing through "7xxx" although controllers I have talked to say it's not a big deal.
So the idea is to keep the transponder squawking, even though numbers are being changed. There is continuity in that they will continue to have returns while you are playing with the knobs. And if you ever have a switch failure, it will likely be on the ground.
Addendum: Also, with ADS-B, one is supposed to keep the transponder on at all times, when on the airport surface in a movement area. So I can see that the philosophy of managing the standby position will continue to change.
Also note that Bob Gardner's book was from the mid-1990's and things change. Both the transponder technology, the technology, such as ADS-B, TCAS (which also relies on transponders, as well as processing algorithms, which decide how to display transitioning codes.
The FAA started advocating not selecting standby for code changes after it was found that more often than one would expect, the transponder doesn't always come back on after standby. Seems they uncovered a number of switch failures.
I figure that someone decided that for TCAS it was better to have a transponder squawking any code than not squawking. But that is my own conjecture.
So for quite a few years the guidance has been to not turn to standby when selecting codes.
I have had the folks at Flight Safety lecture me after sim sessions, with pretty much the same story.
So I now teach students to just switch the codes, and not standby the transponder. And I suggest caution when dialing through "7xxx" although controllers I have talked to say it's not a big deal.
So the idea is to keep the transponder squawking, even though numbers are being changed. There is continuity in that they will continue to have returns while you are playing with the knobs. And if you ever have a switch failure, it will likely be on the ground.
Addendum: Also, with ADS-B, one is supposed to keep the transponder on at all times, when on the airport surface in a movement area. So I can see that the philosophy of managing the standby position will continue to change.
Also note that Bob Gardner's book was from the mid-1990's and things change. Both the transponder technology, the technology, such as ADS-B, TCAS (which also relies on transponders, as well as processing algorithms, which decide how to display transitioning codes.
edited Dec 3 '18 at 12:38
answered Dec 2 '18 at 22:18
mongo
12.5k1356
12.5k1356
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
|
show 1 more comment
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
9
9
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
Also, it is probably more likely for it to be "pilot error" than "switch failure" when the transponder doesn't come back on after setting the code....
– Lnafziger
Dec 2 '18 at 23:31
9
9
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
Modern electronically controlled transponders have a delay that waits until a few seconds after dialing stops before committing the change. And a lot of them are keypad entry now, which avoids the problem too.
– user71659
Dec 2 '18 at 23:42
1
1
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
For a while I would fly a plane daily which would not do the 0400 bit, and of course the local TRACON assigned 0400 bit codes. The unit would go to the shop, get certified and then the switch(i assume) would get spotty. I would negotiate another code with ATC. The only people who were really annoyed were the NYC TRACON folks. Then again, at one time, I flew equipment which had two digit transponders. Yep, 12 for VFR.
– mongo
Dec 3 '18 at 1:19
2
2
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
Good answer. I'd like to add that the transponder interrogation rate for terminal and enroute radars is quite low (5-10 seconds). As such, if you make the code change in less than 5 seconds, the radar will receive at most one, and quite possibly zero, transient codes. I don't suggest rushing through the code change, but it's worth knowing that ATC is not seeing every single transient code you cycle through as you're twisting the knobs.
– TypeIA
Dec 3 '18 at 16:29
1
1
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
@TypeIA Also, ATC will be very aware of the fact that they've just assigned you a new code and are expecting to see it change. Other than emergencies, it should never be a surprise to ATC when your transponder code changes.
– J...
Dec 3 '18 at 16:32
|
show 1 more comment
The AIM implies that you should leave the transponder on ALT when changing codes—since if you are in standby you won’t be transmitting:
4−1−20. Transponder Operation
e. Code Changes
- When making routine code changes, pilots should avoid inadvertent selection of Codes 7500, 7600 or 7700 thereby causing momentary false
alarms at automated ground facilities. For example, when switching
from Code 2700 to Code 7200, switch first to 2200 then to 7200, NOT to
7700 and then 7200. This procedure applies to nondiscrete Code 7500
and all discrete codes in the 7600 and 7700 series (i.e., 7600−7677,
7700−7777) which will trigger special indicators in automated
facilities. Only nondiscrete Code 7500 will be decoded as the hijack
code.
add a comment |
The AIM implies that you should leave the transponder on ALT when changing codes—since if you are in standby you won’t be transmitting:
4−1−20. Transponder Operation
e. Code Changes
- When making routine code changes, pilots should avoid inadvertent selection of Codes 7500, 7600 or 7700 thereby causing momentary false
alarms at automated ground facilities. For example, when switching
from Code 2700 to Code 7200, switch first to 2200 then to 7200, NOT to
7700 and then 7200. This procedure applies to nondiscrete Code 7500
and all discrete codes in the 7600 and 7700 series (i.e., 7600−7677,
7700−7777) which will trigger special indicators in automated
facilities. Only nondiscrete Code 7500 will be decoded as the hijack
code.
add a comment |
The AIM implies that you should leave the transponder on ALT when changing codes—since if you are in standby you won’t be transmitting:
4−1−20. Transponder Operation
e. Code Changes
- When making routine code changes, pilots should avoid inadvertent selection of Codes 7500, 7600 or 7700 thereby causing momentary false
alarms at automated ground facilities. For example, when switching
from Code 2700 to Code 7200, switch first to 2200 then to 7200, NOT to
7700 and then 7200. This procedure applies to nondiscrete Code 7500
and all discrete codes in the 7600 and 7700 series (i.e., 7600−7677,
7700−7777) which will trigger special indicators in automated
facilities. Only nondiscrete Code 7500 will be decoded as the hijack
code.
The AIM implies that you should leave the transponder on ALT when changing codes—since if you are in standby you won’t be transmitting:
4−1−20. Transponder Operation
e. Code Changes
- When making routine code changes, pilots should avoid inadvertent selection of Codes 7500, 7600 or 7700 thereby causing momentary false
alarms at automated ground facilities. For example, when switching
from Code 2700 to Code 7200, switch first to 2200 then to 7200, NOT to
7700 and then 7200. This procedure applies to nondiscrete Code 7500
and all discrete codes in the 7600 and 7700 series (i.e., 7600−7677,
7700−7777) which will trigger special indicators in automated
facilities. Only nondiscrete Code 7500 will be decoded as the hijack
code.
answered Dec 2 '18 at 22:33
JScarry
3,9311724
3,9311724
add a comment |
add a comment |
Thanks for contributing an answer to Aviation Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faviation.stackexchange.com%2fquestions%2f57651%2fshould-i-switch-the-transponder-to-stby-or-not-while-changing-codes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown