procedures for ebos - ivao · procedures for ebos 1. airport information 1.1. general information...

EBOS Procedures

Author: Stas Jessy © IVAO Belgium pg. 1

PROCEDURES FOR EBOS

1. AIRPORT INFORMATION

1.1 . GENERAL INFORMATION

Airport Name Ostend-Bruges International Airport

Airport City Ostend

ICAO / IATA Code EBOS / OST

Type of airfield Controlled

ATC Service Air Traffic Control Service (ATS)

Aerodrome Classes CTR class D

TMA class C

QuickView http://www.ivao.be/community/downloads/quickviews

Charts http://www.ivao.be/community/downloads/charts

Note: The following information is dedicated only for IVAO Network activities. It must not

be used in real aviation or in others networks.

EBOS Procedures


1.2 . ADDITIONAL INFORMATION

This single runway airport located at the coast has one special item, a backtrack. Traffic

departing from runway 26 that would need to make a backtrack starting at “A” and leaving

the runway again at “L” which might put some pressure on you if you have a mix of

departing and arriving traffic.

1.3 . ACTIVE RUNWAYS

Ostend Bruges International Airport has a preferential runway system to minimise noise for

the local residents.

Between 2100 and 0700, when the crosswind component - including gusts - does not exceed

15 knots, or the tailwind component - including gusts - does not exceed 5 knots and traffic

permitting and with approval of pilot-in-command, ATC shall use RWY 26 for departing and

RWY 08 for arriving aircraft.

Outside these hours select runway operations which fit best for the current weather

conditions.

1.4 . ATC POSITIONS

Primary Positions Code Frequency

Ostend Tower EBOS_TWR 118.175 MHz

Ostend Approach EBOS_APP 120.600 MHz

Secondary Positions Code Frequency

Ostend Ground EBOS_GND 121.975 MHz

Secondary Positions can only be opened with permission from BE-AO(A)C!

EBOS Procedures


2. ATC PROCEDURES

2.1 . OSTEND TOWER

POSIT ION INFORMATION

ATC Call sign Ostend Tower

ATC Code EBOS_TWR

Frequency 118.175 MHz

FRA AS1(MON-FRI 0000z-1600z, SAT-SUN 0000z-1400z)

AS2

RESPONSIBIL IT Y

� IFR clearance and VFR start-ups at EBOS;

� All push backs, taxi clearances and ground movements. Ground needs to make sure

all ground movements are safe;

� The airport’s runways and the Ostend Control Zone. Ostend Tower manages the

following traffic as expeditious but as safe as possible:

o Traffic entering, leaving or transiting the EBOS Control Zone (CTR)

o Traffic landing or taking-off from EBOS

AIRSPACE

EBOS Procedures


GENERAL PROCEDURES

F l igh t P lan Check ing

When checking a flight plan make sure to include the following checks:

� Flight Rules (VFR/IFR)

� Equipment (RVSM equipped/Mode S transponder). Mode S type of transponder is

mandatory in the EBBU FIR

� Departure Aerodrome (EBOS)

� Cruising speed (should be filed in Knots [N] TAS)

� Flight Level / Altitude (Conform Semi Circular system), below TA in altitude (Axxx),

above TL in flight levels (Fxxx)

� Correct routing (first FIX for SID, when incorrect usually the whole route is incorrect.

Do not just change the first FIX)

� If required you can coordinate with approach for a vectored departure, do not clear

for vectors without coordination.

� Check the FP (Altitude/route) against the LOAs and QuickViews

IFR Clearance

IFR clearance should contain:

1. Cleared to ... (destination aerodrome)

2. SID

3. Runway in use

4. Initial Climb Altitude/Level

5. SSR code (Squawk)

Star t -up C lea rance

Start-up clearance should contain:

1. Start-up approved

2. Runway in use (with VFR)

3. QNH (with VFR)

Ground movemen t

� Issue push back clearances when traffic and safety permits

� Regulate the priority of traffic by making pilots give way to another.

� Issue taxi clearances

Push Back C learance

A push back clearance should include the following:

1. Push back

2. Direction

EBOS Procedures


Tax i c learance

A taxi clearance should include the following

1. Taxi to ... (Holding Point)

2. Runway

3. Via ... (taxiways)

4. QNH

Usage o f runways

Every runway can only be used by one (1) aircraft at a time, unless there is line-up and wait

clearance issued behind an arriving or departing aircraft. A runway is considered clear if one

of the following criteria is met:

� Departing traffic has passed either the end or one of the sides of the runway;

� Arriving traffic has passed the holding point line completely after vacating;

� Crossing traffic has passed the holding point line completely after crossing.

Depar tu res

Before clearing an aircraft onto a runway, being it for either line-up or take-off, Tower must

� Check for any inbound traffic for that runway;

� Not let an aircraft get passed the holding point line if there is inbound traffic at 4nm

(nautical miles) or closer from touchdown.

When issuing a take-off clearance Tower must

� Check if the runway is clear;

� Adapt the wake turbulence separation if needed;

� Combine the take-off clearance with additional instructions if needed.

If needed tower can cancel a take-off clearance

� Traffic is not moving yet, cancellation of clearance;

� Traffic is moving, instruct to “Abort Take-off”

If traffic has passed its V1 speed, there is no safe way the traffic can abort, for safety

the traffic must continue the take-off

Ar r iva ls

IFR traffic arriving at the airport shall be transferred to Tower when it is established on the

Instrument Approach (ILS/NDB/VOR) or, in case of a visual approach, when runway is in

sight.

On initial contact with the arriving traffic, Tower must

� Issue a landing clearance if possible;

� Issue a continue approach instruction if there is another arrival in front.

EBOS Procedures


When issuing a landing clearance Tower must make sure that

� The runway is clear.

If required, Tower can cancel a landing clearance

� Cancel the landing clearance, this will let the traffic continue its approach and

another faster/closer aircraft can be put first or a departing aircraft can depart

before the arrival;

� Go Around, this will abort the approach and the aircraft will follow the published

missed approach procedure or instructions from Tower.

VFR Tra f f i c

For VFR Traffic there are published VFR routes. These routes can be found on the VFR Charts

or the EBOS QuickView. Tower may deviate from these routes if traffic and safety permits so.

EBOS CTR being class D means Tower should provide separation between

� IFR and Special VFR (SVFR) and;

� SVFR and SVFR.

Traffic information by Tower is provided between

� VFR and IFR and;

� VFR and VFR.

The EBOS CTR runs from GND (Ground level) to 1500ft. Any traffic higher than 1500ft will not

be handled by Tower. All traffic within the EBOS CTR but higher than 1500ft is handled by

Approach.

VFR Traffic transiting the CTR or arriving at EBOS can be delayed by several instructions

� Orbit left/right, this will let the aircraft make one or more 360s at a given point. Traffic

in orbit cannot see other traffic so make sure the orbit area is clear of other traffic;

� Extend downwind or upwind, this will make the aircraft extend its upwind or

downwind leg in the circuit. Tower shall advice the traffic when it can continue with

the circuit.

Tower has the following options for traffic in circuit in relation to arrivals or departures

� Instruct the VFR traffic to turn base behind an arriving aircraft, the VFR traffic must

have the arriving traffic in sight before doing so. Advise about wake turbulence if

needed;

� Instruct a touch and go aircraft to perform a stop and go when it is coming to close to

a departing aircraft from that same runway. Tower will advise the aircraft that it will

be a stop and go and issue a landing clearance and issue a take-off clearance when

spacing is sufficient. This will make the touch and go traffic stop on the runway and

await a take-off clearance before proceeding.

EBOS Procedures


PHRASEOLOGY EXAMPLES

ATC | Pilot

Current ATIS information is A.

IFR Clearance

Ostend Tower, JAF345 gate 4, Boeing 737, information A, request IFR clearance to

Frankfurt.

JAF345, information A correct. Cleared to Frankfurt, KOK3M, runway 26, initial FL60*,

squawk 7125.

Cleared to Frankfurt, KOK3M runway 26, initial FL60, squawk 7125, JAF345

JAF345, read back correct. Start-up approved, report for push back.

Start-up approved, JAF345.

*FL = Flight Level

VFR Sta r t -up

Ostend Tower, OOBEL, at general aviation, Beechcraft 58, information A, VFR to

Kiewit, request start-up.

OOBEL, information A correct. Start-up approved, runway 26, squawk 0041.

Start-up approved, runway 26, squawk 0041, OOBEL

Push Back

Ostend Tower, JAF345, request push back.

JAF345, push back approved facing east.

Push back approved facing east, JAF345

Note: Touch and go or stop and go traffic is considered as an arrival AND a departure.

Therefor wake turbulence separation should be taken into account.

Note: Instruction Orbit left will instruct the aircraft to make orbits to the left until

otherwise instructed. Instruction one orbit right, will instruct the aircraft to do one single

orbit to the right and continue its course after completion of this orbit.

EBOS Procedures


Cond i t iona l Push Back

In this case we have a Saudi Cargo B747 coming in from New York and is assigned gate 7 and

is about to taxi behind our JAF. We want our JAF345 to start its push back when the Saudi

Cargo has passed.

Ostend Tower, JAF345, request push back.

JAF345, behind passing traffic Saudi 747 at your left, push back facing east approved

behind.

Behind passing traffic Saudi 747, push back approved behind, JAF345

Tax i

JAF345 ready for taxi.

JAF345, taxi holding point A runway 26 via K, QNH 1015.

Taxi holding point A runway 26 via K, QNH 1015, JAF345

When traffic is approaching the holding point and needs a backtrack

JAF345, enter and backtrack 26, vacate L.

Enter and backtrack 26, vacate Lima, JAF345.

Cond i t iona l Tax i

Oops, we got another situation here. A KLM Embraer that was parked at the right of our

JAF345 has just received taxi clearance to the same runway and holding point and is also

following K. We will instruct our JAF345 to follow this one.

JAF345 ready for taxi.

JAF345, follow KLM Embraer to Holding Point A runway 26.

Follow KLM Embraer to holding point A runway 26, JAF345

Tra f f i c Management

An A310 from Egyptair Cargo is taxiing via the K and our JAF345 is about to enter K as well.

We are going to let our JAF345 give way.

JAF345, give way to the Egyptair Cargo A310 coming from your right.

Giving way to the Egyptair Cargo A310, JAF345

EBOS Procedures


Take -o f f

Immediate take-off clearance

JAF345, wind 250° 5 knots, runway 26 cleared for take-off.

26 cleared for take-off, JAF345.

When traffic is airborne

JAF345, contact Ostend Approach on 120.6.

Contact Ostend Approach 120.6, JAF345

Runway line up with delayed take-off clearance

JAF345, runway 26 line up and wait.

26, line up and wait, JAF345

When issuing take-off clearance






In case there is a preceding departing aircraft

JAF345, behind departing B747, runway 26, line up and wait behind.

Behind departing B747, 26, line up and wait behind, JAF345







EBOS Procedures


In case there is arriving traffic

JAF345, report arriving B737 on final in sight.

B737 in sight, JAF345

JAF345, behind arriving B737, runway 26, line up and wait behind.

Behind arriving B737, 26, line up and wait behind, JAF345






Contact Ostend Approach 120.6, JAF345.

The same procedures can be used for clearing an aircraft for backtrack with arriving or

departing traffic

JAF345, report arriving B737 on final in sight.

B737 in sight, JAF345

JAF345, behind arriving B737, runway 26, enter and backtrack behind, vacate L.

Behind arriving B737, 26, enter and backtrack behind, vacate L, JAF345

When aircraft is at holding point L ready for take-off





Contact Ostend Approach 120.6, JAF345.

It is important that the departing traffic correctly identifies the arriving traffic. If needed

add extra info such as company, aircraft type, colours...

EBOS Procedures


Land ing C lea rance

Immediate landing clearance

JAF345, wind 240° 5 knots, runway 26 cleared to land.

26 cleared to land, JAF345.

When traffic has vacated runway

JAF345, taxi to stand 3 via K and E2.

Taxi to stand 3 via K and E2, JAF345

If EBOS_GND is online you simple transfer the aircraft to Ostend Ground when traffic has

vacated the runway.

Our aircraft is second in line for landing

JAF345, wind 250° 5 knots, 26, number 2, continue approach. (Additionally you can

add: Number 1 is 3 miles final)

Number 2, 26, continue approach, JAF345

Preceding traffic has cleared the runway

JAF345, winds 250° 5 knots, runway 26 cleared to land.

26 cleared to land, JAF345.

When traffic has vacated runway

JAF345, taxi to stand 3 via K and E2.

Taxi to stand 3 via K and E2, JAF345

If EBOS_GND is online you simple transfer the aircraft to Ostend Ground when traffic has

vacated the runway.

EBOS Procedures


2.2 . OSTEND APPROACH

ATC Call sign Ostend Approach

ATC Code EBOS_APP

Frequency 120.600 MHz

Airspace Class C

FRA AS3 (MON-FRI 0000z-1600z, SAT-SUN 0000z-1400z)

ADC

RESPONSIBIL IT Y

Ostend Approach will handle all departing and arriving traffic from EBOS.

When Ostend Tower is not online, Approach will take over these tasks. Approach is

responsible for separation between departing and arriving traffic.

AIRSPACE

The following airspaces full under the responsibility of Ostend Approach:

� Ostend TMA ONE: 1500 AMSL – FL55

� Ostend TMA TWO: FL55 – FL95

If EBFN CTR is active it is excluded from TMA ONE and does not fall under the responsibility

of Ostend Approach but it falls under Koksijde Tower (EBFN_TWR)

Below you can find an extraction of the Airspace chart. All TMAs that Ostend Approach is

responsible for are coloured.

EBOS Procedures


GENERAL PROCEDURES

Ar r iv ing t ra f f i c

The task of Approach for arriving traffic is to get the traffic safe to the intercept point for

instrument approaches or visual range with the airport for visual approaches. This can be

done by either using full procedures or by vectoring. For Belgium the maximum allowed

offset angle with the final approach course before intercepting is 30°. This means that if the

runway heading is 245°, the aircraft should be between 245° - 275° or between 215° - 245°

before intercepting the instrument approach depending on the arrival direction.

When clearing an aircraft for the approach make sure that the aircraft

� is below glideslope (for ILS);

� follow the published descent profile for that approach (for NDB/VOR);

� has a maximum intercept angle of 30°

Traffic that is stabilised on the approach should be transferred to Tower.

Depar t ing t ra f f i c

Ostend Approach will clear departing traffic to FL70 and when able transfer traffic to

Brussels Control preferably before reaching FL70.

Approach may, in coordination with Brussels Control, direct a departing traffic to the end

point of the SID is traffic and safety permits.

Separa t ion poss ib i l i t ies

On IVAO the minimum separation should be at least 5nm or 1000ft.

Ostend Approach has several possibilities to separate traffic from each other

� Speed control: giving aircraft a faster or slower speed restriction in order to create or

maintain separation. Used for small separation creation.

� Holdings: letting an aircraft hold over a certain point will increase separation with

preceding traffic but will decrease separation with following traffic drastically.

Holdings are also time and fuel consuming.

� Altitude separation: keeping an aircraft 1000ft above preceding traffic. This gives you

time to build up separation by combining it with Speed control

� Vectoring: steering an aircraft away from another aircraft.

EBOS Procedures


PHRASEOLOGY EXAMPLES

Ar r iv ing t ra f f i c to EBOS

Our arriving traffic is inbound to FLO and ATIS D is current

Ostend Approach, JAF345, inbound DENUT descending FL60, information D.

JAF345, information D correct, expect vectoring ILS Approach runway 26, after

DENUT fly heading 290.

Expecting vectoring ILS Approach runway 26. After DENUT heading 290, JAF345

Traffic is coming closer to the ILS

JAF345, cleared ILS approach runway 26.

Cleared ILS runway 26, JAF345.

Traffic reports established on the ILS

Established ILS 26, JAF345

JAF345, QNH 1015, contact Ostend Tower on 118.175.

QNH 1015, contact Ostend Tower 118.175, JAF345

Depa r t ing t ra f f i c f rom EBOS

Ostend Approach, JAF345, KOK3M passing 1200.

JAF345, identified, climb FL70.

Climb FL70, JAF345

Traffic is reaching FL70

JAF345, contact Brussels Control 131.1.

Contact Brussels Control 131.1, JAF345.

Due to the airspace structure around EBOS, we kept our arriving aircraft at FL60. The aircraft intercepted the ILS at FL60. As FL60 is above the Transition level and we want him to keep the Standard QNH 1013 until he starts descending on the glideslope. When the aircraft is established and starts descending on the ILS we give him the QNH so he can adjust his barometric.

procedures for ebos - ivao · procedures for ebos 1. airport information 1.1. general information...

Documents