Module description: Traffic Sample Pim van Leeuwen, NLR Second Demonstration Workshop Braunschweig, Germany June 25 th, 2013
Structure of the presentation Scenario: traffic definition (sample) + events definition Traffic definition: baseline and two future definitions Producing the general traffic definition Producing the detailed traffic definition (Schiphol) Events definition 2
Scenario: traffic definition + events definition A scenario is composed of the following parts: A reference/baseline traffic definition Optional: additional, cloned traffic to yield a future state traffic definition taking e.g. traffic growth forecast, expected traffic demand and capacity at airports, special events, military/general aviation, etc. into account; Meteo conditions of traffic samples; A specific event (e.g. air-ground datalink loss, airport closure) 3
Scenario scope Scope of the traffic samples: Time period: 24 hours; Core area: Benelux-area to proof the concept for Europe Baseline traffic: a historic traffic sample downloaded from Eurocontrol s Dynamic Data Repository: July 1st 2011; A/c types: all aircraft types listed in BADA; Target dates of traffic sample: now, 2030, 2050; Level of detail of airport modeling: all airport in Europe modeled as start/end nodes of trajectories; Amsterdam Airport Schiphol modeled in detail (see slides later on) 4
Baseline traffic definition Baseline traffic definition: Format: SO6 (adapted) Main data sources: Eurocontrol s DDR: SO6: flight plans and additional radar information for July 1st 2011 ALL_FLT: detailed 4D trajectories flown at July 1st 2011 ECAC-wide size: 33.357 flights, Benelux: 5297 flights Reference date: July 1st 2011 Two steps required to conform to data requirements of 4DCo-GC 5
Future traffic definition 2030 traffic definition: Reference date July 1st 2011 (baseline) Method: DDR Forecast Generation Forecast data sets: Eurocontrol s medium term forecast for 2016 (adapted) Growth Hypothesis: high; airport constraints: yes Result: future traffic sample of 49.613 flights, 148 % of baseline (Benelux: 7.512 flights) 2050 traffic definition: Reference date July 1st 2011 (baseline) Method: DDR Forecast Generation Forecast data sets: Eurocontrol s medium term forecast for 2016 (adapted) Growth Hypothesis: high; airport constraints: yes Result: future traffic sample of 78.110 flights, 232 % of baseline (Benelux 11.925 flights) 6
Producing the Traffic Definition: step 1 NLR s 4DCo-GC Scenario Builder: 7
Step 1: details Inputs: Eurocontrol s SO6, ALL-FLT data files DLR s Sid-runway file Process: Parsing SO6-file and storing the required data fields Consolidation of the SO6 flight data to yield only one line per flight Merge of SO6 flights with the ALL_FLT flights to obtain SID information and information on the first two and last two flight coordinates (Lat/Long) Addition of departure runway information of DLR s Sid-runway file (non- Schiphol) and NLR s logic (Schiphol) Extraction of flight level from route segment lines in SO6 file Encryption of all callsigns 8
Step 2: details Process Add missing runways: Determine runway bearing based on direction between segments Match it with a European navigation database to find the runway Add departure and arrival turn points: First waypoint: departure runway threshold Second waypoint: departure turn point at 5 NM in direction of dep rwy Second last waypoint: arrival turn point 5 NM before arr runway threshold Last waypoint: arrival runway threshold 9
Step 2: continued Downsize the scenario to the Benelux area: Creating a polygon Selecting flights with either a DEP, an ARR or at least one flight segment crossing a segment of the polygon Assure uniqueness of callsigns: First occurrence callsign unchanged (e.g. DLH001) Second occurrence: add A1 (e.g. DLH001A1) Third: DLH001A2, etc. 10
Producing the detailed traffic definition: ADOT Arrival and Departure Optimization Tool for detailed airport Schiphol Underlying idea is to take the specific constraints of certain European hub airports into account Two goals, achieved by employing ADOT in two consecutive cycles: Cycle 1: to refine 4D air segment trajectories by shifting slightly the dep + arr times of Schiphol flights to yield an optimal sequence Cycle 2: to enhance 4D air segment trajectories with specific airport data for generating the 4D ground segments (e.g. gates, aobt, aibt) ADOT Core: Basic AMAN: planning arrivals based on preferred arrival times and shifting them if required with a max number of seconds; integrated with: Sophisticated DMAN: planning departures based on preferred departure times, taking arrivals, rwy configuration, WV categories etc into account 11
ADOT Overview: Cycle 1 Pre-processing Original Eurocontrol SO6 + ALL_FLT file 1) T440: processing (NLR) Arr/Dep Optimization Cycle 1 New Baseline SO6 traffic sample 5) Post-processing (NLR) Baseline traffic sample 2) trajectory generation (DLR) Baseline nominal trajectories 3) pre-processing (NLR) ADOT Cycle 1 DMAN/ AMAN Core 4) Calculating (NLR) 12
ADOT Overview: Cycle 2 Pre-processing New Baseline traffic sample 6) trajectory generation cycle 2 (DLR) Baseline nominal trajectories 7) pre-processing (NLR) Arr/Dep Optimization Cycle 2 10) Used by AGMP tool... ADOT final output 9) Post-processing (NLR) DMAN/ AMAN Core ADOT Cycle 2 8) Calculating (NLR) 13
ADOT Output Cycle 1 and 2 ADOT Output Cycle 1: Format same as baseline traffic definition, but with original dep + arr times replaced by the ADOT modified dep + arr times ADOT Output Cycle 2: Traffic definition enhanced with specific data to be used by the Airport Ground Movement Planner (AGMP): wake_cat: CAT_LIGHT, CAT_MEDIUM, CAT_HEAVY aibt = actual in-block time at EHAM (GMT) Aobt = actual off-block time at EHAM (GMT) gate min.sep =minimum separation applied by ADOT 14
Events Definition Four scenarios defined S-1: Baseline scenario S-2: Very congested scenario: 233% S-3: Airport closure: Luxemburg airport closed between 11 and 12 a.m. 4 departures need to be delayed 1 hour 5 arrivals need to be diverted to Brussels airport 5 new conflict-free 4D contracts need to be generated S-4: Data-link loss and emergency descent: Data-link loss: no air-ground data link Rapid decompression necessitating emergency descent Quick on-board generation of an emergency 4D contract required 15