Thedude said:
OK ..for all you contollers out there I have a question.
Concerning squak codes
How are these assigned and I am curious about the 7000 series codes. I have been getting an unusally large number of 7000 series lately.
Dude,
For the complete answer, you'd have to refer to the 7110.66, National Beacon Code Allocation Plan, or NBCAP. Unfortunately, as far as I know, It's not available on line; not that you'd really want to try to read and understand it. I probably couldn't.
The basics are here:
Controller's Handbook, 7110.65, Chap 5, Section 2
Beacon Codes are divided into different sub-sets for different purposes. Any Terminal facility (Approach Control or Tracon) has it's own subset(s). My facility uses 0200. Then that subset is further divided. We have eight codes (0270-0277) that are perminantly assigned to local operators, such as local PD, Air Ambulance, a local Parachute club, etc. Then we have eight codes reserved for local IFR operations which cue the ARTS computer to provide Minimum Safe Altitude Warning (MSAW). The remainder of the 0200 codes are for VFR ops, and DO NOT generate MSAW alarms. Adjacent Terminal Facilities use 0300 and 0400.
If the flight is going to get radar service beyond our local airspace, then of course, that requires an IFR or VFR flight plan in the NAS, which is the same thing as saying in the HOST Computer at the Center. The Host then assigns a beacon code.
Right now, the NAS is very stretched for beacon codes. For one thing, there are an awful lot of IFR aircraft out there. For another, thousands of aircraft that, in the past, would likely have flown VFR without Flight Following are now required, or are choosing to use ATC services, both VFR and IFR. (Think TFR violations).
At times, available codes run so short, we start getting IFR flight plans (proposals) all with a 2400 codes. When that happens, we will wait until you call for clearance, and then, (just to show how kludged up the NAS can be) we have to go to the FDIO terminal, and send two amendment messages. First, we remove the equipment suffix from your aircraft type, (Change a T/B733/G to a T/B733), and then change it
BACK. That generates a discrete code. (I've personally called the automation office at the Center to ask if there isn't a simpler way to force a discrete code assignment, and they say there isn't.) So now you know what the delay in getting a clearance or beacon code is sometimes about.
I'm sure the automation guys in the Centers are scrambling to make as many discrete codes available as possible, and probably has something to do with number of times you're asked to change codes during a flight. It would surely help if you guys could be pro-active in calling us to say when you've cancelled a flight, so we can remove the flight plan, or refrain from filing multiple flight plans to the extent possible. (I've personably seen a Lear with 5 flight plans to 5 destinations in 4 different States, all in the same hour). If you're just going to be late, call us, and we'll update the P-time, rather than file a second FP. On a day with IFR WX, it's not unusual to have 10-20% of flight plans go un-used....