...
Info | ||
---|---|---|
| ||
A change proposal (AIXM-414) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which adds a name attribute for the airspace volume. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-414 Change Proposal. |
Type
Whereas for the name the encoding in AIXM is quite obvious, the type of an airspace may have to be derived from some of its characteristics, e.g. the activity taking place or the kind of access restrictions that it enforces.
...
In case the designator is published in the ICAO Doc 7190, also the attribute designatorICAO should be encoded accordingly with 'YES'.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<aixm:AirspaceTimeSlice gml:id="ASE_AMSWELL_FIR"> ... <aixm:type>FIR</aixm:type> <aixm:designator>EAAD</aixm:designator> <aixm:name>AMSWELL</aixm:name> <aixm:designatorICAO>YES</aixm:designatorICAO> ... </aixm:AirspaceTimeSlice> |
...
PANS-AIM | type | localType | controlType | designator | designatorICAO | Remarks concerning Airspace.type | Remarks concerning Airspace.designator | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
FIR / UIR | 'FIR' | NA | optional | mandatory | 'YES' | The coded identifier shall be the one published in ICAO DOC 7910; if none, then the location indicator of the related FIC [Flight Information Center] shall be used. Examples: Langen FIR, EDGG Brussels UIR, EBUR | ||||||
TMA | 'TMA' | NA | optional | optional | optional | a. the ICAO Doc 7910 location indicator of the airspace or, in case it is not defined, the location indicator of the ATC centre providing services in the airspace; b. if there is no major ATC centre providing services in the airspace or if it does not have a location indicator, use the location indicator of the major airport situated within the airspace; or c. define a 4-letter code using the ICAO Country Code (provided in ICAO Doc 7910) and a unique combination of two letters such as the airspace identifier is not duplicated within the State or territory concerned for the same airspace type. Examples Tallin CTA (also Tallin ACC), EETT Palma TMA (also Palma TACC), LECP Luxembourg TMA, ELLX Split CTR, LDSP | ||||||
CTA / UTA / OCA | 'CTA', 'UTA', 'OCA' | NA | optional | optional | optional | UTA & OCA are Non-ICAO Recognized types of airspaces, but special types of control area, which are frequently used and published in AIPs. | ||||||
CTR | 'CTR' | NA | optional | optional | optional | |||||||
ATZ / HTZ | 'ATZ, 'HTZ' | NA | optional | optional | optional | a. the ICAO Doc 7910 location indicator of the airspace; b. if it does not have a location indicator, use the location indicator of the related airport/heliport situated within the airspace; c. if there is no related airport/heliport or there are more than one airport/heliport situated within the airspace
Examples: Zvekovac ATZ, LDZE Borwin Alpha HTZ, EHHJ Ameland HPZ, EHHPZAMEL Schinveld ATZ, EHATZSV Woensdrecht ATZ, EHATZWO Coningsby MATZ, EGXC | ||||||
Prohibited Area | 'P' | NA | optional | mandatory | optional | For airspace affected by special activities the coded identifier shall be composed of a group of digits and / or letters as follows:
Examples: DROTTNINGHOLM restricted area, ESR24 MONT GRAND MORNE alert area, CYA619 MATHIATIS danger area, LCD21 ECHTEN area PJE, EHVECHTEN GREDA (SINJ) protected area, LDX90 LESMO area, LHSLESMO For regulated airspace with activity ‘ATS’ the coded identifier shall be defined as follows: a. the ICAO Doc 7910 location indicator of the airspace; b. if it does not have a location indicator, use the location indicator of the related airport/heliport situated within the airspace; c. if there is no related airport/heliport situated within the airspace or in case the coded identifier is duplicated (e.g. TIZ and TIA with the same related airport)
Examples: Sveg TIZ, ESTIZESND Sveg TI, ESTIAESND Parnu FIZ, EEPU Lelystad AFIZ, EHAFIZLE The coded identifier of special use airspace that do not fall under the rules above, shall be composed as follows: a. nationality letters for location indicators assigned to the State or territory, which has established the airspace; and b. three letters for:
and c. a combination of up to 5 digits and / or letters unduplicated within the State or territory concerned for the same airspace type. Examples: TSA-LO-RENINGE UAV AREA, EBTSA15 TRA-LANGELAND (LAN), EKTRALAN TRA-PAPA ALPHA, LHTRA11A For P, D, R areas where the coded identifier ends with a number, if the part is also identified with a number, then a separator character ('-') should be added before the digits of the part. For example, EDR11-1, EDR11-2. This is necessary in order to avoid confusion between EDR11-1 (part 1 of Restricted Area 11 in Germany) and EDR111 (Restricted Area 111). Examples: Germany Restricted Area 111, EDR111 Germany part 1 of Restricted Area 11, EDR11-1 Germany part 2 of Restricted Area 11, EDR11-2 | ||||||
Restricted Area | 'R' | NA | optional | mandatory | optional | |||||||
Danger Area | 'D' | NA | optional | mandatory | optional | |||||||
Military exercise and training areas | 'TSA', 'TRA', 'MTR', 'PROTECT', 'D_OTHER', 'OTHER' | as applicable | 'MIL', 'JOINT' | optional | optional | In case no specific type is applicable, 'PROTECT' or 'D-OTHER' or 'OTHER' may be used for the coding. In addition a corresponding localType may be encoded. | ||||||
Other activities of a dangerous nature | 'D_OTHER' | as applicable | optional | optional | optional | |||||||
Aerial sporting and recreational activities | 'A', 'D_OTHER', 'OTHER' | as applicable | optional | optional | optional | Also another type may be used if applicable. | ||||||
Air Defence Identification Zone (ADIZ) | 'ADIZ' | NA | 'MIL' | optional | optional | |||||||
Flexible Use of Airspace (FUA) types | 'TRA', 'TSA', 'CBA' and 'RCA' | NA | optional | optional | optional | |||||||
Other special activity airspace types | 'W', 'A', 'POLITICAL', 'ASR', | as applicable | optional | optional | optional | 'A' and 'W' are mainly used in North America, but also in other regions world-wide. 'POLITICAL' is used for aviation relevant regions like ICAO regions, ECAC, etc., but can a also be used for non-aviation related regions like States, Provinces, etc. | ||||||
Traffic Information Zone | OTHER:FIZ | TIZ | optional | optional | NA |
| ||||||
Traffic Information Area | OTHER:FIZ | TIA | optional | optional | NA |
| ||||||
Parts | 'FIR-P', 'UIR-P', 'TMA-P', 'CTA-P', 'UTA-P', 'OCA-P', 'CTR-P'', 'ATZ-P', 'PART' | NA | optional | optional | optional | These types of airspaces are used as components to define the whole airspace of that type. 'PART' is an artificial airspace, which can solely be used as parent in the scope of an Airspace Aggregation (see section Geometry of Airspace). | a. the four-letter coded identifier of the child airspace (FIR, CTA, TMA, etc.), followed by; b. a combination of up to 6 digits and / or letters, unduplicated within the composition of the child airspace Examples: FIR-P, ENOR1 CTA-P – Debrecen CTA1, LHDC1 TMA-P – Brussels TMA NINE A, EBBR9A The coded identifier of the airspace of type 'PART' shall be composed by: a. nationality letters for location indicators assigned to the State or territory, which has published the airspace; followed by b. a combination of up to 8 digits and / or letters unduplicated within the State or territory concerned for the same airspace type. If the airspace type PART is used to define a child airspace with an already published ICAO location indicator, it is recommended to compose the code identifier of the airspace type PART by
Examples: Airspace within Belgium part of a sector, EB00001 Airspace within Spain part of Sevilla TMA, LECS2 | |||||
Class | 'CLASS' | NA | optional | optional | optional | Some countries publish ATS airspaces in ENR 2.1 according to their class and not as defined types (e.g. AIP Germany). AIXM 5 provides also a dedicated 'CLASS' value for Airspace.type. | The rule defined for TMA may be applied. | |||||
Airway | 'AWY' | as applicable | optional | optional | optional | Airway (corridor). A control area or portion thereof established in the form of a corridor. | a. nationality letters for location indicators assigned to the State or territory, which has established the airspace; followed by b. the route designator of the route segment the AWY is based on Example: AWY L179 corridor, EHL179 | |||||
National Airspace Structure | 'NAS' | NA | optional | optional | optional | For airspace of type NAS (National Airspace Structure - usually, the assembly of all FIR and UIR belonging to one State) the coded identifier shall be the nationality letter(s) of the state concerned. Examples: United Kingdom, EG Hungary, LH | ||||||
Control sector, Temporary consolidated (collapsed) sector. | 'SECTOR', 'SECTOR_C' | NA | optional | optional | optional | a. If a SECTOR or SECTOR-C is part of an ATS airspace (e.g. CTA, UTA, TMA, etc.) the coded identifier shall be defined as follows:
b. If there is no ATS airspace the SECTOR or SECTOR-C is part of, the coded identifier shall be composed of:
Examples: SECTOR within CTA LZBB, LZBBE7 SECTOR-C within CTA EPWW, EPWWTC SECTOR within TAMPERE CTA, EFESIN1 SECTOR (VERAM) within LISBOA FIR, LPVERAM | ||||||
Airspace for which not even an FIR is defined. | 'NO-FIR' | NA | optional | optional | optional | There are parts in the world for which there is neither an FIR nor any other airspace-type is defined. These airspaces will be marked as NO-FIR . | The coded identifier of the airspace of type NO-FIR shall be composed by the letters “XX” followed by a combination of up to 8 digits and / or letters, unduplicated for the same airspace type. Example: ANDORRA NO-FIR, XXANDORRA | |||||
Minimum altitude area. | 'AMA' | NA | optional | optional | optional |
| a. nationality letters for location indicators assigned to the State or territory, which has published the airspace; followed by b. three letters: ‘AMA’; followed by c. a combination of 5 digits and letters (allowed letter values are: N,S,E or W) defined as follows; the lower left corner point of the square defining the AMA shall be taken into consideration. Lower left corner point latitude and longitude are always expressed as full degree values so the following diagram applies for the composition of the coded identifier: Examples: AMA published by Sweden: ESAMA5713E Coordinates of the lower left corner of the square: 570000N 0130000E AMA published by Czech Republic: LKAMA4912E Coordinates of the lower left corner of the square: 490000N 0120000E | |||||
Military Operations Area | 'OTHER:MOA' | Military Operations Area | optional | optional | NA | necessary for Digital NOTAM, SAA.ACT and SAA.NEW scenarios | See rules for Military exercise and training areas | |||||
Remote Conflict Zone | 'OTHER:RCZ' | Remote Conflict Zone | optional | optional | NA | In support to the ICAO Remote Conflict Zone notification concept | ||||||
Free Route Airspace | 'OTHER:FRA' | FRA | optional | mandatory | NA | Airspace types related to the European Free Route Airspace concept.
| ||||||
Flight Plan Buffer Zone | 'OTHER:FBZ' | FBZ | optional | mandatory | NA | |||||||
No Planning Zone | 'OTHER:NPZ' | NPZ | optional | mandatory | NA | |||||||
Radio Mandatory Zone | 'OTHER:RMZ' | RMZ | optional | mandatory | NA | Supports the coding of airspace specified in the standardised European rules of the air.
| ||||||
Transponder Mandatory Zone | 'OTHER:TMZ' | TMZ | optional | mandatory | NA |
...
Tip | ||
---|---|---|
| ||
In an AIP information about the name, designator and type of an airspace may be published in various ways. The figure below shows the basic data of airspaces as they may be published in ENR 2.1 The figure below shows the basic data of airspaces as they may be published in AD 2.17. Although AD 2.17 states "designation" the information published, will be rather encoded as the Airspace.name and not as the Airspace.designator. The figure below shows the basic data of airspaces as they may be published in ENR 5.1. The figures below show the basic data of airspaces as they may be published in ENR 5.2. In this example the airspaces may have the generic type 'PROTECT' or 'D-OTHER' as there is no specific AIXM value for that kind of types. Also 'OTHER:MIL' may be used. The localType should then be used to encode the full textual name of the actual airspace type, e.g 'TRAINING AREA'. In the following example the airspaces will be coded with type TRA or TSA (and not PROTECT, as there are dedicated types for that airspaces). In this example the airspaces may not only have a name but also be coded with a designator, as published. The figure below shows the basic data of airspaces as they may be published in ENR 5.3. In this case airspace will carry different types. If available the specific type will be used , i.e. HTZ, if not the gerenric generic type D-OTHER will be used. The figures below show the basic data of airspaces as they may be published in ENR 5.5 In this example the generic type PROTECT will be used as type for the airspaces. In addition to the airspace name also a designator with may be coded which will be the same as the name. . In some AIPs in ENR 5.5 also specific types are listed, like in the example below where airspaces of type TRA are published. |
...
Coding Examples
See topic Airspace [ASE].
...