TWR - Erbil Tower
Chapter 1. Position Overview¶
Erbil Tower (TWR) controls aircraft on the runway, aircraft holding at runway holding points, and aircraft operating within the Class D Erbil Control Zone. The TWR Controller is responsible for all airborne arrivals and departures at and below 6000ft within the Erbil CTR.
Erbil is a procedural tower environment. Due to the lack of radar, only one aircraft must operate in the non-radar procedural airspace at one time. Special caution must be taken due to terrain east of the airport.
The TWR Controller is responsible for selecting the active runway for arrivals and departures at Erbil and holds full authority over the runway.
| Position | Callsign | Frequency | Logon Callsign |
|---|---|---|---|
| Erbil TWR | Erbil Tower | 128.800 | ORER_TWR |
| Erbil ATIS | 130.400 | ORER_ATIS |
Chapter 2. Airspace¶
The Erbil Control Zone (CTR) is Class D Airspace from the surface up to 6000ft. The TWR Controller is responsible for ensuring traffic inside the CTR is managed safely, including IFR departures, IFR arrivals, VFR aircraft operating within the CTR, and VFR aircraft entering or exiting the CTR.
Chapter 3. GEN | Standard Operating Procedures¶
3.1 Runway Selection¶
At Erbil International Airport (ORER), the preferential runway for arrivals and departures is Runway 18 and shall be used when the tailwind component is less than 8 knots. Winds must always be considered when selecting the runway mode. Crosswind must be less than 20 knots and tailwind must be less than 5 knots, unless using the published preferential runway allowance.
| Priority - Mode | Arrivals | Departures | Remarks |
|---|---|---|---|
| 1 - MODE A | 18 | 18 | Preferential runway |
| 2 - MODE B | 36 | 36 |
3.1.1 Runway Change¶
If the TWR Controller deems it necessary to change the active runway due to wind, traffic flow, or operational requirement, this should be coordinated with the relevant Baghdad TMA controller. This must not be done suddenly, as it affects arrival sequencing, departure releases, and issued clearances.
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. The instruction should include the runway designator, the holding point at which the aircraft is to enter the runway, and any relevant traffic information.
Example:
TWR Controller: "IAW23, via A1, line up and wait runway 18."
3.2.1 Conditional Line Up Clearance¶
The TWR Controller may issue a conditional line-up clearance in order to maximise runway efficiency. The condition must be clear and precise, and the word behind should be used at the start and end of the instruction.
Example:
TWR Controller: "IAW23, behind the landing Iraqi Airways Boeing 737, via A1, line up and wait runway 18, behind."
3.3 Take Off Procedures¶
3.3.1 Standard Instrument Departures (SIDs)¶
All IFR departures from Erbil shall normally be assigned a Standard Instrument Departure (SID). Controllers shall assign the correct SID exit waypoint based on the first enroute waypoint in the aircraft's flight plan, and the correct procedure identifier based on the selected departure runway.
All SIDs with an identifier of 1N are valid for Runway 36. All SIDs with an identifier of 1S are valid for Runway 18.
| SID | Runway 36 | Runway 18 |
|---|---|---|
| DAVAS | 1N | 1S |
| EMIDO | 1N | 1S |
| ROXOP | 1N | 1S |
| UMESA | 1N | 1S |
Departures should primarily adhere to the published SID routes. Radar vectors should be avoided whenever feasible. If radar vectors are assigned, a specific reason must be provided.
Example:
Pilot: "Erbil Tower, IAW123, request clearance to Antalya, with information Alpha."
TWR Controller: "IAW123, Erbil Tower, cleared to Antalya, EMID1S departure, flight planned route, initial climb 6000ft, squawk 4301."
3.3.2 Omni-Directional Departures¶
Aircraft may only be assigned an omni-directional departure if they are unable to fly the published SIDs.
If a departing aircraft is receiving an omni-directional departure, they must receive an assigned heading with their line-up or take-off clearance.
| Runway | Heading |
|---|---|
| 18 | H175 |
| 36 | H355 |
Example:
Pilot: "Erbil Tower, IAW123, request clearance to Antalya, with information Alpha."
TWR Controller: "IAW123, Erbil Tower, cleared to Antalya, expect omni-directional departure, flight planned route, squawk 4301."
3.3.3 Take Off Clearances¶
Aircraft should only be given take-off clearance once the runway is clear of obstructions and separation from any previously departed or arriving aircraft has been achieved.
Example:
Pilot: "IAW23 ready for departure."
TWR Controller: "IAW23, after departure climb to altitude 6000ft, fly runway heading, surface winds variable at 3 knots, runway 18 cleared for take-off."
3.3.4 Handing Off¶
Departing aircraft shall be transferred to the relevant Baghdad TMA controller once safely airborne and released from Tower jurisdiction.
Example:
TWR Controller: "IAW23, contact Baghdad Approach 124.800."
3.3.5 Stopping a Departure¶
In the event a departure must be stopped after take-off clearance has been issued, the instruction must be issued immediately and clearly.
Example:
TWR Controller: "IAW23, stop immediately, I say again, stop immediately, runway incursion."
For an aircraft that has not yet begun the take-off roll, cancel take-off clearance and instruct the aircraft to hold position.
Example:
TWR Controller: "IAW23, hold position, cancel take-off, I say again, cancel take-off due runway incursion."
3.4 Arrival Procedures¶
In addition to aircraft on the ground at Erbil, ORER_TWR is responsible for airborne arrivals and departures at and below 6000ft. As Erbil is a procedural airport, arrivals must be managed carefully to ensure only one aircraft operates in the non-radar procedural airspace at one time.
3.4.1 Approach Monitoring¶
Inbound aircraft should be instructed to report established on the relevant approach. Special caution must be taken due to terrain east of the airport.
Example:
Pilot: "Erbil Tower, IAW123, inbound ILS-Z runway 18, descending through 7000ft."
TWR Controller: "IAW123, Erbil Tower, report established on the ILS runway 18."
3.4.2 Landing Clearance¶
The TWR Controller is responsible for issuing landing clearance once the runway is clear and safe for landing.
Example:
TWR Controller: "IAW123, surface winds 320 degrees 5 knots, runway 18, cleared to land."
3.4.3 Late Landing Clearance¶
If traffic may receive a late landing clearance due to preceding traffic vacating slowly or a departure ahead, the aircraft may be advised to expect late landing clearance.
Example:
TWR Controller: "IAW123, expect late landing clearance, one to vacate ahead."
3.4.4 Vacating Traffic¶
All departing aircraft shall be assigned the most appropriate taxiway onto Taxiway A. Erbil TWR must exercise extreme caution on Taxiway A, as conflicts can easily occur between arriving and departing traffic. Taxiway B is restricted to military traffic only.
Example:
TWR Controller: "IAW123, vacate via A1, continue taxi via A."
3.4.5 Go Around Procedures¶
The TWR Controller shall issue go-around instructions if the runway is obstructed, separation is lost, or landing clearance cannot be safely issued.
Example:
TWR Controller: "IAW123, go around, I say again, go around, acknowledge."
Once the aircraft has acknowledged the go-around, Baghdad TMA shall be notified immediately. After a go-around, the next departure from that runway requires next coordination.
3.5 VFR Procedures¶
All VFR clearances are assigned by Erbil TWR. VFR procedures inside the Erbil CTR must be conducted at or below A060.
VFR departures should be given departure instructions, including turn directions, routing or leg to exit the circuit when appropriate, and altitude. VFR aircraft shall be assigned an SSR code.
Aircraft may request a touch and go, stop and go, low approach, or full stop. Once the TWR Controller is aware of the aircraft's intentions within the CTR, they may be sequenced to the runway with due consideration given to runway occupancy time and IFR traffic.
3.5.1 Traffic Remaining in VFR Circuit¶
VFR circuits are permitted on Runways 36 and 18. Aircraft wishing to remain in the circuit at Erbil shall be issued not above A060 and the following circuit directions:
| Runway | Circuit Direction |
|---|---|
| 18 | Right-Hand |
| 36 | Left-Hand |
VFR circuits shall not be permitted during periods of increased IFR departure or arrival activity.
3.5.1.1 VFR Circuits Phraseology¶
Pilot: "Erbil Tower, ABC holding short A1 runway 18."
TWR Controller: "ABC, Erbil Tower, cleared to operate in the circuit area not above altitude 6000ft, right hand circuits report downwind, surface winds 320 degrees 5 knots, cleared for take-off runway 18."
Pilot: "Cleared to operate in the circuit area not above altitude 6000ft, will report right downwind, cleared for take-off runway 18, ABC."
3.5.2 Zone Exit Clearances¶
Once VFR aircraft are ready for departure, they shall be cleared for take-off in sequence. As they begin their crosswind turn, they shall be instructed to report leaving the Erbil CTR.
Aircraft requesting to exit the Erbil CTR shall be assigned a clearance limit followed by a valid VFR cruising altitude.
Example:
Pilot: "Erbil Tower, YYC is requesting to exit the Erbil CTR via direct Kirkuk, altitude 5500ft."
TWR Controller: "YYC, Erbil Tower, cleared to leave the Erbil CTR direct Kirkuk, maintain altitude 5500ft, squawk 7403, QNH 998 hectopascals."
Pilot: "Cleared to leave the Erbil CTR direct Kirkuk, maintain altitude 5500ft, QNH 998, squawk 7403, YYC."
Once airborne:
TWR Controller: "FYI, report leaving the Erbil CTR, maintain at or below altitude 6000ft."
3.5.3 Inbound VFR Traffic¶
Inbound VFR aircraft shall be sent to Erbil TWR with enough time for two-way radio communications to be established before aircraft receive clearance to enter the Erbil CTR.
On initial contact, Erbil TWR shall pass instructions for joining the circuit and any other relevant traffic information. During times of heavy IFR arrival activity, VFR arrivals may be denied entry into the CTR and instructed to hold outside the CTR awaiting further instructions.
Example:
Pilot: "Erbil Tower, YYC is requesting to enter the Erbil CTR from the south for circuits."
TWR Controller: "YYC, Erbil Tower, information A, cleared to enter the Erbil CTR, maintain at or below altitude 6000ft, report right downwind runway 18 with intentions, squawk 7403."
Pilot: "Information A, cleared to enter the Erbil CTR, at or below altitude 6000ft, will report right downwind runway 18 with intentions, squawk 7403, YYC."
TWR Controller: "YYC, correct, QNH 998 hectopascals."
Chapter 4. Coordination¶
4.1 Departure Procedures¶
Due to the airspace structure at Erbil, all departures shall be coordinated and receive a release for departure from the relevant Baghdad TMA controller before release.
Next coordination is not required to Baghdad TMA for aircraft that are:
- Departing from a runway nominated on the ATIS
- Assigned the standard assignable level and
- Assigned a procedural SID or
- Assigned a standard assignable heading.
Next coordination is required for:
- Visual departures
- All departures not on a standard assignable heading and
- The next departure from that runway after a go-around.
The standard assignable level from Erbil TWR to Baghdad TMA is:
| Aircraft | Level |
|---|---|
| IFR | A060 |
| VFR | A060 |
4.2 Standard Assignable Departure Headings¶
If a departing aircraft is receiving an omni-directional departure, they must receive an assigned heading with their line-up or take-off clearance.
| Runway | Heading |
|---|---|
| 18 | H175 |
| 36 | H355 |
If strong winds are present at altitude, TWR and TMA should discuss slight changes to these headings to compensate for large crosswind components.