Add Teesside FMC to non-discrete squawks

[hazzas-99]

Changes

Teesside Frequency Monitoring Code (FMC) / Listening Squawk established 7047.

Squawk needs to be added to list of squawks not to be auto-correlated.

Link to AMDT or Sector File issue/pr (page number on PDF)

2604 AIP

Files to be changed

• All files containing m_AutoCorrelateDisabledSQs
• All files containing Airspace_No_DUPE_Codes

[frazerxyz]

I can work on this.

Just to check, I should be ignoring instances only containing 1200,2000,2200,7000,7700,7600,7500 like this, but every other line should have 7047 added?

[hazzas-99]

@luke11brown can advise but we may as well make all instances (even those that don't currently have the listening squawks) match across the pack!

[Liaely]

@luke11brown can advise but we may as well make all instances (even those that don't currently have the listening squawks) match across the pack!

I've just checked the squawk allocations, we should not do that, as geographically different areas can utilise the same sets of squawks.

For example, 7047 is the Teesside FMC, and also:

• An Aldergrove Approach squawk,
• Biggin Hill conspicuity,
• RNAS Culdrose conspicuity

Whilst it is fine for TC Thames & RNAS Culdrose, I think Aldergrove Approach would like to have the ability to correlate all of their squawk allocation.

[frazerxyz]

Any more thoughts on how this should be implemented?