WP2 Future Automation Scenarios


The objectives of WP2 Future Automation Scenarios are to achieve a common understanding on the foreseen 2050 Concept of Operations to be addressed in AUTOPACE and to deliver the full set of AUTOPACE Scenarios, together with the skills required to operate in such scenarios. To fulfil these objectives, the overall activity has been divided into two tasks:

  1. Identify the State of the Art and Concept of Operations in 2050
  2. Define AUTOPACE scenarios and a set of operative conditions



In order to achieve the WP2 objectives, AUTOPACE has chosen a three-step approach comprising the development of 2035 AUTOPACE ConOps prior to the identification of 2050 AUTOPACE ConOps. This approach is due to the more specific and detailed documents for 2035 scenario. Then, once 2035 has been defined based on SESAR Step 2 deliveries, it would be much easier to evolve it towards 2050 horizon by taking into account 2050 reference documentation. Finally, the third step consists of the identification of the 2050 automation scenarios that will be studied in AUTOPACE project.


Since the objectives of AUTOPACE focus on the effect of automation on human factors, two 2050 scenarios considering two different levels of automations have been developed:

  • Scenario 1: High Automated ScenarioThis baseline scenario will have a high degree of automation. The ATC System develops the necessary actions for the orderly and safely traffic management, informing the ATC controller, who maintains a monitoring role. Therefore, in High Automated Scenario the system has an active role while the ATC controller remains as the supervisor of the system operation.


  • Scenario 2: Medium Automated Scenario

In this baseline scenario with a medium degree of automation the ATC tools will propose actions to be performed, and the ATC controller will decide which action to apply from the set of proposals suggested by the system. Therefore, in this scenario the system remains as a support tool for the ATC controller, who has the major responsibilities (manage traffic, sequence and synchronize traffic, coordination, etc.)

In addition to these baseline scenarios, it has been defined three non-nominal situations to support the assessment of automation failures.

  • Non-Nominal Situation 1: the Conflict Detection and Resolution tool fails
  • Non-Nominal Situation 2: the Complexity management tools fail
  • Non-Nominal Situation 3: the System supported coordination tools fail


If you want to know more about the WP2 do not hesitate to take a look at:

D2.1 Future Automation Scenarios