PBN Implementation Plan Nepal 2016 - v2.0
PBN Implementation Plan Nepal 2016 - v2.0
PBN Implementation Plan Nepal 2016 - v2.0
December 2016
Nepal
December 2016
Nepal PBN Implementation Plan
Amendments
Amendments and Corrigenda to this "PBN Implementation Plan" are issued by
Director General of CAA, Nepal. The space below is provided to keep a record of
such amendments.
AMENDMENT CORRIGENDA
Table of Contents
Summary 1
1. Background 1
2. Objective 1
3. Aircraft Fleet 2
3.1. International Operation
3.2. Domestic Operation
4. Airspace and Air-route Structure 2
4.1. Airspace
4.2. Airspace Classes
4.3. FIR Sectorization
4.4. TMAs and CTRs
4.5. Route Structures
5. Communication Infrastructure 4
6. Navigation Infrastructure 5
6.1. Conventional NAV Aids
6.2. GNSS
7. Surveillance Infrastructure 6
8. Future Plan 6
8.1. ATS Route Plan
8.2. Communication Plan
8.3. Surveillance Plan
9. PBN Implementation in Nepal 8
9.1. New Development
9.2. Initiation towards implementing PBN
10. PBN Implementation Road Map 8
10.1. Short Term (2010-2012)
10.2. Middle Term (2013-2016)
10.3. Long Term (2017-2025)
11. Description of the Tangible Benefits 12
NEPAL
Summary
In December 2010, Nepal National PBN Task Force Main Committee for PBN
has reviewed the Nepal PBN Implementation Plan in accordance with the review
report of ICAO APAC Regional Office. This Plan aims to provide aviation
stakeholders with appropriate implementation guidance and timelines to allow
proper preparation for PBN implementations within Kathmandu Flight
Information Region (VNSM). This plan has been produced in line with
Resolution A 36/23 adopted by ICAO Assembly in its 36th Session held in
September 2007 and with the Asia/Pacific Regional PBN implementation Plan
developed by ICAO Asia/Pacific PBN Task Force.
1. BACKGROUND
At the 36th Session of ICAO Assembly, it has been resolved: “All the contracting States
should have a PBN implementation plan in place by 2009 to ensure a globally harmonized
and coordinated transition to PBN by 2016.” The specific requirements are as follows:
Each contracting State should implement the approach procedures with vertical guidance
(Baro-VNAV and/or augmented GNSS) for all instrument runways, either as the primary
approach or as a back-up for precision approaches, by 2016, and meet the intermediate
implementation milestones of 30% by 2010 and 70% by 2014.
By introducing PBN System and GNSS technology, CAAN wants to facilitate more efficient
use of airspace and more flexibility for procedure design which cooperatively result in
improved safety, capability, predictability, operational efficiency, fuel economy, and
environmental effects.
2. OBJECTIVE
• To provide the continuity to the development in the field of air navigation including the
GNSS-based procedures- a step for transitioning to PBN
3. AIRCRAFT FLEET
The Air traffic in Nepal has increased tremendously in the last 10 years. International air
traffic continues to record steady growth with more frequent services in many Indian cities
and in the Middle East. The number of international aircraft movement at Tribhuwan
International Airport (TIA), Kathmandu in 2010 was 23 % increase over that of 2009
whereas the aircraft movement compared between 2012 and 2013 indicates the increase was
about 1.3%. In the case of domestic services, the traffic movement in 2010 has increased by
4.9 % as compared to 2009 whereas the movement in 2013 compared to 2012 was decreased
by 2.5% because of introduction of bigger fleet.
3.1 International Operation
Tribhuvan International Airport is being served by 27 international airlines having air-links
with 24 destinations in 14 countries. The aircraft fleet comprises A333, A332, A330, A321,
A320, A319, A310, B777, B772, B757, B739, B738, B737, DH8 and ATR72/42. State
registered airlines in international operations include Nepal Airlines, Buddha Air and
Himalayan Airlines; the later airline has recently started international operations.
There are 2 TMAs (Kathmandu and Nepalgunj) and 8 CTRs (Nepalgunj, Bhairhawa,
Pokhara, Bharatpur, Simara, Kathmandu, Janakpur and Biratnagar) and 10 ATZs
(Nepalgunj, Surkhet, Bhairhawa, Pokhara, Bharatpur, Simara, Kathmandu, Janakpur,
Biratnagar and Chandragadi) within Kathmandu FIR.
- Hotline service has been provided in Simara, Biratnagar and Bhairahawa airports for
rapid ground to ground communication.
- HF coverage in whole FIR for ground to ground communication and can be used for air
to ground communication during contingency operation.
6. NAVIGATION INFRASTRUCTURE
NDB, VOR/DME and other ground radio navigation aids are developed in order to
overcome operational restrictions posed by early navigation that relied on pilot's eye. In
Nepal also conventional navigation that fly along the radio signals provided by ground
facilities has contributed for enhancing flights safety and accessibility in far and wide.
However, out of 17 NDBs in different parts of the country, 12 NDBs are already
decommissioned and remaining NDBs have been planned to be withdrawn in another 5
years.
6.2 GNSS
• WGS-84 Coordinates
CAA Nepal completed WGS-84 survey of the runway thresholds, critical positions of
runway and Navigation Aids of TIA and all domestic airports in operation in 1999 and
data have been published in the AIP Nepal.
Re-verification of WGS-84 data and survey of other essential points at Kathmandu &
Biratnagar Airports has been carried out in 2010.
• Transition to GNSS
To take early benefit of the satellite based navigation, GNSS based approach procedures
for TIA and 8 major domestic aerodromes were developed in 1999, some of them were
flight validated.
GNSS NPA procedures were reviewed and some GNSS/RNAV departure procedures
were developed based on PANS/OPS in 2005. Some of them were flight validated.
GNSS based approach and departure procedures were designed at about nine domestic
airports including Tribhuvan International Airport and some of them were flight
validated.
GPS with TSO C129 Standard has been mandated to be on-board the aircraft since 2001
on selected ATS routes within Kathmandu FIR for en-route purposely only.
7. SURVEILLANCE INFRASTRUCTURE
- PSR/SSR was installed and implemented in 1998 and a new MSSR has already been
installed in Kathmandu to be used for terminal operations.
- Installation of new MSSR has almost been completed and in near future, will be
operational for en-route operation.
- Outside radar coverage, surveillance based on Voice Position Reporting
8. FUTURE PLAN
8.1 ATS route plan
- Inside Kathmandu FIR, existing L626 route will be made straight from ONISA to
KTM, being regional navigational route, will be consulted with concerned
stakeholders.
- Himalaya 2 Route (Kathmandu – BBD – Guwahati – Imphal – Kunming): This route
will be pursued to be developed and materialized, and consultation will be done for
the extension of L626 to connect it with Himalayan 2 Route, and if possible, will be
continued up to Kunming.
• Newly installed MSSR at Kathmandu for Terminal and at Bhattedanda for en-route
will be fully implemented for operations.
• Study will be carried out for the possibility and application of ADS-B outside Radar
coverage area as well as backup for existing RADAR system.
As per the ICAO Assembly Resolutions and APANPIRG Resolution, CAA Nepal has
initiated various works towards PBN since 2009.
CAAN has formed a National PBN Task Force headed by Deputy Director General of
CAAN and members from various disciplines including airline pilots. The National PBN
Taskforce has been mandated to develop PBN implementation plan, continuously review it
as per the guidelines of ICAO Regional PBN Implementation Plan and Global Plan.
PBN Focal Point has been nominated and tasked to coordinate ICAO and various stake-
holders, follow up the PBN Implementations Program, regularly update about the progress to
PBN National Taskforce.
In order to strengthen PBN procedure design and PBN operational approval capabilities,
CAAN has sent its employees to participate in the Procedure Design (including PBN)
Training and PBN Operational Approval Training respectively.
RNP AR APCH and the associated STARS have been successfully implemented in
Kathmandu (VNKT) with the continuous support from Airbus' subsidiary Airbus ProSky,
previous QUOVADIS. RNAV (GNSS) APCH and associated STAR have been
implemented in one of the domestic airports Biratnagar (VNVT) with in-house capability.
CAAN has also planned to introduce RNAV SIDs/STARs and IAPs in some major airports
including restructuring of entire route network primarily focusing on the development of
more direct RNAV routes.
10. PBN IMPLEMENTATION ROAD MAP
CAAN in coordination with AAI has promulgated ATS route L626 (RNP 10) since
November 2009 between Kathmandu and Delhi, and most of the international airlines
departing from Kathmandu towards West and Middle-east destinations are using this route.
CAAN has implemented Required Navigation Performance – Authorization Required (RNP-
AR) procedure for TIA with technical support from COSCAP and QUOVADIS, sister
organization of Airbus Company which came into effect by 28 June 2012.
Eight International Operators are successfully conducting RNP AR APCH at TIA in full-
fledged operations and some more are in pipeline.
Furthermore, CAAN has formulated the PBN Implementation Road Map as short term
(2010–2012), medium term (2013–2016) and long term (2017–2025) plan as shown in the
table below:
Civil Aviation Authority of Nepal Page 8
V2.0 (Dec 2016) Nepal PBN Implementation Plan
Short term • L626 (RNP 10) has been • RNP1 STAR has been • RNP AR APCH for TIA has
implemented for en-route implemented for RNAV been implemented since 28
(2010-2012)
operation. (GNSS) approach at June 2012.
Biratnagar Airport.
• RNP APCH for Biratnagar
• RNP1 STARs has been Airport has been implemented
implemented for RNP AR since 28 June 2012.
APCH at TIA.
Medium term • Existing domestic routes are • RNAV SIDs has been • RNP AR Missed APCH
planned to be redefined as designed for Dhangadi segment at Kathmandu has
(2013-2016)
RNAV 5 where applicable and (domestic airport) which will been modified and will be
new routes will be developed be implemented in the next implemented from 2 February
as necessary. Preliminary route phase. 2017.
design has been developed and
• New and updated RNAV • RNAV (GNSS) APCH has
will be implemented in the
STARs for RNP AR APCH at been designed for Dhangadi
next phase.
Kathmandu has been revised Airport and will be
and will be implemented from implemented in the next phase.
2 February 2017.
• RNAV STARs have been
developed for RNP APCH at
following domestic airports
and will be implemented in the
next phase:
• One at Biratnagar Airport
• Two at Dhangadi Airport
Long term • An extension of L626 will be • RNAV SIDs will be designed • Introduce RNAV APCH at all
proposed from Kathmandu to and implemented at major airports:
(2017-2025)
Kunming via Bagdogra- Kathmandu Airport (VNKT).
Guwahati- Imphal, India in - Chandragadi (VNCG),
• RNAV STARs/SIDs will be - Janakpur (VNJP),
order to materialize the
designed/implemented in all
proposed Himalayan 2 Route - Nepalgunj (VNNG),
other major airports.
and make it bidirectional. - Dhangadi (VNDH)
• RNAV 5 domestic routes will - Chandragadi (VNCG) - Bhairahawa (VNBW)
be implemented replacing the - Janakpur (VNJP) - Pokhara (VNPK) - if
existing routes. Some more - Nepalgunj (VNNG) feasible
routes will be designed and - Dhangadi (VNDH) - Other airports as necessary
implement to connect the - Bhairahawa (VNBW) • Feasibility study for RNP
major domestic airports.
- Pokhara (VNPK) - if Approach with BARO-VNAV
• Selective International ATS feasible will be done and introduced in
routes for regional navigation - Other airports as necessary. selective instrument runways.
i.e., B345, R344, G335, G336,
• Feasibility study will be
R325 and G348 will be
conducted for RNP AR APCH
redefined as RNAV 5 routes in
and if feasible, will be
consultation with the adjacent
implemented at some airports
FIRs.
critically located around
challenging terrain, if needed.
En-route
• An extension of L626 will be proposed from Kathmandu to Kunming via Bagdogra-
Guwahati- Imphal, India in order to materialize the proposed Himalayan 2 Route and
make it bidirectional.
• RNAV 5 domestic routes will be implemented replacing the existing routes. Some more
routes will be designed and implement to connect the major domestic airports.
• Selective International ATS routes for regional navigation i.e., B345, R344, G335, G336,
R325 and G348 will be redefined as RNAV 5 routes in consultation with the adjacent
FIRs.
• An extension of L626 will be proposed from Kathmandu to Kunming via Bagdogra-
Guwahati- Imphal, India in order to materialize the proposed Himalayan 2 Route and
make it bidirectional.
Terminal
• Priority will also be given to introduce RNAV SIDs in Tribhuvan International Airports
and some other major domestic airports of the country.
• RNAV SIDs will be designed and implemented at Kathmandu Airport (VNKT).
• RNAV STARs/SIDs will be designed/implemented in all other major airports.
- Chandragadi (VNCG)
- Janakpur (VNJP)
- Nepalgunj (VNNG)
- Dhangadi (VNDH)
- Bhairahawa (VNBW)
- Pokhara (VNPK) - if feasible
- Other airports as necessary.
Approach
• Introduce RNAV (GNSS) APCH at all major airports:
- Chandragadi (VNCG),
- Janakpur (VNJP),
- Nepalgunj (VNNG),
- Dhangadi (VNDH)
- Bhairahawa (VNBW)
- Pokhara (VNPK) - if feasible
- Other airports as necessary
• Feasibility study for RNP Approach with BARO-VNAV will be done and introduced in
selective instrument runways.
• Feasibility study will be conducted for RNP AR APCH and if feasible, will be
implemented at some airports critically located around challenging terrain, if needed.