local single sky implementation (lssip) turkey · airports of turkey () is the unique provider of...
Post on 15-Mar-2020
0 Views
Preview:
TRANSCRIPT
Year 2013 ‑ Level 1
EUROCONTROL
Local Single Sky ImPlementation (LSSIP) TURKEY
LSSIP Year 2013 Turkey Released Issue
DOCUMENT IDENTIFICATION SHEET
LSSIP for Turkey
Infocentre Reference: 14/01/07-40
Document Identifier Edition: Year 2013
LSSIP Year 2013 Turkey Edition Date: 23/05/14
LSSIP Focal Point - Cihan SAHIN E-mail: Cihan.SAHIN@dhmi.gov.tr ATC Expert
LSSIP Contact Person - Predrag
VRANJKOVIC E-mail:
predrag.vranjkovic@eurocontrol.int Unit DSS/EIPR
Status Intended for
Working Draft General Public
Draft Agency Stakeholders
Proposed Issue Restricted Audience
Released Issue
Accessible via: Internet (www.eurocontrol.int)
Path: X:\03 LSSIP\1. LSSIP States\Turkey (TR)\Year 2013\Released\LSSIP Year 2013_TR_Released.doc
LINKS TO REFERENCE DOCUMENTS
1. LSSIP Guidance Material: http://www.eurocontrol.int/articles/guidance-material 2. ESSIP Plan Edition 2013: www.eurocontrol.int/pepr 3. ESSIP Report 2012: www.eurocontrol.int/pepr 4. STATFOR Forecasts: www.eurocontrol.int/statfor 5. Acronyms and abbreviations: http://www.eurocontrol.int/articles/glossaries 6. European ATM Master Plan: https://www.atmmasterplan.eu/ 7. LSSIP Documents: http://www.eurocontrol.int/articles/lssip
LSSIP Year 2013 Turkey Released Issue
TABLE OF CONTENTS
Executive Summary ................................................................................................................................. 1
Introduction .............................................................................................................................................. 4
Chapter 1 - National ATM Environment ................................................................................................... 5 1.1 Geographical Scope ................................................................................................................ 5
1.1.1 International Membership ......................................................................................................... 5 1.1.2 Geographical description of the FIR(s) ..................................................................................... 5 1.1.1 Airspace Classification and Organisation ................................................................................. 5 1.2 National Stakeholders .............................................................................................................. 6
1.2.1 Civil Regulator(s) ...................................................................................................................... 7 1.2.2 DHMI ......................................................................................................................................... 8 1.2.3 Airports ...................................................................................................................................... 9 1.2.4 Military Authorities ................................................................................................................... 10 1.2.5 Accident/incident Investigation Body ...................................................................................... 11
Chapter 2 - En-route Traffic and Capacity ............................................................................................. 13 2.1 Evolution of traffic in Turkey .................................................................................................. 13 2.2 ANKARA ACC - Traffic and en-route ATFM delays 2009-2018/19 ....................................... 14 2.3 ISTANBUL ACC - Traffic and en-route ATFM delays 2009-2018/19 .................................... 14 2.4 Summer 2013 performance ................................................................................................... 15 2.5 Planning Period 2014-2018/19 .............................................................................................. 15
Chapter 3 - ESSIP Report recommendations ........................................................................................ 17
Chapter 4 - National Projects ................................................................................................................. 19
Chapter 5 - Regional Co-ordination ....................................................................................................... 21 5.1 Regional coordination projects .............................................................................................. 21
Chapter 6 - ESSIP Objective Implementation ....................................................................................... 22
ANNEXES
LSSIP Year 2013 Turkey 1 Released Issue
Executive Summary
State 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.
ESSIP Objective Implementation
Implementation of ESSIP objectives by DHMI (the service provider) is generally on target. Those objectives that are incomplete and/or late are mainly related to implementation of the full SMART ATM system which is planned for mid 2014.
LSSIP 2013 - Turkey * FOC Date █ Planned implementation date (see legend at the bottom of the table)
State-related ESSIP Objectives
<=
2007
20
08
2009
20
10
2011
20
12
2013
20
14
2015
20
16
2017
20
18
2019
20
20
AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling
[IDP] [E] *
AOM19 Implement Advanced Airspace Management [IDP] [E] *
AOM20 Implement ATS Route Network (ARN) - Version 7 [E] * AOM21 Implementation of Free Route Airspace [IDP]
[E] *AOP03 Improve runway safety by preventing runway incursions * ATC02.2 Implement ground based safety nets - Short Term Conflict
Alert (STCA) - level 2 [E] *
ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2 [E] *
ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 [E] *
ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2 [E] *
ATC07.1 Implement arrival management tools [E] * ATC12 Implement automated support for conflict detection and
conformance monitoring [E] *
ATC15 Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations
[IDP] [E] *
ATC16 Implement ACAS II compliant with TCAS II change 7.1 * ATC17 Electronic Dialogue as Automated Assistance to Controller
during Coordination and Transfer [IDP]
[E] *
COM09 Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP)
[IDP] * COM10 Migrate from AFTN to AMHS * COM11 Implementation of Voice over Internet Protocol (VoIP) in
ATM *FCM01 Implement enhanced tactical flow management services [E] * FCM03 Implement collaborative flight planning [IDP]
[E] *
LSSIP Year 2013 Turkey 2 Released Issue
LSSIP 2013 - Turkey * FOC Date █ Planned implementation date (see legend at the bottom of the table)
FCM04 Implementation of Short Term ATFCM Measures - phase 1 [IDP] [E] *
FCM05 Implementation of interactive rolling NOP [IDP] [E] *
INF04 Implement integrated briefing * ITY-ADQ Ensure quality of aeronautical data and aeronautical
information [E] *
ITY-AGDL Initial ATC air-ground data link services above FL-285 [IDP] [E] *
ITY-AGVCS2 Implement air-ground voice channel spacing requirements below FL195 *
ITY-COTR Implementation of ground-ground automated co-ordination processes [E] *
ITY-FMTP Apply a common flight message transfer protocol (FMTP) [IDP] * ITY-SPI Surveillance performance and interoperability *NAV03 Implementation of P-RNAV [E] * NAV10 Implement APV procedures [IDP]
[E] *
SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements *
SAF11 Improve runway safety by preventing runway excursions *SRC-CHNG Implementation of Safety Oversight of Changes to ATM by
National Supervisory Authorities (NSA) *
SRC-RLMK Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) *
SRC-SLRD Safety Levels and Resolution of Deficiencies *
Airport-related ESSIP Objectives <
=20
07
2008
20
09
2010
20
11
2012
20
13
2014
20
15
2016
20
17
2018
20
19
2020
LTAC-Ankara
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1
[E] * AOP04.2 Implement Advanced Surface Movement Guidance and
Control System (A-SMGCS) Level 2 *LTAI-Antalya
AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual
*
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1
[E] * AOP04.2 Implement Advanced Surface Movement Guidance and
Control System (A-SMGCS) Level 2 *AOP05 Implement Airport Collaborative Decision Making (CDM) [IDP]
[E] *ENV01 Implement Continuous Descent Operations (CDO)
techniques for environmental improvements [IDP] *
ENV02 Implement Collaborative Environmental Management (CEM) at Airports *
LTBA-Istanbul
AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual
*
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1
[E] * AOP04.2 Implement Advanced Surface Movement Guidance and
Control System (A-SMGCS) Level 2 *AOP05 Implement Airport Collaborative Decision Making (CDM) [IDP]
[E] *ENV01 Implement Continuous Descent Operations (CDO)
techniques for environmental improvements [IDP] *
ENV02 Implement Collaborative Environmental Management (CEM) at Airports *
LSSIP Year 2013 Turkey 3 Released Issue
Understanding the Table
Objective Completed No Plan
Objective Partly Completed Missing Data
Objective Planned Not Applicable (State/Airport does not participate in this obj.)
Late
NOTE: The year where the coloured box is placed indicates the ‘Implementation Completion Date’ as stated in the ESSIP for each objective. The colour-code indicates the Local progress with respect to this date.
LSSIP Year 2013 Turkey 4 Released Issue
Introduction
The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a five-year plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the ESSIP and to improve the performance of their national ATM System. The LSSIP document – Year 2013 describes the situation in the State at the end of December 2013.
The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them:
Chapters 1 to 5 present the key players in the State, and sets the institutional and geographical scenes to help the reader understand the specifics of the State and interpret the rest of the document correctly. It also presents a short description of the main national and regional projects in which the national Stakeholders are involved.
Chapter 6 contains high-level information on progress and plans of each ESSIP Objective. The information for each ESSIP 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.
Note: Chapter 6 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 ESSIP 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 ESSIP.
LSSIP Year 2013 Turkey 5 Released Issue
Chapter 1 - National ATM Environment
1.1 Geographical Scope
1.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
European Common Aviation Area NA
EASA NA
ICAO 1945
NATO 1952
1.1.2 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.
1.1.1 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.
LSSIP Year 2013 Turkey 6 Released Issue
1.2 National Stakeholders
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 Authorities 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 Authorities
• School of Civil Aviation (Aviation Experts)
• Turkish Airline Pilots’ Association (TALPA)
• Air Traffic Controllers Association of Turkey
• Other related stakeholders
LSSIP Year 2013 Turkey 7 Released Issue
1.2.1 Civil Regulator(s)
1.2.1.1 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
Establishment of Tolerable Safety Levels DGCA The Law No: 2920 and 5431
Safety Performance Monitoring 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
1.2.1.2 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.
LSSIP Year 2013 Turkey 8 Released Issue
1.2.2 DHMI
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 (www.dhmi.gov.tr)
Governance: Governmental department Ownership: 100% State owned
Services provided Y/N Comment
ATC en-route Y
ATC approach Y
ATC Airport(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
Number of air traffic controllers
ACC 385
APP 265
TWR 278
Annual Report published: Y http://www.dhmi.gov.tr/dosyalar/annualreport/2012/ANNUAL_REPORT_2012.pdf
www.dhmi.gov.tr
Organisation chart is shown in Annex B.
1.2.2.1 ATC system in use
Specify the manufacturer of the ATC system currently in use: Selex ES
Major upgrade1 of the ATC system is performed or planned? 2014
1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))
LSSIP Year 2013 Turkey 9 Released Issue
1.2.2.2 ATC units
En-route air navigation services throughout Turkish Airspace from two Area Control Centers located in Ankara and İstanbul. İzmir Approach Control Unit also provides area control service for southern part of İstanbul FIR. There are 24 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:
ATC Unit Number of sectors Associated FIR(s) Remarks
En-route TMA
Ankara ACC 10 2 Ankara The sector structure is currently stable with the Interim SMART system introduced. Ultimately there will be single pan-Turkey ACC located in Ankara
Istanbul ACC 4 7 Istanbul Izmir ACC 4 2
Antalya APP 6 Ankara
Dalaman APP 3 İstanbul
1.2.3 Airports
1.2.3.1 General information
Turkey has 55 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 and İstanbul Hezarfen Airports.
1.2.3.2 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.
LSSIP Year 2013 Turkey 10 Released Issue
1.2.4 Military Authorities
The military authorities also play a major role in managing the Turkish Airspace especially with regard to FUA. The regulation of Military Aviation (Turkish Air Force) comes under the Ministry of Defence. Military ATC is entirely separated from Civil ATC, although very good civil/military co-ordination is maintained. Co-ordination between the military authorities 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.
The EUROCONTROL Flexible Use of Airspace (FUA) concept has not been applied, since the Turkish Military and DHMI have their own alternative FUA concept which is considered more suitable for the local geo-political situation. The Turkish Military, through their alternative FUA concept has shown much flexibility in relinquishing unused military airspace to the DHMI when no military traffic is foreseen (evenings, weekends, etc.). In order to increase the capacity of Turkish airspace during the period up to the implementation of the SMART system, DHMI and the Military Authorities are planning increased coordination/cooperation using the alternative Turkish FUA concept which encompasses these same lines of action in a different manner, more suited to the local geo-political environment.
The military regulatory, service provision and user role within ATM is detailed below.
1.2.4.1 Regulatory role
Regulatory framework and rule-making
Oversight
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 Coordination Y OAT/GAT Coordination 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 (only military pilots) Y ESARR applicability N
Aircrew Licensing N
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 N/A National Military AIP N
EUROCONTROL eAIP N EUROCONTROL eAIP N
Other N/A Other: N/A
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: N/A-
LSSIP Year 2013 Turkey 11 Released Issue
1.2.4.2 Service Provision role
1.2.4.3 User role
1.2.4.4 Flexible Use of Airspace (FUA)
1.2.5 Accident/incident Investigation Body
1.2.5.1 Technical investigations
From DHMI annual report: 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 “Reporting and Assessment of ATM Related Safety Occurrences” which was aligned with the EC directives on investigations of civil aviation accidents.
OAT GAT
Services Provided: Services Provided:
En-Route N/A 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 Turkish State Meteorological Service
N
SAR Y
By the Turkish Air Force for both OAT and GAT
SAR By the Turkish Air Force for both OAT and GAT
Y
TSA/TRA monitoring Y FIS Y
Other: Security Services Other: Security Services
Additional Information: Additional Information:
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
FUA Level 2 implemented: N
FUA Level 3 implemented: N
LSSIP Year 2013 Turkey 12 Released Issue
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 Authorities
School of Civil Aviation (Aviation Experts)
Turkish Airline Pilots’ Association (TALPA)
Air Traffic Controllers Association of Turkey
Other related stakeholders
The commission is formed from experts with sufficient qualifications. An investigation team is formed for each incident to investigate the incident, determine the causal factor(s) and propose necessary measures to avoid the repetition of such incidents in the future (e.g. training, new procedures, etc.). The results of the investigations are reported to DGCA. This procedure is realized according to directive SHY65-02 “Reporting and Assessment of ATM Related Safety Occurrences” which was aligned with the EC directives on investigations of civil aviation accidents.
1.2.5.2 Collection, Evaluation & Processing of Data
In order to collect, evaluate, process and store all the relevant information, the Flight Safety Commission is planning to use the tools developed in the frame of the “European Co-ordination Centre for Aviation Incidents Reporting System: (ECCAIRS).
1.2.5.3 Civil-Military Accidents/Incidents
In the case of incidents/accidents concerning both military and civil aircraft a joint commission is set up under existing legislation. See section 1.2.5.1.
LSSIP Year 2013 Turkey 13 Released Issue
Chapter 2 - En-route Traffic and Capacity
2.1 Evolution of traffic in Turkey
Turkey - Annual IFR Movements
0
200000
400000
600000
800000
1000000
1200000
1400000
1600000
1800000
2009 A 2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 F
IFR
flig
hts
IFR movements - Actuals
IFR movements - Baseline forecast
IFR movements - High forecast
IFR movements - Low forecast
Turkey - Distribution (Ref. year 2012)
International Dep/Arr
44%
Domestic flights 26%
Overflights 30%
A = ActualF = Forecast
2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 FH 8,1% 7,7% 7,0% 6,4% 5,9% 6,7% 6,5%B 12,6% 7,6% 2,6% 7,7% 6,1% 4,9% 5,1% 5,1% 5,2% 5,3%L 7,3% 4,2% 2,9% 3,4% 3,4% 3,5% 3,6%
ESRA B 0,8% 3,1% -2,4% -0,9% 1,4% 2,6% 2,7% 2,2% 2,5% 2,5%
STATFOR Medium-Term Forecast (September 2013)IFR flights yearly growth
Turkey
2013
Traffic in Turkey increased by 7.8% during Summer 2013 (May to October), when compared to the same period during 2012.
2014-2018/19
The STATFOR medium-term forecast (MTF) predicts an average annual increase between 3.5% and 6.7% for Turkey during the 5 year planning cycle, with a baseline growth of 5.3%.
LSSIP Year 2013 Turkey 14 Released Issue
2.2 ANKARA ACC - Traffic and en-route ATFM delays 2009-2018/19
LTAAACC - Traffic and en-route ATFM delays
0
500
1000
1500
2000
2500
3000
3500
IFR
flig
hts
(D
aily
Ave
rag
e)
0.0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
En
rou
te D
ela
y (m
inu
tes
pe
r fli
gh
t)
Peak Day Traff ic 2163 2336 2685 2445 2587
Summer Traff ic 1803 1981 2186 2193 2312
Yearly Traffic 1600 1760 1914 1928 2014
Summer Traff ic Forecast 2424 2554 2684 2818 2960 3108
High Traffic Forecast - Summer 2473 2662 2852 2972 3008 3125
Low Traffic Forecast - Summer 2385 2456 2542 2634 2727 2829
Summer enroute delay (all causes) 0.1 0.1 0.3 0.2 0.1
Yearly enroute delay (all causes) * 0.1 0.1 0.2 0.2 0.1
2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019
2.3 ISTANBUL ACC - Traffic and en-route ATFM delays 2009-2018/19
LTBBACC - Traffic and en-route ATFM delays
0
500
1000
1500
2000
2500
3000
3500
4000
IFR
flig
hts
(D
aily
Ave
rag
e)
0.0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
En
rou
te D
ela
y (m
inu
tes
pe
r fli
gh
t)
Peak Day Traff ic 2341 2623 2865 2821 3000
Summer Traff ic 1943 2169 2375 2418 2613
Yearly Traffic 1655 1842 2003 2050 2187
Summer Traff ic Forecast 2740 2887 3034 3186 3346 3514
High Traffic Forecast - Summer 2796 3010 3225 3361 3402 3535
Low Traffic Forecast - Summer 2696 2777 2875 2979 3084 3200
Summer enroute delay (all causes) 0.0 0.0 0.1 0.0 0.0
Yearly enroute delay (all causes) * 0.0 0.0 0.1 0.0 0.0
2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019
LSSIP Year 2013 Turkey 15 Released Issue
2.4 Summer 2013 performance
Traffic Evolution 2013 Capacity Baseline
En-route Delay (min/flight) Capacity
gap Optimum All reasons Without weather & special events
Ankara: + 5.4%
Istanbul: +8.1%
Ankara: 150 (+7%)
Istanbul: 138 (+3%)
Izmir: 68 (0%)
0.2 0.1 0.1 No
Average enroute delay per flight in Ankara ACC remained at 0.1 minutes per flight in Summer 2013. Reason for the delay was 9% ATC Capacity and 90% Other, due to capacity reductions at the Iraki interface.
Capacity Plan : Achieved Comments
Improved civil/military coordination Yes
ATS route structure development Yes
Additional controllers (45 per year for en-route) Yes
Enhanced management of restricted and danger areas (activation by NOTAM)
Yes
Transition to SMART and new Ankara ACC planned for November 2013, including transition of all Turkish airspace above FL 235 to Ankara ACC
No Transition to SMART will start in 2014
Maximum configuration: 18 sectors Yes
Summer 2013 performance assessment
Ankara: The capacity baseline of 150 was calculated with ACCESS, representing the capacity offered during the measured period. During the same period, the average peak 1 hour demand was 146 and the peak 3 hour demand was 134. A maximum configuration of 9 sectors was opened. Istanbul: The capacity baseline of 138 was calculated with ACCESS, representing the capacity offered during the measured period. During the same period, the average peak 1 hour demand was 136 and the peak 3 hour demand was 125. A maximum configuration of 3 sectors was opened. Izmir: The ACC capacity baseline was assessed to be at the same level as in Summer 2012. During the same period, the average peak 1 hour demand was 57 and the peak 3 hour demand was 51. A maximum configuration of 5 sectors was opened, including APP sectors.
2.5 Planning Period 2014-2018/19
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.
The 2014-2018/19 summer capacity profile and delay breakdown has been derived according to the following parameters:
2014: capacity requirement profiles based on the delay breakdown per ACC as provided in January
2011
2015-2018/19: Reference value based on the breakdown of a yearly European delay target of 0.5
min/flight
2014 2015 2016 2017 2018 20190.13 0.16 0.16 0.15 0.15 0.150.19 0.23 0.23 0.23 0.22 0.22
En-route ATFM delay breakdown - Reference ValuesLTAACTA
AnnualSummer
H 212 0% 220 4% 235 7% 248 6% 264 6% 278 5%Ref. 212 0% 212 0% 223 5% 233 4% 246 6% 258 5%
L 212 0% 212 0% 212 0% 215 1% 223 4% 233 4%C/R 212 0% 212 0% 222 5% 233 5% 244 5% 260 7%
Capacity ProfilesProfiles (hourly movements and % increase over previous year)
2015 2016 2017 2018ACC
2013 baseline 2014
LTAACTANEW
212
2019
LSSIP Year 2013 Turkey 16 Released Issue
Capacity Plan
Year 2014 2015 2016 2017 2018 2019
Measures planned
Improved civil/military coordination
ATS route structure development
Additional controllers (45 per year for en-route)
Stepped implementation of direct/free route
operations above FL290
New Ankara ACC (Max 25 physical sectors + 5 optional) -
Implementation of SMART system
RTS of Turkish airspace –
Autumn 2015
Mode S
Reconfigurationof ACC/APP with DFL 235
and 335
Gradual upper airspace re-sectorisation (20 to 25 sectors +
FL235)
Significant Events
Transition to SMART and new Ankara ACC, including transition of all Turkish airspace above FL
235 to Ankara ACC
New runway and ground
infrastructure at LTFJ and
new airport in Istanbul
43 new parking positions at LTBA and
taxiway connections
Max sectors 20 20 25 25 25 25
Capacity increase p.a.
Capacity: 212 10% 6% 6% 6% 6%
Reference profile
Capacity: 212 0% 5% 4% 6% 5%
Additional information
As from November 2014, Istanbul and Izmir will be serving for approach control up to 235. En-route service will be under responsibility of Ankara ACC. SMART: - Training: no extra delays are expected - Transition plan: November 2013 / January 2014: Complete provisional/technical acceptance tests Spring 2014 / Autumn 2014: Technical transition and shadow mode operations, maintaining normal operations, no delays expected November 2014: Cut over – simultaneous transfer to the new ATM system in Ankara ACC and in Ankara, Istanbul, Izmir, Antalya, Dalaman, Bodrum APPs. Transfer of the upper airspace above FL235 to Ankara ACC. November 2014 / February 2015: Transition period. Further details on the transition period will be discussed as from January 2014.
LTAANEW - Reference capacity profile and alternative scenarios
0
50
100
150
200
250
300
350
Cap
acit
y p
rofi
le (
mo
vem
ents
per
ho
ur)
2014-2019 Reference Capacity Profile 212 212 223 233 246 258
Capacity Profile - Current Routes 212 212 222 233 244 260
Capacity Profile - High 212 220 235 248 264 278
Capacity Profile - Low 212 212 212 215 223 233
Capacity Baseline 198 212
2014 - 2019 Plan 212 233 247 262 278 295
2012 2013 2014 2015 2016 2017 2018 2019
2014-2018/19 Planning Period Outlook
No problems are foreseen for Ankara during the planning cycle.
LSSIP Year 2013 Turkey 17 Released Issue
Chapter 3 - ESSIP Report recommendations
Recommendations issued from the ESSIP Report for 2012 applicable to Turkey for all items that require corrective actions and improvements ahead of the 2013 reporting exercise.
Number Recommendation Ownership
REC-2012-03 To ensure that all Stakeholders report the expected completion dates as defined in their National business plans.
All States
Response: All reported completion dates are in-line with national plan.
Number Recommendation Ownership
REC-2012-05 To ensure correct application of LSSIP guidance material and toimplement the results of mandatory LSSIP in-cycle check.
All States
Response: Turkey will correctly apply LSSIP guidance material in coordination with Agency CP and implement the results of the mandatory in cycle check.
Number Recommendation Ownership
REC-2012-08
Airports to ensure appropriate efforts to implement all relatedactions in the ESSIP objective AOP05, but particularlystakeholder lines of action APO05 and/or APO06, in coordinationwith the Network Manager.
EKCH, LFLL, LGKR, LGTS, LHBP, EIDW, LPPT, LEBL, LEPA, ESSB, LTAI, EGGW.
Response: Antalya Airport (LTAI) is in process of implementing AOP05 objective. The objective isplanned to be implemented by 12/2015. Although some actions are currently late (APO05), the overallobjective will be implemented on time within the overall objective FOC date.
Number Recommendation Ownership
REC-2012-09 ANSPs to ensure appropriate efforts to implement all related actions in the ESSIP objective AOP05, particularly stakeholderlines of action ASP04 and ASP05.
CH (LSGG only), DK, ES, FR (except LFPG), GR, HU, PL, PT, SE (ESSB only), TR, UK.
Response: Both Turkish airports implementing AOP05 ESSIP objective (Istambul and Ankara Airports) plan to implement this improvement before overall objective FOC date (01/2016).
Number Recommendation Ownership
REC-2012-22 States are encouraged to speed up the AFP implementation and to schedule AFP testing with Network Manager
All States
Response: New SMART system will have this capability - to be implemented early 2014.
Number Recommendation Ownership
REC-2012-24 States are encouraged to take into consideration the deployment of ASM systems if it is not already planned.
EE, ES, SK, HU, GR, TR, GE, AZ
Response: Technically current/future (SMART) ATM systems are capable of executing ASM systems inour airspace. The implementation of ASM systems is planned.
LSSIP Year 2013 Turkey 18 Released Issue
Number Recommendation Ownership
REC-2012-27 Airports are encouraged to establish performance committees and implement information sharing and performance reporting processes in line with A-CDM guidelines (AOP05 objective).
Airports in applicability area reported other than
“completed”
Response: See reply on REC-2012-08 and 09.
Number Recommendation Ownership
REC-2012-40 ANSPs are encouraged to publish more APV routes. All ECAC ANSPs
Response: New RNP APCH procedures and Standard Instrument Departure Procedures based on RNP 1 were implemented for VAN Airport and have been in use since 13 December 2012. Studies to design RNAV SIDs / STARs and RNP APCH Procedures for some Major / Constrained Airports in Turkey have also been started and implementation of these procedures will be realized in 2014.
LSSIP Year 2013 Turkey 19 Released Issue
Chapter 4 - National Projects
Name Schedule Description – Scope Status Link with
European Master Plan
Expected Contribution to the Key Performance Areas2
SMART 2006-2014 The SMART Project (Systematic Modernisation of ATM Resources in Turkey) brings together a number of sub projects and strategies in to one global project.
A pan-Turkish ACC located near Esenboğa Airport, near Ankara,
The replacement or extension of the major airport APPs in Turkey (the APP of Ankara will be in the ACC Building), also part of TAMP,
A Building Programme for the new ACC at Ankara,
Replacement or refurbishment of the APP buildings,
A new Tower (TWR) at Antalya and Istanbul-Atatürk,
A state-of-the-art RDPS/FDPS/ODS System. The supply of which will be together with the new Ankara ACC Building (turnkey project).
To shorten the time to the operation of the new SMART system, DHMI are planning to implement as far as possible, an off-the-shelf (OTS) system with a minimum of customisation.
ATC02.2
ATC02.5
ATC02.6
ATC02.7
ATC12
ATC17
COM09
FCM01
FCM03
The new system will positively affect safety and it will enable Turkey to achieve higher capacity.
2 Capacity, safety, cost-efficiency and environment – as defined in Recital 2 of Regulation (EU) No 691/2010.
LSSIP Year 2013 Turkey 20 Released Issue
Name Schedule Description – Scope Status Link with
European Master Plan
Expected Contribution to the Key Performance Areas2
Additional functionalities may be added at a later date (after SMART implementation).
AMAN 2009-2014 AMAN is management tool to arrange the sequence of arrivals. No extension to en-route is planned.
It will be planned to be operational for Atatürk Airport initially.
ATC07.1 Safety benefits and more capacity in TMA.
ARTAS 2006-2014 The main RDP will be ARTAS in SMART project and 3 ARTAS units will be located in Turkey.
It will be operational within SMART project.
- Safety benefits.
RADARS replacement
2009-Q1 2013 18 Mode S and 5 PSR Radars have been installed Completed - Capacity gain and safety benefits.
A-SMGCS II 2008-2010 Advanced Surface Movement and Guidance Level II System is running in Antalya, Esenboğa and Atatürk Airports.
Completed AOP04.1
AOP04.2
Increasing safety and capacity at the airport.
LSSIP Year 2013 Turkey 21 Released Issue
Chapter 5 - Regional Co-ordination
5.1 Regional coordination projects
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 and Russian Federation 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 at Esenboğa Airport.
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 Ukrain 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.
LSSIP Year 2013 Turkey 22 Released Issue
Chapter 6 - ESSIP Objective Implementation
(*) Objective Scope Code: (**) Objective/Stakeholder Progress Code:
ECAC Completed No Plan
EU+ Partly Completed Not Applicable
Multi-N Planned Missing Data
APT Late
AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling (By:12/2018)
[IDP] [Essential]
No Plan
OI Step(s): AOM‐0202 [E], AOM‐0301 The Military cannot implement this objective completely until appropriate legislation is passed. Meantime mature and robust procedures are already in force regarding the handling and interface of OAT/GAT operations
‐
REG (By:12-2018) No current plan until appropriate legislation is passed. No Plan
‐
ASP (By:12-2018)
No current plan until appropriate legislation is passed. Implementation of the objective will take place in parallel with the military
No Plan
‐
MIL (By:12-2018)
The Military cannot implement this objective completely until appropriate legislation is passed. Meantime mature and robust procedures are already in force regarding the handling and interface of OAT/GAT operations
Not Applicable
‐
AOM19 Implement Advanced Airspace Management (By:12/2016) [IDP]
[Essential] No Plan
OI Step(s): AOM‐0201, AOM‐0202 [E], AOM‐0205 [E], AOM‐0401 [E], DCB‐0203 [E]
This objective will be evaluated and implemented by the 2015 completion date. However, for this LSSIP cycle resources will not be available.
12/2015
ASP (By:12-2015)
This objective will be evaluated and implemented by the 2015 completion date. However, for this LSSIP cycle resources will not be available.
No Plan
12/2015
MIL (By:12-2015) No plan.
No Plan
12/2015
AOM20 Implement ATS Route Network (ARN) - Version 7 (By:10/2013)
[Essential] Completed
OI Step(s): AOM‐0205 [E], AOM‐0401 [E], AOM‐0402, AOM‐0504 [E], AOM‐0801 [E], AOM‐0802 [E]
All of the routes comfirmed by our organizations have been implemented 10/2013
ASP (By:10-2013)
Altough the amendment of ATS route network is an on going process, implementation of airspace changes was completed.
Completed
10/2013
MIL (By:10-2013) ‐
Not Applicable
‐
AOM21 Implementation of Free Route Airspace (By:12/2017) [IDP]
[Essential] Planned
OI Step(s): AOM‐0401 [E], AOM‐0402
Implementation of free route airspace is planned for 2016‐ 2018 period. 12/2016 REG (By:12-2017) Implementation of free route airspace is planned for 2016‐ 2018 period.
Planned
12/2016
ASP (By:12-2017) Implementation of free route airspace is planned for 2016‐ 2018 period.
Planned
12/2016
MIL (By:12-2017) Implementation of free route airspace is planned for 2016‐ 2018 period.
Planned
12/2016
LSSIP Year 2013 Turkey 23 Released Issue
AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual (By:12/2013)
Late
OI Step(s): AO‐0305, AUO‐0701
LTAI - AntalyaAntalya has an ongoing ACE study in conjunction with EUROCONTROL. Slot times are issued to all departures, including non‐scheduled and VFR flights.
12/2014
ASP (By:12-2011)
Studies to implement CDM at Antalya Airport will be commenced again after finalization of ‐stanbul CDM project.
Late
AYT Capacity Enhancement
Exercise 12/2014
APO (By:12-2011)
A second ACE data collection was made in Q3 2010 and analysed by EUROCONTROL. Recommendations reported during Q4 2010 or Q1 2011. ACE report recommendations were implemented with the exception of implementation of CDM
Completed
AYT Capacity Enhancement
Exercise 12/2012
AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual (By:12/2013)
Completed
OI Step(s): AO‐0305, AUO‐0701
LTBA - IstanbulAn ACE study was completed at Istanbul Atatürk Airport in conjunction with EUROCONTROL in 2009. All of the recommendations contained in the final report have been implemented except the implementation of CDM. DHMI has taken over the responsibility for allocating slot times from 17 June.
12/2012
ASP (By:12-2011)
ATC training support has been requested through EUROCONTROL to facilitate reduced arrival and departure separations and an increased movement rate of 5‐7 globally per hour. RTS was conducted during Nov.‐Dec. 2012. DHMI allocates slot times which are issued to all departures, including non‐scheduled and VFR flights.
Completed
12/2012
APO (By:12-2011)
All infrastructure changes and improvements have been made as recommended in the ACE report. Rwy 05/23 has been re‐surfaced and restored to operational use at the end of June 2010.
Completed
12/2012
LSSIP Year 2013 Turkey 24 Released Issue
AOP03 Improve runway safety by preventing runway incursions (By:12/2013)
Completed
OI Step(s): AO‐0101
Local Runway Safety Teams (which report to the DHMI ATM Safety Commission) have been set up at all airports and a reporting procedure and dissemination structure is in place. All reports are sent to DHMI HQ and DGCA, but administrative procedures still preclude transfer of same to EUROCONTROL. Ab‐initio and recurrent training in line with EAPPRI guidelines is ongoing. TWR Staff are kept fully aware of all runway incursion matters. Assessment of correct use of the standard ICAO phraseology and read‐back procedures is performed regularly. Investigation related findings are suitably debriefed. All Aerodromes are regularly checked for compliance with ICAO Annex 14.
‐
REG (By:12-2013)
The DGCA oversees the implementation of EAPPRI 2.0 requirements at airports and audits procedures on a regular basis at major and other randomly selected airports. All reports are sent to DHMI HQ and DGCA, but administrative procedures still preclude transfer of same to EUROCONTROL. .
Completed
DHMI/CAA ‐
ASP (By:12-2013)
Local Runway Safety Teams (which report to the DHMI ATM Safety Commission) have been set up at all airports and a reporting procedure and dissemination structure is in place. All reports are sent to DHMI HQ and DGCA, but administrative procedures still preclude transfer of same to EUROCONTROL. Ab‐initio and recurrent training in line with EAPPRI guidelines is ongoing. TWR Staff are kept fully aware of all runway incursion matters. Assessment of correct use of the standard ICAO phraseology and read‐back procedures is performed regularly. Investigation related findings are suitably debriefed. All airports are regularly checked for compliance with ICAO Annex 14.
Completed
‐
MIL (By:12-2013)
The Turkish Airforce has adopted the EAPPRI 2.0 as a basis for training and operational procedures in particular at military airports that are available for civil use. All reports involving civil aircraft are sent to DHMI HQ and the DGCA. ATC personnel are kept aware of all runway incursion matters. TWR Staff are kept fully aware of all runway incursion matters. Assessment of correct use of the standard ICAO phraseology and read‐back procedures is performed regularly. Investigation related findings are suitably debriefed. All Aerodromes are regularly checked for compliance with ICAO Annex 14; however, joint user airports may have signs and markings conforming to NATO standards.
Completed
Military Authorities
‐
APO (By:12-2013)
Local Runway Safety Teams (which report to the DHMI ATM Safety Commission) have been set up at all airports and a reporting procedure and dissemination structure is in place. All reports are sent to DHMI HQ and DGCA, but administrative procedures still preclude transfer of same to EUROCONTROL. Ab‐initio and recurrent training in line with EAPPRI guidelines is ongoing. TWR Staff are kept fully aware of all runway incursion matters. Assessment of correct use of the standard ICAO phraseology and read‐back procedures is performed regularly. Investigation related findings are suitably debriefed. All airports are regularly checked for compliance with ICAO Annex 14.
Completed
Airport/DHMI/CAA
‐
LSSIP Year 2013 Turkey 25 Released Issue
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 (By:12/2011)
[Essential] Completed
OI Step(s): AO‐0201 [E]
LTAC - AnkaraAnkara implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2010) No plan to implement. Not applicable in TR.
Not Applicable
‐
ASP (By:12-2011) Ankara implemented A‐SMGS Level 1 and 2 in June 2010.
Completed
06/2010
MIL (By:12-2010) No plan to implement. Not applicable in TR.
Not Applicable
‐
APO (By:12-2010) Drivers have received instruction on the system.
Completed
06/2010
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 (By:12/2011)
[Essential] Completed
OI Step(s): AO‐0201 [E]
LTAI - AntalyaAntalya implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2010) Not applicable in TR.
Not Applicable
‐
ASP (By:12-2011)
Antalya implemented A‐SMGS Level 1 and 2 in June 2010. All training and development of procedures has been completed.
Completed
06/2010
MIL (By:12-2010) Not applicable in TR.
Not Applicable
‐
APO (By:12-2010) Drivers have received instruction on the system
Completed
06/2010
AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 (By:12/2011)
[Essential] Completed
OI Step(s): AO‐0201 [E]
LTBA - IstanbulIstanbul implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2010) Not applicable in TR.
Not Applicable
‐
ASP (By:12-2011)
Istanbul implemented A‐SMGS Level 1 and 2 in June 2010. All training and development of procedures has been completed.
Completed
06/2010
MIL (By:12-2010) Not applicable in TR.
Not Applicable
‐
APO (By:12-2010) Drivers have received instruction on the system.
Completed
06/2010
AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 (By:12/2017)
Completed
OI Step(s): AO‐0102
LTAC - AnkaraAnkara implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2017) Not applicable in TR.
Not Applicable
‐
ASP (By:12-2017) Ankara implemented A‐SMGS Level 1 and 2 in June 2010.
Completed
06/2020
APO (By:12-2017) Drivers have received instruction on the system.
Completed
06/2010
LSSIP Year 2013 Turkey 26 Released Issue
AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 (By:12/2017)
Completed
OI Step(s): AO‐0102
LTAI - AntalyaAntalya implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2017) Not applicable in TR.
Not Applicable
‐
ASP (By:12-2017) Antalya implemented A‐SMGS Level 1 and 2 in June 2010.
Completed
06/2010
APO (By:12-2017) Drivers have received instruction on the system.
Completed
06/2010
AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 (By:12/2017)
Completed
OI Step(s): AO‐0102
LTBA - IstanbulIstanbul implemented A‐SMGS Level 1 and 2 in June 2010. 06/2010 REG (By:12-2017) Not applicable in TR.
Not Applicable
‐
ASP (By:12-2017) Istanbul implemented A‐SMGS Level 1 and 2 in June 2010.
Completed
06/2010
APO (By:12-2017) Drivers have received instruction on the system.
Completed
06/2010
AOP05 Implement Airport Collaborative Decision Making (CDM) (By:01/2016)
[IDP] [Essential]
Planned
OI Step(s): AO‐0501 [E], AO‐0601 [E], AO‐0602 [E], AO‐0603 [E], DCB‐0301 [E], DCB‐0302 [E]
LTAI - AntalyaA draft MoU has been circulated to key stakeholders. Following the developments of Istanbul CDM studies, studies for Antalya will be focused.
12/2015
ASP (By:01-2016)
DHMI has initiated action to implement this objective. A draft MoU has been developed and circulated to key stakeholders.
Planned
12/2015
MIL (By:01-2016) Not applicable
Not Applicable
‐
APO (By:01-2016)
DHMI has initiated action to implement this objective. A draft MoU has been developed and circulated to key stakeholders
Planned
12/2015
AOP05 Implement Airport Collaborative Decision Making (CDM) (By:01/2016)
[IDP] [Essential]
Planned
OI Step(s): AO‐0501 [E], AO‐0601 [E], AO‐0602 [E], AO‐0603 [E], DCB‐0301 [E], DCB‐0302 [E]
LTBA - IstanbulA MoU has been agreed and signed. Working groups have been formed. CDM platform has been established and tests are going on.
10/2014
ASP (By:01-2016)
A MoU has been agreed and signed. Working groups have been formed. CDM platform has been established and tests are going on.
Partly Completed
10/2014
MIL (By:01-2016) Not applicable
Not Applicable
‐
APO (By:01-2016)
A MoU has been agreed and signed. Working groups have been formed. CDM platform has been established and tests are going on.
Partly Completed
10/2014
LSSIP Year 2013 Turkey 27 Released Issue
ATC02.2 Implement ground based safety nets - Short Term Conflict Alert (STCA) - level 2 (By:01/2013)
[Essential] Late
OI Step(s): CM‐0801 [E]
Is a functionality included as part of the Interim 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.
12/2014
REG (By:01-2013)
STCA implementation/procedures will be audited and approved using the EUROCONTROL specification for STCA when human resources permit.
Late
12/2014
ASP (By:01-2013)
STCA is a functionality included as part of the Interim SMART system. The STCA is in accordance with EUROCONTROL specifications.
Late
SMART 12/2014
MIL (By:01-2013)
Military equipment is STCA capable. However, due to the dynamic nature of military operations the STCA function is disabled to prevent unnecessary alerts including at joint user airports.
Not Applicable
Military Authorities
‐
ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2 (By:12/2016)
[Essential] Planned
OI Step(s): CM‐0801 [E]
APW level 2 will be implemented with the SMART system which is planned for 10/2014 10/2014 ASP (By:12-2016) APW will be implemented with the SMART system.
Planned
10/2014
MIL (By:12-2016) Not applicable
Not Applicable
‐
ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 (By:12/2016)
[Essential] Planned
OI Step(s): CM‐0801 [E]
MSAW will be implemented with the SMART system. 10/2014 ASP (By:12-2016) MSAW will be implemented with the SMART system.
Planned
10/2014
MIL (By:12-2016)
Military system MSAW capable but this system is not compatible with military operations and is therefore disabled.
Not Applicable
‐
ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2 (By:12/2016)
[Essential] Planned
OI Step(s): CM‐0801 [E]
APM, in line with EUROCONTROL specifications, will be implemented at Istanbul, Esenboga, Antalya, Dalaman, Bodrum and Izmir airports in parallel with SMART.
10/2014
ASP (By:12-2016)
APM will be implemented in parallel with SMART at Istanbul, Esenboga, Antalya, Dalaman, Bodrum and Izmir airports.
Planned
10/2014
MIL (By:12-2016)
Military units have APM functionality but due to the dynamic nature of OAT operations this functionality is only enabled at airports that serve GAT.
Completed
12/2008
ATC07.1 Implement arrival management tools (By:12/2015) (Outside Applicability Area)
[Essential] Planned
OI Step(s): TS‐0102 [E]
Tender for AMAN has already been done for Atatürk and S.Gölçen Airports. AMAN will be operational at first quarter 2014.
04/2014
ASP (By:12-2015)
Tender for AMAN has already been done for Atatürk and S.Gölçen Airports. AMAN will be operational at first quarter 2014. Preparation of technical aspects for Antalya Airport AMAN will be started beginning of 2014.
Planned
04/2014
LSSIP Year 2013 Turkey 28 Released Issue
ATC12 Implement automated support for conflict detection and conformance monitoring (By:12/2016)
[Essential] Planned
OI Step(s): CM‐0202 [E], CM‐0203 [E]
Formal collaboration with EUROCONTROL commenced in February 2009. Phase 1 is completed and Phase 2 was agreed with a planned timescale of November 2009 to July 2010 and includes documenting the working methods, assessing the accuracy of the TP, developing the local operational concept for using FASTI tools and reviewing the requirements for TP/MTCD.
10/2014
REG (By:12-2016) Regulatory actions will be defined and achieved as the project matures.
Planned
SMART 10/2014
ASP (By:12-2016)
Phase 1 completed. Phase 2 commenced in November 2009 and due for completion in July 2010. Phase 2 includes documenting the working methods, assessing the accuracy of the TP, developing the local operational concept for using FASTI tools and reviewing the requirements for TP/MTCD.
Planned
SMART 10/2014
ATC15 Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations (By:12/2017)
[IDP] [Essential]
Planned
OI Step(s): TS‐0305 [E]
The implementation of AMAN is planned for Istanbul Atatürk and S.Gökçen Airports. 01/2017 REG (By:12-2017) Necessary measures will be taken after the implementation of AMAN.
Planned
01/2017
ASP (By:12-2017)
The implementation of AMAN is planned for Istanbul Atatürk and S.Gökçen Airports.
Planned
04/2014
ATC16 Implement ACAS II compliant with TCAS II change 7.1 (By:12/2015)
Partly Completed
Enabler(s): CTE‐S11a
The training plan for ACAS II version 7.1 has been developed.ATC units have been monitoring the performance of ACAS. Certain type of the military transport aircraft have been equipped with ACAS.
01/2015
REG (By:12-2015) Necessary actions will be taken before 2015.
Planned
01/2015
ASP (By:03-2012)
The training plan for ACAS II version 7.1 has been developed.ATC units have been monitoring the performance of ACAS.
Completed
03/2012
MIL (By:12-2015)
Certain type of the transport aircraft have been equipped with ACAS. The tarining has been completed.
Partly Completed
01/2015
ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer (By:12/2018)
[IDP] [Essential]
Planned
OI Step(s): CM‐0201 [E]
All functions will be in use with SMART project. 10/2014
REG (By:12-2018)
Necessary coordination will be completed before SMART project will be functional.
Planned
10/2014
ASP (By:12-2018) All functions will be in use with SMART project.
Planned
10/2014
COM09 Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP) (By:12/2014)
[IDP]
Completed
Enabler(s): CTE‐C11a, CTE‐C11b
Turkey has no X.25 connection. Radar and voice connections are using TDM point to point connection. AFTN/CIDIN/AMHS and other ground data connections are already using IP based connections.
12/2008
REG (By:12-2010) No Regulatory action taken. IP based connections in use.
Completed
12/2008
ASP (By:12-2014)
Turkey has no X.25 connection. Radar and voice connections are using TDM point to point connection. AFTN/CIDIN/AMHS and other ground data connections are already using IP based connections.
Completed
12/2008
MIL (By:12-2014) Military has its own network. No plan to implement this objective.
Not Applicable
‐
LSSIP Year 2013 Turkey 29 Released Issue
COM10 Migrate from AFTN to AMHS (By:12/2014)
Partly Completed
Enabler(s): CTE‐C10
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.
10/2014
ASP (By:12-2014)
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.
Partly Completed
AMHS 10/2014
MIL (By:12-2014)
Military have their own communication network for OAT message purposes. The system is fully interoperable with the ANSP
Completed
DHMI/Military 03/2009
COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM (By:12/2020)
Planned
Enabler(s): CTE‐C8
In SMART Project Turkey is implementing VoIP based network. 10/2014 REG (By:12-2018) DGCA will take the necessary measures with SMART project.
Planned
10/2014
ASP (By:12-2020) In SMART Project Turkey is implementing VoIP based network.
Planned
10/2014
MIL (By:12-2020) No plan
No Plan
‐
ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements (By:12/2013)
[IDP]
Late
OI Step(s): AOM‐0701
LTAI - AntalyaAn initial CDA workshop meeting was given by EUROCONTROL. There is no final date for this to be implemented but DHMI will implement CDA in the medium term future.
12/2014
ASP (By:12-2013) DHMI will implement CDA approaches in the medium term.
Late
12/2014
APO (By:12-2013) DHMI will implement CDA approaches in the medium term.
Late
12/2014
ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements (By:12/2013)
[IDP]
Late
OI Step(s): AOM‐0701
LTBA - IstanbulAn initial CDA workshop meeting was given by EUROCONTROL. There is no final date for this to be implemented but DHMI will implement CDA in the medium term future.
12/2014
ASP (By:12-2013) DHMI will implement CDA approaches in the medium term.
Late
12/2014
APO (By:12-2013) DHMI will implement CDA approaches in the medium term.
Late
12/2014
LSSIP Year 2013 Turkey 30 Released Issue
ENV02 Implement Collaborative Environmental Management (CEM) at Airports (By:12/2016)
Partly Completed
OI Step(s): AO‐0703, AO‐0705, AO‐0706
LTAI - AntalyaSIDs 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.
12/2014
ASP (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.
Partly Completed
12/2014
MIL (By:12-2015) ‐
Not Applicable
‐
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.
Partly Completed
12/2014
ENV02 Implement Collaborative Environmental Management (CEM) at Airports (By:12/2016)
Partly Completed
OI Step(s): AO‐0703, AO‐0705, AO‐0706
LTBA - IstanbulSIDs 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.
12/2014
ASP (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.
Partly Completed
12/2014
MIL (By:12-2015) Not applicable.
Not Applicable
‐
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.
Partly Completed
12/2014
FCM01 Implement enhanced tactical flow management services (By:12/2006)
[Essential] Late
OI Step(s): IS‐0102 [E]
Some system modifications are still required and the date of 10/2014 is the planned completion date for all objectives.
10/2014
ASP (By:12-2006)
Objective FCM01‐ASP08 will be in SMART phase so date of 10/2014 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 messagesfor Istanbul and Izmir . In addition the system is sending OAT rather than just GAT correlated flight data. All objectives will be completed by 10/2014
Late
Interim SMART / SMART
10/2014
MIL (By:12-2001) GAT flights co‐ordinated through DHMI.
Not Applicable
‐
LSSIP Year 2013 Turkey 31 Released Issue
FCM03 Implement collaborative flight planning (By:12/2015) [IDP]
[Essential] Planned
OI Step(s): DCB‐0302 [E], IS‐0101 [E], IS‐0102 [E]
The Interim SMART system is capable of compliance with all SLoAs other than ASP09. The other remaining objectives are theoretically ready but closed and not tested because of the new AFTN system is recently in force and some other requires extra SW due to military needs. .
10/2014
ASP (By:12-2015)
The Interim SMART system is capable of compliance with all SLoAs other than ASP09. The other remaining objectives are theoretically ready but closed and not tested because of the new AFTN system is recently in force and some other requires extra SW due to military needs.
Planned
Interim SMART / SMART
10/2014
MIL (By:12-2015) No plan. All military GAT flight plans are submitted through DHMI.
Not Applicable
DHMI/Military ‐
FCM04 Implementation of Short Term ATFCM Measures - phase 1 (By:12/2015) (Outside Applicability Area)
[IDP] [Essential]
Not Applicable
OI Step(s): DCB‐0205 [E]
TR is not in the applicability area. ‐ REG (By:12-2015) ‐
Not Applicable
‐
ASP (By:12-2015) ‐
Not Applicable
‐
FCM05 Implementation of interactive rolling NOP (By:12/2016) [IDP]
[Essential] No Plan
OI Step(s): AOM‐0205 [E], DCB‐0102 [E]
No plan ‐ REG (By:12-2016) No plan
No Plan
‐
ASP (By:12-2016) No plan
No Plan
‐
MIL (By:12-2016) No plan
No Plan
‐
APO (By:12-2016) No plan
No Plan
‐
INF04 Implement integrated briefing (By:12/2012)
Completed
OI Step(s): IS‐0201
All infrastructure ready for full implementation in 07/2010. 07/2010 ASP (By:12-2012) All infrastructure ready for full implementation in 07/2010.
Completed
DHMI 07/2010
MIL (By:12-2012) Completed.
Completed
‐
ITY-ADQ
Ensure quality of aeronautical data and aeronautical information (By:07/2017) (Outside Applicability Area)
[Essential] Not Applicable
OI Step(s): IS‐0202, IS‐0204 [E]
Turkey is not within the area of applicability of this objective. ‐ REG (By:07-2017) ‐
Not Applicable
‐
ASP (By:07-2017) ‐
Not Applicable
‐
MIL (By:07-2017) ‐
Not Applicable
‐
APO (By:07-2017) ‐
Not Applicable
‐
LSSIP Year 2013 Turkey 32 Released Issue
ITY-AGDL
Initial ATC air-ground data link services above FL-285 (By:02/2015) (Outside Applicability Area)
[IDP] [Essential]
Not Applicable
OI Step(s): AUO‐0301 [E]
Turkey is not within the area of applicability of this objective. ‐ REG (By:02-2015) ‐
Not Applicable
‐
ASP (By:02-2015) ‐
Not Applicable
‐
MIL (By:-) ‐
Not Applicable
‐
ITY-AGVCS2
Implement air-ground voice channel spacing requirements below FL195 (By:12/2020) (Outside Applicability Area)
Not Applicable
Enabler(s): CTE‐C5
TR is not in the applicability area. ‐ REG (By:12-2018) ‐
Not Applicable
‐
ASP (By:12-2018) ‐
Not Applicable
‐
MIL (By:12-2020) ‐
Not Applicable
‐
APO (By:12-2018) ‐
Not Applicable
‐
ITY-COTR
Implementation of ground-ground automated co-ordination processes (By:02/2015) (Outside Applicability Area)
[Essential] Not Applicable
OI Step(s): CM‐0201 [E]
Turkey is not within the area of applicability of this objective. ‐ REG (By:12-2012) ‐
Not Applicable
‐
ASP (By:02-2015) ‐
Not Applicable
‐
MIL (By:12-2012) ‐
Not Applicable
‐
ITY-FMTP Apply a common flight message transfer protocol (FMTP) (By:12/2014)
[IDP]
Planned
Enabler(s): CTE‐C11b
The common flight message transfer protocol will be introduced with the SMART system. 10/2014
REG (By:12-2014)
Completion of the REG objectives is subject to availability of human resources.
Planned
10/2014
ASP (By:12-2014)
The common flight message transfer protocol will be introduced with the SMART system.
Planned
Interim SMART 10/2014
MIL (By:12-2014)
Military has its own network between military sites and there is no plan to upgrade this system. The interface between military/civil sites will be completed once the SMART system is operational.
Planned
SMART 10/2014
ITY-SPI Surveillance performance and interoperability (By:12/2019) (Outside Applicability Area)
Not Applicable
Turkey is not an EU+ State. ‐ REG (By:12-2013) Turkey is not EU+ State.
Not Applicable
‐
ASP (By:02-2015) Turkey is not EU+ State.
Not Applicable
‐
MIL (By:12-2019) Turkey is not EU+ State.
Not Applicable
‐
LSSIP Year 2013 Turkey 33 Released Issue
NAV03 Implementation of P-RNAV (By:12/2012)
[Essential] Completed
OI Step(s): AOM‐0601 [E]
P‐RNAV SIDs and STARS have been implemented at Istanbul and Antalya. Implementation at other airports will continue in due course.
11/2010
REG (By:01-2005)
Whilst P‐RNAV is planned as a future functionality by the Service Provider (DHMI), the Regulator (DGCA) will not implement these local actions.
Not Applicable
DHMI ‐
ASP (By:12-2012)
P‐RNAV SIDs and STARS have been implemented at Istanbul and Antalya. Implementation at other airports will continue in due course.
Completed
11/2010
MIL (By:12-2012) Not applicable for MIL.
Not Applicable
DHMI/Military / Military
Authorities ‐
NAV10 Implement APV procedures (By:12/2016) [IDP]
[Essential] Planned
OI Step(s): AOM‐0602‐A [E], AOM‐0602‐B [E]
Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published. APV BARO‐VNAV procedures are planned.
12/2015
REG (By:04-2016)
Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published. APV BARO‐VNAV procedures are planned.
Planned
12/2015
ASP (By:12-2016)
Regulation for RNP Approach Operations including APV BARO ‐VNAV operations has been published. APV BARO‐VNAV procedures are planned.
Planned
12/2015
MIL (By:12-2016) APV procedures will be the subject of a future project.
No Plan
‐
SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements (By:12/2011)
Late
Planned for implementation with SMART system by 10/2014. 10/2014 REG (By:12-2011) Planned for implementation with SMART system by 10/2014.
Late
10/2014
ASP (By:12-2011) Planned for implementation with SMART system by 10/2014.
Late
10/2014
MIL (By:12-2011) No intention to implement. Not applicable to MIL.
Not Applicable
‐
SAF11 Improve runway safety by preventing runway excursions (By:01/2018)
Planned
Local runway safety teams have been established for each aerodromes. These teams will be responsible for runway excursions.
12/2014
REG (By:01-2018)
Necessary actions are planned in accordance with the implementation date.
Planned
12/2014
ASP (By:12-2014)
Local runway safety teams have been established for each aerodromes. These teams will be responsible for runway excursions.
Planned
12/2014
MIL (By:01-2018) No intention to implement.
Not Applicable
‐
APO (By:12-2014)
Local runway safety teams have been established for each aerodromes. These teams will be responsible for runway excursions.
Planned
12/2014
SRC-CHNG Implementation of Safety Oversight of Changes to ATM by National Supervisory Authorities (NSA) (By:12/2010)
Completed
ESARR6 was enacted 27 January 2010 and gazetted 27475/2010. 12/2013 REG (By:12-2010) ESARR6 was enacted 27 January 2010 and gazetted 27475/2010.
Completed
12/2013
MIL (By:12-2010) The DGCA has no role. Military internal procedures apply.
Not Applicable
‐
LSSIP Year 2013 Turkey 34 Released Issue
SRC-RLMK Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) (By:12/2010)
Completed
ESARR1( SHY‐GOZETIM), ESARR 2 (SHY6502), ESARR3 (SHT 65‐03), ESARR 4 (SHT 65‐04) ESARR 5 (SHY6501) and ESARR 6 (SHY 6) have been enacted.
06/2011
REG (By:12-2010)
ESARR1( SHY‐GOZETIM), ESARR 2 (SHY6502), ESARR3 (SHT 65‐03), ESARR 4 (SHT 65‐04) ESARR 5 (SHY6501) and ESARR 6 (SHY 6) have been enacted.
Completed
06/2011
MIL (By:12-2010) No plan to implement. MIL internal procedures. It is not applicable for MIL.
Not Applicable
‐
SRC-SLRD Safety Levels and Resolution of Deficiencies (By:12/2010)
Completed
Turkey has adopted the ECAC TLS but will review this in time in order to ensure its validity. The DGCA supports a just culture environment and mechanisms are in place to ensure incidents are both reported and investigated. A process to monitor achieved levels of safety has yet to be implemented. An annual Safety Oversight Report is published and ESARR 1 is enacted.
12/2013
REG (By:12-2010)
The DGCA supports a just culture environment and mechanisms are in place to ensure incidents are both reported and investigated.
Completed
12/2013
MIL (By:12-2010)
The military has a mature system to monitor safety levels and resolve deficiencies. The DGCA is informed and involved regarding any incident involving GAT.
Completed
01/2007
LSSIP Year 2013 Turkey 35 Released Issue
Annexes
Annex A – Specialists involved in the LSSIP Process LSSIP Co-ordination
LSSIP Focal Point for Turkey DHMI Cihan Sahin
LSSIP Contact Person for Turkey EUROCONTROL Predrag Vranjkovic
ESSIP Objective Implementation
ESSIP Objective
EUROCONTROL Objective Owners EUROCONTROL EIPR Objective Coordinator
National Stakeholder Specialist(s)
AOM13.1 R. BUCUROIU, O. MROWICKI, E. REUBER
O. CIOARA
AOM19 G. ACAMPORA, O. MROWICKI O. CIOARA
AOM20 R. BUCUROIU O. CIOARA
AOM21 R. BUCUROIU O. CIOARA
AOP01.2 P. ADAMSON P. VRANJKOVIC
AOP03 T. LICU P. VRANJKOVIC
AOP04.1 P. ADAMSON P. VRANJKOVIC
AOP04.2 P. ADAMSON P. VRANJKOVIC
AOP05 P. ADAMSON P. VRANJKOVIC
ATC02.2 B. BAKKER, S. DROZDOWSKI I. FEIJT
ATC02.5 B. BAKKER, S. DROZDOWSKI I. FEIJT
ATC02.6 B. BAKKER, S. DROZDOWSKI I. FEIJT
ATC02.7 B. BAKKER, S. DROZDOWSKI I. FEIJT
ATC07.1 N. GAUTIER L. DELL’ORTO
ATC12 N. GAUTIER L. DELL’ORTO
ATC15 N. GAUTIER L. DELL’ORTO
ATC16 S. DROZDOWSKI L. DELL’ORTO
ATC17 N. GAUTIER L. DELL’ORTO
COM09 B. GASZTYCH, J. POUZET O. ALFARO
COM10 B. GASZTYCH, J. POUZET A. KOKONA
COM11 B. GASZTYCH, J. POUZET A. KOKONA
ENV01 P. ADAMSON B. HILL
ENV02 S. MAHONY, A. WATT B. HILL
FCM01 H. KOOLEN O. CIOARA
FCM03 S. SMIDT O. CIOARA
FCM04 M. RICHARD O. CIOARA
FCM05 N. AGACDIKEN O. CIOARA
INF04 P. MATERN A-P. FRANGOLHO
ITY-ADQ M. UNTERREINER A-P. FRANGOLHO
LSSIP Year 2013 Turkey 36 Released Issue
ESSIP Objective
EUROCONTROL Objective Owners EUROCONTROL EIPR Objective Coordinator
National Stakeholder Specialist(s)
ITY-AGDL E. CERASI, S. DISSING A. KOKONA
ITY-AGVCS2 J. ROCA O. ALFARO
ITY-COTR S. MORTON L. DELL’ORTO
ITY-FMTP B. GASZTYCH, J. POUZET O. ALFARO
ITY-SPI M. BORELY, R. STEWART A-P. FRANGOLHO
NAV03 F. PAVLICEVIC A. KOKONA
NAV10 R. FARNWORTH, F. PAVLICEVIC A. KOKONA
SAF10 T. LICU I. FEIJT
SAF11 S. LAWRENCE I. FEIJT
SRC-CHNG M. DEBOECK A. DYBOWSKA
SRC-RLMK M. DEBOECK A. DYBOWSKA
SRC-SLRD M. DEBOECK A. DYBOWSKA
LSSIP Year 2013 Turkey 37 Released Issue
Annex B – National Stakeholders Organisation Charts
1. DHMI Organisational chart
LSSIP Year 2013 Turkey 38 Released Issue
2. DGCA Organisational chart
LSSIP Year 2013 Turkey 39 Released Issue
Annex C – Glossary of Abbreviations
ACAS Airborne Collision Avoidance System
ACC Area Control Centre
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
ECAC European Civil Aviation Conference
ECIP European Convergence and Implementation Plan
ESARR EUROCONTROL Safety Regulation Requirement
ESP European Safety Programme
LSSIP Year 2013 Turkey 40 Released Issue
FDP Flight Data Processing
FIR Flight Information Region
FL Flight Level
FSQA Flight Safety and Quality Assurance
FUA Flexible Use of Airspace
GBAS Ground Based Augmentation System
GNSS Global Navigation Satellite System
HRS Human Resources
HUM Human (Domain)
ICAO International Civil Aviation Organisation
IFPS Initial Flight-plan Processing System
IFR Instrument Flight Rules
ISO International Standards Organisation
JAA Joint Aviation Authorities
kHz Kilohertz
LoA Letters of Agreement
MIL Military
NAV Navigation
NM Nautical Mile
NOTAM Notice To Airmen
OLDI On Line Data Interchange
OPS Operations
PSR Primary Surveillance Radar
QMS Quality Management System
REG Regulatory Authorities
RNP Required Navigation Performance
RVSM Reduced Vertical Separation Minimum
SAN Sakaeronavigatsia Ltd (ATM of Georgia)
SBAS Satellite-Based augmentation systems (SBAS)
SLOA Stakeholder Line of Action
SMQS Safety Management and Quality System
LSSIP Year 2013 Turkey 41 Released Issue
SMS Safety Management System
SRC Safety Regulation Commission
SSR Secondary Surveillance Radar
STCA Short Term Conflict Alert
SUR Surveillance (Domain)
TAV Tepe Akfen Urben
TMA Terminal Manoeuvring Area; Terminal Control Area
top related