Defining sectors with varying upper altitudes

[Karl Kornel 964857]

Good evening!

 

I am wondering if anyone here has advice for how to define two sectors, where they overlap partially, and the ownership depends on what altitude you are at.

 

Here is the situation: There are two approach airspaces: CVG_APP goes from SFC to 13,000; DAY_APP goes from SFC to 10,000. The two approaches share a common border, except for one area.

 

The area is the lateral airspace around KILN (Airborne Airpark, where DHL used to live before they left). DAY_APP owns the airspace up to 10,000; CVG_APP owns the airspace from 11,000 to 13,000. Because DAY_APP airspace upper limit is 10,000 always, creating a sector definition for it is easy. What I wonder about is, how to define the extra airspace owned by CVG_APP?

[Stephan Boerner 945550]

Not sure if I understand the airspace correctly (with such questions, images are always helpful ), but why don't you just add the same lateral airspace border for the levelband of 10500 to 13500 to CVG_APP?

[Oliver Gruetzmann]

Karl,

 

as it sounds, you just need to define the SECTOR for DAY_APP first in the ESE file.

 

So the order

 

SECTOR:DAY_APP:0:10000

OWNER:...

BORDER:...

 

SECTOR:CVG_APP:0:13000

OWNER:...

BORDER:...

 

will do the trick.

 

In this case, CVG_APP owns his full airspace if DAY_APP is not online, else, DAY_APP will his airspace and CVG_APP his own without the parts owned by DAY_APP.

 

Hope this is what you needed

[Gergely Csernak]

Karl,

 

There is a strict rule how ES decides if an airplane is inside a sector or not. The rule is very simply: It tests the sectors in the order they are defined in the ESE file, and finds one then the rest is ignored. So in this case if you define DAY_APP first and CVG_APP later then both can be from 0 to their max level. In the KILN area altitude between 0 and 10000 will be allocated to DAY_APP and above 10000 to CVG_APP. That is what you are expecting.

[Karl Kornel 964857]

Karl,

 

There is a strict rule how ES decides if an airplane is inside a sector or not. The rule is very simply: It tests the sectors in the order they are defined in the ESE file, and finds one then the rest is ignored. So in this case if you define DAY_APP first and CVG_APP later then both can be from 0 to their max level. In the KILN area altitude between 0 and 10000 will be allocated to DAY_APP and above 10000 to CVG_APP. That is what you are expecting.

 

Thank you both for the information! I already moved the sector definitions so that DAY_APP comes before CVG_APP, and the overlying center comes at the very end.

 

Here is the interesting fact, though: The way it should work is, CVG_APP should never own the airspace in that area from 0 to 10,000. If DAY_APP is online, then DAY_APP owns the airspace. If DAY_APP is not online, then either the airspace is owned by the overlying center, or it is uncontrolled airspace.

[Oliver Gruetzmann]

Hi Karl,

 

in this case the only thing you can do is to split the sector definition.

 

So you need to define one sectorline CVG_APP_0_13000 and one CVG_APP_10000_13000

 

Then you define two sectors. If you want them treated as one within Euroscope, use the same name for both Sectors.

[Karl Kornel 964857]

OK, will do. Thanks!