InterFAB Cooperation: XMAN
Implementing Extended Cross-Border Arrival Management
World ATM CongressMadrid, 8 March 2016
FABEC XMAN ProjectDr Frank Zetsche, DFS
Agenda
§ Overview§ Traffic Flows§ XMAN Roadmap§ XMAN Concept§ XMAN Benefits
Overview
One pillar of the FABEC Airspace Strategy is the optimisation of trafficflows in and out of the major hubs in and close to the FABEC area (i.e. London, Paris, Frankfurt, Amsterdam, Munich).
Cross Centre Arrival Management (XMAN) constitutes an important element of this strategy.
XMAN
AMAN
Extended Cross Border/Centre Arrival Management (XMAN) constitutes an important element of this strategy.
XMAN: Cross border/centre arrival management§ Covers almost all FABEC Airspace§ Includes potentially all FABEC ACC/UAC
4200NMradius around TMA(40NM)of FABECmajor hubs,incl.London
§ Can be implemented step-wise§ Can be extended to
intermediate airports§ The PCP (Implementing Rule
has been adopted by the Single Sky Committee covering 15 airports in the FAB UK/IRL andFABEC airspace.
§ The deadline for completeExtended AMAN implementation is January 1st, 2024.
Overview
Traffic Flows
EDGGtotal234566flights
100.00%
EDMM107879flights
45.99%
EDUU35902flights
15.31%
EDYY64414flights
27.46%
LSAZ4944flights
2.11%
EDWW4932flights
2.10%
LFEE3flights0.00%
EBBU10177flights
4.34%
EHAA303flights0.13%
LFFF54flights0.02%
EDGGdomestic5958flights
2.54%
Frankfurt/EDDF– year2014arrivalsfiguresspreadbyadjacentACCs*
*Displayofrouteswasdoneforinformation,with2monthsoftraffic:January2014andJuly2014atallFL.FigureswereprocessedusingFlightPlanroutings(model1)extractedfromDDR2,cancelledflightsweresuppressed.MapshowsACCsatDFL340,hencesomeACCsarenotdisplayed(EDMM,EDGG…)
EDMM (ACC Munich) +EDYY (UAC Maastricht) + EDUU (UAC Karlsruhe) deliver about 90 % of thetraffic for EDDF
Primary XMAN imple-mentations for EDDF
§ Planninghorizon:withinAoRoflocalACC
§ NoAMInformationtoupstreamunits
§ RadarandFPLdatafromlocalATSsystem
§ Planninghorizon:~100-200NMbeforeMF 1
§ AM 2 Informatione.g.viaAMA 3 messageorSWIMService
§ RadarandFPLdatafromupstreamunit
§ EFDdatafromNetworkManager
Local AMAN
XMANBasic
§ IntegrationofDMAN,EMAN4,AMANtocoverentireflight
Gate-toGate
§ Planninghorizon:unrestricted
§ AMInformationviaNetworkmanagement
§ RelayofAMinformationoutsideFABEC
§ ImprovedlinktoNetworkManager
§ ImprovedlinktoA-CDM§ LinktoAircraftoperator
XMANOptimized
XMANAdvanced
§ Planninghorizon:FABECAirspace
§ Considerdepartureswithinplanninghorizon
§ Hub-centricAM§ Net-centricdistributionofAMInformation
§ TimebasedFlowmanagement§Delaysharingstrategy§ LinktoA-CDM§ LinktoNetworkManager
1MeteringFix2ArrivalManagement3Messagei.a.w.OLDIstandard4 Enroute manager
2012- 2017 2013– 2024 2017- 2024
XMAN/AMANProject
XMAN Roadmap
§ XMAN: Cross border/centre arrival management§ Extends the planning horizon of AMAN systems into the
airspace of upstream ACC/UAC up to 200 NM (or beyond) including economical Top of Descent (ToD).
§ Provides information for pre-sequencing of the arrivalstream to upstream ACC/UAC and to aircraft.
§ Utilizes upgraded AMAN systems operated at the top 5 TMAs (where available also at intermediate airports).
§ New features for Advanced Step:§ Extension of Active Advisory horizon (next adjacent unit)§ Delay apportionment and distribution§ Dealing with in-horizon departures§ Set-up of XMAN Portal (Information Platform)
XMAN Concept
8
It is estimated that about 25-30 % of the total benefits as calculated for PCP AF 1 (Extended AMAN & PBN) can be attributed to XMAN in the FABEC and FAB UK/IRL airspace.
Benefit calculationrefers to period of2015 – 2030.
FABEC and FAB UK/IRL areaaccounts for 15 ofthe 25 airports in Europe to beregulated by PCP ImplementingRule.
Expected Benefits
XMAN LHR – FABECPaul Nicholls, NATS UK; Theo Hendriks, EUROCONTROL
§ 470,000 flights per annum§ 1300 daily movements § Night time curfew on aircraft movements§ About 60% of arrival traffic is held in one of 4 stacks§ Average arrival delay approximately 8 minutes§ 70 Kt (225Kt CO2) annual fuel burn in holds
Heathrow Operational Overview
Typical Heathrow Daily Stack Holding
UsesETFMS(EnhancedTacticalFlowManagementSystem)
Phase 1 April 2014 – May 2014XMAN activity when delay greater than 9 minutes speed reduction of M0.03
Phase 2 May 2014 – September 2014Introduced a range of speed reductions M0.02 - 0.04 same > 9 minute delay trigger time
Phase 3 September 2014 – December 2014Brest ACC join the TrialUp to Mach 0.04 number reduction applied &decrease to > 7 minute delay trigger time
Phase 4 December 2014 – December 2016Transition into permanent procedures & architecture with each ANSP
Heathrow XMAN Trial Phases
§ AMAN data shared with Partner ANSPs via Web Service – XML Format§ Allows flexible use of data at client end§ Options available for displaying delay information include –
§ HMI at Network Management Positions (Shannon & Brest)§ HMI at Controller working positions (Reims & Prestwick)§ Directly displayed on radar track data block (Maastricht)
§ Open web based architecture using PENS (Messaging VPN)§ Service Oriented ATM Technology § System Virtualisation § Reduced Cost and Development Times
System Architecture and Attributes
§ XMAN delivering annual savings of 4.7Kt fuel/15Kt CO2
§ Stack delay absorbed, in more efficient en-route phase, XMAN flights averaging 48 seconds absorption, flight times unchanged
§ Aircraft reduced in speed by up to M0.04 at 350nm
§ Inter FAB cooperation delivering savings to operators, environmental benefits and reduced noise close to stacks
Heathrow XMAN Case Study
XMAN Multiple TMA SimulationThomas Leparlier, DSNA
Measured Sectors
§ Reims UAC§ 3 Sectors
§ Above FL 315§ 7 Airports§ Simulation prepared
FABEC Core Team§ Zurich ACC§ Maastricht UAC§ Karlsruhe UAC§ Reims UAC
§ Generic Stripless EEC Platform
FABEC ANSPs “Act as One” in SESAR 696
XMAN Horizon
LSZH
EDDK
EHAM
EGLL EDDF
EDDL-DK
EBBR
Simulation Organisation
§ Traffic testing Winter 15§ 3 Prototyping session Spring 15
§ HMI§ Scenario Testing§ Workload adaptation
§ 1 RTS End 15§ Safety Meeting§ Final ATCO debriefing with common point of view
Results: XMAN Capacity
23
XMANhasalimit
§ XMAN Strategy Management is required
§ XMAN workload integrated in local DCB Tool
XMAN § Best effort§ Easy to use§ Easy to share§ Easy to understand
Impact of XMAN § Exit condition§ Traffic presentation§ Creating complexity§ Catch up
Speed Management in UAC
§ Different Speed constraints in UAC§ Cost Index§ TTA distributed by AO/
Airport…§ XMAN
§ Monitoring Speed Variation Tool MonS
§ Managed Mach Advisory
Multiple Airport XMAN Requirements
§ ASD to support XMAN§ Adapt LOA and Procedure§ Complexity at COP
§ Adapted Horizon Design § Mach Advisory before aircraft
on frequency § Horizon aligned with the
airspace design and ATCMOPS
§ Reduce RT Load
AMS
DUS
LGWFRA
OPS AAH OPS AAH
5RSector
Airport OperationalAAH
LGW 250Nm
FRA 260Nm
DUS 240Nm
AMS 250Nm
Jagged Horizon
What’s next ?§ AssessXMANWorkload
§ LocalDCBTools§ PredictXMANActivity§ XMANPortal
§ SharedlocalTP§ EnrichAMANData
§ XMANStrategyManagement§ HorizonDesignoptimization§ TacticalStrategymanagementinsideATFCMprocess
SharedlocalTPEnrichAMANData