|
|
|
|
|
|
 |
| | Arrival Manager (Click for larger image) |
Arrival Management within PHARE was carried out by the PHARE Advanced Tools (PATs) Arrival Manager.
The PATS Arrival Manager was a ground based planning tool. It provided support to the air traffic controller in automatically establishing an optimal arrival sequence, and provided facilities to enable the controller to subsequently manually edit the computed sequence. Additional facilities provided include automatic stack management and “what if” sequence generation.
The tool generated arrival sequences that included both ‘equipped’ (4D-Flight Management System with datalink) and ‘unequipped’ (without any datalink or 4D capability) aircraft.
|
|
|
|
The tool automatically computed an optimal arrival sequence for the airport being managed. The optimal arrival sequence for an airport was considered to be the arrival sequence that delivers the minimum deviations (delays) from the preferred arrival times for all of the aircraft within the sequence. Computation of an optimal arrival sequence utilised available runway and preferred aircraft arrival time data. The output of the sequence computation algorithms was a set of scheduled arrival times and landing runways for all of the aircraft destined for the airport being managed.
During optimal sequence computation, the tool automatically re-computed the scheduled arrival time and landing runway of all aircraft that were outside the configurable planning horizon for the airport being managed. The optimal sequence was re-computed when either data for a new arrival was acquired by the tool; or an update to the preferred time of arrival was received for a previously planned arrival; or an air traffic controller issued a request to modify the scheduled arrival time or landing runway of an arrival.
The tool provided a number of facilities to enable an air traffic controller to manually edit the computed optimal arrival sequence. The facilities enabled the controller to manually amend the scheduled arrival time and landing runway of aircraft; adjust the maximum landing flow rate for aircraft at the airport; and reserve time slots on a landing runway.
The tool provided automatic stack management support to ensure that aircraft were correctly separated when flying holding patterns at pre-defined fixes in order to accommodate a delay that could not be met through speed control.
The tool provided support for generating “what if” sequences. This facility enabled an air traffic controller to assess the impact of manually editing the sequence without necessarily having to apply the sequence changes to the real world situation.
|
|
|
The PHARE Arrival Manager is documented in:
|
|
|
