1

Military and TMA Sectors Sequences since ACE2009A (UR 422 implemented)

Author Pascal PauchetAuthor Pascal PauchetIPAS data preparation TRAININGIPAS data preparation TRAININGEUROCONTROL- Tuesday, 20 January 2009

Coe RIF

European Organisation for the Safety of Air Navigation

2

Military and TMA Sectors Sequences since ACE2009A

Overlap of volumes still remains not allowed, however after UR422 implemented in ACE2009A overlap of sectors will be now allowed.

What will change after implementation of UR422 ? The use of a common volume into different sectors will be possibly allowed

in order to:

1. To define properly military airspaces overlapping the civil airspace.

2. In TMA, sector sequence calculation will not only based onto airspace volumes but now possibly applied to controller responsibilities shared along SID/STAR procedures. (Optional: volume shared under Adep, Ades, Rwys conditions)

3

Reminder: Airspace construction rules

The volumes for sectors must cover the WHOLE simulation area …

It shall cover this simulation area without any leaving HOLES. This also means that segments common to several adjacent volumes should be described with the same points without fail even if it seems unnecessary because the points are aligned.

VOLUMES, part of the definition of sectors, SHALL not OVERLAP geographically(3D)… (However in some particular cases after the implementation of UR422 in future ACE2009A, SECTORS may OVERLAP by sharing common VOLUME(S) which allocation will be conditioned as described in point 4 below: 

Until ACE2008B a VOLUME was not allowed to be allocated to several SECTORS but to only one unique sector.In ACE2009A in some particular cases sharing volume(s) between sectors will be possible:

1. Civil/Civil sectors TMA volume(s) sharing (under volume conditions :Adep, Ades, Arr/Dep 4 Rwys)

2. MIL/CIV sectors will be able to share a volume(s). It will be conditioned by the Type of Flight (Mil or Civil) entering the volume (after implementation of UR422)

4

Sectors sequence of a flight

Currently, the sectors are associated to 3D areas. The sectors sequence of a flight is computed by the Ground Flight Manager by identifying the succession of the sector volumes crossed by the corresponding 3D path.

In order to avoid ambiguous/arbitrary volume selections, it is assumed that there is absolutely neither overlap between the various volumes, nor any hole in the simulated airspace. This assumption is guarantied by IPAS.

This sectors sequence allows the system to allocate and distribute the sequence of controllers that is going to assume successively the flight, including the times at which they are expected to be transferred from controllers to controllers.

Using 3D volumes as areas of responsibility is particularly well adapted when the controllers have only the responsibility of a real volume of airspace.

5

TMA sectorisation

In TMA, controllers often work in a shared airspace environment, each controller managing different aircraft in the same “Area Of Responsibility” (AOR). These could be parts of departure (SIDS) and/or arrival (STARS) procedures.

SID and STARS may cross common pieces of airspace and therefore it may not be possible to group SID or STAR in distinct volumes.

Since ACE2009A, the data preparator is now able to describe into the system the exhaustive list of TMA sectors, so that the Flight Manager is able on its own to provide the correct expected TMA controller sequence.

6

Military sectorisation (1)

The airspace is shared between civil and military controllers. A piece of airspace may be civil, military or both (new).

Now the system can manage both into a single piece of airspace (no more forbidden because of the previous sector non overlap assumption )

Now the system allows military sectors to overlap one or several civil sectors.

When processing a change of sector for a military flight, the FDPS attempts first to identify whether the new penetrated sector may be a military one before using the civil sectors. Respectively for civil flights, the FDPS only use the civil sectors to establish the sector crossing list.

7

Military sectorisation (2)

Once an aircraft is assumed by a military controller, it is now possible to maintain the aircraft under the responsibility of the military controller whatever the calculated downstream sectors.

S1 S2 S3

M1Civ1

Mil1

Civ1: S1 S2 S3 Mil1: S1 M1 S3

Figure 1 Military Sector Overlap

8

Military sectorisation into TMA

It is now possible to define military sectors overlapping TMA sectors… (Not to confuse with Volumes overlapping still not allowed)

S1 S2 S3

M1Civ1

Mil1

Civ1: S1 S2 S3 Mil1: S1 M1 S3

Figure 1 Military Sector Overlap

9

New sector definition (1)

The system now allows the use of common volume(s) into different sectors.

It is now possible in IPAS to:

1. Share a volume (box) between a civil sector and a military sector2. Share a volume (box) between several civil sectors under conditions

These civil Sectors conditions are related to one of the following topics:

1. Specific ADEP or ADES (and negations)2. Specific runway(s) with their usage condition (Departure/Arrival)

In IPAS, a sector may be described with one volume or more.

10

New sector definition (2)

However, the conditions used for a particular volume used by several civil (only) sectors is limited to a specific set of allowed combinations: (One per Condition)

1. ADEP X // not ADEP X

2. ADES X // not ADES X

3. ( Runway X or Runway Y or … (up to 4 for a single volume)) // (Runway Z or … ) // … (possibly more than 2 sectors overlapping)

11

New sector definition (3)

Combination Examples

Figure 3 Sector Parts to be used for Departures

12

New sector definition (4)

AS AN

IS IN

AP

FNFS

FI

TWREIDW

V1 V2

V3 V4

AP: V1 with not ADEP EIDWV2 with not ADEP EIDW

FI: V3 with not ADEP EIDWV4 with not ADEP EIDW

Figure 4 Overlapping Sectors to be used for Arrivals

Combination Examples

13

Combination Examples

New sector definition (5)

AS AN

IS IN

AP

FNFS

FI

TWREIDW

V1 V2

V3 V4

AP: V1 with not ADEP EIDWV2 with not ADEP EIDW

FI: V3 with not ADEP EIDWV4 with not ADEP EIDWTWR LFTT

V2

V1

UW UE

Rwy LRwy R

IAF 1IAF 2

INI: V2 with Dep Rwy LDEP: V1 with not ADES LFTT

APP: V1 with ADES LFTTV2 with Arr Rwy L

FIN: V2 with Arr Rwy R

App

App

App

FinApp

Ini

Dep

Fin

Figure 5 Overlapping Sectors with Rwy conditions

14

Runways

Condition name :Unique Identifier of the condition (string [5])

ADEP:

Negation :

Departure Airport.

Tick Box

ADES:

Negation :

Arrival Airport.

Runway 1

Runways

VOLUME CONDITIONS

Up Down Refresh Ok Cancel

Runway 4Runway 3Runway 2Runway Kind

Departure or Arrival

Conditions Panel (proposal)

An Ipas panel especially dedicated to the management of a volume condition.

This panel allows creating ‘condition’ instances as much as necessary.

This new panel is located near by the ‘volume’ section in the Sectors panel.

15

Condition Checking

IPAS checks that a condition name is unique.

IPAS allows associating a volume to a sector without any condition associated. Remark: A volume in a military sector is never associated to a condition.

IPAS allows associating a condition to a volume only for the civil sector.

IPAS checks a volume used by a civil sector has only one associated condition defined.

IPAS checks that this condition contains only one criterion (ADES (or NOT) or ADEP (or NOT) or Runways list)

IPAS checks that the condition criteria are not already defined.

For instance if the condition ‘A’ with the ‘ADEP X’ criteria is defined, IPAS checks that another condition (B) is not defined with the same criteria.

16

Condition and complementary condition

IPAS insures that in the airspace definition there will be an eligible volume and so an eligible sector whatever the aircraft features.

IPAS checks each volume used to describe a military sector is also used in another civil sector (volume with or without condition).

IPAS checks each volume used with an ADEP or ADES (positive) condition is also used in another civil sector with the complementary (negative-Not) condition.

Refer to Figure below.

17

Runway condition (1)

IPAS checks each volume used with a runway condition is also used at least once in another civil sector with another runway condition.

Refer to Figure below.

18

Runway condition (2)

IPAS insures the defined runway conditions comply with the other data exercise. The following checking will be performed by IPAS.

1. IPAS checks that at least one STAR is defined for an arrival runway condition.2. IPAS checks that at least one SID is defined for a departure runway condition.3. When a runway condition exists, IPAS checks the runways not associated to a

condition are not used in a SID or a STAR.

19

Volume consistency

IPAS checks the volumes consistency of the whole airspace by applying the following process:

1. Volumes selection:

Identifying all the volumes associated to the civil airspace (sectors). In the case where several identical volumes (same id) are defined, IPAS selects one.

(when reading the volumes composing each sector, the same volume name may be found several time through sectors, only the first civil one will be kept for the following checking)

2. Apply the following checking:

Detect the overlapping volumes. (overlap) Detect the areas not being into a volume. (holes)

20

Flight Manager sectorisation computation (1)

The “Ace_get_sector_list” service will be used to drive the condition associated to the volumes.

: SECTORS_FILE.DATA

: ASP : FM : CDMN : CWP

Reads

Ace_get_sector_list

Ace_get_sector_list

Ace_get_sector_list

21

Flight Manager sectorisation computation(2)

The FM currently uses the “Ace_get_sector_list” service so to get the sectors and the associated volumes.

The FM was adapted to comply with the new signature of the “Ace_get_sector_list” service.

The FM sectorisation computation process was adapted to take into account the eventual condition associated to each volume.

When processing a change of sector for a military flight, the FM attempts first to identify whether the new penetrated sector may be a military one before using the civil sectors.

Respectively for civil flights, the FM only uses the civil sectors to establish the sector crossing list.

22

Flight Manager sectorisation computation (3)

Algorithm dedicated to the sectors sequence computation.Let’s take the following figure:1. Sector civil TMA1 contains volumes V1, V2, V3 (without condition) and V4 with condition (Not

ADES X)2. Sector civil TMA2 contains volumes V5, V6, V8 (without condition) and V7 with condition (Not

ADES X)3. Sector military M1 contains the volumes V3, V4, V6 and V7. (without condition) 4. Sector CTR contains the volumes V4 and V7 with condition (ADES X)

23

Flight Manager sectorisation computation (4)

For instance the FM will determine the sector sequence as detailed below:Aircraft : CivilSector sequence = V1 => TMA1, V5 => TMA2Aircraft : MilitarySector sequence = V2 => TMA1, V3 => M1, V6 => M1, V8 => TMA2Aircraft : Civil, ADES XSector sequence = V1 => TMA1, V2 => TMA1, V3 => TMA1, V4 => CTRAircraft : Military,Sector sequence = V5 => TMA2, V6 => M1, V7 => M1, V4 => M1

24

END OF THIS DOCUMENT

Any Question ?

Pascal PAUCHET - RIF centre of expertise,EUROCONTROL Experimental Centre (EEC),BP 15, Centre du bois des Bordes,91222 Brétigny-sur-Orge Cedex, FranceTel: + 33. (0) 1.6988.7450 -- Fax: + 33. (0) 1.6988.7352mailto:pascal.pauchet@eurocontrol.intweb: <http://www.eurocontrol.int/>