44 replies to this topic

[Jamie Fox]

New version 2012/08 now available:
London FIR (Euroscope)
London FIR (VRC)

For Euroscope users, the Olympics CAS(T) is in the 'ARTCC high boundary' section and the airspace base labels are in the 'Freetext' section; both will need to be enabled in order to see the added airspace. This also applies to other airspace that has been added in the past, such as the Norwich CTA - if you don't switch it on, you won't see it!

The base of CAS(T) is shown with a '/' in order to distinguish it from the plethora of other bases of CAS that are still visible.

The temporary reporting points, routes and STARs and there for curiosity and reference, as they're not expected to be used. For Southend/Biggin/Rochester the normal STARs operate by default, but for Farnborough/Manston be aware that the STARs will operate automatically for an appropriate flight plan, because Farnborough/Manston do not normally have STARs.

Changes in version 2012/08

	* AIRAC 2012/08 (effective 26th July 2012):
	   * Danger area D011 withdrawn, D011A, D011B and D011C introduced
	   * Lashenden/Headcorn EGKH ARP co-ordinates amended
	* AIRAC 2012/07 (effective 28th June 2012):
	   * East Midlands listening squawk 4572 introduced (main squawk range amended 4550-4571)
	   * Oxford Approach frequency changed to 127.750 (not previously in sector file, Oxford positions added)
	* AIRAC 2012/06 (effective 31st May 2012):
	   * Leeds Approach listening squawk 2677 introduced (main squawk range amended 2655-2676)
	   * East Midlands EGNX SMAA, very small changes to dimensions of 2100ft area (already added in 2012/05 sector file)
	   * OCK3E/2J (Heathrow), WILLO3D/2J (Gatwick) level restrictions - FL270 by GIBSO becomes FL270 by 15nm before BILNI/27nm before BEWLI
	   * Shoreham EGKA ATIS frequency amended from 125.3 to 130.97
	* Olympics temporary controlled airspace (CAS(T) and STARs added, and Atlas ATC position. The bases of CAS(T) are shown preceded by a '/' to distinguish them from other CAS bases.

Edited by Jamie Fox, 26 July 2012 - 08:45 AM.

[Johan Grauers]

Just a question, the ever occuring problem with aircraft on UN859 and BCN VOR (times 2), is there anything that can be done about this?

I'm sure anyone who has controlled a LON sector has noticed it, ES incorrectly draws the route to BCN (Brecon) rather than BCN (Barcelona), causing incorrect intention code, sector handoff frequency, incorrect SEL entry for W, and so on.


I have to admit I'm not sure what's causing it, as far as I can tell BCN (Brecon) isn't a part of UN859 at all?

So, do we know what's causing it?
Can it be fixed?

Not a rant, but a question to see if we can do anything about this fairly simple but still annoying problem.

[Phillip Speer]

Not sure if can be fixed automatically but of you edit the route to UN859 PUMAL UN859 BCN then it works properly.

Phillip

[Jamie Fox]

The bad news is that it's not caused by anything incorrect in the sector file or the nav data, so there's nothing that we can do in there to fix it.

The good news is that you can work around the problem by amending 'UN859 BCN' to 'UN859 PUMAL UN859 BCN', which EuroScope understands correctly.

Without the EuroScope code it's impossible to say for sure what's happening, but what I think is going on is that EuroScope finds the airway start and end point first, and then tries to connect them up, even if it makes no sense. So for example, to process 'CPT UN859 BCN', EuroScopes says 'CPT - Compton', then chooses the nearest 'BCN' VOR to Compton, Brecon. Then it tries to connect them using UN859, which fails because Brecon isn't on UN859, but it tries, so you end up with a messy route to Brecon involving DIGUT, KIDLI, etc.

Amending to PUMAL seems to work because it breaks the above logic, as PUMAL is nearer to Barcelona than Brecon. It also works with any other such reporting point on UN859.

Edited by Jamie Fox, 03 October 2012 - 09:29 PM.

[Johan Grauers]

Well then there is a fix anyway, even though it takes a bit of manual work I guess we'll have to live with that, thanks