D4.3 Simulation. Modelling and Analyses

Transcription

1 D4.3 Simulation Modelling and Analyses This document contains the description of the ATM simulations that have been carried out for the Endless Runway project. It includes the scenarios that have been modelled, the simulation tools and their adaptation to the circular runway shape, and finally the simulations results and analyses. Project Number Document Identification D4.3_Simulation Status Final Version 2.0 Date of Issue Authors S. Loth; H. Hesselink; R. Verbeek; M. Dupeyrat, S. Aubry Organisation Classification DLR, NLR, ONERA

2 Page 2/69 Document Change Log Version Author Date Affected Sections Description of Change 0.1 S. Loth 7/02/2013 All Initiation of the document structure 0.2 M. Dupeyrat 20/08/ Scenario Definition 3.1 Runway Scheduler Scenarios and runway scheduler behaviour detailed 0.3 S. Aubry 28/08/ Runway Scheduler Minor updates 0.4 S. Loth 26/09/2013 All additional text in some section, review comments, corrections 0.5 M. Dupeyrat 27/09/2013 All Comments answered and document reviewed. 0.6 S. Loth 29/09/2013 All Updated text for sections. Working on comments, references /09/2013 All Release version 2.0 H. Hesselink 11/04/2014 All Review EC + final meeting Document Distribution Organisation EC NLR DLR ONERA INTA ILOT Name Ivan Konaktchiev Henk Hesselink, René Verbeek, Carl Welman, Joyce Nibourg Steffen Loth, Franz Knabe, Sandro Lorenz, Paul Weitz Maud Dupeyrat, Sébastien Aubry, Peter Schmollgruber Francisco Mugnoz Sanz, María Vega Ramírez, Albert Remiro Marián Jez Review and Approval of the Document Organisation Responsible for Review Reference of comment documents Date All Organisation Responsible for Approval Name of person approving the document Date NLR H. Hesselink

3 Page 3/69 Table of Contents Document Change Log 2 Document Distribution 2 Review and Approval of the Document 2 1. Abbreviations 5 Introduction Scope of the document Simulation and analyses overview 8 Scenario Definition Description of the use cases Low wind use case High wind use case Description scenario parameters and rationales 13 Modelling and Simulation Framework Runway Low wind use case Single departing flight Single arrival flight Orchestration High wind use case Single departing flight Single arrival flight Orchestration Terminal Manoeuvring Area TrafficSim TMA Simulation Concept and Simulation Tool TrafficSim Preparation and Running the Simulation Checking for Conflicts Conflict Resolution Extensible Workflow Management for Simulations Ground Taxiway Usage Turnaround Modelling Stand Selection 32

4 Page 4/69 4. Simulation results and analyses Runway TMA Conflicts Capacity Flight Distance and Duration Ground Conclusion References 50 Appendix A Data extraction from the BADA files 51 Appendix B Eurocontrol Demand Data Repository File Types 56 Appendix C Ouput files of the runway scheduler 57 Appendix D Segment and TMA Coordinates 58 Appendix E Traffic Scenario Movements 59 Appendix F Result charts 62

5 Page 5/69 Abbreviations Acronym Arr ATM BADA DDR Dep DLR DOW ER EWMS ft IATA ICAO ILOT INTA ISA kts LDL LFPG m MLW NLR NM ONERA s TAS TERA TMA Definition Arrival Air Traffic Management Base of Aircraft Data Demand Data Repository Departure Deutsches Zentrum für Luft- und Raumfahrt Description of Work Endless Runway Extensible Workflow Management for Simulations feet International Air Transport Association International Civil Aviation Organisation Instytut Lotnictwa Instituto Nacional de Técnica Aeroespacial International Standard Atmosphere Knots Landing Length Paris Charles de Gaulle airport meter Maximum Landing Weight Nationaal Lucht- en Ruimtevaartlaboratorium Nautical Mile Office National d Études et de Recherches Aérospatiales second True Air Speed the Endless Runway Airport Terminal Manoeuvring Area

6 Page 6/69 TOL WP Take Off Length Work Package

7 Page 7/69 1. Introduction This document D4.3 Simulation is part of work package 4 ATM of the Endless Runway project. As described in the DOW [1]: This work package will cover all aspects of the operation of aircraft at the airport, including aspects concerning navigation systems. The operations include the approach and departure phase, runway operations during take-off and landing, and some basic ground movement considerations. Based on the conceptual work, simulation models will be setup, scenarios defined, simulations performed, and analysed. Five tasks are associated to the objectives of the WP, structured as follows: Objective Develop the operational concept for airspace and runway ops. Develop a basic ground operation concept Define the scenarios that should be evaluated in the simulation Setup and model the simulation Run the simulation, record and analyse the data Task 4.1 Airspace and Runway Operations 4.2 Ground Operations 4.3 Scenario Definition 4.4 Modelling 4.5 Simulation and Analyses This document, D4.3, is based on the ATM concept presented in D4.2 [4], which was the output of Tasks 4.1 and Scope of the document D4.3 covers the work related to Tasks 4.3, 4.4 and 4.5 of WP4 and provides the simulation approach, the scenarios used and the analyses of the results from the ATM perspective. Specifically, the document will cover the simulation framework, required parameters, scenario data, the analyses approach and the results.

8 Page 8/69 The document will contain the simulation setup, the scenarios and the results of the evaluation. The following areas are part of the document: Scenario Definition Description of the use cases Brief description of the scenario parameters and their rationale. Modelling and Simulation framework Description of the general simulation approach Description of the simulation tools Description of the recorded and analyzed data Simulation results and analyses Presentation of obtained results Conclusion 1.2 Simulation and analyses overview The concept of the Endless Runway should be evaluated by using simulations. In a first step it had to be checked, whether available simulations can be used and adapted to the Endless Runway idea. It turned out, that some tools can be used and some have to be developed for the project. Three different areas have been identified to be evaluated, the runway itself, the surrounding TMA and the ground movement area. For the runway a special tool was setup by ONERA to optimize the usage, the TMA was simulated with the DLR inhouse solution TrafficSim and the ground area was implemented in Simmod Pro!. The layout of the Endless Runway has been taken from the conceptual work of WP4. The runway is separated into 18 segments and there are also 18 arrival and departure routes that connect to the same number of TMA entry and exit points. Two use cases have been worked out. A low wind situation, where all segments of the runway can be used and a high wind situation where only a limited number is available. Because of limited resources in the project, only the low wind use case has been taken for simulation as this is considered the more demanding one. The base for the simulations is a real traffic data file for flights to and from Paris Charles de Gaulle on 1 st of July By using the developed runway scheduler tool these data were processed to a get an optimized and conflict free flight plan file for the Endless Runway airport. This flight plan was then taken by the other simulation tools as an input. This approach leads to an optimized runway schedule but has the effect that TMA and ground might not operate at the optimum. To evaluate the capacity of the Endless Runway different traffic demands have been setup. By adding virtual flights to the original flight schedule from Charles de Gaulle, traffic demands up to 2 times have been generated. All three areas (runway, TMA, ground) have been evaluated separately by the used simulation tools. Different parameters as delays or capacity are used to get a first indication on the feasibility of the concept.

9 Page 9/69 2. Scenario Definition DOW Scenarios will be developed to cover various situations and conditions at the airport, to enable an evaluation of capacity and environmental aspects. A reference airport will be taken with a conventional runway, which can be used as a comparison to The Endless Runway. High and Low wind operations as well as departure/arrival peaks are foreseen as specific interesting scenarios. In D2.2 [2], two airports categories are envisaged as potentially positively impacted by a circular runway design: Small seasonal airports Large hub airports The two categories are significantly different in terms of airport infrastructure and expected traffic demand and distribution. As examples for the categories Palma de Mallorca and Paris Charles de Gaulle have been selected. A detailed description of the differences between them can be found in [2]. Besides the different timely distribution of the traffic (seasonal and daily) also the geographic distribution of the flights is taken into consideration. In the scope of the project it was not possible to setup complete simulations for both categories. Therefore the large hub airport (taking Paris Charles de Gaulle) was considered as the most constraining and limiting case. In addition, in order to fully use the circular runway length, a scenario with traffic flows coming from every direction was preferred. 2.1 Description of the use cases Two use cases are applicable to the operation on the Endless Runway, depending on the weather (wind) situation. In low wind conditions, the aircraft will be able to take off and land in any direction, at any position on the circle. This will allow optimizing the runway schedule based on the direction the aircraft uses in the TMA. In high wind conditions, part of the runway will deal with cross wind exceeding the safety limits. In this use case, the runway will be separated into two parts, where wind speed and wind direction determine the length of each section and the parts of the runway open for use Low wind use case In the low wind case, wind speed is lower than 20 kts. On the ground, aircraft follow the taxiways in the directions authorized by the circulation map, see Figure 1, from their runway high-speed exit to their allocated gate for arrivals, and from their gate to the runway entry for departures. Figure 1 depicts the circulation map for an Endless Runway operated counter-clockwise. All directions are reversed if the runway is operated clockwise.

10 Page 10/69 ER low wind counter clockwise configuration DEP ARR Stop bar (holding position) Terminal A Figure 1 - Circulation map for aircraft in the low wind case On the runway, aircraft take-off and land within their allocated runway segments. Those are determined as a function of the aircraft preferred route and performances and of the other traffic. In the TMA, aircraft can use any of the TMA entry and exit routes described in [4] and shown on Figure 2. Arriving aircraft will fly directly from their last En-Route point (or from origin airport in the case of free flight) to the allocated TMA entry point, and vice versa for departing aircraft. The TMA entry point corresponds to the first runway segment reserved for landing roll for arriving aircraft, while the TMA exit point corresponds to the last runway segment reserved for take-off roll for departing aircraft. 1 1 In Figure 2 the TMA entry and exit points are named Arr00 to Arr17 and Dep00 to Dep17. Entry Point Arr00 is the first point on the arrival route that is connected to the start of runway segment 00. The same concept applies to the departures. Exit point Dep14 is the last point of the departure route that starts at the end of runway segment 14. This is valid for the anti-clockwise operation of the runway. If the direction changes to clockwise, Entry and Exit points are switched from Arr to Dep and vice versa. This is indicated by the identifiers in brackets in Figure 2.

11 EC DG-RTD Page 11/69 Arr 12 (Dep 12) Dep 03 (Arr 03) Dep 04 (Arr 04) Arr 13 (Dep 13) Dep 05 (Arr 05) Arr 14 (Dep 14) Dep 06 (Arr 06) Arr 15 (Dep 15) Arr 11 (Dep 11) Dep 07 (Arr 07) Dep 02 (Arr 02) Arr 16 (Dep 16) Arr 10 (Dep 10) Dep 08 (Arr 08) Dep 01 (Arr 01) Arr 17 (Dep 17) Arr 09 (Dep 09) ARP Dep 09 (Arr 09) Dep 00 (Arr 00) Arr 00 (Dep 00) Arr 08 (Dep 08) Dep 10 (Arr 10) Dep 17 (Arr 17) Arr 01 (Dep 01) Arr 07 (Dep 07) Dep 11 (Arr 11) Dep 16 (Arr 16) Arr 02 (Dep 02) Arr 06 (Dep 06) Dep 12 (Arr 12) Dep 15 (Arr 15) Arr 05 (Dep 05) Dep 14 (Arr 14) Arr 04 (Dep 04) Dep 13 (Arr 13) Arr 03 (Dep 03) High wind use case Figure 2 - TMA arrival and departure routes available in the low wind case In the high wind case, wind speed is higher than 20 kts, leading to some parts of the runway where the crosswind limits are exceeded. The runway will be split in two parts whose separation axis will correspond to the wind direction. The two runway parts operate in opposite directions, always facing the wind at one point. Runway segments joining the two parts are not allowed for operations. On the ground, aircraft follow the published circulation map established depending on the wind direction from their runway high-speed exit taxiway to their allocated gate for arrivals, and from their gate to the runway entry for departures. Figure 3 shows the circulation map for an Endless Runway with strong North wind.

12 Page 12/69 ARR ER high wind configuration DEP Stop bar (holding position) Terminal A Terminal D Terminal B Terminal C Figure 3 - Circulation map for aircraft in the high wind case On the runway, aircraft take-off and land using their allocated runway segments. Those are determined as a function of the closest aircraft En-Route point, of the aircraft performances and of the other traffic. Aircraft land on the half runway on the same side as their departure airport (direction of origin) or last En Route point, and vice versa for departure aircraft. In the air, aircraft can use the opened TMA entry and exit routes as shown on Figure 4. Arriving aircraft fly from the last En-Route point (or from origin airport in the case of free flight) to the allocated TMA entry point, from where they will reach the intermediate approach point. Then, they will continue with the arrival route that corresponds to the allocated touchdown runway segment. Similarly, departing aircraft fly on the departure route corresponding to their allocated take-off segment until the intermediate departure point. From there, they use the allocated route until the TMA exit point that will take them to their first En-Route point or straight to their destination airport in case of free flight.

13 EC DG-RTD Page 13/ Wind: 30 kts Intermediate departure points Dep 16 Dep 02 Dep 15 Dep 03 Dep 14 Dep 04 Dep 13 Dep ARP Arr 14 Arr 13 Arr 04 Arr Intermediate approach points Figure 4 - TMA arrival and departure routes available in the high wind case 2.2 Description scenario parameters and rationales As a base for both use cases, existing traffic data are used. An airport that answers to the criteria of being a central hub with traffic flows coming from all direction and all fleet categories represented has been chosen: Paris Charles de Gaulle airport (IATA code is LFPG).

14 Page 14/69 The following scenario parameters are specified for the modelling and simulation of the operation on the Endless Runway. Airport altitude: The airport is located at sea level. Runway characteristics: The runway inner radius and width as well as the number of segments dividing the runway define the length of the runway segments and the average centreline used in the scenario modelling. According to [4], these parameters are fixed and set to respectively 1500 meters (runway radius), 140 meters (runway width) and 18 (number of segments). The runway centreline is taken at the middle of the runway width, that is to say 1570 meters from the circle centre. Knowing the runway average centreline and the number of segments, the length of each runway segment is 2π 1570 = 548 m. The numbering of the segments 18 is depicted in Figure 5. Figure 5 - Endless Runway segments numbering Meteorological situation: The scene is set under standard atmospheric conditions (ISA). The wind speed is considered to determine which use case is applicable: high wind (>20 kts) or low wind (<20 kts). In the latter case, the directional use of the runway must be chosen (clockwise or counter-clockwise). Traffic demand: Traffic demand is retrieved from the Eurocontrol s06 file, which contains flight information (callsign, aircraft model) and a few radar plots per flight of all air traffic flows over Europe. It is considered as the traffic demand for the Endless Runway simulation and can be artificially increased or decreased to evaluate capacity limits of the Endless Runway. July 1st, 2011 is used as it was the busiest traffic day of the year 2011 in Europe and departures and arrivals on LFPG are extracted flights are accounted for that day, from 00:14 to 23:53. The maximum number of flights per hour observed is 109. Aircraft performances: For each aircraft of the traffic sample, the following data are extracted from the EUROCONTROL Bada aircraft database ([6]): Take-off distance (TOL) Stall speed in take-off configuration Landing distance (LDL) Stall speed in landing configuration Wake category True Air Speed (TAS) during climb between FL0 and FL090 True Air Speed (TAS) during descent between FL0 and FL 030 It is assumed that arriving aircraft are loaded at Maximum Landing Weight (MLW).

15 Page 15/69 The following Table 1 summarizes the parameters previously described. Table 1- ER scenario input parameters Parameter category Parameter Value Meteorological situation Wind speed 0 kts for the low wind case Strong North wind (25 kts) for the high wind case Runway characteristics Inner radius 1500 m Width 140 m Average centreline 1570 m (segment length : 548 m) Runway directional use counter-clockwise Traffic demand Extraction for LFPG airport of the s06 file for July 1st, exp2 file Aircraft performances Take-off length see aircraft performances Stall speed at take-off see aircraft performances Landing length Stall speed at landing Wake category TAS during climb between FL0 and FL090 TAS during descent between FL0 and FL 030 see aircraft performances see aircraft performances see aircraft performances see aircraft performances and Appendix A see aircraft performances and Appendix A The following Table 2 gives an example of aircraft performances data for the B aircraft. Table 2 - Aircraft performances for the B Take-off length Stall speed at take-off Landing length Stall speed at landing Wake category TAS during climb between FL0 and FL090 TAS during descent between FL0 and FL m 70 m/s 1905 m 60,7 m/s Heavy See Appendix A See Appendix A

16 Page 16/69 3. Modelling and Simulation Framework DOW Based on the conceptual work of the previous tasks the preparation of the simulations will be carried out by modelling the airport with The Endless Runway and by preparing the scenarios. To prepare the simulation, tools and/or analytical models will be adapted accordingly. To transfer the Endless Runway concept developed in D4.2 [4] into a simulation framework, different approaches have been considered. At first it was planned to use Simmod PRO! for all parts of the simulation. Setting up a flight plan as input was not easily possible and had to be done with other tools. Using a fixed runway schedule as a parameter leads also to problems, as Simmod PRO! has no freedom anymore of optimizing aircraft trajectories. It turned out that a single simulation tool cannot cover all aspects of the concept as they are significantly different from today s airport operations. Therefore it was decided to use different tools for the different simulation aspects of the Endless Runway airport concept. As the tools are not directly interconnected to each other, all simulations need to be performed and evaluated separately. To align the simulations, a common scenario based on the Eurocontrol data was used. From the ATM perspective the following areas need to be considered Runway TMA Ground (Manoeuvring Area) For each of the mentioned geographical areas, operational and design criteria where worked out in [4]. These criteria have been implemented in the simulation tools and modelled as close as possible to the concept. Figure 6 gives an overview of the simulation setup as it is described in more detail in the following sections. Aircraft Data (BADA, WP 3, ) Performance Parameter Movement Data (Eurocontrol so6 files) Scenario Route Structure (Arrival/Departure) Separation Runway Layout (Segments) Segment reservation rules Taxiway/Stand Layout Ground movement concept Concept Elements Flight Plan Runway Scheduler Flight Plan Integrated Noise Model (INM) Traffic Sim Simmod PRO! (Taxi Operations) Simulation Tools Data Recording and Analysis Extensible Workflow Management for Simulations Results Figure 6 Simulation Framework setup

17 Page 17/ Runway For the runway part a dedicated program was developed by ONERA that is used as runway scheduler. The runway scheduler program takes existing traffic as input that is used as the traffic demand for the Endless Runway. In line with the methodology described in [4], it produces a de-conflicted runway sequence for arriving and departing aircraft. One day traffic at a European airport (EUROCONTROL s06 file) Aircraft characterisics: -wake category -performances (BADA) => LDL, TOL, ROT Runway parameters: Radius, number of segments Runway Scheduler Runway sequence + Comparative statistics Runway segments reservation rules The runway scheduler follows these steps: Figure 7 - Runway scheduler chain 1. Recorded traffic data are retrieved from the EUROCONTROL.so6 files 2, which contain flight information (callsign, aircraft model) and a few radar plots per flight of all air traffic flows over Europe for the reference simulation day. 2. Departure and arrival flights for the reference airport are extracted from the file, for the chosen timeframe. 3. Intermediate waypoints are removed, so that only the last En-Route point (or the departure / arrival airport if a direct route is possible) are kept for each aircraft. 4. Landing and take-off distances and durations are computed for each aircraft of the simulation, using Eurocontrol BADA aircraft database and according to the methodology described in [4]. 5. The optimum arrival/departure points on the runway 3 and the associated take-off/landing distances are used to compute requested runway segments A requested timeframe for take-off and landing is established, starting at the departure and arrival time from the input file and lasting the duration computed in step 4. 2 The so6 files are part of the Eurocontrol Demand Data Repository, which includes a high number of different air traffic data from Europe. A list of available Data files is available in Appendix B 3 The optimum arrival/departure point on the runway is computed taking into account the optimum entry/exit point in the TMA. An aircraft going to the South will fly on a TMA departure route going to the South. With a runway in the counterclockwise direction, this route comes from the West where aircraft lifts-off. 4 In the low wind case, buffer segments are added upwards landing segments and downwards take-off segments.

18 Page 18/69 7. The aircraft runway usage is planned sequentially, using time-shifting and space-shifting where necessary 5. During this process, wake turbulence separation is applied between aircraft pairs when applicable. Points 5 and 7 depend on the configuration of the runway, e.g. of the applicable use case. In the next paragraphs, we will detail these steps with concrete examples Low wind use case The method adopted to simulate the attribution of the runway segments along time in the low wind use case is described in the following paragraphs. It will be assumed that there is no wind at all Single departing flight Let s consider the following A320 departure flight at an Endless Runway which is operated counter clockwise. Type Departure airport Arrival airport Callsign ICAO Code Aircraft model Wake category Requested take-off time at airport First En-Route point bearing from ER airport DEPARTURE Endless runway airport LFPG LFBO (Toulouse Blagnac) AF782UM A320 Airbus A320 M 09:00: The TOL and V S are extracted from the corresponding.opf file (see Appendix A). According to [4], the A320 take-off length on the circular runway is equal to the TOL, that is to say 2,190 metres, which corresponds to segments, rounded to the upper integer, 4 segments. Consequently, 548 the additional upstream buffer (10% of this distance) is equal to 0.4 segments, rounded at one segment. 5 segments in total will be booked for this aircraft. 5 In the low wind case, if the desired segments are not available at the desired time, the program looks for the closest available ones, and if not, delays the aircraft to a later slot.

19 Page 19/69 N centre angle = 277 N α = 187 Figure 8 - Best guess departure point on an Endless Runway airport operating counter-clockwise The requested take-off roll end bearing being 187 (the aircraft heads south of the Endless Runway airport). Thus, the centre angle corresponding to the ideal take-off point is π = 277. This corresponds to 2 = 14, at the west. As 4 segments are requested for the take-off roll and as the runway is segment (277+10) oriented counter-clockwise, the first segment to be reserved is segment number (mod 18) = 17 (at the north). Considering the additional buffer segment, the runway will be reserved from segment 17 to 14-1=13. Then, the aircraft will fly on departure route 14 (as segment 13 is a buffer segment), heading south. The stall speed in take-off configuration is found equal to kts (= 57,7 m.s -1 ). The take-off duration is estimated equal to: Δt = TOL + 25 = s (00: 01: 28) 0,6 V S 0,6 57,7 Considering that the aircraft aims to start its take-off roll on the runway at 09:00:50 and that this duration includes 10 seconds to line-up from the taxiway to the runway, this means that the desired segments would ideally be booked from 09:00:40 to 09:02:18.

20 Page 20/ Single arrival flight Let s consider the following A arrival flight. Type Departure airport Arrival airport Callsign ICAO Code Aircraft model Wake category Requested touchdown time at airport First En-Route point bearing from Endless runway airport ( ) ARRIVAL LEMD (Madrid Barajas) Endless Runway airport LFPG LAN722 A343 Airbus A H 15:17: The aircraft is an A , whose performances are directly extracted from the A343_.OPF bada file (see Appendix A). Its landing length on a straight runway is 1,830 metres, increased of 12.8% for the Endless Runway ([3]) to 2,064 metres, which corresponds to 112, segments. Consequently, the additional upstream buffer (10% of this distance) is equal to 0.37 segments, rounded at one segment. 5 segments in total will be booked for this aircraft. N centre angle = 122 N α = 32 Figure 9 - Best guess arrival point on an Endless Runway airport operating counter-clockwise 360 The arrival bearing being 032 until final approach (e.g. the aircraft arrives from the South-West), the aircraft will land on the segment whose centre angles includes 32+ π = 122. This corresponds to segment number 2 (122+10) As 4 segments are requested for the landing roll and as the runway is oriented counterclockwise, the last segment to be reserved is segment number (mod 18) = 3. Considering the additional buffer segment, the runway will be reserved from segment 7 to 3. The calculation of the landing duration needs the knowledge of the stall speed in landing configuration. It can be found in the A343_.OPF file. For the A , its value is 101 kt (52 m.s -1 ).

21 Page 21/69 Δt = LDL + 5 = seconds 0,65 V S 0,65 52 Considering that the aircraft aims to have landed at 15:17:22, this means that the preferred runway segments would ideally be booked from 15:17:22 to 15:18: Orchestration The requested segments and timeslots are known for all aircraft in the simulation. Timeslots might be extended if wake turbulence separation applies, e.g. when an aircraft of a lighter category aims at using the same segments as a heavier one before. In this case, the segments are booked for a longer time, between 2 and 4 minutes (ICAO wake turbulence separation minima). Then, as described in [4], to avoid overlap in assignment of segments, the following sequential strategy is adopted. The first aircraft of the day gets the desired runway segments and timeframe For following aircraft, if the required adjoining segments are not available within the preferred timeframe, the scheduler looks for the closest available ones. If none is available, it delays the aircraft to the first available slot. The generated traffic file shows the requested timeslots for a given section of the runway, and the attributed one, and computes the delay. The following table is an extraction of the output of the runway scheduler. Aircraft model Endless Runway Initial Final Initial Closest Closest Aircraft Roll Number Number Stall Climb First Last Booking Requested Requested First Last Effective Effective Departure Arrival Other airport name Callsign ICAO Code Wake segment approach approach takeoff Nb Type category RFL cruise lat. cruise long bearing length of roll of buffer speed speed requested requested duration booking booking booked booked Delay (s) booking booking Comment airport airport (assuming speed speed speed segments ( ) ( ) ( ) (m) segments segments (m/s) (m/s) segment segment (s) start end segment segment start end counterclockwise) (m/s) (m/s) (m/s) ARRIVAL EDDM LFPG Munich International Airport AFR1423 A318 AIRBUS A318 M :59:07 09:00: :59:40 09:00:34 Follows AFR3539. Wake turbulence (H, M): 3 min DEPARTURE LFPG LFBO Toulouse-Blagnac Airport AF782UM A320 AIRBUS A320 M :00:50 09:02: :00:50 09:02:18 Shifted from 17 to 1 (2-segment shifting). ARRIVAL CYUL LFPG Montreal / Pierre Elliott Trudeau AFR349 B744 BOEING H :01:24 09:02: :01:24 09:02:24 Request granted without modification DEPARTURE LFPG EGLL London Heathrow Airport BAW307 A321 AIRBUS A321 M :01:50 09:03: :02:18 09:03:45 Follows AF782UM Figure 10 - Sequencing of traffic demand on the Endless Runway It is possible to have a graphical view of the runway segments reservation over time. In the following figure, the time in the middle of the Endless Runway-radar view is the current time. The blue boxes represent the departures, the orange ones the arrivals, with a green line as the boundary of the first booked segment and a red line as the end of the last booked segment. The first black ring is at 5 minutes and the second one is at 15 min.

22 Page 22/69 Figure 11 - ER-radar view of booked segments along time at a busy hour The graphical representation in Figure 11 was originally developed for passenger processes visualisation by DLR [13]. For the Endless Runway it was adapted to the presentation of the timely distribution of the flight at the runway. Statistics are provided by the runway scheduler regarding average and maximum delay encountered by aircraft (they do not take into account TMA or taxiing constraints) High wind use case The method to simulate the attribution of the runway segments along time in the high wind use case is described in the following paragraphs. However, due to time constraints, it was not possible to implement it in the runway scheduler, nor in Simmod PRO! or TrafficSim. We assume a strong north wind (25 kts). Therefore, the runway is operated clockwise in its western part and counter-clockwise in its eastern part.

23 Page 23/69 Figure 12 - Runway directional use with a strong North wind The runway is now operated as a conventional, two runway airport. Thus, aircraft segments reservation only depends on aircraft landing and take-off length. The aim is to lift-off and touchdown as close as possible to headwind (on Figure 12, segments 13 and 05 for takes-offs, 14 and 04 for landings), avoiding the runway area where crosswind is too strong (segments 08 to 10 and 17 to 01) and without incursion in the protected area where both runway sides converge (segments 00 and 09). The following table, in which these principles have been applied, shows which runway segments will be booked for all possible take-off and landing lengths. Table 3 - Correspondence between the TOL and LDL and runway segments reserved in the high wind case with a North wind Number of segments needed Western side Eastern side Departure Arrival Departure Arrival

24 Page 24/ Single departing flight Let s consider the same A320 departure flight as in the low wind case. Type Departure airport Arrival airport Callsign ICAO Code Aircraft model Wake category Requested take-off time at airport First En-Route point bearing from ER airport DEPARTURE ER airport LFPG LFBO (Toulouse Blagnac) AF782UM A320 Airbus A320 M 09:01: The TOL was already calculated in chapter , equal to 2,190 metres, and the number of required segments for the take-off roll to be 4 segments. Following take-off, the aircraft is heading south-south-west (bearing of 187 ), which is it in the left plan of the runway. According to the principles recalled in chapter 2.1.2, this means that the aircraft will take-off on the western part of the runway. In this case, it means of course additional track in the air as the aircraft takes-offs almost in the opposite direction as desired due to the Endless Runway operating as two parallel runways facing the wind ARP Figure 13 -Take-off segments and routes on the west side of the runway (strong North wind) As only 4 segments are necessary for the ground roll, it is possible to take-off almost at headwind: take-off roll will start on segment 11 (following forbidden segment 10 6 ) and finish on segment mod (18) = 14 (see Table 3). Then, the aircraft will fly on departure route 14 heading north until the intermediate departure point, and continue on departure route 15 before exiting the TMA and be authorized to head south. As seen previously, the take-off duration is estimated equal to 88 seconds (00:01:29). Considering that the aircraft aims to start its take-off roll on the runway at 09:01:00 and that this duration includes 10 seconds to line-up from the taxiway to the runway, this means that the runway segments would ideally be booked from 09:00:50 to 09:02:28. 6 Note that with an aircraft with a TOL covering 7 segments (maximum TOL), the take-off roll would start exceptionally on segment 10 rather than on segment 11. The formula used is changed as a consequence: an aircraft that needs 7 segments would start at segment 10 and finish on segment =16.

25 Page 25/ Single arrival flight Let s consider the same A arrival flight as in the low wind case. Type Departure airport Arrival airport Callsign ICAO Code Aircraft model Wake category Requested touchdown time at airport First En-Route point bearing from ER airport ( ) ARRIVAL LEMD (Madrid Barajas) ER airport LFPG LAN722 A343 Airbus A H 15 :18 : We have already calculated in chapter the LDL, equal to 2064 metres, and the number of required segments for the take-off roll, 4 segments. The aircraft arrives from the South West (bearing of 32 ), which is it in the left plan of the runway. According to the principles recalled in chapter 2.1.2, this means that the aircraft will land on the western part of the runway. Contrary to the departing flight seen above, in this case the aircraft air trajectory is minimised as the aircraft will land South West of the runway ARP Figure 14 - Landing segments and routes on the west side of the runway (strong North wind) As only 4 segments are necessary for the ground roll, it is possible to land on segment =13, almost headwind: landing roll will start on segment 13 and finish on segment 16 (see Table 3). As seen previously, the landing duration is estimated equal to 66 seconds. Considering that the aircraft aims to have landed at 15:18:29, this means that the runway segments would ideally be booked from 15:17:23 to 15:18: Orchestration The requested segments and timeslots are known for all aircraft of the simulation. Timeslots might be extended if wake turbulence separation applies, e.g. when an aircraft of a lighter category takes-offs or lands behind an aircraft of a heavier category. In this case, the segments are booked for a longer period, between 2 and 4 minutes (ICAO wake turbulence separation minima are used). Furthermore, two takes-offs using 7 segments are not allowed simultaneously. Requested runway segments are fixed and cannot be moved contrary to the low wind use case.the following sequential strategy is adopted on each side of the runway (independent operations). The first aircraft of the day gets the desired timeframe. For following aircraft, if the runway side is available within the requested timeframe, it takes-offs or lands at the requested time. If the runway is not available during the timeframe, the aircraft will be delayed to the end of the previous aircraft timeslot.

26 EC DG-RTD Page 26/ Terminal Manoeuvring Area Modelling of the Terminal Manoeuvring Area (TMA) can be done by different simulation tools. Based on the defined simulation framework defined in chapter 3, the DLR in-house simulation tool TrafficSim was used TrafficSim The designed TMA concept according to D4.2 [4] has many crossings of departure and arrival routes. The runway simulation only considers the capacity and limiting requirements of the runway and the segments and does not take the actual capacity of the TMA into account. Therefore, the implementation of a fast time simulation that calculates the possible trajectory and checks the flights for conflicts is necessary. Calculation of TMA entry and exit points In the resultant flight plan of the runway scheduler the touch down and take off segments are shifted to get a maximum capacity. Since the aircraft must take-off and land tangentially to the runway segment, it was necessary to add significant routing points at the border of the TMA, see Figure 15. As a consequence the aircraft can t flight a direct route but have to take a detour and overfly a TMA ENTRY or EXIT point from origin airport to the Endless Runway and the other way around ENTRY 03 (9.42 NM) 14 Endless Runway Airport ARP EXIT 10 (9.42 NM) Airport A Optimized for flight distance Route after segment shifting Enroute Segment Figure 15 - Entry and Exit Points at TMA border To implement the routing points for the shifted flight plan, the coordinates of the entry and exit points had to be calculated with the specified distance and bearing. As center of the circle the airport reference point of

27 Page 27/69 Charles De Gaulle Airport was defined. The exact coordinates for the segments and TMA constraint points are summarized in Table 12 and Table 13 in Appendix D TMA Simulation Concept and Simulation Tool TrafficSim The workflow of analyzing a traffic scenario is standardized for air traffic simulations and is presented in Figure 16. The scheduled flight plan is taken as a basis and the route is defined by adding constraints and routing points. In the TMA simulation, a unique trajectory was generated without checking conflicts between aircraft. This means, each aircraft flies an optimized independent profile and doesn t know anything about the other trajectories within the scenario. As a result of this, a high number of conflicts exist. The number of conflicts depends on the defined separation standards. A strategy for conflict resolution has to be developed, so that at the end of the simulation exercises a fully conflict free traffic scenario is implemented in the fast time simulation tool. Figure 16- TMA Simulation Concept Workflow The traffic scenario is implemented and simulated with the software TrafficSim developed by the DLR Institute of Flight Guidance. The simulation tool requires a flight plan, a constraint list including routes, speed and other information for each flight and the aircraft performance file (BADA 3.9) [6]. The simulation system models the aircraft performance, the environment, the pilot, as well as the controller. The use of fast time simulation makes an investigation of a huge scenario within a few minutes possible. The calculation of trajectories is based on the point-mass-model and logs the trajectory points in a file. The resulting trajectory files include position, speed, heading, fuel, etc. for each second in the simulation Preparation and Running the Simulation To run a simulation with TrafficSim the scheduled flight plan had to be converted in a particular text file. The structure is displayed in Figure 17. The time represents the real time at the assigned segment. The type of file is defined by the ending *.scenario.

28 Page 28/69 Segment RelTime CallSign ICAO CO_Route CFL LFPG16 05:54:50 AF620JL A319 AF620JL_LFPG_LFBD_ LFPG09 05:52:45 EZY75HV A319 EZY75HV_LFBO_LFPG_ LFPG12 05:54:45 BCY5002_3 RJ85 BCY5002_3_LFPG_EIDW_ LFPG11 05:56:07 AF660XE A319 AF660XE_LFPG_LFML_ LFPG17 05:55:59 BCY5050_2 RJ85 BCY5050_2_LFPG_EGPH_ LFPG09 05:53:43 NLY8514 A320 NLY8514_LOWW_LFPG_ LFPG05 05:53:55 AFR6881 B744 AFR6881_HKJK_LFPG_ LFPG08 05:54:54 DAL48_2 B763 DAL48_2_KBOS_LFPG_ LFPG00 05:55:59 VLG8202 A320 VLG8202_LEMD_LFPG_ LFPG15 05:58:14 AFR138A A319 AFR138A_LFPG_LOWW_ Figure 17 - TrafficSim scenario file For each flight a unique constraint file has to be created. For example, the routing information of the flight with the callsign AF620JL must be defined in the file AF620JL_LFPG_LFBD_16.cstr (Figure 18). The file defines all necessary information like waypoints, type of descent and type of turn. LFPG16 and EXIT16 as waypoints indicate the take-off segment and the TMA point that has to be overflown. Company Route : AF620JL_LFPG_LFBD_16 Take off Time : LFPG16 05:54:50 Cruise Flight Level : 290 Departure Airport Name : LFPG Runway Name : Segment 16 Speed Restr Alt : Transition Alt : 5000 TMA NA Lmt Alt : 2000 Runway Threshold : 183 Runway Latitude : Runway Longitude : Arrival Airport Name : LFBD Runway Name : LFBD Speed Restr Alt : Transition Alt : 5000 TMA NA Lmt Alt : 1684 Runway Threshold : 364 Runway Latitude : Runway Longitude : Descent Specification Descent Kind: Continuous_Descent Start Of Steep Descent : 0 Intercept Alt : 4000 Glideslope Angle : 3.0 Level_at_Gate : 5.0 Waypoints Nr, Name, Lat, Long, Turn, Radius 1 LFPG mot EXIT sot LFBD mot 2.00 Figure 18 - TrafficSim Constraint file for flight AF620JL

29 Page 29/ Checking for Conflicts An additional script checks if the scenario includes conflicts based on the trajectory and parameter settings. The main parameters for the conflict checker are displayed in Figure 19. In the simulation file endless_runway_scenario.tin the requested lateral and vertical separation are set. /****************************************************************************** / Conflicts / Lateral_Sep: requested lateral separation / Level_Vertical_Sep: requested vertical separation in case both / aircraft are in level / Vertical_Speed_Vertical_Sep: requested vertical separation in case at least / one aircraft has a vertical speed / Lower_Alt_Threshold consider only trajectory data above / /****************************************************************************** LOAD endless_runway_scenario.tin CALC_CONFLICTS Lateral_Sep: 1.5 NM Level_Vertical_Sep: ft Vertical_Speed_Vertical_Sep: ft Lower_Alt_Threshold: 5.0 fl Figure 19 - Setup for the conflict checking script Running the conflict script, results in a table that includes a row for each single conflict. In Table 4 you can see a part of the conflict parameters. The conflicts are represented by two aircrafts, the duration of conflict and the position of the conflict. The original table includes additional parameters like altitude, altitude rate and the track. Table 4 - Conflicts Table Callsign WTC Callsign WTC Start Conf (hh:mm:ss) End Conf (hh:mm:ss) Conflict Start Coordinates [degree] Conflict End Coordinates [degree] Flight 1 Flight 2 Flight 1 Flight 2 Flight 1 Flight 2 FDX5083 M UPS218 H 02:29:10 02:29: ABR2CL M BCS6848 M 02:36:05 02:36: AWE754 H EZY2DA M 05:17:26 05:17: LOT334 M TSC488 H 05:32:17 05:32: AAL146 M AFR1000 M 05:33:43 05:33: Conflict Resolution There are different possibilities to handle the conflict resolution. One possible way is to implement a vertical separation level segment. First results from the conflict detection showed, that most of the conflicts occur shortly after departure. In this phase it is not possible to implement an additional separation level and therefore this method is not applicable. Hence, a trivial method was used to solve the conflicts by deleting one of the conflict partners. As some flights are involved in more than one conflict, an algorithm deletes that one of a conflicting pair that has more following conflicts than the other one.

30 Page 30/69 For the final scenario, the traffic was simulated conflict-free with a separation of 1.5 NM lateral or 500 ft vertical. The conflicts have been resolved by an algorithm that identifies the flights with the most conflicts and deletes it. Afterwards the iterative process starts the analysis again, until all conflicts are resolved. By the use of this method as few as necessary flights were deleted. Another resolution algorithm developed by DLR [7]postpones one of the conflict partners for few seconds up to a maximum of +/- 5 minutes. However, this would possibly result in a conflict on the runway. Therefore and because of a high effort, a deconflicting by the use of this advanced algorithm was not possible in the frame of the Endless Runway project but could be lead to optimized capacity values in possible further investigations Extensible Workflow Management for Simulations Due to the concept of shifting of runway segments when the originally planned is blocked, it is interesting to study the effect in flight distance, flight duration and fuel consumption. For the reporting of fast time simulation data the evaluation environment Extensible Workflow Management for Simulations (EWMS), developed by the DLR, was used. The EWMS-Software streamlines and simplifies simulation data management significantly to reduce the effort required to analyze simulation results. It provides a large number of validated analysis algorithms [9]. The best way to investigate trajectories generated by the TrafficSim offers the implemented concept for determination and visualization of significant trajectory parameters. The concept was modified for the Endless Runway concept to generate useful quantitative (diagrams) as well as qualitative (geospatial imaging) visualizations. For the representation of scalar values, charts generated by JFreeChart- Tool [10] are suitable. NASA World Wind [11] is used for the geographical visualization of trajectories. 3.3 Ground A third component for the simulation of the Endless Runway is the ground movement. In D2.2 [2] the design of the airport layout has been developed defining the infrastructure available for aircraft ground traffic. The ground simulation is intended to give an indication on how a specific airport configuration is able to accommodate the requested traffic from prior simulations. As shown in Figure 6 the ground movement simulation uses data from the runway scheduler, the taxiway/stand layout and the ground movement concept as major inputs. Combined with specific aircraft taxi performance parameters, a simulation in Simmod PRO! has been prepared. The chosen software tool uses rule-based simulation algorithms that allow a straightforward handling of each flight movement phase. In principle, the approach of the ground movement simulation can be described as follows: 1. Aircraft movements will be specified in the simulation as they are delivered by the runway scheduler (arriving traffic = end of segment booking; departing traffic = specified amount of time prior to begin of segment booking). 2. Aircraft will move along taxi routes as defined in D4.2 with respect to the circulation map, which reflects the taxiway usage concept. 3. Aircraft will be parked at a preselected stand to release/pick up passengers or freight, refuel etc. for a specific time (based on required minimum time or linked turnaround flight information if available) Taxiway Usage The layout and the rules for using the taxiways of the endless runway were specified in D4.2 and correspondingly implemented in the simulation. At this point parameters concerning aircraft s performance were added. Regardless of the aircraft type a standard taxi speed of 15 kts was set for all taxiway segments of the airport, exceptional high-speed exits that are used at an average speed of 35 kts. Another special

31 Page 31/69 procedure has to be considered with the push-back since all stands are designed as terminal positions. In this case a taxi speed of 3 kts was used combined with an additional duration of 90 s modelling the release of the tug. Thereby the concerned aircraft are pushed back onto the outer taxiway of the inner apron area Turnaround Modelling For the evaluation of the ground structure the knowledge of the turnarounds is important. Arrivals and departures are connected as one physical aircraft blocking ground resources for specific time windows. Especially the required number of gates depends heavily on the turnaround times of the flights. Not only the hourly departure and arrival numbers are relevant but also the number of aircraft that stay on the ground during this period due to longer turnaround times or overnights. For the runway scheduler and the TMA simulation Eurocontrol s s06 were used. As there is no rotation information in the file, linking arriving and departing aircraft at an airport, turnaround information have to be worked out separately. To establish the link between an arrival at and a departure from the same gate, it will be necessary to use additional. One possibility was to use the aircraft registration, as this is a unique identifier. For this reason the exp2 data file (part of the Eurocontrol DDR - Demand Data Repository see Appendix B) was analyzed. This file type contains aircraft registrations and can be easily matched with existing so6 files. Thus, whenever possible, the aircraft registration number was used to match arriving and departing flights at the Endless Runway Airport (TERA). The following results could be achieved for the analyzed traffic sample (see Table 5). Table 5 - Aircraft registration analysis results Movements at TERA (Runway Scheduler Demand 1.0) Detected registrations (exp2 data) Matched flight pairs at TERA Departure Arrival Departure Arrival Departure -> Arrival 1 Arrival -> Departure : Departure -> Arrival: reverse turnaround : Aircraft registration departs from TERA, stays somewhere and returns to TERA once. 2 : Arrival -> Departure: Aircraft registration arrives at TERA, stays there and departs at a specific time. As indicated in the detected registrations column of Table 5, only for 50% of the flights aircraft registration data were available. Therefore a considerable number of unmatched flights are left, that needed further investigation. In this context a heuristic algorithm using other information e.g. aircraft type and company was developed to improve the hit ratio.

32 Page 32/ Stand Selection The ground movement concept proposes a 4-Terminal-Layout offering an overall number of 294 stands. Each stand in the simulation is designed as a triple aircraft position that can either be used by one Code E or F aircraft or two smaller aircraft simultaneously (see red dots in Figure 20, taxiways in grey). Figure 20 - Endless Runway available aircraft stands in ground simulation Beyond that the ATM operational concept determines that aircraft taxiing times shall be minimized. So, a first task to be solved is to find a suitable stand for each aircraft. Based on the assumptions above the initial approach was to park aircraft next to the point they are exiting/entering the runway. Since most of the flights are linked turnaround flights and towing is not considered a stand can either be optimized for the arrival or departure part of a flight. For this study the runway exit point was chosen as the reference (for departure without prior arrival = runway entry point).

33 Page 33/69 4. DOW Simulation results and analyses Simulations will be carried out. As much as possible recordings will be made, including those of internal events, to enable analysis of the results and to measure the effect of new operations. This will be the base for the impact considerations in WP Runway The output of the runway scheduler is a flight plan, with a detailed description of the every single flight. With increasing demand, the runway system is not able to handle the traffic anymore without delaying some of the flights. This delay is recorded and can be used as a parameter to determine the runway capacity. When a defined delay value is exceeded the runway capacity is reached. Different traffic scenarios were used in the simulation leading to the following results: Traffic ratio Table 6 - Average and maximum delay encountered by aircraft for various input traffic Number of flights Max fligts per hour Average delay with wake rule (h:min:s) Max delay with wake rule (h:min:s) 100.0% :00:21 00:04: % :00:33 00:07: % :01:16 00:09: % :03:41 00:20: % :12:53 00:41: % :27:31 01:04: % :37:43 05:11:33 It can already be seen that exceeding 110 movements per hour is not acceptable in terms of delays if it is required that delays should not exceed 5 minutes. Therefore, from the runway point of view, the maximum capacity is established at 110 movements per hour. In addition, the distribution of the delay over the day gives a clear indication of the problem with the increasing demand. Figure 21 presents the delay for the Traffic scenarios 1.0, 1.5 and 2.0. The 1.0 delay is o very low o almost constant over the day o is 0 at the end of the (all flights have been handled) The 1.5 delay is o significantly higher than 1.0 o is increasing during the day with a peak at 1pm o is decreasing in the second half of the day o is 0 at the end of the (all flights have been handled) The 2.0 delay is o Extremely higher than 1.0 and 1.5 o Is increasing during the day with a peak at 8 pm o Is decreasing in the evening hours o Is still at 200 minutes at the end of the day (some of the flights have to be moved to the next day)

34 Page 34/69 Figure 21 - Traffic scenario 4.2 TMA Conflicts As described in a script has been developed that checks whether the scenario includes conflicts based on the trajectory and parameter settings. Three separation criteria are applied, leading to a different number of conflicts. The criteria are applied to three scenarios ranking from the current-day LFPG demand to double this demand. To sum up the findings, Table 7 shows the number of conflicts within the TMA for the traffic scenarios 1.0, 1.5 and 2.0 for three different separation setups. Table 7 - Number of conflicts in TMA with different separation standards #Conflicts inside 9NM radius Separation [2NM; 1000ft] #Conflicts inside 9NM radius Separation [1.5NM; 1000ft] #Conflicts inside 9NM radius Separation [1.5NM; 500ft] Demand Demand Demand The following figures demonstrate the conflicts in the given scenarios. Figure 22 shows the double-demand scenario where all flights during the simulation run are visualized through a line in the figure. Conflicts between flights are highlighted in red. Figure 23 shows a limited number of flights where one conflict situation between a departing and an arrival aircraft has been highlighted.

35 Page 35/69 Figure 22 - Traffic scenario (increased 2.0) with visualization of the conflicts (separation 1.5 NM or 1000 ft) Figure 23 - Representative example of arrival-departure conflict

36 Page 36/69 As described in flights have been deleted that causing conflicts. As some of the flights causing more than one conflict the number of conflicts and the number of deleted flights are different. The following Table 8 summarizes this correlation. Table 8 - Number of deleted flights to resolve the conflicts Traffic scenario Number of conflicts Number of deleted flights Demand Demand Demand The deletion of flights leads to a conflict free flight plan in TMA but reduces the number of flights and therefore the capacity values Capacity Capacity analyses have been performed to get an indication, if the Endless Runway can handle comparable traffic as today s airports. To get the results different demand scenarios have been setup and used in the simulations. It should be stated, that the results are only a first indication. A full capacity evaluation is much more complex, as different capacity values exist. With the simulation setup described in chapter 3, three simulation runs have been performed. First a traffic demand that is the same as LFPG (Scenario 1.0), then a 1.5 fold increased demand (Scenario 1.5) and finally a 2 fold demand (scenario 2.0). The additional demand was generated by cloning original flights from the Eurocontrol data for LFPG. The following figure presents the generated demand distribution for the three scenarios.

37 Page 37/69 Figure 24 - Traffic Demand Chart Figure 25 - Traffic Demand Data Table Hour Scenario Sum , , ,140 The busiest hour (from 08:00 to 9:00) has 110 movements. The additional generated traffic leads to a demand of 177 for the 1.5 scenario and 222 for the 2.0 scenario. This demand is used as an input to the runway scheduler. Following the steps described in chapter 3 the runway scheduler delivers a conflict free flight plan by optimizing the traffic demand to the available runway resources. The following figure presents an overview of the traffic distribution after the runway scheduler tool.

38 Page 38/69 Figure 26 - Runway Schedule Chart Figure 27 - Runway Schedule Data Table Hour Scenario Sum , , ,708 In the 1.0 scenario (blue line) the demand can be handled by the runway. During the highlighted time interval (8:00 to 9:00), the runway scheduler plans 109 movements with a demand of 110 (see Figure 24). The situation changes with the increased traffic scenario. The demand of 177 and 222 (see Figure 24) movements cannot be handled anymore in this hour and has to be delayed. Due to the higher traffic demand in the previous hours flights have to be shifted in time. The timely distribution of the peaks is also changing. The runway scheduler produces a runway conflict free flight plan that is used as the input for the TMA simulation. As described before, this flight plan leads to conflicts in the TMA. Removing flights to get a conflict free flight plan in the TMA also, results in a reduced number of movements for the TMA. Figure 28presents the results from the TMA simulation with the TrafficSim tool.

39 Page 39/69 Figure 28 - TMA Simulation Chart Figure 29 - TMA Simulation Data Table Hour Scenario Sum , , ,932 For the selected time interval the number of movements changes from 109 to 83 for the 1.0 scenario, from 130 to 94 in the 1.5 scenario and from 136 to 97 in the 2.0 scenario. As a rough estimation a reduction of 25% occurs. The following chart summarizes the capacity analyses. For the three traffic scenarios the values for demand, runway scheduler and TMA simulation are combined. All blue line colors are related to the 1.0 scenario, the orange colors to the 1.5 scenario and the green colors to the 2.0 scenario.

40 Page 40/69 Figure 30 - Runway Schedule Chart In Appendix F some more detailed graphs are available, separating the number of movements into departures and arrivals. In addition a slightly different approach is taken for calculating the numbers. In the previous figures a one hour interval was used for calculation for easier presentation. Besides this, an analysis in a moving time interval was conducted. The capacity was calculated every five minutes with a one hour time interval. With this approach a more smoothed curve of the capacity graph could be reached Flight Distance and Duration As a basic idea for the Endless Runway is was considered, that flights can have the most direct flight profile from and to the ER-airport. The runway segments for landing and take-off are selected to have the shortest flight distance. As the runway scheduler optimizes the runway capacity also by shifting flights from blocked to available segments, this approach is not valid in all cases. With the shifting flight distance and flight duration may change. To get a first estimate on the effects a number of flights have been analyzed in detail. Five different flights from the Endless Runway Airport (TERA) to Frankfurt (EDDH) via a direct route from TMA Exit point to Frankfurt airport have been investigated. As presented in Figure 31, all flights have different departure segments. The green line is used as the reference trajectory as it represents the optimal situation. The last booked segment of this flight is segment 8. This means that the aircraft departs at segment 7 and flies the shortest route of the selected flights. The red lines are the trajectories of the comparison flights, where the departure segments have been shifted by the runway scheduler.

41 Page 41/69 Figure 31 - Flights from the endless runway Airport to Frankfurt (Top view) Figure 32 - Flights from the endless runway Airport to Frankfurt (3D and vertical profile view)

42 Page 42/69 Using the EWMS the following flight distances have been calculated (Figure 33): Flights TERA to EDDF Flight Distance [NM] DLH8F DLH5J ABR6TR DLH2J_2 DLH2F Callsign Figure 33 - Flight Distance from endless runway to Frankfurt in NM In addition to the flight distance the flight duration can be calculated by using aircraft performance data (Figure 34). Figure 34 - Flight Duration of Flights to Frankfurt in seconds

43 Page 43/69 The increased flight duration responds to the aircraft type of ABR6TR. While all other flights are operated by jet aircraft this one is a turboprop. In addition to flight distance and flight duration the fuel flow was calculated. The following Table 9 recaps the results of the investigation. Table 9 - Summary of different parameters Callsign Aircraft Type Last Booked Segment Distance [NM] Duration [mm:ss] Fuel [kg] DLH8F A :27 1,957 DLH5J A :55 1,933 DLH2J_2 A :17 1,905 DLH2F A :43 1,881 ABR6TR ATR : For better comparison the flight ABR6TR was then replaced by an A319 aircraft and simulated again, leading to the following values: Callsign Aircraft Type Last Booked Segment Distance [NM] Duration [mm:ss] Fuel [kg] DLH2F_3 A :46 1,839 Comparing DLH8F and the new DLH2F_3 flight, a difference of 19NM, 02:41 minutes and 118kg of fuel is calculated. The increased values of the not optimal trajectory have to be assessed against the shifting of segments. 4.3 Ground The ground simulation has been run with the traffic scenario 1.0. The following figure Figure 35 presents the simulation with the ground movement concept as a background image and the aircraft objects moving along the taxiways or at the stand.

44 Page 44/69 Aircraft at the Gate Arrivals moving along the taxiways according to the concept Figure 35 Screenshot of the SIMMOD simulation. First results of the simulation showed, that the ground movement is also very complex and aircraft movements interfere. Especially pushbacks lead sometimes to blockings that cause delays during taxiing. In WP 2 calculations about the required number of gates have been conducted [2]. From the theoretical perspective the airport layout and the number of gates have been expected to be sufficient. Taking into account the results from the turnaround modeling it seems that the number of gates is not enough for the traffic demand from LFPG. Table 10 - Stands occupied by time Time 05:00:00 08:00:00 12:00:00 14:00:00 No. stands occupied Due to long turnarounds and blocking of gates, there might be no gate available for arriving aircraft. As Table 10 indicates, at 8 o clock in the morning 158 stands are already occupied. As the number of available stand depends on the aircraft type, this can lead to problems. During peak hours with a high number of long haul flights only 96 stands for aircraft code E or F are available. A more detailed analysis was carried out confirming the lack of stand capacity. The following Figure 36 presents the results, clearly indicating, that in the time frame from 6 o clock to 11 o clock more stands are required than available.

45 Page 45/69 Stand usage for non Code E/F prioritized allocation occupied by other occupied by code E/F available for Code E/F number of stands Time Figure 36 Stand usage analysis A check on the available stands at LFPG indicated that the number at LFPG is significantly higher. From this perspective the selected LFPG scenario is not directly adaptable to the provided endless runway ground infrastructure concept. One solution could be to use some space in the inner airport area for additional stands and move some of the airport facilities to the outside. In [2] future airport expansion possibilities are addressed and approaches for additional stands are presented. Using the 1.0 traffic scenario and the implemented turnaround model the ground simulation with SIMMOD could not be executed successfully. The limited number of stands lead to the effect, that aircraft had to wait for parking on the taxiway system, blocking other ground movements. Finally deadlock situations occurred causing the simulation to freeze. With this situation no further evaluation was possible. To overcome this problem different approaches have been thought of. While some of them would require a complete new iteration of all conceptual work and simulations (e.g. redesign of the airport) some others could be realized with acceptable modifications. Finally it was decided to modify the 1.0 scenario. Analyses have shown that the number of heavy aircraft is consuming a high number of the gate capacity and might be the main reason for the problems. Therefore a very pragmatic approach was taken by replacing all heavy aircraft with medium type aircraft. Even this is not acceptable in terms of the chosen scenario it helps to gather some information on the taxiway system. It is assumed, that the behavior of movements of heavy and medium aircraft are comparable while moving on the ground. With this configuration the simulation was successful and could be run without interruption. Based on this adaption it can be summarized, that the concept of the taxiway rings and the inner circulation setup seems to be feasible and not a limiting factor.

46 Page 46/69 The following results for taxi times have been obtained from the ground simulation runs. Figure 37 Taxi Times distribution see also Annex F for charts Figure 37 illustrates the distribution of the taxi times. Two values are presented. One is the overall taxi time (including stoppings) and the other one the net taxi time which represents only the time the aircraft is moving. While taxi-in times (blue lines) do not vary very much between overall and net there are significant differences for taxi-out times (red lines). In addition the following Table 11 presents minimum, maximum and average values for the given taxi-in and taxi-out times. Taxi-out Taxi-in Table 11 Taxi Times Min. Time [s] ([min]) Max. Time [s] ([min]) Avg. Time [s] ([min]) overall 325 (5.4) (23.7) 684 (11.4) net 235 (3.9) 745 (12.4) 506 (8.4) overall 89 (1.5) 730 (12.2) 360 (6.0) net 86 (1.4) 600 (10) 350 (5.8) The taxi-in times are in a good range. An average of 6 minutes for the overall time is a very good value. The maximum taxi-in time is 12.2 minutes but most of the flights do not exceed a 10 minutes limit. As already mentioned, taxi-out times for total and net are significantly different. While the average taxi times still provide good values, the maximum time is quite high. In addition, the high taxi times have a significant frequency so they cannot be neglected as a special situation. Analyzing the results, the allocation algorithm that is used in SIMMOD is one important factor. For arrivals the stand is selected, that is available and can be reached at the first possible time. For departures the stand, the runway entry segment and the runway entry time is fixed by the simulation and the traffic scenario. Therefore only the taxi-out route can be adapted by the simulation. As a result the stand optimization is based on the inbound traffic leading to higher taxi-out times compared to taxi-in.

47 Page 47/69 One critical step in the simulation setup is the off-block time of the departure traffic. While usually the offblock time is given as a parameter and the runway lineup results in the addition of the taxi time, the situation with the runway scheduler is different. Relevant is the time, the scheduler has blocked the requested runway segments. At this time the departure has to be ready for line-up. This would result in a backward calculation for the requested off-block time, possibly provided by a surface management tool. As this is not available in the SIMMOD environment the off-block time had to be defined by a fixed value of 15 minutes before line-up. As discovered from the net taxi-out times this was assumed to be an acceptable time buffer for all aircraft to be at the runway entry in time. If the lineup position is reached to early the aircraft will wait for the scheduled take off time at the entry segment. In some circumstances this had led to the effect that the sequence for a specific runway segment was mixed up. Due to shorter taxi distances (other stand) the number two aircraft arrived first at the segment. As the number one aircraft cannot overtake it is blocked and has to wait. Even both aircraft would have arrived the lineup position in time, the earlier scheduled flight cannot use the segment and discovers a stopping delay which leads to the high taxi delays. As a second result it has been observed, that the simulation mainly uses the ring behind the outer terminal stands for departures as this is the fastest route. Due to pushback operations to this ring, stoppings occur, that have a negative effect to the taxi-out time. Experimenting with cost functions to force different usages had no significant effect. Other routes were used but the overall taxi times did not change. The most inner ring was implemented in the simulation as a taxiway only, with no connections to the gates. The intention was to allow aircraft, heading for the opposite area of the airport, to pass by when pushbacks are in progress. During the simulation runs it became clear, that the most inner ring was not used at all with this setup. Obviously operations that are directly heading for the outer rings are favored. Based on the chosen setup the most inner taxiway ring can be left out, allowing more space in the inner area of the airport. To get benefit of the most inner ring the simulation setup needs to be changed. The stands have to be connected and the taxiway usage concept as to be adapted. This was not possible in the remaining time of the project. An overall optimization, covering the planned arrival and departure segment for a flight, should be in place to optimize taxi times. This would be directly related to the benefits of the Endless Runway concept and the proposed ground structure. Due to time and budget constraints this optimization algorithm could not be implemented at this stage.

48 Page 48/69 5. Conclusion This document contains the simulation and analyses of the Endless Runway. It has been set up based on the ATM concept developed in Tasks 4.1 and 4.2 of WP4 and in coordination with the work that is performed in WP2 and WP 3 of the project. The document describes the simulation approach, the scenario setup, the simulation tools and the results obtained by running the simulations. Scenario definition Two scenarios have been defined for operating the Endless Runway. A low wind scenario (winds below 20 kts) where all segments of the runway can be used for arrival and departure operations. This is the most demanding case as the system operates at the limits. In the high wind use case (wind above 20kts) some segments are not available for all operations anymore. The Endless Runway is then operated as a runway system with two parallel runways. For the simulations only the high wind case is considered as it was not possible to implement both use case with their different operational concepts into the simulation. As a base for the scenarios, real flight data from Eurocontrol were used. Paris Charles de Gaulle was selected as a comparable airport in terms of traffic demand in hub airport operations. Flight plans for the endless runway have been processed and artificially increased by adding virtual flights to evaluate the capacity limits of the Endless Runway. Modelling and simulation framework In accordance with D4.2 three areas have been evaluated: the runway, the TMA and the ground movement area. For each of them a separate simulation tool was selected, as one single tool cannot handle all required concept elements. The developed runway scheduler has been defined as the master, providing the optimized and conflict free flight plan (related to the runway) for the simulations of TMA and ground. Standardised BADA data have been used for aircraft performance characteristics. Some of the parameters have been adapted by results of WP3. Especially landing and Take-Off distances need to be corrected because of the banked nature of the runway. TMA and ground simulation take the flight plan and simulate the traffic with the given time and segment restrictions. The DLR TrafficSim tool has been used for the TMA simulation. The conceptual elements of the route structures and TMA entry and exit points have been integrated. Additional routing points have been implemented to allow the aircraft to enter the TMA at the entry points correctly. For ground operations Simmod Pro! was used. All related elements of the airport layout, like taxiways and stands have been implemented and the ground movement concept for the low wind scenario has been setup. Special attention has been taken to the modelling of the turnaround, which was not available from the original data files. The turnaround (rotation) of physically the same aircraft has a significant effect on the capacity of the ground structure as stands may be blocked for longer times. Simulation and analyses The runway scheduler provides a conflict free scenario for the low wind case. For different traffic demands the resulting delay was calculated. With increasing demand the delay increases significantly. While the delay stays in acceptable limits for the 1.0 scenario (corresponding to today s Charles de Gaulle traffic), it exceeds the defined 5 minute threshold already with a 10% traffic increase. The capacity from the runway part is therefore set to the maximum hourly movements of the 1.0 scenario, which is 110. The TMA simulation was run with three traffic scenarios. The 1.0 traffic demand, the 1.5 fold increase and the doubled traffic scenario. The separation criteria have been set to 1.5NM lateral and 500ft vertical. Because of the complex crossing route structure in the TMA a number of conflicts between flights occur. A straight forward method was used, to eliminate the conflicts by deleting on of the flights of a conflicting pair. This leads to conflict free scenarios in TMA but reduces the number of movements that have been handled. The

49 Page 49/69 maximum number of movements per hour in the TMA was handled with the 2.0 traffic demand as an input reduced by the conflicting flights. A number of around 110 movements could be achieved also in the TMA under best circumstances. This is comparable to the runway limit. The ground simulation has only been run with the traffic scenario 1.0 which is the original traffic from Paris Charles the Gaulles. As a first result the number of stands might be a problem as the ground simulation shows blockings and deadlocks for moving aircraft. Long turnarounds block the stands and limit the number of available stand for new arrivals. A solution could not be found so far. One option would be to make room for additional stands in the centre of the airport and move some facilities to the outside. To obtain any result of the ground simulation, the traffic scenario was changed. All heavy aircraft have been replaced by medium types and the simulation could be run successfully. As a result, taxi in and taxi out times could be analysed. All values are comparable to today s operations or even better (especially hub airports). All simulations of the Endless Runway from the ATM perspective have given a first indication that the concept is generally feasible but could be limited compared to today s high traffic operation. A few assumptions in terms of separation had to be made, to allow the multiple use of the runway. The chosen traffic demand of Paris Charles de Gaulle with a number of 1570 movements per day and a maximum of 110 movements per hour seems to be close to the limits of the Endless Runway. A higher number of movements tend to not acceptable delays for flights and a high number of conflicts in the TMA. The selected framework with different simulations was the only possible approach within the frame of the project. A consistent simulation environment with optimization taking into account runway, TMA and ground, could probably lead to a harmonized traffic and better results. The simulations and analyses presented here will be the base for the evaluation of the impact of the Endless Runway that will be carried out in WP5.

50 Page 50/69 6. References [1] The Endless Runway DoW, Hesselink, H.H., [2] D2.2 The Endless Runway Airport Infrastructure, Remiro Albert, et.al., version 1, August 2013 [3] D3.2 The Endless Runway Aircraft Aspects, Schmollgruber Peter, et.al., version 1, August 2013 [4] D4.2 The Endless Runway ATM Concept, Loth Steffen, et.al., version 2, September 2013 [5] Witt, G.A.A., Well-rounded Improvement of Airport Capacity, analysing the Endless Runway Concept, Amsterdam, May 2013, NLR-TR [6] User manual for the Base of Aircraft Data (BADA), Report No , revision 3.8, Eurocontrol Experimental Centre [7] Kuenz, Alexander, Efficient Conflict Detection and Resolution for 4D Air Traffic Management, German Aerospace Center (DLR), Braunschweig, [8] Edinger, Christiane, Angela Schmitt, Rapid Prototyping for ATM operational concepts development, German Aerospace Center (DLR), Braunschweig, [9] Scharnweber, Alexander, S. Schier, Automated Simulation Data and Process Management for Heterogeneous Air Traffic Management Simulations, German Aerospace Center (DLR), Braunschweig, [10] Gilbert, David, The JFreeChart Class Library Developer Guide, Object Refinery Limited, United Kingdom, [11] Hogan, Patrick, NASA World Wind Java Software Development Kit, NASA Ames Research Center, 2009, [12] DDR Reference Manual Version 1.5.8, Eurocontrol, 2010 [13] Urban B., Rudolph F., Helm, S. M., Development of an HMI to Monitor and Predict Passenger Progress in the Landside Process Chain for a Holistiv Airport Management, Deutscher Luft- und Raumfahrtkongress 2013 Proceedings, Berlin 2012.

51 Page 51/69 Appendix A Data extraction from the BADA files BADA OPF file (example for the A320): CCCCCCCCCCCCCCCCCCCCCCCCCCCCCC A320.OPF CCCCCCCCCCCCCCCCCCCCCCCCCCCC/ CC / CC AIRCRAFT PERFORMANCE OPERATIONAL FILE / CC / CC / CC File_name: A320.OPF / CC / CC Creation_date: Apr / CC / CC Modification_date: Mar / CC / CC / CC====== Actype ======================================================/ CD A320 2 engines Jet M / CC A with V2500 engines wake / CC / CC====== Mass (t) ====================================================/ CC reference minimum maximum max payload mass grad / CD.64000E E E E E+00 / CC====== Flight envelope =============================================/ CC VMO(KCAS) MMO Max.Alt Hmax temp grad / CD.35000E E E E E+03 / CC====== Aerodynamics ================================================/ CC Wing Area and Buffet coefficients (SIM) / CCndrst Surf(m2) Clbo(M=0) k CM16 / CD E E E E+00 / CC Configuration characteristics / CC n Phase Name Vstall(KCAS) CD0 CD2 unused / CD 1 CR CLEAN.14050E E E E+00 / CD 2 IC E E E E+00 / CD 3 TO 1+F.11210E E E E+00 / CD 4 AP E E E E+00 / CD 5 LD FULL.10130E E E E+00 / CC Spoiler / CD 1 RET / CD 2 EXT.00000E E+00 / CC Gear / CD 1 UP / CD 2 DOWN.38000E E E+00 / CC Brakes / CD 1 OFF / CD 2 ON.00000E E+00 / CC====== Engine Thrust ===============================================/ CC Max climb thrust coefficients (SIM) / CD.14231E E E E E-02 / CC Desc(low) Desc(high) Desc level Desc(app) Desc(ld) / CD.10847E E E E E+00 / CC Desc CAS Desc Mach unused unused unused / CD.31000E E E E E+00 / CC====== Fuel Consumption ============================================/ CC Thrust Specific Fuel Consumption Coefficients / CD.75882E E+04 / CC Descent Fuel Flow Coefficients / CD.89418E E+05 / CC Cruise Corr. unused unused unused unused / CD.96358E E E E E+00 / CC====== Ground ======================================================/ CC TOL LDL span length unused / CD.21900E E E E E+00 / CC====================================================================/ FI /

52 Page 52/69 BADA OPF file (example for the A ): CCCCCCCCCCCCCCCCCCCCCCCCCCCCCC A343.OPF CCCCCCCCCCCCCCCCCCCCCCCCCCCC/ CC / CC AIRCRAFT PERFORMANCE OPERATIONAL FILE / CC / CC / CC File_name: A343.OPF / CC / CC Creation_date: Apr / CC / CC Modification_date: Feb / CC / CC / CC====== Actype ======================================================/ CD A343 4 engines Jet H / CC A with CFM56 5C4 engines wake / CC / CC====== Mass (t) ====================================================/ CC reference minimum maximum max payload mass grad / CD.21000E E E E E+00 / CC====== Flight envelope =============================================/ CC VMO(KCAS) MMO Max.Alt Hmax temp grad / CD.33000E E E E E+03 / CC====== Aerodynamics ================================================/ CC Wing Area and Buffet coefficients (SIM) / CCndrst Surf(m2) Clbo(M=0) k CM16 / CD E E E E+00 / CC Configuration characteristics / CC n Phase Name Vstall(KCAS) CD0 CD2 unused / CD 1 CR Clean.14200E E E E+00 / CD 2 IC E E E E+00 / CD 3 TO 1+F.10800E E E E+00 / CD 4 AP E E E E+00 / CD 5 LD FULL.10100E E E E+00 / CC Spoiler / CD 1 RET / CD 2 EXT.00000E E+00 / CC Gear / CD 1 UP / CD 2 DOWN.27000E E E+00 / CC Brakes / CD 1 OFF / CD 2 ON.00000E E+00 / CC====== Engine Thrust ===============================================/ CC Max climb thrust coefficients (SIM) / CD.38118E E E E E-02 / CC Desc(low) Desc(high) Desc level Desc(app) Desc(ld) / CD.56674E E E E E+00 / CC Desc CAS Desc Mach unused unused unused / CD.30000E E E E E+00 / CC====== Fuel Consumption ============================================/ CC Thrust Specific Fuel Consumption Coefficients / CD.62965E E+04 / CC Descent Fuel Flow Coefficients / CD.31094E E+05 / CC Cruise Corr. unused unused unused unused / CD.92082E E E E E+00 / CC====== Ground ======================================================/ CC TOL LDL span length unused / CD.27650E E E E E+00 / CC====================================================================/ FI /

53 Page 53/69 Initial approach, final approach and climb speed calculation We take the example of the A For the initial approach, final approach and climb speed calculation, we read the BADA.PTF file. BADA PERFORMANCE FILE Apr AC/Type: A343 Source OPF File: Feb Source APF file: Mar Speeds: CAS(LO/HI) Mach Mass Levels [kg] Temperature: ISA climb - 250/ low cruise - 250/ nominal Max Alt. [ft]: descent - 250/ high =========================================================================== =============== FL CRUISE CLIMB DESCENT TAS fuel TAS ROCD fuel TAS ROCD fuel [kts] [kg/min] [kts] [fpm] [kg/min] [kts] [fpm] [kg/min] lo nom hi lo nom hi nom nom nom =========================================================================== ===============

54 Page 54/69 V(initial approach) V(initial approach) = average TAS(DESCENT) between FL 080 and FL 030 As there is no value for the FL 090, we interpolate twice. TAS DESCENT,FL TAS DESCENT,FL80 + TAS V(initial approach) = 2 DESCENT,FL = 2 TAS DESCENT,FL TAS DESCENT,FL TAS DESCENT,FL V(initial approach A ) == 271 kts 4 V(final approach) V(final approach) = average TAS(DESCENT) between FL 030 and FL 0 V(final approach) = TAS DESCENT,FL TAS DESCENT,FL V(final approach A ) = = 183 kts 2 V(climb) V(climb) = average TAS(CLIMB) between FL 0 and FL090 TAS CLIMB,FL TAS CLIMB,FL80 + TAS V(climb) = 2 CLIMB,FL 0 2 = 2 TAS CLIMB,FL 0 + TAS CLIMB,FL TAS CLIMB,FL V(climb A ) = = 226 kts 4 V(initial take off) For the initial take-off speed, we read the Bada.OPF file corresponding to the A aircraft.

55 Page 55/69 CCCCCCCCCCCCCCCCCCCCCCCCCCCCCC A343.OPF CCCCCCCCCCCCCCCCCCCCCCCCCCCC/ CC / CC AIRCRAFT PERFORMANCE OPERATIONAL FILE / CC / CC / CC File_name: A343.OPF / CC / CC Creation_date: Apr / CC / CC Modification_date: Feb / CC / CC / CC====== Actype ======================================================/ CD A343 4 engines Jet H / CC A with CFM56 5C4 engines wake / CC / CC====== Mass (t) ====================================================/ CC reference minimum maximum max payload mass grad / CD.21000E E E E E+00 / CC====== Flight envelope =============================================/ CC VMO(KCAS) MMO Max.Alt Hmax temp grad / CD.33000E E E E E+03 / CC====== Aerodynamics ================================================/ CC Wing Area and Buffet coefficients (SIM) / CCndrst Surf(m2) Clbo(M=0) k CM16 / CD E E E E+00 / CC Configuration characteristics / CC n Phase Name Vstall(KCAS) CD0 CD2 unused / CD 1 CR Clean.14200E E E E+00 / CD 2 IC E E E E+00 / CD 3 TO 1+F.10800E E E E+00 / CD 4 AP E E E E+00 / CD 5 LD FULL.10100E E E E+00 / V(initial take off) = V2 = 1. 2 Vstall TO V(initial take off A ) = kts We note that this value is slightly lower than the TAS in the climb phase at FL0 (=145 kts).

56 Page 56/69 Appendix B Eurocontrol Demand Data Repository File Types