Transcript Tower - Eurocontrol

Tower
ESSA User Handbook
Configuration
• The Tower system can be configured to model
different configurations of controller and pilot
positions.
• Controller positions allow the user to issue
clearances and orders.
• Pilot positions allow the user to accept, delay, reject
or deviate from the controller clearance/order.
• Also available are:
– Hybrid controller positions. Clearances and orders issued
from a hybrid position are automatically accepted and
actioned.
– Unmanned (automatic) controller positions. Unmanned
positions reduce the need of human intervention.
Arlanda Airport (ESSA)
• The following example, based at Arlanda (ESSA)
airport, details just one configuration that might be
modelled.
• ESSA has three pairs of runways 26-08, 19R-01L and
19L-01R.
• The example will demonstrate one departure leave
by runway 19R and one arrival arrive on runway 26.
• Pilots will follow Controller clearances and orders.
• Vehicles will impede both departures and arrivals,
triggering alerts.
User Views
• The ESSA example consists of:
–
–
–
–
–
Apron controller.
Runway controller.
Apron pilot.
Runway pilot.
Approach controller.
• Each view is summarised on the following
pages.
Airport Controller Views
• Apron Controller APR
–
–
–
–
Toolbar
Alert Window
Arrival List
Departure List
• Runway Controller RWY
–
–
–
–
–
Toolbar
Alert Window
Arrival List
Departure List
Approach inset view
Airport Pilot Views
•
•
•
•
APR and RWY Pilots
– Toolbar
– Alert Window
– Message In Window
Message in window contains
prompts derived from ground
controller clearance requests.
The prompts are derived from
the partnering controller e.g.
APR pilot receives prompts for
the APR controller
clearances/orders.
Pilots can either acknowledge
or reject the prompt.
Approach View
• Approach controller
TMA.
• TMA feeds arriving
flights into airport.
• TMA accepts departing
flights from airport
Departure Pushback
•
•
•
•
After starting the scenario the
departure DEP1 will appear on
the airport views and in the
departure list.
DEP1 will be coloured to
indicate that APR controller can
assume jurisdiction control.
The DEP1 label will indicate that
DEP1 is ready for its pushback
clearance.
By clicking on the (track or list)
callsign and issuing the
pushback clearance, APR
assumes control and prompts
the pilot to pushback.
Departure Pilot Pushback
• After the pushback
clearance is issued the APR
pilot receives the pushback
prompt in the Message in
window.
• On accepting the pushback
clearance DEP1 starts its
push back.
• The prompt is removed from
the Message in window
Departure Taxi
• After reversing from the
stand and completing the
pushback manoeuvre the
DEP1 label indicates that
DEP1 is ready for its taxi
clearance to the runway.
• From the APR view and
clicking on the (track or list)
callsign the APR controller
can issue the taxi clearance.
• Issuing the taxi clearance
prompts the pilot to taxi.
Departure Pilot Taxi
• After the taxi clearance is
issued the APR pilot
receives the taxi prompt in
the Message in window.
• On accepting the taxi
clearance DEP1 starts its
taxi to its departure runway.
• The prompt is removed from
the Message in window
Departure Transfer To RWY
• When the APR controller
judges it is time to transfer
jurisdiction of DEP1 (usually
when the aircraft has left the
apron area) he can click on
the callsign and select
transfer.
• In this example the transfer
will be to the RWY controller.
• Note there is no prompt to
the pilot.
Departure Transferred
• After the transfer:
– DEP1 is coloured on the
APR view to indicate the
transfer.
– DEP1 is coloured on the
RWY view to indicate
jurisdiction of DEP1 is
ready to be assumed by
the RWY controller.
Departure Assumed By RWY
• When the RWY
controller is ready to
assume jurisdiction of
DEP1 he can click on
the callsign and select
assume.
Departure Assumed
• After the assume:
– DEP1 is coloured on the
APR view to indicate the
completion of the
transfer-assume.
– DEP1 is coloured on the
RWY view to indicate
that the RWY controller
now has jurisdiction.
Departure Lineup
• Just prior to entering the
runway area, DEP1 reaches
a lineup point.
• To continue from the lineup
point onto the runway DEP1
requires lineup clearance.
• From the RWY view and
clicking on the (track or list)
callsign the RWY controller
can issue the lineup
clearance.
• Issuing the taxi clearance
prompts the pilot to lineup.
Departure Pilot Lineup
• After the lineup clearance is
issued the RWY pilot
receives the lineup prompt in
the Message in window.
• On accepting the lineup
clearance DEP1 continues
into the runway area.
• The prompt is removed from
the Message in window
Departure Alert
• As DEP1 enters the
protected area around the
departure runway an alert is
raised as a vehicle VAN2 is
blocking the runway.
• The alert is detailed in the
Alert window indicating the
area and offending vehicle
and departure.
• Note the callsigns of the
departure and vehicle are
highlighted in yellow.
Departure Takeoff
• As DEP1 completes its
lining-up in the direction of
the runway, DEP1 requests
takeoff clearance.
• From the RWY view and
clicking on the (track or list)
callsign the RWY controller
can issue the takeoff
clearance.
• Issuing the takeoff clearance
prompts the pilot to takeoff.
• Issuing the takeoff clearance
raises the alert to an alarm!
Departure Alarm
• Even though DEP1 is
stationary just issuing
the takeoff clearance is
enough to raise the
alert to an alarm.
• The offending callsigns
are now highlighted red.
Departure Pilot Takeoff
• After the takeoff clearance is
issued the RWY pilot
receives the takeoff prompt
in the Message in window.
• On accepting the takeoff
clearance DEP1 accelerates
down the runway.
• The prompt is removed from
the Message in window
Departure Alarm Cleared
• Later as DEP1 passes
VAN2 on the runway the
alarm and alert
indicators are cleared.
• DEP1 continues to
accelerate to its takeoff
speed.
Departure Takeoff
• After takeoff DEP1
will be shown on the
RWY Controller’s
approach inset view.
• As the RWY
Controller has not
transferred control of
DEP1 to the
neighbouring sector
(i.e. TMA) it is
automatically
transferred.
Departure TMA Assume
• After takeoff DEP1 will be
shown on any enroute or
approach views.
• In our example this is the
TMA controller.
• As DEP1 was transferred it
will be coloured on the TMA
view to indicate that it is
ready to be assumed.
• By clicking on the next
sector button the TMA
controller can assume
jurisdiction.
Departure TMA Controlled
• The completion of the
transfer-assume will be
indicated on the RWY view.
• The Departure List entry for
DEP1 will be in the CTR
section of the list and
coloured to indicate that the
transfer has been assumed.
• Using the RWY approach
inset view the RWY
controller will still be able to
track concerned flights.
Departure Deviation
(Optional)
•
•
•
•
To demonstrate that pilots can
deviate from the planned controller
clearances and orders, re-run the
scenario to the point where DEP1
requests takeoff clearance.
From the RWY Pilot view and
clicking on the track callsign the
RWY Pilot can initiate the takeoff
manoeuvre without the clearance.
As DEP1 starts to accelerate down
the runway note that “Takeoff
clearance due” is still shown in the
label.
Note an alarm is not raised
immediately but only when DEP1
accelerates to a speed higher than
a normal taxi speed.
Arrival
• This example has been
configured such that:
– The TMA sector and airport
sector share the same
boundaries but with the
TMA sector sitting
immediately above the
airport sector with
jurisdiction changing at
9000ft.
– Advance boundary
information is transmitted 6
minutes prior to entry to the
airport sector.
– Inbound information is
transmitted 5 minutes prior
to entry to the airport sector.
Arrival ABI
• As ARR1 approaches
the airport sector
Advance Boundary
Information is received
(ABI message) and an
entry appears in the
Final section of the
RWY Controller’s Arrival
list.
• The entry will show an
estimate landing time.
Arrival Inbound
• On receipt of the ABI
message the arrival list entry
is coloured as not
concerned.
• As ARR1 nears the airport
sector Inbound information is
received (ACT message)
and the arrival list entry will
be updated with a new
estimate landing time.
• The entry will now be
coloured as inbound.
Arrival TMA Transfer
• As ARR1 begins its final
appraoch to the airport
the TMA transfers
control to the airport.
• By clicking on the next
sector the TMA
controller can initiate
the transfer.
Arrival RWY Assume
• After the TMA controller
initiates the transfer of ARR1
the RWY controller’s arrival
list entry will be coloured to
indicated he can assume
jurisdiction.
• By clicking on the Arrival list
LDT field for ARR1 the RWY
controller assumes
jurisdiction and gives
clearance to land.
• The arrival list entry is then
coloured to indicate RWY
has assumed control.
• Note there is no pilot prompt.
Arrival Alert
• As ARR1 approaches (long
final time) runway 26 an alert
is raised as VAN1 is blocking
the runway.
• Callsigns are highlighted
yellow.
• As ARR1 approaches even
nearer (short final time) the
alert is raised to an alarm.
• Callsigns are highlighted red.
Arrival Alarm Cleared
• After ARR1 touches down
the alarm remains.
• Later as ARR1 passes VAN1
on the runway the alarm and
alert indicators are cleared.
• ARR1 continues to
decelerate to its taxi speed.
• ARR1 then leaves the
runway at the first
opportunity.
Arrival Taxi
• After leaving the runway
ARR1 reaches a taxi
clearance point. ARR1 track
label indicates taxi clearance
due.
• From the RWY controller
view and clicking on the
(track or list) callsign the
RWY controller can issue the
taxi clearance.
• Issuing the taxi clearance
prompts the pilot to taxi.
Arrival Pilot Taxi
• After the taxi clearance
is issued the RWY pilot
receives the taxi prompt
in the Message in
window.
• On accepting the taxi
clearance ARR1 starts
its taxi to its stand.
• The prompt is removed
from the Message in
window
Arrival Transfer To APR
• When the RWY controller
judges it is time to transfer
jurisdiction of ARR1 (usually
when the aircraft has left the
runway area) RWY can click
on the callsign and select
transfer.
• In this example the transfer
will be to the APR controller.
• Note there is no prompt to
the pilot.
Arrival Transferred
• After the transfer:
– ARR1 is coloured on the
RWY view to indicate the
transfer.
– ARR1 is coloured on the
APR view to indicate
jurisdiction of ARR1 is
ready to be assumed by
the APR controller.
Arrival Assumed By APR
• When the APR
controller is ready to
assume jurisdiction of
ARR1, APR can click on
the callsign and select
assume.
Arrival Assumed
• After the assume:
– ARR1 is coloured on the
RWY view to indicate the
completion of the
transfer-assume.
– ARR1 is coloured on the
APR view to indicate that
the APR controller now
has jurisdiction.
Arrival Parks
• If ARR1
continues on its
current taxi
route it will park
near the centre
of the airport at
stand B12.
• Optionally the
controller may
decide to
change the
stand.
Arrival Change Stand
(Optional)
• Positioning the mouse over
an aircraft symbol and
clicking on the RIGHT button
displays the planned taxi
route (white solid line) and
the travelled taxi route (red
dashed line).
• By clicking the RIGHT button
again while still on the
aircraft symbol removes the
planned route.
Modifying Taxi Route
• Positioning the mouse
over an aircraft symbol
and clicking on the LEFT
button not only displays
the planned taxi route but
allows the taxi route
destination to be changed
(and optionally inserts an
intermediate taxi route
point “go VIA”).
• Clicking the RIGHT
button cancels the action
• To change the destination of
the taxi route for ARR1
position the “kink” over an
appropriate stand.
• The yellow circle will then
move to the selected stand.
• By LEFT clicking submits the
new taxi route and prompts
the pilot to change taxi route.
• After the taxi route is
changed the RWY pilot
receives the change stand
prompt in the Message in
window.
• On accepting the clearance
ARR1 will take a new taxi
route to the new stand.
• The prompt is removed from
the Message in window
Arrival Parks At New Stand
• ARR1 reaches
its new stand.