  |
|
 |
|
Departure Management within PHARE was carried out by the PHARE Advanced Tools (PATs) Departure Manager.
The PATS Departure Manager was a ground based planning tool. It assisted airport controllers in managing departure traffic, by providing takeoff schedules as well as optimised and conflict-free climbing trajectories, in order to achieve optimal use of runway capacity and TMA airspace. As soon as the proportion of departing flights compared to the whole traffic is significant, managing departure traffic before take-off is mandatory.
|
|
|
|
|
 |
|
| Departure Manager (Click for larger image) |
|
|
For each departure, as soon as the flight plan was available to the ground system, the Departure Manager allocated a runway and computed a scheduled takeoff time. The departure sequence was regularly updated to cope with the current traffic situation.
To build an optimised sequence, the Departure Manager took into account many factors that encompass surface movement constraints, usage of runways, traffic organisation in the TMA and transfer conditions to the Extended TMA.
The Departure Manager provided facilities for controllers to modify the computed sequences, and includes a “what-if” mode.
The departure controller planned trajectories within the TMA and negotiated with 4D equipped aircraft while flights were in taxiing phase. The Departure Manager assisted the controller in performing this task by searching for optimised and conflict-free climbing trajectories in respect with operational rules.
The Departure Manager was designed to be adaptable to any airport configuration, i.e. runways used in single or mixed mode. It was able to support a safe and optimised handling of the share of runway usage between incoming and outgoing flows, in co-operation with an Arrival Manager.
The Departure Manager was designed to assist the departure planner in:
|
|
|
 |
optimising runway usage |
|
|
organising the departure traffic in TMA |
|
|
minimising flight times and delays |
|
|
improving co-ordination with en-route and arrival controllers |
|
|
allowing anticipation for downstream controllers and tools to plan traffic |
|
|
|
|
To achieve these goals, the Departure Manager provides takeoff schedules and optimised climbing trajectories in TMA.
The requirements and the design of the Departure Manager are based on several concepts or hypothesis:
|
|
Accuracy of estimated and scheduled times of departure. |
|
|
Sequencing and traffic organisation in TMA airspace. |
|
|
Controllers stay in the Loop. |
|
|
Adaptation of free-flight concept in TMA. |
|
|
|
|
The Departure Manager is documented in:
|
|
|
| |
