Just out of curiosity. If you get assigned a squawk code and you don’t like it out of superstition or other negative associations you have with it, can you request a new one?
No, there is no procedure for assigning a new squawk code because a pilot is superstitious. The whole system behind assigning squawk codes is fairly complex, and requesting new codes for non-operational reasons would put extra load on the system for no reason. In many cases, the controller doesn't even have the option to manually change the code, and doing so could result in significantly increased workload (actually getting the code, updating the flight data record, communicationg with the pilot, coordinating with downstream sectors etc.).
Squawk codes are a limited resources, we only have 4096 of them, and the system is already near its limit in busy airspaces. If we started to change codes just because we feel like it, we may very well run out of codes. And how should we choose which codes to avoid? Some probably wouldn't like codes such as 4666, others 1313. What about a pilot not liking 2403 because it happens to be the date a relative of his died? 4 is an unlucky number in Chinese culture, should we avoid all squawk codes with 4 in them?
We use numbers in aviation for all sorts of things, all the time, and it simple does not make sense to avoid some of them for non-operational reasons.
You can request a new one, but it’s up to ATC to decide whether to change it. Some will and some won’t, but mostly it depends on how busy they are.
I’ve seen discussions (in a private forum) about the specific case of pilots unhappy with 666, and a few controllers reported having gone out of their way to find a new squawk code that also had 666 in it. Others reported that they just change it themselves as soon as they see it. But the majority didn’t care either way.
Well you can always ask...
ATC is unlikely to give you a requested code or change your code though. There are a few ways to get a code, either from an IFR flight plan submission, or from a local block(s) the associated controller uses for various things. How they are assigned is discussed here and the most recent beacon allocation plan can be found here. I cant say I have ever heard of it happening nor was i taught any such procedure in my flight training.
A couple of times I have heard requests for change and they have been granted. Several years ago I asked a couple of approach controllers about it. The supervisor said that he simply avoids numbers with "666" because he is aware of pilot concerns.
In the days of codes being entered by dial switches, it happened, but was not common that there might be a sticky bit on the switch. One plane I flew had that with the 0400 bit. Fortunately, it rarely happened that a code was assigned with that bit. If one was assigned, spinning the knob a few times might get it to work.
Normally the controller only has blocks, which at best, are the last two digits of the code. So their ability to change codes is limited.
So I can't tell you the rules, cite the controller handbook, or provide a copy of a procedure, but I will say that it has been done, I have heard requests for different codes and I have heard the controller accommodate the request.
Yes, you can. "Center, N123DY request a new squawk." There should be no problem with being issued a new one. The "06" subset is one of Denver Center's enroute squawks, so 0666 gets assigned pretty much every day. I've reissued squawks for that code on several occasions. It's not a big deal.
Fulfilling your request for a code consists of my pushing a button, entering your aircraft ID (which we have a 3-digit shortcut for), and reading the new beacon out to you.