Kuwait Tower [OKKK_TWR]
Amendment History
| Revision | Effective Date | Notes |
|---|---|---|
| Version 1 | 13AUG25 | Initial Publication |
Chapter 1. Position Overview
Kuwait Tower (TWR) controls movement of aircraft on the runway and holding at all runway holding points. In addition to this the TWR Controller also has the responsibility of all aircraft within the Class D Kuwait Control Zone and shall ensure separation within the Control Zone (CTR) between IFR traffic is maintained for flights arriving and departing Bahrain. Traffic Information is provided between IFR and VFR Flights as well as VFR to IFR Flights within the Control Zone (CTR)
The TWR Controller is responsible for selecting the active runways for arrivals and departures at Kuwait and holds full authority over the runway.
Chapter 2. Airspace
The Kuwait Control Zone (CTR) is Class D Airspace from the Ground up to 2000ft Mean Sea Level (MSL). The TWR Controller is responsible for ensuring all traffic within the Control Zone are separated. This will typically include all IFR Flights departing and arriving as well as VFR Flights operating within the Control Zone or entering and exiting.
Chapter 3. GEN | General Operating Procedures
3.1 Runway Selection
At Kuwait International Airport (OBBI), the preferential runway is 33R for arrivals and 33L for departures which may be utilised with a tailwind of up to 5kts. If the tailwind component is greater than 5kts then the 15s should be used for arrivals and departures. If the 15s have to be utilised then 15L is the favoured departure runway and 15R is used for arrivals.
References to Use
-
You can always refernece real world sources! However, this should NEVER become a reliance.
-
All Controllers should bare the ability to read weather and make an assessment on what the active runway in use should be.
3.1.1 Runway Change
If the TWR Controller deems it necessary to change the active runway due to a change in wind direction this should be coordinated with all controllers above and below as this changes departure and arrival clearances. This should not be done suddenly, it must be carefully coordinated. The Approach Controller and Tower Controller will carefully select which aircraft is the last aircraft to land prior to the runway change.
This process is the same with the DLV or GMC Controller if an aircraft is already taxing to the active runway prior to runway change it may be less disruptive to allow the aircraft to depart if they can accept the tailwind. Aircraft can be re-issued with a departure clearance.
3.2 Line Up Procedures
The TWR Controller must issue clear and precise instructions when issuing aircraft with an instruction to line up on the active runway. There should be no delay and must include the following information:
- The Correct Runway Designator.
- The Holding Point at which the aircraft is to enter the runway by.
- Any relevant traffic information.
Example:
TWR Controller: "KAC501, via Loop line up and wait RWY33L"
3.2.1 Conditional Line Up Clearance (Landing Traffic)
The TWR Controller may issue a conditional line up clearance in order to maximise movements and runway efficency. This must be done efficently and precisely.
Example:
TWR Controller: "KAC501, behind the landing Qatar Airbus A320, 3 mile final, line up and wait RWY33L via Loop, behind"
Vitally Important
The use of the word "behind" at the start and end of the instruction is compulsory, this is to ensure the aircraft fully understands they are to give way to the landing traffic
3.2.2 Conditional Line Up Clearance (Departing Traffic)
The TWR Controller can also issue a conditional line up clearance for traffic waiting to depart behind a departing aircraft ahead of him. Again, this must be done efficently and precisly to prevent any runway incursions or misunderstanding.
Example:
TWR Controller: "KAC501, behind the departing Company Airbus A330 Neo, via Loop line up and wait RWY33L, behind"
Company Traffic
The use of the word company traffic in clearances can be used if the traffic related to the instruction is of the same company that is receiving the clearance
3.3 Take Off Procedures
3.3.1 Standard Instrument Departures (SIDs)
All departures from Kuwait will be assigned a Standard Instrument Departure (SID) when they recieve their departure clearance, they are assigned based on the first waypoint in their flight plan and/or direction of flight. The purpose of SIDs are to ehance safety, predictability and efficiently guide traffic from their initial departure phase to the en-route traffic environment.
All SIDs in Kuwait are RNAV1 (Area Navigation) which means aircraft must be able to maintain a total system error of no more than 1 nautical mile (NM) for 95% of the flight time. This enhances safety, and accuracy of the departure routing an aircraft should fly.
| Runway | Identifier | Initial Altitude |
|---|---|---|
| 33L/33R | ALVAX4F | 4000ft |
| 33L/33R | ASVIR4F | 4000ft |
| 33L/33R | BOXIK4F | 4000ft |
| 33L/33R | KFR4F | 4000ft |
| 33L/33R | RALKA4F | 4000ft |
| 33L/33R | SESRU4F | 4000ft |
| Runway | Identifier | Initial Altitude |
|---|---|---|
| 15L/15R | ALVAX4E | 4000ft |
| 15L/15R | ASVIR4E | 4000ft |
| 15L/15R | BOXIK4E | 4000ft |
| 15L/15R | KFR4E | 4000ft |
| 15L/15R | RALKA4E | 4000ft |
| 15L/15R | SESRU4E | 4000ft |
The initial climb for all departures for aircraft assigned a Standard Instrument Departure (SID) is 4000ft.
3.3.2 Take Off Clearances
Aircraft should only be given take off clearance once the runway is clear of obstructions and separation between any previously departed aircraft has been achieved.
Example:
TWR Controller: "KAC393, Surface Wind 300 Degrees at 12 knots, Runway 33L, Cleared for takeoff"
3.3.3 Handing Off
Once the aircraft has taken off and a postive rate of climb can be seen (typically passing 800ft) they should be informed to contact the Approach Controller with their passing altitude.
Example:
TWR Controller: "KAC393, report your passing altitude to Kuwait Approach 124.800, Goodbye"
3.3.4 Wake Separation
Time based separation is utilised at Kuwait to ensure separation between various wake turbulence catergories is maintained. The TWR Controller is responsible for ensuring the seperation system is enforced.
3.3.4.1 Wake Turbulence Catergories
Aircraft are divided into 4 different Wake Turbulence Catergories (WTC) based on the aircrafts certified Maximum Take Off Weight.
| Wake Turbulence Catergory (WTC) | Maximum Take Off Weight (MTOW) |
|---|---|
| Light (L) | ≤ 7000KG |
| Medium (M) | 7000KG to 136,000KG |
| Heavy (H) | ≥ 136,000KG |
| Super (J) | A388 ONLY |
It is the responsibility of the controller to check the Flight Plan (FPL) if they are unsure of an aircrafts Wake Turbulence Catergory.
3.3.4.2 Time Based Separation Table
| Preceeding (Before) | Behind | Suceeding (After) | Separation Time | From an intersection |
|---|---|---|---|---|
| Light | Medium | 2 min | 3 min | |
| Medium | Heavy | 2 min | 3 min | |
| Light | Heavy | 2 min | 3 min | |
| Medium | Super | 3 min | 4 min | |
| Light | Super | 3 min | 4 min |
3.3.5 Stopping a Departure
In the event you are required to stop a departure after take off clearance has been issued you need to act fast. This can be to prevent a potential collision as a result of a runway incursion or due to a go around which is now in the flight path of the departing aircraft.
The instruction must be issued early enough so that the departing aircraft does not reach it's "V1" (maximum speed at which a rejected takeoff can be initiated).
For stopping an aircraft that has already begun it's take off roll the following phraseology should be used.
Example:
TWR Controller: "FDB687, stop immediately, I say again, stop immediately, runway incursion"
For an aircraft that has not yet begun the take off roll the following phraseoloy should be used:
Example:
TWR Controller: "FDB687, hold position, cancel take off, I say again, cancel take off due runway incursion"
3.4 Arrival Procedures
The TWR Controller is responsible for issuing traffic landing clearance. They must ensure that separation is maintained on the approach between all aircraft and that all arriving aircraft have a clear unobstructed runway with an issued clearance no later than 2nm from touchdown.
3.4.1 Landing Clearance
Example:
TWR Controller: "JZR1144, Surface Winds 300 Degrees at 10 knots, Runway 33R, Cleared to land"
3.4.1.1 Late Landing Clearance
In the event traffic may be issued a late landing clearance due to traffic departing ahead of them or vacating slowly they can be issued a late landing clearance, however, the landing traffic must be issued a landing clearance no later than 2nm from touchdown.
TWR Controller: "JZR1144, Expect late landing clearance, one to vacate ahead"
3.4.2 Preferred Exit Points
In order to ensure minimum runway occupancy time pilots are expected to vacate the active runway by the taxiways.
| Runway | Exit Points |
|---|---|
| 33R | Loop 2 |
| 33L | W4 or W5 |
| 15R | W2 |
| 15L | E2 |
3.4.3 Vacating Traffic
Traffic vacating the active runway shall not be immediately transfered to the GMC Controller, it is the responsibility of the TWR Controller to issue an initial taxi clearance onto taxiway W1 or E1 to ensure the runway is not obstructed by aircraft stopping at the holding point and then waiting for an instruction from the GMC controller.
The aim is to ensure the runway is kept clear to allow smooth and efficent flow of traffic in and out of Kuwait International Airport (OKKK).
The GMC Controller (if online) has the responsibility to ensure all aircraft on final approach are allocated with a stand number, this allows the TWR Controller to be able to issue an initial taxi clearance after vacating the runway in the direction of that allocated parking stand.
3.4.3.1 After Landing Phraseology
Example:
TWR Controller: "IAW1017, Welcome to Kuwait, left turn on taxiway W1, hold short of taxiway W4, Contact Kuwait Ground 121.700"
3.4.4 Separation Requirements
Within the Kuwait Control Zone (CTR) the TWR Controller is responsible for ensuring adequate separation exists between all traffic, this includes vertically and laterally to ensure safe and efficient operation.
3.4.4.1 Longitudinal Separation (Lateral)
Aircraft arriving into Kuwait should be separated by 7nm laterally.
3.4.4.2 Speed Control
Though the TWR Controller is not able to issue aircraft with a measurement of speed they can advise aircraft to reduce to their minimum final approach speed if separation on the approach is starting to look like it may not work.
Example:
TWR Controller: "QTR1072, reduce to minimum approach speed"
3.4.4.3 Wake Turbulence Separation
Aircraft must also be suitable separated in accordance with their Wake Turbulence Catergories, much like departing aircraft to reduce the impact of wake produced by the preceding aircraft.
| Succeeding Aircraft | Behind | Preceding Aircraft | Arrival Separation Minima |
|---|---|---|---|
| Light (L) | Medium (M) | 5nm | |
| Medium (M) | Heavy (H) | 5nm | |
| Light (L) | Heavy (H) | 6nm | |
| Heavy (H) | Heavy (H) | 4nm | |
| Medium (M) | A380 | 7nm | |
| Light (L) | A380 | 8nm |
3.4.5 Go Around Procedures
It is the responsibility of the TWR Controller to issue Go Around Instructions if the controller observes a loss of separation on the final approach or an obstruction on the runway that will not clear before the arriving aircraft meets the 2nm clearance issued critera.
Example:
TWR Controller: "KAC156, "go around, I say again, go around, acknowledge"
Once the aircraft has acknowledged the go around, the TWR Controller shall issue the aircraft which the standard missed approach phraseology.
TWR Controller: "KAC156, fly the standard missed approach procedure, climb altitude 5000ft, contact Kuwait Approach on 124.800"
Coordination
If a go around instruction has been issued, the Approach Controller should be notified immediately once the aircraft has been given instructions.
3.5 VFR Procedures
- VFR Flights shall not take place above FL150 to prevent entering the Class A Airspace.
- VFR Flights are not permitted when the ceiling is less than 1500ft or when the ground visibility is less than 5KM.
- Kuwait Tower (TWR) and Kuwait Approach (APP) both hold the authority to delay VFR flights into either Class D Control Zone or the Class C Control Area if traffic levels permit.
- All Traffic shall be cleared to operate up to 1000ft within the Control Zone.
3.5.1 Visual Reporting Points (VRPs)
Visual Reporting Points (VRPs) are specific geographical locations used in aviation to assist pilots in navigation and communication with air traffic control. These points help pilots maintain situational awareness and provide reference points for reporting their position during flight.
Kuwait has a number of Visual Reporting Points (VRPs) which you can see below.
| Route Identifier | Reporting Point | Radial & DME from KUA VOR/DME | Coordinates |
|---|---|---|---|
| VFR Q East | Qurain Shopping Center | 115 Degrees / 5.8nm | 291156.75N 480257.11E |
| VFR G West | Petrol Station | 195 Degrees / 4.2nm | 291058.02N 475530.96E |
| VFR F East | Mishrif Fairground | 075 Degrees / 5.0nm | 291607.33N 480249.03E |
| VFR U West | Alshedadiya University | 245 Degrees / 3.2nm | 291524.08N 475359.15E |
3.5.2 VFR Departure Routes Procedures
VFR Flights Departing the Kuwait Control Zone should be assigned one of the below VFR Departure Routes.
| Runway | Identifier | Direction of Flight | Procedure |
|---|---|---|---|
| RWY15L/15R | VFR Q East | East | Pilot should climb to 1000ft on runway heading, when passing the departure end of runway (DER) pilots shall turn left towards Qurain Shopping Area and report overhead. |
| RWY15L/15R | VFR G West | West | Pilots should climb to 1000ft on runway heading, when passing the departure end of runway (DER) pilots shall turn right towards Petrol Station located on the 7th Ring Road beside the drag circuit and report overhead. |
| RWY33L/33R | VFR F East | East | Pilots should climb to 1000ft on runway heading, when passing the departure end of runway (DER) pilots shall turn right towards Mishrif Fairground on report overhead. |
| RWY33L/33R | VFR U West | West | Pilots should climb to 1000ft on runway heading, when passing the departure end of runway (DER) pilots shall turn left towards Alshedadiya University and report overhead. |
Please direct the pilot to the Pilot Briefing page if they're unsure with the above VFR Departure Procedures. It is the pilots responsibility to ensure they are fully aware of the departure procedures above.
3.5.1.2 VFR Departure Phraseology
Pilot: "Kuwait Tower, 9K-VFR with you holding point W2, runway 33L"
TWR: "9K-VFR, via W2, cleared for takeoff runway 33L, winds calm, Foxtrot East Procedure, Report Overhead Mishrif Fairground."
Pilot: "Via W2, cleared for takeoff runway 33L, Foxtrot East, will report over Mishrif."
Pilot: "Kuwait Tower, 9K-VFR overhead Mishrif"
TWR: "9-FR, roger, contact Kuwait Approach 124.800"
Callsign Shortening
With VFR Traffic you are allowed to abbreviate the callsign once contact has been established. Your first transmission with the aircraft must always include their full callsign however, from then on, you may abbreviate the callsign to 3 letters, this helps reduce frequency congestion.
3.5.2.2 VFR Zone Entry Phraseology
Pilot: "Kuwait Tower, 9K-VFR with you 5nm North West of the Qurain Shopping Area, Altitude 1000ft, request clearance into the Control Zone for Full Stop Landing"
TWR: "9K-VFR, Good Afternoon, cleared to enter the Control Zone, not above altitude 1000ft via Quebec East, VFR, QNH 1001, Squawk 7001"
Pilot: "Cleared to enter the Control Zone not above altitude 1000ft via Quebec East, VFR QNH 1001, Squawk 7001"
TWR: "9-FR, Readback Correct, report left downwind runway 15L."
Controller Preference
The Controller can elect where to have the inbound VFR traffic head to after they have recieved their initial zone entry clearance depending on traffic levels.
3.5.2.3 VFR Circuits
Pilot: "Kuwait Tower, 9K-VFR, with you holding point E2, ready for departure"
TWR: "9K-VFR, after departure right hand turn out, via W2, cleared for takeoff RWY33R, winds calm"
Pilot: "After departure right hand turn out, via W2, cleared for takeoff RWY33R, 9K-VFR"
Once the aircraft is airborne and established on the right hand turn off you can advise them to report downwind with intentions.
TWR: "9-FR, report downwind with intentions"
Pilot: "Wilco, 9-FR"
Pilot: "9-FR, right hand downwind RWY33R for touch and go"
TWR: "9-FR, roger, you are number 2 to a Qatari Airbus A350 on 5nm final, maintain visual separation, caution wake turbulence, report final runway 33R"
Pilot: "traffic is in sight, maintaining visual separation, will report final runway 33R, 9-FR"
Pilot: "A-ZZ, final runway 33R"
TWR: "A-ZZ, cleared touch and go runway 33R, winds calm, report downwind"
3.5.2.4 Traffic Information
The TWR Controller is responsible for providing VFR and IFR flights with the necessary traffic information to prevent any loss of seperation within the Control Zone (CTR).
Example:
TWR: "9-ZZ, traffic information, traffic is a Gulf Air Airbus A320, 7nm final RWY33R, report the traffic in sight"
Once the aircraft confirms they have the aircraft in sight, the TWR Controller can then further issue the aircraft with an instruction.
Example:
TWR: "9-FR, you are number 2 to the Gulf Air Airbus A320 on 7nm final RWY33R, maintain visual separation, caution wake turublence, report final Runway 33R"
3.5.2.5 VFR Service Requirements
Within the Class D Kuwait Control Zone (CTR) the TWR controller is not required to provide VFR traffic with separation, the only service provided to VFR traffic is Traffic Information between VFR and IFR aircraft. The pilot can request traffic avoidance on request, however it is up to TWR controller as to whether they can provide.