Integration of the Airport with the Network Impact on Operational Communications & Procedure between CDM Airport & NMOC

Transcription

1 Integration of the Airport with the Network Impact on Operational Communications & Procedure between CDM Airport & NMOC Hans Koolen NMOC Airports Unit Edition Nov 2013

2 Current Operations At Non-CDM Airport Main operational info exchange is currently between NMOC (CFMU) Operations and local FMP. This concerns: Implementation decision for ATFM measures Changes of runway configurations Extensions of taxi-times STW/DTW extensions for aerodromes Improvements or extensions of CTOTs Information about capacity shortfall (e.g. due to WX or WIP) Pre-tactical and strategic ATFM 19/11/2013 2

3 A-CDM Operations At CDM Airports Variable Taxi-Times are provided for each flight SIDs are provided for each flight Outbound traffic is managed by RWY sequence tool To be considered: Is there still a need to update runway-config in NMOC/ETFMS? For ARRiving flights for STAR selection If SID is provided late Operational Communication for CDM Airports Principle: Info exchange between NMOC/CFMU for ATFM/capacity related issues remains between FMP & NMOC/CFMU Info exchange for individual CDM flights shall be done between & NMOC/CFMU directly 19/11/2013 3

4 What will FMP do? CDM Airport: Will be main contact for: Implementation decision for ATFM inbound regulations During normal operations: Runway config update for arriving flights Taxi-time extensions in ENV data for departure > EOBT-3hrs During contingency operations (no DPI sent to NMOC) FMP resumes all actions as was done before the start of CDM operations, such as: All changes of runway configurations Send REA message (via CHMI) Send DLA message Coordination with NMOC/CFMU with regards of general information (e.g. WX, technical issues) Defining the TIS value Needs to keep a close link with both the CDM TWR and NMOC/CFMU operations. 19/11/2013 4

5 What will TWR at CDM Airports do? CDM Airports Needs to communicate with NMOC/CFMU operations for: Situation at the airport to improve situational awareness for NMOC/CFMU. For e.g. display in NOP Portal Actions on individual flight (e.g. adjust CTOT) Will be main contact for: Unexpected runway (un)availability Updates to taxi-times via DPIs (long ground delays) via input of Operational scenario s Slot & Departure Tolerance Window (STW and DTW) extensions (e.g. very bad weather conditions); maximum up to 1h period. DTW (for non regulated flights) STW (for regulated flights) CTOT extensions for individual flights More details: see DPI Implementation Guide section /11/2013 5

6 Impact on Ops Procedures Levels of Operations (1/4) 3 Levels of Operations Purpose: to simplify and harmonise Communication and operations between CDM Airport & NMOC Level 0 Normal Operations Level 1 Adverse Conditions/Hindered Operations Level 2 Disrupted Operations The level of Operations/impact will be agreed between TWR and NMOC operations. 19/11/2013 6

7 Impact on Ops Procedures Levels of Operations Level 0 Normal Operations Situations that qualify: Situation when Demand & Capacity are in balance Actions by CDM TWR: Coordinate on individual flights Inform NMOC about any changes in the situation Inform FMP about any changes in the situation Identify & help flights with disproportional ATFM delay Support from NMOC: ATFM Slot Improvements/extensions for individual flights (if possible) Possible ATFM Slot Swaps Identify & help flights with disproportional ATFM delay 19/11/2013 7

8 Impact on Ops Procedures Levels of Operations Level 1 Adverse Conditions/Hindered Operations Situations that qualify (examples): Emergencies such as security alerts, hijacking, fire, short term closure of rwy/apron/taxiway ATC or Airport system failures, sudden RWY closure, ground stop Extreme adverse weather such as freezing rain, thunderstorm De-icing problems (long delays, lack of de-icing fluid) Actions by CDM TWR: Inform NMOC a.s.a.p. about the situation (and possible development) Inform FMP and agree actions Support from NMOC: Extend STW and DTW Evaluate possible actions Inform ATFM Community (AIM, NOP headline news, Tele-conferences) 19/11/2013 8

9 Impact on Ops Procedures Levels of Operations Level 2 Disrupted Operations Situations that qualify (examples): Departure rate is below 25% of normal capacity Average start-up delay (TSAT-TOBT) > 90min Actions by CDM TWR: Inform NMOC about any changes in the situation Inform FMP about any changes in the situation Support from NMOC: Inform ATFM Community (AIM, NOP Headline news, tele-conference ) Further extend STW and DTW 19/11/2013 9

10 Your questions are very welcome 19/11/