Skip to content

Islamabad Aerodrome Guide (OPIS)

1. Aerodrome Information

Item Information
Location Islamabad, Pakistan
ICAO / IATA OPIS / ISB
Coordinates N33° 32.9', E072° 49.5'
Elevation 1761 ft
Transition Altitude / Level 12000 ft / FL140

1.2 Communication Information

Position Callsign Frequency
Islamabad ATIS OPIS_ATIS 126.200
Islamabad Delivery OPIS_DEL 118.550
Islamabad Ground OPIS_GND 130.600
Islamabad Tower OPIS_TWR 122.150
Islamabad Approach OPIS_APP 121.650
Islamabad Departures OPIS_DEP 119.650

1.3 Navigational Aids

Instrument Identifier Frequency
ILS/DME RWY 28L IBBA 108.1
ILS/DME RWY 28R IBIP 110.7
ILS/DME RWY 10R IBAP 111.3
VOR BTR 114.6

1.4 Runways

Characteristics

Runway True/Magnetic Bearing Dimensions
28L 278/280 12001 ft × 197 ft
28R 278/280 12001 ft × 148 ft
10L 097/100 12001 ft × 148 ft
10R 097/100 12001 ft × 197 ft

Takeoff Distances

Runway TORA ASDA
28L 3658 m 3658 m
28R 3658 m 3658 m
10R 3658 m 3658 m
10L 3658 m 3658 m

2. Departure Clearance Procedures

Delivery Controller is responsible for validating routes and providing IFR clearance to departing aircraft. The controller shall assign the correct departure procedure based on the first point filed in the flight plan.

Where the flight plan contains an invalid route, level, or departure procedure, Delivery Controller shall ensure the error is corrected before clearance is issued.

2.1 Requesting ATC Clearance

Pilots are expected to report the following on first contact before requesting ATC clearance:

  1. Callsign
  2. Stand number
  3. Destination
  4. Current ATIS letter
  5. Requested flight level

2.2 Receiving ATC Clearance

An ATC clearance shall contain the following:

  1. Callsign
  2. Destination
  3. Departure procedure / Radar Vectors / SID / Airway
  4. Runway in use
  5. Initial flight level
  6. Assigned SSR code

Example

Pilot: Islamabad Delivery, PIA301 at stand 12, destination Karachi, requested level FL380, we have information C, requesting ATC clearance.

Controller: PIA301, Islamabad Delivery, cleared to destination Karachi enroute J121, INDEK2C departure, RWY 10R in use, initially climb and maintain altitude 8000 ft, expect higher enroute, squawk on departure 3642.

Pilot: Cleared to destination enroute J121 via the INDEK2C departure, RWY 10R, climb initially altitude 8000 ft, squawk 3642, PIA301.

Controller: PIA301, readback is correct, information C is current, report ready for push and start.

Note: QNH must be provided during taxi instructions.

Example

Controller: PIA301, taxi to holding point RWY 10R via M,T,K,A, QNH 1013.

2.3 Departure Procedures

2.3.1 RNAV Instrument Departures

Islamabad generally uses RNAV SIDs for departures and these are preferred. Certain non-RNAV SIDs may also be used.

Commonly used RNAV SIDs:

  1. BELKO2F
  2. DAMTO2G
  3. INDEK2D
  4. KALMI2D
  5. INDEK2C

2.3.2 Omni-directional Departures

When a pilot is unable to fly a SID, an omni-directional departure may be assigned. Aircraft can expect radar vectors to the first waypoint filed in the flight plan.

During takeoff clearance, Tower shall assign an initial heading. Further vectors will then be issued by Approach.

Example ATC Clearance

Pilot: Islamabad Delivery As-salamu alaykum, PIA301, stand 12, POB 112, requested level 380, request IFR clearance to Karachi, we are unable to accept SID.

Controller: PIA301, cleared to destination via the omni-directional departure, RWY 28L in use, initially climb and maintain altitude 8000 ft, squawk 3642.

Example Takeoff Clearance

Controller: PIA301, after departure turn right heading 010, surface winds 260 degrees 08 knots, RWY 28L, cleared for takeoff.

2.4 Runway Change

At Islamabad, the primary runway in use is RWY 28L due to the availability of CAT II and CAT III ILS systems which support low visibility procedures (LVP).

Aircraft already cleared shall receive updated clearances reflecting the revised runway and SID.

Example

Controller: PIA301, runway has been changed. ATC clearance available, report ready to copy.

Pilot: Ready to copy clearance, PIA301.

Controller: PIA301 re-cleared to destination via the INDEK2D departure, RWY 28L in use, initially climb to altitude 8000 ft, squawk 3642.

2.5 VFR Aircraft

2.5.1 General

VFR operations at OPIS are permitted subject to ATC clearance and prevailing traffic conditions. Due to high IFR traffic volume at Islamabad International Airport, VFR aircraft may be delayed, rerouted, or subject to altitude restrictions.

All VFR aircraft shall maintain continuous two-way radio communication with ATC while operating within controlled airspace.

2.5.2 Airspace Classification

The airspace surrounding OPIS is controlled airspace.

Therefore:

  • VFR flights require explicit ATC clearance before entry.
  • Standard VFR “see and avoid” principles apply.
  • ATC shall provide separation from IFR traffic where possible.
  • Pilots remain responsible for maintaining vigilance for other traffic.

2.5.3 VFR Entry and Exit Procedures

VFR aircraft shall use designated reporting points when entering or exiting the Islamabad CTR.

Pilots must report:

  1. Position
  2. Altitude
  3. Intentions

ATC may assign:

  1. Specific routing
  2. Altitude restrictions
  3. Holding instructions if required

2.5.4 Circuit Procedures

Standard traffic circuits at OPIS are conducted as follows unless otherwise instructed:

Item Information
Circuit Altitude Typically 1000 ft AGL (approximately 2800 ft)
Circuit Direction Left-hand or right-hand depending on runway in use
Circuit Area Always south of the airfield
Joining Procedure Overhead join or as instructed by ATC

Pilots shall:

  1. Report joining, downwind, base, and final
  2. Maintain spacing from preceding traffic
  3. Be prepared for extended circuits during busy traffic periods

3. Ground Movement Procedures

Ground Movement Controller (GMC) is responsible for all aircraft movements on aerodrome movement areas except runways and associated taxiways.

Departing aircraft are provided pushback and taxi instructions. Arriving aircraft are assigned stands and taxi routes.

For intersection departure requests, Ground Controller shall coordinate with Tower before approval.

3.1 Pushback Procedures

Aircraft requesting pushback without displaying the assigned transponder code shall remain on stand until the correct squawk is set.

Pushback or ground movement shall not be authorized until compliance is confirmed.

Depending on stand allocation, aircraft shall receive a specific pushback direction.

3.1.2 Coordination Requirement

Where pushback affects taxiway flow or sequencing, Ground Controller shall coordinate appropriately with adjacent positions.

3.2 Taxi Procedures

3.2.1 Departure Taxi Clearance

  • Aircraft shall receive taxi instructions to the appropriate holding point after pushback and engine start.
  • Taxi routes shall be issued in full where necessary.
  • Pilots shall read back all taxi instructions.

3.2.2 Taxi Route Management

  • Taxi instructions shall prioritize efficiency and safety.
  • Intermediate holding points may be used to regulate traffic.
  • Aircraft shall exercise caution at intersections and give way when instructed.

3.2.3 Runway Coordination and Holding Points

  • Aircraft shall not enter holding points without Tower clearance.
  • GMC shall hand aircraft to Tower at appropriate positions to avoid unnecessary stopping.

3.2.4 Taxiways for All Runways

Taxiway routing shall be assigned by Ground Controller based on stand allocation, active runway, and prevailing traffic conditions.

3.3 Stand Allocation Procedure

Main Terminal

Stand Range Usage
Stands 13–28 Domestic Flights
Stands 1–12 International Flights

3.3.1 Restrictions

  • Stands 6, 7, and 8 are certified for Super category aircraft operations including the A380.
  • Remaining stands support heavy to medium aircraft.
  • Stands 13–16, 25–28, 1–3, and 10–12 are remote stands without direct boarding infrastructure.

3.4 Handoff Procedures

Transfer of control between ATS units shall ensure continuous separation and situational awareness.

Controllers shall not issue clearances beyond their area of responsibility without coordination.

Aircraft may be instructed to hold at suitable intermediate points when required.

4. Aerodrome Procedures

The Aerodrome Controller (ADC) is responsible for all movements on active runways and associated taxiways.

ADC shall ensure safe and efficient IFR arrival and departure separation while also coordinating IFR and VFR operations within the control zone.

4.2 Preferred Runways

Due to CAT III ILS capability, RWY 28L is the preferred runway.

When wind conditions require a runway change combined with wind changes greater than 8 knots, RWY 10R becomes the preferred runway.

4.3 Departure Procedures

4.3.1 Line-up Clearance

Aircraft handed over to Tower may be cleared to line up once the runway is confirmed clear.

Example

Controller: PIA301, via Holding Point J, line up and wait RWY 28L.

Conditional Line-up Clearance

Controller: PIA301, behind departing company A320, line up and wait RWY 28L behind.

4.3.2 Takeoff Clearance

Aircraft shall be cleared for takeoff once separation standards are met.

Example

Controller: PIA301, surface winds 260 degrees 10 knots, RWY 28L, cleared for takeoff.

4.3.3 Separation Requirements

  • IFR departures shall comply with standard IFR separation minima.
  • Enhanced wake turbulence separation (eWTS) shall be applied where applicable.
  • Aircraft on the same SID shall generally receive a minimum spacing of two minutes unless reduced separation is permitted.
  • VFR departures may be cleared maintaining visual separation where appropriate.

4.3.4 Departure Handoff Procedure

Aircraft shall normally be handed to Departure after becoming airborne and reaching 1000 ft AGL.

Example

Controller: PIA301, airborne time 17, contact Islamabad Departures 119.650.

4.3.5 Omni-directional Departures

Aircraft conducting omni-directional departures may receive heading assignments after departure to assist with sequencing and terrain separation.

Example

Controller: PIA301, after departure fly heading 270, maintain altitude 2000 ft, wind 280 degrees 6 knots, RWY 28L, cleared for takeoff.

4.3.6 Rejecting a Departure

Aircraft may be instructed to reject takeoff where required to prevent unsafe situations.

Example

Controller: PIA301, cancel takeoff clearance, stop immediately, I say again, stop immediately.

4.4 Arrival Procedures

While Approach primarily manages arrival separation, ADC shall ensure separation is maintained until the preceding aircraft crosses the threshold safely.

4.4.1 Speed Restriction

ADC may issue speed control instructions to maintain arrival spacing.

Example

Controller: PIA301, surface winds 270 degrees 08 knots, RWY 28L, continue approach number 2, reduce to minimum approach speed for separation.

4.4.2 Visual Separation

Aircraft without Mode C or VFR aircraft may be instructed to maintain visual separation.

4.4.3 Go-around Instruction

Controllers may issue go-around instructions where landing is no longer suitable.

Example

Controller: PIA301, go around, I say again, go around, acknowledge going around.

Pilot: PIA301 going around.

Controller: PIA301, continue missed approach procedure, contact Islamabad Departures 119.650.

4.4.4 Arrival Taxi Procedure

After vacating the runway, aircraft shall receive taxi instructions and be transferred to Ground once fully clear of the runway environment.

4.5 VFR Procedures

ADC is responsible for managing all VFR traffic within the control zone.

4.5.1 VFR Departures

Once ready and traffic conditions permit, VFR aircraft shall be cleared for departure in an orderly sequence.

Aircraft shall report when leaving the control zone.

4.5.2 VFR Traffic in Circuit

At Islamabad, circuit operations are conducted south of the airfield.

Aircraft shall:

  • Enter downwind as instructed
  • State intentions
  • Expect orbit instructions during IFR arrival sequencing where required

Once orbiting is no longer required, ADC shall issue base turn instructions followed by landing or touch-and-go clearance.

4.5.3 VFR Arrivals

Inbound VFR aircraft shall establish contact with ADC before entering the control zone.

ADC shall issue:

  • Joining instructions
  • Circuit direction
  • Circuit altitude
  • Runway in use
  • Traffic information
  • Sequencing requirements

Pilots shall remain outside controlled airspace until clearance to enter has been issued.