Guys, if you go to http://www.nats-uk.ead-it.com/ (or http://www.ais.org.uk/), then click on “eAIPPackage”, you get the current AIP, which says “when operating within United Kingdom airspace in accordance with IFR (… etc …)”.
boscomantico wrote:
why have they cancelled AIC Y 128/2019?
Because its content was integrated into the AIP?
arj1 wrote:
They’ve moved it now to CAP413 where it should be.
Do you mean this new version here?
It makes no mention of 2000 as an IFR squawk either…
So the question still remains: why have they cancelled AIC Y 128/2019?
arj1 wrote:
There is also an older site at http://www.nats-uk.ead-it.com, which contains even more outdated info.
I don’t think it is old. I even believe it is the official one. You also get there from www.ais.org.uk. But it is important to go through the front page to get the valid version of the AIP.
Indeed. There is that weird “aurora” portal, which leads to some outdated documents. Looks like aurora shall only be used to advise of any changed to be made to the AIP.
boscomantico wrote:
have just checkout what the UK AIP says… here
That link is for the January 2019 AIRAC. So clearly out-of-date.
How did you get to that link?
boscomantico wrote:
What is also interesting is that the AIC (from February 2020) which introduced the obligation to use squawk 2000 for uncontrolled IFR in the UK (local copy still here) has already vanished again from the list of current AICs, And the AIP itself (as linked above) still says something entirely different wrt to squawk 2000…:Code 2000. When entering United Kingdom airspace from an adjacent region where the operation of transponders has not been required; or by Mode S transponder equipped aircraft on the aerodrome surface when under tow, or parked and prior to selecting OFF or STDBY – unless otherwise instructed by ATC.
They’ve moved it now to CAP413 where it should be. Although it is even more interesting:
Copy of the AIP at https://www.aurora.nats.co.uk/ says what you just quoted. BUT!
Copy of the AIP on Eurocontrol EAD says:
2.2.1 e) Code 2000. When:
i. entering United Kingdom airspace from an adjacent region where the operation of transponders has not been required;or
ii. when operating within United Kingdom airspace in accordance with IFR and is either not receiving an ATS or has not received a specific instruction from ATS concerning the setting of the transponder; or
iii. unless instructed otherwise by ATS, Mode S transponder equipped aircraft on the aerodrome surface when under tow, or parked and prior to selecting Off or STBDY.
There is also an older site at http://www.nats-uk.ead-it.com, which contains even more outdated info.
It is a mess!
The table in section 2.6 is out-dated. But the text in section 2.2.2.1 is correct. (yes UK CAA and NATS describe themselves as world leading)
I have just checkout what the UK AIP says… here. ENR_1_6_ATS_SURVEILLANCE_SERVICES_AND_PROCEDURES local copy
Turns out I was wrong. 7000 is the general conspicuity code, whereas others (like 1177 for aircraft in contact with London FIS) is an “other” conspicuity code. Lots of other very special use other conspicuity codes there. So yes, if the releasing controller wants to remain as non-committal as possible, he will will have to remain very unspecific.
What is also interesting is that the AIC (from February 2020) which introduced the obligation to use squawk 2000 for uncontrolled IFR in the UK (local copy still here) has already vanished again from the list of current AICs, And the AIP itself (as linked above) still says something entirely different wrt to squawk 2000…:
Code 2000. When entering United Kingdom airspace from an adjacent region where the operation of transponders has not been required; or by Mode S transponder equipped aircraft on the aerodrome surface when under tow, or parked and prior to selecting OFF or STDBY – unless otherwise instructed by ATC.
