Exercise 6: FPSC + Departure and Arrival Procedure + Traffic Info + DEP/IFR + Multi

Runways Operations

1.20.4. Departure procedure

1.20.4.4. Determination of runway-in-use rests on SHE TWR. Before clearing IFR traffic to
depart, release time statement shall be obtained from SHE APP
1.20.4.5. Irrespective weather conditions, departure IFR will be transferred from SHE TWR to
SHE APP immediately after the aircraft is airborne.
1.20.4.6. SHE TWR shall ensure that the departure IFR is separated from other arriving
(IFR/VFR) traffic in accordance with the minima specified at the aerodrome
1.20.5.4. Separation of departing aircraft

1.20.5.4.1. A departing aircraft will not normally be permitted to commence take-off until the
preceding departing aircraft has crossed the end of the runway-in-use or has started a turn
or until all preceding landing aircraft are clear of the runway-in-use (has crossed the runway
holding position marking).
1.20.5.5. Separation of arriving aircraft

1.20.5.5.1. A landing aircraft will not normally be permitted to cross the runway threshold on
its final approach until the preceding departing aircraft has crossed the end of the runway-in-
use, or has started a turn, or until all preceding landing aircraft are clear of the runway-in-
use.
Note 1.— The above statement indicates that the landing clearance may be issued to arriving
aircraft at any time provided that when the arriving aircraft crosses the threshold, the
departing aircraft has crossed the end of the runway-in-use, or has started a turn, or until all
preceding landing aircraft are clear of the runway-in-use;
Note 2.— Even so, for the purpose of avoiding the arriving aircraft to make go around, it is
recommended for SHE TWR not to issue landing clearance until the departing aircraft has
rolled for take-off;
Note 3.— Landing clearance for IFR flight shall only be issued when the flight crew has
reported that he/she has established visual contact or runway in sight.
1.20.5.6. Time-based wake turbulence longitudinal separation minima

1.20.5.6.1. SHE TWR shall not be required to apply wake turbulence separation:
for arriving VFR flights landing on the same runway as a preceding landing HEAVY or MEDIUM
aircraft; and between arriving IFR flights executing visual approach when the aircraft has
reported the preceding aircraft in sight and has been instructed to follow and maintain own
separation from that aircraft

TRAFFIC INFORMATION
Traffic information shall be given to VFR flights concerned whenever they constitute traffic to
each other.
Traffic information shall include :
a) aircraft identification (ACID) or call sign;
b) type of aircraft concerned;
c) route of flight;
d) current position;
e) level; and
f) ETA significant point
Example: PKGUS TRAFFIC TRILANDER COMING FROM SANDSHARK POSITION APPROACHING
POINT BT NBD MAINTAINING 3000 FT ESTIMATING POINT BT NBD 14 ALPHA 18 SHE 23

1.20.7. Multi-runways operation

1.20.7.1. Parallel runways
1.20.7.1.1. Since the only one runway (16R/34L) which is assigned as the instrument runway
and only runway 34L which is furnished with ILS and the distance between their runway
centre lines is 1088 metres, the following procedures apply:
a) Departing aircraft

(1) aircraft may be cleared for take-off simultaneously from both runways
provided that the paths of the aircraft after taking-off will not cross one to
each other;
(2) if the paths of the aircraft after taking-off will be converging or proceeding to
the same point or route, they shall be separated vertically;
b) Arriving aircraft
 (1) if in visual meteorological conditions, aircraft may be cleared to land
simultaneously to both runways provided that both aircraft are not coming
from the same point or route;
(2) if in instrument meteorological conditions, aircraft may not be cleared to land
simultaneously to both runways.
1.20.7.1.2. When the arriving aircraft has reported on final or short final of one runway, the
departing aircraft using another runway may be cleared for take-off provided that the path
of the departing aircraft will not cross the missed track of the adjacent runway.
1.20.7.2. Crossing runways

1.20.7.2.1. The criteria for the operation of crossing runways are similar to the criteria for
single runway, it means that both runways shall not be used for take-off and/or landing
simultaneously.
1.20.7.2.2. If there are two departing aircraft intend to take-off using different runways, the
second aircraft shall not be cleared for take-off until the first aircraft has positively crossed
the main intersection of runways.
1.20.7.2.3. If there are two arriving aircraft intend to land using different runways, the second
aircraft shall not be cleared to land until the first landing aircraft has positively crossed the
main intersection of runways.
1.20.7.2.4. If there is an arriving aircraft intends to land using any runway while the other
departing aircraft intends to take-off using another runway, the arriving aircraft shall not be
cleared to land until the departing aircraft has positively crossed the main intersection of
runways.
1.20.7.2.5. If there is a departing aircraft intends to take-off using any runway while the other
arriving aircraft intends to land using another runway, the departing aircraft shall not be
cleared to take-off until the landing aircraft has positively:
a. crossed the main intersection of runways; or

b. stopped for holding before the main intersection of runways

1.20.7.2.6. Since there is no ILS for runway 07/25, when using multi runways simultaneously,
caution shall be advised for aircraft on final runway 07 and aircraft on downwind runway
34L/right hand downwind runway 16R or aircraft on final runway 25 and aircraft on downwind
runway 16L/right hand downwind runway 34R. Make sure that aircraft on downwind/right
hand downwind has sufficient vertical separation with aircraft on final.

1.20.8. Pilot or ATC action on change of runway

1.20.8.1. It is possible that during the control of traffic, wind condition changed abruptly from
the opposite direction. When it happens, SHE TWR shall revise runway-in-use and issue
revised instruction to all aircraft (departure as well as arrival). For aircraft which is on take-
off position (about to take-off) or on final approach and appears to be in difficulties if he has
to pull up and go round, shall be advised to permit the pilot-in-command to decide whether
he will use another runway or continue approach to land with the existing tail wind condition.
Example phraseology for runway change:

a. For aircraft in the traffic circuit other than on final and on take-off position:

ALL STATIONS DUE TO WIND CHANGE TO 320 DEGREES AT 20 [KNOTS], RUNWAY IN-USE NOW
[RUNWAY] 34L, JOIN ........... (or PROCEED TO ...... ETC.)

............. REPORT .................

b. For aircraft on final and on take-off position : [ACID] WIND CHANGE TO 320 DEGREES AT
20 [KNOTS] REQUEST YOUR INTENTION.
(1) If the aircraft intend to change the runway-in-use : [ACID] ROGER TAXI TO ........... VIA
TAXIWAY (or RUNWAY) REPORT ..................,
(2) If the aircraft intend to coninue approach or take-off : [ACID] ROGER WIND 320

DEGREES AT 20 [KNOTS] RUNWAY 34L CLEARED TO LAND (or FOR TAKE OFF).
1.20.8.2. The pattern of arriving aircraft who intends to change the runway-in-use shall pull
up and go round then follow the circling procedure (see again paragraph 1.20.3.4.1. on page
26 and 1.20.3.4.2. on page 27).

7.2 SELECTION OF RUNWAY-IN-USE

7.2.1 The term “runway-in-use” shall be used to indicate the runway or runways that, at a
particular time, are considered by the aerodrome control tower to be the most suitable for
use by the types of aircraft expected to land or take off at the aerodrome.
Note.— Separate or multiple runways may be designated runway-in-use for arriving aircraft
and departing aircraft.
7.2.2 Normally, an aircraft will land and take off into wind unless safety, the runway
configuration, meteorological conditions and available instrument approach procedures or
air traffic conditions determine that a different direction is preferable. In selecting the
runway-in-use, however, the unit providing aerodrome control service shall take into
consideration, besides surface wind speed and direction, other relevant factors such as the
aerodrome traffic circuits, the length of runways, and the approach and landing aids available.
7.2.3 A runway for take-off or landing, appropriate to the operation, may be nominated for
noise abatement purposes, the objective being to utilize whenever possible those runways
that permit aeroplanes to avoid noise-sensitive areas during the initial departure and final
approach phases of flight.
7.2.4 Runways should not be selected for noise abatement purposes for landing operations
unless they are equipped with suitable glide path guidance, e.g. ILS, or a visual approach slope
indicator system for operations in visual meteorological conditions.
7.2.5 A pilot-in-command, prompted by safety concerns, can refuse a runway offered for
noisepreferential reasons.
7.2.6 Noise abatement shall not be a determining factor in runway nomination under the
following circumstances:
a. if the runway surface conditions are adversely affected (e.g. by snow, slush, ice,
water, mud, rubber, oil or other substances);
b. for landing in conditions:

(1) when the ceiling is lower than 150 m (500 ft) above aerodrome elevation, or the
visibility is less than 1 900 m; or
(2) when the approach requires use to be made of vertical minima greater than 100
m (300 ft) above aerodrome elevation and:
i. the ceiling is lower than 240 m (800 ft) above aerodrome elevation; or

ii. the visibility is less than 3 000 m;

c. for take-off when the visibility is less than 1 900 m;

d. when wind shear has been reported or forecast or when thunderstorms are
expected to affect the approach or departure; and
e. when the crosswind component, including gusts, exceeds 28 km/h (15 kt), or the
tailwind component, including gusts, exceeds 9 km/h (5 kt).