RV628PV Squawk..... Never had that before!

[81270]

Originally Posted by newt

ALT-> SBY
Select 7701.
SBY->ALT

That's how we were all taught to do it, isn't it?

- mark

that's how I've been taught so as not to create the 7700 inadvertent scenario

[rjbob]

Originally Posted by VH-VRN

that's how I've been taught so as not to create the 7700 inadvertent scenario

Bad idea...again, controllers would rather that aircraft don't disappear from their scopes for any reason.

The following is a direct quote from a controller:
Also, just to add from a controllers standpoint, I would rather see a limited data block with your callsign still associated with the primary target than seeing a primary target with no information whatsoever (as in, Squawking Standby). The time between the change is so miniscule that I do not believe it would be an issue.

Another quote I found (but this one is unofficial):
I think that the "turn to standby" when changing code is likely to have been dreamed up instructors sitting about on bad weather days who seem to like to try to turn flying into a black art.

Avoiding unnecessary steps is generally safer when piloting, also.
Bob

[rjbob]

Another thing...
Almost all the newer transponders, especially the digital ones, don't change to the new squawk until the last number of the new code has been entered.

Check your manual.

[Ironflight]

What many folks posting against the STBY procedure is that the folks posting that are all from Australia - different country, maybe slightly different rules and customs. I am with the Americans who have never heard of doing it that way, and don't - but its interesting that it is taught that way down under....

[newt]

Originally Posted by rjbob

Negative...Controller friend tells me that they know you are changing codes and would rather see a very short time with screwy numbers than the numbers disappearing altogether.

That doesn't make a lot of sense. I only see the flashing radar-paint indicator every few seconds. I can change from one code to another with the transponder off between samples and they won't even know.

- mark

[hgerhardt]

Originally Posted by Ironflight

What many folks posting against the STBY procedure is that the folks posting that are all from Australia - different country, maybe slightly different rules and customs. I am with the Americans who have never heard of doing it that way, and don't - but its interesting that it is taught that way down under....

Nope, in my case it was two tower controllers from KTOA who were part of a safety seminar. They were FAA employees. I had never heard of doing it that way either until then.

Heinrich

[rjbob]

Originally Posted by newt

That doesn't make a lot of sense. I only see the flashing radar-paint indicator every few seconds. I can change from one code to another with the transponder off between samples and they won't even know.

- mark

Cool...then they won't be able to see your inadvertent erroneous code even if you don't put it on STBY.

[KRviator]

Originally Posted by rjbob

Bad idea...again, controllers would rather that aircraft don't disappear from their scopes for any reason.

A worse idea is an incorrectly assigned ID block because TAAATS has assigned your location to the aircraft whose code you inadvertently selected or the system has dropped the ID block on a legitimate RPT flight because you cycled through his code. this is what happens when "the system" mucks up codes.

The following is a direct quote from a controller:
Also, just to add from a controllers standpoint, I would rather see a limited data block with your callsign still associated with the primary target than seeing a primary target with no information whatsoever (as in, Squawking Standby). The time between the change is so miniscule that I do not believe it would be an issue.

That is a quote from an American controller. While that may be the case for FAA Controllers it is not true for Australian controllers and presumably others. The point being, you need to know what your regulatory requirements are, not just blindly assume what should be done based on hearsay.

Another quote I found (but this one is unofficial):
I think that the "turn to standby" when changing code is likely to have been dreamed up instructors sitting about on bad weather days who seem to like to try to turn flying into a black art.

Again, in the US, possibly, but it is required procedure to select standby in Australia. Why? Because:

In Australia, under the TAAATS system, cycling "live" through codes could trigger the activation of various flight plans -- nine between 1200 and 1237, for example. With TAAATS auto coupling and flight "corridor" matching, it should be less of a problem; however, certainly not outside the realms of possibility that, whilst transitioning from one code to another, that another flight-plan could be moved from "announced" to "active"; based on autocoupling; rudimentary route segment and code match.

From AIP ENR 7.1.10

Originally Posted by Airservices Australia

Pilots must select the transponder to STANDBY before effecting an SSR code change and returning the transponder to ON/ALT.

Note: This action is required to prevent possible loss of displayed aircraft position/label information and possible misidentification of aircraft in automated Australian ATC systems due to temporary selection (while effecting the change) of a code already in use.

TAAATS is based on EuroControl, so presumably the same requirements will apply in Europe, but as I don't fly there, I can't say for sure. AIUI, a derivative of TAAATS has been sold to China so expect to see more of this "select standby" occurring.

[rjbob]

Thanks for the info, KRviator.
My wife and I will be visiting Australia within a couple of years so it's good to learn some of the technique differences.
Bob