Local Single Sky ImPlementation LSSIP 2017 - TURKEY · 2019-02-18 · Introduction The Local Single...

Level 1 - Implementation Overview

Local Single Sky ImPlementation LSSIP 2017 - TURKEY

EUROCONTROL

LSSIP Year 2017 Turkey Released Issue

Document Title LSSIP Year 2017 for Turkey

Infocentre Reference 18/02/26/43

Date of Edition 04/06/18

LSSIP Focal Point Cihan Sahin ‐ [email protected]

LSSIP Contact Person Predrag Vranjkovic ‐[email protected]

Status Released

Intended for Agency Stakeholders

Available in http://www.eurocontrol.int/articles/lssip

Reference Documents

LSSIP Documents http://www.eurocontrol.int/articles/lssip

LSSIP Guidance Material http://www.eurocontrol.int/articles/lssip

Master Plan Level 3 – Plan Edition 2017

http://www.eurocontrol.int/articles/european‐atm‐master‐plan‐level‐3‐implementation‐plan

Master Plan Level 3 – Report Year 2016

http://www.eurocontrol.int/articles/european‐atm‐master‐plan‐level‐3‐implementation‐report

European ATM Portal https://www.eatmportal.eu and http://www.atmmasterplan.eu/

STATFOR Forecasts http://www.eurocontrol.int/statfor

Acronyms and abbreviations http://www.eurocontrol.int/articles/glossaries

APPROVAL SHEET

The following authorities have approved all parts of the LSSIP Year 2017 document and their signature

confirms the correctness of the reported information and reflects their commitment to implement the actions

laid down in the European ATM Master Plan Level 3 Implementation Plan - Edition 2017 (also known as the

ESSIP Plan).

Stakeholder/ Name Position Signature

Organisation

DIRECTORATE

GENERAL OF CIVIL

AVIATION (DGCA)

GENERAL

DIRECTORATE OF

STATE AIRPORTS

AUTHORITY

TURKISH AIR FORCE

LSSIP Year 2017 Turkey

Bahri KESICI

Funda OCAK

Brigadier General

Yusuf ERGE

Acting Director

General

General Director

Director of Air

Defence and

Com.Cont.

Released Issue

LSSIP Year 2017 Turkey Released Issue

CONTENTS

1. National ATM Environment ............................................................. 6 Geographical Scope .............................................................................................6 1.1. National Stakeholders .........................................................................................7 1.2.

2. Traffic and Capacity ....................................................................... 15 Evolution of traffic in Turkey ............................................................................ 15 2.1. ANKARA ACC ‐ Traffic and en‐route ATFM delays 2013‐2022 ......................... 16 2.2. Summer 2017 performance ............................................................................. 16 2.3. Planning Period 2018‐2022 .............................................................................. 17 2.4.

3. Master Plan Level 3 Implementation Report conclusions ............. 19

4. Implementation Projects ............................................................... 20 National projects .............................................................................................. 20 4.1. Regional projects .............................................................................................. 21 4.2.

5. Cooperation activities .................................................................... 22 FAB Co‐ordination ............................................................................................ 22 5.1. Regional cooperation ....................................................................................... 22 5.2.

6. Implementation Objectives Progress ............................................. 24 State View......................................................................................................... 24 6.1. Detailed Objectives Implementation progress ................................................ 30 6.2.

Annexes

LSSIP Year 2017 Turkey 1 Released Issue

24; 49%

5; 10%

3; 6%

9; 19%

6; 12%

2; 4% Completed

Ongoing

Planned

Late

No Plan

Not Applicable

Missing Data

Undefined

Executive Summary

National ATM Context

Civil aviation in Turkey is the responsibility of the Ministry of Transport, Maritime Affairs and Communications which represents Turkey at the EUROCONTROL Commission. The Directorate General of Civil Aviation (DGCA) is the Turkish Regulatory Authority which represents Turkey at the EUROCONTROL Provisional Council and DHMI is the unique civil ANSP in Turkey.

Devlet Hava Meydanlari Isletmesi (DHMI) Air Navigation Department of Directorate general of State Airports of Turkey (www.dhmi.gov.tr) is the unique provider of Civil Air Navigation Services for Turkey. DHMI is a 100 % State‐owned Governmental department.

According to SHY‐ Gözetim which was enacted in parallel ESARR 1, DGCA Air Navigation Department undertakes the NSA responsibilities.

Traffic and Capacity

Traffic in Turkey increased by 7.5% during Summer 2017 (May to October), when compared to the same period during 2016.

Implementation Objectives Overview

Progress distribution for applicable Implementation Objectives

All phases of the objectives (ATC02.9, ATC12.1 and ATC17) have been completed.

The objectives on direct routing and free route airspace will be finalized for 2019‐2020 period.

All actions of the objectives (ATC15.2, COM12, INFO07.1) will be conducted on time.

The objectives (AOP10, AOP 12 and AOP 13) are planned to complete in short term for Istanbul New Airport.

Progress per SESAR Phase

The figure below shows the progress made so far in the implementation of the pre‐SESAR and PCP elements. The percentage is calculated as an average of the relevant objectives as shown in Chapter 6.1.2 ‐ PCP objectives are marked as such, the rest except AOP14, ATC02.9, ATC18 and NAV12 are considered pre‐SESAR. The four aforementioned objectives are neither pre‐SESAR nor PCP and will be part of an overall future indicator covering the SESAR 1 phase.

Note that two objectives – AOM19.1 and FCM05 – are considered as both part of the pre‐SESAR and PCP so their progress contributes to the percentage of both phases.


The objectives declared ‘Achieved’ in previous editions (up to, and including, ESSIP Edition 2011‐2015) are also taken into account for as long as they were linked to the Level 2 of the ATM Master Plan and implemented by the State.

Pre‐SESAR Implementation

2010 2019

84%

PCP Implementation

2015 2023

9%

Progress per SESAR Key Feature and Phase

The figure below shows the progress made so far, per SESAR Key Feature, in the implementation of the pre‐SESAR and the PCP elements. The percentages are calculated as an average, per Key Feature, of the same objectives as in the previous paragraph.

ICAO ASBUs Progress Implementation

The figure below shows the progress made so far in the implementation of the ICAO ASBUs both for Block 0 and Block 1. The percentage is calculated as an average of the relevant Objectives contributing to each of the relevant ASBUs; this is explained in Chapter 6.1.3.

Block 0 2010 2018

85%

Block 1 2015 2022

15%

43%

0%

Pre‐SESAR

89%

10%

94%

15%

96%

11%

Pre‐SESAR

Pre‐SESAR

Pre‐SESAR

PCP

PCP

PCP

PCP

Optimised ATM Network Services

Advanced Air Traffic Services High Performing

Airport Operations

Enabling Aviation Infrastructure


ATM Deployment Outlook

● State objec ves

Deployed in 2016‐2017: ‐ RNAV 1 for TMA Operations [NAV03.1] 100% progress ‐ Runway excursions [SAF11] 100% progress

‐ ETFMS [FCM01] 89% progress ‐ eTOD [INF07] 81% progress ‐ APV Procedures [NAV10] 55% progress

‐ TCAS II v7.1 [ATC16] 87% progress ‐ AMAN to en‐route [ATC15.1] 78% progress ‐ Direct Routing [AOM21.1] 10% progress

‐ Voice over IP [COM11] 53% progress ‐ Free Route Airspace [AOM21.2] 10% progress

‐ Extended Flight Plan [FCM08] 0% progress ‐ NewPENS [COM12] 0% progress

● Airport objec ves ‐ LTAC ‐ Ankara Esenboga Airport

Deployed in 2016‐2017:

● Airport objec ves ‐ LTAI ‐ Antalya Airport

Deployed in 2016‐2017: ‐ CCOs [ENV03] 100% progress

‐ CDOs [ENV01] 47% progress ‐ Airport CDM [AOP05] 10% progress

By 12/2018 By 12/2019 By 12/2020 2021+

By 12/2018 By 12/2019 By 12/2020 2021+

By 12/2018 By 12/2019 By 12/2020 2021+


● Airport objec ves ‐ LTBA ‐ Istanbul Atatürk Airport

Deployed in 2016‐2017: ‐ AMAN [ATC07.1] 100% progress

‐ Airport CDM [AOP05] 93% progress ‐ CDOs [ENV01] 47% progress ‐ Airport Safety Nets [AOP12] 18% progress ‐ Surface Movement Planning & Routing [AOP13] 12% progress

By 12/2018 By 12/2019 By 12/2020 2021+


Introduction

The Local Single Sky ImPlementation (LSSIP) documents, as an integral part of the Master Plan (MP) Level 3 (L3) / LSSIP mechanism, constitute a short/medium term implementation plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the MP Level 3 and to improve the performance of their national ATM System. This LSSIP document describes the situation in the State at the end of December 2017, together with plans for the next years.

Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organisations, the organisational structure of the main ATM players ‐ civil and military ‐ and their responsibilities under the national legislation. In addition, an overview of the Airspace Organisation and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided;

Chapter 2 provides a comprehensive picture of the situation of Air Traffic, Capacity and ATFM Delay per each ACC in the State. It shows the evolution of Air Traffic and Delay in the last five years and the forecast for the next five years. It gives also the achieved performance in terms of delay during the summer season period and the planned projects assumed to offer the required capacity which will match the foreseen traffic increase and keep the delay at the agreed performance level;

Chapter 3 provides a set of conclusions extracted from the MP L3 Implementation Report 2016 which are relevant to the State/stakeholders concerned. The State reports how they have handled those conclusions and the actions taken during the year to address the concerns expressed by those conclusions;

Chapter 4 provides the main Implementation Projects (at national, FAB and regional level) which contribute directly to the implementation of the MP Operational Improvements and/or Enablers and Implementation Objectives. Level 1 document covers high level list of the projects showing the applicable links. All other details like description, timescale, progress made and expected contribution to the ATM Key Performance Areas provided by the State per each project are available in Level 2 document;

Chapter 5 deals with other cooperation activities beyond Implementation Projects. It provides an overview of the FAB cooperation and also all other regional initiatives which are out of the FAB scope. The content of this chapter generally is developed and agreed in close cooperation between the States concerned;

Chapter 6 contains aggregated information at State level covering the overall level of implementation, implementation per SESAR Key Feature and implementation of ICAO ASBUs. In addition the high‐level information on progress and plans of each Implementation Objective is presented. The information for each Implementation Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section.

Level 1 document is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of Implementation Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the European ATM Master Plan L3 Implementation Plan Edition 2017. In addition it covers detailed description of the Implementation Projects for the State as extracted from the LSSIP Data Base.

The information contained in Chapter 6 is deemed sufficient to satisfy State reporting requirements towards ICAO in relation to ASBU (Aviation System Block Upgrades) monitoring.


1. National ATM Environment

Geographical Scope 1.1.

International Membership

Turkey is a Member of the following international organisations in the field of ATM:

Organisation Since

ECAC 1955

EUROCONTROL 1989

European Union NA

EASA NA

ICAO 1945

NATO 1952

ITU 1866

Geographical description of the FIR(s)

The geographical scope of this document addresses the Ankara and Istanbul FIRs. There is no separation between the lower and the upper airspace in the Turkish FIRs.


Airspace Classification and Organisation

Turkey is evaluating the implementation of ICAO classification for both present and future systems. Airspace reorganisation as a result of studies is planned. It is not yet possible to predict when this will be completed.

National Stakeholders 1.2.

The main National Stakeholders involved within ATM in Turkey are the following:

- The Ministry of Transport, Maritime Affairs and Communication;

- The Directorate General of Civil Aviation – DGCA;

- The Devlet Hava Meydanlari Isletmesi (Directorate General of State Airports (Turkey) – DHMI;

- The Turkish Military Authority; and

- The Turkish State Meteorological Service.

Their activities are detailed in the following subchapters.

Civil aviation in Turkey is the responsibility of the Ministry of Transport, Maritime Affairs and Communication which represents Turkey at the EUROCONTROL Commission. The Directorate General of Civil Aviation (DGCA) is the Turkish Regulatory Authority which represents Turkey at the EUROCONTROL Provisional Council, and DHMI is the unique civil ANSP in Turkey.

The Military Authority permit some military aerodromes to be used by civil aviation in order to improve air transport links within Turkey.

Civil ATM incidents are investigated by the “Investigation and Assessment Commission” which reports incidents and investigation findings to the DGCA. The commission is formed from experts with sufficient qualifications. Where requested by the DHMI and/or if DGCA consider it necessary, experts from DGCA will also join the commission in accordance with SHY 65‐02. For civil or civil/military ATM related incidents occurring within the Military Terminal Area and military joint user airports, the DGCA will receive all documentation/reports concerning the incident from the military authorities and a joint investigation will be carried out.


The Advisory and Steering Committee holds regular (quarterly) meetings with the participation of aviation organisations as coordinated by the DGCA to classify incidents, prepare statistical data, evaluate reports of the “Investigation and Assessment Commission” and to impose actions and/or give recommendations to the aviation community to prevent the re‐occurrence of similar incidents. The committee has the authority to include any aviation related issue on its agenda. Members of this Committee are comprised from the following organisations as appropriate:

- DGCA (www.shgm.gov.tr)

- DHMI (www.dhmi.gov.tr)

- Military Authority

- School of Civil Aviation (Aviation Experts)

- Turkish Airline Pilots’ Association (TALPA)

- Air Traffic Controllers Association of Turkey

- Other related stakeholders.

Their activities are detailed in the following subchapters and their relationships are shown in the diagram below.

Civil Regulator(s)

General Information

Civil Aviation in Turkey is the responsibility of the Ministry of Transport, Maritime Affairs and Communication. The different national entities having regulatory responsibilities in ATM are summarised in the table overleaf. The DGCA is further detailed in the following sections.

Activity in ATM: Organisation responsible Legal Basis

Rule‐making DGCA The Law No: 2920 and 5431

Safety Oversight DGCA The Law No: 2920 and 5431

Enforcement actions in case of non‐compliance with safety regulatory requirements

DGCA The Law No: 2920 and 5431

Airspace DGCA The Law No: 2920 and 5431

Economic Ministry of Transport, maritime Affairs and Communication

Environment DGCA and Ministry of Environment and Urbanism

Security DGCA The Law No: 2920 and 5431

Accident investigation Investigation and Assessment Commission


DGCA

The Regulator is the Directorate General of Civil Aviation (DGCA). The DGCA is a body within the Ministry of Transport, Maritime Affairs and Communication with its own operating budget. The CAA responsibility is processed by DGCA.

The DGCA is responsible for:

- Licensing of Aircrew and Engineers

- Licensing of Air Traffic Controllers

- Licensing of ATSEPs

- Certificate of Airworthiness (CoA) of aircraft

- Approval of all airborne electronic equipment

- Oversight and certification of airports

- Investigation of Incidents by means of participation in Investigation and Assessment Commission and holding Advisory and Steering Committee Meetings.

- Approval and generation of all ATM rules/regulations (including ESARRs) in coordination with stakeholders (DHMI, Turkish Air Force General Staff and other bodies as appropriate).

Economic regulation is carried out by the Turkish Ministry of Transport, Maritime Affairs and Communication.

Annual Report published: N

www.shgm.gov.tr

Organisation chart is shown in Annex B of this document.

ANSP‐DHMI

Services provided

Devlet Hava Meydanları Isletmesi (DHMI) Air Navigation Department of Directorate General of State Airports of Turkey (www.dhmi.gov.tr) is the unique Provider of Civil Air Navigation Services for Turkey. DHMI is a 100 % State‐owned Governmental department. DHMI provides all the Air Traffic Services within civil airspace (Controlled Airspace, TMA and CTRs).

DHMI cooperates very closely with the DGCA, particularly on safety matters such as the implementation of the ESARRs.


Name of the ANSP: Devlet Hava Meydanları Isletmesi (DHMI) Air Navigation Department of Directorate General of State Airports of Turkey

Governance: Governmental department Ownership: 100% State owned

Services provided Y/N Comment

ATC en‐route Y

ATC approach Y

ATC Aerodrome(s) Y

AIS Y

CNS Y

MET N Turkish State Meteorological Service

ATCO training Y

Others Y Airport management

Additional information:

Provision of services in other State(s):

N

Annual Report published: Y http://www.dhmi.gov.tr/dosyalar/annualreport/2016/DHMI%20Annual%20Report%202016.pdf

www.dhmi.gov.tr

Organisation chart is shown in Annex B.

ATC systems in use

Main ANSP part of any technology alliance1 N

FDPS

Specify the manufacturer of the ATC system currently in use: SELEX

Upgrade2 of the ATC system is performed or planned? 2015

Replacement of the ATC system by the new one is planned? -

ATC Unit Ankara ACC

SDPS

Specify the manufacturer of the ATC system currently in use: SELEX

Upgrade of the ATC system is performed or planned? 2015

Replacement of the ATC system by the new one is planned? -

ATC Unit Ankara ACC

1Technology alliance is an alliance with another service provider for joint procurement of technology from a particular supplier (e.g. COOPANS alliance) 2 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))


ATC Units

En‐route air navigation services throughout Turkish Airspace from one Area Control Center located in Ankara There are 27 TMAs and 12 MTMAs in Turkish Airspace. Description of the ATC units providing the services and their areas of responsibility; Size of the ATC unit (maximum number of sectors); Service provided (en‐route or TMA – no more ref to TWR).

The ATC units in the Turkish airspace, which are of concern to this LSSIP are the following:

The ATC units in the Turkish airspace, which are of concern to this LSSIP are the following:

ATC Unit Number of sectors Associated FIR(s) Remarks

En‐route TMA

Ankara ACC 22 2 Ankara

Istanbul

Istanbul / Yeşilköy APP

7 Istanbul

Izmir / Menderes APP

4 Istanbul

Antalya APP 8 Istanbul

Dalaman APP 3 İstanbul

Airports

General information Turkey has 58 airports used by GAT. These range from busy international airports to small regional airports with perhaps ten or less movements daily.

Air navigation service is provided for all airports by DHMI except Eskişehir Anadolu, İzmir Efes, Samsun Ondokuz Mayıs and İstanbul Hezarfen Airports.


Airport(s) covered by the LSSIP

The airports covered by this LSSIP document are as follows:

- Istanbul Atatürk airport - Antalya Airport, and - Ankara Esenboga airport

The EUROCONTROL Public Airport Corner also provides information for the following airport(s): https://ext.eurocontrol.int/airport_corner_public/LTBA

https://ext.eurocontrol.int/airport_corner_public/LTAC

https://ext.eurocontrol.int/airport_corner_public/LTAI

Military Authorities

The military authority also plays a major role in managing the Turkish Airspace especially with regard to FUA. Military ATC is entirely separated from Civil ATC, although very good civil/military co‐ordination is maintained. Co‐ordination between the military authority and the DHMI is ensured through a Civil‐Military Co‐ordination Group. Some (11) airports/airfields of military origin are jointly used by military and civil aviation. For the eight (8) airports of them, all aircraft are under military ATC control.

Currently, Turkish Military Authority and DHMI have their own alternative FUA concept which is considered more suitable for the local geo‐political situation. In order to increase the capacity of Turkish airspace, with implementation of the SMART system, DHMI and the Military Authority are planning to implement EUROCONTROL Flexible Use of Airspace (FUA) concept to do that necessary legislation has been published at Official Gazette dated 18 April 2014. The studies are going on to establish infrastructure and units. The military regulatory, service provision and user role within ATM is detailed below.

Regulatory role

Regulatory framework and rule‐making

OAT GAT

OAT and provision of service for OAT governed by national legal provisions?

Y Provision of service for GAT by the Military governed by national legal provisions?

y

Level of such legal provision: State Law 2920. Level of such legal provision: State Law 2920

Authority signing such legal provision: Parliament Authority signing such legal provision: Parliament

These provisions cover: These provisions cover:

Rules of the Air for OAT N

Organisation of military ATS for OAT Y Organisation of military ATS for GAT Y

OAT/GAT Co‐ordination Y OAT/GAT Co‐ordination Y

ATCO Training Y ATCO Training Y

ATCO Licensing Y ATCO Licensing Y

ANSP Certification N ANSP Certification N

ANSP Supervision N ANSP Supervision N

Aircrew Training Y ESARR applicability N

Aircrew Licensing N


Oversight

Service Provision role

Military ANSP providing GAT services SES certified?

N If YES, since: ‐ Duration of the Certificate:

‐

Certificate issued by: MOD If NO, is this fact reported to the EC in accordance with SES regulations?

Additional Information:

Additional Information: Other than the State Law 2920 which grants provision for OAT the Turkish Air Force operate under different State or NATO regulations

Additional Information: There is a protocol between the General Staff and Ministry of Transport, Maritime affairs and Communication for the use of military airports by civil aircraft.

Means used to inform airspace users (other than military) about these provisions:

Means used to inform airspace users (other than military) about these provisions:

National AIP Y National AIP Y

National Military AIP NA National Military AIP N

EUROCONTROL eAIP N EUROCONTROL eAIP N

Other: NA Other: NA

OAT GAT

National oversight body for OAT: Turkish General Staff HQ.

National Supervisory Authority (as per SES reg. 550/2004) for GAT services provided by the military.

OAT GAT

Services Provided: Services Provided:

En‐Route NA En‐Route N

Approach/TMA Y Approach/TMA Y

Airfield/TWR/GND Y Airfield/TWR/GND Y

AIS Y AIS Y

MET N Turkish State Meteorological Service

MET N

SAR Y By the Turkish Air Force for both OAT and GAT

SAR Y

TSA/TRA monitoring Y FIS Y

Other: Security Services Other:

Additional Information: NIL. Additional Information: NIL.


User role

Flexible Use of Airspace (FUA)

IFR inside controlled airspace, Military aircraft can fly?

OAT only GAT only Both OAT and GAT Y

If Military fly OAT‐IFR inside controlled airspace, specify the available options:

Free Routing Within specific corridors only

Within the regular (GAT) national route network Y Under radar control Y

Within a special OAT route system Under radar advisory service

If Military fly GAT‐IFR inside controlled airspace, specify existing special arrangements:

No special arrangements Exemption from Route Charges Y

Exemption from flow and capacity (ATFCM) measures Y Provision of ATC in UHF Y

CNS exemptions: RVSM Y 8.33 Y Mode S Y ACAS Y

Others: The above exemptions do not apply to military heavy transport or VIP aircraft.

Military in Turkey applies FUA requirements as specified in the Regulation No 2150/2005: N

FUA Level 1 implemented: N




2. Traffic and Capacity

Evolution of traffic in Turkey 2.1.

2017 Traffic in Turkey increased by 7.5% during Summer 2017 (May to October), when compared to the same period during 2016.

2018‐2022

The EUROCONTROL Seven‐Year Forecast predicts an average annual increase between 2.8% and 6.7% for Turkey during the 5 year planning cycle, with a baseline growth of 4.6%.

0

500.000

1.000.000

1.500.000

2.000.000

2.500.000

2013 A 2014 A 2015 A 2016 A 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F 2023 F

IFR

flig

hts

Turkey - Annual IFR Movements

IFR movements - Actuals

IFR movements - Baseline forecast

IFR movements - High forecast

IFR movements - Low forecast A = ActualF = Forecast

2014 A 2015 A 2016 A 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F 2023 FH 6.3% 9.2% 6.6% 6.4% 5.5% 5.6% 5.7%B 11.2% 6.8% -1.5% 5.8% 6.9% 4.8% 4.0% 3.6% 3.8% 3.6%L 5.4% 4.9% 2.5% 2.8% 1.8% 2.0% 1.9%

ECAC B 1.7% 1.6% 2.8% 4.5% 2.8% 2.1% 1.9% 1.5% 1.7% 1.7%

EUROCONTROL Seven-Year Forecast (September 2017)IFR flights yearly growth

Turkey


ANKARA ACC - Traffic and en-route ATFM delays 2013-2022 2.2.

Summer 2017 performance 2.3.

Traffic Evolution 2017 Capacity Baseline En‐route Delay (min/flight) ‐ Summer

Capacity gap Ref value Actual

+ 7.4% 221 (+6%) 0.23 0.0 No

The enroute delay per flight in Ankara ACC remained at zero minutes per flight as in Summer 2016.

Capacity Plan +10% Achieved Comments

Improved civil/military coordination Yes

DMAN at LTBA No

Technical problems solved. Tests ongoing. Planned implementation 2018.

Airport CDM at LTBA No Technical problems solved. Tests ongoing. Planned implementation 2018.

Improved ATFCM, including STAM Yes

ATS route structure development Yes

Gradual upper airspace re‐sectorisation (20 to 25 sectors + FL235) Yes

Additional controllers (45 per year for en‐route) Yes

MINI project for interface within Turkey – additional CWPs Yes Ongoing

Capacity Assessment through a CAPAN study Yes

Maximum configuration: 17 sectors Yes 15 sectors were sufficient

Summer 2017 performance assessment

The capacity baseline of 221 was calculated with ACCESS for the new area of responsibility of Ankara ACC. During the same period, the average peak 1 hour demand was 225 and the peak 3 hour demand was 211.

2013 2014 2015 2016 2017 2018 2019 2020 2021 2022

Peak Day Traffic 2587 2993 3370 4377 4629

Summer Traffic 2312 2626 2893 3842 4128

Yearly Traffic* 2037 2302 2574 3443 3705

Summer Traffic Forecast 4382 4589 4751 4925 5110

High Traffic Forecast - Summer 4468 4754 5033 5318 5614

Low Traffic Forecast - Summer 4294 4404 4512 4606 4689

Summer enroute delay (all causes) 0.11 0.11 0.22 0.00 0.00

Yearly enroute delay (all causes) * 0.14 0.12 0.12 0.00 0.00

0.0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1.0

0

1000

2000

3000

4000

5000

6000

En

rou

te D

ela

y (m

inu

tes

pe

r fli

ght)

IFR

flig

hts

(Dai

ly A

vera

ge)

LTAAACC - Traffic and en-route ATFM delays

*From 01/01/2017 to 31/10/2017


Planning Period 2018-2022 2.4.

The planning focuses on the Summer season to reflect the most demanding period of the year from a capacity perspective. This approach ensures consistency with the previous planning cycles.

Capacity Profiles

ACC 2017

baseline

Profiles (hourly movements and % increase over previous year)

2018 2019

LTAA 221

H 250 13% 267 7%

Ref. 245 11% 256 4%

L 240 9% 245 2%

Open 235 6% 246 5%

C/R 242 10% 253 5%

Summer Capacity Plan

2018 2019 2020 2021 2022

Free Route Airspace Stepped implementation of direct/free

route operations above FL290

Airspace Management Advanced FUA

Improved civil/military coordination

Airport & TMA Network Integration Istanbul area

ATC/TMA Center

Cooperative Traffic Management Improved ATFCM, including STAM

Airspace

ATS route structure development

Gradual upper airspace re‐

sectorisation (20 to 25 sectors +

FL235)

New interface with neighbouring states for new Istanbul airport

Procedures New SIDs/STARs for Istanbul TMA

airports

Staffing Additional controllers (45 per year for en‐route)

Technical

MINI project for interface within

Turkey – additional CWPs

Capacity

RTS of Turkish airspace and Interface with neighbouring

states

Capacity Assessment

through a CAPAN study

Significant Events

New airport in Istanbul

from Q3 2018 phase 1A

New airport in Istanbul

from beginning 2019 phase 1B New airport in Istanbul

3 additional phases (depending on capacity triggers)

New APP control office for LTFJ

Independent parallel runway and new ground infrastructure at

LTFJ

Max sectors 30 30 30 30 30

Planned Annual Capacity Increase 20% 6% 6% 6% 6%

Reference profile Annual % Increase 11% 4% N/A N/A N/A


Difference Capacity Plan v. Reference Profile

8.2% 9.8% N/A N/A N/A

Annual Reference Value (min) 0.15 0.15 N/A N/A N/A

Summer reference value (min) 0.22 0.22 N/A N/A N/A

Additional information

Based on the expected traffic evolution in summer 2018, a maximum of 21 sectors should be sufficient to handle traffic demand. However, as stated in the above plan, up to 30 sectors can be opened if required.

2018‐2022 Planning Period Outlook

DHMI is planning sufficient capacity to cope with expected demand. However, some delays and restrictions might be necessary due to the crisis situation in neighbouring states, shifting and concentrating traffic flows in some sectors of Ankara ACC.

0

5

10

15

20

25

00:00

02:00

04:00

06:00

08:00

10:00

12:00

14:00

16:00

18:00

20:00

22:00

Sectors available ‐ Summer 2018 ‐WD

0

5

10

15

20

25

00:00

02:00

04:00

06:00

08:00

10:00

12:00

14:00

16:00

18:00

20:00

22:00

Sectors available ‐ Summer 2018 ‐WE

2016 2017 2018 2019 2020 2021 2022

2018‐2019 Reference Capacity Profile 245 256

Capacity Profile ‐ Shortest Routes (Open) 235 246

Capacity Profile ‐ Current Routes 242 253

Capacity Profile ‐ High 250 267

Capacity Profile ‐ Low 240 245

Capacity Baseline 208 221

2018 ‐ 2022 Plan 265 281 298 316 335

0

50

100

150

200

250

300

350

400

Cap

acity profile (movemen

ts per hour)

LTAAACC - Reference capacity profile and alternative scenarios


3. Master Plan Level 3 Implementation Report conclusions

Conclusions issued from the European ATM Master Plan Level 3 Implementation Report 2016 applicable to Turkey for all items that require corrective actions and improvements.

Conclusion Applicable to VERY GOOD PROGRESS IN IMPLEMENTATION OF BOTH FREE ROUTE AND DIRECT

ROUTING.

THIS MOMENTUM SHOULD BE KEPT AND SUPPORTED BY ALL INVOLVED STAKEHOLDERS.

(page 14 of the Report)

All State that are

implementing

AOM21.1 and

AOM21.2 State’s action planned for this conclusion: YES

Description of the planned action: TR is planning implementation of Free Route by 2020.


4. Implementation Projects

National projects 4.1.

Name of project: Organisation(s): Schedule: Status: ATM MP Links:

A‐SMGCS Level I and II (SMGCS)

DHMI (TR) 2008‐2010 Completed L3: AOP04.1, AOP04.2

AMAN (AMAN) DHMI (TR) 2009‐2016 Completed L3: ATC07.1

AMAN/DMAN (Arrival Manager/Departure Manager) Extention at Istanbul Ataturk Airport

DHMI (TR) 2018‐2019 Ongoing ‐

ARTAS (ART) DHMI (TR) 2006‐2015 Completed L3: ITY‐SPI

MINI Project (MINI_TR)

DHMI (TR) Target date is the opening time of the Istanbul New Airport.

Ongoing ‐

Project SMART implementation (SMART_SYS)

DHMI (TR) 2006‐2015 Completed L3: ATC17, FCM03

Radars replacement (RDR)

DHMI (TR) 2009‐2013 Completed L3: ITY‐SPI

Renovation of Dalaman SSR System and Supply and Installation of PSR / Mode‐S SSR System to Istanbul New Airport

DHMI (TR) 2017‐2019 Ongoing ‐


Regional projects 4.2.

Extended AMAN Project (EXT‐AMAN)

Organisation(s): DHMI (TR) Type of project: Regional

Schedule: Target date for this project is first quarter of 2018.

Status: Ongoing

Description: This project is comprimising Bulgarian airspace besides Istanbul TMA including Atatürk and Istanbul New Airport. New AMAN positions will be installed related Bulgarian ATC units.

Link and references

ATM MP links: L3: ATC15.1, ATC15.2

Other links: ‐

Project included in RP2 Performance Plan:

NA Name/Code in RP2 Performance Plan:

‐

Project included in DP2016:

NA Name/Code in DP2016: ‐

Performance contribution

Safety: ++ Providing more efficient safety benefits

Environment: ‐

Capacity: +++ Increasing capacity

Cost‐efficiency: ‐

Operational efficiency: +++ Increasing the coordination and operational procedures between two

adjacent ATC units

Cooperation Activities: ‐


5. Cooperation activities

FAB Co‐ordination 5.1.

Not applicable.

Regional cooperation 5.2.

Regional cooperation initiatives

It is to be noted that Turkey maintains very close cooperation/co‐ordination with all neighbouring states.

Turkey has taken on responsibility of some transition tasks in the area and arranging air traffic flow to / from

Europe. Turkey is co‐operating with neighbouring states such as Greece and Bulgaria to optimise the

performance of Ground‐Ground Networks and data exchange.

It is also considered that, collaborating as closely as we can with our neighbouring civil air navigation service

providers has a paramount importance in order to optimise the airspace design and management and increase

the regional capacity, safety and quality. Therefore, Turkey undertakes initiatives and efforts to ensure the

application of same concepts, standards and projects under the EUROCONTROL framework.

The fundamental purpose of the Cooperative Airspace Initiative (CAI) is to foster cooperation between NATO

members on airspace surveillance and air traffic coordination with the goals of enhancing transparency,

predictability and the collective capabilities to fight against terrorist air threats. Turkey is playing an essential

role in this project with Local Coordination Unit (LCU), established in Ankara.

On 16 May 2012, a Memorandum of Co‐operation (MoC) was signed between DHMI and Bulgarian Air Traffic

Services Authority (BULATSA) in Ankara. The MoC aimed at common understanding or adoption of ICAO,

EUROCONTROL and other international requirements relevant for the ATM domain and cooperation for

operational area. In the framework of this MoC, the delegations of the DHMI and BULATSA discussed the main

aspects of future co‐operation, such as ensuring an effective route network, common operational and

technical projects, etc.

On 20 June 2012 Ukrainian State Air Traffic Service Enterprise (UkSATSE) and DHMI signed a MOU in Ukraine

which aims the development of regional cooperation between UkSATSE and DHMI. It was also agreed that

working groups on air traffic management, communication, navigation and surveillance, economic and

financial support will further negotiate the related issues.


Regarding with the enhancement of traffic flow between airspaces of Turkey and her neighbouring countries,

DHMI has been co‐operated with ANSPs to implement airspace changes (new COPs and routes) at the

Bulgarian, Georgian, Iranian and Iraq interfaces. As a result of this co‐operation; DHMI has completely changed

the routes on main axes for traffic between Europe and Mid‐East / Gulf Area / Asia / Far‐East.

Also; together with her neighbouring ANSPs and Eurocontrol, DHMI has been working on the airspace changes

that are required to facilitate the traffic flow for Istanbul New Airport that is planned to be in use from the last

quarter of 2018.


6. Implementation Objectives Progress

State View 6.1.

Overall Objective Implementation

Progress distribution for applicable Implementation Objectives

All phases of the objectives (ATC02.9, ATC12.1 and ATC17) have been completed.

The objectives on direct routing and free route airspace will be finalized for 2019‐2020 period. All actions of the objectives (ATC15.2, COM12, INFO07.1) will be conducted on time.

The objectives (AOP10, AOP 12 and AOP 13) are planned to complete in short term for Istanbul New Airport.


Objective Progress per SESAR Key Feature

Note: The detailed table of links between Implementation Objectives and SESAR Key Features is available in Annex C.

Legend:

## % = Expected completion / % Progress = Implementation Objective timeline (different colour per KF)

100% = Objective completed = Completion beyond Implementation Objective timeline


<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling

25%

‐

AOM19.1 (PCP) ASM Support Tools to Support AFUA 0%

‐

AOM19.2 (PCP) ASM Management of Real‐Time Airspace Data 0%

‐

AOM19.3 (PCP) Full rolling ASM/ATFCM Process and ASM Information Sharing

0%

‐

FCM01 Enhanced Tactical Flow Management Services 89%

FCM03 Collaborative Flight Planning 100%

FCM04.1 STAM Phase 1

n/a

FCM04.2 (PCP) STAM Phase 2

n/a

FCM05 (PCP) Interactive Rolling NOP 0%

‐

FCM06 (PCP) Traffic Complexity Assessment

n/a


Advanced Air Traffic Services

<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOM21.1 (PCP)

Direct Routing 10%

AOM21.2 (PCP)

Free Route Airspace 10%

AOP14 Remote Tower Services Local objective

LTCO ‐ AGRI 0%

ATC02.2 STCA En‐Route 100%

ATC02.8 Ground‐Based Safety Nets 100%

ATC02.9 Enhanced STCA for TMAs 100%

ATC07.1 AMAN Tools and Procedures

LTBA ‐ Istanbul Atatürk Airport 100%

ATC12.1

Automated Support for Conflict Detection, Resolution Support Information and Conformance Monitoring

100%

ATC15.1 Information Exchange with En‐route in Support of AMAN

78%

ATC15.2 (PCP) Arrival Management Extended to En‐route Airspace

16%

ATC16 ACAS II Compliant with TCAS II Change 7.1

87%

ATC17

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

100%

ATC18 Multi Sector Planning En‐route ‐ 1P2T

Local objective

n/a

ENV01 Continuous Descent Operations

LTAI ‐ Antalya Airport 47%

LTBA ‐ Istanbul Atatürk Airport 47%

ENV03 Continuous Climb Operations Local objective


LTBA ‐ ISTANBUL/ATATURK 100%

LTBS ‐ MUGLA/DALAMAN (MIL.CIV.) 100%

LTFE ‐ MILAS/BODRUM 100%

ITY‐COTR Ground‐Ground Automated Co‐ordination Processes

n/a

NAV03.1 RNAV 1 in TMA Operations 100%

NAV03.2 (PCP) RNP 1 in TMA Operations 10%

‐

NAV10 APV procedures 55%

NAV12 Optimised Low‐Level IFR Routes in TMA for Rotorcraft

Local objective

n/a


High Performing Airport Operations

<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOP04.1 A‐SMGCS Level 1

LTAC ‐ Ankara Esenboga Airport

100%


LTBA ‐ Istanbul Atatürk Airport

100%

AOP04.2 A‐SMGCS Level 2


100%



100%

AOP05 Airport CDM



93%

AOP10 (PCP)

Time‐Based Separation 0%

LTBA ‐ Istanbul Atatürk Airport (Outside Applicability Area)

0%

AOP11 (PCP)

Initial Airport Operations Plan


n/a

AOP12 (PCP)

Improve Runway and Airfield Safety with ATC Clearances Monitoring


18%

AOP13 (PCP)

Automated Assistance to Controller for Surface Movement Planning and Routing


12%

ENV02 Collaborative Environmental Management



100%

SAF11 Improve Runway Safety by Preventing Runway Excursions

100%



<15 15 16 17 18 19 20 21 22 23 24 ≥25

COM10 Migrate from AFTN to AMHS 100%

COM11 Voice over Internet Protocol (VoIP) 53%

COM12 (PCP) NewPENS 0%

FCM08 (PCP) Extended Flight Plan 0%

INF04 Integrated Briefing 100%

INF07 Electronic Terrain and Obstacle Data (eTOD) 81%

ITY‐ACID Aircraft Identification

n/a

ITY‐ADQ Ensure Quality of Aeronautical Data and Aeronautical Information

36%

ITY‐AGDL Initial ATC Air‐Ground Data Link Services

n/a

ITY‐AGVCS2 8,33 kHz Air‐Ground Voice Channel Spacing below FL195

n/a

ITY‐FMTP Common Flight Message Transfer Protocol 100%

ITY‐SPI Surveillance Performance and Interoperability

n/a


ICAO ASBU Implementation

The following table shows, for each of the ASBU Block 0 modules, the overall status, the final date foreseen for completion and the percentage of progress achieved in the current cycle.

These results were determined using the LSSIP Year 2017 declared statuses and progress of the relevant Implementation objectives in accordance with the mapping approved by ICAO EUR EANPG/59 (European Air Navigation Planning Group).

Legend:

= Completed (during 2017 or before)

= Missing planning date

= Progress achieved in 2017 = Not applicable

<16 16 17 18 19 20 21 22 23 24 ≥25

B0‐APTA Optimization of Approach Procedures including vertical guidance

100%

78%

B0‐SURF Safety and Efficiency of Surface Operations (A‐SMGCS Level 1‐2)

100%

B0‐FICE Increased Interoperability, Efficiency and Capacity through Ground‐Ground Integration

100%

B0‐DATM Service Improvement through Digital Aeronautical Information Management

100%

68%

B0‐ACAS ACAS Improvements 100%

87%

B0‐SNET Increased Effectiveness of Ground‐Based Safety Nets

100%

B0‐ACDM Improved Airport Operations through 100%

52%

B0‐RSEQ Improved Traffic flow through Runway sequencing (AMAN/DMAN)

100%

89%

B0‐FRTO Improved Operations through Enhanced En‐Route Trajectories

100%

37%

B0‐NOPS Improved Flow Performance through Planning based on a Network‐Wide view

100%

94%

B0‐ASUR Initial capability for ground surveillance

B0‐CDO Improved Flexibility and Efficiency in Descent Profiles (CDO)

100%

47%

B0‐TBO Improved Safety and Efficiency through the initial application of Data Link En‐Route


Detailed Objectives Implementation progress 6.2.

Note: The detailed table of applicability area for the Implementation Objectives is available in Annex C.

Objective/Stakeholder Progress Code:

Completed No Plan

Ongoing Not Applicable

Planned Missing Data

Late


Main Objectives

AOM13.1

Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) Handling Timescales: Initial operational capability: 01/01/2012 Full operational capability: 31/12/2018

25% No Plan

‐

Turkish FUA Regulation has been published in Official Gazette on 18 April 2014. The Military Authority has completed it's structure to implement FUA in Turkish Airspace. Personnel assignments and software developments has been completed. The Military Authority is ready to fully implement FUA in Turkish Airspace.

‐

REG (By:12/2018)

DGCA No current plan related appropriate legislation. ‐ 0% No Plan

‐

ASP (By:12/2018)

DHMI No current plan until appropriate legislation is passed. Implementation of the objective will take place in parallel with the military

‐ 0% No Plan

‐

MIL (By:12/2018)

Mil. Authority

Turkish FUA Regulation has been published in Official Gazette on 18 April 2014. The Military Authority has completed it's structure to implement FUA in Turkish Airspace. Personnel assignments and software developments has been completed. The Military Authority is ready to fully implement FUA in Turkish Airspace.

‐ %

Not Applicable

‐

AOM19.1

ASM Support Tools to Support Advanced FUA (AFUA) Timescales: Initial operational capability: 01/01/2011 Full operational capability: 31/12/2018

0% No Plan

‐

This objective will be re‐evaluated for the next LSSIP cycle. ‐

ASP (By:12/2018)

DHMI ‐ ‐ 0% No Plan

‐

AOM19.2

ASM Management of Real‐Time Airspace Data Timescales: Initial operational capability: 01/01/2017 Full operational capability: 31/12/2021

0% No Plan

‐

No plan ‐

ASP (By:12/2021)


‐


AOM19.3

Full Rolling ASM/ATFCM Process and ASM Information Sharing Timescales: Initial operational capability: 01/01/2014 Full operational capability: 31/12/2021

0% No Plan

‐

No plan ‐

ASP (By:12/2021)


‐

AOM21.1

Direct Routing Timescales: Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2017

10% Late

‐

Implementation of direct routing planned and necessary activities will be completed before 31/12/2019.

31/12/2019

ASP (By:12/2017)

DHMI Implementation of direct routing planned and necessary activities will be completed before 31/12/2019.

‐ 10% Late

31/12/2019

AOM21.2

Free Route Airspace Timescales: Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021

10% Ongoing

‐

Implementation of free route airspace is planned in 2020. 31/12/2020

ASP (By:12/2021)

DHMI Implementation of free route airspace is planned in 2020. ‐ 10% Ongoing

31/12/2020

AOP04.1

Advanced Surface Movement Guidance and Control System A‐SMGCS Surveillance (former Level 1) Timescales: Initial operational capability: 01/01/2007 Full operational capability: 31/12/2011

100% Completed


Ankara implemented A‐SMGS Level 1 and 2 in June 2010. 30/06/2010

REG (By:12/2010)

DGCA No plan to implement. Not applicable in TR. ‐ % Not Applicable

‐

ASP (By:12/2011)

DHMI Ankara implemented A‐SMGS Level 1 and 2 in June 2010. A‐SMGCS

Level I and II 100%

Completed

30/06/2010

APO (By:12/2010)

ANKARA Esenboga Airport

Drivers have received instruction on the system. ‐ 100% Completed

30/06/2010


AOP04.1


100% Completed

LTAI ‐ Antalya Airport

Antalya implemented A‐SMGCS Level 1 and 2 in June 2010. 30/06/2010

REG (By:12/2010)

DGCA Not applicable in TR. ‐ % Not Applicable

‐

ASP (By:12/2011)

DHMI Antalya implemented A‐SMGS Level 1 and 2 in June 2010. All training and development of procedures has been completed.

A‐SMGCS Level I and II

100% Completed

30/06/2010

APO (By:12/2010)

ANTALYA Airport

Drivers have received instruction on the system ‐ 100% Completed

30/06/2010

AOP04.1


100% Completed


Istanbul implemented A‐SMGCS Level 1 and 2 in June 2010. 30/06/2010

REG (By:12/2010)

DGCA Not applicable in TR. ‐ % Not Applicable

‐

ASP (By:12/2011)

DHMI Istanbul implemented A‐SMGCS Level 1 and 2 in June 2010. All training and development of procedures has been completed.

A‐SMGCS Level I and II

100% Completed

30/06/2010

APO (By:12/2010)

ISTANBUL Atatürk Airport


30/06/2010

AOP04.2

Advanced Surface Movement Guidance and Control System (A‐SMGCS) Runway Monitoring and Conflict Alerting (RMCA) (former Level 2) Timescales: Initial operational capability: 01/01/2007 Full operational capability: 31/12/2017

100% Completed


Ankara implemented A‐SMGS Level 1 and 2 in June 2010. 30/06/2010

ASP (By:12/2017)

DHMI Ankara implemented A‐SMGS Level 1 and 2 in June 2010. A‐SMGCS

Level I and II 100%

Completed

30/06/2010

APO (By:12/2017)

ANKARA Esenboga Airport


30/06/2010


AOP04.2


100% Completed


Antalya implemented A‐SMGS Level 1 and 2 in June 2010. 30/06/2010

ASP (By:12/2017)

DHMI Antalya implemented A‐SMGS Level 1 and 2 in June 2010. A‐SMGCS

Level I and II 100%

Completed

30/06/2010

APO (By:12/2017)

ANTALYA Airport


30/06/2010

AOP04.2


100% Completed


Istanbul implemented A‐SMGS Level 1 and 2 in June 2010. 30/06/2010

ASP (By:12/2017)

DHMI Istanbul implemented A‐SMGS Level 1 and 2 in June 2010. A‐SMGCS

Level I and II 100%

Completed

30/06/2010

APO (By:12/2017)



30/06/2010

AOP05

Airport Collaborative Decision Making (A‐CDM) Timescales: Initial operational capability: 01/01/2004 Full operational capability: 31/12/2016

10% Late


A draft MoU has been circulated to key stakeholders. Studies for Antalya are going on. 31/12/2018

ASP (By:12/2016)

DHMI DHMI has initiated action to implement this objective. A draft MoU has been developed and circulated to key stakeholders.

‐ 10% Late

31/12/2018

APO (By:12/2016)

ANTALYA Airport

DHMI has initiated action to implement this objective. A draft MoU has been developed and circulated to key stakeholders

‐ 10% Late

31/12/2018


AOP05

Airport Collaborative Decision Making (A‐CDM) Timescales: Initial operational capability: 01/01/2004 Full operational capability: 31/12/2016

93% Late


A MoU has been agreed and signed. Working groups have been formed. CDM platform has been established and tests have been completed.

31/12/2018

ASP (By:12/2016)

DHMI A MoU has been agreed and signed. Working groups have been formed. CDM platform has been established and tests have been completed.

‐ 100% Completed

31/12/2017

APO (By:12/2016)


A MoU has been agreed and signed. Working groups have been formed. CDM platform has been established. The exchange of messages will be implemented.

‐ 85% Late

31/12/2018

AOP10 Time‐Based Separation Timescales: ‐ not applicable ‐

0% Planned


The implementation of TBS is planned for Istanbul New Airport in 2021. 31/12/2021

REG (By:12/2023)

DGCA Necessary actions will be taken before the implementation date.

‐ 0% Planned

31/12/2021

ASP (By:12/2023)

DHMI The implementation of TBS is planned for Istanbul New Airport in 2021.

‐ 0% Planned

31/12/2021

AOP11 Initial Airport Operations Plan Timescales: ‐ not applicable ‐

% Not

Applicable


All information effecting the air traffic flow for airports has been published via AIP, NOTAMs and airport corner web site.

‐

ASP (By:12/2021)

DHMI All information effecting the air traffic flow for airports has been published via AIP, NOTAMs and airport corner web site.

‐ % Not Applicable

‐

APO (By:12/2021)


AOP12

Improve Runway and Airfield Safety with Conflicting ATC Clearances (CATC) Detection and Conformance Monitoring Alerts for Controllers (CMAC) Timescales: Initial operational capability: 01/01/2015 Full operational capability: 31/12/2020

18% Ongoing


No plan for Atatürk Airport. The installation of the electronic flight strips with DCL function is planned for Istanbul New Airport which will be fully integrated with new A‐SMGCS Level 4 (+) system. The implementation of the ATC clearances monitoring tools will be included within new software.

31/12/2018

ASP (By:12/2020)

DHMI


‐ 20%

Ongoing

31/12/2018

APO (By:12/2020)



‐ 10%

Ongoing

31/12/2018

AOP13

Automated Assistance to Controller for Surface Movement Planning and Routing Timescales: Initial operational capability: 01/01/2016 Full operational capability: 31/12/2023

12% Ongoing


No plan for Atatürk Airport. These functions will be executed as the part of Istanbul New Airport's A‐SMGCS System in 2018.

31/12/2018

REG (By:12/2023)

DGCA All actions will be taken before implementation date. ‐ 0% Planned

31/12/2018

ASP (By:12/2023)

DHMI No plan for Atatürk Airport. These functions will be executed as the part of Istanbul New Airport's A‐SMGCS System in 2018.

‐ 15% Ongoing

31/12/2018


ATC02.8

Ground‐Based Safety Nets Timescales: Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016

100% Completed

‐

All functions implemented. 18/11/2015

ASP (By:12/2016)

Mil. Authority Military units have APM functionality but due to the dynamic nature of OAT operations this functionality is only enabled at airports that serve GAT.

‐ 100% Completed

31/12/2008

DHMI

APW level 2 has been implemented with the SMART project which was completed 11/2015. MSAW has been implemented with the SMART system. APM, in line with EUROCONTROL specifications, has been implemented at Istanbul, Esenboga, Antalya, Dalaman, Bodrum and Izmir airports in parallel with SMART.

‐ 100%

Completed

18/11/2015

ATC02.9

Enhanced Short Term Conflict Alert (STCA) for TMAs Timescales: Initial operational capability: 01/01/2018 Full operational capability: 31/12/2020

100% Completed

‐

Implementation of STCA funct,on in TMA has already adapted to major TMAs like Istanbul, Ankara, Antalya, Izmir; Dalaman, Milas and Trabzon.

31/12/2015

ASP (By:12/2020)

DHMI Implementation of STCA funct,on in TMA has already adapted to major TMAs like Istanbul, Ankara, Antalya, Izmir; Dalaman, Milas and Trabzon.

‐ 100% Completed

31/12/2015

ATC07.1

AMAN Tools and Procedures Timescales: Initial operational capability: 01/01/2007 Full operational capability: 31/12/2019

100% Completed


Tender and acceptance of AMAN has already been done for Atatürk and S.Gölçen Airports. AMAN has been operational since last quarter of 2016.

30/09/2016

ASP (By:12/2019)

DHMI

Tender and acceptance of AMAN has already been done for Atatürk and S.Gölçen Airports. AMAN has been operational since last quarter of 2016. Preparation of technical aspects for Antalya Airport AMAN has been finalised and tender held on in 2015 but due to lack of enough participants for tender, second tender will be realized in 2017.

AMAN 100%

Completed

30/09/2016


ATC12.1

Automated Support for Conflict Detection, Resolution Support Information and Conformance Monitoring Timescales: Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021

100% Completed

‐

MONA functions has been implemented. ATCO training on MONA has been conducted. 07/07/2015

ASP (By:12/2021)

DHMI MONA functions has been implemented. ATCO training on MONA has been conducted.

‐ 100% Completed

07/07/2015

ATC15.1

Information Exchange with En‐route in Support of AMAN Timescales: Initial operational capability: 01/01/2012 Full operational capability: 31/12/2017

78% Late

‐

AMAN is operational for Istanbul Atatürk and S.Gökçen Airports. Adjacent ACC sectors within SMART project have been equiped with AMAN supporting systems, including monitors and sofware. New AMAN software will be implemented by 2019 for Istanbul TMA including Istanbul New Airport and S.Gökçen Airport. Beside this related ACC sectors of Sofia ACC will equiped with AMAN supporting systems, including monitors and sofware

31/12/2019

ASP (By:12/2017)

DHMI

The implementation of AMAN is planned for Istanbul Atatürk and S.Gökçen Airports. We have already arranged close cooperation with BULATSA on AMAN implementation.

Extended AMAN Project

78%

Late

31/12/2019

ATC15.2

Arrival Management Extended to En‐route Airspace (Outside Applicability Area) Timescales: ‐ not applicable ‐

16% Ongoing

‐

Extended AMAN project for Istanbul TMA and related ACC sectors including Sofia ACC will be started by end of 2018.

31/12/2018

ASP (By:12/2023)

DHMI Extended AMAN project for Istanbul TMA and related ACC sectors including Sofia ACC will be started by end of 2018.

Extended AMAN Project

16% Ongoing

31/12/2018


ATC17

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer Timescales: Initial operational capability: 01/01/2013 Full operational capability: 31/12/2018

100% Completed

‐

All functions have been in use with SMART project.Safety arguments for changes will be generated.

18/11/2015

ASP (By:12/2018)

Mil. Authority ‐ ‐ % Not Applicable

‐

DHMI All functions have been in use with SMART project.

Project SMART

implementation

100%

Completed

18/11/2015

COM10

Migrate from AFTN to AMHS Timescales: Initial operational capability: 01/12/2011 Full operational capability: 31/12/2018

100% Completed

‐

The AMHS/AFTN/CIDIN system is active now. The existing system is making data exchange. There is no need to Implement gateway between national non‐AMHS network (other than AFTN) and AMHS at the moment. Military have their own communication network for OAT message purposes. The system is fully interoperable with the ANSP.

31/12/2014

ASP (By:12/2018)

DHMI ‐ ‐ 100% Completed

31/10/2014

Mil. Authority

The AMHS/AFTN/CIDIN system is active now. The existing system is making data exchange. There is no need to Implement gateway between national non‐AMHS network (other than AFTN) and AMHS at the moment. Military have their own communication network for OAT message purposes. The system is fully interoperable with the ANSP.

‐ 100%

Completed

31/12/2014

COM11

Voice over Internet Protocol (VoIP) Timescales: Initial operational capability: 01/01/2013 Full operational capability: 31/12/2020

53% Ongoing

‐

Turkey will implement VoIP based network until 2020. 31/10/2020

ASP (By:12/2020)


‐

DHMI Turkey will implement VoIP based network until 2020. ‐ 53% Ongoing

31/10/2020


COM12

New Pan‐European Network Service (NewPENS) Timescales: Initial operational capability: 01/01/2018 Full operational capability (Other stakeholders): 31/12/2024

0% Planned

‐

Infrastructure will be adapted for NewPENS by end of 2022. New contract and migration of services will be done until end of 2023.

31/12/2023

ASP (By:12/2024)

DHMI Infrastructure will be adapted for NewPENS by end of 2022. New contract and migration of services will be done until end of 2023.

‐ 0% Planned

31/12/2023

APO (By:12/2024)

DHMI Infrastructure will be adapted for NewPENS by end of 2022. New contract and migration of services will be done until end of 2023.

‐ 0% Planned

31/12/2023

ENV01

Continuous Descent Operations (CDO) Timescales: Initial operational capability: 01/07/2007 Full operational capability: 31/12/2013

47% Late


An initial CDA workshop meeting was given by EUROCONTROL. DHMI will implement CDO in the medium term future.

31/12/2018

ASP (By:12/2013)

DHMI DHMI will implement CDO in the medium term. ‐ 45% Late

31/12/2018

APO (By:12/2013)

ANTALYA Airport

DHMI will implement CDO in the medium term. ‐ 50% Late

31/12/2018

ENV01

Continuous Descent Operations (CDO) Timescales: Initial operational capability: 01/07/2007 Full operational capability: 31/12/2013

47% Late


An initial CDA workshop meeting was given by EUROCONTROL. DHMI will implement CDO in the medium term future.

31/12/2018

ASP (By:12/2013)

DHMI DHMI will implement CDO in the medium term. ‐ 45% Late

31/12/2018

APO (By:12/2013)


DHMI will implement CDO in the medium term. ‐ 50% Late

31/12/2018


ENV02

Airport Collaborative Environmental Management Timescales: Initial operational capability: 01/09/2004 Full operational capability: 31/12/2016

100% Completed


SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project. There is legislation regarding maximum noise levels generated by aircraft but no system of enforcement/punitive measures has been developed as yet. Local traffic regulations have been developed in coordination with airport and airline operators in 2014 and implemented at first half of 2015.

30/04/2015

ASP (By:12/2016)

DHMI

SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project.Local traffic regulations have been developed in coordination with airport and airline operators in 2014 and implemented at first half of 2015.

‐ 100%

Completed

30/04/2015

APO (By:12/2016)

ANTALYA Airport

SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project.Local traffic regulations have been developed in 2014 and implemented at first half of 2015.

‐ 100%

Completed

31/12/2014

ENV02

Airport Collaborative Environmental Management Timescales: Initial operational capability: 01/09/2004 Full operational capability: 31/12/2016

100% Completed


SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project. There is legislation regarding maximum noise levels generated by aircraft but no system of enforcement/punitive measures has been developed as yet.

31/12/2014

ASP (By:12/2016)

DHMI

SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project.

‐ 100%

Completed

31/12/2014

APO (By:12/2016)


SIDs have been designed to provide noise abatement over the most congested areas. Noise monitors have been established and data is being analysed in a noise map pilot project.

‐ 100%

Completed

31/12/2014


FCM03

Collaborative Flight Planning Timescales: Initial operational capability: 01/01/2000 Full operational capability: 31/12/2017

100% Completed

‐

The SMART system is capable of compliance with all SLoAs other than ASP09. The other remaining objectives are in use.

07/07/2015

ASP (By:12/2017)

DHMI The SMART system is capable of compliance with all SLoAs other than ASP09. The other remaining objectives are in use.

Project SMART

implementation

100%

Completed

07/07/2015

FCM04.1

Short Term ATFCM Measures (STAM) ‐ Phase 1 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

TR is not in the applicability area. ‐

ASP (By:10/2017)

DHMI ‐ ‐ % Not Applicable

‐

FCM04.2

Short Term ATFCM Measures (STAM) ‐ Phase 2 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Turkey is not within applicability area of this objective. ‐

ASP (By:12/2021)


‐

FCM05

Interactive Rolling NOP Timescales: Initial operational capability: 01/09/2013 Full operational capability: 31/12/2021

0% No Plan

‐

The decision to implementation of interactive rolling NOP has not been taken yet. ‐

ASP (By:12/2021)


‐

APO (By:12/2021)

DHMI No plan ‐ 0% No Plan

‐


FCM06

Traffic Complexity Assessment (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Turkey is not within the area of applicability of this objective. ‐

ASP (By:12/2021)

DHMI Turkey is not within the area of applicability of this objective.

‐ % Not Applicable

‐

FCM08

Extended Flight Plan Timescales: Initial operational capability: 01/01/2016 Full operational capability: 31/12/2021

0% Planned

‐

The infrastucture and operational functions will be prepared until 2021. 31/12/2021

ASP (By:12/2021)

DHMI The infrastucture and operational functions will be prepared until 2021.

‐ 0% Planned

31/12/2021

INF07

Electronic Terrain and Obstacle Data (eTOD) Timescales: Initial operational capability: 01/11/2014 Full operational capability: 31/05/2018

81% Ongoing

‐

National law has been published to enable the provision of electronic terrain and obstacle data for Area 1. The other regulatory issues will be completed in 2018.

31/05/2018

REG (By:05/2018)

DGCA

National law has been published to enable the provision of electronic terrain and obstacle data for Area 1.TOD regulatory has been prepared in accordance with law for Area 1.

‐ 63%

Ongoing

31/05/2018

ASP (By:05/2018)

DHMI All actions have been completed in accordance with national TOD regulations.

‐ 100% Completed

31/12/2017

APO (By:05/2018)

DHMI All actions have been completed in accordance with national TOD regulations.

‐ 100% Completed

31/12/2017

ITY‐ACID

Aircraft Identification (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Turkey is not within applicability area of this objective. ‐

ASP (By:01/2020)


‐


ITY‐ADQ

Ensure Quality of Aeronautical Data and Aeronautical Information (Outside Applicability Area) Timescales: ‐ not applicable ‐

36% Late

‐

Data quality and digital exchange format requirements have been implemented.The other actions will be completed before implementation date.

31/12/2022

REG (By:06/2017)

DGCA Verification processes will be completed before the implementation date.

‐ 0% Late

31/12/2022

ASP (By:06/2017)

DHMI Data quality and digital exchange format requirements have been implemented.The other actions will be completed before implementation date.

‐ 40% Late

31/12/2022

APO (By:06/2017)

DHMI Data quality and digital exchange format requirements have been implemented.The other actions will be completed before implementation date.

‐ 52% Late

31/12/2022

ITY‐AGDL

Initial ATC Air‐Ground Data Link Services (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐


REG (By:02/2018)

DGCA ‐ ‐ % Not Applicable

‐

ASP (By:02/2018)


‐

MIL (By:01/2019)


‐


ITY‐AGVCS2

8,33 kHz Air‐Ground Voice Channel Spacing below FL195 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

TR is not in the applicability area. ‐

REG (By:12/2018)

DGCA ‐ ‐ % Not Applicable

‐

ASP (By:12/2018)


‐

MIL (By:12/2020)


‐

APO (By:12/2018)

ITY‐FMTP

Common Flight Message Transfer Protocol (FMTP) Timescales: Entry into force of regulation: 28/06/2007 All EATMN systems put into service after 01/01/09: 01/01/2009 All EATMN systems in operation by 20/04/11: 20/04/2011 Transitional arrangements: 31/12/2012 Transitional arrangements when bilaterally agreed between ANSPs: 31/12/2014

100% Completed

‐

The common flight message transfer protocol has been introduced with the SMART system. 31/05/2015

ASP (By:12/2014)

DHMI The common flight message transfer protocol has been introduced with the SMART system.

‐ 100% Completed

31/05/2015

Mil. Authority

Military has its own network between military sites and there is no plan to upgrade this system. The interface between military/civil sites has been completed. Current interface is limited for monitoring the sellected flights.

‐ 100%

Completed

31/05/2015

MIL (By:12/2014)

Mil. Authority Military has its own network between military sites and there is no plan to upgrade this system. The interface between military/civil sites has been completed.

‐ 100% Completed

31/05/2015


ITY‐SPI

Surveillance Performance and Interoperability (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Turkey is not an EU+ State. ‐

REG (By:02/2015)

DGCA Turkey is not EU+ State. ‐ % Not Applicable

‐

ASP (By:02/2015)

DHMI Turkey is not EU+ State. ARTAS / Radars

replacement

% Not Applicable

‐

MIL (By:06/2020)

Mil. Authority Turkey is not EU+ State. ‐ % Not Applicable

‐

NAV03.1

RNAV 1 in TMA Operations Timescales: Initial operational capability: 01/01/2001 Full operational capability: 31/12/2023

100% Completed

‐

P‐RNAV SIDs and STARS have been implemented at Istanbul, S.Gökçen, Antalya, Esenboga, Dalaman, Bodrum, Trabzon Airports. Implementation at other airports will continue in due course.

31/12/2017

ASP (By:12/2023)

Mil. Authority P‐RNAV SIDs and STARS have been implemented at some military airports. Implementation at other military airports will continue in due course.

‐ % Completed

‐

DHMI

P‐RNAV SIDs and STARS have been implemented at Istanbul, S.Gökçen, Antalya, Esenboga, Dalaman, Bodrum Airports. Implementation at other airports will continue in due course.

‐ 100%

Completed

31/12/2017

NAV03.2

RNP 1 in TMA Operations Timescales: Initial operational capability: 01/01/2018 Full operational capability: 31/12/2023

10% No Plan

‐

No plans at this stage. ‐

ASP (By:12/2023)


‐


NAV10

APV Procedures Timescales: Initial operational capability: 01/06/2011 Full operational capability: 31/12/2016

55% Late

‐

Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published. APV BARO‐VNAV procedures for some airports have been published. Studies to design new procedures are going on.

31/12/2018

REG (By:04/2016)

DGCA Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published.

‐ 100% Completed

31/12/2015

ASP (By:12/2016)

DHMI

Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published. APV BARO‐VNAV procedures for some airports have been published. Studies to design new procedures are going on.

‐ 40%

Late

31/12/2018

SAF11

Improve Runway Safety by Preventing Runway Excursions Timescales: Initial operational capability: 01/09/2013 Full operational capability: 31/01/2018

100% Completed

‐

Local runway safety teams have been established for each aerodromes. These teams are responsible for runway excursions.

31/12/2016

REG (By:01/2018)

DGCA Necessary actions have been handled. ‐ 100% Completed

31/12/2016

Mil. Authority Necessary actions have been handled. ‐ 100% Completed

‐

ASP (By:12/2014)

DHMI Local runway safety teams have been established for each aerodromes. These teams are responsible for runway excursions.

‐ 100% Completed

31/12/2016

APO (By:12/2014)


Local runway safety teams have been established for each aerodromes. These teams areresponsible for runway excursions.

‐ 100% Completed

31/12/2015


Additional Objectives for ICAO ASBU Monitoring

ATC02.2

Implement ground based safety nets ‐ Short Term Conflict Alert (STCA) ‐ level 2 for en‐route operations Timescales: Initial operational capability: 01/01/2008 Full operational capability: 31/01/2013

100% Completed

‐

Is a functionality included as part of SMART system and was operational from 09/2008. All en‐route and TMA airspace is covered. STCA implementation/procedures will be audited by the DGCA when human resources permit.

30/09/2008

ASP (By:01/2013)

DHMI STCA is a functionality included as part of the Interim SMART system. The STCA is in accordance with EUROCONTROL specifications.

‐ 100% Completed

30/09/2008

ATC16

Implement ACAS II compliant with TCAS II change 7.1 Timescales: Initial operational capability: 01/03/2012 Full operational capability: 31/12/2015

87% Late

‐

The training plan for ACAS II version 7.1 has been developed. ATC units have been monitoring the performance of ACAS. Regulation on ACAS II version 7.1 has been published on 06 November 2015. Certain type of the military transport aircraft have been equipped with ACAS.

31/12/2019

REG (By:12/2015)

DGCA Regulation on ACAS II version 7.1 has been published on 06 November 2015.

‐ 100% Completed

01/12/2015

ASP (By:03/2012)

DHMI The training plan for ACAS II version 7.1 has been developed.ATC units have been monitoring the performance of ACAS.

‐ 100% Completed

31/03/2012

MIL (By:12/2015)

Mil. Authority

Certain type of the transport aircraft have been equipped with ACAS. The training has been completed.All the transport type a/c with ACAS II will be equipped until end of 2019

‐ 55%

Late

31/12/2019


FCM01

Implement enhanced tactical flow management services Timescales: Initial operational capability: 01/08/2001 Full operational capability: 31/12/2006

89% Late

‐

Some system modifications are still required and the date of 12/2017 is the planned completion date for all objectives.

31/12/2018

ASP (By:07/2014)

DHMI

Objective FCM01‐ASP08 will be in SMART phase so date of 12/2016 is the planned completion date. The other remaining objectives are ready and FSA mesages for Ankara have been tested with CFMU and approved. The software is not installed in accordance with sending proper FSA messages for Istanbul and Izmir . In addition the system is sending OAT rather than just GAT correlated flight data. All objectives will be completed by 12/2016.

‐ 89%

Late

31/12/2018

INF04

Implement integrated briefing Timescales: Initial operational capability: 01/07/2002 Full operational capability: 31/12/2012

100% Completed

‐

All infrastructure ready for full implementation in 07/2010. 31/07/2010

ASP (By:12/2012)

DHMI ‐ ‐ 100% Completed

31/07/2010

Mil. Authority

All infrastructure ready for full implementation in 07/2010.

‐ 100% Completed

31/07/2010

ITY‐COTR

Implementation of ground‐ground automated co‐ordination processes (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐


ASP (By:12/2012)

DHMI ‐ ‐ % Not

Applicable

‐

MIL (By:12/2012)

Mil. Authority

‐ ‐ % Not

Applicable

‐


Local Objectives

AOP14 Remote Tower Services Applicability and timescale: Local

0% Planned

LTCO ‐ AGRI

Remote tower services planned by the end of 2019. 31/12/2019

ATC18 Multi‐Sector Planning En‐route ‐ 1P2T Applicability and timescale: Local

% Not

Applicable

‐

Considered as not applicable in TR. ‐

ENV03 Continuous Climb Operations (CCO) Applicability and timescale: Local

100% Completed


PBN SIDs have been developed and implemented for Antalya Airport. These SIDs are designed to provide optimised vertical profile and short track and to avoid the conflict btn. STARs and SIDs as possible. Also, CCO techniques are implemented by ATC as tactically for stated airports now. The necessary notification in AIP will be issued in short term.

01/06/2016


100% Completed

LTBA ‐ ISTANBUL/ATATURK

PBN SIDs have been developed and implemented for Istanbul Atatürk. These SIDs are designed to provide optimised vertical profile and short track and to avoid the conflict btn. STARs and SIDs as possible. Also, CCO techniques are implemented by ATC as tactically for stated airports now. The necessary notification in AIP will be issued in short term.

01/06/2016


100% Completed

LTBS ‐ MUGLA/DALAMAN (MIL.CIV.)

PBN SIDs have been developed and implemented for Dalaman Airport. These SIDs are designed to provide optimised vertical profile and short track and to avoid the conflict btn. STARs and SIDs as possible. Also, CCO techniques are implemented by ATC as tactically for stated airports now. The necessary notification in AIP will be issued in short term.

01/06/2016


100% Completed

LTFE ‐ MILAS/BODRUM

PBN SIDs have been developed and implemented for Milas Bodrum Airport. These SIDs are designed to provide optimised vertical profile and short track and to avoid the conflict btn. STARs and SIDs as possible. Also, CCO techniques are implemented by ATC as tactically for stated airports now. The necessary notification in AIP will be issued in short term.

01/06/2016

NAV12 Optimised Low‐Level IFR Routes in TMA for Rotorcraft Applicability and timescale: Local

% Not

Applicable

‐

Considered as not applicable in TR. ‐


ANNEXES

ANNEX A ‐ Specialists involved in the LSSIP Process

LSSIP Co‐ordination

LSSIP Focal Points Organisation Name

LSSIP National Focal Point for Turkey DHMI Cihan Sahin

EUROCONTROL LSSIP Support

Function Directorate Name

LSSIP Contact Person for Turkey DECMA/PEPR Predrag VRANJKOVIC


Implementation Objectives

Implementation Objective

EUROCONTROL PEPR Objective Coordinator

EUROCONTROL Objective Owners

National Stakeholder Specialist

AOM13.1 A. DYBOWSKA O. MROWICKI/ C. LUCCIOLI

AOM19.1 O. ALFARO G. ACAMPORA /

O. MROWICKI


O. MROWICKI


O. MROWICKI

AOM21.1 A. DYBOWSKA C. BRAIN

AOM21.2 A. DYBOWSKA C. BRAIN

AOP04.1 P. VRANJKOVIC R. GRAHAM

AOP04.2 P. VRANJKOVIC R. GRAHAM

AOP05 F. ROOSELEER M. BIRENHEIDE

AOP10 F. ROOSELEER R. GRAHAM

AOP11 F. ROOSELEER M. BIRENHEIDE

AOP12 P. VRANJKOVIC R. GRAHAM

AOP13 P. VRANJKOVIC R. GRAHAM

AOP14 A. DYBOWSKA R. GRAHAM / G. ASSIRE

ATC02.8 F. ROOSELEER S. DROZDOWSKI

ATC02.9 F. ROOSELEER S. DROZDOWSKI

ATC07.1 L. DELL’ORTO pending



ATC15.2 L. DELL’ORTO P. HOP

ATC17 L. DELL’ORTO S. MORTON

ATC18 L. DELL’ORTO I. PENDACHANSKI

COM10 J. PINTO Y. EYUBOGLU

COM11 J. PINTO L. POPESCU

COM12 J. PINTO W. JANSSENS

ENV01 B. HILL D. BRAIN

ENV02 B. HILL S. MAHONY

ENV03 A‐P. FRANGOLHO D. BRAIN

FCM03 O. CIOARA C. BOUMAN/I. PENDACHANSKI

FCM04.1 I. MARCETIC P. HOP/I. PENDACHANSKI

FCM04.2 I. MARCETIC P. HOP/I. PENDACHANSKI

FCM05 O. CIOARA I. MENDES VIDEIRA/I. PENDACHANSKI

FCM06 F. ROOSELEER P. HOP/I. PENDACHANSKI


FCM08 O. CIOARA K. BREIVIK/I. PENDACHANSKI

INF07 A‐P. FRANGOLHO A. PETROVSKY

ITY‐ACID O. CIOARA pending

ITY‐ADQ A‐P. FRANGOLHO M. UNTERREINER

ITY‐AGDL B. HILL D. ISAAC

ATY‐AGVCS2 B. HILL J. POUZET

ITY‐FMTP O. ALFARO L. POPESCU

ITY‐SPI O. CIOARA M. BORELY

NAV03.1 I. MARCETIC F. PAVLICEVIC

NAV03.2 I. MARCETIC F. PAVLICEVIC

NAV10 I. MARCETIC R. FARNWORTH

NAV12 I. MARCETIC B. RABILLER / F. RIQUET

SAF11 F. ROOSELEER pending


ANNEX B ‐ National Stakeholders Organisation charts 1. DHMI Organisational Chart


2. DGCA Organisational chart


ANNEX C – Implementation Objectives’ Applicability

Objective SESAR

Key Feature

ICAO ASBU

B0 European ATM Masterplan Level 3 Applicability area

AOM13.1

‐ All ECAC States except Albania, Latvia, Luxembourg, Maastricht UAC and

Moldova.

AOM19.1

B0‐FRTO All ECAC States except Armenia, FYROM, Malta, Luxembourg, and

Moldova

AOM19.2

‐ All ECAC States except Armenia, Luxembourg and Moldova

AOM19.3

‐ All ECAC States except Armenia, Luxembourg and Moldova

AOM21.1

B0‐FRTO 25 ECAC States

AOM21.2

‐ All ECAC States except Azerbaijan, Belgium, Luxembourg and the

Netherlands

AOP04.1

B0‐SURF 25 PCP airports, 22 non‐PCP airports

AOP04.2

B0‐SURF 25 PCP airports, 22 non‐PCP airports

AOP05

B0‐ACDM 25 PCP airports, 21 non‐PCP airports

AOP10

‐ 16 PCP Airports

AOP11

‐ 24 PCP airports, 15 non‐PCP airports

AOP12

‐ 25 PCP airports

AOP13

‐ 25 PCP airports

AOP14

‐ Local: Low to medium complexity aerodromes, subject to local needs

ATC02.2 B0‐SNET Additional for ICAO ASBU monitoring: applicable all ECAC States that did

not yet implement it

ATC02.8

B0‐SNET All ECAC States except the Netherlands

ATC02.9

B0‐SNET TMAs, according to local business needs

ATC07.1

B0‐RSEQ 23 PCP Airports, 8 non‐PCP airports

ATC12.1

‐ All ECAC States except Luxembourg

ATC15.1

B0‐RSEQ

EU States except Cyprus, Greece, Lithuania, Luxembourg, Malta, Slovak

Republic, Slovenia. Plus: Bosnia and Herzegovina, Maastricht UAC,

Norway, Switzerland, Turkey

ATC15.2

‐ ACCs within the extended AMAN horizon, including those adjacent to

TMAs serving/associated to PCP airports

ATC16 B0‐ACAS Additional for ICAO ASBU monitoring: applicable to all ECAC States that

did not yet implement it

ATC17

B0‐FICE All ECAC States except Ireland, Slovak Republic and Ukraine

ATC18

‐ Local: Subject to local needs and complexity

COM10

‐ All ECAC States

COM11

‐ All ECAC States


COM12

‐

‐ Area 1 (ANSPs signatories of the NewPENS Common Procurement

Agreement): 33 ANSPs

‐ Area 2 (Other stakeholders): Stakeholders from all ECAC States not part

of Area 1

ENV01

B0‐CDO 59 Airports

ENV02

‐ 47 Airports

ENV03

B0‐CCO Local: Aerodromes subject to local needs and complexity

FCM01 B0‐NOPS Additional for ICAO ASBU monitoring: applicable to all ECAC States that


FCM03

B0‐NOPS All ECAC States

FCM04.1

B0‐NOPS Austria, Belgium, Croatia, Czech Republic, France, Germany, Italy, Poland,

Spain, Switzerland

FCM04.2

B0‐NOPS All EU+ States

FCM05

B0‐NOPS All ECAC States except Armenia, FYROM, Luxembourg, Maastricht UAC

and Moldova

FCM06

B0‐NOPS All EU+ States

FCM07

‐ All EU+ States

FCM08

‐ All ECAC States

FCM09

‐ All ECAC States

INF04 B0‐DATM Additional for ICAO ASBU monitoring: applicable to all ECAC States that


INF07

‐ All ECAC States except Maastricht UAC

INF08.1

‐ All EU+ States

INF08.2

‐ All EU+ States

ITY‐ACID

‐ All EU+ States

ITY‐ADQ

B0‐DATM All EU+ States except FYROM, Georgia and Maastricht UAC

ITY‐AGDL

B0‐TBO All EU+ States except Georgia, Luxembourg and Netherlands

ITY‐AGVCS2

‐ All EU+ States except Georgia and Moldova

ITY‐COTR B0‐FICE Additional for ICAO ASBU monitoring: applicable all EU+ States that did

not yet implement it

ITY‐FMTP

B0‐FICE All ECAC States

ITY‐SPI

B0‐ASUR All EU+ States

NAV03.1

B0‐CDO,

B0‐CCO All ECAC States except Luxembourg, Maastricht UAC and Slovak Republic

NAV03.2

‐ Mandatory for TMAs listed in section 1.2.1 of the Annex of the PCP

Regulation. For all other ECAC TMAs, according to local business needs

NAV10

B0‐APTA All ECAC States except Maastricht UAC

NAV12

‐ Local: TMAs subject to local needs and complexity

SAF11

‐ All ECAC States except Malta


Legend:

Objective’s link to SESAR Key Feature:


High Performing Airport Operations

Advanced Air Traffic Services



ANNEX D ‐ Glossary of Abbreviations

This Annex mostly shows only the Abbreviations that are specific to the LSSIP Turkey.

Other general abbreviations are in the Acronyms and Abbreviations document in http://www.eurocontrol.int/articles/glossaries

Term Description

AF ATM Functionality

FT Fast Track

PCP Pilot Common Project

PDP Preliminary Deployment Programme

S‐AF Sub ATM Functionality

ACAS Airborne Collision Avoidance System

ACC Area Control Centre

AF ATM Functionality

AIS Aeronautical Information Services

AMC Acceptable means of Compliance

ANS Air Navigation Services

ANSP ANS Provider

AOP Airports Operations (Domain)

APV Approach with Vertical Guidance

ARN ATS Route Network

ATC Air Traffic Control

ATCO Air Traffic Controller

ATFM Air Traffic Flow Management

ATM Air Traffic Management

ATS Air Traffic Services

CAD Civil Aviation Department

CDM Collaborative Decision Making

CEATS Central European Air Traffic Services

CFMU Central Flow Management Unit

CNS Communications, Navigation and Surveillance

COM Communications

CTR Control Zone

DFL Division Flight Level

EAD European AIS Database

eAIP European Aeronautical Information Publication

EATM European Air Traffic Management

Local Single Sky ImPlementation LSSIP 2017 - TURKEY · 2019-02-18 · Introduction The Local Single...

Documents

Transcript of Local Single Sky ImPlementation LSSIP 2017 - TURKEY · 2019-02-18 · Introduction The Local Single...