duplicated and like-sounding 5lncs in icao eur/nat … meetings seminars and workshops/icard... ·...

The European Organisation for the Safety of Air Navigation

ICAO / ICARD 5LNC users forum ICAO / ICARD 5LNC users forum 2020th th -- 2121stst September 2010September 2010

Paris, France Paris, France

DUPLICATED and LIKEDUPLICATED and LIKE--SOUNDING 5LNCsSOUNDING 5LNCsIN ICAO EUR/NAT REGIONIN ICAO EUR/NAT REGION

2

Duplicated 5LNCsDuplicated 5LNCs

3

IntroductionIntroduction

Progressing with the globalisation of the ICAO Five-Letter Name Code and Route Designators (ICARD) System data base has brought up more instances of duplicate 5LNCs identified as contrary to the provisions of ICAO Annex 11, Appendix 2, paragraph 3.1. stating that “Where a significant point is required at a position not marked by the site of a radio navigation aid, the significant point shall be designated by a UNIQUE five-letter pronounceable “name-code”. Furthermore several other instances of 5LNCs included in the ICARD data base that appeared to be unused were also noted.

In this respect, the ICAO RDGE/8 (Spring 2008) requested that a specific Task Force be set up to ensure that action was taken to clear up duplicates and like-sounding 5LNCs. The Group agreed that whilst the basic principle of “the first to coordinate with ICAO gets priority to keep the code", would be exercised, efforts would be made to apply flexibility whenever possible. It was agreed that the Task Force should begin its work at RDGE/9.

At ICAO RDGE/9 (Autumn 2008) in discussing whether priorities should be assigned to the use of duplicated 5LNCs, the group agreed that whichever State had first reserved the 5LNC using ICARD system should have priority. It was also agreed that if a duplicate 5LNC had been assigned to one State via ICARD system and another State had not used the ICARD system to reserve it, the State which had reserved it using ICARD system should have priority.

Concerning the task to review and replace duplicated 5LNCs, States noted the necessity and urgency to resolve this issue. Both ICAO and EUROCONTROL reiterated their willingness to provide support to States in this matter.

ICAO agreed to provide lists of duplicated 5LNCs for further review by the States in order to determine if any of the duplications could be resolved by one of the State concerned agreeing to change. It was also agreed that all coordination to resolve duplicate 5LNCs would take place directly between the States concerned and ICAO without convening a specific Task Force, as it was previously proposed.

4

Rationalisation processRationalisation process

Based on actions taken by the RDGE, ICAO and EUROCONTROL decided to establish a 5LNCs duplication rationalisation process and to extend it to the remaining part of the ICAO EUR/NAT Region - ECAC States. The aim is to make the process coherent and fully co-ordinated for the entire ICAO European region by establishing common criteria for replacement of duplicated 5LNCs and monitoring bodies - ICAO and RNDSG secretariats.

Following the verbal presentation made at RNDSG/66 (FEB 2009), the secretariat initiated, by correspondence, actions to eliminate current duplication of 5LNCs. The initial list of all duplicated 5LNCs in ICAO EUR/NAT Region was created and circulated on 21st November 2008 to the States concerned for further actions.

The ICARD 5LNC Data Manager took proper actions as from 1 May 2009. ICARD planners are requested to review these lists and inform the ICARD 5LNC Data Manager before this date if the action required is not to be taken.

The next step to resolving the duplicated 5LNCs would be to initiate co-ordination with other ICAO Regions to reach the final goal - worldwide uniqueness of all five-letter name-codes.

5

Common criteria for replacement of duplicated 5LNCsCommon criteria for replacement of duplicated 5LNCs

First criteria - ICARD / AIP existence comparison:

in ICARD - if two or more 5LNCs are in ICARD - go to Second criteria;

in ICARD / not in ICARD - change should be proposed to the State/s concerned with 5LNCs not in ICARD.

Second criteria - ICARD status comparison:

reservation (decision date) - if there are two or more 5LNCs reserved, the FIRST reserved has priority - change should be proposed to the State/s concerned following verification of the real use of the reserved 5LNC;

reservation / no reservation - change should be proposed to the State/s concerned with no ICARD allocation;

no reservation - if there are two or more not reserved 5LNCs - go to Third criteria.

Third criteria - 5LNCs usage comparison:The following characteristics will receive priority:

FIR boundary point (due to the involvement of more than one State);

SID/STAR (more difficult to change procedures than ATS route);

major en-route crossovers;

upper airspace;

lower airspace.

Note: If 5LNCs have the same third criteria, the final judgement will be made by ICAO and/or EUROCONTROL.

6

List of duplicated 5LNCs in ICARDList of duplicated 5LNCs in ICARD

ICARDlatitude

ICARDlongitude

NAME CODE ITU CODE ICARD

Status/reservation Current Status Action required

584100N 0794100E AGOTI RUS No record. IN AIP Russia and CIS. Used on ATS routes A819, R211.

Deletion to be proposed by ICAO to RUS due to Italian ICARD reservation.

410805N 0143847E AGOTI I Reserved - 03.06.99. IN AIP Italy. Used as STAR LIRN.

4200N 01500W BANAL POR No record. IN AIP Portugal. Decision pending until final check-up.

565954N 0365754E BANAL RUS No record. IN AIP Russia and CIS. Used on ATS route R815.

214221.0S 0524607.2W BANAL B No record. To be checked by ICAO. ICARD Comment: Uncoordinated (from AIP).

4210N 00202E BERGA E No record. IN AIP Spain. Used on ATS route B31 within Barcelona TMA / STAR LERS.

Will be changed by Italy - 9 APR 2009.

4539N 00937E BERGA I No record. IN AIP Italy. Used as intermediate point in SID LIMC/E/L.

RNDSG secretariat will be responsible

5700N 00642E DANKO DNK, NOR No record. IN AIPs Denmark and Norway. FIR boundary point.

NO DUPLICATION.

610912N 0455830E DANKO RUS No record. NOT in AIP Russia and CIS. ICAO to delete RUS from ICARD and reserve it for DNK/NOR in ICARD.

463000N 0015039W LAGOR F No record. IN AIP France. Decision to be taken by ICAO / EUROCONTROL.

572900N 1235700E LAGOR RUS No record. IN AIP Russia and CIS. Used on ATS route G495.

Blue - action to be taken at the RDGE meeting;

Grey - decision pending due to need for further verifications;

Red - decision has been taken and State highlighted to take action;

Yellow - no actual duplication - ICARD to be cleaned up; and

Orange - more than 2 or 3 criteria are the same and a decision needs to be taken by EUROCONTROL/ICAO.

7

List of duplicated 5LNCs used in List of duplicated 5LNCs used in AIPsAIPs but not in ICARDbut not in ICARD

Blue - action to be taken at the RDGE meeting;

Grey - decision pending due to need for further verifications;

Red - decision has been taken and State highlighted to take action;

Yellow - no actual duplication - ICARD to be cleaned up; and

Orange - more than 2 or 3 criteria are the same and a decision needs to be taken by EUROCONTROL/ICAO.

ICARDlatitude

ICARDlongitude

NAME CODE ITU CODE ICARD

Status/reservation Current Status Action required

NOT IN ICARD CARBO G No record. IN AIP UK. Will be deleted by the UK - 12 MAR 2009

473403.55N 1111417.29W CARBO USA Reserved - 30.04.87. To be checked by ICAO. Further decision pending until final check-up.

3615N 00130W CARBO ALG, E No record. IN AIP Spain. FIR boundary point.

NOT IN ICARD FRANK D IN AIP Germany. To be changed by Germany - NOT in ICARD - decision by EUROCONTROL.

5143N 00041W FRANK G No record. IN AIP UK.

303257.87N 0900000.09W FRANK USA Reserved - 28.02.05 To be checked by ICAO.

113109.3N 0773528.6W FRANK PNR No record. To be checked by ICAO. ICARD Comment: Uncoordinated (from AIP)

Further decision pending until final check-up.

075737.8S 0400318.6W FRANK B No record. To be checked by ICAO.

8

LikeLike--sounding 5LNCssounding 5LNCs

9

Like sounding 5LNCs ambiguity

LEMD - LKPR

130NM

When on airway UN871 and flying from the west to the east, Swiss ACC often provides clearance direct to VEBEG (Swiss/Vienna boundary). Some 130NM further away, waypoint MEBEK (FIR Munich) is on the same airway. We have received reports from flight crews that due to phonetic similarity of these two waypoints there is a possibility of confusion when receiving clearance from ATC. Such confusion may pose a threat to safe operations and therefore we would like to bring this issue into your attention.

CSA Director Deputy Flight Safety

Annex 11, Appendix 23.3. The name-code designator shall be easily recognizablein voice communications and shall be free of ambiguity withthose used for other significant points in the same general area.

VEBEG will be replaced by GAMSA as from 21 OCT 2010

10

Initial idea for likeInitial idea for like--sounding algorithms avoiding existing ambiguitysounding algorithms avoiding existing ambiguity

4 (four) letters should not match if are on the same position.Example: “BAKOV” should not be used if other code is “BUKOV”.

The last 3 letters should not match.Examples (“n” - consonant and “y” - vowel):if in order of “nyn” - “NAKOV” should not be used if other code is “BUKOV”;if in order of “yny” - “ALAMI” should not be used if other code is “OKAMI”.

The 1st letter, 3rd letter and 5th letter should not match.Examples:if in order of “nyn” - “BAKUV” should not be used if other code is “BUKOV”;if in order of “yny” - “ALAMI” should not be used if other code is “AGATI”.

The 2nd letter, 3rd letter and 4th letter should not match.Examples:if in order of “nyn” - “ABATI” should not be used if other code is “OBATO”if in order of “yny” - “VEBEG” should not be used if other code is “MEBEK”.

The already approved (see RNDSG/66, WP/19 and RDGE/10, WP/4) “Common criteria for replacement of duplicated 5LNCs” will be applied when proposing the withdrawals.

Initial radius of proximity check could be established as 500NM.

11

Initial list of possible likeInitial list of possible like--sounding 5LNCs ambiguity in sounding 5LNCs ambiguity in South East EuropeSouth East Europe

Presented at SEERM/10 (27th - 29th January 2010).

All 5LNCs (except one) contains same 4 (four) letters on the same place.

02/11/1999ALB/MKDDOBAR

DABAR - double 5LNC with CLN/IND.To be further considered.310NM

19/08/2002HRVDABAR

18/02/2005ROUTALIK

TALIK - double 5LNC with RUS. To be further considered.270NM

15/02/2000BGRBALIK

02/10/2009BGRLUKOV

To be further considered.293NM

-UKR/ROUBUKOV

-UKR/ROUBUKOV

Withdrawal of one of the points to be considered.122NM

11/10/2000ROUBAKOV

07/02/2001HRV/SVNBUSET

BUSER to be withdrawn by ITA.88NM

-ITABUSER

15/01/2004BIHBOSNA

BASNA is located on planned for re-designation ATS route W85. To be further considered.220NM

06/03/2001ROUBASNA

23/12/2004HUN/SVKBADOV

BADOR could be considered for withdrawal by HUN/ROU.283NM

-HUN/ROUBADOR

18/09/2000BIHBARIT

BABIT - double 5LNC with USA. Withdrawal of one of the points to be considered.167NM

-HUN/SRBBABIT

12/01/2009ROUBABUT


-HUN/SRBBABIT

06/04/2006ROUALESU

ALESU could be considered for withdrawal by ROU. 379NM

27/04/2005ALB/MNEALELU

Comment / ProposalDistance between 5LNCs

ICARD Decision Date

States5LNC

02/11/1999ALB/MKDDOBAR

DABAR - double 5LNC with CLN/IND.To be further considered.310NM

19/08/2002HRVDABAR

18/02/2005ROUTALIK

TALIK - double 5LNC with RUS. To be further considered.270NM

15/02/2000BGRBALIK

02/10/2009BGRLUKOV


-UKR/ROUBUKOV

-UKR/ROUBUKOV

Withdrawal of one of the points to be considered.122NM

11/10/2000ROUBAKOV

07/02/2001HRV/SVNBUSET

BUSER to be withdrawn by ITA.88NM

-ITABUSER

15/01/2004BIHBOSNA

BASNA is located on planned for re-designation ATS route W85. To be further considered.220NM

06/03/2001ROUBASNA

23/12/2004HUN/SVKBADOV

BADOR could be considered for withdrawal by HUN/ROU.283NM

-HUN/ROUBADOR

18/09/2000BIHBARIT


-HUN/SRBBABIT

12/01/2009ROUBABUT


-HUN/SRBBABIT

06/04/2006ROUALESU

ALESU could be considered for withdrawal by ROU. 379NM

27/04/2005ALB/MNEALELU

Comment / ProposalDistance between 5LNCs

ICARD Decision Date

States5LNC

12-SRB/MKDXAXAN

XAXAN used and published but not in ICARD. To be further considered.201NM

31/08/2001BIH/HRVXAPAN

24/02/2005AUTVENEN


02/07/2008ITA/AUTVEKEN

22/04/2009BIHVEBAR

VEBAR could be considered for withdrawal by BIH.137NM

13/09/2001HRV/HUNVEBAL

-BGR/TURVADEN

VADEN - double 5LNC with USA. To be further considered.232NM

22/04/2003SRBVAGEN

-HRV/MNETIMUS

TIMUS exists in ICARD but reserved for RUS.TIMUS to be withdrawn by HRV/MNE.261NM

02/10/2009BGR/ROUTIMUR

-HRV/BIHSIRMI

Both 5LNCs are on same ATS route. SIRMA to be withdrawn by HRV.66NM

-HRVSIRMA

15/02/2000BGRSUMEN

SUMEN will be withdrawn by BGR on 6 MAY 2010.141NM

02/10/2009BGRRUMEN

-BGR/GRCRODOP


08/01/2004MNE/ALBRODON

27/03/2006BGRRESLA

RESLA could be considered for withdrawal by BGR.207NM

20/07/1999ROUREBLA

17/08/2001MNEMODRA

MOBRA could be considered for withdrawal by ROU.283NM

10/12/2003ROUMOBRA

-SRB/ROUMAVIT


11/10/2000HUNMAVIR

12/07/2000BGRMAVAD


-ALB/MKDMAVAR

18/02/2004TURKUMAN

KUMAN - double 5LNC with MEX. To be further considered.364NM

-ROU/BULKOMAN

-GRCKOROS

KOROS could be considered for withdrawal by GRC.20NM

15/05/2001GRCKERES

-UKRIZMAL

IZMAL exists in ICARD and JEPPESEN. To be further considered.5NM

-ROU/UKRIRMAL

-SRB/MKDXAXAN



24/02/2005AUTVENEN



22/04/2009BIHVEBAR



-BGR/TURVADEN


22/04/2003SRBVAGEN

-HRV/MNETIMUS



-HRV/BIHSIRMI


-HRVSIRMA

15/02/2000BGRSUMEN


02/10/2009BGRRUMEN

-BGR/GRCRODOP



27/03/2006BGRRESLA


20/07/1999ROUREBLA

17/08/2001MNEMODRA


10/12/2003ROUMOBRA

-SRB/ROUMAVIT


11/10/2000HUNMAVIR

12/07/2000BGRMAVAD


-ALB/MKDMAVAR

18/02/2004TURKUMAN


-ROU/BULKOMAN

-GRCKOROS


15/05/2001GRCKERES

-UKRIZMAL


-ROU/UKRIRMAL

-SRB/MKDXAXAN



24/02/2005AUTVENEN



22/04/2009BIHVEBAR



-BGR/TURVADEN


22/04/2003SRBVAGEN

-HRV/MNETIMUS



-HRV/BIHSIRMI


-HRVSIRMA

15/02/2000BGRSUMEN


02/10/2009BGRRUMEN

-BGR/GRCRODOP



27/03/2006BGRRESLA


20/07/1999ROUREBLA

17/08/2001MNEMODRA


10/12/2003ROUMOBRA

-SRB/ROUMAVIT


11/10/2000HUNMAVIR

12/07/2000BGRMAVAD


-ALB/MKDMAVAR

18/02/2004TUR

-SRB/MKDXAXAN



24/02/2005AUTVENEN



22/04/2009BIHVEBAR



-BGR/TURVADEN


22/04/2003SRBVAGEN

-HRV/MNETIMUS



-HRV/BIHSIRMI


-HRVSIRMA

15/02/2000BGRSUMEN


02/10/2009BGRRUMEN

-BGR/GRCRODOP



27/03/2006BGRRESLA


20/07/1999ROUREBLA

17/08/2001MNEMODRA


10/12/2003ROUMOBRA

-SRB/ROUMAVIT


11/10/2000HUNMAVIR

12/07/2000BGRMAVAD


-ALB/MKDMAVAR

18/02/2004TURKUMAN


-ROU/BULKOMAN

-GRCKOROS


15/05/2001GRCKERES

-UKRIZMAL


-ROU/UKRIRMAL

-SRB/MKDXAXAN



24/02/2005AUTVENEN



22/04/2009BIHVEBAR



-BGR/TURVADEN


22/04/2003SRBVAGEN

-HRV/MNETIMUS



-HRV/BIHSIRMI


-HRVSIRMA

15/02/2000BGRSUMEN


02/10/2009BGRRUMEN

KUMAN


-ROU/BULKOMAN

-GRCKOROS


15/05/2001GRCKERES

-UKRIZMAL


-ROU/UKRIRMAL

-SRB/MKDXAXAN



24/02/2005AUTVENEN



22/04/2009BIHVEBAR



-BGR/TURVADEN


22/04/2003SRBVAGEN

-HRV/MNETIMUS



-HRV/BIHSIRMI


-HRVSIRMA

15/02/2000BGRSUMEN


02/10/2009BGRRUMEN

-BGR/GRCRODOP



27/03/2006BGRRESLA


20/07/1999ROUREBLA

17/08/2001MNEMODRA


10/12/2003ROUMOBRA

-SRB/ROUMAVIT


11/10/2000HUNMAVIR

12/07/2000BGRMAVAD


-ALB/MKDMAVAR

18/02/2004TURKUMAN


-ROU/BULKOMAN

-GRCKOROS


15/05/2001GRCKERES

-UKRIZMAL


-ROU/UKRIRMAL

13

BGR

RUMEN

SUMEN

141NM

SUMEN was withdrawn on 6 MAY 2010

14

HRV / BIH

SIRMI

SIRMA

66NM

SIRMA to be withdrawn by HRV

15

HRV / SVN / ITA

BUSET

BUSER

88NM

BUSER to be withdrawn by ITA

16

ASPIS

ASTIS

347.8NM

ASPIS could be replaced by CYP

Reported by ATC Safety Manager of British Airways

GRC / CYP

17

ABOKA 460633.89N 0245807.14E L/UL620ABORA 443307.93N 0262026.96E STAR LRBS

AMODA 443154.30N 0263004.35E STAR LRBSAMODI 461134.96N 0213011.65E IAC LRAR

BARID 460831.75N 0210046.84E IAC LRARBARIV 465028.43N 0232710.09E STAR LRCL

ARBAD 43592400N 033283600E UL99ARNAD 45210000N 036384800E T145 / UT145

BABIB 46104300N 029030500E UM406BABIN 44253000N 031000000E M861 / UM861BABIS 49595400N 026212900E UN191 / UR22

Other examples of likeOther examples of like--sounding 5LNCssounding 5LNCsRomania

Turkey

Ukraine

18

Other reported likeOther reported like--sounding issues in Europesounding issues in Europe

19

Like sounding NAVAID and 5LNC

KOPOL

GRC

KPL

19NM

20

RODOP

RDS

363.3NM

Like sounding NAVAID and 5LNC

BGR / GRC

Reported in SKYBRARY

RDS usually pronounced by ATCOs as RODOS

21

Oceanic Errors Safety Bulletin (OESB) - OESB-01-09 (June 2009)Gross Navigation Errors (GNEs)

9. Crews must be alert for similar soundingNamed oceanic boundary waypoints(e.g. PITAX versus BERUX)when receiving the ATC clearance.

Oceanic issues with likeOceanic issues with like--sounding 5LNCssounding 5LNCs

PITAX

BERUX

Shanwick Oceanic FIR

22

AOsAOs likelike--sounding informationsounding information

Despite that the simplification process of like-sounding 5LNCs is under study information for the AOs regarding possible ambiguity is presented via SKYBRARY website - http://www.skybrary.aero/ipbforums/.

SKYBRARY is owned and managed by EUROCONTROL with the objective to facilitate wide dissemination and exchange of aviation safety information to and between aviation professionals in order to raise their awareness of aviation safety related issues.

http://www.skybrary.aero/ipbforums/

23

ENDEND

duplicated and like-sounding 5lncs in icao eur/nat … meetings seminars and workshops/icard... ·...

Documents