Local Single Sky ImPlementation (LSSIP) AUSTRIA · Proposed Issue Restricted Audience ... 2.2.3...

EUROCONTROL

Year 2015 - Level 1

Local Single Sky ImPlementation (LSSIP) AUSTRIA

LSSIP Year 2015 Austria Released Issue

DOCUMENT IDENTIFICATION SHEET

LSSIP for Austria

Infocentre Reference: 16/01/29-55

Document Identifier Edition: Year 2015

LSSIP Year 2015 Austria Edition Date: 10/05/2016

LSSIP Focal Point - Martin Stieber E-mail: [email protected]

Manager ATM Int’l Program Coordination

LSSIP Contact Person - Agnieszka Dybowska

E-mail: [email protected]

Unit DPS/PEPR

Status Intended for

Working Draft General Public

Draft Agency Stakeholders

Proposed Issue Restricted Audience

Released Issue

Accessible via: Internet (www.eurocontrol.int)

Path: Y:\03 LSSIP\1. LSSIP States\Austria (AT) - AD\Year 2015\Released\LSSIP Year 2015_Austria Released.docx

LINKS TO REFERENCE DOCUMENTS

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

2 ESSIP Plan Edition 2015 http://www.eurocontrol.int/pepr

3 European ATM Portal Working - https://www.eatmportal.eu/working

Public - https://www.atmmasterplan.eu/ 4 ESSIP Report 2014 http://www.eurocontrol.int/pepr

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

6 Acronyms and abbreviations

http://www.eurocontrol.int/articles/glossaries

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

8 National AIP http://eaip.austrocontrol.at/

9 RP2 FAB Performance Plan

Latest FABCE Performance Plan V2.0 For details contact: Mr Matej Eljon [email protected]


APPROVAL SHEET

The following authority(ies) have approved all parts of LSSIP Year 2015 document and their signature confirms the correctness of the reported information and reflects their commitment to implement the actions laid down in the European Single Sky ImPlementation (ESSIP) Plan – Edition 2015.


TABLE OF CONTENTS

Executive Summary ................................................................................................................................. 1

Introduction .............................................................................................................................................. 5

National ATM Environment ................................................................................................... 6 Chapter 1 -1.1 Geographical Scope ................................................................................................................ 6

1.1.1 International Membership ......................................................................................................... 6 1.1.2 Geographical description of the FIR(s) ..................................................................................... 6 1.1.3 Airspace Classification and Organisation ................................................................................. 7

1.2 National Stakeholders .............................................................................................................. 7 1.2.1 Civil Regulator(s) ...................................................................................................................... 8 1.2.2 ANSP(s) .................................................................................................................................... 9 1.2.3 Airports .................................................................................................................................... 11 1.2.4 Military Authorities ................................................................................................................... 11

Traffic and Capacity ............................................................................................................ 14 Chapter 2 -2.1 Evolution of traffic in Austria .................................................................................................. 14 2.2 VIENNA ACC ......................................................................................................................... 15

2.2.1 Traffic and en-route ATFM delays 2011-2020 ........................................................................ 15 2.2.2 Summer 2015 performance .................................................................................................... 15 2.2.3 Planning Period 2016-2020 - Summer ................................................................................... 16

ESSIP Report recommendations ........................................................................................ 18 Chapter 3 -

National Projects ................................................................................................................. 19 Chapter 4 -

Regional Co-ordination ....................................................................................................... 21 Chapter 5 -5.1 FAB Co-ordination ................................................................................................................. 21 5.2 FAB Projects .......................................................................................................................... 22 5.3 Regional cooperation ............................................................................................................. 24

ESSIP Objective Implementation ....................................................................................... 25 Chapter 6 -6.1 Conventions ........................................................................................................................... 25 6.2 ESSIP Objectives Implementation progress .......................................................................... 26 6.3 Alignment of PCP with ESSIP Objectives and related progress ........................................... 47

ANNEXES

Annex A – Specialists involved in the LSSIP Process

Annex B – National Stakeholders Organisation Charts

Annex C – Glossary of Abbreviations

LSSIP Year 2015 Austria 1 Released Issue

Executive Summary

National ATM Context

NSA: Austria signed a Memorandum of Understanding (MOU) with ICAO regarding the USOAP CMA. According to the MOU, Austria agreed to an ICVM, which was conducted from 15 to 21 July 2015. The mission evaluated the status of implementation of the latest CAP of the State on the USOAP F&Rs and resulted in an updated overall EI of 92.63 per cent.

Austro Control: In November 2015, ATM System TOPSKY was fully deployed for Approach/TWR Wien plus Local APP Units. Since this date, all ATC units are commonly using one single ATM system.

Military Control Centre: In November 2015, ATM System TOPSKY was fully deployed for MCC, plus enhanced monitoring and evaluation of TRAs.

MIL: The MIL Authority in Austria is the Federal Ministry of Defence and Sports (MoD = BMLVS)

Traffic and Capacity

Traffic and capacity in 2015

ACC:

Traffic increase in 2015 was +1.7%.

Summer 2015 performance assessment:

ATFM delay target derived from RP2 was 0.21 min/flight, actually ACC produced only 0.09 min delay per flight.

The ACC capacity baseline was measured with ACCESS at 194, 3% higher than in 2014. During the measured period, the average peak 1 hour demand was 187 and the average peak 3 hour demand was 170.

APP/TWR Wien:

Traffic decreased by 1.4%, producing 1.05 min delay per arriving flight (Delay reasons: majority weather delays, and to a small extent the implementation of the new ATM system for APP/TWR Wien in November)

ESSIP Objective Implementation

Quick implementation status of the objectives:

Completed: 21

Partly Completed: 1

Planned: 15

Late: 4

No Plan: 0

Outside applicability area:

FCM04 (Short Term ATFCM Measures / STAM phase 1).

Although FAB CE and Austria are not in the initial applicability area for STAM Phase 1 implementation, a FAB CE wide STAM Live Trial was executed in September 2015, and based on preliminary results (the final Report on the Operational Trial will be published Q1/2016), FABCE states agreed to proceed with STAM Phase 1 implementation in FABCE.


Problems in completing objectives due for 2013-2015 (status late):

AOM19 (Advanced Airspace Management): although AMC has been established since March 2010, the implementation of the local ASM support system interoperable with the NM system (LARA tool) is conceived by mid 2017.

AOP05 (Airport CDM): CDM has been locally implemented, but connectivity with Network Manager (DPI message) is pending. Implementation foreseen by mid 2017.

ATC7.1 (AMAN tools/procedures): Full AMAN functionality for Vienna is conceived to be operational by end of 2017, in alignment with the TopSky ATM system development.

ITY-ADQ (quality of aeronautical data and information): A pattern for a formal arrangement has been developed and issued by Austro Control and approved by NSA. Several formal arrangements have been already signed (2 Airports and several Austro Control internal originators), but not all parties referred to in ADQ Article 2(2b) and Article 2(2c) have signed the formal arrangement yet. Due to the high amount of ADQ affected obstacle originators in Austria, the implementation date is dependent on the full implementation of the Austrian eTOD project according to ESSIP INF07 with its final milestone on 31.05.2018.

Plans for completing objectives due for 2016 and 2017

AOM21.2 (Implement Free route Airspace): In close coordination within FABCE, Slovenia and Austria are planning a cross border FRA application between the two ACCs in November 2016.

ATC2.6 (MSAW level2): This function was implemented as part of the new ATC System (Top Sky) for ACC Wien, whereas the full rollout of the TopSky-Safety Net Server for the complete Area of Responsibility will take place by end of 2016.

ATC2.7 (APP Path monitor): The operational release for APM is scheduled for mid 2016.

FCM03 (collaborative flight planning): Collaborative flight planning was already fully implemented, but after the deployment of the new ATM System, it turned out that one action - the AFP activation and provision - has been wrongly implemented. Time for correction is under discussion to reach the final operational capability by end of 2017 at the latest.


LSSIP 2015 - Austria

* FOC Date

█ Planned implementation date (see legend at the bottom of the table)

State-related ESSIP Objectives

<=

2009

2010

2011

2012

2013

2014

2015

2016

2017

2018

2019

2020

2021

2022

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

*

AOM19 Implement Advanced Airspace Management

*

AOM21.1 Implementation of Direct Routing [PCP]

[E] *

AOM21.2 Implement Free Route Airspace [PCP]

[E] *

AOP03 Improve runway safety by preventing runway incursions

*

ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2

*

ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2

*

ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2

*

ATC12.1 Implement automated support for conflict detection, resolution support information and conformance monitoring

*

ATC15 Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations

*

ATC16 Implement ACAS II compliant with TCAS II change 7.1

*

ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

*

COM10 Migrate from AFTN to AMHS

*

COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM

*

FCM01 Implement enhanced tactical flow management services

*

FCM03 Implement collaborative flight planning

*

FCM04 Implementation of Short Term ATFCM Measures - phase 1

FCM05 Implementation of interactive rolling NOP [PCP]

[E] *

FCM06 Traffic Complexity Assessment [PCP]

[E] *

INF04 Implement integrated briefing

*

INF07 Electronic Terrain and Obstacle Data (TOD)

*

ITY-ACID Aircraft identification

ITY-ADQ Ensure quality of aeronautical data and aeronautical information

*

ITY-AGDL Initial ATC air-ground data link services above FL-285

*

ITY-AGVCS2 Implement 8,33 kHz air-ground voice channel spacing below FL195

*


LSSIP 2015 - Austria

* FOC Date

█ Planned implementation date (see legend at the bottom of the table)

ITY-COTR Implementation of ground-ground automated co-ordination processes

*

ITY-FMTP Apply a common flight message transfer protocol (FMTP)

*

ITY-SPI Surveillance performance and interoperability

*

NAV03 Implementation of P-RNAV

NAV10 Implement APV procedures

*

SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements

*

SAF11 Improve runway safety by preventing runway excursions

*

Airport-related ESSIP Objectives

<=

2009

2010

2011

2012

2013

2014

2015

2016

2017

2018

2019

2020

2021

2022

LOWW-Vienna International Airport

AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1

*

AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2

*

AOP05 Implement Airport Collaborative Decision Making (CDM)

*

AOP10 Time Based Separation [PCP]

[E]

AOP11 Initial Airport Operations Plan [PCP]

[E] *

AOP12 Improve runway and airfield safety with ATC clearances monitoring

[PCP]

[E] *

ATC07.1 Implement AMAN tools and procedures

*

ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements

*

ENV02 Implement Collaborative Environmental Management (CEM) at Airports

*

Understanding the Table

Objective Completed No Plan

Objective Partly Completed Missing Data

Objective Planned Not Applicable (Austria does not participate in this obj.)

Late

E= Essential – Master Plan Reference PCP = Pilot Common Project

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.


Introduction

The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a short/medium term implementation 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 2015 describes the situation in the State at the end of December 2015.

The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them:

Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organizations, the organizational structure of the main ATM players - civil and military - and their responsibilities under the national legislation. In addition, an overview of the Airspace Organization and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided in this chapter.

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 recommendations extracted from the ESSIP Report which are relevant to the state/stakeholders concerned. The state reports how they have handled those recommendations and the actions taken during the year to address the concerns expressed by those recommendations;

Chapter 4 provides a set of the main ATM national projects which contribute directly to the implementation of the ATM MP OIs and/or Enablers and ESSIP related Objectives. The description, timescale, progress made and expected contribution to the ATM Key Performance Areas are provided by the states per each project included in this chapter;

Chapter 5 deals with the ATM Regional Coordination. It provides an overview of the FAB cooperation and Projects and also all other regional initiatives and Projects 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 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.

Note: 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.


National ATM Environment Chapter 1 -

1.1 Geographical Scope

1.1.1 International Membership

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

Organisation Since

ECAC

1955

EUROCONTROL 1993

European Union 1995

EASA 2003

ICAO 1948

NATO N/A Partnership for peace since 1995

ITU 1866

1.1.2 Geographical description of the FIR(s)

FIR WIEN is surrounded by FIRs of 8 States, namely Germany, (FIR Munchen), Czech Republic (FIR Praha), Slovak Republic (FIR Bratislava), Hungary (FIR Budapest), Slovenia (FIR Ljubljana), Italy (FIR Milano), Switzerland (FIR Zurich) and Croatia (FIR Zagreb) as adjacent FIR to the MURA Sector (Slovenian Airspace) which is delegated to Austria. Further details to be found in Austrian eAIP:

http://eaip.austrocontrol.at/lo/160108/enr_6.htm


1.1.3 Airspace Classification and Organisation

To see recent details, open the following www-link and refer to Part II – ENR 1.4:

http://eaip.austrocontrol.at/index_new.php

1.2 National Stakeholders

The main National Stakeholders involved in ATM in Austria are the following:

- The Civil Aviation Authority (CAA) which is part of the MoTIT and which performs the function of the Austrian Regulatory Authority (Oberste Zivilluftfahrt Behörde),

- The Federal Ministry of Transport, Innovation and Technology (MoTIT / NSA),

- Austro Control ‘Luftfahrtagentur (LFA)’, NSA for civil ATCO licensing.

- The Accident Investigation Board which is an independent Body within the MoTIT,

- Austro Control, the sole ANS Provider in Austria,

- The Federal Ministry of Defence and Sports: Joint Forces Command / Air.

Their activities are detailed in the following subchapters and their relationships are shown in the figure below:

Other main National Stakeholders are the 6 main Airports in Austria. They are operated by public and public/private enterprises.

Institutional Arrangements and Links

Joint Forces Command / Air

Federal Ministry of Defence and Sports

(MoD)

Federal Ministry of Transport, Innovation

and Technology

as supreme CAA / NSA

(MoTIT)

AUSTRO CONTROL


1.2.1 Civil Regulator(s)

1.2.1.1 General information

Civil Aviation in Austria is the responsibility of the Federal Ministry of Transport, Innovation and Technology (M of TIT) which represents Austria at the EUROCONTROL Decision Making Bodies.

The Regulator is institutionally separated from the ANS Service Provider. The Civil Aviation Authority (CAA) is part of the MoTIT (Oberste Zivilluftfahrtbehörde).

The different national entities having regulatory responsibilities in ATM are summarised in the table below. The Civil Aviation Authority is further detailed in the following sections.

Activity in ATM: Organisation responsible Legal Basis

Rule-making CAA Aviation Act

(BGBl Nr. 253/1957)

Safety Oversight NSA as part of the CAA Aviation Act (BGBl Nr. 253/1957) section. 120c and section 141. SMS and Safety Oversight are described in AASREF (ministerial decree) and

NSA directive for ongoing oversight.

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

NSA as part of the CAA Aviation Act (BGBl Nr. 253/1957) section 120c, d and section 141. SMS and Safety Oversight are described in AASREF (ministerial decree) and

NSA directive for ongoing oversight.

Airspace CAA/Austro Control Aviation Act (BGBl Nr. 253/1957) section 119, 120 a,c and section 124.

Economic NSA as part of the CAA Aviation Act (BGBl Nr. 253/1957) section 120c and section 141.

Refer to FAB CE performance plan RP2

Environment NSA as part of the CAA Aviation Act (BGBl Nr. 253/1957) section 120c and section 141.

Refer to FAB CE performance plan RP2

Security CAA Aviation Act (BGBl Nr. 253/1957) section 120c and section 141.

Accident investigation SUB (Sicherheitsuntersuchungsstelle des Bundes)

§ 136 Aviation Act and

§2 UUG 2005, BGBl. I Nr. 123/2005

1.2.1.2 Austrian Civil Aviation Authority (CAA)

MoTIT incorporates the Civil Aviation Authority (CAA) which performs at the same time the function of the Austrian Regulatory Authority (Oberste Zivil – Luftfahrtbehörde).

ATM Safety occurrence analysis is done by the ANSP and there is a separate Accident Investigation Board as an independent body within the MoTIT; details can be found in chapter 1.2.5.

CAA Web site is the same as the NSA one: www.bmvit.gv.at.

Annual Report published: Y

To ensure conformity with Art. 12, Commission Regulation (EC) 549/2004, continuous reporting takes place through EASA Audit Reports, answering of pilot procedures and the LSSIP reporting process.

An organisational chart of MoTIT is given in Annex B.


1.2.2 ANSP(s)

1.2.2.1 Services provided

1.2.2.1.1 AustroControl GmbH

Name of the ANSP: Austro Control Österreichische Gesellschaft für Zivilluftfahrt mbH

Governance: State enterprise Ownership: 100% Republic of Austria

Services provided Y/N Comment

ATC en-route Y

ATC approach Y

ATC Aerodrome(s) Y

AIS Y

CNS Y

MET Y

ATCO training Y

SAR Y

Others Y Certification of Aircraft, Pilot licensing, Medical check for pilots and ATCOs

Additional information:

Provision of services in other State(s):

Y German regional airports (ATS-TWR for 9 German regional Airports)

Annual Report published: Y The latest annual report covering yearly activities of the ANSP in 2014 can be found under: http://www.austrocontrol.at/unternehmen/profil/facts__figures

Address of ANSP website: www.austrocontrol.at

An organisational chart is given in Annex B.

1.2.2.1.2 ANSP Meteo Serve Wetterdienst GmbH

Name of the ANSP: Meteo Serve Wetterdienst GmbH

Governance: GmbH Ownership: 100% Austro Control

Services provided Y/N Comment

ATC en-route N

ATC approach N

ATC Aerodrome(s) N

AIS N

CNS N

MET Y certified MET-Provider, no designation

ATCO training N

SAR N

Others N

Additional information:

Provision of services in other State(s):

N

Annual Report published: N


1.2.2.2 ATC systems in use

FDPS

Specify the manufacturer of the ATC system currently in use: THALES: TOPSKY system within COOPANS alliance AVIBIT: for all main TWRs, using the Electronic Flight strip system DIFLIS

Upgrade1 of the ATC system is performed or planned? A major upgrade of the TOPSKY took place in November 2015, integrating the terminal areas and MIL Control Centre. Upcoming releases in line with COOPANS enhancements up to twice per year.

Replacement of the ATC system by the new one is planned? First deployment of TOPSKY took place in 2013. So, no plans yet, as the current system is considered as a new one.

ATC Unit ACC and APP Wien, all Local Approach Units plus TWRs (linked with the DIFLIS system), VFSS (Vienna Flight Service Station)

SDPS

Specify the manufacturer of the ATC system currently in use: Thales, using ARTAS tracker

Upgrade1 of the ATC system is performed or planned? Planned continuously, 1-2 upgrades/year

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

ATC Unit ACC, APP/ TWR Vienna, Local APP Units, MCC

1.2.2.3 ATC units

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

ATC Unit Number of sectors Associated FIR(s) Remarks

En-route TMA

Wien ACC Max 18 ** Refer to 1.4.1 The hardware/software configuration of the A-ATMS allows a theoretical maximum of 18 elementary sectors The current demand is served by a maximum of 12 sectors (during daytime).

Wien APP 6 FIR Praha, Bratislava and Budapest

TWR and APP Wien in the TWR Wien building

SALZBURG 1 LAU* SALZBURG

INNSBRUCK 1 LAU* INNSBRUCK

LINZ 1 LAU* LINZ

GRAZ 1 LAU* GRAZ

KLAGENFURT 1 LAU* KLAGENFURT

* LAU=Local Approach Unit

** Note that the number of sectors, as indicated in this Table, is the maximum number of civilian control sectors that can be operated simultaneously by the unit, provided there is sufficient availability of ATCOs. Due to FRQ limitations a theoretical maximum of 16 sectors can be achieved.

1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))


1.2.3 Airports

1.2.3.1 General information

The main airports in Austria are operated by public and public/private enterprises. They are listed in the table below. As the sole ANS Provider, Austro Control provides Air Traffic Services at the airports.

Terminal Airspace (TMA or equivalent)

Airport Controlled by

WIEN WIEN/ SCHWECHAT TWR and APP Wien in the TWR Wien building

SALZBURG SALZBURG LAU*

INNSBRUCK INNSBRUCK LAU*

LINZ LINZ LAU*

GRAZ GRAZ LAU*

KLAGENFURT KLAGENFURT LAU*

* LAU = Local Approach Unit

1.2.3.2 Airport(s) covered by the LSSIP

Referring to the List of Airports in the ESSIP Plan – Part I Section 4, it is up to the individual State to

decide which additional airports will be reported through LSSIP for those objectives.

So the following airports are covered in this LSSIP: WIEN Schwechat.

1.2.4 Military Authorities

The Military Authority in Austria is the Federal Ministry of Defence and Sports (MoD = BMLVS) .

The Military Aviation Division = Abteilung Militaerluftfahrt (MLF) is part of the Ministry of Defence and Sports (MoD = BMLVS) and is responsible for Air Traffic Management (ATM) plus Air Navigation Services (ANS). Co-ordination with Ministry of Transport at strategic level is done via the CIV/MIL ATS coordination board = Lenkungsausschuss Flugsicherung (LAF).

The planning of airspace use at pre-tactical level is done via the civil/military joint unit Airspace Management Cell (AMC).

Day-to-day co-ordination of Operational Air Traffic (OAT) and General Air Traffic (GAT) is handled at the tactical level between Austro Control and representatives of the Military Control Centre (MCC).

Austro Control is the sole Austrian ATS provider and allocates airspace to military units on a temporary basis. Military ATS is normally provided only to OAT, and additionally to GAT within Military Training Areas (MTA) on and around Air Force bases.


1.2.4.1 Regulatory role

Regulatory framework and rule-making

Oversight

1.2.4.2 Service Provision role

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, Aviation Act Level of such legal provision: Y

Authority signing such legal provision: Austrian Government

Authority signing such legal provision: MOD / MLF

These provisions cover: These provisions cover:

Rules of the Air for OAT Y

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 Y ANSP Supervision Y

Aircrew Training Y ESARRs as applicable Y

Aircrew Licensing Y SES legislation as applicable Y

Additional Information: N/A Additional Information: N/A

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

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

National AIP Y National AIP Y

National Military AIP N/A National Military AIP N/A

EUROCONTROL eAIP N EUROCONTROL eAIP N

Other: Aeronautical Charts Y Other: Aeronautical Charts Y

OAT GAT

National oversight body for OAT: MoD NSA (as per SES reg. 550/2004) for GAT services provided by the military: Y

Additional information: N/A Additional information: N/A

For TRG and licensing of MIL ATC personnel MIL NSA

OAT GAT

Services Provided: Services Provided:

En-Route Y En-Route within MIL TRG Areas Y

Approach/TMA Y Approach/TMA Y

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

AIS Y AIS Y

MET Y MET Y

SAR Y SAR Y

MIL Training Area (MTA) monitoring

Y FIS Y

Other: N/A Other: N/A


Military ANSP providing GAT services SES certified?

N If YES, since: N/A Duration of the Certificate:

N/A

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

Y

Additional Information: N/A

1.2.4.3 User role

1.2.4.4 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 Y Within specific corridors only N

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

Within a special OAT route system Y Under radar advisory service Y

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

No special arrangements N 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: N/A

Military in Austria applies FUA requirements as specified in the Regulation No 2150/2005: Y

FUA Level 1 implemented: Y




Traffic and Capacity Chapter 2 -

2.1 Evolution of traffic in Austria

2015

Traffic in Austria (ACC plus INN corridor) increased by 0.6% during Summer 2015 (May to October inclusive), when compared to the same period during 2014.

In total for 2015, traffic increased by 1.7% compared to 2014.

2016-2020

The STATFOR medium-term forecast (MTF) predicts an annual traffic growth of between 0.8% and 4.0% throughout the planning cycle, with a baseline growth of 2.5%.

0

200,000

400,000

600,000

800,000

1,000,000

1,200,000

1,400,000

1,600,000

2011 A 2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F

IFR

flig

hts

Austria - Annual IFR Movements

IFR movements - Actuals

IFR movements - Baseline forecast

IFR movements - High forecast

IFR movements - Low forecast A = ActualF = Forecast

2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F

H 2.2% 4.4% 4.3% 4.0% 3.3% 4.1% 3.1%

B -1.8% -1.7% 3.4% 1.8% 2.4% 2.4% 2.8% 2.4% 2.6% 1.9%

L 1.3% 0.0% 0.4% 1.3% 1.0% 1.2% 0.6%

ESRA08 B -2.4% -1.1% 1.7% 1.6% 2.3% 2.3% 2.3% 2.2% 2.7% 1.8%

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

Austria


2.2 VIENNA ACC

2.2.1 Traffic and en-route ATFM delays 2011-2020

2.2.2 Summer 2015 performance

Traffic Evolution 2015 Capacity Baseline En-route Delay (min/flight) - Summer Capacity

gap Ref value Actual

+0.5 % 194 (+3%) 0.33 0.15 No

The average en-route delay per flight increased from 0.04 minutes per flight in Summer 2014 to 0.15 minutes per flight in Summer 2015.

69% of the delays were due to Weather, 22% due to staffing and 8% due to ATC capacity Capacity Plan 5 % Achieved Comments

DCTs H24/7 165+ in parallel ops with ATS routes Yes

Improved ATFCM techniques, including STAM Yes

Participation in FABCE STAM Live Trial 09/2015

Enhanced sectorisation according to the FAB CE Airspace Plan Yes

Stepped improved sectorisation according to on-going projects Yes

Additional layer top sector Yes

Improved operational procedures including FMP/AMC Yes

Data link (Oct 2014) Yes

Recruitment to maintain staff level Yes

SYSCO with neighbouring units No

Additional sectors as required, depending on traffic demand levels Yes

Maximum configuration: 13 sectors Yes Maximum 12 sectors needed

Summer 2015 performance assessment

The ACC capacity baseline was measured with ACCESS at 194, 3% higher than in 2014. During the measured period, the average peak 1 hour demand was 187 and the average peak 3 hour demand was 170. Actual observed peak was higher.

2011 2012 2013 2014 2015 2016 2017 2018 2019 2020

Peak Day Traffic 2782 2788 2733 3060 2946

Summer Traffic 2347 2303 2275 2481 2493

Yearly Traffic 2015 1961 1916 2057 2097

Summer Traffic Forecast 2526 2596 2668 2730 2815

High Traffic Forecast - Summer 2583 2697 2800 2898 3032

Low Traffic Forecast - Summer 2461 2473 2501 2533 2558

Summer enroute delay (all causes) 0.34 0.27 0.28 0.04 0.15

Yearly enroute delay (all causes) * 0.23 0.16 0.26 0.03 0.11

0.0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1.0

0

500

1000

1500

2000

2500

3000

3500

En

rout

e D

ela

y (m

inu

tes

pe

r fli

gh

t)

IFR

flig

hts

(D

aily

Ave

rag

e)

LOVVACC - Traffic and en-route ATFM delays

*From 01/01/2015 to 31/10/2015


2.2.3 Planning Period 2016-2020 - Summer

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 Plan

2016 2017 2018 2019 2020

Free Route Airspace

DCTs H24/7 165+ in parallel ops with ATS

routes Cross border DCTs FAB

intern & with adjacent ACCs where possible

November 2016

SAXFRA

Stepwise increase of FAB CE wide cross border FRA

applications

full FAB CE wide cross

border application of

DCT/FRA H24

Airspace Management Advanced FUA

ASM

Airport & TMA Network Integration

AMAN LOWW

Cooperative Traffic Management

Improved ATFCM techniques, including STAM

Airspace Enhanced sectorisation according to the FAB CE Airspace Plan Stepped improved sectorisation according to on-going projects

Procedures Improved operational procedures including FMP/AMC

Staffing Recruitment to maintain staff level

Technical

Capacity Additional sectors as required, depending on traffic demand levels

Significant Events 3rd Runway

Munich

Max sectors 14 14 14 14 15

Capacity increase p.a. 5% 3% 3% 3% 3%

Reference profile 11% 4% 3% 2% N/A

Profile – Current routes 1% 2% 2% 2% N/A

Additional information Capacity planning ACC Vienna is based on C/R. In case the political or financial situation changes, they are prepared to cope with an expected traffic increase on the shortest route

2016 2017 2018 20190.21 0.2 0.19 0.190.32 0.32 0.31 0.31

En-route ATFM delay breakdown - Reference ValuesLOVVCTA

AnnualSummer

H 221 14% 230 4% 239 4% 249 4%

Ref. 215 11% 224 4% 230 3% 235 2%

L 208 7% 211 1% 215 2% 220 2%

Open 207 7% 216 4% 221 2% 225 2%

C/R 196 1% 200 2% 205 2% 209 2%

2016 2017 2018 2019

Capacity ProfilesProfiles (hourly movements and % increase over previous year)

LOVV 194

ACC2015

baseline


2014 2015 2016 2017 2018 2019 2020

2016‐2019 Reference Capacity Profile 215 224 230 235

Capacity Profile ‐ Shortest Routes (Open) 207 216 221 225

Capacity Profile ‐ Current Routes 196 200 205 209

Capacity Profile ‐ High 221 230 239 249

Capacity Profile ‐ Low 208 211 215 220

Capacity Baseline 189 194

2016 ‐ 2020 Plan 204 210 216 222 229

140

160

180

200

220

240

260Cap

acity profile (movements per hour)

LOVVCTA - Reference capacity profile and alternative scenarios

2016-2020 Planning Period Outlook

Vienna ACC will have sufficient capacity to cope with the expected traffic growth during the planning period.


ESSIP Report recommendations Chapter 3 -

Recommendations issued from the ESSIP Report for 2014 applicable to Austria for all items that require corrective actions and improvements.

REC-2014-2

Local Stakeholders that declared delays in implementation of FCM01, AOP04.1, SAF10, INF04, NAV03, AOP03, ENV01, ITY-AGDL, ITY-ADQ, COM09, COM10, ITY-FMTP and ITY-COTR, to take corrective measures to reduce the implementation delays.

Local Stakeholders

Corrective actions taken:

All the above indicated Objectives are completed, except ITY-ADQ. For details refer to the elaboration in Chapter 6.

Description:

See above and ITY-ADQ

REC-2014-06

(equal to REC-2013-15)

The ANSPs within a FAB should coordinate their system renewal and capability evolution more closely in order to deliver larger scale performance improvements to customers.

FAB ANSPs

Corrective actions taken:

YES

Description:

ANSPs within FAB CE had been coordinating their system renewal and capability evolution mainly through the following activities: CNS Cost Containment Task Force, Project 10 (technical harmonization and optimization) and Project 1 (FRA Study activity 5). The following systems’ deployment and upgrades have been and are being coordinated among FAB CE ANSPs: regional data network X-BONE (communication infrastructure), surveillance infrastructure (including SUR data exchange) and (currently as a study) ATM system upgrade supporting FRA.


National Projects Chapter 4 -

The main national projects currently ongoing in Austro Control are depicted in the table below.

Name / Code Description - Scope Schedule Status Link with ATM Master Plan / Other references

Expected Contribution to the Key Performance Areas

Austrocontrol (AT) eTOD Database Phase 1 (AIM / ATM System)

establish a Data base and basic software including GUI to collect the required terrain and obstacle data.

implementation of the eTOD requirements is planned to be ready by May 2018.

ongoing ESSIP:INF07 OI-Steps: - Other: -

Capacity: - Safety: detailed and more precise Terrain and Obstacle data Environment: - Cost-Efficiency: -

Implementation of Voice over IP technology (COM Services)

Implementation of Voice over IP technology for all ATM units

2020 ongoing ESSIP:COM11 OI-Steps: - Other: -

Capacity: - Safety: improved information consistency Environment: - Cost-Efficiency: improved FAB interoperability

8,33 FRQ channel spacing below FL195 (COM Services )

According to EU IR 1079/2012, the conversion to 8,33 kHz will be implemented below FL195, including Airport VIE.

31st December 2018

ongoing ESSIP:ITY-AGVCS2 OI-Steps: - Other: -

Capacity: - Safety: The justification results from operator´s obligation from 1st January 2018 not to operate an aircraft in airspace where carriage of radio is required unless the aircraft radio equipment has the 8,33 kHz channel spacing capability. Environment: - Cost-Efficiency: -

ATM system and Sub-System evolution for COTR (ATM System)

Implementation of OLDI messages according to national and FAB roadmap - Transfer of Communication - Transfer of Coordination

Dependent on bilateral implementation until 2016

ongoing ESSIP:ATC17, ITY-COTR OI-Steps: CM-0201 Other: -

Capacity: reduced ATCO workload Safety: interoperability for improved consistency and improved safety net performance Environment: - Cost-Efficiency: -

Mode S and WAM

As of 31/03/2015 the basis for correlation within FIR Wien (more than 50% of the

End 2016 ongoing ESSIP:ITY-ACID Capacity: -




implementation (SUR Service)

traffic) is the downlinked ACID by means of Mode S and A-WAM. The remaining Local Approach Units' A-WAM segments will be operational by end of 2016. Nonetheless, the ACID requirements have been fulfilled for the whole FIR Wien since mid 2015.

OI-Steps: - Other: -

Safety: - Environment: - Cost-Efficiency: improved FAB interoperability according to FAB CE ACID Implementation Plan


Regional Co-ordination Chapter 5 -

5.1 FAB Co-ordination

Having signed and ratified the Agreement on the Establishment of Functional Airspace Block Central Europe, Austria, Bosnia and Herzegovina, Croatia, the Czech Republic, Hungary, Slovakia and Slovenia are part of FAB CE.

The FAB CE States agreed on establishment of the following permanent bodies - the FAB CE Council, NSA Coordination Committee and Joint Civil-Military Airspace Coordination Committee. The FAB CE Council can also establish other bodies necessary for the implementation, operation and further development of the FAB CE Project. For this reason the FAB CE Legal Committee and the FAB CE Performance Body (responsible for preparation of FAB CE Performance Plan for RP2) have been established.

The air navigation service providers of the FAB CE countries established and signed the foundation deed of a joint venture on 17 October 2014, at Brnik, Slovenia - FABCE Aviation Services, Ltd. The company is responsible for the professional management of various regional air navigation projects. The establishment of this joint venture is not only effectively aiming at the progress of the FAB CE programme, but at the same time the Single European Sky programme of the European Union.

The FAB CE Strategy was finalized and approved in June 2014, driven by a need to move towards seamless operations in a way that ensures safe and efficient operations. The document describes the environment in which FAB CE is being developed and defines strategic objectives and targets in order to meet the SES performance requirements. The four priority areas are: Performance, Safety, Free Route Airspace and EU targets.

A FAB CE Performance Plan 2015 – 2019 (for AT, CZ, HR, HU, SI and SK) was adopted and signed by FCC representatives. In June 2015 it was sent to the European Commission for final approval.

An Inter-FAB Cooperation Agreement at ANSP level between DANUBE FAB and FAB Central Europe was signed on 14 October 2015. Through the signature of this Agreement, DANUBE FAB and FAB CE have created a framework for cooperation for nine ANSPs. Establishing a flexible cooperation mechanism, the agreement will contribute towards the safe, efficient and optimised provision of air navigation services. The Agreement supports the Single European Sky legislation, with the aim of providing a safer, more cost-efficient, environment-friendly and performance-driven service. The areas of cooperation under the Agreement include the areas of operations, technical, training, performance and safety.

FAB CE actively participated also at the Inter-FAB Coordination Platform Workshop in October 2015.

Two Social Dialogue forums were held, in May and November 2015, with a wide variety of participants – ANSP CEOs, FAB CE program management, social partners and trade unions. Two major milestones were achieved at the Social Dialogue Forums: the Social Dialogue Charter was amended, paving the way for the FAB CE Alpe Adria Alliance to officially join the Social Dialogue; the second one is the signing of the ATCO Mobility Paper by the CEO Committee and the ATCO unions.


5.2 FAB Projects

Name / Code Description - Scope Schedule Status Link with ATM

Master Plan / Other references


ASP ANS CR (CZ), Austrocontrol (AT), BHANSA (BA), CCL Service Provider (HR), Hungarocontrol (HU), Letové prevádzkové služby Slovenskej republiky, štátny podnik (SK), Slovenia Control (SI) FAB CE Strategic Operational Planning (FAB CE P1)

'The objective of P1 is the optimal use of the airspace within FAB CE, taking into account air traffic flows while ensuring consistency with the wider European network together with the assessment and implementation of the Free Route Airspace concept. The project will implement the FAB CE FRA study („Free route airspace from the Black Forest to the Black Sea” project) which will include a simulation exercise to validate the concept and define requirements for the individual ATM systems. The study will also assess the feasibility of implementation FABCE FRA operations with the potential extension to neighbouring FABs (particularly to FABEC and Danube FAB).

Initiation: 3.1.2011

Ongoing activity ESSIP:AOM21.2 OI-Steps: AOM-0401 Other: DP Family 3.2.4

Capacity: Improve performance (capacity, - flight efficiency), implementation of FUA, implementation of the agreed Airspace Plan; Contribute to achieve following performance indicators: • Capacity: to increase capacity to cope with the increase of around 60% in traffic in 2017 with a maximum delay of 0.3 minutes Safety: - Environment: 11% saving in horizontal flight efficiency by saving 2.1 km deviations (millions) from GCD and saving 23,000 tonnes of Annual CO2 in 2017. Cost-Efficiency: Improvement over 2006 in ATM/CNS costs per flight hour and achieve €469 of economic costs per flight hour in 2017.

Functional integration of ASM/ATFCM processes (FAB CE P3)

The objective of the project is to optimise the flow of air traffic and the management of airspace within FAB CE, taking into account the FAB CE airspace plan and ensuring consistency with the wider European network operations together with the assessment and implementation of the Rolling ASM/ATFCM Processes and STAM IDP/DM Activity Areas. The project achieved most of its original objectives and is currently being redefined to meet the STAM and FUA/ASM requirements stemming from SESAR DP. A new follow-on project will be initiated in 2016.


Ongoing activity ESSIP:AOM19, FCM05 OI-Steps: AOM-0202, AOM-0205, AOM-0401, DCB-0203,

DCB-0102

Other: DP Family 3.1.1

Capacity: Improve performance through implementation of regular processes for the functional integration of pre-tactical ASM/ATFCM processes and STAM; enhance civil-military cooperation and contributing to full application of FUA in FAB CE airspace. Safety: - Environment: See "Capacity" Cost-Efficiency: See "Capacity"




Deployment of FAB CE Competence Scheme (FAB CE P13)

The objective of the project is to implement the agreed measures described in the FAB CE Competence/Transition Plan to fill in the remaining detected gaps towards full harmonisation of ATCOs competence. It will progressively extend to AMC/FMP Staff and ATSEP, where the level of harmonisation is currently lower. The coordination with NSAs will be the essential part of the project activities. The project was frozen in 2015.


Frozen in 2015 ESSIP:- OI-Steps: - Other: -

Capacity: - Safety: - Environment: - Cost-Efficiency: Cost-efficiency of training

Training Facilities (FAB CE P14)

The objective of the project is to define and fully harmonise the training of ATCOs, AMC/FMP Staff and ATSEP based on the Common Competence Schemes defined by FAB CE P13, focus on achieving an optimal use of ATM staff and higher cost efficiency in training. All above in order to facilitate the development of the same performance standards, interoperability, common licensing and increase in performance and quality by applying best practices and exchanging resources. The project has been frozen in 2015.



Capacity: - Safety: - Environment: - Cost-Efficiency: Contributes to develop the network human capital and improve its flexibility.

ANSP Charging (FAB CE P15)

The objective of the project is to identify how the Single Unit Rate or other modification to the charging mechanism can support Free Route Airspace implementation from the point of view of the revenue distribution and capacity utilization of FABCE ANSPs. The project was frozen in 2015.



Capacity: - Safety: - Environment: - Cost-Efficiency: Improve cost-effciency, mitigation of financial risks


The following projects from the 2014 LSSIP list of FAB projects were closed in 2015:

FAB CE P2 – Flexible, Efficient and Safe Operations - Completed in 2015, remaining activities transferred to P1,

FAB CE P5 - Regional Communications Infrastructure Development - Closed in 2015; a follow-on project dealing with the X-bone hardware upgrade will be imitated in 2016,

FAB CE P6 - Frequency management - Closed in 2015; remaining activities transferred to other projects and activities,

FAB CE P8 – Contingency - Closed in 2015

FAB CE P10 - Technical Services harmonisation and optimisation - Closed in 2015; remaining activities transferred to other projects and activities which will be initiated in 2016,

FAB CE P16 - Air Ground Data Link -Closed in 2015.

The following projects were deleted from the 2014 LSSIP list of FAB projects (closed before 2015):

FAB CE P4 – FMTP implementation,

FAB CE P7 – Safety,

FAB CE P9 – ANSP Performance Review Process,

FAB CE P11 – Coordination of FAB CE common approach to Aircraft Identification .

5.3 Regional cooperation

No specific regional projects


ESSIP Objective Implementation Chapter 6 -

6.1 Conventions

Two colour codes are used for each ESSIP Objective ‘box’:

o a colour code is used to show the Objective Scope in the Objective ID cell, and

o another colour code is used to show the Objective Progress in the State and for each national stakeholder.

Obj. ID (*) Obj. Title (By mm/yyyy of overall objective, inc non-State SloAs) Obj. Progress (**)

State’s high level progress statement State Impl. Date

REG (By:mm-yyyy) REG high level progress statement

APO. Progress (**)

APO Impl. Date ASP (By:mm-yyyy) ASP high level progress statement

ASP. Progress (**)

ASP Impl. Date MIL (By:mm-yyyy) MIL high level progress statement

MIL. Progress (**)

MIL Impl. Date APO (By:mm-yyyy) APO high level progress statement

APO. Progress (**)

APO Impl. Date

(*) Objective Scope Code: (**) Objective/Stakeholder Progress Code:

ECAC Completed No Plan

EU+ Partly Completed Not Applicable

Multi-N Planned Missing Data

APT Late


6.2 ESSIP Objectives Implementation progress

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

Planned

‐

Based on an agreement between Ministry of Transport (BMVIT) and MoD (BMLVS) the described objectives are planned, respectively will be closely monitored within the European and FABCE context. National agreements between MoD and MoT will be established with respect to EUROAT by due date.

31/12/2018

REG (By:12/2018)

Mil. Aviation Authority

National agreements between MoD and MoT (Ressort‐bereinkommen) will be established with respect to EUROAT by due date.

‐ Planned

31/12/2018

Oberste Zivil‐Luftfahrtbehörde in Austria

National agreements between MoD and MoT (Ressort‐bereinkommen) will be established with respect to EUROAT by due date.

‐ Planned

31/12/2018

ASP (By:12/2018)


Planned to be based on an agreement between Ministry of Transport (BMVIT) and MoD (BMLVS) ‐ 'Ressortübereinkommen'

‐ Planned

31/12/2018

Austrocontrol Planned to be based on an agreement between Ministry of Transport (BMVIT) and MoD (BMLVS) ‐ 'Ressortübereinkommen'

‐ Planned

31/12/2018

MIL (By:12/2018)


planned to be based on the agreement between Ministry of Transport (BMVIT) and MoD (BMLVS) ‐ 'Ressortübereinkommen'

‐ Planned

31/12/2018

AOM19

Implement Advanced Airspace Management

Timescales:


Late

‐

AMC has been implemented and is fully operational since March 2010. Further enhancements are planned according to the described objective process and common FABCE implementations in the context of ASM System Support tool LARA, which is going to be implemented by mid 2017. CDRs are operationally used according to the ASM handbook.

Objective is planned in the context of FAB CE projects – see details in Chapter 5.

30/06/2017

ASP (By:12/2016)


AMC has been implemented and is fully operational since March 2010. Further enhancements are planned according to the described objective process and common FABCE implementations. CDRs are operationally used according to the ASM handbook. As a follow up procedure and in favour of an interoperable system, the decision for the future ASM support system LARA was made, to be implemented by mid of 2017.

Functional integration of ASM/ATFCM processes

Late

30/06/2017

Austrocontrol

AMC has been implemented and is fully operational since March 2010. Further enhancements are planned according to the described objective process and common FABCE implementations. CDRs are operationally used according to the ASM handbook. As a follow up procedure and in favour of an interoperable system, the decision for the future ASM support system LARA was made, to be implemented by mid of 2017.


Late

30/06/2017


AOM21.1

Implementation of Direct Routing

Timescales:

Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2017

[PCP]

[Essential] Completed

‐

Within the AoR of ACC Wien, Direct Routing Airspace has been identified and DCT Connections have been continuously implemented from FL165 / FL245 up to FL660.

Coordination with NM via RNDSG and ERNIP publication goes without saying; the RAD has also been updated accordingly.\Under the umbrella of the overall FABCE airspace planning, this step has been elaborated and coordinated with all FABCE Partners.


10/12/2015

ASP (By:12/2017)

Austrocontrol

Within the AoR of ACC Wien, Direct Routing Airspace has been identified and DCT Connections have been continuously implemented from FL165 / FL245 up to FL660. Coordination with NM via RNDSG and ERNIP publication goes without saying; the RAD has also been updated accordingly. Under the umbrella of the overall FABCE airspace planning, this step has been elaborated and coordinated with all FABCE Partners.

‐

Completed

10/12/2015

AOM21.2

Implement Free Route Airspace

Timescales:


[PCP]

[Essential] Planned

‐

In fulfilment of the FABCE FRA Roadmap, the first implementation of Free Route Airspace will be achieved in conjunction with a FRA cross border application between Slovenia and Austria in November 2016 (‘SAXFRA’). The cross border area will vertically extend from ground up to FL660 (partly FL460) and comprise the Areas of Responsibility of Austro Control (east of Rocky Line) and Slovenia Control H24. ATS routes within SAXFRA will be deleted, except NONRNAV ATS Routes below FL095 ‐ UFN. Objective is planned in the context of FAB CE projects – see details in Chapter 5.

10/11/2016

ASP (By:12/2021)

Austrocontrol

In fulfilment of the FABCE FRA Roadmap, the first implementation of Free Route Airspace will be achieved in conjunction with a FRA cross border application between Slovenia and Austria in November 2016 (‘SAXFRA’). The cross border area will vertically extend from ground up to FL660 (partly FL460) and comprise the Areas of Responsibility of Austro Control (east of Rocky Line) and Slovenia Control H24. ATS routes within SAXFRA will be deleted, except NONRNAV ATS Routes below FL095 ‐ UFN.

FAB CE Strategic

Operational Planning

Planned

10/11/2016


AOP03

Improve runway safety by preventing runway incursions

Timescales:


Completed

‐

Objective completed at State level (and at Vienna Airport as far as airport authorities are concerned). There are also local safety Teams performing the European Action Plan at regional airports.

30/04/2011

REG (By:12/2013)


Objective completed. ‐ Completed

30/04/2011

Flughafen Wien AG


30/04/2011

ASP (By:12/2013)

Austrocontrol Objective completed. ‐ Completed

30/04/2011



30/04/2011

Flughafen Wien AG


30/04/2011

APO (By:12/2013)



30/04/2011

Flughafen Wien AG

Objective completed at Vienna Airport. There are also local safety Teams performing the European Action Plan in regional airports.

‐ Completed

30/04/2011

AOP04.1

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level1

Timescales:


Completed

LOWW ‐ Vienna International Airport

A‐SMGCS is used as an advisory tool since June 2004. The required technical equipment is installed and in operation. See AIP

The required safety assessment documentation by the ANSP has been delivered in Dec. 2013.

31/12/2013

REG (By:12/2010)


The approval of the changes in the Regulatory Framework has been delayed until 12/2013, due to consideration and application of Interoperability regulatory requirements (Required Declarations). The required safety assessment documentation by the ANSP has been delivered in Dec. 2013.

‐

Completed

31/12/2013

ASP (By:12/2011)

Austrocontrol

Operational procedures defined and the related safety case are pending the regulatory approval. The Certification of technical equipment and operational procedures are thus planned for 2011. The required safety assessment is still pending.

‐

Completed

31/12/2011

APO (By:12/2010)

Flughafen Wien AG

The APO SLOAs are completed for Vienna airport. ‐ Completed

31/12/2004


AOP04.2

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level 2

Timescales:


Completed


The approval of the changes in the Regulatory Framework has been issued in Dec 2013 31/12/2013

ASP (By:12/2017)

Austrocontrol Operational procedures defined and the related safety case is pending for the regulatory approval. The Certification of technical equipment and of operational procedures are thus planned by mid 2013.

‐ Completed

30/09/2013

APO (By:12/2017)

Flughafen Wien AG

The approval of the changes in the Regulatory Framework was delayed till mid 2013 due to consideration and application of Interoperability regulatory requirements (Required Declarations) as well as the certification of technical equipment and operational procedures (although in place).

‐

Completed

31/12/2009

AOP05

Implement Airport Collaborative Decision Making (CDM)

Timescales:


Late


The Airport CDM project has been implemented and reached the status of 'locally implemented' in June 2014. Stepwise completion according to the A‐CDM project in order to reach the status of 'full implementation' is conceived until April 2017, dependent on the DPI implementation.

30/04/2017

ASP (By:12/2016)

Austrocontrol

The Airport CDM project has been implemented and reached the status of 'locally implemented' in June 2014. List of adverse conditions agreed, procedures are partially established and will be finalized by June 2016. De‐icing procedures according to the CDM manual guidelines with regard to the status 'locally implemented 'are already in place. Refinement of the current procedures is in place and subject to ongoing continuous improvements.

‐

Partly Completed

30/06/2016

APO (By:12/2016)

Flughafen Wien AG

The majority of APO tasks is fulfilled, required specific LoAs were ratified. DPI implementation is late, planned by April 2017. (Verification of Interface Connections between VIE and Austro Control Systems is ongoing, first trials with NMOC/ETFMS foreseen in Q1/2017)

‐

Late

30/04/2017


AOP10

Time Based Separation

Timescales:


[PCP]

[Essential] Planned


TBS Project has been nationally set up. Operational and technical experts involved in procedural and architectural developments, including HMI aspects.

Publication aspects with regard to national aeronautical information will be duly respected.

31/12/2023

REG (By:12/2023)


TBS Project has been nationally set up. Operational and technical experts involved in procedural and architectural developments, including HMI aspects. Publication aspects with regard to national aeronautical information will be duly respected.

‐

Planned

31/12/2023

ASP (By:12/2023)

Austrocontrol TBS Project has been nationally set up. Operational and technical experts involved in procedural and architectural developments, including HMI aspects.

‐ Planned

31/12/2023

AOP11

Initial Airport Operations Plan

Timescales:

Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2021

[PCP]

[Essential] Planned


Based on the current CDM Agreements, further planning with regard to the Initial AOP will continue and set up in coordination with all relevant stakeholders.

31/12/2021

ASP (By:12/2021)

Austrocontrol Based on the current CDM Agreements, further planning, Information and data exchange with regard to the Initial AOP will continue in close cooperation with the Airport .

‐ Planned

31/12/2021

APO (By:12/2021)

Flughafen Wien AG

Based on the current CDM Agreements, further planning with regard to the Initial AOP will continue and set up in coordination with all relevant stakeholders.

‐ Planned

31/12/2021

AOP12

Improve runway and airfield safety with ATC clearances monitoring

Timescales:


[PCP]

[Essential] Planned


For more than 10 years, a very advanced digital Flight Strip System is in operation at Vienna TWR, having been updated continuously to reach a state of the art system (DIFLIS by AVIBIT). Based on this tool, the advanced ATC clearance Monitoring function will be embedded.

31/12/2020

ASP (By:12/2020)

Austrocontrol

For more than 10 years, a very advanced digital Flight Strip System is in operation at Vienna TWR, having been updated continuously to reach a state of the art system (DIFLIS by AVIBIT). Based on this tool, the advanced ATC clearance Monitoring function will be embedded.

‐

Planned

31/12/2020

APO (By:12/2020)

Flughafen Wien AG

The required Training / Information will be executed when necessary. ‐ Planned

31/12/2020


ATC02.5

Implement ground based safety nets ‐ Area Proximity Warning ‐ level 2

Timescales:


Completed

‐

APW function according to the ECTL guideline has been implemented being part of the new ATM System (Top Sky) for ACC Wien since 03/2013.

31/03/2013

ASP (By:12/2016)

Austrocontrol APW function according to the ECTL guideline has been implemented being part of the new ATM System (Top Sky) for ACC Wien since 03/2013.

‐ Completed

31/03/2013


APW function according to the ECTL guideline has been implemented being part of the new ATM System (Top Sky) for ACC Wien since 03/2013. The Military Control Centre uses AUSTRO CONTROL ATM system. The APW function according to the ECTL guideline is implemented and used.

‐

Completed

31/03/2013

ATC02.6

Implement ground based safety nets ‐ Minimum Safe Altitude Warning ‐ level 2

Timescales:


Planned

‐

This function was implemented as part of the new ATC System (Top Sky) for ACC Wien, whereas the full rollout of the TopSky‐Safety Net Server for the complete Area of Responsibility will take place by end of 2016. The Military will use the civil ATM system functionality accordingly.

31/12/2016

ASP (By:12/2016)


This function was implemented as part of the new ATC System (Top Sky) for ACC Wien, whereas the full rollout of the TopSky‐Safety Net Server for the complete Area of Responsibility will take place by end of 2016. The Military will use the civil ATM system functionality accordingly.

‐

Planned

31/12/2016

Austrocontrol This function was implemented as part of the new ATC System (Top Sky) for ACC Wien, whereas the full rollout of the TopSky‐Safety Net Server for the complete Area of Responsibility will take place by end of 2016.

‐ Planned

31/12/2016

ATC02.7

Implement ground based safety nets ‐ Approach Path Monitor ‐ level 2

Timescales:


Planned

‐

This function was implemented as part of the new ATC System (Top Sky) in Phase 2 for APP Wien and Local APP Units in Nov. 2015. The operational release for APM is scheduled for mid 2016. The civil infrastructure applies for MIL likewise.

30/06/2016

ASP (By:12/2016)

Austrocontrol

This function was implemented as part of the new ATC System (Top Sky) in Phase 2 for APP Wien and Local APP Units in Nov. 2015. The operational release for APM is scheduled for mid 2016

‐

Planned

30/06/2016


This function was implemented as part of the new ATC System (Top Sky) in Phase 2 for APP Wien and Local APP Units in Nov. 2015. The operational release for APM is scheduled for mid 2016.The civil infrastructure applies for MIL likewise.

‐

Planned

30/06/2016


ATC07.1

Implement AMAN tools and procedures

Timescales:


Late


Implementation of the AMAN functionality of the TopSky ATM system is foreseen to be operational by end 2017.

Since 2009, DFS and AUSTROCONTROL are applying Arrival Management procedures by receiving and transmitting 'time to lose' and 'time to gain' information via AMA message exchange.

31/12/2017

ASP (By:12/2015)

Austrocontrol

Implementation of the AMAN functionality of the TopSky ATM system is foreseen to be operational by end 2017. Nonetheless, since 2009, DFS and AUSTROCONTROL are applying Arrival Management procedures by receiving and transmitting 'time to lose' and 'time to gain' information via AMA message exchange.

‐

Late

31/12/2017

ATC12.1

Implement automated support for conflict detection, resolution support information and conformance monitoring

Timescales:


Completed

‐

TOP SKY functionality of MTCD covers in total this objective and the required lines of Actions. 28/11/2015

ASP (By:12/2021)

Austrocontrol TOP SKY functionality of MTCD covers in total this objective and the required lines of Actions.

‐ Completed

28/11/2015

ATC15

Implement, in En‐Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations

Timescales:


Completed

‐

The information exchange mechanisms, tools and procedures in support of Basic AMAN are in place for ACC Vienna. ATC system is compliant with AMAN use in En Route.

31/03/2013

ASP (By:12/2017)

Austrocontrol En Route: information exchange mechanisms, tools and procedures in support of Basic AMAN are in place for ACC Vienna. ATC system is compliant to AMAN use in En Route.

‐ Completed

31/03/2013


ATC16

Implement ACAS II compliant with TCAS II change 7.1

Timescales:


Completed

‐

Austria fulfils the supervising obligations in accordance with EU regulation 1332/2011 and has achieved the training and performance monitoring actions.

MIL transport A/C have been adequately equipped since March 2015

31/03/2015

REG (By:12/2015)


Austria fulfils the supervising obligations in accordance with EU regulation 1332/2011

‐ Completed

31/12/2014

ASP (By:03/2012)

Austrocontrol Austro Control has implemented the EU regulation 1332/2011 and has achieved the training and performance monitoring Actions accordingly.

‐ Completed

31/03/2012

MIL (By:12/2015)


MIL transport A/C have been equipped since March 2015 ‐ Completed

31/03/2015

ATC17

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

Timescales:


Partly Completed

‐

Implementation of Electronic Dialogue messages will be implemented in several phases. First stage will be the limited use within the AoR, further applications are bound to the COTR implementation roadmap for FABCE and the remaining adjacent units.

31/03/2017

ASP (By:12/2018)

Austrocontrol

Implementation of Electronic Dialogue messages will be implemented in several phases. First stage will be the limited use within the AoR; further applications are bound to the COTR implementation roadmap for FABCE and the remaining adjacent units.

ATM system and Sub‐System

evolution for COTR

Partly Completed

31/03/2017

COM10

Migrate from AFTN to AMHS

Timescales:


Completed

‐

Austro Control has implemented the complete required infrastructure and is prepared for AMHS transfer. Operational AMHS connections are in place with several COM Centres within Europe. (e.g. Sarajevo, Bratislava, Eurocontrol NM, UK , DFS and additional 8 COM Centres... tendency: increasing...) ACG will also proactively support the extended ATMHS application.

31/12/2014

ASP (By:12/2014)

Austrocontrol

Austro Control has implemented the complete required infrastructure and is prepared for AMHS transfer. Operational AMHS connections are in place with several COM Centres within Europe. (e.g. Sarajevo, Bratislava, Eurocontrol NM, UK , DFS and additional 8 COM Centres... tendency: increasing...) ACG will also proactively support the extended ATMHS application. Austro control is the sole ANSP. The MIL unit is not an ANSP. AirDefence Centre is AMHS compatible and capable.

‐

Completed

31/12/2014


COM11

Implementation of Voice over Internet Protocol (VoIP) in ATM

Timescales:


Planned

‐

Planned according to the VoIP roadmap. Initial upgrades for emergency systems in place. Further upgrades at all Local Approach Units and ATM units at Airport Schwechat have been undertaken during 2015. Final upgrades planned till 2020 at the latest for ATCCV. The voice over IP communication to NMOC has been established since 03/2013. For the military, VoI is planned according to the VoIP project plan.

31/12/2020

ASP (By:12/2020)

Austrocontrol

Planned according to the VoIP roadmap. Initial upgrades for emergency systems in place. Further upgrades at all Local Approach Units and ATM units at Airport Schwechat have been undertaken during 2015. Final upgrades planned till 2020 at the latest for ATCCV. The voice over IP communication to NMOC has been established since 03/2013.

Implementation of Voice over IP

technology

Planned

31/12/2020


Planned according to the VoIP Roadmap and the VoIP project plan.

Implementation of Voice over IP

technology

Planned

31/12/2020

ENV01

Implement Continuous Descent Operations (CDO) techniques for environmental improvements

Timescales:


Completed


CDO is facilitated by ATC for airport Vienna (originally conceived for off peak periods, meanwhile performed on a regular basis) including cross border application.

With effect from AIRAC November 2013, approaches are in force applying CDO by means of vectoring to the IAF below FL150 to the RWY in use.

(See AIP LOWW 2‐26)

31/12/2013

ASP (By:12/2013)

Austrocontrol

CDO is facilitated whenever feasible during off peak periods by ATC including cross border application. With effect from AIRAC November 2013, approaches are in force applying CDO by means of vectoring to the IAF below FL150 to the RWY in use. (See AIP LOWW 2‐26) Additionally, shortened Y‐BAR GNSS approaches are in force since Nov. 2013 for noise abatement reasons during night time.

‐

Completed

31/12/2013

APO (By:12/2013)

Flughafen Wien AG

These SLoAs will be implemented according to the target date i.e. end of 2013. There is a partnership agreement between AustroControl, Vienna airport and Austrian Airlines. All other Airlines are also invited. AustroControl is coordinating the actions between all partners.

‐

Completed

31/12/2013


ENV02

Implement Collaborative Environmental Management (CEM) at Airports

Timescales:


Completed


This objective is completed for Vienna Airport.

Regular meetings of the "dialogue forum" are held between local Vienna Airport communities and Vienna Airport partners.

check web page: www.dialogforum.at

31/12/2012

ASP (By:12/2016)

Austrocontrol Objective completed at Vienna Airport. check web page: www.dialogforum.at

‐ Completed

31/12/2005

APO (By:12/2016)

Flughafen Wien AG

Objective completed at Vienna Airport. ‐ Completed

31/12/2012

FCM01

Implement enhanced tactical flow management services

Timescales:


Completed

‐

AustroControl fully completed this objective already in 2008, whereas the remaining objective FCM01‐ASP08 (DPI) is subject to the use of the runway sequencing tool and further CDM Implementation. The DPI is also described in AOP05‐APO05 and will be implemented by 06/2016 in cooperation with Airport Vienna

31/12/2008

ASP (By:07/2014)

Austrocontrol AustroControl fully completed this objective in 2008. The remaining objective FCM01‐ASP08 (DPI) is also covered by AOP05‐APO05 and will be implemented by 06/2016 in the context of CDM.

‐ Completed

31/12/2008

FCM03

Implement collaborative flight planning

Timescales:


Planned

‐

Collaborative flight planning was already fully implemented, but after the deployment of the new ATM System, it turned out that the AFP activation and provision has been wrongly implemented. Time for correction is under discussion to reach the final operational capability by end of 2017 at the latest.

31/12/2017

ASP (By:12/2017)

Austrocontrol

Collaborative flight planning was already fully implemented, but after the deployment of the new ATM System, it turned out that the AFP activation and provision has been wrongly implemented. Time for correction is under discussion to reach the final operational capability by end of 2017 at the latest.

‐

Planned

31/12/2017


FCM04

Implementation of Short Term ATFCM Measures ‐ phase 1

(Outside Applicability Area)

Timescales:

‐ not applicable ‐

Planned

‐

Although FAB CE and Austria are not in the initial applicability area for STAM Phase 1 implementation, FAB CE STAM Working Group was formed and tasked with a STAM Live Trial, which was executed in September 2015., Live Trial was used to verify the possibility to introduce the application of STAM Phase 1 in FABCE area.

Based on preliminary results (the final Report on the Operational Trial will be published Q1/2016), FABCE states agree to proceed with STAM Phase 1 implementation in FABCE.

OTMVs (peak and sustained) are defined for the most used traffic volumes and based on these, local procedures are applied.

As soon as the official STAM applicability area will include Austria and further FABCE states, more detailed info in SLoAs will be given.

31/03/2017

ASP (By:12/2015)

Austrocontrol

Although FAB CE and Austria are not in the initial applicability area for STAM Phase 1 implementation, FAB CE STAM Working Group was formed and tasked with a STAM Live Trial, which was executed in September 2015., Live Trial was used to verify the possibility to introduce the application of STAM Phase 1 in FABCE area. Based on preliminary results (the final Report on the Operational Trial will be published Q1/2016), FABCE states agree to proceed with STAM Phase 1 implementation in FABCE. OTMVs (peak and sustained) are defined for the most used traffic volumes and based on these, local procedures are applied. As soon as the official STAM applicability area will include Austria and further FABCE states, more detailed info in SLoAs will be given.

‐

Planned

31/03/2017


FCM05

Implementation of interactive rolling NOP

Timescales:


[PCP]

[Essential] Planned

‐

In the context of FABCE local/regional automated ASM support is under development. Close coordination with NMOC is ensured at FABCE level and via regional FMPs / AMCs.

Airport slots are already transmitted to DDR.

Implementation of LARA System is envisaged until July 2017.

In accordance with the planned initiative of the Airport Operations Plan for Vienna, the required Integration with the NOP is envisaged and recognised until 2021.


31/12/2021

ASP (By:12/2017)

Austrocontrol In the context of FABCE local/regional automated ASM support is under development ‐ implementation planned for July 2017. (LARA)


Planned

31/07/2017


In the context of FABCE local/regional automated ASM support is under development and implementation in progress. Close coordination with NMOC is ensured at FABCE level and via regional FMPs / AMCs. LARA implementation by July 2017. MIL is integral part of AMC, and MCC interface is technically ready for AIXM 5.1.


Planned

31/07/2017

APO (By:12/2021)

Flughafen Wien AG

Slot data for all airports in Austria are sent by SCA to the EUACA* Common Databank on a daily base (1900loc). From this databank EUACA provides the data regularly to EUROCONTROL for the use of these slot data in the DDR (DDR II) Project. The future AOP, being subject to coordination with the NOP, will be set up and conceived accordingly.

‐

Planned

31/12/2021

FCM06

Traffic Complexity Assessment

Timescales:


[PCP]

[Essential] Planned

‐

The required tools and messages foreseen to assess the traffic complexity are planned to be implemented by end of 2021 at the latest.

31/12/2021

ASP (By:12/2021)

Austrocontrol The required tools and messages foreseen to assess the traffic complexity are planned to be implemented by end of 2021 at the latest.

‐ Planned

31/12/2021


INF04

Implement integrated briefing

Timescales:


Completed

‐

Objective completed. ACG runs an integrated system service, which enables its customers to plan a flight, coordinate an inner‐European flight regarding air traffic (NMOC) to complete the necessary pilot pre‐flight briefing including the MET briefing, either directly at the airport or via internet

31/12/2005

ASP (By:12/2012)

Austrocontrol

ACG runs an integrated system service, which enables its customers to plan a flight, coordinate an inner‐European flight regarding air traffic (NMOC) to complete the necessary pilot pre‐flight briefing including the MET briefing, either directly at the airport or via internet. Not applicable to the Military. The Austrian Military Authorities are using their own briefing and FPL‐system which is tailored to their own specific needs and independent from the civil IBS. Only for flights outside Austrian airspace ‐ which is a very rare case ‐ the civil IBS is used for the retrieval of AIS and MET briefings, without using the FPL‐functions.

‐

Completed

31/12/2005

INF07

Electronic Terrain and Obstacle Data (TOD)

Timescales:


Planned

‐

The Ministry of Transport is planning the national eTOD policy by mid 2016 and does foresee the establishment of oversight and all regulatory tasks and activities for the TOD implementation according to the objective deadlines. A national TOD project has been launched by the Ministry of Transport, whereas it is planned to establish this policy by mid of 2016 due to coordination work between Austro Control and National Geodetic Institute.

Nonetheless, the implementation of the eTOD objective and its requirements is planned to be ready by May 2018 according to the national TOD policy in cooperation with MoD.

31/05/2018

REG (By:05/2018)


The Ministry of Transport is planning the national eTOD policy by mid 2016 and does foresee the establishment of oversight and all regulatory tasks and activities for the TOD implementation according to the objective deadlines. A national TOD project has been launched by the NSA, whereas it is planned to establish this policy by mid of 2016 due to coordination work between Austro Control and a National Geodetic Institute.

‐

Planned

31/05/2018

ASP (By:05/2018)

Austrocontrol The implementation of the eTOD requirements is planned to be ready by May 2018 according to the national TOD policy

eTOD Database Phase 1

Planned

31/05/2018

APO (By:05/2018)

Flughafen Wien AG

The Airport Vienna is expected to implement the required activities for the collection, management and provision of TOD in accordance with national TOD policy in time

‐ Planned

31/05/2018


ITY‐ACID

Aircraft identification

Timescales:

Entry into force of the Regulation: 13/12/2011 System capability: 02/01/2020 Possible deferred compliance, only for services provided by military units or under military supervision, subject to conditions:: 02/01/2025

Completed

‐

Since 31/03/2015 the basis of Aircraft ID for En Route and TMA Vienna is the use of downlinked ACID by means of Mode S and A‐WAM. The required evidences have been delivered in time to reach the target time in March 2015.

MIL Control Centre: applies the civil surveillance structure Airport VIE: applies Mode S ACID and Multilateration

31/03/2015

ASP (By:01/2020)

Austrocontrol

As of 31/03/2015 the basis for correlation is the downlinked ACID by means of Mode S and A‐WAM. The required evidences have been delivered in time to reach the target time in March 2015. The following Mode S sensors are fully installed: Linz, Wien, Koralpe, Austrian Wide Area Multilateration. External sensors and sources: Muenchen, Javornik

Mode S and WAM

implementation

Completed

31/03/2015


ITY‐ADQ

Ensure quality of aeronautical data and aeronautical information

Timescales:

Entry into force of the regulation: 16/02/2010 Article 5(4)(a), Article 5(4)(b) and Article 6 to 13 to be implemented by: 30/06/2013 Article 4, Article5(1) and Article 5(2), Article 5(3) and Article 5(4)(c) to be implemented by: 30/06/2014 All data requirements implemented by: 30/06/2017

Late

‐

A pattern for a formal arrangement (ADQ Compliance checklist) has been developed and issued by Austro Control, and has been approved by NSA. Several formal arrangements have been already signed (2 Airports and several Austro Control internal originators).

Today not all parties referred to in ADQ Article 2(2b) and Article 2(2c) have signed the formal arrangement yet. The national legal framework for the origination of aeronautical data according to the ADQ regulation is published, including the need of having a signed formal arrangement with Austro Control in order to supply aeronautical data in compliance with the ADQ regulation. Due to the high amount of ADQ affected obstacle originators in Austria, the implementation date is dependent on the full implementation of the Austrian eTOD project according to ESSIP INF07 with its final milestone on 31.05.2018.

30/06/2017

REG (By:06/2017)


Ongoing according to project plan (to be analysed, if the Austro Control / ADQ compliance check list is the proper means of compliance for MIL)

‐ Late

30/06/2017


A pattern for a formal arrangement (ADQ Compliance checklist) has been developed and issued by Austro Control, and has been approved by NSA. Several formal arrangements have been already signed (2 Airports and several Austro Control internal originators).

Today not all parties referred to in ADQ Article 2(2b) and Article 2(2c) have signed the formal arrangement yet. The national legal framework for the origination of aeronautical data according to the ADQ regulation is published, including the need of having a signed formal arrangement with Austro Control in order to supply aeronautical data in compliance with the ADQ regulation.Due to the high amount of ADQ affected obstacle originators in Austria, the implementation date is dependent on the full implementation of the Austrian eTOD project according to ESSIP INF07 with its final milestone on 31.05.2018.

‐

Late

30/06/2017

ASP (By:06/2017)


The data quality project, led by ACG/AIM, is running according to the project plan. Several awareness workshop were held by ACG to find proper ways to comply with ADQ together with NSA, provincial governments (en route obstacles), aerodrome operators and surveyors for aerodromes.

A draft formal arrangement has already been issued by Austro Control to be signed by the originators.

A proper system (PLX) to supply AIP relevant data is already in place, even for external originators.

For the military, ongoing according to project plan.

‐

Late

30/06/2017

Austrocontrol The required data quality requirements have been fulfilled according to the ACG project 'DATA QUALITY' by 03/2013. Working instructions to describe the processes are in place.

‐ Late

30/06/2017

APO (By:06/2017)

Flughafen Wien AG

Ongoing according to project plan: Further steps can be made following the signature process for the required checklist, which will be given after clearing issues by CAA.

‐ Late

30/06/2017


ITY‐AGDL

Initial ATC air‐ground data link services above FL‐285

Timescales:

ATS unit operational capability: 05/02/2018 Aircraft capability: 05/02/2020

Completed

‐

CPDLC operation has been put into service for the FIR Vienna above FL 285 since 17 October 2014 (AIRAC Cycle 1311).

17/10/2014

REG (By:02/2018)


CPDLC operation has been put into service for the FIR Vienna above FL 285 since 17 October 2014 (AIRAC Cycle 1311).

‐ Completed

17/10/2014

ASP (By:02/2018)

Austrocontrol CPDLC operation has been put into service for the FIR Vienna above FL 285 since 17 October 2014 (AIRAC Cycle 1311).

Air Ground Data Link

Completed

17/10/2014

MIL (By:01/2019)


Military committed to implement the objective by the SES target date . Present transport type aircraft remain outside applicability area (below FL285)

‐ Not Applicable

‐


ITY‐AGVCS2

Implement 8,33 kHz air‐ground voice channel spacing below FL195

Timescales:

Entry into force: 07/12/2012 New and upgraded radio equipment: 17/11/2013 New or upgraded radios on State aircraft: 01/01/2014 Interim target for freq. conversions: 31/12/2014 All radio equipment: 31/12/2017 All frequencies converted: 31/12/2018 State aircraft equipped, except those notified to EC: 31/12/2018 State aircraft equipped, except those exempted [Art 9(11)]: 31/12/2020

Planned

‐

Conversion is partly completed, required notifications to the commission have been, respectively will be transmitted in time.

Requirements for the remaining stakeholders will be fulfilled in time. Conversion at ANSP level completed. For safety reasons, frequencies assigned to ATIS and Volmet will be converted to 8,33 kHz channel spacing as of 31st December 2018.

31/12/2018

REG (By:12/2018)


8.33 kHz conversion is planned and already partly completed. Required notifications to the commission have been, respectively will be transmitted in time.

‐ Planned

31/12/2018


Conversion is partly completed, required notifications to the commission have been, respectively will be transmitted in time.

‐ Planned

31/12/2018

ASP (By:12/2018)


8,33 conversions will take place by 12/2017 according to the national MIL conversion plan.

8,33 FRQ channel

spacing below FL195

Planned

31/12/2018

Austrocontrol Conversion at ANSP level completed. For safety reasons, frequencies assigned to ATIS and Volmet will be converted to 8,33 kHz channel spacing as of 31st December 2018.

8,33 FRQ channel

spacing below FL195

Planned

31/12/2018

MIL (By:12/2020)


8,33 conversions will take place by 12/2017 according to the national MIL conversion plan. State aircraft / MIL carrier aircraft are already equipped to a major part. No local exemptions for MIL aircraft are envisaged. 8,33 kHz channel spacing capability will be available for all MIL aircraft.

‐

Planned

31/12/2018

APO (By:12/2018)

Flughafen Wien AG

The national Frequency plan does foresee the required FRQ assignments and conversions for VIE plus relevant procedures.

‐ Planned

31/12/2018


All necessary measures have been taken and verified at MoD Level to ensure compatibility with 8.33 kHz channel spacing.

‐ Planned

31/12/2018


ITY‐COTR

Implementation of ground‐ground automated co‐ordination processes

Timescales:

Entry into force of Regulation: 27/07/2006 For putting into service of EATMN systems in respect of notification and initial coordination processes: 27/07/2006 For putting into service of EATMN systems in respect of Revision of Coordination, Abrogation of Coordination, Basic Flight Data and Change to Basic Flight Data: 01/01/2009 To all EATMN systems in operation by 12/2012: 31/12/2012 Systems serving ACCs providing services above FL285 in the airspace defined in Regulation (EU) 2015/310: 05/02/2018

Completed

‐

The main functionalities as required for coordination and transfer have been implemented in the current ATM system (TopSky). LOF / NAN messages for AGDL implementation were implemented in Oct 2014.

17/10/2014

ASP (By:02/2018)

Austrocontrol

The main functionalities for coordination and transfer are already implemented in the current ATM system. Enhanced functions are part of the new ATM System (NG AATMS) and were implemented in October 2014.

ATM system and Sub‐System

evolution for COTR

Completed

17/10/2014

MIL (By:12/2012)


The Military are exchanging BFD and CFD data with the civil ATM system ‐ Not Applicable

31/12/1995

ITY‐FMTP

Apply a 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

Completed

‐

With regard to Regulation (EC) No 633/2007, the verification activities and the assessment of verification of systems (DoV) and the technical file (TF) was positively performed. Local system implementation has been finished and started with FMTP operation with MUN in 04/2011. Meanwhile all adjacent partners have been connected applying FMTP.

30/09/2015

ASP (By:12/2014)

Austrocontrol

Local and national system implementation is completed since . First FMTP operation with MUN since 04/2011 PRA since 10/2012. BRA since 05/2014, BUD since 02/2014, ZAG since 09/2013, LJU and PAD since 03/2015 ZUR since 09/2015

‐

Completed

30/09/2015

MIL (By:12/2014)


Finalised 04/2011 with the common use of the ATM System ‐ Not Applicable

‐


ITY‐SPI

Surveillance performance and interoperability

Timescales:

Entry into force of regulation: 13/12/2011 ATS unit operational capability: 12/12/2013 New aircraft capability: 08/06/2016 ELS in transport‐type State aircraft : 07/12/2017 EHS and ADS‐B Out in transport‐type State aircraft : 07/06/2020 Ensure training of MIL personnel: 07/06/2020 Retrofit aircraft capability: 07/06/2020

Planned

‐

Safety assessments for changes and new SUR systems are continuously monitored and audited by NSA. Formal acceptance is communicated to the ANSP.

SUR data transfer is based on ASTERIX format since the year 2000, and safety assessments for existing and newly implemented SUR infrastructure and the relevant training is applied according to regulations. According to the Safety assessment process and derived procedures, all changes referring to the surveillance infrastructure have been subject to SA's and were delivered to the NSA. The overall SUR chain related Safety assessment has been subject to all safety assessments in question. Dependent on the MIL planning and budget, aircraft fleet and the specific carriage and operation of Mode S Enhanced Surveillance and ADS‐B Out avionics, will be implemented by 12/2019

31/12/2019

REG (By:02/2015)


Safety assessments for changes and new SUR systems are continuously monitored and audited by NSA and formal acceptance comminicated to the ANSP.

‐ Completed

31/10/2012

ASP (By:02/2015)

Austrocontrol

SUR data transfer is based on ASTERIX format since the year 2000. Safety assessments for existing and newly implemented SUR infrastructure and the relevant training is applied according to regulations. According to the Safety assessment process and derived procedures, all changes referring to the surveillance infrastructure have been subject to SA's and were delivered to the NSA. The overall SUR chain related Safety assessment has been subject to all safety assessments in question.

‐

Completed

31/03/2014

MIL (By:06/2020)


partly completed ‐ full Mode S compatible implementation covering the fleet update is foreseen by 12/2019.

‐ Planned

31/12/2019

NAV03

Implementation of P‐RNAV

Timescales:


Completed

‐

As far as RNAV applications are concerned, Austria is fully compliant with ICAO implementation plans, including the advanced ability of RNP 'AR' procedures.

After full completion of P‐RNAV implementation (SIDs, STARs, transitions) in Vienna in 2012, an RNAV rollout plan for the remaining Austrian airports has been established which includes the gradual replacement of conventional SIDs, STARs and ‐where applicable‐ transitions by P‐RNAV procedures. Besides STAR procedures which are still based on RNAV5 to serve all our customers, the roll out is completed.

31/12/2014

ASP (By:12/2023)

Austrocontrol

As far as RNAV applications are concerned, Austria is fully compliant with ICAO implementation plans, including the advanced ability of RNP 'AR' procedures.After full completion of P‐RNAV implementation (SIDs, STARs, transitions) in Vienna in 2012, an RNAV rollout plan for the remaining Austrian airports has been established which includes the gradual replacement of conventional SIDs, STARs and ‐where applicable‐ transitions by P‐RNAV procedures. Besides STAR procedures which are still based on RNAV5 to serve all our customers, the roll out is completed.

‐

Completed

31/12/2014


As far as RNAV applications are concerned, MIL will act from case to case..

‐ Not Applicable

31/12/2010


NAV10

Implement APV procedures

Timescales:


Completed

‐

In accordance with the ICAO assembly resolution 37, currently there are APV/Baro procedures published in AIP for Vienna, Innsbruck, Salzburg and Graz. APV/SBAS procedures for Linz and Graz have been published in 2013.

31/12/2013

REG (By:04/2016)


AMCs are generally not converted into national regulations. ‐ Completed

31/12/2010

ASP (By:12/2016)

Austrocontrol

In accordance with the ICAO assembly resolution 37, currently there are APV/Baro procedures published in AIP for Vienna, Innsbruck, Salzburg and Graz. APV/SBAS procedures for Linz and Graz have been published in 2013.

‐

Completed

31/12/2013

SAF10

Implement measures to reduce the risk to aircraft operations caused by airspace infringements

Timescales:


Completed

‐

Based on initially arranged documentations, a series of workshops has been held in 2010. Additional specific workshops together with flight training organizations, aviation agency and the aero club had been held in 2011 and results were presented to the NSA in the beginning of 2012. Derived from the European Action Plan the national action plan has been elaborated and finalized. All relevant stakeholders have approved the plan under the authority of the NSA.

31/12/2012

REG (By:12/2011)


Based on initially arranged documentations, a series of workshops has been held in 2010 and additional specific workshops together with flight training organisations, aviation agency and the aero club are regularly executed. Derived from the European Action Plan the national action plan has been elaborated and finalized. All relevant stakeholders have approved the plan and the actions have been completed.

‐

Completed

31/12/2012

ASP (By:12/2011)

Austrocontrol

Based on initially arranged documentations, a series of workshops has been held in 2010. Additional specific workshops together with flight training organizations, aviation agency and the aero club had been held in 2011 and results were presented to the NSA in the beginning of 2012. Derived from the European Action Plan the national action plan has been elaborated and finalized. All relevant stakeholders have approved the plan under the authority of the NSA.

‐

Completed

31/12/2012

MIL (By:12/2011)


The locally planned necessary actions have been implemented by end 2012

‐ Completed

31/12/2012


SAF11

Improve runway safety by preventing runway excursions

Timescales:


Completed

‐

The required measures in terms of dissemination of documents, oversight activities and implementation reporting have been executed by the relevant ministerial section of the Ministry of Transport. The remaining stakeholders have completed their tasks.

31/12/2015

REG (By:01/2018)


The required measures in terms of dissemination of documents, oversight activities and implementation reporting have been executed by the relevant ministerial section of the Ministry of Transport.

‐ Completed

31/12/2015

ASP (By:12/2014)

Austrocontrol

Local RWY Safety Team for Vienna established; regular meetings are held 4 times per year at senior operational and managerial level between ATC, airport and main airlines to tackle operational issues (ATC OPS meeting) All relevant recommendations are fulfilled.

‐

Completed

31/12/2013

APO (By:12/2014)

Flughafen Wien AG

Local RWY Safety Team for Vienna established; regular meetings are held 4 times per year at senior operational and managerial level between ATC, airport and main airlines to tackle operational issues (ATC OPS meeting) All relevant recommendations are fulfilled.

‐

Completed

31/12/2013


6.3 Alignment of PCP with ESSIP Objectives and related progress


Annexes

Annex A – Specialists involved in the LSSIP Process

LSSIP Co-ordination

LSSIP Focal Points Organisation Name

LSSIP Focal Point for Austria Austro Control Martin STIEBER

LSSIP Focal Point for NSA/CAA MoT / BMVIT Alfred GULDER

LSSIP Focal Point for ANSP Austro Control Martin STIEBER

LSSIP Focal Point for Airport Airport VIE Franz EHMOSER

LSSIP Focal Point for Military MoD / BMLVS Obst Gerold DOBLHAMMER

EUROCONTROL LSSIP Support

Function Directorate Name

LSSIP Contact Person for Austria DPS/PEPR Agnieszka DYBOWSKA

ESSIP Objective Implementation

ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL PEPR Objective Coordinator

National Stakeholder Specialist(s)

AOM13.1 R. BUCUROIU, O. MROWICKI, C. LUCCIOLI, E. REUBER

A. DYBOWSKA Kristian WOLLNER

AOM19 G. ACAMPORA, O. MROWICKI A. DYBOWSKA Ralph MICHALKE

AOM21.1 R. BUCUROIU A. DYBOWSKA Kristian WOLLNER

AOM21.2 R. BUCUROIU A. DYBOWSKA Kristian WOLLNER

AOP03 T. LICU P. VRANJKOVIC Bernhard SÖLLNER

AOP04.1 P. ADAMSON P. VRANJKOVIC Bernhard SÖLLNER

AOP04.2 P. ADAMSON P. VRANJKOVIC Bernhard SÖLLNER

AOP05 P. ADAMSON P. VRANJKOVIC Roland SCHMIDT

AOP10 M. BIRENHEIDE B. HILL Christian KERN

AOP11 M. BIRENHEIDE B. HILL Franz EHMOSER

AOP12 M. BIRENHEIDE P. VRANJKOVIC Christian WOBORSKY

ATC02.5 B. BAKKER, S. DROZDOWSKI I. FEIJT Roman KIENAST



ATC07.1 P. CONROY, P. TERZIOSKI L. DELL’ORTO Roman KIENAST

ATC12.1 P. TERZIOSKI L. DELL’ORTO Roman KIENAST

ATC15 P. CONROY, P. TERZIOSKI L. DELL’ORTO Roman KIENAST

ATC16 S. DROZDOWSKI L. DELL’ORTO Roman KIENAST

ATC17 S. MORTON L. DELL’ORTO Roman KIENAST

COM10 Y. EYUBOGLU A. KOKONA Gerhard BERGER

COM11 L. POPESCU A. KOKONA Thomas BAUMGARTNER

ENV01 C. FABER B. HILL Daniel SCHAAD

ENV02 S. MAHONY, A. WATT B. HILL Christian WOBORSKY

FCM01 H. KOOLEN O. CIOARA Ralph MICHALKE


ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL PEPR Objective Coordinator

National Stakeholder Specialist(s)

FCM03 TBD O. CIOARA Ralph MICHALKE

FCM04 P. HOP O. CIOARA Ralph MICHALKE

FCM05 I. MENDES O. CIOARA Ralph MICHALKE

FCM06 P. HOP O. ALFARO Ralph MICHALKE

INF04 P. MATERN A-P. FRANGOLHO Joachim BRUJA

INF07 A. PETROVSKY A-P. FRANGOLHO Joachim BRUJA

ITY-ACID A. DESMOND-KENNEDY O. CIOARA Reinhard WALCHER

ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Robert WEHOFER

ITY-AGDL S. DISSING A. KOKONA Michael LÖFFLER

ITY-AGVCS2 J POUZET O. ALFARO Thomas BAUMGARTNER

ITY-COTR S. MORTON L. DELL’ORTO Roman KIENAST

ITY-FMTP L. POPESCU O. ALFARO Michael LÖFFLER

ITY-SPI M. BORELY, R. STEWART O. CIOARA Herbert SCHRANZ

NAV03 F. PAVLICEVIC A. KOKONA Daniel SCHAAD

NAV10 R. FARNWORTH A. KOKONA Daniel SCHAAD

SAF10 T. LICU I. FEIJT Alfred VLASEK

SAF11 S. LAWRENCE I. FEIJT Alfred VLASEK


Annex B – National Stakeholders Organisation Charts

NSA:

http://www.bmvit.gv.at/ministerium/organisation/index.html


Austro Control:


Annex C – Glossary of Abbreviations Note: The meaning of some abbreviations (i.e. FAP, ANS, MS, ORD and SIS) is valid only for purpose of this document and does not correspond with the ICAO 8400 Doc. A-ATMS Austrian ATM system ACAS Airborne Collision Avoidance System ACC Area Control Centre AF ATM Functionality AFTN Aeronautical Fixed Telecommunication Network AIS Aeronautical Information Services AMAN Arrival Management AMC Airspace Management Cell ANS Air Navigation Services AOP Airport Operations (domain) APP Approach Control Service APW Area Proximity Warning ASM Airspace Management A-SMGCS Advanced Surface Movement Guidance and Control System ASP ATS Provider ATC Air Traffic Control ATCO Air Traffic Control Officer ATFM Air Traffic Flow Management ATM Air Traffic Management ATS Air Traffic Services bmvit Austrian: Bundesministerium für Verkehr, Innovation und Technologie (MoTIT) CEO Chief Executive Officer CFMU Central Flow Management Unit (replaced by -> NMOC) CNS Communication, Navigation and Surveillance COM Communications (domain) CP Contact Person EAD European AIS Data Base EATM European Air Traffic Management Programme EC European Commission ECAC European Civil Aviation Conference ESSIP European Single Sky and ImPlementation ENV Environment EU European Union EUR ICAO European Region FAB CE Functional Airspace Block Central Europe (AT, BiH, CZ, HR, HU, SI, SK) FCM Flow and Capacity Management (domain) FIR Flight Information Region FL Flight Level FMP Flow Management Position FT Fast Track FUA Flexible Use of Airspace (concept) GAT General Air Traffic GNSS Global Navigation Satellite System HUM Human Resources (domain) IATA International Air Transport Association ICAO International Civil Aviation Organisation ILS Instrument Landing System JAA Joint Aviation Authorities LAU Local Approach Unit (Graz, Klagenfurt, Innsbruck, Salzburg, Linz) LSSIP Local Single Sky and ImPlementation LoA Letter of Agreement MET Meteorology MIL Military MoD Ministry of Defence MS Member State MoTIT Federal Ministry for Transport, Innovation and Technology NAV Navigation (domain)


NG AATMS New Generation Austrian ATM System NMOC Network Management Operation Cell NSA National Supervisory Authority NSP Network Strategic Plan OAT Operational Air Traffic OLDI On Line Data Interchange OPS Operations OR Operational Requirements ORD Operational Requirements Document PC Provisional Council PCP Pilot Common Project PDP Preliminary Deployment Programme PRC Performance Review Commission PRB Performance Review Board R&D Research and Development RNAV Area Navigation RVR Runway Visual Range RVSM Reduced Vertical Separation Minimum SAF Safety (domain) S-AF Sub ATM Functionality SLoA Stakeholder Line of Action SMGCS Surface Movement Guidance and Control System SMS Safety Management System STATFOR EUROCONTROL Statistics and Forecast (Specialist Panel on Air Traffic Statistics and Forecast) STCA Short Term Conflict Alert SUR Surveillance (domain) TACT Tactical Flow Management TCAS Traffic alert and Collision Avoidance System TF Task Force TMA Terminal Control Area TOPSKY Austrian ATM system provided by Thales ToR Terms of Reference UAC Upper Area Control /Centre UIR Upper flight Information Region

Local Single Sky ImPlementation (LSSIP) AUSTRIA · Proposed Issue Restricted Audience ... 2.2.3...

Documents

Transcript of Local Single Sky ImPlementation (LSSIP) AUSTRIA · Proposed Issue Restricted Audience ... 2.2.3...