Agenda Item 4: Inter-Regional Afghanistan ATM Contingency - - PowerPoint PPT Presentation

▶
agenda item 4 inter regional afghanistan atm contingency
SMART_READER_LITE
LIVE PREVIEW

Agenda Item 4: Inter-Regional Afghanistan ATM Contingency - - PowerPoint PPT Presentation

Sep 08, 2023 364 likes •789 views

Agenda Item 4: Inter-Regional Afghanistan ATM Contingency Arrangement: Implementation Airspace Developments since AHACG/3 influencing ICAO EUR/NAT traffic distribution AFGHANISTAN CONTINGENCY SPECIAL COORDINATION MEETING 25 th August 2016

slide-1
SLIDE 1

Agenda Item 4: Inter-Regional Afghanistan ATM Contingency Arrangement: Implementation

Airspace Developments since AHACG/3 influencing ICAO EUR/NAT traffic distribution

Presented by: ICAO EUR / NAT Office - EUROCONTROL NM Prepared by: Mr. Tihomir Todorov

Head of Section Airspace Design Operations Planning Network Operations Management Division Network Manager Directorate EUROCONTROL

AFGHANISTAN CONTINGENCY SPECIAL COORDINATION MEETING

25th August 2016 Dubai, United Arab Emirates

slide-2
SLIDE 2

Current Airspace Penalization / Unavailability

slide-3
SLIDE 3
slide-4
SLIDE 4

29/08/2016

Current and Proposed Airspace Developments related to Afghanistan Contingency

slide-5
SLIDE 5

29/08/2016

Inside ICAO EUR/NAT Region

slide-6
SLIDE 6

29/08/2016

Turkey / Bulgaria ATS route re-organization 28 APR 2016

(Action and Task List - number 35)

slide-7
SLIDE 7

7

 Traffic to/from Middle East Asia - only at Turkish / Iranian interface

 Increase from 200/300 flights per day to more than 1000 flights per day.

 Approximately 90 flight/hour in critical sectors in Ankara ACC.  No further possibility for sectors split.  Not possible to re-route major traffic flows towards South.  Dualisation of several flows achieved.

Reason for Airspace Re-organization

slide-8
SLIDE 8

29/08/2016

ODERO / UDROS Area Re-organization

Bucuresti FIR Sofia FIR Istanbul FIR Ankara FIR

slide-9
SLIDE 9

29/08/2016

Bucuresti FIR - ATS Routes

RONBU ARGES LUGEB DINRO REVDA IRDUM BINBI URELA BCU BUKOV RILAS NARKA

New ATS route Changing direction Current ATS route

NARKA - RONBU eastbound for traffic to ARTAT RILAS - RONBU eastbound for traffic to ARTAT LUGEB - URELA westbound for traffic from NEGEM LUGEB - BCU westbound for traffic from NEGEM BCU - BUKOV changing direction from eastbound to bidirectional

slide-10
SLIDE 10

ODERO UDROS NEGEM 422742N 0295213E ARTAT 422150N 0293727E BULEN

New ATS route Current ATS route

KOMAN RONBU ARGES LUGEB DINRO REVDA IRDUM BINBI IBLAL RIXEN MAKOL from ETIDA from NISVA to ERDOM / DOLAP

Sofia FIR - ATS Routes

X

  • 1. FRA options from ODERO to ARGES not allowed
  • 2. NEGEM DCT LUGEB only available for traffic: DEP OK**/OM**/OO**/OT**

with ARR EETN, EFHK, EKCH, ENGM, EPWA, ESSA, EVRA, EYVI, ULLI, UMMS

slide-11
SLIDE 11

Ankara FIR / Istanbul FIR - ATS Routes

ODERO UDROS NEGEM ARTAT KABAN NINVA ALRAM BONAM DASIS AGINA REBLO ROLIN ODIRA BAG BUK SIV EZS SRT VAN CRM INB ARI SIN TBN KARDE AKCAK TEPKI CCCCC EEEEE ERZ ODALI SONAD

New ATS route Current ATS route

ARTAT - Not available for traffic via UKOV2CTA / URRVCTA / UG** / UD** / DASIS / AGINA NEGEM - Not available for traffic via DASIS ODERO - Not available for traffic via BONAM / KABAN UDROS - Not available for traffic Overfly/ARR OS** / OR** / LC** / via ALRAM

slide-12
SLIDE 12

Ankara FIR - Tehran FIR Interface No Changes

DORUK ULKEM ALRAM BONAM DASIS AGINA UP146 VAN ARI

  • 1. In accordance with LT NOTAM A2316/16 valid till 1612312359:

UG81 / UL124 - available bi-directional below FL325; UG8 / UT36 / UT888 - available above FL325.

  • 2. Afghanistan Contingency OTS within Tehran FIR option via DASIS is available eastbound below FL295.

UL223 FL285 – FL295 UR660 UL333 FL285 – FL295 UL746 / UL852 UG8 UT36 UT888 Not for LB/UK/UR/UG/UD UG81 / UL124

slide-13
SLIDE 13

Past Traffic Distribution Before changes

M1

UDROS ODERO ALRAM BONAM DASIS AGINA

02 APR 2016 SAT FPL data

More than 200 A/C 100 to 200 A/C 50 to 100 A/C 20 to 50 A/C 5 to 20 A/C Traffic Density

slide-14
SLIDE 14

Current Traffic Distribution After changes

M1

UDROS ODERO NEGEM ARTAT

06 AUG 2016 SAT FPL data

More than 200 A/C 100 to 200 A/C 50 to 100 A/C 20 to 50 A/C 5 to 20 A/C Traffic Density

ALRAM BONAM DASIS AGINA

slide-15
SLIDE 15

Current Traffic Distribution Interface Bulgaria / Turkey - All points

FPL data

ARTAT NEGEM ODERO UDROS

M1 06 AUG 2016 SAT

More than 200 A/C 100 to 200 A/C 50 to 100 A/C 20 to 50 A/C 5 to 20 A/C Traffic Density

slide-16
SLIDE 16

Current Traffic Distribution Interface Bulgaria / Turkey - ARTAT eastbound

ARTAT 278 flights

FPL data M1 06 AUG 2016 SAT

slide-17
SLIDE 17

Current Traffic Distribution Interface Bulgaria / Turkey - NEGEM westbound

NEGEM 202 flights

FPL data M1 06 AUG 2016 SAT

slide-18
SLIDE 18

Current Traffic Distribution Interface Bulgaria / Turkey - ODERO westbound

ODERO 167 flights

FPL data M1 06 AUG 2016 SAT

slide-19
SLIDE 19

Current Traffic Distribution Interface Bulgaria / Turkey - UDROS eastbound

UDROS 160 flights

FPL data M1 06 AUG 2016 SAT

slide-20
SLIDE 20

Current Traffic Distribution Turkey / Iran - All points

FPL data

ALRAM BONAM DASIS AGINA

M1 06 AUG 2016 SAT

More than 200 A/C 100 to 200 A/C 50 to 100 A/C 20 to 50 A/C 5 to 20 A/C Traffic Density

slide-21
SLIDE 21

Current Traffic Distribution Interface Turkey / Iran - ALRAM bi-directional

ALRAM 433 flights

FPL data M1 06 AUG 2016 SAT

slide-22
SLIDE 22

Current Traffic Distribution Interface Turkey / Iran - BONAM bi-directional

BONAM 195 flights

FPL data M1 06 AUG 2016 SAT

slide-23
SLIDE 23

Current Traffic Distribution Interface Turkey / Iran - DASIS bi-directional

DASIS 175 flights

FPL data M1 06 AUG 2016 SAT

slide-24
SLIDE 24

Current Traffic Distribution Interface Turkey / Iran - AGINA eastbound

AGINA 41 flights

FPL data M1 06 AUG 2016 SAT

slide-25
SLIDE 25

Current Traffic Distribution in Tehran FIR Flows via ALRAM / BONAM / DASIS / AGINA

ALRAM AGINA DASIS BONAM

UT36 - 182 flights UL223 - 226 flights M317 - 177 flights

FPL data M1 06 AUG 2016 SAT

slide-26
SLIDE 26

29/08/2016

Turkey / Georgia ATS route re-organization Proposed for Summer 2017

(Action and Task List - number 32)

slide-27
SLIDE 27

Unidirectional ATS Route System Proposal by Turkey at RDGE/24

  • 1. ROLIN - Change from bi-directional to Eastbound for

traffic from UDROS.

  • 2. SARPI - Westbound for traffic via NEGEM / ODERO and

Istanbul Area.

 

ROLIN SARPI

slide-28
SLIDE 28

29/08/2016

Other ATS route changes with possible impact on adjacent ICAO Regions

slide-29
SLIDE 29

29/08/2016

Armenia

5 FEB 2015

REBLO ADANO GOGOL

T925 N449

INDUR MAGRI

  • 1. Reported at AHACG/3 meeting
  • 2. Action and Task List - number 33
slide-30
SLIDE 30

29/08/2016

Tajikistan / Kyrgyzstan

5 MAR 2015

POMIR

B496

OU

G500 P500 B357/B496

  • 1. Reported at AHACG/3 meeting
  • 2. Action and Task List - number 30

G91

slide-31
SLIDE 31

29/08/2016

Azerbaijan / Georgia

15 SEP 2016

NETON

L133

DISKA

L131 M737 P567

ULDUS

L133 L133 NETON - DISKA bi-directional

slide-32
SLIDE 32

29/08/2016

Interface ICAO EUR/NAT - MID Regions

Turkey - Iran

Proposed Airspace Developments

slide-33
SLIDE 33

Option 1 - Proposal by Turkey (Short-term)

  • 1. ALRAM - Eastbound for traffic from Ankara FIR towards Emirates, Karachi and Delhi FIRs.
  • 2. XXXXX - New COP 12NM south of ALRAM for Eastbound traffic from Ankara FIR to Kuwait

and Bahrain FIRs.

 

ALRAM XXXXX

slide-34
SLIDE 34

Option 3 - Proposal by Turkey (Short-term)

 

  • 1. YYYYY - New COP between BONAM and DASIS for Westbound traffic.
  • 2. BONAM - Eastbound for traffic from Ankara FIR towards Emirates,

Karachi and Delhi FIRs.

  • 3. ALRAM - Eastbound for traffic from Ankara FIR towards Kuwait and

Bahrain FIRs.

ALRAM BONAM YYYYY

slide-35
SLIDE 35

Option 4 - Proposal by Iran (Short-term)

  • 1. AGINA - Bidirectional for Far East operation
  • 2. DASIS - Bidirectional for traffic via Emirates FIR to Ankara FIR and all international

departure from Tehran FIR to Ankara FIR.

  • 3. ALRAM and BONAM same as current situation (ALRAM for traffic entering Tehran

FIR towards Bahrain and Kuwait FIRs and BONAM for traffic from Bahrain and Kuwait FIRs to Ankara FIR.)

 

ALRAM BONAM AGINA DASIS

slide-36
SLIDE 36
  • 1. AGINA - Bidirectional for Far East operation
  • 2. DASIS - Bidirectional for traffic via Emirates FIR to Ankara FIR and all

international departure from Tehran FIR to Ankara FIR (Westbound traffic) and all Eastbound traffic except toward Emirates FIR.

  • 3. BONAM - Bidirectional

Eastbound: Traffic from Ankara FIR to Emirates FIR Westbound: Traffic from Kuwait and Bahrain FIRs to Ankara FIR

  • 4. ALRAM for traffic entering Tehran FIR towards Bahrain and Kuwait FIRs

Option 5 - Proposal by Iran (Mid-term)

ALRAM BONAM AGINA DASIS

  

slide-37
SLIDE 37

Option 6 - Proposal by Iran (Long-term)

  • 1. AGINA - Westbound for traffic from Far East to Ankara FIR.
  • 2. DASIS - Eastbound for traffic from Ankara FIR to Far East.
  • 3. AAAAA - New COP south of DASIS - Westbound for traffic from Emirates FIR to Ankara FIR.
  • 4. BBBBB - New COP north of BONAM - Eastbound for traffic from Ankara FIR to Emirates FIR.
  • 5. BONAM - Westbound for traffic from Kuwait and Bahrain FIRs to Ankara FIR.
  • 6. ALRAM - Eastbound for traffic from Ankara to Bahrain & Kuwait FIRs.

   

ALRAM BONAM AGINA

 

BBBBB AAAAA DASIS

slide-38
SLIDE 38

ICAO EUR/NAT Region Conclusions

slide-39
SLIDE 39

 In general considering existing airspace penalisation / unavailable areas there will be NO traffic increase inside ICAO EUR/NAT Region airspace except possible re-distribution of around 200 flights from Central to West Interface and further East.  ICAO EUR/NAT Region West Interface

  • The main traffic concentration will be on axis Tehran FIR - Ankara FIR - Sofia FIR - Bucuresti FIR and

vice-versa where traffic increase is NOT expected. Simply flights might be re-distributed from Central West (Caucasus Area) to West Interface (Ankara FIR / Tehran FIR). 4 TCPs at Ankara FIR / Tehran FIR interface are properly fed and connected to other 4 TCPs between Ankara FIR and Sofia FIR.

  • Implemented airspace changes on that interface allow proper options and sufficient ATC capacity in all

relevant ACCs to meet the expected demand. Further ATC capacity improvements might also expected considering other planned airspace changes.

  • Afghanistan Contingency OTS within Tehran FIR: ASVIB - DASIS option is available Eastbound ONLY

below FL295 and practically can be used only Westbound. Eastbound option via AGINA shall be considered to join this OTS around TBZ.  ICAO EUR/NAT Region Central West Interface

  • Reduction of flights via Caucasus Area (Yerevan FIR, Tbilisi FIR and Baku FIR) despite that all

improvements allow shorter options and balance in entry into the Region.

  • Implemented airspace changes on that interface allow proper options and sufficient ATC capacity in all

relevants ACCs to meet the expected demand.

  • Afghanistan Contingency OTS within Tehran FIR: KEDUB - MAGRI and DERBO - ULDUS options

further continuations are fully available.

Conclusions (1)

slide-40
SLIDE 40

 ICAO EUR/NAT Region Central East Interface

  • Options for flights from Tehran FIR via Ashgabat FIR remains unchanged and are fully available.
  • Sufficient ATC capacity available in all relevant ACCs to meet the expected demand.

 ICAO EUR/NAT Region East Interface

  • Options for flights on ATS route G500 via Dushanbe FIR remains unchanged and are fully available.

Utilisation depends on availability of ATS route P500 within Kabul FIR.

  • Sufficient ATC capacity available in all relevant ACCs to meet the expected demand.

 ICAO EUR/NAT Region Far East Interface

  • Options for flights via Almaty FIR remains unchanged and are fully available.
  • Sufficient ATC capacity available in all relevant ACCs to meet the expected demand.

 General conclusion is that ICAO EUR/NAT Region is ready for implementation of any Afghanistan Contingency Scenario allowing proper airspace options and sufficient ATC capacity to meet the expected demand.  Prior information and traffic re-distribution inside ICAO EUR/NAT Region shall be properly communicated in

  • rder to assure necessary internal coordination.

Conclusions (2)

slide-41
SLIDE 41

29/08/2016

QUESTIONS