REPUBLIC OF AFGHANISTAN
ENROUTE
PART 2
EDITION 84
2. ATS Airspace Classes, Service Provided & Flight Requirements ENR 1.4-2
3. Separation………………………………………...................... ENR 1.4-3
4. Wake Turbulence ................................................................. ENR 1.4-3
5. Airspace Control Measures.................................................. ENR 1.4-3
ENR 1.5 Holding, Approach and Departure Procedures……… ......... ENR 1.5-1
1. Holding……………………………………… ........................... ENR 1.5-1
2. Arriving Flights ..................................................................... ENR 1.5-1
3. Departing Flights .................................................................. ENR 1.5-2
4. Military and Civil Aircraft Lighting Requirements ................. ENR 1.5-2
ENR 1.6 ATC Surveillance Services and Procedures…………….… . ENR 1.6-1
1. Services and Coverage........................................................ ENR 1.6-1
2. Radio Failure Procedures .................................................... ENR 1.6-1
3. Deviation from Airways ........................................................ ENR 1.6-1
ENR 1.7 Altimeter Setting Procedures………………………... ............ ENR 1.7-1
1. Standard Altimeter Pressure Setting.................................... ENR 1.7.1
2. Flight Levels ......................................................................... ENR 1.7-1
ENR 1.8 Regional Supplementary Procedures……………………… .. ENR 1.8-1
ENR 1.9 Air Traffic Flow Management…………................................. ENR 1.9-1
1. ATFM BOBCAT Kabul FIR .................................................. ENR 1.9-1
2. PPR General ........................................................................ ENR 1.9-7
3. PPR Request. ...................................................................... ENR 1.9-8
ENR 1.10 Flight Planning…………………………….............................. ENR 1.10-1
1. General ................................................................................ ENR 1.10-1
2. Procedures Applicable to Operators/Pilots .......................... ENR 1.10-1
3. Approval Prior to Flight Plan Submission............................. ENR 1.10-3
4. Flight Plan Information ......................................................... ENR 1.10-3
ENR 1.11 Addressing of Flight Plan Messages………………………… ENR 1.11-1
1. General……………………………………….... ...................... ENR 1.11-1
2. Mazar-e-Sharif (OAMS) Requirements……. ........................ ENR 1.11-1
3. Kabul (OAKB) Requirements…...... ..................................... ENR 1.11-1
ENR 1.12 Interception of Civil Aircraft…………………... ...................... ENR 1.12-1
1. Interception Procedures ....................................................... ENR 1.12.1
2. Phraseology during Interception .......................................... ENR 1.12.1
3. Signals for use in the Event of Interception ......................... ENR 1.12.2
ENR 1.13 Unlawful Interference…………………………. ...................... ENR 1.13-1
1. General………………………. ............................................... ENR 1.13-1
2. Procedures……………......................................................... ENR 1.13-1
ENR 1.14 Air Traffic Incidents…………………………………. .............. ENR 1.14-1
3.2.2. For Afghanistan based operators and the operators of civil ACFT registered in
Afghanistan, the RVSM approval is to be obtained from the ACAA Flight Safety and
Standards Office. Once obtained, RVSM approval is not restricted to a specific
region. Instead, it is valid globally, where RVSM procedures are applied, with the
understanding that any operating procedures specific to a given region should be
3.14.2. Wake Vortices Encounters: Due to the special nature of the airspace and frequent
poor communications, pilots are to make every effort to contact KACC prior to making
maneuver away from wake vortices. Pilots are in all cases to report the presence of
wake vortices as soon as possible to allow KACC to provide increased vertical
separation on a tactical basis.
3.15. Pilot Actions:
3.15.1. When an ACFT is operating in the Afghanistan RVSM airspace and encounters
severe turbulence due to weather or wake vortex, and the Pilot-in-Command believes
the vertical navigation performance requirements for Afghanistan RVSM airspace
cannot be maintained, the pilot shall:
a. Inform ATC as soon as possible (‘UNABLE RVSM DUE TURBULENCE’);
b. Obtain a revised ATC clearance prior to initiating any deviation from cleared route
or flight level;
c. Where such revised ATC clearance could not be obtained prior to such a
deviation, obtain a revised clearance as soon as possible thereafter.
3.15.2. These procedures should not be interpreted in any way that prejudices the final
authority and responsibility of the Pilot-in-Command for the safe operation of the
ACFT.
3.16. Controller Actions:
3.16.1. The Air Traffic Controller shall:
a. Establish either an appropriate horizontal separation or an increased vertical
separation of 2000ft;
b. To the extent possible, accommodate the pilot's request for flight level and/or
route changes and pass traffic information as required;
c. Confirm that the pilot is ready to resume RVSM operations ('REPORT READY TO
RESUME RVSM').
3.17. CONTROLLER/PILOT RVSM PHRASEOLOGY
1. ATC ascertain the RVSM approval (call sign) CONFIRM RVSM APPROVED
status of a flight
5. ATC denial of clearance into the RVSM (call sign) UNABLE CLEARANCE INTO
airspace: RVSM AIRSPACE, MAINTAIN (or
DESCEND/CLIMB TO) FLIGHT LEVEL
(number)
9. To solicit this information ATC shall use (call sign) REPORT ABLE TO RESUME
the phrase: RVSM
4. Horizontal Separation
4.1. Where surveillance separation standards are not being applied, longitudinal
separation is established between IFR ACFT at the same level, equal to or greater
than ICAO minimums. Speed control may be applied between ACFT that are at or
near the minimum longitudinal separation standards to prevent loss of separation.
4.1.1. 50NM or 7-minute longitudinal separation will be applied on ATS routes L750, N644,
M875, P173, L509, UL333, V848, and P628/N636.
5. Flight Priorities
5.1 The following flight priorities apply within the AFG FIR:
a. Aircraft in Distress (declared emergency such as engine fault, fuel
shortage/diversion, seriously ill passenger, etc.) *
b. Flights are carrying the President of Afghanistan (POA).
c. National Priority Missions when executed by counter-terrorism forces and
support aircraft; or Afghan National Defense Security Forces (ANDSF) and RS
Coalition partners securing national objectives or securing the critical
preservation of life. When this exception is required, aircraft, ATC and /or
Tactical Command and Control (TAC C2) agencies should use the term priority
d. Flights are operating as air ambulances (call sign "MEDEVAC," “AIREVAC" or
"HOSP").
e. Flights are supporting Search and Rescue efforts to include (CSAR/PR/CAS
EVAC or other humanitarian reasons (Human Remains Flights).
f. Flights notified by the ACAA carrying visiting heads of State/Government (to
include Prime Ministers) and very senior GIRoA Ministers.
g. Flight check aircraft engaged in critical calibration flights. Other flights
authorized by the ACAA.
h. IFR Flights. Flights that have filed a flight plan and are conforming to routine
procedures. Training, non-standard and other flights.
i. Military support tasks, unless supporting priority operations as noted in Cat E.
j. Training, non-standard and other flights (i.e. VFR flights)
6. Military Activity
6.1. Afghanistan’s airspace contains complex military activity by aircraft, which may not
follow the rules of the air inside reserved military areas.
6.2. Agreed in advance between the ACAA and Coalition Military forces, information on
activity is published via following means;
a. Afghanistan AIP
b. NOTAM
c. As coordinated with ATC
6.3. Where possible, information has been declassified and is available on the ACAA
website or within this AIP. KACC, TAC C2, and Local ATC units will act as
coordinators to maintain safety and integrate civil traffic with ongoing ACMs.
6.4. TAC C2 units have established ATC CAL (Coalition Airspace Liaison) positions. This
personal coordinates the deconfliction of military operations, which need to occur in
ATC airspace.
6.5. ATC will use every communication means available to maintain civil and military
aircraft safety. If coordination with aircraft under TAC C2 control is required, ATC will
coordinate with TAC C2.
6.6. TAC C2 will coordinate special use airspace/areas (SUAs) under their control, with
any affected ATC facility prior to the SUA becoming active. TAC C2 will also notify
ATC of any changes to SUAs or when the area is no longer required.
1 500 m horizontally
At and below 3 000 ft. A* C D E 5 km
AMSL, or 1 000ft above 1 000ft vertically
terrain, whichever is the
higher Clear of cloud and with the
G 5 km
surface in sight
* The VMC minima in Class A airspace are included for guidance to pilots and does not imply
acceptance of VFR flights in Class A airspace.
3.1.1. There are no altitude restrictions on military VFR ACFT within Class G airspace.
Military VFR ACFT may cross Class E air routes up to and including FL285, subject to
ATC clearance.
3.2. All civilian VFR flights must adhere as much as possible to the published air route
corridors in order to segregate from military activity. Compliance with these
procedures does not relieve pilots of own responsibility to see and avoid other ACFT
or for maintaining own safe terrain/obstacle clearance at all times.
3.3. Except when necessary for take-off, landing or by permission of an appropriate
authority, a VFR flight shall not be flown:
a. Over the congested areas of cities, towns or settlements or over an open air
assembly of persons at a height less than 1000ft above the highest obstacle
within a radius of 600m of the ACFT;
b. Elsewhere, at a height less than 500ft above the ground or water.
3.4. Civil ACFT operating in Class G airspace shall keep to the minimum tracking
possible. This includes departing and joining the Air Routes at 90 degrees from the
aerodrome.
4. Air Traffic Services
4.1. VFR flights shall comply with the provisions of air traffic control instructions:
a. When operated within Class C and D airspace;
b. When forming part of aerodrome traffic at controlled aerodromes; or
c. When operating within or into designated controlled airspace and shall
maintain continuous air-ground voice communication on the appropriate
communication channel and report position as necessary to the air traffic
services unit providing air traffic services.
4.2. All VFR ACFT must receive a clearance prior to entering Class C and Class D
airspace. Flight advisory with Kabul ACC should not be construed as a clearance to
enter Class C or Class D airspace.
5. VFR Flight in Class E airspace
5.1. Prior to entering Class E airspace, all VFR ACFT (military and civil) shall establish
two-way communications with either an ATC or TAC C2 agency. This includes prior
to crossing Class E Air Routes. TAC C2 will coordinate air route crossings with ATC
to ensure deconfliction. VFR ACFT unable to comply shall remain clear of Class E
airspace until communications can be established.
6. VFR Flight in Class G airspace
6.1. Prior to VFR flight through Class G airspace, aircrew must communicate with an ATC
and/or Military TAC C2 agency.
6.2. All VFR ACFT should monitor Guard (UHF/243.0 preferably, 121.5 if VHF capable
only) in addition to the Common Traffic Advisory Frequency (CTAF) 125.2, or as
otherwise directed. TAC C2 will attempt to establish two-way communication with
aircrew on these frequencies if deviation from the current flight path is required for
deconfliction.
6.3. ATC will provide VFR ACFT departing from controlled airfields within Afghanistan an
airspace deconfliction service within the Class G airspace surrounding the
aerodrome’s CTR and traffic information, if practicable. On entering Class G
airspace, VFR ACFT will then be instructed to contact a TAC C2 agency or broadcast
on CTAF 125.2.
6.4. VFR ACFT arriving at or departing an aerodrome providing a Class G ATZ are to
contact the AD FIS provider prior to entering the ATZ or prior to departure (refer ENR
2.1para. 1.1 for Class G ATZ locations, dimensions and frequency information). On
departure, ACFT are also to broadcast intentions on CTAF 125.2 and attempt to
contact TAC C2 prior to exiting the ATZ.
6.5. For aerodromes located in Class G airspace, with no supporting Class G ATZ FIS
provider, ACFT shall attempt to contact TAC C2 for traffic and hazardous airspace
information. ACFT should also broadcast intentions on the CTAF 125.2.
6.6. ACFT on Class E airways in contact with KACC that are required to leave the airway
to reach their destination will, workload permitting, receive traffic and airspace
avoidance advice from KACC prior to leaving the airway. When leaving the airway,
KACC will instruct the ACFT to contact TAC C2 or broadcast on CTAF 125.2 for
further traffic and airspace avoidance advice.
6.7. Due to the line of sight limitations (both UHF/VHF), two-way communication with TAC
C2 may not be possible. Aircrews are to broadcast on the TAC C2 frequency for the
duration of flight in Class G airspace. Flight within Class G airspace under these
circumstances is at high risk; therefore, aircrew is to maintain an increased level of
seeing, avoiding and continue flight with due regard.
7. TAC C2 communication procedures
7.1. Military ACFT are to provide the following information on the first contact with TAC
C2:
a) ACFT call sign
b) Mode 3
c) Departure Aerodrome or Position
d) Destination or Next Position
e) Current Altitude
f) Requested Altitude
g) KINGPIN Check-in Example communication:
“Kingpin, Dash08, squawking 4501, 5 miles north Sharana, enroute Bagram, currently
11 thousand 5 hundred feet, request Flight Level 165 for transit.”
TAC C2 Check-in Example communication in the blind (both TAC C2 and TAF125.2):
“Kingpin All stations NATO276, squawking 3615, 5 miles south of Herat, enroute
DILAM, passing 3 500, climbing to FL205.”
7.2. Radio and radar coverage are permitting, TAC C2 may provide airspace and ACFT
deconfliction, workload permitting, while within Class G airspace by recommending
heading, altitude, and/or traffic information.
7.3. If TAC C2 is unable to provide these services due to limited radar coverage, aircrew
will be advised that TAC C2 have ‘negative radar contact.' TAC C2will then direct
aircrew to ‘proceed at your own discretion’ while providing restricted airspace advice.
Aircrew may be asked to respond to additional position requests.
7.4. If TAC C2 is unable to provide these services due to limited radio coverage, TAC C2
will attempt to establish contact with the ACFT on the TAC C2 frequency, CTAF 125.2
and/or Guard. Additionally, TAC C2 may use other ACFT in the vicinity to relay
avoidance advice.
7.5. While providing airspace and ACFT deconfliction to ACFT in Class G airspace, TAC
C2 may be tasked with higher priority requirements. TAC C2 may discontinue service
without notice but will endeavor to inform ACFT prior to termination. If ACFT believes
a termination of service has occurred, they are to adopt standard CTAF broadcast
procedures.
8. Change to Instrument Flight Rules (IFR)
8.1. An ACFT operating VFR that wishes to change to IFR shall:
a. If a flight plan was submitted, communicate the necessary changes to be
effected to its current flight plan, or
b. Submit a flight plan to the appropriate air traffic services unit and obtain a
clearance prior to proceeding IFR when in controlled airspace.
8.2. ACFT departing satellite airports in contact with ATC will be instructed to report a
position or waypoint within Class E Airspace. On reaching this position or waypoint,
ACFT should expect to receive an IFR clearance; however, ATC may issue an IFR
clearance earlier to become effective at the position or waypoint. If air traffic control is
unable to issue an IFR clearance immediately, the controller will advise the pilot when
or where to expect an IFR clearance.
9. Special Visual Flight Rules (SVFR)
9.1. SVFR may be approved under certain conditions at some airfields throughout
Afghanistan. Pilots are to refer to the Aerodrome (AD) section, of this document, to
acquire information on SVFR for individual AD.
10. VFR Reporting Points
10.1. To increase situational awareness and assist in identifying potential conflictions within
the Kabul FIR, Pilots in Class G airspace are to make position reports using the VFR
reporting points and transmitting on the CTAF 125.2 MHz
10.2. The pilot in command (PIC) is to ensure that reports are made within 6NM of the VFR
reporting point. Direct over-flight of the VFR reporting point should be avoided.
10.3. The direction of flight shall be referenced using the phonetic alphabet. The following
is an example of phraseology to be used:
10.3.1. “Afghanistan Traffic, Call sign [aircraft identification], vicinity [VFR reporting point] /
North West [cardinal direction].
10.4. ACFT transmitting should avoid using number and type of ACFT unless there is
potential for conflict with other traffic. If other traffic is identified within the vicinity, the
PIC may pass information that will assist in ACFT deconfliction, such as a number of
ACFT and altitude.
10.5. The Afghanistan VFR Waypoint structure is contained in a separate document titled
“Visual Flight Rules Reporting Points Republic of Afghanistan” and is accessible
via the ACAA website.http://acaa.gov.af/en/page/civil-aviation-authority/atm/aip---
important-information. This document is under revision and may not be accurate.
CLASS G AIRSPACE
AIR-ROUTES CLASS A
Above FL290 to FL510
FL300
FL280‐FL290 and FL310‐FL510*
from 2000Z‐2359Z
*= UL333, L750, N644, L509 and M875.
G206 MAL FL350
AIR-ROUTES CLASS E
FL160-FL290
IFR FL240 and above
IFR/VFR at or below FL235
CLASS D CTR
See ENR 2.1.3
2
IFROnly All aircraft ATC service N/A Continuous two- Yes
A
way
IFR IFR from IFR ATC service N/A Continuous two- Yes
way
IFR from VFR
VFR VFR from IFR 1) ATC service for 250kt IAS Continuous two- Yes
C
separation from IFR2) below 10000ft way
VFR/VFR traffic AMSL
information (and traffic
avoidance advice on
request
IFR IFR from IFR ATC service, traffic 250kt IAS Continuous two- Yes
information about VFR below 10000ft way
flights (and traffic AMSL
avoidance advice on
request)
D
VFR Nil IFR/VFR and VFR/VFR 250kt IAS Continuous two- Yes
traffic information (and below 10000ft way
traffic avoidance advice AMSL
on request)
IFR IFR from IFR ATC service and, as far 250kt IAS Continuous two- Yes
as practicable, traffic below 10000ft way
information about VFR AMSL
4 flights
E
3&4
VFR Nil Traffic information as far 250kt IAS Continuous two- No
as practical below 10000ft way
AMSL
Note 1: VFR aircraft with in Class G airspace must contact a TAC C2 agency or broadcast on 125.2. See ENR 1.2 paragraph
6.
Note 2: VFR Military aircraft may be cleared to cross Class A airways by ATC provided they are separated from IFR traffic up
to and including FL295.
Note 3: All VFR aircraft (includes military) in Class E shall be in contact with the appropriate ATC or TAC C2 agency. See
ENR 1.2 paragraph 5.
Note 4: HEAVY wake turbulence category aircraft (aircraft with a Maximum Take-off Weight (MTOW) greater than 136,000kg)
shall operate IFR when transiting via Class E Air Routes.
Note 5: Due to ongoing combat operations access for Civil IFR ACFT remains prohibited in Class G airspace. Civil VFR
operations in Class G airspace shall, as far as practicable, also be kept to the minimum to enhance the safety of ACFT
operations.
Note 6: Due to limited low-level communications coverage, military IFR is required to carry serviceable radios and broadcast
intentions on CTAF 125.2.
2.1. Unless otherwise defined in ENR 2.1, when ATS airspace adjoins vertically (one
above the other), flights at the common level must comply with the requirements of
and will be given services applicable to the less restrictive class of airspace. In
applying these criteria, Class C airspace is considered less restrictive than Class A
airspace, etc.
2.2. When Class C and D adjoin laterally, flights at the common boundary will be given
services applicable to Class D airspace.
3. Separation
3.1. Separation standards, including wake turbulence, applied in the Kabul FIR are in
accordance with ICAO Doc 4444 Procedures for Air Navigation Services – Air Traffic
Management except where coalition ATC has been given authority to use their home
nation separation standards.
4. Wake Turbulence
4.1. Categories. For the purpose of wake turbulence, ACFT are divided into the following
weight categories:
a. HEAVY (H) − All other ACFT types of 136,000KG maximum take−off weight or
more;
b. MEDIUM (M) –ACFT types of less than 136,000KG maximum take-off weight
but more than 7,000KG maximum takeoff weight;
c. LIGHT (L) –ACFT types of 7,000KG maximum take-off weight or less.
Note: B757 and H47 (Chinook) are categorized Heavy (H) when the following ACFT is
categorized either Medium (M) or Light (L) and categorized Medium (M) when the
preceding ACFT is categorized Heavy (H).
5. Special Use Airspace (SUAs)
5.1. SUAs are airspace constructs of defined vertical and lateral dimensions created to
allow military aerial operations to take place in a segregated environment. They are
activated at the request of users via NOTAM, or tactically via ATC, and deactivated
once the activity has been completed. These SUA constructs take precedence over
all airspace categories within Afghanistan. In this event, as much notice as possible
will be given pre-activation.
5.2. When notified of an SUA activation KACC will ensure that IFR traffic in controlled
airspace is routed clear of the activated SUA. VFR traffic or aircraft operating in
uncontrolled airspace may not receive directed notification that an SUA has been
activated. Those aircraft should monitor the Common Traffic Advisory Frequency
(CTAF) 125.2 to receive any update broadcasts. TAC C2 will use all available
sensors to ensure that the area is clear prior to activation. In only extreme
circumstances where sufficient time does not exist to clear the area of traffic, and
there is imminent danger of lives being lost, the TAC C2 may clear an ACFT into the
SUA. KACC will provide traffic information to affected ACFT while the TAC C2
agency will pass details of transiting traffic to the military ACFT operating within the
ACM airspace.
5.3. The Afghanistan SUA areas, their geographical location and height blocks are found
in ENR 5.
will enter the Turkmenabad FIR at FL200 and above. No VFR ACFT will be permitted
to fly into Turkmenabad FIR at FL200 and above.
1.1 Provision of ATFM Services for Flights Transiting Kabul FIR (BOBCAT ATFM)
1.1.1 As one of the ATFM services provided, Bangkok Air Traffic Flow Management Unit
(Bangkok ATFMU) provides ATFM service for flights intending to transit Kabul FIR
between 2000 UTC and 2359 UTC daily. The service provided includes calculation,
promulgation, and management of mandatory Calculated Take-Off Time (CTOT) and
flight level, ATS route, and Calculated Time-Over (CTO) at entry waypoint for entry
into Kabul FIR for each affected flight.
1.1.2 Air Navigation Service Providers (ANSPs) retain responsibility for the tactical
management of flights that are subjected to this ATFM measure. In discharging
tactical responsibilities, ANSPs will manage non-ATFM compliant flights using
delayed pushback and start clearances, non-preferred routes and/or flight levels,
enroute holding and/or diversion around Kabul FIR.
1.1.3 Bangkok ATFMU utilizes the automated, web-based Bay of Bengal Cooperative
ATFM System (BOBCAT) in meeting its Kabul FIR ATFM responsibilities. These
responsibilities will be managed in coordination with aircraft operators and ANSPs in
the FIRs concerned.
1.1.4 The following subsection 1.2 of this section describes in greater detail the procedures
involved in this ATFM service. The objectives of this service are to:
Reduce ground and enroute delays;
Maximize capacity and optimize air traffic flow through Kabul FIR;
Provide an informed choice of routing and flight level selection;
Alleviate unplanned in-flight re-routing and technical stops; and
Assist regional ANSPs in planning for and managing workload in handling
increased air traffic flow through Kabul FIR.
1.2 BOBCAT ATFM-Affected ATS Routes, Flight Levels, and Applicable Period
1.2.1 All westbound flights intending to enter the Kabul FIR between 2000 UTC and 2359
UTC daily on ATS routes and Flight Levels in Table 1 shall comply with the BOBCAT
ATFM procedures contained herein. This includes a mandatory requirement for all
flights to obtain a specific ATFM slot allocation – CTOT, CTO at Kabul FIR entry
waypoint, allocated flight level, and allocated ATS route – from the Bangkok ATFMU
for entry into Kabul FIR during the period above mentioned.
Table 1: ATS Route and Flight Levels Requiring ATFM Slot Allocation
Routing
Metering
through the Flight Level
Waypoint(s)
Kabul FIR
L509-M875 LAJAK FL300, FL320, FL340, FL360, FL380, FL400
M875 SITAX FL280
FL280, FL300, FL320, FL340, FL360, FL380,
N644 DOBAT
FL400
FL280, FL300, FL320, FL340, FL360, FL380,
L750 BIROS
FL400
P628 ASLUM FL320, FL340, FL360, FL380, FL400
N636-P628 SERKA FL280, FL300
1.2.2 Flights that plan to enter Kabul FIR without an ATFM slot allocation – CTOT, CTO at
Kabul FIR entry waypoint, allocated flight level, and allocated ATS route – will be
accommodated only after flights with slots have been processed. Such flights should
expect delayed pushback and start clearances, non-preferred routes and/or flight
levels, enroute holding and/or diversion around Kabul FIR.
1.2.3 In order to ensure availability of slots for westbound departures from designated
airports in northern India and Pakistan, departures from these airports are given
priority for FL280 in the slot allocation. This does not preclude these flights from
requesting higher flight levels with initial slot request
1.3.1 The following flights are exempted from the BOBCAT ATFM procedures:
Flights experiencing an emergency, including aircraft subjected to unlawful
interference;
Flights on search and rescue or firefighting missions;
Urgent medical evacuation flights or humanitarian flights specifically declared
by State medical authorities that flight delays would put the life of patients
aboard at risk; and
Flights with “Head of State” status.
Note: After medical flights have completed their mission, they should be subject to
ATFM measures. Scheduled passenger transfer flights are, by their nature,
non-urgent and should not be given priority under the normal operational
situation.
1.3.2 Flights exempted from ATFM procedure shall indicate the exemption in their flight
plan (Field 18 – ATFM EXMP)
1.3.3 AIS Centers, Aerodrome Aeronautical Information Services Units or Base Operations
shall forward the flight plan information to the Bangkok ATFMU at AFTN address
VTBBZDZX
1.4.1 Affected flights shall obtain the mandatory Kabul FIR slot allocation – CTOT, CTO at
Kabul FIR entry waypoint, and allocated flight level and ATS route – from the
BOBCAT system. The Kabul FIR slot allocation will enable ANSPs to tactically
control westbound flights transiting the Kabul FIR at specified times by assigning
minimum spacing requirements at established gateway waypoints in the vicinity of the
eastern boundary of the Kabul FIR.
1.4.2 The application, calculation, and distribution of CTOT and associated Kabul FIR entry
waypoint slot allocations will be managed via internet access to the BOBCAT system
in accordance with the BOBCAT ATFM operation procedure in section 1.5
1.5.1 All affected flights are required to submit slot requests to the BOBCAT system by
logging into https://www.bobcat.aero between 0001 and 1200 UTC on the day of flight
and completing the electronic templates provided.
1.5.2 Affected operators who do not have dedicated BOBCAT username / password access
should complete the attached application form in Appendix A and fax the form to the
ATFMU as soon as possible.
1.5.4.1 The slot allocation is divided into 3 phases, namely; the slot request submission, initial
slot allocation, and slot distribution to aircraft operators and ANSPs.
1.5.5.1 Slot requests including preferred ATS route, flight level, and Maximum Acceptable
Delay (MAD) should be lodged between 0001 UTC and 1200 UTC on the day of the
flight. Slot requests may subsequently be amended prior to the cut-off time of
1200UTC. Aircraft operators are encouraged to submit additional slot request options
in case their first choice is not available. This may include variations to ATS route,
flight level, and MAD.
1.5.5.2 Slot requests shall be for flight parameters that can be met by the flight. For example,
flights requesting a slot at FL390 must be able to transit Kabul FIR at FL390. Flight
subsequently unable to meet slot parameters (flight level, ATS route, or CTO at entry
waypoint) should expect non-preferred routes and/or flight levels, enroute holding
and/or diversion around Kabul FIR.
1.5.5.3 As BOBCAT will allocate FL280 on a priority basis to facilitate departures from
northern India and Pakistan underneath over-flying traffic, flights departing these
airports are encouraged to include FL280 as at least one slot request preference.
1.5.5.4 Flights that were not allocated a slot in the initial slot allocation are not satisfied with
the allocated slot or did not submit a slot request should select slots from the listing of
remaining unallocated slots available immediately after slot distribution has been
completed.
1.5.6.1 Slot allocation will commence at the cut-off time of 1200 UTC. BOBCAT will process
and generate the slot allocation based on the information submitted in the slot
requests. Notification of slot allocation will be made not later than 1230UTC via the
ATFMU website. Alternative arrangements for notification of slot distribution (e.g.
Fax, Telephone, and E-mail) should be coordinated with the ATFMU.
1.5.6.2 After the slot allocation has been published at https://www.bobcat.aero, aircraft
operators can:
(a) Use the slot allocation result for ATS flight planning purposes,
(b) Cancel the allocated slot and/or,
(c) Change slot allocation to another available slot in the published list of
unallocated slots.
1.5.6.3 ATS Units involved (e.g. Area Control Center, Aerodrome Control at the departure
airports, AIS Centers, Aerodrome Aeronautical Information Services Units and Base
Operations) can also view the slot allocation results at https://www.bobcat.aero
1.5.7.1 Once aircraft operators are in receipt of the slot allocation, they shall submit the ATS
flight plan using the time, ATS route and flight level parameters of the BOBCAT
allocated slot.
1.5.7.2 In addition to normal AFTN addresses, operators should also address flight plan
(FPL) and related ATS messages (e.g. DLA, CNL, CHG) to the ATFMU via AFTN
address VTBBZDZX for all flights that have submitted a slot request.
1.6.1 In accordance with ICAO PANS ATM provisions, it is the responsibility of the Pilot-in-
Command (PIC) and the aircraft operator to ensure that the aircraft is ready to taxi in
time to meet any required departure time. PIC shall be kept informed by their
operators of the CTOT, CTO at Kabul FIR entry waypoint, and flight parameters
(route, flight level) allocated by BOBCAT.
1.6.2 The PIC, in collaboration with ATC, shall arrange take-off as close as possible to
CTOT in order to meet the allocated CTO at Kabul FIR entry waypoint.
ANSPs
1.6.3 In accordance with ICAO PANS ATM provisions, flights with an ATFM slot allocation
should be given priority for take-off to facilitate compliance with CTOT.
1.6.4 CTOT shall be included as part of the initial ATC clearance. In collaboration with the
PIC, Aerodrome Control shall ensure that every opportunity and assistance is granted
to a flight to meet CTOT and allocated CTO at Kabul FIR entry waypoint.
1.7.1 Bangkok ATFMU (VTBBZDZX) shall be included in the list of AFTN addresses for
NOTAMs regarding any planned activities that may affect slot availability (e.g.
reservation of airspace / closure of airspace, non-availability of routes, etc.).
1.7.2 Bangkok ATFMU (VTBBZDZX) shall be included in the list of AFTN addresses for
ATS messages (e.g. FPL, DEP, DLA, CHG, CNL) relating to flights subject to ATFM
procedures.
1.7.3 Prior to departure and before obtaining an ATC Clearance, in circumstances where it
becomes obvious that the allocated Kabul FIR slot parameters will not be met, a new
slot allocation should be obtained as soon as possible. To avoid frequency
congestion, this should be obtained primarily via aircraft operators / flight dispatchers.
Ground Control or Clearance Delivery may be asked to assist in the coordination with
Bangkok ATFMU as an alternative. Early advice that the allocated Kabul FIR slot
parameters will be missed also enables the slots so vacated to be efficiently
reassigned to other flights.
1.7.4 The PIC shall include the CTOT in the initial ATC clearance request.
1.7.5 A missed slot results in a considerable increase in coordination workload for ATC/PIC
and should be avoided. To minimize coordination workload in obtaining a revised slot
allocation, if the flight is still at the gate and an ATC Clearance has been obtained,
PIC shall advice Ground Control of the missed slot and obtains new CTOT as
specified in A.7.3. If it becomes essential, the ATC Clearance may be canceled.
1.7.6 Prior to departure and after the aircraft has left the gate, in the event that the aircraft
is unable to meet the allocated Kabul FIR slot parameters when requested by the
PIC, Aerodrome Control shall assist the PIC in coordination with Bangkok ACC and
ATFMU for a revised slot allocation.
1.7.7 PIC shall adjust cruise flight to comply with slot parameters at the Kabul FIR entry
waypoint, requesting appropriate ATC clearances including speed variations in
accordance with published AIP requirements.
1.8 BOBCAT ATFM Operations for Departing Aircraft from Suvarnabhumi Airport
(VTBS)
1.8.1 To increase the effectiveness for departing aircraft from VTBS during the BOBCAT
ATFM period and to ensure priority departure in accordance with CTOT, the following
procedures are required for all BOBCAT ATFM-related flights:
(a) Before obtaining an ATC Clearance, ensure the flight is ready at least 25
minutes prior to the allocated CTOT (the additional 5-minute buffer to CTOT
should not be taken into account under this provision);
(b) Radio communication with Suvarnabhumi Ground Control shall be established
within 5 minutes of enroute ATC clearance being received;
(c) Flights that do not adhere to the procedures mentioned in (a) and (b) will be
considered not-ready and may result in the withdrawal of ATC Clearance as
well as CTOT;
(d) Notwithstanding the above, there may be some occasions where, due to the
location of the aircraft's parking bay, the aircraft could take less time to taxi
than the Standard Taxi Time (STT) used by the BOBCAT system. In these
cases, ATC may delay push-back and start-up procedures in order for the
aircraft to have a smooth transition to the holding point.
1.10.2 ANSPs and aircraft operators shall ensure that they are conversant with and able to
apply the relevant procedures described in the ATFM Users Handbook
1.11.1 In the event that an aircraft operator or ATS unit is unable to access the ATFMU
website, Bangkok ATFMU shall be contacted via the alternative means (telephone,
fax, AFTN) described in 1.12.
1.12.1 An ATFM system fault is defined as a significant occurrence affecting an ATS unit, an
aircraft operator or ATFMU resulting from the application of ATFM procedures.
1.12.2 Aircraft operators and ATS units involved in Bangkok FIR, experiencing an ATFM
system fault, should complete an ATFM System Fault Report Form from the ATFM
Users Handbook (see Appendix B) and forward it to the ATFMU at the address
indicated on the form. The ATFMU will analyze all reports, make
recommendations/suggestions as appropriate and provide feedback to the parties
concerned to enable remedial action.
1.13.1 Bangkok ATFMU is staffed 24 hours and may be contacted via the following:
2. PPR – General
2.1. The following Airfields require PPRs:
Bagram (OAIX)
Dwyer (OADY)
Herat (OAHR)
Jalalabad (OAJL)
Kabul (OAKB)
Kandahar (OAKN)
Mazar-e-Sharif (OAMS)
NOTE: Changes to PPR procedures may be specified in NOTAM.
2.2. For civilian ACFT an approved PPR (if required), in conjunction with ACAA approval
and the submission of a flight plan, constitutes authorization to enter the Kabul FIR
and fly to the requested airport.
2.3. PPR times are not ATC flow times. They are based on ground handling capability
only. Issuance of a PPR does not encompass any ACFT servicing, ground handling,
or other aircrew requirements, nor does it imply air traffic control separation, weather
conditions or threat assessment. A PPR is valid for ±30 minutes from scheduled time.
All flights shall have sufficient fuel and maintenance support to meet their scheduled
arrival and departure times and be prepared for minimum ground times. Aircrews
need to consider adequate fuel for potential ground/air delays due to unforeseen
events.
3. PPR Requests
3.1. Military and Civilian ACFT Supporting NATO. Obtain PPRs by submitting a
Movement Request Form (MRF) to the Resolute Support Strategic Flight
Coordination Center (RSFCC) via respective National Representative (NRs) or
National Airflow Authorities (NAAs). MRFs and instructions may be obtained from:
https://isfcc.ncia.nato.int/Pages/Documents.aspx and reference
http://acaa.gov.af/en/page/civil-aviation-authority/atm-aip---important-information
3.2. COALITION MILITARY USERS
Coalition military customers must contact their respective liaison officers (LNOs) at
the Combined Air Operation Center (CAOC). Coalition military customers for
countries that do not have an active LNO contact the Coalition Coordination Center
Air operation Cell at CENTCOM headquarters. For time critical information after hours
and on weekends, contact you respective CENTCOM LNO. Leave name number or
Email address and an Air Operation Officer will call back.
3.3. CCC Air Operation Contact
CENTCOM CAOC Air Mobility Division (AMD)
DSN: 318-436-4141
VOSIP: 308-436-3057
Unclassified email: mu_amdalctc130pln@afcent.af.mil
All ISAF users shall contact ISFCC, Eindhoven.
3.5. PPR Requests for Bagram: All operators using an AMC mission number and
managed by the USAF 618/TACC will receive their PPR in the course of flight
management via TACC dispatchers. All operators not using an AMC mission number
should refer to paragraph 3.1 above.
2.2. The phrases shown in the table above shall be used by the intercepting ACFT and
transmitted twice in the circumstances described in the preceding paragraph.
2.3. If any instructions received by radio from any source conflicts with those given by the
intercepting ACFT by visual signals and/or by radio, the intercepted ACFT shall
request immediate clarification while continuing to comply with the visual and/or radio
instructions given by the intercepting ACFT.
Note: The form may be used as a template for the text of a message to be
transmitted over the AFS network.
5. Reporting Procedures (including In-Flight Procedures)
5.1. The following are the procedures to be followed by a pilot who is or has been involved
in an incident:
a. During the flight, use the appropriate air/ground frequency for reporting an
incident of major significance, particularly if it involves other ACFT, to permit
the facts to be ascertained immediately. Inform air traffic control immediately
of intentions to file a report to facilitate a timely investigation.
b. As promptly as possible after landing, submit a completed Air Traffic Incident
Report Form for the following reasons:
(i) Confirming a report of an incident made initially via air/ground
frequency, or for making the initial report on such an incident if it had not
been possible to report it by radio.
(ii) For reporting an incident that did not require immediate notification at
the time of occurrence.
5.2. An initial report made by radio should contain the following information:
a. ACFT identification
b. Type of incident, e.g. AIRPROX
c. The incident details of sections A, F, I, J, K, L, M, N, and O in the form in
section 7 below.
d. The confirmatory report of an incident of major significance initially reported
by radio or the initial report on any other incident should be submitted to each
of the following:
a. ACAA: safety.board@acaa.gov.af
b. AFCENT Safety: afforsafety@afcent.af.mil
c. RS Safety: rshqnacafsobh@hq.isaf.nato.int
e. It is also recommended to mail or hand deliver a hard copy of the Incident
Report Form to:
a. Safety Department
b. Civil Aviation Authority
c. Ansari Watt, Kabul Afghanistan
f. To confirm receipt of the Incident Report Form, call the following POCs:
a. Majeed Keramat : +93(0) 775 641 566
b. Dr. Ahmad Amani : +93(0) 700 233 170
6. Purpose of Reporting and Handling of the Form
6.1. The purpose of the reporting of incidents and their investigation is to promote the
safety of ACFT. The degree of risk involved in an AIRPROX incident should be
determined in the incident investigation and classified as “risk of collision,” “safety not
assured,” “and no risk of collision” or “risk to be determined.”
6.2. The purpose of the form is to provide investigation authorities with as complete
information on an air traffic incident as possible and to enable them to report back,
with the least possible delay to the pilot or operator concerned, the result of the
investigation of the incident and, if appropriate, the remedial action taken.
D 123.350
15NM radius centered on ARP
Herat Herat Tower 126.450
Surface to 8 500ft AMSL
CTR 240.300
Herat
D 30NM radius centered on ARP
Herat 119.150
Herat From 1 000ft AGL up to, but not Approach 386.250
CTA including, FL160
D
6NM radius centered on ARP 120.600
Kabul Kabul Tower
Surface to 9 500ft AMSL 284.275
CTR
125.400
20NM arc centered on
342717N0690913E from
343919N0692834E clockwise to
C 344417N0685623E and a straight
132.5
Kabul line back to Kabul Arrival
Hamid Karzai 343919N0692834E 301.950
CTA
International / 1000ft AGL up to and including
Kabul FL180
See ENR Excludes Kabul Class D CTR.
2.1.2 for
diagram of Section 1:
Kabul/Bagram Arc 50NM radius centered on
CTA/TMA. 345622N0691547E from
343929N0701259E clockwise to
350023N0681506E then straight
E
lines to
Kabul 344417N0685623E to
CTA 343919N0692834E and back to
343929N0701259E
1 000ft AGL up to and including
FL180
Excludes Kabul Class C CTA, and
Class D CTR.
Section 2:
Arc of a circle 50NM radius
centered on the Kabul ARP from
343929N0701259E to
342115N0701116E. A line from
342115N0701116E to
334422N0692133E. Arc of a circle
50NM radius centered on the
Kabul ARP from
334422N0692133E to
345020N0681524E. An arc of a
circle 50NM centered on
345622N0691547E from
343929N0701259E to
345020N0681524E.
E
ABOVE FL180 up to and including
Kabul FL290
TMA Section2:
Arc of a circle 50NM radius
centered on the Kabul ARP from
343929N0701259E to
342115N0701116E.
A line from
342115N0701116E to
334422N0692133E.
Arc of a circle 50NM radius
centered on the Kabul ARP from
334422N0692133E to
345020N0681524E.
D to N362227E0664444 then
E
30NM radius circle centered on
Mazar-e
the ARP.
Sharif
FL160 up to and including FL200
TMA 2
N364500E0674949 -
E
N371305E0674713 -
Mazar-e N371656E0673004 -
Sharif N371209E0671745 -
2500AGL -FL200
Table 1 – Low Air Routes (Strike through text indicates route closure between points)
A455
(RNP 10) Caution:
MRA:
RAMSO
342548N 0702830E 118°/298° 20 RAMSO to IMTIL 25 000ft
39NM FL 290 A455 UNUSABLE UNTIL
IMTIL (FIR BDRY)
FL 160 FURTHER NOTICE
340559N 0710859E
Class E
V390 For continuation, see AIP Iran
(RNP 10)
V717
(RNP 10)
Cautions:
SIGSI
310530N 0615300E 008°/188° FL 290 20 MOCAs:
78NM
FL 160 SOTRI to NIPIR 14 000ft
FARAH
322200N 0620930E 002°/182°
MRAs:
37NM
V718
(RNP 10)
Caution MRAs:
SAKUX
341236N 0621318E 150°/330° 20 ALEXY to DILAM 25 000ft
30NM
GOSKI DILAM to VACUK 16 500ft
334539N 0622929E 150°/330°
29NM VACUK to SERKA Unknown
DAPVI
331937N 0624508E 150°/330°
9NM Caution: Approaching SERKA
FL 290
ALEXY from EMERO, R249E in the
331130N 0625000E 152°/332°
FL 160 Karachi FIR is very close to the
67NM
air route to the south. It is
DILAM
162°/342° recommended ACFT maintain
321030N 0632400E
91NM Class E Centerline into and out of SERKA
to avoid the restricted area.
VIGOD 165°/345°
312434N0633825E 43NM
VACUK DILAM-SERKA UNUSABLE
304244N 0635119E 111°/291°
71NM UNTIL FURTHER NOTICE
EMERO
109°/289°
ALKIB MRAs:
355940N 0695416E 152°/332° SURVI-RAMSO
59NM PINAX to OLDEX 21 100ft
SURVI
350606N 0702512E FL290 OLDEX to ALKIB 27 000ft
173°/353° FL170
40NM ALKIB to SURVI None
RAMSO
342548N0702830E Class E
SURVI to RAMSO 21 000ft
ALKIB-RAMSO UNUSABLE
UNTIL FURTHER NOTICE
SURVI-RAMSO UNUSABLE
UNTIL FURTHER NOTICE
L750
For continuation, see AIP
(RNP 10) Turkmenistan
MAL FL490
AMDAR (FIR BDRY) 148°/328° 20
371230N 0672036E 34NM
KHOLM
148°/328° Between 2000Z to 2359Z only
364300N 0674100E
76NM FL280-FL290 are available
DOSHI between SITAX and TAPIS due
353600N 0682630E 148°/328° converging FIR boundary traffic.
74NM
TAPIS FL 510 Caution:
343100N 0690900E 150°/330°
27NM Above FL 290 MRAs:
KODAD AMDAR to KHOLM 29 000ft;
340659N 0692406E 150°/330°
40NM KOLM to DOSHI 32 000ft;
Class A
BOXUD DOSHI to TAPIS 29 000ft
333132N 0694612E 149°/330°
TAPIS-SITAX 30 000ft
30NM
For continuation, see AIP
SITAX (FIR BDRY) Pakistan
330500N 0700259E
MAX FL490
EGPAN (FIR BDRY) 184°/004° 20
382500N 0704400E 80NM
NIPIR
370530N 0703000E 179°/359° Caution:
119NM
FL 510 MRA:
SURVI
350606N 0702512E 174°/354°
Above FL 290 EGPAN to SURVI 31 000ft
70NM
SURVI to LAJAK 25 000ft
LAJAK (FIR BDRY)
335559N 0702959E Class A EGPAN –SURVI UNUSABLE
UNTIL FURTHER NOTICE
For continuation, see AIP
Pakistan
V848
(RNP 10)
MAL FL490
PAMTU (FIR BDRY) 20
351006N 0610806E
SAKUX
313°/133° Between 2000Z - 2359Z FL280 -
341236N 0621318E
79NM FL290 only
BURTA
323730N 0642630E 307°/127°
146NM
PAROD FL 510
312900N 0655400E 310°/130°
101NM Above FL 290
SODAS
303938N 0660402E 348°/168°
50NM Class A
ELEKO
302005N 0660845E 346°/166°
20NM
SERKA (FIR BDRY) 347°/167°
295101N 0661501E 30NM For continuation, see AIP Iran
MALFL430
LEMOD (FIR BDRY) 125°/305° 20
361000N 0641730E 162NM
VUVEN
126°/306° Between 2000Z – 2359Z: FL280-
343230N 0665530E
54NM FL290 and FL310-FL430
NEVIV FL 510
335848N 0674700E 127°/307°
41NM Above FL 290 Caution:
PATOX
333254N 0682512E 128°/308° MRA:
25NM
MESRA Class A NEVIV to DOBAT 30 000ft
331639N 0684756E 126°/306°
40NM
DOBAT (FIR BDRY) For continuation, see AIP
325200N 0692600E Pakistan
P628
(RNP 10)
SAKUX
341236N 0621318E 127°/307° MAL FL490
146NM FL 510
PAROD –ASLUM only available
BURTA Above FL 290 2000Z to 2359Z
323730N 0642630E 130°/310°
101NM Caution:
3. VFR REPORTING POINTS. Aircrews shall use VFR Reporting Points to aid in
airspace deconfliction and aircrew situational awareness. Current VFR Reporting
Points by TAAC are listed in the Afghanistan AIP. These points are designed for
military and civilian use and will remain unclassified to increase the safety of flight for
all aircraft operating below the CA. The AC/PIC shall ensure reports are made on
CTAF within 6 nautical miles of the VFR Reporting Point. Aircraft should avoid direct
over-flight of these points and use them as a reference to avoid aircraft and various
ACMs. However, pilots should use caution as some points are choke points that may
require multiple calls or calls further from the actual VFR Reporting Point than 6nm.
Requests for changes to these points will be forwarded to the CJTF-3 CJ3
(FECC/AOC) Aviation for consideration.
provided by ATC. Otherwise, ATC will reroute or restrict nonparticipating IFR traffic. On-
participating VFR traffic may transit the area with due caution; the effect of the creation of the
MOA is to highlight to operators or pilots of ACFT that it is necessary for them to assess the
increased hazard of military operations in relation to their responsibility for the safety of their
ACFT.
2.3.2. Examples of activities conducted in MOAs include, but are not limited to air combat tactics, air
intercepts, aerobatics, formation training, and low−altitude tactics.
2.3.3. Pilots operating under VFR should exercise extreme caution while flying within a MOA when
military activity is being conducted. The activity status (active/inactive) of MOAs may
frequently change, therefore; pilots should contact the airspace authority within 30 miles of the
boundary to obtain accurate real-time information concerning the MOA status. Prior to
entering an active MOA, pilots should contact the controlling agency for traffic advisories
(VFR) or clearance (IFR).
2.3.4. MOAs are specified in the AIP ENR 5.1 and should be depicted on all relevant charts.
2.3.5. Subject to the conditions for IFR operations in Class G airspace, operators may flight plan
through the airspace but, given the requirement for separation of IFR for participating military
traffic, should expect to be offered re-routing in the event that separation cannot be achieved.
Note: The conditions stated above are designed to be an enduring definition of the
requirements of a MOA. The current security situation in AFG means that Class G airspace is
not available to IFR civil traffic and so the IFR elements of the conditions may be disregarded
until Class G airspace is normalized.
2.4. Danger Area. Airspace of defined dimensions within which activities dangerous to the ACFT
may exist at specified times. This term is used only when the potential danger to ACFT has
not led to the designation of the airspace as restricted or prohibited. The effect of the creation
of the danger area is to caution operators or pilots of ACFT that it is necessary for them to
assess the dangers in relation to their responsibility for the safety of their ACFT.
2.4.1. Danger areas will also be established for Aerostat operations (tethered balloons). For all
military ACFT, these areas are to be considered as Special Use Airspace, No Fly Area (SUA,
NOFLY).
2.4.2. Tethered balloons from GND to 1000 AGL radius is reduced to 0.1NM for military helicopter
operation only (Refer below diagram: Airspace for Tethered Balloons – Military Helicopter).
3. Designations
3.1. The type of area involved is indicated by the nationality letters OA (Afghanistan), followed by
the letter -P- for Prohibited, -R- for Restricted or -D- for Danger. A map detailing the location
of these areas can be found on page 4.2-1 and 4.2-2.
3.2. Danger/Restricted/Prohibited (DRP) amendments or a new request form is available at
http://acaa.gov.af/en/page/civil-aviation-authority/aip---important-information
PROHIBITED AREA Sequence Numbers: Prohibited Areas for Afghanistan Airspace start
from OAP200-299.
RESTRICTED AREA Sequence Numbers: Restricted Areas numbering series are OAR001-
099, OAR400-499, OAR600-699 & OAR900-999 for Afghanistan Airspace
DANGER AREA Sequence Numbers: Danger Areas for Afghanistan Airspace- numbering
starts from OAD101-199.
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR001 Activity: MILITARY SUA
3503N06721E - 3722N07120E Hours: By NOTAM, or ATC
3600N07104E - 3521N07111E Service: Nil
3409N07049E - 3412N06951E FL300 Remarks: Contact KACC for status and transit or
3403N06943E deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR002 Activity: MILITARY SUA
3403N 06943E - 3353N 06937E - Hours: By NOTAM, or ATC
3322N 07005E - 3310N 06920E - Service: Nil
3224N 06903E - 3200N06905E - FL300 Remarks: Contact KACC for status and transit
3154N 06843E - 3152N 06800E- or deconfliction instructions.
3122N06716E - 3143N06420E - Sponsor: CAOC, AFFOR A3A
3444N 06650E - 3503N06721E (e-mail: affora3aairspace@afcent.af.mil)
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR402 POLYGON, Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
3431N06940E, 3426N06949E, 3425N7040E,
3540N07040E, 3450N06940E Hours: By NOTAM
FL270 Service: Nil
FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR403 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
345000N06920E, 345000N070400E,
342500N070400E, 342600N0692000E Hours: By NOTAM
Service: Nil
FL270
Remarks: Contact KACC for status and transit
FL160 or deconfliction instructions.
Contact: KACC
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR404 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
343435N0703349E, 341558N0701145E,
342934N0695519E, 344731N0700155E Hours: By NOTAM
Service: Nil
15000 AMSL
Remarks: Contact KACC for status and transit
12 000 AMSL or deconfliction instructions.
Contact: KACC
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR406 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
344808N0693400E,
Hours: By NOTAM
344807N0701436E, Service: Nil
FL230
343309N0701435E Remarks: Contact KACC for status and transit
FL170 or deconfliction instructions.
343303N0693431E Contact: KACC
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR408 HERAT RANGE Activity: RTC FIRING RANGE
A circle radius 0.5NM centered on position Hours: H24
341254N 0621431E Service: HERAT APP / TWR
8300 AMSL Remarks: Contact Herat APP Control for status.
GND Transit or avoidance instructions. Do not enter
Unless in receipt of a positive instruction to do so.
However, TWR may not be aware of all users.
Aircrews are to approach location with utmost
Caution.
Sponsor: TAAC –WEST RS: 932-390-391-1160
OAR410 MAHOLIC RANGE Activity: MILITARY LIVE FIRING
313907N0654012E- 313954N0654055E Hours: H24
313936N0654147E-313909N0654155E 7700 MSL Service: Military only
GND Remarks: Military Live Firing Range.
313842N0654151E-313802N0654119E
Sponsor: Maholic Air Operations
313817N0654041E SVOIP 308-431-3933 TAAC-SOUTH
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR411 EAST RIVER RANGE Activity: MILITARY LIVE FIRING
345010N 0691656E – 345233N 0691625E – Hours: Unknown
345336N 0691628E – 345413N 0691812E – Service: BAGRAM APP / TWR
345413N 0692049E – 345311N 0692216E – Remarks: Contact BAGRAM APP / TWR for
344931N 0691822E – 345010N 0691656E
FL170 Status and transit or avoidance instructions.
GND Status also available on Bagram ATIS. Do not
enter unless in receipt of a positive instruction to
Do so.
Sponsor: BAGRAM DSN 318-481-1511
TAAC-EAST
OAR416 HERAT A-CAMP ZAFAR Activity: MILITARY FIRING RANGE
340835N 0621445E – 340850N 0621630E – Hours: 0600LT – 2200LT
340504N 0621835E – 340345N 0621435E – Service: HERAT APP / TWR
340835N 0621445E FL150
Remarks: Contact Herat APP Control for status.
GND
Transit or avoidance instructions. Do not enter
Unless in receipt of a positive instruction to do so.
Sponsor: TAAC-WEST RS: 932-390-391-1160
OAR420 CALM LAKE Activity: RANGE
343653N 0692318E – 343729N 0692338E – Hours: H24
343846N 0692623E – 343807N 0692809E – Service: Kabul Approach
343626N 0692820E – 343516N 0692527E – FL190 Remarks: Contact Kabul Approach Control for
343526N 0692436E – 343342N 0692115E –
343542N 0692100E – 343653N 0692318E GND Status, transit, or avoidance instructions. Do not
enter unless in receipt of a positive instruction to
Do so.
Sponsor: KMTC Mobile: +93 (0)70-797-0908
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR432 ROZ UAS LION Activity: Small Group UAS Operation
Hours: NOTAM /ATC
A circle 0.5N M radius centered on
position 343513N0691435E Service: Nil
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR608 E-NAN SEAL 02 POLYGON Activity: WING TEST
Hours: Via NOTAM or ATC
364630N 0665900E – 364630N 0670100E Service: Mazar Tower 126.125 or 135.35 VHF
363900N 0670100E – 363900N 0665900N 4000AMSL Remarks: Contact Mazar TWR for status and
GND
transit or avoidance instructions.
Sponsor: RS ASM DSN: 318-449-2221
TAAC-NORTH
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR902 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
315448N/06642’40E,3327’11”N/0683451E, FIRING
334704N/0685039E, Hours: Via NOTAM, or ATC
334439N/06907’43E, 334511N/0692234E, Service: Nil
334857N/0693706E,
335403N/0694751E, 335540N/0695101E, Remarks: Contact KACC for status and transit
335242N/0695507E, or deconfliction instructions.
334752N/0695720E, 334455N/0695855E, Sponsor: CAOC, AFFOR A3A
334351N/0700223E, (e-mail: affora3aairspace@afcent.af.mil)
334318N/0700533E, 334110N/0700939E,
333812N/0701114E,
333547N/0701152E, 333129N/0701036E,
332639N/0701521E,
332149N/0701927E, 331611N/0701540E,
331209N/0700649E,
331313N/0700436E,330856N/0700204E,
330735N/0695701E,
330614N/0695545E,330631N/0694907E,
330807N/0694810E,
330614N/0694404E,330614N/0693454E,
330140N/0693028E,
FL290
325425N/0693028E,325216N/0693144E,
325056N/0692834E, FL160
324815N/0692622E,324654N/0692350E,
324429N/0692447E,
324011N/0692719E,323505N/0692312E,
323152N/0691712E,
322750N/0691421E,322155N/0691615E,
320830N/0691556E,
320548N/0691731E,315640N/0691944E,
315014N/0691131E,
313752N/0690143E,313913N/0685755E,
313616N/0685446E,
313648N/0684845E,314001N/0684652E,
314122N/0684323E,
314612N/0684207E,314644N/0683801E,
314941N/0683451E,
314556N/0682638E,314524N/0681650E,
314749N/0681535E,
314925N/0680953E,314154N/0680315E,
313808N/0675618E,
313704N/0675037E,313838N/0673755E,
313838N/0671632E,
313910N/0664916E.
OAR903 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
303904N/0655110E, 294904N/0660245E,
293316N/0650341E, 293440N/0645439E, Hours: Via NOTAM, or ATC
304052N/0653744E. FL160-FL260 Service: Nil
GND-14000 AMSL Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR904A POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
301405N/0645046E, 302207N/0633326E,
305934N/0650441E, 305010N/0651517E, Hours: Via NOTAM, or ATC
301405N/0645046E, FL160-FL260 Service: Nil
GND- 14000 AMSL Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR904B POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
301405N/0645046E, 293422N/0642531E, FIRING
293025N/0641207E, 292811N/0640910E, Hours: Via NOTAM, or ATC
292446N/0640419E, 292958N/0633503E, FL160-FL260 Service: Nil
292358N/0622840E, 293658N/0614630E, GND-14000 AMSL Remarks: Contact KACC for status and transit
or deconfliction instructions.
302207N/0633326E, 301405N/0645046E,
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR905 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
301029N/0620536E, 320142N/0633253E,
322430N/0642322E, 315606N/0645817E, Hours: Via NOTAM, or ATC
314542N/0645334E, 313518N/0645141E, FL290 Service: Nil
312542N/0645141E, 311853N/0645306E FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR906 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
323448N/0644734E, 330857N/0660933E,
322004N/0655550E, 322033N/0655112E, Hours: Via NOTAM, or ATC
322009N/0654703E, 321955N/0654435E, Service: Nil
321935N/0654134E, 321921N/0653912E, FL160-FL290
Remarks: Contact KACC for status and transit
321907N/0653644E, 321823N/0653326E, GND-14000 AMSL or deconfliction instructions.
321702N/0652927E, 321559N/0652711E,
321507N/0652404E, 321414N/0652142E, Sponsor: CAOC, AFFOR A3A
321316N/0652011E, 321209N/0651829E, (e-mail: affora3aairspace@afcent.af.mil)
321107N/0651653E.
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR909 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
345943N/0671558E, 344232N/0680432E,
344320N/0671142E Hours: Via NOTAM, or ATC
FL290 Service: Nil
FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR910 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
361633N/0674352E, 352129N/0682116E,
351237N/0681720E, 350208N/0681403E, Hours: Via NOTAM, or ATC
352024N/0672311E FL290 Service: Nil
FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR911 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
362926N/0685313E, 355712N/0682734E,
363135N/0680334E. Hours: Via NOTAM, or ATC
FL160-FL290 Service: Nil
GND-14000 AMSL Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR912 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
362701N/0692209E, 355849N/0693954E,
354507N/0693339E, 354700N/0691911E, Hours: Via NOTAM, or ATC
354611N/0690106E, 354033N/0684500E FL290 Service: Nil
FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR913 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
362436N/0695303E, 364814N/0700533E,
364147N/0694133E Hours: Via NOTAM, or ATC
FL290 Service: Nil
FL160 Remarks: Contact KACC for status and transit
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR914 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
370059N/0692947E, 371348N/0701650E,
380332N/0702523E, 375602N/0701025E, Hours: Via NOTAM, or ATC
374938N/0701546E, 373928N/0701618E, FL290 Service: Nil
373231N/0700640E, 373407N/0695807E, FL160 Remarks: Contact KACC for status and transit
373752N/0695455E, 373544N/0694341E, or deconfliction instructions.
373544N/0693123E, 372638N/0692426E,
371140N/0692250E. Sponsor: , CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR915 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
371345N/0673518E, 371120N/0674708E,
370453N/0674708E, 370156N/0675343E, Hours: Via NOTAM, or ATC
365602N/0680116E, 370124N/0681227E, FL290 Service: Nil
365947N/0681544E, 370614N/0681723E, Remarks: Contact KACC for status and transit
FL160
370558N/0682437E, 371209N/0683845E, or deconfliction instructions.
371659N/0684559E, 371450N/0684936E,
365409N/0690344E, 365055N/0685253E, Sponsor: CAOC, AFFOR A3A
365320N/0674847E. (e-mail: affora3aairspace@afcent.af.mil)
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR920 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
325153N/0615618E, 320210N/0614849E,
312549N/0614152E, 313142N/0605441E, Hours: Via NOTAM, or ATC
320030N/0605027E, 321542N/0605509E, Service: Nil
330705N/0603605E, 332324N/0604945E, Remarks: Contact KACC for status and transit
333407N/0605855E, 333431N/0604448E, or deconfliction instructions.
333607N/0604006E, 334207N/0603716E,
334455N/0603716E, 335255N/0603430E, Sponsor: CAOC, AFFOR A3A
340207N/0603524E, 340831N/0603524E, FL290 (e-mail: affora3aairspace@afcent.af.mil)
341207N/0604006E, 341543N/0604448E,
FL160
341631N/0605248E, 341631N/0605826E,
341943N/0605923E, 342255N/0605702E,
342519N/0605537E, 343007N/0605123E,
343119N/0605537E, 343519N/0605702E,
343943N/0610405E, 345255N/0610626E,
342607N/0613950E, 341655N/0613632E,
341119N/0613632E, 335631N/0614114E,
335007N/0614721E, 334631N/0615232E,
334407N/0620003E
Identification, Name and Lateral Limits Upper Limit (ft.) Remarks (time of activity, type of restriction,
Lower Limit (ft.) nature of hazard, risk of interception)
1 2 3
OAR926 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
354242N/0670412E, 362155N/0664012E,
362436N/0664944E, 362002N/0665658E, Hours: Via NOTAM, or ATC
361721N/0670610E, 361721N/0671701E FL290 Service: Nil
FL160 Remarks: Contact KACC for status and transit,
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
OAR927 POLYGON Activity: VARIOUS MILITARY INCLUDING LIVE
FIRING
294629N/0611647E, 295141N/0605855E,
304717N/0614942E, 310113N/0615306E, Hours: Via NOTAM, or ATC
310113N/0620451E, 314535N/0621429E, FL290 Service: Nil
320939N/0622126E, 324424N/0622719E, FL160 Remarks: Contact KACC for status and transit
331628N/0623103E, 321142N/0630844E
or deconfliction instructions.
Sponsor: CAOC, AFFOR A3A
(e-mail: affora3aairspace@afcent.af.mil)
TAAC-CAPITAL
Activity: Tethered Balloon
OAD130 SIA SANG Hours: H24
A circle 0.12NM radius centered on position Service: Kabul Approach/Tower
343032N 0691234E 1500 AGL Remarks: A tethered aerostat is secured to this
GND
location and may drift up to 0.3NM from this point.
ACFT are to avoid overflight of aerostat or near
aerostat tethered path.
TH
Sponsor: 111 CORPS DSN: 318-449-0361
TAAC-CAPITAL
ENR 5.2 MILITARY EXERCISE AND TRAINING AREAS AND AIR DEFENCE
IDENTIFICATION ZONE
1. Military exercise and training areas are all enclosed within prohibited, restricted or
danger areas. These areas, including the times of activity and the relevant restrictions
placed upon non-participating traffic, are listed in ENR 5.1. NOTAMs may be used to
notify activation of such areas on a non-scheduled basis.
Bagram’s creek, and the pond has a chemical color and smells polluted. Near the
RWY of Kabul, Lapwings are observed at the end of March. After the first rains,
migrating waterfowl appear at Kabul. Tens of Curlews, Avocets, and small plovers
are present. In April, Cormorants are observed circling above Bagram’s RWY and
then heading for the river valley. In March, White-tailed Lapwings are present in the
vicinity of Bagram. Gulls, ducks, and other waterfowl appear in Bagram and Kabul
during rainfall in Sept - Oct and March- April (autumn and spring migration
season).10’s of Great Black-headed gulls appear at Kabul during snowfall in
February. At Bagram, thousands of Demoiselle cranes have been observed in the last
years passing by enroute to their northern breeding grounds in March and April.
These flights coincide with ACFT flight paths. As with the geese at Mazar-e-Sharif,
data about the numbers of cranes, arrival, and departure dates, time of day passing
by, the height of flight, etc. have never been recorded. Therefore, it is not known
whether the Demoiselle cranes use the Ghorban valley as a stopover site, or that they
continue their flight without stopping. In other years, some Demoiselle cranes were
even spotted in airfield itself.
4.1.3. Birds of prey. Most birds of prey (raptors) hunt for living animals while a few birds,
like vultures, rely on carrion (dead animals and animal parts found in the garbage). A
few species, like kites, feed on a mix of carrion and animals captured alive. Of all
raptors, vultures are most hazardous to ACFT because of their weight and the many
hours spent soaring in the air looking for carrion. According to the bird guide (Birds of
South Asia), a few vulture species are inhabitants of Afghanistan. Although huge
numbers of sheep and goat were grazing the steppes and semi-deserts, the number
per flock was small, and each flock was tended by a shepherd. It is expected that the
shepherds take away the animals before dying, leaving no food for vultures and kites.
At the airfields, carcasses of wild animals are rare and if present, they are eaten by
Jackals and foxes. Carrion can only be found in the burn pits at Kandahar, and
Bagram, being meat leftovers from the restaurants. The garbage at the other airfields
is transported to landfills outside the airfields. At Kandahar, the burn pits are not
visited by birds of prey. Only Bagram´s burn pit attracts raptors; Black-eared kites are
present at the burn pit early in the mornings. Black-eared Kites are observed soaring
at different places above the Ghorban river valley, adjacent to Bagram. Around dawn
and dusk, they soar up to 1 kilometer above the river valley, coinciding with the flight
paths of ACFT flying over the valley. According to Bagram´s personnel, the Black-
eared kites are, like the Demoiselle cranes, only present in the migration periods.
Other raptors that are observed at Bagram are (in single numbers) the Long-legged
buzzard, Kestrel, Osprey, and Short eared Owl. At Kandahar, few Raptors are
observed, i.e. the Pallid harrier and Kestrel. Steppe eagles are observed at Mazar-e-
Sharif and at Herat. Other raptors at Herat are the Kestrel and the Black kite. At Kabul
airport, in total 5 species of raptors are observed; Pallid Harrier, Kestrel, Steppe Eagle
and Black-eared Kites on migration. Besides the Black-eared Kites, all other birds of
prey are observed hunting for small animals.
4.1.4. Passerines, partridges, and pigeons. Since the vegetation of the airfields is not
being grazed by sheep and goats or being mowed (except Kabul) the vegetation at all
airfields is more natural, lush and dense than the vegetation in the vicinity. For this
reason, more seeds and insects are present at the airfields than in the vicinity, and
thus the airfields are more attractive to birds. At each airfield, House sparrows and
Tree sparrows are present. As observed at Kabul, these species reach high numbers
in spring and summer, finding abundant insects, that thrive in the lush vegetation, and
seeds produced by grasses and other plants. Furthermore, 10’s of Barn Swallows and
Crested Larks are present at each airfield, feeding on insects. The Crested lark finds
insects on the ground; the Barn swallow is catching insects in the air. At Bagram,
single Swifts and Alpine swifts are observed. These bird species are, like the Barn
swallow, foraging on flying insects. Bee-eaters also catch flying insects. The bee-