Doc 9849

AN/457

Global Navigation
Satellite System
(GNSS) Manual
________________________________

Second Edition – June 2012

Notice to Users

This document is an unedited advance version of an ICAO publication as approved, in principle,

by the Secretary General, which is rendered available to the public for convenience. The final
edited version may still undergo alterations in the process of editing. Consequently, ICAO accepts
no responsibility or liability of any kind should the final text of this publication be at variance from
that appearing here.

Advanced edition (unedited)

 EXECUTIVE SUMMARY

The growth of aviation and the urgent need to reduce fuel consumption, emissions and delays demands
increased airspace and airport capacity as well as a focus on providing a preferred trajectory (route and
altitude) to each airspace user. This, in turn, dictates improvements to communications, navigation and
surveillance (CNS) services. Aircraft operators also require efficiency gains via approaches that offer the
lowest possible minima and the significant safety benefits of straight-in approaches and vertical guidance.

The draft fourth edition of the Global Air Navigation Plan (Doc 9750, GANP) presents a high level summary
of ICAO’s Aviation System Block Upgrade (ASBU) methodology. The ASBUs define operational objectives
that address four specific and interrelated aviation performance areas: greener airports; globally
interoperable systems and data; optimum capacity; and flexible flights and efficient flight paths. The draft
GANP and ASBUs recognize the Global Navigation Satellite System (GNSS) as a technical enabler
supporting improved services that meet these objectives. Roadmaps in the draft GANP outline timeframes
for the availability of GNSS elements, the implementation of related services and the rationalization of
conventional infrastructure.

GNSS supports positioning, navigation and timing (PNT) applications. GNSS is already the foundation of
Performance-Based Navigation (PBN), Automatic Dependent Surveillance – Broadcast (ADS-B) and
Automatic Dependent Surveillance – Contract (ADS-C), described below. GNSS also provides a common
time reference used to synchronize systems, avionics, communication networks and operations, and
supports a wide range of non-aviation applications.

The ICAO Charter on the Rights and Obligations of States Relating to GNSS Services highlights the
principles that shall apply in the implementation and operation of GNSS, including: the primacy of safety;
non-discriminatory access to GNSS services; State sovereignty; the obligation of provider States to ensure
reliability of services; and cooperation and mutual assistance in global planning.

The goal of this manual is to provide information about GNSS technology and operational applications to
assist State regulators and air navigation service (ANS) providers to complete the safety and business case
analyses needed to support implementation decisions and planning.

GNSS Implementation

The introduction of GNSS-based services was made possible by the operational implementation of two core
satellite constellations, the Global Positioning System (GPS) and the GLObal NAvigation Satellite System,
(GLONASS) provided, respectively, by the United States of America and the Russian Federation. GPS and
GLONASS signals are defined in Annex 10 Standards and Recommended Practices (SARPs).

In 1994, the United States offered GPS to support the needs of international civil aviation, and reaffirmed the
offer in 2007; the ICAO Council accepted both offers. In 1996, the Russian Federation offered GLONASS to
support the needs of international civil aviation; the ICAO Council accepted this offer. Both States are
upgrading their constellations and have committed to ICAO to take all necessary measures to maintain
service reliability. Europe and China are developing systems (Galileo and Beidou) that will be interoperable
with upgraded GPS and GLONASS. The availability of multiple constellations addresses certain technical
and institutional issues.

GPS was declared fully operational in 1993, and several States approved the use of GPS guidance for
Instrument Flight Rules (IFR) en route, terminal and non-precision approach (NPA) operations that same
year. In 2001 ICAO adopted SARPs supporting GNSS operations based on augmenting core satellite
constellation signals to meet safety and reliability requirements.
There are three augmentation systems defined in Annex 10: the Aircraft-Based Augmentation System
(ABAS); the Satellite-Based Augmentation System (SBAS); and the Ground-Based Augmentation System
(GBAS).

ABAS is an avionics implementation that processes GPS and/or GLONASS signals to deliver the accuracy
and integrity required to support en route, terminal and non-precision approach (NPA) operations.

SBAS uses a network of ground reference stations and provides signals from Geostationary Earth Orbit
(GEO) satellites to support operations from en route through to approaches with vertical guidance over a
large geographic area. SBAS approach operations do not require augmentation stations at the airports
served. The Wide Area Augmentation System (WAAS), an SBAS developed by the United States, has been
operational since 2003. It also provides service in Canada and Mexico. The Japanese Multi-functional
Transport Satellite (MTSAT) Satellite-based Augmentation System (MSAS) became operational in 2007.
The European Geostationary Navigation Overlay Service (EGNOS) became operational in early 2011. The
Indian GPS and GEO Augmented Navigation System (GAGAN) is expected to be operational in 2013. The
Russian System for Differential Correction and Monitoring (SDCM) is under development and is expected to
be operational in 2015. These systems have the potential to support seamless guidance where their service
areas overlap. As of 2012, almost 3,000 SBAS vertically guided approach procedures were implemented,
mostly in North America, some of which support Category I (CAT I) minima, currently provided by the
instrument landing system (ILS). Over 1,100 of these serve airports without ILS. For technical reasons
described in this manual, the current SBAS architecture cannot reliably support approaches with vertical
guidance in equatorial areas.

GBAS uses monitoring stations at airports to process signals from core constellations and broadcast
corrections and approach path data to support precision approach operations. As of 2012, approximately 40
GBAS stations around the world were supporting testing and CAT I operations with special approvals.
GBAS has the potential to support CAT II/III and some surface movement operations, as well as terminal
area navigation.

Performance-Based Navigation (PBN)

One key to increased airspace capacity is a transition to a total area navigation environment in which aircraft
maintain flight paths within defined corridors. GNSS-based PBN provides a seamless, harmonized and cost-
effective guidance from departure to vertically guided final approach that provides safety, efficiency and
capacity benefits. The PBN Manual (Doc 9613) describes implementation processes, and for each
navigation application, ANS provider considerations and a navigation specification describing performance,
functionality and associated operations. Navigation specifications include approval processes and
requirements for aircraft, aircrew knowledge and training. The PBN concept represents a shift from
technology-based to performance-based navigation, but for all except the least demanding applications,
GNSS is required. GNSS enables States to develop a PBN implementation plan in accordance with ICAO
Resolution A37/11.

Automatic Dependent Surveillance – Broadcast (ADS-B)

Improved surveillance performance is the key to reduced separation standards, increased airspace capacity
and the ability to support user-preferred trajectories. ADS-B is based on aircraft broadcasting GNSS
position, velocity and other on-board data. ADS-B ground stations, which are much less costly than radars,
receive and process aircraft ADS-B data for use on controller situation displays. Other suitably equipped
aircraft can also process and display these data to enhance aircrew situational awareness. Several States
have implemented ADS-B in areas where there is no radar coverage. This has allowed for a reduction in
separation from as much as eighty to five nautical miles, thus increasing airspace capacity and supporting
reductions in fuel consumption and emissions.

2
 Automatic Dependent Surveillance – Contract (ADS-C)

In oceanic and remote areas where it is not possible to install either radar or ADS-B ground stations, ADS-C
position reports are relayed via communications satellites to air traffic control (ATC). In this implementation,
ATC specifies when to provide position reports in a contract. A significant number of aircraft already use
ADS-C in designated oceanic and non-radar continental airspace, and this technology has also led to
reduced separation standards.

Safety Risk Management

GNSS SARPs and avionics standards were developed to meet recognized safety targets, so in most cases
no further analysis of technical risk is required. Procedure design standards in Procedures for Air
Navigation Services – Aircraft Operations (PANS-OPS – Doc 8168) have a similar safety foundation. Many
States have introduced GNSS-based services since GPS was declared fully operational in 1993. The
regulations and operational procedures developed by these States reflect a safety assessment that can be
used as a basis by other States when they are developing regulations, training programs, procedures and
implementation plans for their operational environment.

GNSS signals are vulnerable to intentional and unintentional interference and to certain natural phenomena.
States can manage this by controlling the use of spectrum and by having procedures in place and retaining
some conventional infrastructure to mitigate the impact on operations in the event of a temporary loss of
service. This manual discusses related issues and describes strategies for rationalizing networks of
conventional aids.

Business Case

The business case supporting an implementation decision considers the costs and benefits of the
operational implementation of a GNSS-based service. Several States have completed such analyses for the
implementation of ABAS, SBAS, GBAS, ADS-B and ADS-C operations. This manual describes the factors
that are normally considered. The implementation of en route, terminal and NPA operations relying on core
constellations has significant benefits in terms of reduced flying time and improved airport access. ANS
provider costs are low without the requirement to install ground aids and because approach procedure flight
checks are not required periodically and do not require aircraft with complex equipment.

ANS providers need to include aircraft operators in business case development to ensure that all benefit and
cost elements are validated and that investments are coordinated. The analysis needs to consider all GNSS-
based services to ensure that operators acquire avionics that meet their expectations. Experience has
shown that operators will invest in avionics if there are significant incremental benefits.

Implementation of GNSS-Based Services

GPS has provided safety and efficiency benefits to civil aviation since 1993, leading to widespread
acceptance of GNSS-based services by aircraft operators, State regulators and ANS providers. Many States
have started reorganizing airspace for increased efficiency based on PBN, ADS-B and ADS-C, and have
designed approaches that enhance safety and improve airport accessibility. The availability of multiple
constellations broadcasting on multiple frequencies will make GNSS more robust and will allow service
expansion with increased benefits after 2020 when systems and avionics are available. In the meantime,
ANS providers can work with aircraft operators to expand GNSS-based services and benefits while planning
next generation services.

When planning to implement GNSS-based operations, States are encouraged to refer to the GANP and
relevant ASBUs, to comply with ICAO provisions and to take advantage of the expertise and information
available at the ICAO planning and implementation regional groups (PIRGs).

3
 FOREWORD

The draft fourth edition of the Global Air Navigation Plan (Doc 9750, GANP) presents a high level
summary of ICAO’s Aviation System Block Upgrade (ASBU) methodology. ASBUs define operational
objectives that address goals of: greener airports; globally interoperable systems and data; optimum
capacity and flexible flights; and efficient flight paths. The Global Navigation Satellite System (GNSS) is
recognized within the ASBU system as a key element of the air navigation system that will deliver improved
services and meet these objectives.

The Standards and Recommended Practices (SARPs) for GNSS were introduced as part of
Amendment 76 to Annex 10 to the Convention on International Civil Aviation — Aeronautical
Telecommunications, Volume I (Radio Navigation Aids) in 2001. The guidance information and material in
Attachment D to Annex 10, Volume I provides extensive guidance on the technical aspects and the
application of GNSS SARPs. The Navigation Systems Panel (NSP) continues to develop new material for
publication in Annex 10 amendments.

The primary purpose of this manual is to provide information on the operational implementation
of GNSS to assist States to introduce GNSS-based services. The manual is therefore aimed at air
navigation service providers responsible for fielding and operating GNSS elements, and at regulatory
agencies responsible for approving the use of GNSS for flight operations. Additionally, it provides GNSS
information to aircraft operators and manufacturers.

This manual is to be used in conjunction with the relevant provisions in Annex 10, Volume I, and
with the Performance Based Navigation Manual (Doc 9613).

Comments on this manual would be appreciated from all parties involved in the development and
implementation of GNSS-based services. These comments should be addressed to:

The Secretary General

International Civil Aviation Organization
999 University Street
Montréal, Quebec H3C 5H7
Canada

4
 Table of Contents
EXECUTIVE SUMMARY.............................................................................................................................................. 1
FOREWORD .................................................................................................................................................................. 4
CHAPTER 1 ................................................................................................................................................................... 7
INTRODUCTION .......................................................................................................................................................... 7
1.1 GENERAL .................................................................................................................................................................................. 7
1.2 GNSS ELEMENTS ................................................................................................................................................................... 7
1.3 IMPLEMENTATION OF GNSS-BASED SERVICES ................................................................................................................ 8
1.4 OPERATIONAL APPLICATIONS OF GNSS ............................................................................................................................ 8
1.5 GNSS LIMITATIONS AND OTHER ISSUES ........................................................................................................................ 10
CHAPTER 2 ................................................................................................................................................................. 11
PERFORMANCE REQUIREMENTS ........................................................................................................................ 11
2.1 GENERAL ............................................................................................................................................................................... 11
2.2 REQUIREMENTS ................................................................................................................................................................... 11
CHAPTER 3 ................................................................................................................................................................. 14
EXISTING CORE SATELLITE CONSTELLATIONS ............................................................................................. 14
3.1 GENERAL ............................................................................................................................................................................... 14
3.2 GLOBAL POSITIONING SYSTEM (GPS) ............................................................................................................................. 14
3.3 GLOBAL NAVIGATION SATELLITE SYSTEM (GLONASS) ............................................................................................ 15
CHAPTER 4 ................................................................................................................................................................. 17
AUGMENTATION SYSTEMS ................................................................................................................................... 17
4.1 GENERAL ............................................................................................................................................................................... 17
4.2 AIRCRAFT-BASED AUGMENTATION SYSTEM (ABAS) .................................................................................................. 17
4.3 SATELLITE-BASED AUGMENTATION SYSTEM (SBAS) ................................................................................................. 18
4.4 GROUND-BASED AUGMENTATION SYSTEM (GBAS) .................................................................................................... 22
CHAPTER 5 ................................................................................................................................................................. 24
GNSS VULNERABILITY ............................................................................................................................................ 24
5.1 GENERAL ............................................................................................................................................................................... 24
5.2 UNINTENTIONAL INTERFERENCE ..................................................................................................................................... 24
5.3 INTENTIONAL INTERFERENCE AND SPOOFING ............................................................................................................... 25
5.4 SPECTRUM REGULATION .................................................................................................................................................... 26
5.5 EFFECTS OF THE IONOSPHERE AND SOLAR ACTIVITY ................................................................................................... 27
CHAPTER 6 ................................................................................................................................................................. 29
GNSS EVOLUTION ..................................................................................................................................................... 29
6.1 GENERAL ............................................................................................................................................................................... 29
6.2 MULTI-CONSTELLATION/MULTI-FREQUENCY GNSS .................................................................................................. 29
6.3 STANDARDS DEVELOPMENT.............................................................................................................................................. 30
6.4 INSTITUTIONAL ISSUES ....................................................................................................................................................... 30
6.5 CORE CONSTELLATION EVOLUTION ................................................................................................................................. 30
6.6 PLANNED NEW CORE CONSTELLATIONS......................................................................................................................... 31
6.7 ABAS EVOLUTION .............................................................................................................................................................. 33
6.8 SBAS EVOLUTION ............................................................................................................................................................... 33

5
 6.9 GBAS EVOLUTION............................................................................................................................................................... 33
CHAPTER 7 ................................................................................................................................................................. 34
IMPLEMENTATION OF GNSS-BASED SERVICES.............................................................................................. 34
7.1 GENERAL ............................................................................................................................................................................... 34
7.2 INTERNATIONAL IMPLEMENTATION PLANNING ............................................................................................................ 34
7.3 DEVELOPMENT OF A CONCEPT OF OPERATIONS (CONOPS) ...................................................................................... 35
7.4 BUSINESS CASE ANALYSIS.................................................................................................................................................. 37
7.5 SYSTEM SAFETY ASSESSMENT .......................................................................................................................................... 40
7.6 CERTIFICATION AND OPERATIONAL APPROVALS .......................................................................................................... 41
7.7 SYSTEM TESTING AND PROCEDURE VALIDATION.......................................................................................................... 43
7.8 MONITORING AND RECORDING OF GNSS INFORMATION ............................................................................................ 43
7.9 AIRSPACE PLANNING AND PROCEDURE DEVELOPMENT.............................................................................................. 45
7.10 AERONAUTICAL INFORMATION SERVICES .................................................................................................................... 46
7.11 GNSS SERVICE STATUS NOTIFICATION ........................................................................................................................ 47
7.12 ANOMALY REPORTING ..................................................................................................................................................... 50
7.13 GNSS VULNERABILITY: MITIGATING THE IMPACT ON OPERATIONS ...................................................................... 52
7.14 TRANSITION PLANNING ................................................................................................................................................... 53
7.15 PROGRAMMATIC AND SECURITY ISSUES ....................................................................................................................... 55
7.16 REALIZING GNSS POTENTIAL ........................................................................................................................................ 55
APPENDIX A - ACRONYMS ..................................................................................................................................... 56
APPENDIX B - REFERENCES .................................................................................................................................. 59
APPENDIX C - ROLES OF ANS PROVIDERS AND REGULATORS ................................................................. 62
APPENDIX D - GNSS SPECTRUM .......................................................................................................................... 65
APPENDIX E - NAVIGATION ROADMAP ............................................................................................................ 66
APPENDIX F - PBN ROADMAP .............................................................................................................................. 67

6
 Chapter 1
INTRODUCTION

1.1 General

1.1.1 The Global Navigation Satellite System (GNSS) is defined in Annex 10 as a worldwide position
and time determination system that includes one or more satellite constellations, aircraft receivers and
system integrity monitoring, augmented as necessary to support the required navigation performance for the
intended operation.

1.1.2 The draft fourth edition of the Global Air Navigation Plan (Doc 9750, GANP) recognizes GNSS as
a key element of the air navigation system that will deliver improved services and meet environmental,
efficiency and safety objectives.

1.1.3 The ICAO “Charter on the Rights and Obligations of States Relating to GNSS Services”
addresses institutional issues. The Charter highlights the principles that shall apply in the implementation
and operation of GNSS, including: the primacy of safety; non-discriminatory access to GNSS services; State
sovereignty; the obligation of provider States to ensure reliability of services; and cooperation and mutual
assistance in global planning.

1.1.4 States are ultimately responsible to ensure that new air navigation services meet established
safety standards. In some cases States pool resources to establish a regional safety oversight organization
(RSOO) to ensure a common approach to safety regulation, oversight and enforcement. References to
States in this manual also apply to RSOOs.

1.1.5 The content of this manual is aligned with several Assembly Resolutions as well as with the PBN
Manual (Doc 9613), Safety Oversight Manual (Doc 9734) and Safety Management Manual (Doc 9859).
Readers should be familiar with these and other relevant ICAO documents.

1.1.6 The navigation and PBN roadmaps in the GANP are reproduced in Appendices E and F. These
roadmaps, which will be updated with each GANP revision, outline the timeframes for the availability of
GNSS elements, the implementation of related services and the rationalization of conventional
infrastructure. These roadmaps provide States with planning outlines that are consistent with the ASBUs.

1.1.7 This manual provides information about GNSS technology and operations that will assist States
to oversee the safety of GNSS operations and complete the business case analyses needed to support
implementation decisions and planning.

1.2 GNSS Elements

1.2.1 The introduction of GNSS-based services was made possible by the operational implementation
of two core satellite constellations, GPS and GLONASS, provided, respectively, by the United States of
America and the Russian Federation. Both States are upgrading their constellations and have committed to
ICAO to maintain service levels. Europe and China are developing systems (Galileo and Beidou) that will be
interoperable with upgraded GPS and GLONASS. All systems that are offered to support international civil
aviation will be included in Annex 10. The frequencies used by existing and emerging core constellations are
depicted in Appendix D.

1.2.2 The existing core satellite constellations were not designed to meet civil aviation performance
requirements. Their signals require augmentation in the form of ABAS, SBAS or GBAS as prescribed in

7
Annex 10. There are also SARPs for the ground-based regional augmentation system (GRAS), but no State
plans to implement GRAS.

1.2.3 Annex 10 prescribes a six-year advance notice of any change in the SARPs that will require the
replacement or modification of GNSS equipment. A six-year notice is also required of a core constellation or
augmentation system provider who plans to terminate service.

1.3 Implementation Of GNSS-Based Services

1.3.1 Implementation of a GNSS-based service requires a State to complete, approve or accept safety
assessments that support the implementation of training, airspace, instrument and ATC procedures and the
fielding of related systems, in compliance with applicable regulations.

1.3.2 ANS providers and aircraft operators will also normally complete business case analyses to
support implementation of a GNSS-based service. Several States have completed such analyses for the
implementation of basic GNSS, SBAS, GBAS, ADS-B and ADS-C operations.

1.3.3 The transition to GNSS-based services represents a significant change for aviation, so it requires
new approaches to regulation, provision of services, airspace and procedures and operation of aircraft.

1.3.4 A successful transition requires a comprehensive orientation and training programme aimed at all
involved parties, including decision makers in aviation organizations. Staff in regulatory and ANS provider
organizations require training to better appreciate how they can contribute to the operational implementation
of GNSS-based services. Training should include: the basic theory of GNSS operations; GNSS capabilities
and limitations; avionics performance and integration; applicable regulations; and concepts of operation.
This manual addresses most of these requirements.

1.4 Operational Applications of GNSS

1.4.1 General

1.4.1.1 GNSS enables PBN and provides navigation guidance for all phases of flight, from en route
through to precision approach. By providing position information, GNSS enables ADS-B, ADS-C, moving
map displays, terrain awareness and warning systems (TAWS) and synthetic vision systems. Emergency
Locator Transmitters (ELTs) also use GNSS position data. GNSS also supports a wide variety of precision
timing applications. Many States already employ GNSS to deliver improved service to aircraft operators
where no conventional systems exist.

1.4.1.2 The first approvals to use GNSS came in 1993, supporting IFR en-route (domestic and oceanic),
terminal and NPA operations. These approvals were based on the use of GPS signals and certified GPS
avionics. The original approvals came with some operational restrictions but delivered significant benefits to
aircraft operators. Since 1993 GPS has gained widespread acceptance by States and aircraft operators.

1.4.1.3 GNSS provides accurate guidance in remote, oceanic and mountainous areas where it is too
costly or impossible to provide reliable and accurate conventional navigation aid guidance. GNSS can also
provide service where it is not possible to install conventional aids (e.g. approaches to runways on islands).

1.4.1.4 The availability of accurate GNSS-based guidance on arrival and departure supports efficient
noise abatement procedures. It allows greater flexibility in routings, where terrain is a restricting factor,
providing for efficient descent profiles and the possibility of lower climb gradients and higher payloads.

1.4.1.5 The availability of GNSS-based services will allow the phased decommissioning of some
conventional aids. This will result in savings for ANS providers and aircraft operators in the longer term.

8
Even in the early stages of GNSS implementation, States may be able to avoid the cost of replacing some of
these aids.

1.4.2 Performance-Based Navigation (PBN)

1.4.2.1 Meeting the goal of increased airspace capacity requires the transition to a total area navigation
environment based on aircraft maintaining flight paths within defined corridors while en route, in the terminal
area and on approach. The PBN Manual (Doc 9613) explains the PBN concept and defines aircraft area
navigation performance requirements in navigation specifications. These prescribe the accuracy, integrity,
availability, continuity and functionality needed to support a particular airspace concept. The PBN concept
represents a shift from technology-based to performance-based navigation, but for all except the least
demanding applications, GNSS is the key enabler.

1.4.2.2 ABAS and SBAS as defined in Annex 10 support the application of GNSS signals-in-space within
all the PBN specifications, ranging from oceanic en route to approach with vertical guidance. The standards
for ABAS and SBAS avionics are identified within each individual PBN specification. ABAS supports the
RNP APCH navigation specification to LNAV minima and when combined with barometric vertical guidance
(Baro VNAV), supports approaches with vertical guidance to LNAV/VNAV minima. SBAS supports RNP
APCH with vertical guidance to LPV minima, and localizer-like guidance to LP minima where vertical
guidance is not feasible due to obstacles or terrain. RNP APCH requires GNSS.

1.4.2.3 In States without SBAS service and where few aircraft are equipped with Baro VNAV, GNSS can
provide lateral guidance for straight-in approaches to the majority of runways now served by circling
procedures, which are associated with a higher accident rate. The GBAS positioning service defined in
Annex 10 may support some terminal area PBN in future, but GBAS is primarily designed to support CAT
I/II/III operations and it will not likely be used for PBN to the same extent as ABAS and SBAS. GBAS
approach is not considered a PBN operation.

1.4.2.4 GNSS enables compliance with ICAO Assembly Resolution A37/11, which requires States to “…
complete a PBN implementation plan as a matter of urgency to achieve:

1) implementation of RNAV and RNP operations (where required) for en route and terminal areas
according to established timelines and intermediate milestones;

2) implementation of approach procedures with vertical guidance (APV) (Baro VNAV and/or
augmented GNSS), including LNAV only minima, for all instrument runway ends, either as the
primary approach or as a backup for precision approaches by 2016 with intermediate milestones as
follows: 30 per cent by 2010 and 70 per cent by 2014; and

3) implementation of straight-in LNAV only procedures, as an exception to 2) above, for instrument

runways at aerodromes where there is no local altimeter setting available and where there are no
aircraft suitably equipped for APV operations with a maximum certificated take-off mass of 5,700 kg
or more.”

1.4.2.5 The availability of off-the-shelf ABAS and SBAS avionics brings PBN within the economic reach
of all aircraft operators. This allows States to design en-route and terminal airspace for maximum capacity
and to support aircraft operators’ requirements for preferred trajectories. PBN navigation specifications
enabled by GNSS allow aircraft to follow more efficient flight paths, even in areas well served by
conventional aids.

1.4.2.5 PBN navigation applications also require error-free navigation databases. States should therefore
apply procedures and systems to ensure the integrity of the data as they are processed for use in avionics.
As described in Chapter 7, commercial database suppliers process the data provided in State Aeronautical
Information Publications (AIP) for use in avionics.

9
1.4.3 Automatic Dependent Surveillance – Broadcast (ADS-B)

Improved surveillance performance is the key to reduced separation standards, increased airspace capacity
and the ability to support user-preferred trajectories. ADS-B is based on aircraft broadcasting GNSS
position, velocity and other on-board data. ADS-B ground stations, which are much less costly than radars,
provide ADS-B data for use on controller situation displays. Suitably equipped aircraft can also display these
data to enhance aircrew situational awareness. Several States have implemented ADS-B in areas where
there is no radar coverage. This has allowed for a reduction in separation from as much as eighty to five
nautical miles, thus increasing airspace capacity and supporting significant reductions in fuel burn and
emissions. Future concepts include using low Earth orbit (LEO) satellites to receive ADS-B position reports
from aircraft, thus making it possible to extend service to oceanic and remote airspace.

1.4.4 Automatic Dependent Surveillance – Contract (ADS-C)

In oceanic and remote areas where it is not possible to install surveillance ground stations, GNSS time-
stamped position reports are relayed via satellite to ATC. With ADS-C, ATC specifies in a contract when to
provide position reports – typically at significant points or at specified time intervals. Many aircraft already
use ADS-C in designated oceanic and non-radar continental airspace, making it possible to reduce
separation standards.

1.4.5 Aviation Systems using GNSS Time

GNSS provides precise time information that is used in many aviation systems to synchronize local clocks to
Coordinated Universal Time (UTC). Synchronized clocks may then be used to assign a globally valid and
comparable time stamp to events. Examples of current or future applications using GNSS time are: ADS-B
and ADS-C, 4D Navigation and trajectory synchronization, required time of arrival, multilateration and wide
area multilateration, multi-radar tracking systems, air ground data link, flight data processing and ground
communication networks.

1.5 GNSS Limitations And Other Issues

1.5.1 While GNSS offers significant benefits, the technology has some limitations that State regulators
and ANS providers must address when introducing GNSS-based services.

1.5.2 This manual explains the vulnerability of GNSS signals to intentional and unintentional sources of
interference and to certain ionospheric effects. It describes ways to reduce the likelihood that GNSS-based
services will be disrupted by effectively controlling the use of spectrum and by ensuring that these issues are
adequately addressed in avionics and augmentation system design. It describes how to mitigate the impact
on aircraft operations in the event of the temporary loss of GNSS signals.

1.5.3 GNSS can support straight in approaches with lower minima to many runways now served by
NDBs or VORs. Approach minima, however, also depend on the terrain, physical characteristics of the
aerodrome and on airport infrastructure such as lighting. States therefore have to consider the cost of
meeting aerodrome standards when planning for new GNSS-based approaches or approaches with lower
minima.

1.5.4 Realizing maximum benefits from GNSS-based services in en route and terminal airspace
requires virtually all aircraft to be equipped with GNSS avionics. Implementation decisions must take
account of aircraft operators’ plans to equip, which depend on cost savings that justify avionics and related
costs. ANS providers and aircraft operators must work together and coordinate investments in GNSS
technology.

10
 Chapter 2
PERFORMANCE REQUIREMENTS

2.1 General

2.1.1 PBN navigation specifications define the accuracy, integrity, availability, continuity and
functionality needed to support a particular airspace concept. Functional requirements include: displaying
position relative to desired track; display of distance, bearing and time to the active waypoint; database
requirements; and appropriate failure indications.

2.1.2 In the development of GNSS SARPs, total system requirements were used as a starting point for
deriving specific signal-in-space performance requirements. Degraded performance that would
simultaneously affect multiple aircraft was also considered.

2.1.3 Detailed design system performance requirements are outlined in Annex 10, Volume I, Chapter
3, Table 3.7.2.4-1. This chapter describes these criteria and their relationship to levels of service.

2.2 Requirements

2.2.1 Accuracy

2.2.1.1 GNSS position accuracy is defined as the difference between a computed and a true position.

2.2.1.2 Ground-based systems such as very high frequency (VHF) omnidirectional radio range (VOR)
and ILS have relatively time-invariant error characteristics. These characteristics can therefore be measured
during flight inspection and subsequently be monitored electronically to ensure signal accuracy. GNSS
errors, however, can change over a period of hours due to satellite movements and the effects of the
ionosphere. Augmentation systems are designed to monitor and compensate for these changes.

2.2.2 Integrity and Time-to-Alert

2.2.2.1 Integrity is a measure of the trust that can be placed in the correctness of the information
supplied by the total system. Integrity includes the ability of the system to alert the user when the system
should not be used for the intended operation. In the case of a conventional aid like ILS, signal accuracy can
be monitored at specific points. In contrast, GNSS integrity is based on avionics performing complex
calculations to ensure that the error in computed position will not exceed the maximum allowed for the
current operation.

2.2.2.2 The necessary level of integrity for each operation is established with respect to specific
horizontal/lateral, and, for approaches with vertical guidance, vertical alert limits (HAL/LAL and VAL).
Avionics continuously calculate corresponding protection levels (HPL/LPL and VPL). The terms HAL/HPL
are used with ABAS and SBAS, whereas the terms LAL/LPL are used with GBAS. Protection levels are
upper confidence bounds on position errors; alert limits define the maximum position error allowed for an
operation. When any protection level exceeds the corresponding alert limit, the avionics must provide an
alert and the aircrew must comply with prescribed procedures. ADS-B integrity, described in other standards
documents, is linked to GNSS alert limits.

2.2.2.3 Time to alert is part of the integrity requirement; it is the maximum amount of time allowed from
the onset of a failure condition to the annunciation in the aircraft.

11
2.2.2.4 The type of operation and the phase of flight dictate the maximum allowable horizontal/lateral
and vertical errors, associated alert limits and the maximum time to alert the aircrew. These values, which
are shown in Table 2-1 below, are taken from Annex 10 Table 3.7.2.4-1.

[Table 2-1] Signal-in-space performance requirements

Approach procedure
with vertical guidance
(APV)
Non-
Oceanic Continental precision Category I
Operation en-route en-route Terminal approach APV-I APV-II (CAT I)
Horizontal alert 7.4 km 3.7 km 1.85 km 556 m 40 m 40 m 40 m
limit (4 NM) (2 NM) (1 NM) (0.3 NM) (130 ft) (130 ft) (130 ft)
Vertical alert N/A N/A N/A N/A 50 m 20 m 35 to 10 m
limit (164 ft) (66 ft) (115 to 33
ft)
Time-to-alert 5 min 5 min 15 s 10 s 10 s 6s 6s

Note 1: For ABAS-based non-precision approach, LNAV minima are specified on charts. There is another
type of non-precision approach based on using SBAS to achieve localizer performance with a 40m HAL; LP
minima are charted in this case.

Note 2: APV implemented with SBAS has LPV minima specified on charts. These procedures can be based
on APV-I, APV-II or CAT I alert limits. The alert limits are linked to SBAS performance and are stored in the
avionics database. A State may design APV procedures with geographically varying alert limits (e.g. APV-I
close to the edge of coverage, CAT I elsewhere).

Note 3: The term APV also encompasses approaches using GNSS lateral guidance with Baro VNAV
providing the vertical; associated minima are charted as LNAV/VNAV. In this case the horizontal alert limit is
usually that for ABAS-based non-precision approach, and the vertical alert limit is not applicable, since there
is no technical way to establish Baro VNAV integrity. Approach procedure design accounts for Baro VNAV
technical performance, which is defined in the PBN Manual.

2.2.3 Continuity

2.2.3.1 Continuity is the capability of the system to perform its function without unscheduled interruptions
during the intended operation, expressed as a probability. For example, there should be a high probability
that guidance will remain available throughout an entire instrument approach procedure. In the case of
ABAS, continuity depends on the number of satellites in view. For SBAS and GBAS, continuity also depends
on redundancy of augmentation system components.

2.2.3.2 Continuity requirements are less stringent for low traffic density en-route airspace and more
stringent for areas with high traffic density and airspace complexity where a failure could affect a large
number of aircraft. Requirements are also more stringent for approach operations.

2.2.3.3 Where there is a high degree of reliance on GNSS for en route and terminal area navigation,
mitigation against loss of service may be achieved through the use of alternative navigation means or
through the use of radar and ATC intervention to ensure that separation is maintained. This is not an option
when ADS-B is the only surveillance source because GNSS provides ADS-B position.

2.2.3.4 For GNSS-based APV and CAT I approaches, missed approach is considered a normal operation,
since it occurs whenever an aircraft descends to the decision altitude for the approach and the aircrew is

12
unable to continue with visual reference. The continuity requirement for these operations applies to the
average risk (over time) of loss of service, normalized to a 15-second exposure time. The specific risk of
loss of continuity for a given approach could therefore exceed the average requirements without necessarily
affecting the safety of the service provided or the approach. A safety assessment performed for one system
led to the conclusion that, in the circumstances specified in the assessment, continuing to provide the
service was safer than withholding it. Predicted failures for which a Notice to Airmen (NOTAM) is distributed
are not to be considered in the continuity computation.

2.2.4 Availability

2.2.4.1 The availability of a service is the portion of time during which the system is simultaneously
delivering the required accuracy and integrity. In fact integrity always determines availability. Some
applications have specific continuity requirements that need to be met to consider the service available. The
movement of satellites relative to a coverage area complicates GNSS availability, as does the potential
delay associated with returning a failed satellite to service. The level of availability in a certain airspace at a
certain time should be determined through design, analysis and modelling, rather than through
measurement. Guidance material pertaining to reliability and availability is contained in Annex 10, Volume I,
Attachment F.

2.2.4.2 The availability specifications in Annex 10, Volume I, Chapter 3, Table 3.7.2.4-1 present a range
of values valid for all phases of flight. When setting availability specifications for specific airspace, States
should take into account traffic density, available conventional aids, radar surveillance coverage, potential
duration and geographical size of outages, as well as flight and ATC procedures.

13
 Chapter 3
EXISTING CORE SATELLITE CONSTELLATIONS

3.1 General

3.1.1 GPS and GLONASS satellites broadcast very precise timing signals and data messages that
include their orbital parameters (ephemeris data). If receiver clocks were perfectly synchronized with the
very accurate satellite clocks, a receiver could calculate its three dimensional position by knowing its range
from three satellites. In practice it calculates the “pseudoranges” to at least four satellites as well as their
positions at time of transmitting. By finding the pseudorange of the fourth satellite, the receiver is able to
calculate the clock offset. Accuracy is dependent on the precision of the range measurements and the
relative positions (geometry) of the satellites used. Geometry is ideal when satellites are widely spaced; it is
poor when they are grouped in one direction. Joint use of more than one constellation improves GNSS
performance.

3.2 Global Positioning System (GPS)

3.2.1 The United States Air Force operates GPS for the government of the United States. In 1994, the
United States offered the GPS standard positioning service (SPS) to support the needs of international civil
aviation, and reaffirmed the offer in 2007 as follows: "The US Government maintains its commitment to
provide GPS SPS signals on a continuous worldwide basis, free of direct user fees, enabling worldwide civil
space-based PNT services (to include GPS SPS augmentation), and to provide open, free access to
information necessary to develop and build equipment to use these services.“ The ICAO Council accepted
both offers. The United States has published a GPS performance standard that defines a minimum level of
service.

3.2.2 The nominal GPS space segment is comprised of 24 satellites in six orbital planes. The satellites
operate in near-circular orbits at an altitude of 20,200 km (10,900 NM) and an inclination angle of 55
degrees to the equatorial plane; each satellite completes an orbit in approximately 12 hours. The GPS
control segment has seventeen monitor stations and four ground antennas with uplink capabilities. The
monitor stations use GPS receivers to track all satellites in view and accumulate ranging data. The master
control station processes this information to determine satellite clock and orbit states and to update the
navigation message of each satellite. This updated information is transmitted to the satellites via the ground
antennas, which are also used for receiving and transmitting health and control information.

3.2.3 The navigation message is made up of three major components. The first contains the GPS date
and time, plus the satellite's status and an indication of its health. The second contains orbital information
called ephemeris data that allows the receiver to calculate the position of the satellite. The third, called the
almanac, provides the locations and PRN numbers of all the satellites, which allows the receiver to
determine which satellites are in view.

3.2.4 The GPS SPS, using a coarse acquisition (C/A) code on the L1 frequency (1575.42 MHz), is
designed to provide global users with accurate positioning. A precise positioning service (PPS), which uses
the Precise Code (P-code) on L2 (1227.6 MHz), provides a more accurate positioning capability, but is
encrypted to restrict its use to authorized agencies. GPS uses code division multiple access (CDMA),
meaning that all satellites broadcast on the same frequency and are differentiated by transmitting unique
pseudo-random noise (PRN) codes.

3.2.5 The GPS SPS performance standard defines the level of performance commitment to civilian
users. The Interface Specification IS-GPS 200 details the technical characteristics of the SPS L-band carrier
and the C/A code as well as the technical definition of requirements between the GPS constellation and SPS

14
receivers. The performance standard is conservative, in that it guarantees only 21 operational satellites.
GNSS-based service design must be based on the conservative guarantees, but this means that most of the
time availability of service will exceed design levels. At times the number of operational satellites has
exceeded 30. GPS has met existing performance standards continuously since 1993. Additional information
can be found on the United States Coast Guard’s Navigation Center website (www.navcen.uscg.gov).

3.2.6 GNSS-based services were introduced when GPS reached full operational capability in 1993,
and in 2012 GPS continued to support all such services. Moreover, the availability of the GPS performance
standard allowed manufacturers, regulators and ANS providers to proceed with the development of GPS
standards and systems.

3.2.7 The United States has developed the following Space-Based PNT Policy (see
http://www.pnt.gov) to guide its efforts in the further development of GPS and augmentation systems:

a) Provide GPS and augmentations free of direct user fees on a continuous, worldwide basis;

b) Provide open, free access to information needed to develop user equipment;

c) Improve performance of GPS and augmentations; and

d) Seek to ensure international systems are interoperable with civil GPS and augmentations or, at
a minimum, are compatible.

3.3 GLObal NAvigation Satellite System (GLONASS)

3.3.1 The Ministry of Defense of the Russian Federation operates GLONASS. The Federal Space
Agency of the Russian Federation is appointed to act as a coordinator of activities on maintenance and
development of the GLONASS system, civilian applications and relevant international cooperation. In 1996,
the Russian Federation offered GLONASS service to civil aviation as follows: "… to confirm, on behalf of the
government of the Russian Federation, the proposal made at the tenth Air Navigation conference
concerning the provision of a standard-accuracy GLONASS channel to the world aviation community for a
period of at least 15 years with no direct charges collected from users." The ICAO Council accepted the
offer.

3.3.2 The nominal GLONASS space segment consists of 24 operational satellites and several spares.
GLONASS satellites orbit at an altitude of 19,100 km (10,310 NM) with an orbital period of 11 hours and
15 minutes. Eight evenly spaced satellites are arranged in each of three orbital planes, inclined at
64.8 degrees to the equator and spaced 120 degrees apart. GLONASS provides three-dimensional position
and velocity determinations based upon the measurement of transit time and Doppler shift of radio
frequency (RF) signals transmitted by GLONASS satellites.

3.3.3 A navigation message transmitted from each satellite consists of satellite coordinates, velocity
and acceleration vector components, satellite health information and corrections to GLONASS system time.
GLONASS satellites broadcast navigation signals in the L1 frequency band (1559-1610 MHz) modulated by
code of standard accuracy (CSA) and containing the navigation data message. GLONASS is based upon a
frequency division multiple access (FDMA) concept: each satellite transmits carrier signals on a different
frequency. A GLONASS receiver separates the total incoming signal from all visible satellites by assigning
different frequencies to its tracking channels. The use of FDMA permits each GLONASS satellite to transmit
an identical CSA code.

3.3.4 The navigation data message provides information regarding the status of the transmitting
satellite along with information on the remainder of the satellite constellation. From a user’s perspective, the
primary elements of information in a GLONASS satellite transmission are the clock correction parameters

15
and the satellite position (ephemeris). GLONASS clock corrections provide data detailing the difference
between an individual satellite’s time and GLONASS system time, which is referenced to Coordinated
Universal Time (UTC).

3.3.5 Ephemeris information includes the three-dimensional Earth-centred Earth-fixed position, velocity
and acceleration for every half-hour epoch of each satellite. For a measurement time somewhere between
the half-hour epochs, a user interpolates the satellite’s coordinates using position, velocity and acceleration
from the half-hour marks before and after the measurement time.

3.3.6 The GLONASS control segment performs satellite monitoring and control functions, and
determines the navigation data to be modulated on the coded satellite navigation signals. The control
segment includes a master control station as well as monitoring and upload stations. The master control
station processes measurement data from each monitoring station and computes the navigation data that
upload stations broadcast to the satellites. Operation of the system requires precise synchronization of
satellite clocks with GLONASS system time. To accomplish such synchronization, the master control station
provides the clock correction parameters.

3.3.7 Additional information concerning GLONASS, including the GLONASS Interface Control
Document, is available on the website: http://www.glonass-ianc.rsa.ru/.

16
 Chapter 4

AUGMENTATION SYSTEMS

4.1 General

4.1.1 The existing core satellite constellations require augmentation by ABAS, SBAS or GBAS to meet
Annex 10 performance requirements for specific operations. GNSS avionics process signals from core
satellite constellations, and, where available, SBAS or GBAS signals, to meet these requirements. Avionics
standards documents are listed in Appendix B.

4.2 Aircraft-Based Augmentation System (ABAS)

4.2.1 ABAS is an avionics implementation that processes core constellation signals with information
available on board the aircraft. Many States have taken advantage of GPS/ABAS to improve service without
incurring any expenditure on infrastructure.

4.2.2 There are two general classes of integrity monitoring: receiver autonomous integrity monitoring
(RAIM), which uses GNSS information exclusively, and aircraft autonomous integrity monitoring (AAIM),
which also uses information from additional on-board sensors such as inertial reference systems (IRS).

4.2.3 ABAS provides integrity monitoring using redundant range measurements to support fault
detection (FD) or fault detection and exclusion (FDE). The goal of fault detection is to detect a potential
position error caused by a satellite exceeding tolerances. Upon detection, the navigation function is lost.
Avionics with FDE identify and exclude the faulty satellite, thereby allowing GNSS navigation to continue
without interruption, provided that sufficient healthy satellites with good geometry remain in view.

4.2.4 An essential element of ABAS is a Basic GNSS receiver that supports en-route, terminal and
NPA operations and provides, as a minimum, RAIM fault detection. To enhance the overall performance of
the aircraft navigation system, the GNSS receiver may be incorporated into an integrated navigation system
as a sensor.

4.2.5 A Basic GNSS receiver meets the requirements for a GPS receiver as outlined in Annex 10 and
the specifications of RTCA/DO-208 or EUROCAE ED-72A, as amended by United States Federal Aviation
Administration (FAA) TSO-C129c or European Aviation Safety Agency (EASA) ETSO-C129A (or
equivalent). These documents specify the minimum performance standards for en-route, terminal and NPA
operations. RAIM satisfies the PBN requirement for on board performance monitoring and alerting
prescribed in required navigation performance (RNP) navigation specifications. Combined GLONASS/GPS
airborne receivers are used in the Russian Federation.

4.2.6 In addition to RAIM fault detection, a Basic GNSS receiver must support turn anticipation and the
retrieval of approach procedures from a read-only electronic navigation database. Receiver design does not
allow for approaches with user-defined waypoints, and if the aircrew changes or deletes any waypoint that is
part of an approach, the receiver will not enter approach mode.

4.2.7 RAIM requires redundant satellite range measurements (at least 5 satellites with good geometry)
to detect a faulty signal and alert the aircrew; FDE requires 6. The availability of RAIM and FDE is slightly
lower for mid-latitude operations and slightly higher for equatorial and high latitude regions due to the nature
of core constellation orbits. The requirement for redundant signals means that navigation guidance with

17
integrity provided by RAIM may not be available 100 per cent of the time, so GPS/RAIM approvals usually
have operational restrictions.

4.2.8 A barometric altimeter may be used to provide an additional measurement that reduces by one
the number of satellites in view required for RAIM and FDE. Barometric aiding can also help to increase
availability when there are enough visible satellites, but their geometry is not adequate to support the
integrity function. Note that RAIM barometric aiding is different from the barometric vertical navigation (Baro
VNAV) function used to support approaches with vertical guidance to LNAV/VNAV minima.

4.2.9 The inputs to the RAIM and FDE algorithms are the standard deviation of the measurement
noise, the measurement geometry and the maximum allowable probabilities for a false alert and a missed
detection. The output from the algorithm is the HPL, which is the radius of a circle centred at the true aircraft
position that is guaranteed to contain the indicated horizontal position within the specified integrity
requirement. It should be noted that the value of HPL is normally significantly larger than any position error,
but its value is the key to position integrity.

4.2.10 A RAIM alert occurs when there is poor satellite geometry, causing HPL to exceed HAL. In this
case the the ability to detect a failed satellite is lost. The type of operation determines HAL, specifically, 2
NM for en route, 1 NM for terminal and 0.3 NM for the final approach segment of an NPA procedure. RAIM
availability is therefore highest for en route and lowest for NPA. The detection of a satellite fault by the RAIM
algorithm also triggers an alert, which results in the loss of GNSS navigation capability unless the receiver
has FDE capability.

4.2.11 Some States have approved the use of GPS as the only navigation service in domestic airspace
and in oceanic and remote areas. In these cases the avionics require FDE. Under such approvals,
commercial aircraft may be required to carry dual systems and, to ensure continuity, operators must perform
pre-flight predictions to make certain that there will be enough satellites in view to support service
throughout the planned flight.

4.2.12 Until 1 May 2000, the United States applied a feature called selective availability (SA) that
degraded GPS accuracy. The discontinuation of SA resulted in an immediate GPS accuracy improvement.
As discussed in 4.3.3, this also results in a higher availability of integrity for some receiver designs.

4.2.13 GNSS information can be integrated with non-GNSS information to enhance navigation
performance. An IRS or an area navigation system using multiple distance measuring equipment (DME)
inputs can be used to coast through short periods of poor satellite geometry or when the aircraft structure
shadows the GNSS antennas while manoeuvring. The combination of GNSS FD or FDE, along with the
short-term accuracy of IRS mitigates the effects of signal jamming or loss of service due to ionospheric
events. These airborne augmentations may be certified in accordance with United States FAA TSO-C115A.

4.3 Satellite-Based Augmentation System (SBAS)

4.3.1 SBAS System Architecture and Operation

4.3.1.1 An SBAS augments core satellite constellations by providing integrity and correction information;
some systems also provide additional ranging signals. SBAS reference stations, distributed over a large
area, monitor core constellation satellite signals and continuously provide data to master stations. Master
stations use these data to assess satellite signal validity and compute corrections to the broadcast
ephemeris and clock data for each satellite. SBAS master stations also estimate the ranging delay
introduced by the Earth’s ionosphere, and compute the corrections applicable at predetermined ionospheric
grid points. In addition to providing corrections, master stations assess parameters that bound the
uncertainty in the corrections. The User Differential Range Error (UDRE) for each satellite describes the
uncertainty in the clock and ephemeris corrections for that satellite. The Grid Ionospheric Vertical Error

18
(GIVE) for each ionospheric grid point describes the uncertainty in the ionospheric corrections around that
grid point.

4.3.1.2 Master stations generate SBAS messages that uplink stations transmit to GEO satellites.
Transponders on the GEO satellites rebroadcast the SBAS messages on the GPS L1 frequency using a
unique PRN code. A GEO satellite appears to be stationary over the equator at a specific longitude, so its
signals cover virtually a complete hemisphere except for polar areas.

4.3.1.3 SBAS can send a “DO NOT USE” message if it detects a faulty satellite or a “NOT MONITORED”
message if a satellite is not visible to any monitoring station. A satellite with a “DO NOT USE” message
cannot be used under any circumstances, while a satellite with a “NOT MONITORED” message can be used
in an ABAS RAIM/FDE mode.

4.3.1.4 Ionospheric corrections are key to providing the accuracy and integrity needed to support APV.
This requires a widespread network of reference stations to measure ionospheric delays. As an example,
WAAS uses 38 reference stations in Canada, Mexico and the United States to meet these requirements. As
described in Chapter 5, the ionosphere is very active in equatorial regions, making it very technically
challenging for the current generation of SBAS to provide vertically guided approaches in these regions.

4.3.1.5 The GNSS SARPs allow for three levels of SBAS capability that provide: core satellite status and
GEO ranging; clock and ephemeris corrections; and clock, ephemeris and ionospheric corrections. The first
two levels support PBN en route through NPA, while the third also supports APV.

4.3.2 SBAS Avionics

4.3.2.1 The term “SBAS receiver” designates the GNSS avionics that meet the minimum requirements
outlined in Annex 10 and the specifications of RTCA/DO-229D, as amended by FAA TSO-C145c or EASA
ETSO C145C for sensors that provide data to other on-board systems, or TSO-C146c or ETSO C146C for
stand-alone systems.

4.3.2.2 There are four classes of SBAS avionics that support different performance capabilities. Class I
equipment supports en-route, terminal and LNAV approach operations. Class II supports en route through
LNAV/VNAV approach operations. Class III and IV support en route, terminal and four approach minima
levels: LPV, LP, LNAV/VNAV and LNAV.

4.3.2.3 The SBAS receiver produces differentially corrected three-dimensional positions by applying the
broadcast ephemeris and clock corrections and by interpolating between grid points to calculate the
ionospheric correction along its line-of-sight to each satellite. This provides the position accuracy needed for
APV approaches.

4.3.2.4 The SBAS receiver combines UDRE and GIVE error estimates with estimates of the
uncertainties in its own pseudorange measurement accuracy and in its tropospheric delay model to compute
HPL and VPL. These values are continuously compared with the HAL, and for APV approaches, VAL.
When either alert limit is exceeded, the avionics alert the aircrew.

4.3.2.5 For approach operations, SBAS avionics are required to annunciate the highest level of service
supported by the combination of the SBAS signal integrity level and the receiver certification, using the
naming conventions on the minima lines of the approach procedure chart. SBAS avionics support flying the
complete RNAV procedure and also can operate in a vector to final mode.

4.3.2.6 SBAS avionics can also provide advisory vertical guidance when flying NDB and VOR
approaches and GNSS NPAs in areas where an SBAS supports this level of service, thus providing the
benefits of a stabilized descent. In this case the aircrew is responsible for complying with all minimum
altitudes specified on the approach chart.

19
4.3.2.7 The integrity of approach procedures with vertical guidance depends on the validity of the data
used to define the approach. For all approaches with vertical guidance, SBAS avionics use data from a final
approach segment (FAS) data block in the avionics database. FAS data are protected with high integrity
using a cyclic redundancy check, which employs a computational algorithm to validate the data, specifically
to detect any change in data values since they were originally defined.

4.3.2.8 SBAS avionics standards prescribe a significantly improved and more standardized pilot/avionics
interface compared with Basic GNSS avionics. This reduces aircrew workload and is particularly beneficial
during missed approaches and other high workload phases of flight.

4.3.2.9 In virtually every SBAS avionics installation the aircrew will load specific approaches from the
database by selecting airport, runway and approach. If, however, the avionics have a very basic pilot
interface, there is the option of selecting an approach by entering the SBAS approach channel number that
appears on each approach chart.

4.3.2.10 SBAS avionics are required to track the GEOs that are broadcasting corrections for current
position and must be capable of rapidly switching between the SBAS data from one to another GEO to
maximize continuity of function. Minimum avionics requirements permit the use of any SBAS service
provider as well as the mixing of information from more than one SBAS service provider for en-route,
terminal and LNAV approach procedures. For APV operations SBAS avionics must use only the SBAS
defined in the FAS data block. This feature provides a measure of control to ANS providers in areas where
augmentation signals from two or more SBASs could provide service.

4.3.2.11 Regardless of the availability of SBAS service in a State, SBAS avionics provide a considerable
increase in availability for en route through NPA compared with Basic GNSS receivers by taking advantage
of the fact that SA is discontinued, by including FDE functionality and by using GEO satellite ranging. This
allows States to remove operational restrictions required when using Basic GNSS receivers.

4.3.2.12 Most TSO-C129 avionics assume SA is present, and for these the average RAIM availability is
99.99 per cent for en-route and 99.7 per cent for NPA with a 24-satellite GPS constellation. FDE availability
ranges from 99.8 per cent for en-route to 89.5 per cent for NPA. For SBAS and DO-316/TSO C196 avionics
(which do not have SBAS functionality), the availability of RAIM is 100 per cent for en-route and 99.998 per
cent for NPA; FDE availability ranges from 99.92 per cent for en-route and 99.1 per cent for NPA operations.

4.3.3 SBAS Operations

4.3.3.1 In most cases, SBAS approaches increase airport usability via lower minima while providing the
safety benefits of vertical guidance. These improvements are affordable at most airports because an SBAS
approach does not require any SBAS infrastructure at the airport. Minima do, however, depend on the
physical environment (obstacles, runway and lighting). SBAS availability levels allow operators to take
advantage of SBAS instrument approach minima when designating an alternate airport.

4.3.3.2 There will be only one approach with LPV minima to a runway end, based on the level of service
that SBAS can support at an airport. The FAS data block defines the HAL and VAL for the associated
procedure, but these values are transparent to the aircrew, who will use the published LPV minima.
Approach charts that include SBAS procedures are entitled RNAV(GNSS) RWY NN, and can have up to
four minima lines: LPV (or LP), LNAV/VNAV, LNAV and Circling. Charts will have either LPV or LP minima
lines, not both. LP minima will appear only when it is not possible to design a procedure with vertical
guidance due to terrain or obstacles.

4.3.3.3 It was originally expected that 250 ft would be the lowest decision height (DH) supported by
SBAS. Experience with WAAS demonstrated that this assumption was conservative, and that a 35m VAL
would support a 200 ft DH (LPV-200), equivalent to ILS CAT I. The United States completed an analysis that
compared recorded WAAS vertical errors with ILS glideslope monitor limits. The ILS glideslope

20
displacement at a nominal 200 ft DH location can be as large as 17m and remain within monitor limits. On
the other hand, flight inspection tolerance at the 200 ft DH location is 12m. Based on more than 1.76 billion
observations with a VAL less than or equal to 35m, the maximum observed WAAS signal in space vertical
error was 8.9m. Similar containment was observed for EGNOS. An SBAS vertical error on approach results
in a vertical path that is parallel to the design path but that is biased high or low. A barometric altimeter that
is independent of SBAS defines the DH, however, so for a low bias the aircraft would reach the DH farther
from the runway than the nominal position. The analysis addressed a worst-case, extremely conservative
35m low vertical error and demonstrated that the aircraft would remain within CAT I ILS obstacle clearance
surfaces. Because of various assumptions in the analysis, Annex 10 requires other States to complete a
system-level safety assessment before proceeding with LPV-200 operations.

4.3.4 SBAS Coverage and Service Areas

4.3.4.1 GEO satellite footprints define the coverage area of an SBAS. Within this coverage area, States
can establish service areas where SBAS supports approved operations. Other States within the coverage
area could also establish service areas either by installing integrated reference/monitoring stations in
cooperation with the SBAS provider, or by approving the use of SBAS signals. The first option offers
improved performance and some degree of control. The second option lacks any degree of control, and
performance depends on the proximity of the host SBAS to the service area. In either case, a State that has
established an SBAS service area is responsible for designating the types of operations that can be
supported within that area, and assumes responsibility for the SBAS signals within that service area.

4.3.4.2 In a fully-implemented SBAS, ranging, satellite status and basic differential correction functions
are available throughout the entire GEO coverage area, and are technically adequate to support NPA by
providing monitoring and integrity data for core and SBAS satellites.

4.3.4.3 SBAS avionics standards ensure smooth and transparent operations when transitioning from one
SBAS service area to another or to an area where no SBAS provides service. In the latter case, the receiver
switches automatically to navigation using FDE. The receiver can also switch back to SBAS-based
navigation when such a switch is beneficial. This ensures a worldwide navigation capability for PBN en
route, terminal area and approach operations.

4.3.4.4 There will likely be deficits in availability of integrity for APV near the edge of an SBAS service
area. States should complete availability studies for airports in these areas, using simulation and in some
cases data collection techniques, and refrain from implementing approaches with LPV minima where
decreased availability would create operational problems.

4.3.4.5 The Wide Area Augmentation System (WAAS) developed by the United States has been
operational since 2003. In 2007 the United States committed to provide “… single frequency WAAS signals
on a non-discriminatory basis, free of direct user fees, throughout the area of coverage of WAAS satellites
within its prescribed service volume, and to provide open, free access to information necessary to develop
and build equipment to use these services." Under bilateral agreements, Canada and Mexico host WAAS
reference stations, thus supporting SBAS service in all three States. The Japanese MSAS became
operational in 2007. Europe’s EGNOS became operational in early 2011. The European Commission (EC)
has informed ICAO that the EGNOS Safety of Life (SoL) service is being offered to the international civil
aviation community free of direct user charges. India’s GAGAN is under development and is expected to be
operational in 2013. The above systems augment GPS but not GLONASS. The Russian SDCM is under
development and is expected to be operational in 2015; it is designed to provide GNSS users with
corrections and integrity for GPS and GLONASS. By adhering to Annex 10 standards, these systems have
the potential to support seamless service where their service areas overlap. EGNOS, GAGAN, SDCM and
WAAS are designed to support en route through APV; as of 2010, MSAS supports en route through NPA,
and Japan is considering the technical feasibility of supporting APV approaches.

4.3.4.6 Although the architectures of EGNOS, GAGAN, MSAS, SDCM and WAAS are different, they
broadcast the standard message format on the same frequency (GPS L1) and so are interoperable from the

21
aircraft perspective. When SBAS coverage areas overlap, it is possible for an SBAS operator to monitor and
broadcast integrity and correction messages for the GEO satellites of another SBAS, thus improving
availability by adding ranging sources. All SBAS operators are encouraged to implement this system
enhancement.

4.3.4.7 SBAS avionics will function within the coverage area of any SBAS. States or regions should
coordinate through ICAO to ensure that aircraft do not suffer operational restrictions where there are valid
SBAS signals. If a State does not approve the use of some or all SBAS signals for en-route through terminal
operations, pilots using SBAS avionics would have to deselect GNSS altogether, since receiver standards
do not encourage deselection of a particular SBAS for these operations. This would make GNSS operations
impossible and could raise significant safety concerns.

4.4 Ground-Based Augmentation System (GBAS)

4.4.1 GBAS System Architecture

4.4.1.1 A GBAS ground station is located at or near the airport served. The ground station monitors core
constellation signals and broadcasts locally relevant pseudorange corrections, integrity parameters and
approach definition data to aircraft in the terminal area via a VHF data broadcast (VDB) in the 108.025 –
117.975 MHz band. As defined in Annex 10, GBAS will support CAT I precision approach and the provision
of GBAS positioning service in the terminal area. A draft SARPs amendment for GBAS to support CAT II/III
approaches is completed and currently undergoing validation by States and industry. The GBAS service
level determines the complexity of a GBAS ground station.

4.4.1.2 GBAS precision approach service provides lateral and vertical deviation guidance for the final
approach segment. The optional GBAS positioning service supports two-dimensional PBN operations in
terminal areas. GBAS can optionally provide corrections for SBAS GEO ranging signals.

4.4.1.3 GBAS infrastructure includes antennas to receive the satellite signals and electronic equipment
that can be installed in any suitable airport building. Unlike ILS and the microwave landing system (MLS),
antenna location is relatively independent of the runway configuration, but requires the careful evaluation of
local sources of interference, signal blockage, airport protection area and multipath. Siting of the VDB
antenna should ensure that the coverage area is sufficient for the intended operations.
4.4.1.4 A single GBAS ground installation may provide guidance for up to 49 approaches within its VDB
coverage. Guidance on allocation of multiple approaches may be found in Annex 10, Volume I, Attachment
D, Section 7.
4.4.1.5 The GBAS VDB transmits with either horizontal or elliptical polarization (GBAS/H (standard) or
GBAS/E (recommendation)). The majority of aircraft will be equipped with a horizontally polarized VDB
receiving antenna, which can receive both GBAS/H and GBAS/E signals. Other aircraft, notably certain
military aircraft, will be equipped with a vertically polarized antenna and will be limited to using GBAS/E
equipment. GBAS service providers should indicate the type of VDB antenna polarization at each of their
facilities in the State AIP.
4.4.1.6 The broadcast final approach segment (FAS) data block defines the final approach path. The
FAS data block enables the computation of “ILS lookalike” deviation guidance. The FAS data block is
associated with a GBAS channel number in the range of 20,001 to 39,999 through a channel mapping
formula that also references the associated VDB frequency. Guidance on channel assignments can be
found in Annex 10, Volume I, Attachment D, Section 7.

4.4.1.7 Unlike ILS, GBAS can provide multiple approaches to the same runway end with a unique
channel number identifying each one. These multiple approaches may have different glide path angles
and/or may have displaced thresholds.

22
4.4.1.8 The GBAS datalink includes a provision for authentication of the signal provided by the GBAS
ground station. This capability is optional for CAT I but will be a requirement for CAT II/III.

4.4.2 GBAS Avionics and Operations

4.4.2.1 The term “GBAS receiver” designates the GNSS avionics that meet the minimum requirements
for a GBAS receiver as outlined in Annex 10 and the relevant State specifications, such as RTCA/DO-253A,
as amended by FAA TSO C-161a/162a.

4.4.2.2 Like ILS and MLS, the GBAS receiver provides lateral and vertical guidance relative to the
defined final approach course and glide path. The receiver employs a channeling scheme that selects the
VDB frequency and identifies the specific FAS data block that defines the approach. Each separate
procedure requires a different channel assignment. For a precision approach, the GBAS receiver only uses
satellites for which corrections are available.

4.4.2.3 GBAS avionics standards have been developed to mimic ILS to simplify the integration of GBAS
with existing avionics. Display scaling and deviation outputs are equivalent to ILS to reduce aircrew training
requirements. All avionics will provide final approach course and glide path guidance to all configurations of
ground stations.

4.4.2.4 When GBAS positioning service is available it will provide position, velocity and time data that
can be used as an input to an on-board navigator or as a source of position information for ADS-B.
If this service is not supported by a particular ground station or by the avionics, the receiver will provide
position, velocity and time in accordance with ABAS requirements to support PBN. (See Table 4-2)

4.4.2.5 The term GBAS landing system (GLS) is used in the charting of GBAS approaches, both for the
chart title (GLS RWY NN) and the GBAS minima line.

4.4.2.6 A more detailed description of GBAS and the performance levels supported by GBAS is provided
in Annex 10, Volume I, Attachment D, Section 7.

4.4.2.7 In line with ICAO SARPs and the strategy for the introduction and application of non-visual aids
to approach and landing, which permit a mix of systems providing precision approach service, industry has
developed the multi-mode receiver (MMR). This receiver may support precision approach operations based
on ILS, MLS, GBAS and possibly SBAS.

23
 Chapter 5
GNSS VULNERABILITY

5.1 General

5.1.1 GNSS signals from satellites are very weak at the receiver antenna, so are vulnerable to
interference. Services provided by conventional aids can also be disrupted by interference, but GNSS
typically serves more aircraft simultaneously and the interference may affect wide geographic areas. GNSS
signals are also susceptible to ionospheric effects.

5.1.2 GNSS receivers must meet specified performance requirements in the presence of levels of
interference defined in Annex 10 and used within International Telecommunication Union (ITU)
recommendations. Interference above defined levels may cause degradation or loss of service, but avionics
standards require that such interference shall not result in hazardously misleading information (HMI).

5.1.3 Current GNSS approvals use a single frequency band common to GPS, GLONASS and SBAS.
This makes it easier to intentionally jam GNSS signals and it also makes unintentional interference more
likely. The next generation GNSS will be based on multiple frequencies. This will reduce the likelihood of
unintentional interference and will make intentional interference more difficult. Enhanced services depending
upon the availability of multiple frequencies would, however, be degraded by interference with one
frequency.

5.1.4 GNSS provides precise time information to support the applications described in section 1.4.5.
The majority of these applications use GNSS in a non-critical manner; timing receivers are used with other
time distribution systems and do not have demanding absolute accuracy requirements. Systems can coast
for a considerable amount of time on internal quartz clocks before needing another GNSS time update. The
most notable exception is multilateration, which can have a critical dependence on GNSS time.

5.1.5 State regulators and ANS providers can take the measures described in this chapter to reduce
the likelihood that GNSS service will be lost. As discussed in Chapter 7, they can assess the residual risk
and develop strategies to reduce the impact on aircraft operations in the event of a service disruption.

5.2 Unintentional Interference

5.2.1 GPS and GLONASS have filings with the ITU to use spectrum allocated to the Radionavigation
Satellite Service (RNSS) in the 1,559 – 1,610 MHz and 1,164 – 1,215 MHz bands. The RNSS allocation in
these bands is shared with the Aeronautical Radionavigation Service (ARNS). There are also filings under
the RNSS allocation for SBAS GEOs operating in the 1,559 – 1,610 MHz band. The GBAS VDB, as well as
VDL-4, which are Aeronautical Mobile (R) Services (AMRS), use the 108.025 – 117.975 MHz band, shared
with ILS and VOR, which are ARNS. GPS, GLONASS and SBAS GEOs also have ITU filings in the 1,164-
1,215 MHz band, which is intended for future civil aviation applications. Galileo and Beidou also have ITU
filings in place.

5.2.2 There are a number of sources of potential interference to GNSS from both in-band and out-of-
band emitters, including mobile and fixed VHF communications, harmonics of television stations, certain
radars, mobile satellite communications and military systems. Of specific concern is the use of the 1,559 –
1,610 MHz band by point-to-point microwave links that are allowed by a number of States. The use of these
links is due to be phased out no later than 2015.

24
5.2.3 Effective spectrum management is the primary way to reduce the likelihood of unintentional and
intentional interference with GNSS signals. This comprises creating and enforcing regulations/laws that
control the use of spectrum and carefully assessing applications for new spectrum allocations.

5.2.4 Many reported instances of GNSS interference have been traced to on-board systems, including
VHF and satellite communications equipment and portable electronic devices. Such interference can be
prevented by proper installation of GNSS avionics (e.g. shielding, antenna separation and out-of-band
filtering), integration with other aircraft systems and restrictions on the use of portable electronic devices.

5.2.5 The additional GNSS signals in the band 1,164-1,215 MHz to be broadcast by second-generation
core satellites share the band with DME and Tactical Air Navigation system (TACAN). ITU rules require that
DME/TACAN must be protected from interference. Compatibility studies based on the current DME/TACAN
infrastructure concluded that the impact of interference on the processing of the new GNSS signals is
tolerable. The studies also concluded that a high density of DME/TACAN facilities operating in or near the
new GNSS band could result in interference with GNSS signals at high altitudes. States should assess
whether an increase of the DME/TACAN infrastructure is compatible with expanded use of GNSS and if
necessary reallocate DME assignments away from GNSS frequencies.

5.3 Intentional Interference and Spoofing

5.3.1 In an era when essentially all conventional navigation aids remain in service, and when all aircraft
are still equipped to use them, there is little motivation to deliberately interfere with GNSS-based aviation
services. As reliance on GNSS increases, however, the threat of intentional interference could increase.

5.3.2 GNSS is used in many applications: financial, security and tracking, transportation, agriculture,
communications, weather prediction, scientific research, etc. Threat analysis must consider the likelihood
that jamming directed at non-aviation users could affect aircraft operations. It should also consider the
mitigations put in place by non-aviation service providers. Of primary concern is the proliferation of personal
privacy jammers designed to defeat vehicle-tracking systems.

5.3.3 The likelihood of interference depends on such factors as population density and the motivation
of individuals or groups in an area to disrupt aviation and non-aviation services. The likelihood will be
virtually nonexistent in oceanic and sparsely settled areas and will be highest near major population centres.
Impact assessment must consider the type of airspace, traffic levels and the availability of independent
surveillance and communications services, and must address safety and economic effects. Mitigation will be
required when disruption is deemed to be possible and would have a significant impact.

5.3.4 As described in Chapter 7, retaining DME is recommended as part of a mitigation strategy in

the case of a GNSS outage. Although DME shares a frequency band with GNSS, the interference threshold
of DME is significantly higher than for GNSS, so interference in the common band would not likely affect
DME. Furthermore, it is unlikely that interference in this band would jam all DMEs inside an aircraft’s radio
horizon.

5.3.5 Spoofing is the broadcast of GNSS-like signals to cause avionics to calculate erroneous positions
and provide false guidance. It is considered that the spoofing of GNSS is less likely than the spoofing of
traditional aids because it is technically much more complex. To avoid immediate detection, spoofing
requires accurate target aircraft position information. It is very difficult to match the spoofing signal to the
dynamics of a target receiver and maintain sufficient signal strength to enable the receiver to remain locked
to the spoofing signal. If the avionics did remain locked to a spoofing signal, there are various ways that it
could be detected: integrated avionics could annunciate discrepancies between GNSS and IRS or DME-
DME positions; pilots could note deviations through normal monitoring of instruments and displays; and in a
radar environment, ATC could observe deviations. Moreover, all other aircraft in the area that locked to the
spoofing signal would appear to have the same position as the target aircraft. If an aircraft did deviate from

25
track, Ground Proximity Warning Systems (GPWS) and Aircraft Collision Avoidance Systems (ACAS) would
provide protection against collision with the ground and other aircraft.

5.3.6 Spoofing of the GBAS data broadcast is at least as difficult as spoofing conventional landing
aids. An authentication scheme has been developed that will make spoofing of GBAS virtually impossible.

5.3.7 States must evaluate and address the risk of intentional interference in their airspace. If States
determine that the risk is unacceptable in specific areas, they can adopt an effective mitigation strategy as
described in section 7.13.

5.4 Spectrum Regulation

5.4.1 States should prohibit all actions that lead to disruption of GNSS signals. They should develop
and enforce a strong regulatory framework governing the use of intentional in-band radiators, including
GNSS repeaters, pseudolites, spoofers and jammers. Particular regulatory care is also required to address
out-of-band radiators that are harmonically related to GNSS frequency bands, such as certain television
broadcast channels and other industrial applications.

5.4.2 GNSS repeaters and pseudolites are systems that transmit signals to supplement GNSS
coverage in buildings and other areas where normal GNSS signals cannot be readily received. Aeronautical
test equipment may also act as a GNSS signal generator. When such equipment does not operate in
accordance with specific conditions, it may interfere with GNSS avionics and ANS providers’ ground
equipment. In some cases these systems can cause GNSS receivers within range to calculate erroneous
positions. Such cases should be detectable because there would be effects such as sudden, readily evident
position shifts.

5.4.3 The use of GNSS repeaters and pseudolites is carefully regulated by some States, but many
others have no relevant regulations. To ensure that these systems do not disrupt GNSS-based services,
States must create a regulatory framework to ensure that they have a valid application and that their
operation is not harmful to existing primary GNSS users. ICAO Electronic Bulletin EB 2011/56 Interference
to Global Navigation Satellite System (GNSS) Signals provides more information and a list of documents
that States can use for guidance in developing regulations.

5.4.4 Cases of harmful interference have been traced to short range GNSS jammers used to avoid
vehicle fee collection or tracking. The mobile nature and short range of these jammers disrupts signals
intermittently, making it difficult to identify and locate the source. States should establish regulations that
forbid the use of jamming and spoofing devices and regulate their importation, exportation, manufacture,
sale, purchase, ownership and use. Some States prohibit all actions that lead to disruption of GNSS signals
and prescribe severe penalties for the purchase or use of jammers. States should develop the means to
detect interference sources in support of enforcement programs.

5.4.5 States should take more preventive measures to reduce the likelihood of GNSS disruption to
aviation by non-aviation users. This could involve implementing location privacy provisions that are accepted
by citizens. Conversely, the design of fee collecting or tracking applications should anticipate interference by
including additional sensor integration or other mechanisms to prevent simple jamming from achieving its
aim. In most cases this can be achieved by simple measures.

5.4.6 The ICAO Convention and ITU Regulations protect GNSS frequencies for aviation use. There is,
however, significant demand for electromagnetic spectrum for new applications, such as mobile phone and
broadband data services that may emit signals that are much stronger than GNSS signals at the receiver.
States must not allocate spectrum adjacent to GNSS bands to proposed systems if there is any possibility
that these systems will interfere with currently installed GNSS receivers. While future multi-constellation and
multi-frequency GNSS equipment for aviation will be designed to maximize interference robustness as far as
reasonably possible, it is important that new spectrum services do not neutralize these improvements.

26
 5.5 Effects of the Ionosphere and Solar Activity

5.5.1 The ionosphere is a region of the upper atmosphere that is partially ionized. GNSS signals are
delayed by a varying amount depending on the density of ionized particles, which itself depends on the
intensity of solar radiation and other solar energy bursts. One phenomenon is rapid and large ionospheric
delay changes resulting in range measurement errors that must be addressed by system design. Solar
storms can cause severe ionospheric scintillation that can cause temporary loss of one or more satellite
signals. The likelihood of disruption due to scintillation will depend on the geographic area and will require
scientific assessment. Ionospheric phenomena have negligible impact on en route through NPA operations.

5.5.2 The type and severity of ionospheric effects vary with the level of solar activity, the region of the
world and other factors such as time of year and time of day. Rare solar storms can cause large variations in
ionospheric delays that can affect receivers over a wide area. Solar activity peaks every eleven years.

5.5.3 Severe scintillation can disrupt satellite signals but it occurs in patches and does not affect wide
areas of the ionosphere simultaneously. It therefore generally affects only a few of the satellites in view of an
aircraft. Losses of signal tracking due to scintillation are of short duration, but they may occur repeatedly
during periods of several hours. This can cause GNSS service to be degraded or temporarily lost, the
duration dependent on the receiver’s ability to rapidly reacquire a signal following the event. Scintillation
affects all GNSS frequencies, so multi-frequency receivers will not offer stronger protection. On the other
hand, multi-constellation GNSS would allow the receiver to track more satellites, reducing the likelihood of
service disruption.

5.5.4 Scintillation is virtually nonexistent in mid-latitudes, except at low to moderate levels, which can
occur during rare severe ionospheric storms. Severe scintillation is fairly common in equatorial regions
where it typically occurs after sunset and before local midnight. Moderate scintillation occurs frequently in
high-latitude regions, and can reach severe levels during ionospheric storms.

5.5.5 In mid-latitudes severe ionospheric storms may infrequently cause outages of SBAS APV
service, but in equatorial regions service outages would be much more frequent due to the formation of wide
bands of accumulated ionized particles located approximately 15 degrees north and south of the magnetic
equator. Narrow, elongated volumes, called depletions (or bubbles), in which the density of ionized particles
can drop well below that in the surrounding ionosphere, often develop in the midst of these bands just after
local sunset and persist late into the local night. The combination of these phenomena results in large spatial
and temporal variations in ionospheric delay and therefore presents a major challenge to the integrity of
SBAS ionospheric corrections. It is therefore not practical to provide single-frequency SBAS APV service in
equatorial regions.

5.5.6 Basic GNSS receivers use a simple theoretical ionospheric model and a small set of coefficients
broadcast by GNSS satellites to compute ionospheric corrections. This technique has been shown to reduce
the pseudorange errors due to ionospheric delays by a factor of about two. SBAS reduces these errors to a
few metres and assures the integrity of the corrections. SBAS can also detect the effects of ionospheric
storms that might threaten the integrity of the broadcast corrections and ensure that APV operations do not
continue when the system cannot compensate for these effects.

5.5.7 GBAS broadcasts pseudorange corrections that account for all error sources, as well as integrity
information that is effective even when the local ionosphere is severely disturbed. GBAS service would,
however, be lost if severe scintillation caused avionics or the GBAS station to lose lock on enough satellite
signals. The GBAS VDB is not affected by ionospheric conditions. The ionospheric threat model used by
GBAS integrity monitors must, however, be consistent with local conditions, which may result in lower
service availability or more siting constraints in equatorial regions than in mid-latitudes. Dual frequency
GBAS systems would be able to compensate for ionospheric delay effects, thus allowing for improved
performance with fewer constraints.

27
5.5.8 The Sun also has a direct effect on GNSS. Disturbances in the Sun's corona can create solar
radio bursts that may cause an increase in the level of RF noise in the GNSS frequency band(s), thereby
affecting the reception of signals from all satellites in view on the dayside of the Earth. In some rare cases,
the intensity and frequency band of a solar radio burst can cause GNSS receivers to temporarily lose all
satellite signals. Experience has shown that these events may last up to an hour. The vulnerability of
receivers to such events is highly dependent on their design. While geodesy receivers have been observed
to lose all signals for several minutes, so far no significant impact has been detected on aviation receivers.

28
 Chapter 6
GNSS EVOLUTION

6.1 General

6.1.1 GNSS will evolve by improving existing elements and creating new elements and signals (see
Appendix D). This will enhance GNSS performance but it will introduce technical complexity that must be
managed effectively in order to provide operational benefits.

6.1.2 The key to acceptance by aircraft operators is the business case – the value of incremental
operational benefits must exceed the cost of new avionics and their share of the cost of GNSS
infrastructure. GPS, GLONASS, ABAS, SBAS and GBAS, as well as ADS-B and ADS-C, already provide
very significant benefits to aircraft operators. It is not evident that every further technical advance will provide
clear incremental benefits. It will be necessary to quantify these benefits before taking decisions to proceed
with development and implementation.

6.1.3 If the issues related to GNSS evolution are properly addressed and aircraft operators are
satisfied with the business case, the introduction of new constellations and additional signals would resolve
some technical and institutional issues and provide operational benefits. Experience has shown that the time
required to refine a technical concept, develop standards and develop certified systems is often
underestimated. State ANS providers should proceed with PBN and ADS-B based on existing GNSS
elements rather than awaiting next generation systems. This will provide significant safety and efficiency
benefits and will provide the foundation for more benefits in future.

6.2 Multi-Constellation/Multi-Frequency GNSS

6.2.1 Today’s GNSS-based services rely for the most part on GPS, providing service on a single
frequency. GLONASS, however, is already in operation, and Beidou and Galileo are being deployed. All
constellations will eventually operate in multiple frequency bands. Related developments are expected in the
domain of GNSS augmentation systems.

6.2.2 The use of GNSS signals from multiple constellations broadcasting in multiple frequency bands
improves GNSS technical performance. The use of combined signals from independent systems will
enhance performance and service coverage. Moreover, combining signals improves robustness and will
allow GNSS to meet performance requirements when there is interference or an individual system failure.

6.2.3 Each of the new GNSS signals will be more resistant to interference due to higher power, wider
bandwidth and improved signal designs, resulting in better interference rejection capability. All signals
intended for safety-of-life applications should benefit from the protection provided through ITU allocation
within the ARNS bands.

6.2.4 GNSS performance is sensitive to the number of satellites in view. Multi-constellation GNSS will
substantially increase that number. This will improve availability and continuity of service, particularly in
areas where ionospheric scintillation can cause loss of lock on individual satellites. Furthermore, availability
of more than thirty interoperable ranging sources could allow ABAS to provide worldwide vertically guided
approaches with minimal, or potentially no need for external augmentation signals in the long term.

6.2.5 The availability of a second frequency will allow avionics to calculate ionospheric delay in real
time, effectively eliminating a major error source. Future SBAS systems would be able to support nearly
100% APV service availability with minima as low as 200 ft, even in equatorial regions. Moreover, as

29
discussed in 5.1.3, frequency diversification is a very effective mitigation against unintentional interference,
since it is highly unlikely that a source of unintentional interference could simultaneously affect more than
one GNSS frequency.

6.2.6 The availability of multiple independent constellations will provide redundancy to mitigate the risk
of service loss due to a major system failure within a core constellation, and will address the concerns of
some States about reliance on a single GNSS constellation outside their operational control.

6.3 Standards Development

6.3.1 As GNSS elements are added it will be necessary to develop ICAO SARPs and/or industry
standards for new elements and combinations considering technical, operational and economic factors. The
choice of combinations will have to take into account the incremental benefits as seen by aircraft operators
and ANS providers. Although the PBN concept allows for multiple technical solutions to meet performance
specifications, having fewer solutions is more cost-effective because more operators can share certification
costs. This is also less time consuming, because individual civil aviation authorities do not have to devote
resources to assessing multiple technical options.

6.3.2 The introduction of multi-constellation, multi-frequency GNSS entails a number of new

challenges, including: the need for signals of different GNSS constellations to be interoperable; legal liability
concerns; the more complex role of augmentation systems potentially dealing with different combinations of
GNSS constellations; and the increased complexity of avionics and aircraft integration and operational
control. To realize multi-constellation benefits, ICAO, States, ANS providers, standardization bodies,
manufacturers and aircraft operators need to coordinate activities to overcome these challenges. Experience
has demonstrated the need to devote attention to safety regulation and oversight, since lack of clarity in
these processes delays progress.

6.3.3 The GNSS evolutionary process should preserve backward compatibility so that aircraft
operators will not incur excessive costs and operational penalties.

6.4 Institutional Issues

6.4.1 Current GNSS avionics automatically select satellite and augmentation signals. The PBN
concept allows aircraft and avionics manufacturers the freedom to develop effective hardware and software
solutions to match airspace requirements. States, in their planning for implementation of GNSS services,
should avoid institutionally driven requirements or limitations on the use of specific GNSS elements. Such
regulations would increase avionics complexity, resulting in higher manufacturing, maintenance and training
costs. Moreover, a complex avionics interface could increase aircrew workload and create safety risks. The
ultimate goal is to establish an institutional and legal framework that would enable the unrestricted use of
any GNSS element. Until then, ICAO and the aviation industry will have to develop pragmatic solutions that
enable a gradual introduction of multi-constellation GNSS.

6.5 Core Constellation Evolution

6.5.1 GPS Evolution

6.5.1.1 GPS is evolving to meet the needs of civilian users by making the system more robust,
increasing system availability and possibly including features that reduce the complexity of GPS
augmentations.

30
6.5.1.2 L1C will be a civilian-use signal to be broadcast on the L1 frequency (1,575.42 MHz) that
currently contains the coded signal used by all GPS users, so it will be backward compatible. The L1C signal
will be available with the first Block III launch, currently scheduled for 2014. It will have a higher power and
other features to improve tracking by receivers, and it will enable greater compatibility with Galileo. The plan
is to have 24 operational satellites with L1C by about 2021.

6.5.1.3 An additional signal (L5) that can meet civil aviation’s safety requirements is being added at
1,176.45 MHz. The L5 signal is more robust than the current L1 and is being implemented on Block IIF
satellites; the first was launched in 2010. Plans call for the L5 signal to be broadcast from 24 GPS satellites
by 2018.

6.5.1.4 Although L2 (1,227.60 MHz) is currently not part of the GPS SPS, many civilian users, including
SBAS providers, employ codeless or semi-codeless dual frequency receivers to support their requirements.
A coded signal has been added at the GPS L2 frequency (L2C at 1,227.60 MHz). L2 is not in a band
protected for aviation, so it will not be used directly for aviation applications. Users, including SBAS
providers, who rely on codeless and semi-codeless access on L2 will have to transition to L2C or L5 before
2021. Plans call for the L2C signal to be broadcast from 24 GPS satellites by 2016.

6.5.1.5 The GPS III programme will include satellites with enhanced L1, L2, and L5 signals that will
meet civilian and military requirements for the next 30 years. The objective is a full transition to GPS III after
2030. Challenges that are being addressed include: representing both civilian and military GPS user
requirements; bounding GPS III requirements within operational objectives; providing a flexibility allowing for
future changes to meet user requirements through 2030; and providing robustness for the increasing
dependency on precise positioning and timing as an international utility.

6.5.2 GLONASS Evolution

6.5.2.1 The long-term (up to 2020) Russian Federation programme for GLONASS development and
modernization envisages an upgrade of both space and control segments.

6.5.2.2 The current GLONASS constellation consists of GLONASS-M satellites with a lifetime of seven
years and improved technical characteristics.

6.5.2.3 The next upgrade envisages the development of GLONASS-K satellites with better accuracy and
a lifetime of more than ten years that will transmit the standard accuracy signals for civilian users in the
bands L1 (1,559-1,610 MHz) and L3 (1,164-1,215 MHz).

6.5.2.4 The GLONASS-K satellites will transmit, along with CSA navigation signals in the L1 band
(FDMA), new CDMA navigation signals in the L1 and L3 bands. The next upgrade of GLONASS-K will
introduce the capability to receive and retransmit distress signals of the COSPAS-SARSAT global search
and rescue satellite-aided system.

6.6 Planned New Core Constellations

6.6.1 Galileo

6.6.1.1 Galileo is a satellite-based radio navigation system that uses precise range measurements from
Galileo satellites to determine position and time anywhere in the world. The system is operated on behalf of
the European Union.

6.6.1.2 The fully deployed Galileo system (expected in the 2019/2020 timeframe) will consist of a
constellation of 30 medium earth orbit (MEO) satellites in three orbital planes (27 operational satellites plus 3

31
spares), as well as control centres in Europe and a network of sensor and uplink stations installed around
the globe.

6.6.1.3 Galileo’s global signals will support open, commercial and publicly regulated services. Galileo will
also provide a Search and Rescue (SAR) service compatible with COSPAS/SARSAT. The open service
signals, which will support aviation applications in combination with standardized augmentation systems,
offers three frequencies at 1575.420 MHz, 1191.795 MHz and 1176.450 MHz, known as E1, E5b and E5a
respectively.

6.6.1.4 It is planned to provide early capabilities of the open, publicly regulated and SAR services from
2014 onwards when sufficient satellites are deployed. The service capabilities will then gradually evolve
towards their full performance as the constellation deployment nears its completion.

6.6.1.5 It is intended that the Galileo open service will be offered for use by the aviation community once
a stable service provision regime has been reached.

6.6.1.6 The ICAO NSP work programme includes the development of SARPs for Galileo with a phased
approach corresponding to the envisaged service implementation plan for Galileo.

6.6.1.7 Although clearly independent, Galileo is compatible and interoperable with GPS and GLONASS.

6.6.2 Beidou Navigation Satellite System

6.6.2.1 China started providing satellite navigation services with the Beidou navigation demonstration
system, an experimental regional system consisting of three GEO satellites; the first was launched in 2000
and the system was completed in 2003. This system was not designed to serve civil aviation; it provides
fundamental regional services including positioning, navigation, timing and short-message communications.

6.6.2.2 The Beidou Navigation Satellite System will operate in a similar way to Galileo and the next
generation GPS and employ the same frequency bands and signal structure. It will provide worldwide
coverage with a constellation of 35 satellites, including 5 GEOs and 30 non-GEO satellites (3 IGSO and 27
MEO). On Dec. 27, 2011, China officially announced that the BeiDou system began to provide Initial
Operational Service. Like GPS and Galileo, this system will provide open services and authorized services.

6.6.2.3 Beidou will be implemented in stages. It will cover the Asia-Pacific area by the end of 2012, and
will have global coverage around 2020.

6.6.2.4 The Beidou Time System (BDT) is traced to UTC and synchronized with UTC within 100
nanoseconds. To ensure interoperability, the offset between BDT and GPS/Galileo time will be measured
and broadcast.

6.6.2.5 The Beidou Coordinate System uses China Geodetic System 2000 (CGS2000), coinciding with
the International Terrestrial Reference Frame (ITRF) within a few centimetres. For most applications the
difference between CGS2000 and ITRF can be ignored.

6.6.2.6 Beidou will provide two global services: Open Service is free and open to users; Authorized
Service ensures high reliability even in complex situations. In addition the intention is to provide two kinds of
regional services: wide area differential service and short message service.

6.6.2.7 Additional information about Beidou, including the Beidou SIS Interface Control Document (ICD)
(test version) was published on December 27, 2011. The completed document and its updates will be
released gradually on the BeiDou governmental website: www.beidou.gov.cn.

32
 6.7 ABAS Evolution

6.7.1 The availability of multiple constellations and frequency diversity offers the possibility to develop
advanced RAIM (ARAIM) that could support high availability for en route through NPA and also support APV
globally. ARAIM investigations identify the need to refresh core satellite constellation and satellite reliability
parameters, or ARAIM integrity support messages, on an hourly basis, which will require an augmentation
signal of some kind. The ARAIM integrity support messages could be broadcast by the core constellations
through an integrity data channel or via SBAS. The ARAIM monitoring algorithms would detect fast-
occurring satellite faults and protect the user by excluding faulty satellites from the user position calculations.
This concept requires further research, development and validation, but it could simplify integrity
requirements for core constellations or SBAS systems in the long term. At least two core constellations
would be required to achieve ARAIM-based APV service.

6.8 SBAS Evolution

6.8.1 Some current and all planned SBAS GEOs include a ranging signal on L5 as well as L1. The
development of dual-frequency SBAS and associated avionics would have significant technical benefits.

6.8.2 The evolution of SBAS may also include augmentation of multiple GNSS constellations, with the
potential to support CAT II approaches. Because ionospheric delay is a function of frequency, dual
frequency avionics will be able to correct for delay when scintillation is not present. This would eliminate the
need to broadcast ionospheric grid points, delay values, and estimates of error. It will then become possible
to extend APV service to States in the equatorial region.

6.9 GBAS Evolution

6.9.1 GBAS as currently specified in Annex 10 is based on a single frequency band and provides CAT
I approach service. Russia has developed prototype systems that process GLONASS and GPS signals to
support GBAS approaches.

6.9.2 The evolution of GBAS will begin with an extension of the standards to enable operations to
lower minima ultimately to include CAT IIIB. The first step involves the implementation of multiple service
types and an associated equipment classification scheme to ensure that future services are compatible with
legacy GBAS avionics. New requirements will include enhanced monitoring in both the ground station and
the avionics to meet CAT IIIB integrity requirements. A SARPs amendment introducing a new GBAS
Approach Service Type (GAST) intended to support CAT II/III operations has been developed and is
currently undergoing operational validation.

6.9.3 The next step in GBAS evolution will be to extend the system to take advantage of multiple
frequencies and multiple constellations. Use of multiple frequencies will allow more robust monitoring and
detection of errors caused by ionospheric anomalies. Use of multiple constellations will enable higher
availability of robust geometries that are required to support CAT II/III operations and mitigate common
mode errors.

6.9.4 These evolutionary developments may support a variety of enhanced operational capabilities such
as: surface movement guidance and control; surface surveillance for situational awareness or conflict
detection and alerting; low visibility take-off guidance; guided departure procedures; complex approach
paths; and CAT I and CAT II approaches to lower than standard minima. The existing GBAS SARPS may
support some of these capabilities, but evolutionary developments may facilitate their introduction.

33
 Chapter 7

IMPLEMENTATION OF GNSS-BASED SERVICES

7.1 General

7.1.1 The growth of aviation and the urgent need to reduce fuel consumption and emissions demands
increased airspace and airport capacity and a focus on providing the preferred trajectory (route and altitude)
to each aircraft. Aircraft operators also require efficiency gains via approaches with the lowest possible
minima and the significant safety benefits of vertical guidance. In fact controlled flight into terrain (CFIT) in
the absence of vertical guidance is still a frequent accident category, at least for some segments of the
aviation community. Another key goal is to reduce the effects of airport noise on populated areas. GNSS-
based services can meet these goals and have already provided significant safety and efficiency benefits to
aircraft operators. The PBN Manual (Doc 9613) provides the guidance necessary to implement GNSS-
based navigation services.

7.1.2 GPS-based operations were first approved in several States in 1993. Many other States have
developed the legal framework for such services, but GNSS-based approaches are not yet approved on a
worldwide scale. It is recommended that States follow the precedents set by numerous aviation authorities
to allow the use of GNSS-based services. Where this is not deemed currently possible, those States are
encouraged to develop a set of preconditions or requirements under which the use of GNSS-based services
could become acceptable.

7.1.3 The ultimate goal is a transition to GNSS-based services to the extent that this can be shown to
be the most cost beneficial solution supported by safety and security analyses. Due to the vulnerability of
GNSS signals, however, some ground aids (e.g. DME and ILS) will be required for the foreseeable future.

7.2 International Implementation Planning

7.2.1 The basis for developing a seamless, global ATM system is through an agreed structure of
homogeneous ATM areas and major traffic flows. This requires States to cooperate to assess current and
foreseen aircraft population and capabilities, predicted traffic and the ATM infrastructure, including personnel
availability and requirements. States will then be able to identify gaps in performance and plan improved
services that would meet GANP performance objectives.

7.2.2 In making appropriate GNSS implementation decisions, States are encouraged to take
advantage of the expertise and information available at the ICAO PIRGs and their subgroups. ICAO has a
mandate to contribute to this process by:

a) ensuring regional and interregional coordination via regional planning groups;

b) providing a forum for the exchange of expertise and information among States and
international organizations; and

c) identifying technical assistance needs in the region and arranging for the provision of such
assistance.

7.2.3 States should pursue bilateral and multilateral coordination for detailed aspects not covered
within the ICAO framework.

34
 7.3 Development of a Concept of Operations (CONOPS)

7.3.1 After deciding to implement a GNSS-based service, the next step should be the development of
a concept of operations (CONOPS). This task should involve all stakeholders at the national and regional
level, and it should start with a high level description of the service and the enabling technology. A CONOPS
is a description of the characteristics of the service from the users’ (aircrew and air traffic controller)
perspectives. The CONOPS should state the goals, strategies, policies and constraints affecting the service.
It should identify organizations, activities and interactions among participants and stakeholders, including a
clear statement of responsibilities. It must support the development of the safety case, business case and
regulations. Once there is agreement that the safety case and the business case are valid, the ANS provider
can develop a comprehensive implementation plan.

7.3.2 The business case will be the key to a decision to implement, so the analysis must focus on
defining and quantifying costs and operational benefits and gaining acceptance by all stakeholders,
particularly aircraft operators, that the analysis is valid. In the case of en route and terminal operations, the
level of avionics equipage determines benefits. As long as the airspace design has to accommodate
equipped and non-equipped aircraft, benefits will be constrained. This does not apply to approach
operations, for which equipped aircraft will obtain the full benefit of lower minima.

7.3.3 Safety assessment starts at the first stage of CONOPS development; hazards and risks identified
in each phase will have to be mitigated at subsequent stages by adjusting the CONOPS. The CONOPS will
eventually reach a point where simulations and proof-of-concept trials can be used to validate assumptions,
quantify benefits and costs and identify safety risk mitigation measures.

7.3.4 When developing a CONOPS, States or regional entities need to consider the following
elements, some of which are discussed in this chapter:

a) current and projected regional and State traffic flows and volumes as described in regional
plans;

b) stated requirements of aircraft operators and their current and planned fleet composition
and avionics equipage;

c) plans of States in the region;

d) business case analysis;

e) system safety assessment;

f) certification and operational approvals;

g) training of ANS provider staff and aircrews;

h) airspace planning and procedure development;

i) air traffic management, including airspace and ATC considerations, including ATC
standards and procedures and automation systems;

j) aeronautical information services, including the notification of system failures;

k) GNSS signal vulnerability and anomaly/interference reporting;

l) effects on the environment, including emissions and noise; and

35
 m) transition planning.

7.3.5 States should include participants from the following groups to address the above elements and
develop a valid CONOPS that can guide decision-making and planning:

a) aircraft operators – personnel with decision-making roles who can assess benefits and
validate the business case;

b) aircraft operations - personnel from flight operations and aircrew training within airlines,
business aviation and general aviation who can validate operational procedures and the
safety assessment;

c) air traffic services – personnel responsible for airspace design, ATC procedures and
controller training;

d) airworthiness standards - personnel responsible for approving avionics and installations;

e) aviation standards - personnel responsible for developing the criteria for airspace design
and instrument approach procedures etc.;

f) aeronautical information services (AIS) - personnel who are involved with survey, AIS and
navigation databases, procedure design, NOTAM etc;

g) regulatory - personnel responsible for operational and other approvals, aircrew training
requirements and flight procedures in order to anticipate regulatory hurdles, since CONOPS
development is normally not a regulated activity;

h) aerodrome operators - personnel responsible for developing aerodrome infrastructure to

support approach operations;

i) engineering - personnel responsible for the design of CNS/ATM systems and equipment,
including avionics;

j) military representatives;

k) civil aviation officials from States in the region, and ICAO officials; and

l) other stakeholder groups, including labour unions and other GNSS users.

7.3.6 A common goal of regulators and ANS providers is to ensure high standards of safety while
providing aircraft operators with the benefits of GNSS technology in a timely and effective manner. This
requires a cooperative approach to the development of the standards, systems, airspace and procedures as
well as the terms and conditions for regulatory approvals that respond to the needs of the aviation
community. This applies whether the ANS provider is a State entity or a private company. Regulatory and
ANS provider organizations will have to allocate resources to specific tasks, outlined in Appendix C.

36
 7.4 Business Case Analysis

7.4.1 Introduction

7.4.1.1 Before implementing a new air navigation service it is necessary to develop an impact statement
detailing the costs to aircraft operators and ANS providers. The benefits of a GNSS-based service will be
realized only if aircraft operators equip with the required avionics. They will decide to equip when they are
satisfied that the incremental benefits of the proposed service exceed the incremental costs. Refitting a fleet
of aircraft with new avionics is very costly and can take years to accomplish, and operators generally seek a
quick return on investment. Experience has shown that aircraft operators with a fleet of older aircraft will
often decide to wait until they procure new aircraft. The analysis has to account for a transition period during
which benefits will gradually increase until all aircraft are equipped. For these reasons, ANS providers must
coordinate the development of a comprehensive business case with aircraft operators, accounting for all the
costs and benefits identified by the participants in the CONOPS development. The business case will be
credible only if the related CONOPS is credible, and this will require simulation and trials to satisfy
participants.

7.4.1.2 Along with system acquisition, operations and maintenance costs, ANS providers need to fund
operational implementation to include procedure development, training, possibly sharing in the cost of
avionics development, integration and operational approval. ANS providers need to provide an incentive to
equip by designing airspace and procedures that provide operational benefits.

7.4.1.3 In some cases non-quantifiable benefits (e.g. in a community that relies completely on aviation
for supplies and medical evacuation) will drive an implementation decision.

7.4.1.4 The analysis should consider such elements as cost recovery, revenue policy and extra costs
during a transition period. Experience has shown, however, that when cost recovery is linked to an individual
service, aircraft operators are very reluctant to support a CONOPS and will not equip with the required
avionics. They will be much more likely to equip if the service is not subject to specific charging. In cases
where the State is the ANS provider, the business case could consider benefits to other sectors of the
economy.

7.4.1.5 Some ICAO references for developing a business case are listed in Appendix B.

7.4.2 Common Cost Elements – Basic GNSS, SBAS and GBAS

7.4.2.1 The following costs borne by ANS providers are common to Basic GNSS, SBAS and GBAS
services: surveying to the World Geodetic System – 1984 (WGS-84) standard; designing airspace and
instrument approach procedures; performing flight checks; developing procedures and phraseology for ATC;
developing and delivering training material; developing a notification/NOTAM system; developing approval
and information documents for the aviation community; and funding annual costs associated with continuing
to provide service.

7.4.2.2 Common costs borne by aircraft operators include: avionics and installation; development of flight
procedures; development and delivery of training material to aircrew; development of maintenance material;
avionics database subscriptions; and associated recurring costs. The cost of aircraft out-of-service time
should be included except when modifications can be completed during scheduled maintenance.

7.4.2.3 Aircraft operators should choose avionics that meet all foreseen requirements (e.g. PBN, ADS-B,
ADS-C). This could mean a higher cost than initially anticipated, but would provide a wider range of future
benefits.

37
7.4.3 Basic GNSS Costs and Benefits

7.4.3.1 Many States implemented basic GNSS operations without developing a detailed business case
because the navigation system infrastructure (GPS) came at no cost. Many aircraft operators decided to
equip with off-the-shelf TSO C129 avionics when they calculated the fuel savings provided by direct routings
and the cost savings associated with lower approach minima: fewer diversions, overflights and
cancellations, including the cost of accommodating passengers when flights are disrupted. It is suggested
that when States are contemplating the introduction of basic GNSS services, they could take advantage of
documentation available from other States and implement basic GNSS operations without the need for a
detailed business case analysis.

7.4.4 SBAS Costs and Benefits

7.4.4.1 The costs associated with SBAS implementation from the ANS provider perspective, in addition
to those listed in section 7.4.2 include: system development; ground infrastructure, including reference
stations, master stations, terrestrial communications network; and GEO satellite costs. Options for the GEO
component include: employing an SBAS transponder on a State GEO that has multiple functions (e.g.
weather observation or communications); using a GEO dedicated to the SBAS function; or, contracting with
a commercial GEO operator to include an SBAS transponder on a GEO satellite in a suitable orbital slot.

7.4.4.2 It is desirable to implement SBAS in regions where multiple States share costs. This results in a
more affordable system, uniform service and benefits for all States in the region. One State could develop
the system and others could join later, or States could form a partnership for the development and
implementation of a regional SBAS.

7.4.4.3 Aircraft operators’ costs include those listed in section 7.4.2. It should be noted that as of 2012,
international airlines did not generally believe there was a business case to equip with SBAS avionics for
several reasons: these airlines typically serve airports with ILS; by integrating GNSS with IRS they achieve
high availability of guidance; and through integration with Baro VNAV they can fly vertically-guided
approaches, albeit to higher minima than with SBAS. At least one domestic airline, however, has equipped
Boeing 737 aircraft with stand-alone SBAS avionics that support ILS look-alike guidance to LPV minima.
This option provides benefits to airlines that serve domestic airports with little or no ILS service. Airbus is
developing SBAS avionics for the A350.

7.4.4.4 The benefits of SBAS include:

a) reduced flight disruptions and associated costs by providing lower minima to many runways,
including LPV down to 200 ft (CAT I minima);

b) reduced delays by providing increased airport capacity during LPV operations because SBAS,
unlike ILS, does not have sensitive areas that must be protected;

c) enhanced efficiency by supporting en route and terminal area PBN procedures, allowing more
aircraft to follow preferred trajectories;

d) improved access to runways where siting constraints prevent the use of conventional aids;

e) increased capacity on closely spaced parallel runways by supporting multiple glide path angles
and displaced thresholds;

f) reduced costs by allowing for the decommissioning of some conventional aids;

g) reduced costs for periodic maintenance because SBAS ground infrastructure is limited to a few
dozen locations, is normally installed in existing ANS facilities and employs redundant line

38
 replaceable components;

h) reduced costs for procedure validation compared with ILS and other conventional aids because
SBAS approaches do not require periodic flight inspections by aircraft with complex equipment;

i) reduced aircrew training costs when all approaches can be flown using vertical guidance; and

j) SBAS position accuracy and integrity meet the performance requirements for ADS-B terminal and
surface surveillance, as well as surface movement guidance and control systems.

7.4.5 GBAS Costs and Benefits

7.4.5.1 The costs of GBAS implementation from the perspectives of ANS providers and aircraft operators
include the cost of airport ground stations and those listed in section 7.4.2. It should be noted that as of 2012
GBAS avionics were only available for large airline and business aircraft.

7.4.5.2 The benefits of GBAS include:

a) reduced cost for ground infrastructure because a single GBAS ground station can provide
approach guidance to all runways at an airport, unlike ILS, where each runway requires a
dedicated system; costing must, however, account for any requirement to retain ILS to mitigate
vulnerability risks;

b) reduced flight disruptions and associated costs by providing lower minima to runways now
served by NPAs;

c) increased airport capacity because unlike ILS, GBAS does not have sensitive areas that must be
protected; service providers will, however, have to assess how to accommodate a fleet of users
equipped with GBAS or ILS avionics; realizing benefits may require runways reserved for GBAS
users;

d) enhanced efficiency by supporting terminal area PBN procedures when GBAS positioning
service is available, allowing more aircraft to follow preferred trajectories;

e) improved access to runways where siting constraints prevent the use of conventional aids;

f) reduced costs for periodic maintenance and flight inspection compared with ILS;

g) increased capacity on closely spaced parallel runways by supporting multiple glide path angles
and displaced thresholds; and

h) in future, the GBAS positioning service may provide benefits via surface movement guidance
and control.

7.4.5.3 Most of the cost for an airport to achieve CAT II/III operations is in airfield lighting, surface
movement guidance and control (possibly surface movement radar) and approach design (obstacle
clearance surface compliance), regardless of whether GBAS, ILS, or MLS are used. These other costs,
unless a runway already supports CAT II/III, must be included in the GBAS business case analysis. Airports
with CAT II/III service are typically very busy hubs, serving major cities and playing a significant role in the
local economy and in the financial viability of aircraft operators. Even brief service disruptions at such
airports can be very costly to operators. The business case for CAT II/III GBAS needs to consider the
requirement to retain ILS or MLS on one or more runways to support continued operations in the event of
GNSS signal interference.

39
7.4.6 ADS-B Costs and Benefits

7.4.6.1 Costs to the ANS provider associated with ADS-B surveillance include: ground stations (or in
future LEO satellite costs); terrestrial or satellite communications links; modification to ATC automation
systems to display ADS-B targets; development of ATC procedures and training material; simulation to
quantify benefits; training of ATC staff; and development of approval and information documentation for
aircraft operators. ADS-B ground stations are much less costly than radar to purchase and operate.

7.4.6.2 The benefits of ADS-B are significant in areas not currently served by radar. ICAO has
established that current ADS-B architecture, from a technical perspective, can support the 5NM separation
standard in en route airspace currently supported by radar. Starting from this point and considering local
traffic density and patterns, several States have completed ADS-B safety assessments that have led to the
application of a 5NM separation standard in non-radar airspace. This requires Basic GNSS avionics and a
Mode S transponder capable of broadcasting position information on 1090 Mhz. In remote airspace in
Canada and Australia, ADS-B implementation reduced separation standards from as much as 80NM to
5NM. In these States, despite the fact that not all aircraft in the ADS-B area are equipped, many operators
are realizing the potential for fuel savings based on their aircraft flying preferred trajectories. Airspace
simulation can be used to quantify benefits.

7.4.6.3 The United States plans to use ADS-B surveillance for all operations including surface movement
guidance and control. For the latter operation, SBAS is currently the only system capable of meeting ADS-B
accuracy and integrity requirements.

7.4.7 ADS-C Costs and Benefits

7.4.7.1 Costs to the ANS provider associated with ADS-C include modifying ATC automation systems to
process ADS-C data and display aircraft position on ATC situation displays. ADS-C uses the Aircraft
Communications Addressing and Reporting System (ACARS) digital datalink system used by airlines mainly
for operational messages. ATC systems need an interface with ACARS providers (ARINC and SITA) to
obtain position reports. This communications architecture also supports Controller Pilot Data Link
Communications (CPDLC).

7.4.7.2 The reduced separation standards supported by ADS-C provide increased airspace capacity.
This allows more aircraft to fly at optimum altitudes along optimum tracks, thus saving fuel and reducing
emissions.

7.5 System Safety Assessment

7.5.1 By approving GNSS-based operations, a State or RSOO accepts responsibility to ensure that
such operations meet accepted safety standards. States can either provide GNSS signals or can authorize
the use of signals provided by other entities. In the latter case the State retains the responsibility to oversee
the safety of the service, as described in the ICAO Safety Oversight Manual (Doc 9734). Moreover, States
are responsible for the total system, including aircraft, ATC and aircrew performance, aeronautical
information and aerodrome elements.

7.5.2 The ICAO Safety Management Manual (Doc 9859) describes the processes of hazard
identification and risk analysis that should be used to assess a proposed service before implementation. The
safety assessment should identify all technical and operational hazards and associated risks and develop
ways to eliminate hazards and/or reduce the probability or severity of possible outcomes.

7.5.3 Annex 11 — Air Traffic Services calls for a safety assessment before making significant safety-
related changes to the ATC system. The same principle applies to ANS providers, aerodrome operators,

40
aircraft operators or other regulated organisations. To avoid duplication of effort, more entities could jointly
assess the safety of the changes (e.g. implementation of a GBAS where the power supply is provided by the
aerodrome operator, where there is a control tower whose procedures will change and where the GBAS
operates in an area where SBAS signals are also available).

7.5.4 Each safety assessment normally relies on a number of assumptions, such as the installed
avionics have an airworthiness approval and the pilots are trained. It is the responsibility of the State to
verify that all the assumptions are substantiated.

7.5.5 SARPs for core constellations and augmentation systems and standards for avionics were
developed to meet recognized target levels of safety, so in some cases no further analysis of these
elements is required. Procedure design standards in PANS-OPS (Doc 8168) have a similar safety
foundation.

7.5.6 An effective safety assessment process starts at the first stage of development of a CONOPS
and considers all the technical and operational aspects of a proposed service. This supports the
development of suitable regulations, training, procedures and the fielding of related systems. The process
continues throughout the life cycle of the service. Experience shows that this approach results in the most
efficient use of resources by avoiding unanticipated problems that reduce benefits, create safety risks or
delay implementation.

7.5.7 In the case of GNSS augmentation and ADS-B systems, safety assessment must ensure that the
system design and implementation meets the SARPs. Since the first GNSS approvals in 1993, many States
have implemented PBN operations and some have implemented ADS-B. The regulations and operational
procedures developed by these States reflect a safety assessment that can be used as a basis by other
States, perhaps with a “differences analysis” to address any State-specific issues.

7.5.8 Not all aircraft are equipped with GNSS avionics. The safety assessment must consider the
operational procedures that accommodate equipped and non-equipped aircraft.

7.6 Certification and Operational Approvals

7.6.1 Operational Approvals

7.6.1.1 A State can authorize GNSS-based operations in its airspace in a number of different ways. The
most common alternatives are:

a) by granting GNSS approach privileges to instrument rated pilots;

b) by including the operations in the operational specification attached to the Air Operator
Certificate for commercial aircraft operators, having verified the approved flight manual and the
aircrew training; and
c) by issuing a document (e.g. specific approval in the form of letter of authorization) approving
specific operations for aircraft with certified equipment.

7.6.1.2 Some States have required the “specific approval” for CAT II and III operations, for other complex
operations or for “new” concepts of operations. The approval specifies all terms and conditions and
limitations on proposed operations.

7.6.1.3 Applying, documenting and obtaining a specific approval, especially for non-commercial
operators, will represent an administrative burden. It is therefore recommended that States or RSOOs do not
impose such additional processes when all the following eight requirements are fulfilled:
a) the aircraft, including its navigation avionics, has an airworthiness approval covering the proposed
IFR operations;

41
 b) the complexity of proposed IFR operations does not present particular challenges;
c) the concept and systems upon which the IFR operations will be carried out are mature enough, as is
the case today for GNSS;
d) the risk associated with improper operation is tolerable;
e) accuracy, integrity, availability and continuity of radio-navigation signals is ensured;
f) appropriate standards for quality and management of procedure design are established;
g) accuracy and integrity of the navigation data base is ensured; and
h) appropriate aircrew training and checking standards and procedures for the proposed IFR
operations exist and are implemented.

7.6.1.4 The wide variety of GNSS avionics and pilot interfaces dictates a tailored approach to aircrew
training and certification. In the case of aircraft equipped with Flight Management Systems (FMS) the
transition to GNSS-based operations will be relatively simple. In the case of stand-alone GNSS avionics, the
authorization of GNSS operations could include provisions for specific training, aircrew certification
requirements and the handling of airborne databases. Many States have developed training material
addressing GNSS-based services, and publish this material on the Internet.

7.6.2 Avionics Certification

7.6.2.1 As described in the PBN Manual, aircraft require avionics that meet the prescribed navigation
specification. Avionics used for GNSS-based services must be of an approved type and be installed in
accordance with specific criteria. Any new installation should be validated by a series of tests,
measurements and inspections. Certification and check procedures are based on the performance
standards contained in RTCA and EUROCAE documentation and in State documents. Avionics installations
can be approved as part of the original aircraft type design (type certificate) or as a modification to the
original aircraft type design (supplemental type certificate).

7.6.2.2 Supplements to aircraft flight manuals are part of the certification process. Most aircraft
manufacturers have made additions to their aircraft flight manuals to include GNSS-based avionics. The
appropriate State authority should approve these manuals, which contain operating procedures and
limitations necessary to ensure proper operation.

7.6.2.3 Pilot procedures, contained in aircraft operating manuals, need to address the characteristics of
GNSS and minimize aircrew and ATC workload. General flight procedures for the use of GNSS are included
in PANS-OPS (Doc 8168).

7.6.2.4 For ADS-B operations, the integration of GNSS sensors with the transponder or other medium
used for broadcasting position information must be shown to operate properly. This can be evaluated by
ANS providers who are able to observe ADS-B performance.

7.6.2.5 Since many States apply FAA or EASA standards, harmonization of these standards is essential
and is in practice pursued whenever possible by both agencies.

7.6.3 Use of non-IFR GNSS receivers for VFR navigation

7.6.3.1 Many pilots use receivers that do not meet the standards for IFR operations to supplement visual
flight rules (VFR) navigation, particularly in areas where there are few landmarks and where conventional
aids are not available or reliable.

42
7.6.3.2 Non-IFR receivers provide accurate guidance most of the time, but they do not provide the fault
detection afforded by RAIM, so a faulty satellite signal could produce a significant position error without any
warning to the pilot. Other potential problems may result from poor antenna location with portable receivers,
the inability to update receiver databases in some cases, and the use of map data other than WGS-84.

7.6.3.3 Pilots using non-IFR receivers must remain in visual meteorological conditions (VMC) and apply
pilotage or dead reckoning to ensure safety. They must resolve any difference between the GNSS position
and maps or navigation data available from other sources. There have been accidents in which VFR pilots
who relied excessively on GPS continued in deteriorating weather conditions without visual references and
lost control or became the victims of a CFIT accident. Some States have published safety material on this
subject.

7.6.3.4 Some States have adopted the use of VFR reporting points around airports where there is a
significant level of light aircraft traffic. GNSS assists in navigating to these VFR reporting points in VMC.
This enhances situational awareness and affords pilots more time to watch for other aircraft.

7.6.4 SBAS and GBAS System Safety Oversight

7.6.4.1 Ultimately an SBAS or GBAS must meet the SARPs. Typically States contract for the provision of
SBAS or GBAS, and a contractor must demonstrate:

a) that its system safety assessment process has adequately identified and assessed all
system safety hazards and that the design can be shown to meet the top-level safety
requirements (e.g. integrity and continuity of service);

b) that its testing and requirements verification processes confirm compliance with each
specification requirement. Typical areas of review under this activity include the applicant’s
system level verification/test plans, procedures and reports. States will also typically
complete verification testing with the contractors’ equipment; and

c) that its hardware and software development processes comply with the appropriate
standards.

7.7 System Testing and Procedure Validation

7.7.1 The Manual on Testing of Radio Navigation Aids (Doc 8071), Volume II — Testing of Satellite-
based Radio Navigation Systems provides guidance on the testing of GNSS. This testing is designed to
confirm the ability of GNSS signals to support flight procedures in accordance with Annex 10.

7.7.2 ANS providers must also assess the suitability of a procedure for publication, as detailed in
PANS-OPS, Volume II, Part I, Section 2, Chapter 4, Quality Assurance. The Quality Assurance Manual for
Flight Procedure Design (Doc 9906), Volume 5 – Flight Validation of Instrument Flight Procedures provides
the required guidance for GNSS-based procedures. Flight validation for GNSS-based procedures is less
costly than for conventional aids because there is no need for complex signal measurement and recording
systems and there is no requirement to check signals periodically.

7.8 Monitoring and Recording of GNSS Information

7.8.1 Annex 10 recommends that a State that approves GNSS-based operations should monitor and
record relevant GNSS data to support accident and incident investigations. These data can also be used
periodically to confirm GNSS performance. The objective is not to support a real-time notification process.

43
7.8.2 The parameters to be recorded are dependent on the type of operation, augmentation system
and core elements used. All parameters available to users within a given service area should be recorded at
representative locations in the service area.

7.8.3 The recording system need not be independent of the GNSS service and may be delegated to
other States or entities. To enable future reconstruction of position, velocity and time indications provided by
specific GNSS configurations, it is recommended to log data continuously, generally at a 1 Hz rate.

7.8.4 For GNSS core systems the following monitored items should be recorded for all satellites in
view:

a) observed satellite carrier-to-noise density (C/N0);

b) observed satellite raw pseudorange code and carrier phase measurements;

c) broadcast satellite navigation messages, for all satellites in view; and

d) relevant recording receiver status information.

7.8.5 For SBAS the following monitored items should be recorded for all GEO satellites in view in
addition to the GNSS core system items listed above:

a) observed geostationary satellite C/N0;

b) observed geostationary satellite raw pseudorange code and carrier phase measurements;

c) broadcast SBAS data messages; and

d) relevant receiver status information.

7.8.6 For GBAS the following monitored items should be recorded in addition to the GNSS core system
and SBAS monitored items listed above:

a) VDB power level;

b) VDB status information; and

c) broadcast GBAS data messages.

7.8.7 States and regions have addressed monitoring in different ways; examples include:

a) The United States has implemented a performance analysis network (PAN) used to
continuously verify GPS and WAAS performance. The results are documented in PAN
reports produced quarterly. These are available on the Internet at
http://www.nstb.tc.faa.gov/;

b) Eurocontrol has developed the EGNOS Data Collection Network (EDCN) for continuous
EGNOS performance monitoring. The network supported EGNOS certification and will
support the operational validation of EGNOS evolutions. The results will be documented in
quarterly reports, and will be available on the Internet at www.ecacnav.com; and

c) Russia uses a network of GBAS ground stations as regional monitoring data sources.

44
 7.9 Airspace Planning And Procedure Development

7.9.1 General

7.9.1.1 The PBN Manual explains the strategic objectives that define the airspace concept for a
particular area, the links to navigation functional requirements and the resulting navigation specification. In
most cases GNSS provides the only way to satisfy the technical performance required by an RNAV or RNP
navigation specification. Off-the-shelf systems that comply with Annex 10 and related avionics standards
meet these specifications. GNSS makes PBN affordable and accessible for all aircraft operators.

7.9.1.2 The PBN Manual also provides guidance for the design of flight procedures, including the
construction of routes, arrivals, departures and approaches based on navigation specifications.

7.9.1.3 PANS-OPS Volumes I and II include criteria for GNSS terminal, NPA and departure operations,
developed in line with Basic GNSS receiver performance. Standard instrument departure/standard
instrument arrival (SID/STAR) criteria have also been published. PANS-OPS also addresses APV SBAS,
APV Baro VNAV and GBAS procedures.

7.9.2 GNSS-Based Approach Procedures

7.9.2.1 When GNSS was first approved for NPA procedures, many ANS providers designed new GPS
stand-alone approaches. These offer significant benefits because they often provide lower minima, do not
require a course reversal and provide the aircrew with precise position information throughout the
procedure. They also provide a safety benefit by providing straight-in approaches to runways where
conventional aids could only support circling procedures.

7.9.2.2 In some States, pilots are authorized to fly suitable VOR, VOR/DME, non-directional beacon
(NDB) and NDB/DME NPA procedures using GPS guidance. These “GPS overlay” approaches allow
operators to benefit from better accuracy and situational awareness without the need for the ANS provider to
design a new approach. This is seen as an interim step to bring early benefits to users. This may in
particular allow users without automatic direction finder (ADF) avionics to fly in airspace where NDBs
support some operations. Using GPS guidance, pilots follow the path defined by the conventional aids and
comply with the charted minimum descent altitude. Some VOR and NDB-based procedures are not suited to
the overlay programme because certain approach legs cannot be adapted to the RNAV data coding system.

7.9.2.3 An overlay approach should be removed from the State Aeronautical Information Publication
(AIP) when a GPS stand-alone approach is designed for the same runway in order to avoid the potential for
confusion between two approaches to the same runway.

7.9.2.4 Certain operational restrictions were deemed necessary for the initial implementation of ABAS-
based NPA procedures flown using TSO C129 avionics. The reasons for and nature of these restrictions
vary from State to State and include: the lack of 100% RAIM availability; the availability of conventional aids
as a backup; traffic density; and regulations for avionics redundancy. A common operational restriction in
some States is that the pilot shall not take credit for GPS approaches at an alternate airport when
determining alternate weather minima requirements.

7.9.2.5 The Annex 10 terms NPA and APV coincide with Annex 6 approach categories but not with the
instrument and precision instrument runway categories in Annex 14. Current ICAO provisions do, however,
allow for the design of APV (LPV or LNAV/VNAV minima) approaches, consistent with the PBN RNP APCH
navigation specification, as demonstrated through implementations in many regions of the world. PANS-
OPS Vol II Part III section 3, chapter 4 paragraph 4.1.6 and chapter 5 paragraph 5.1.4 address this issue as
follows:

45
 “Annex 14 does not provide guidance on runway infrastructure requirements for approach and
landing operations with vertical guidance. In order to assess whether the runway is suitable for an
approach procedure with vertical guidance, that runway and associated OLS should at least meet
the Annex 14 requirements for non-precision approach runway if the OCH is not less than 90 m (300
ft) and for CAT I precision approach runway if the OCH is lower than 90 m (300 ft).”

Note: work is currently in progress to update the terminology associated with the classification of
approaches. The anticipated applicability date for the new approach classification provisions is in 2013;
when they become applicable this paragraph will be amended accordingly.

7.9.2.6 The advent of GNSS created a strong demand for PBN approach procedures, and some States
have experienced difficulty meeting this demand. These procedures are, however, well suited to computer-
aided design, which increases productivity and makes it possible to quickly evaluate alternatives and find the
best available design in a given situation.

7.9.3 Minimum En-route Altitude (MEA)

7.9.3.1 Conventional navigation aid coverage limitations affect minimum en route altitude (MEA) on
airways. In some cases this requires aircraft to fly at higher altitudes where oxygen may be required or
where icing conditions exist. GNSS provides coverage to the ground, so MEA can be based on
considerations of terrain, obstructions and communications coverage.

7.10 Aeronautical Information Services

7.10.1 Information about GNSS-Based Operations

7.10.1.1 When a State approves GNSS-based operations it must provide a clear statement of terms and
conditions, procedures and such things as training requirements in the State AIP.

7.10.1.2 States also need to provide background information about GNSS technology and its operational
applications. Experience has shown that aircraft operators require detailed information to ensure compliance
with regulations as well as ensure the most effective and efficient use of GNSS. Many States have
developed such information and it is available on their web sites.

7.10.1.3 Due to the pace of development of GNSS technology and operations, aircraft operators require
current information that can assist them in planning for the acquisition of avionics. This can be achieved by
involving them in CONOPS and business case development.

7.10.1.4 Information updates may be published in an Aeronautical Information Circular (AIC), State AIP or
in some cases an advisory circular.

7.10.2 WGS-84 Coordinate System

7.10.2.1 With PBN, navigation guidance depends on the accurate definition of waypoint coordinates
based on a common geodetic reference system.

7.10.2.2 Annex 10 specifies that GNSS position information shall be expressed in terms of WGS-84.
Additional information on the use of WGS-84 may be found in Annex 4 — Aeronautical Charts, Annex 11 —
Air Traffic Services, Annex 14 — Aerodromes, and Annex 15 — Aeronautical Information Services, as well
as the WGS-84 Manual (Doc 9674).

7.10.2.3 The WGS-84 Manual contains guidance material regarding the transformation of existing
coordinates and reference data to WGS-84. It should be noted that this is a mathematical process that does

46
not take into consideration the quality and accuracy of the original coordinates. Many States have elected to
resurvey to WGS-84 standards due to the lack of integrity of existing surveys, and resurvey is considered to
be the preferred option.

7.10.2.4 Annex 10 specifies that the GLONASS coordinate system shall be PZ-90, and it provides
conversion parameters used to obtain coordinates in WGS-84. In 2007 the PZ-90 datum was updated to
differ from WGS 84 by less than 40 cm in any given direction.

7.10.3 Airborne Navigation Database

7.10.3.1 The safety of GNSS navigation and approach guidance depends on the integrity of the data in
the airborne navigation database. States must ensure that the quality (accuracy, integrity and resolution) of
position data is retained from the time of survey to the submission of information to database suppliers who,
with avionics manufacturers, create the airborne navigation database. States can ensure database integrity
through certification and oversight of data providers or by delegating oversight responsibility to certified
aircraft operators. This process should also ensure consistency with the data used in ATC flight data and
radar systems.

7.10.3.2 Navigation specifications in the PBN Manual identify database requirements for specific
operations. Two harmonized EUROCAE/RTCA documents are available to assist in the production and
handling of aeronautical data: Standards for Processing Aeronautical Data (RTCA/DO-200A/EUROCAE ED-
76) and Standards for Aeronautical Information (RTCA/DO-201A/EUROCAE ED-77). These documents
provide a framework for developing valid waypoint coordinates and for ensuring that only correct coordinates
reside in airborne navigation databases. Provisions relating to aeronautical data are contained in Annex 11,
Chapter 2, and Annex 15, Chapter 3.

7.10.3.3 Maps and charts used by aircrew must be consistent with airborne navigation databases. The
path to be followed when flying a procedure is defined by waypoint coordinates and leg type designators
coded by database suppliers. Designers must therefore have an appreciation of data coding standards and
States should validate all waypoint coordinates and essential leg type designators, particularly those used in
instrument approach and departure procedures.

7.10.3.4 The airborne navigation database must be valid with respect to the effective AIRAC cycle, which
generally requires that a current database be loaded into the avionics every 28 days. The use of expired
navigation databases creates a safety risk.

7.11 GNSS Service Status Notification

7.11.1 General

7.11.1.1 State ANS providers have the responsibility to report the status of air navigation services. If the
status of a service changes or is predicted to change, users should be notified via direct communications
from air traffic services (ATS) and/or via a NOTAM or aeronautical information system (see Annex 15 —
Aeronautical Information Services and Procedures for Air Navigation Services — Air Traffic Management
(PANS-ATM, Doc 4444)).

7.11.1.2 With conventional aids, service is directly related to equipment status. Therefore a NOTAM
stating that an ILS is out of service indicates that the associated precision approach will not be available.

7.11.1.3 In the case of GNSS, when a core constellation satellite or an SBAS reference station fails or is
removed from service for maintenance, there is no direct relationship to a loss of service. In such cases ANS
providers and aircraft operators can determine the general effects of outages using mathematical models.
There are commercial and State entities that can assist States to develop systems to serve their airspace.

47
As described below, however, such models cannot define service availability with precision for all aircraft in
an area.

7.11.2 Core Satellite System Status NOTAMs

7.11.2.1 Operators of GNSS core constellations should provide information on actual and projected
outages of their satellites. The United States provides advisories via Notices Advisory to NAVSTAR Users
(NANUs) and the Russian Federation provides advisories via Notices advisory to GLONASS Users
(NAGUs). ANS providers and some aircraft operators require this information in NOTAM form to support
service status modelling. Systems operated by ANS providers typically generate service status notifications
and NOTAMs without human intervention.

7.11.2.2 It is not possible to establish precisely the performance at the aircraft level everywhere within a
service area using monitor receivers or mathematical models for the following reasons:

a) aircraft and monitor receivers may track different sets of satellites;

b) variations in the tracked satellite signals that are caused by airframe shape and antenna
installations cannot be estimated by a monitor;

c) aircraft dynamics can affect satellite signal reception;

d) terrain masking can affect the aircraft or monitor;

e) error sources such as multipath, receiver noise and the ionosphere may not be correlated
between the monitor and the aircraft receiver; and

f) aircraft receivers may apply unique techniques that improve on basic RAIM/FDE
availability.

7.11.2.3 Given the variety of avionics designs, one service status model cannot meet all operators’
requirements. A conservative model would produce false alarms for some aircraft. A less conservative
model would lead to missed detection of a service outage for some, false alarms for others. Regardless,
only the aircrew, not ATC, is in a position to determine whether, for example, it is possible to continue an
ABAS-based instrument approach. In contrast, ATC has access to ILS monitor data and can deny an ILS
approach clearance based on a failure indication. The real time monitor concept is neither practical nor
required for GNSS ABAS operations. It may be practical for SBAS and GBAS, but implementation would
depend on a valid operational requirement.

7.11.2.4 Aircraft operators with access to prediction software specific to their particular ABAS/RAIM
avionics will find it advantageous to employ that software rather than use the general notification service. In
the case of SBAS and GBAS, operators will rely on service status notifications.

7.11.2.5 AIS providers may choose to provide all service status notifications via NOTAM, but based on
experience in some States, the Internet provides an alternative that has certain advantages. These include:
the ability to graphically display predicted outages within a service area; the ability to automatically display
notifications pertinent to a specified route of flight; and the widespread acceptance of the Internet as a
source of pre-flight planning information. The Internet is not acknowledged in some States for service status
notification, however, because it does not meet the same security standards as a NOTAM system.

48
7.11.2.6 Regardless, service providers should use the NOTAM system to disseminate the information on
the following:

a) core satellite system status;

b) GNSS interference;

c) widespread SBAS service outages (e.g. due to a GEO failure); and

d) GBAS outages.

7.11.3 Interference NOTAMs

7.11.3.1 ANS providers must be prepared to act when anomaly reports from aircraft or ground-based units
suggest signal interference. If an analysis concludes that interference is present, ANS providers must
identify the area affected and issue an appropriate NOTAM.

7.11.3.2 In some States, military authorities test the capabilities of their equipment and systems
occasionally by transmitting jamming signals that deny GNSS service in a specific area. This activity is
normally coordinated with State spectrum offices and ANS providers. Military and other authorities operating
jamming devices should coordinate with ANS providers to enable them to determine the airspace affected,
advise aircraft operators and develop any required procedures.

7.11.4 “SBAS UNAVAILABLE” NOTAMs

7.11.4.1 An “SBAS UNAVAILABLE” NOTAM would be used in a case when all GEO satellites serving an
area failed. SBAS users would then be dependent upon RAIM/FDE for integrity monitoring. This NOTAM
would alert SBAS users to the requirement to perform pre-flight predictions of RAIM availability.

7.11.4.2 The failure of an SBAS reference station near the edge of a service area could lead to APV
unavailability at airports in a region. This could also be subject to an SBAS UNAVAILABLE NOTAM
specifying the region affected, or users could be advised about the affected airports as described in 7.11.6.

7.11.4.3 Although very unlikely, it is possible that the number of core constellation satellites could be
greatly reduced (e.g. fewer than 21 available) or that failure of components of the SBAS system could result
in low availability of SBAS en route through NPA (LNAV) service. Thus, SBAS service could still be
“available,” but there would be service outages. In this case the SBAS UNAVAILABLE NOTAM should
instruct SBAS users to perform preflight RAIM checks.

7.11.5 GBAS Station Outage NOTAMs

7.11.5.1 If a GBAS station is out of service or predicted to be out of service, an outage NOTAM is
required. It may be possible for a GBAS element failure to result in downgraded service (e.g. CAT II/III to
CAT I) rather than a complete service interruption.

7.11.6 PBN Service Status Notifications

7.11.6.1 Service status models should reflect all service levels approved in the State based on
ABAS/RAIM or SBAS, but not including those that require special authorization based on a proprietary
avionics design. Ensuring that service status models reflect appropriate service levels entails modelling for
the various integrity alert limits associated with PBN navigation specifications and those associated with
TSOs governing basic GNSS and SBAS operations.

49
7.11.6.2 Where multiple core constellation signals are used operationally, it will be necessary to model
joint use of these constellations.

7.11.6.3 In view of the fact that SBAS avionics (TSO C145/C146) and TSO C196 avionics can function as
TSO C129 avionics with better availability, the model should cater to users with SBAS avionics flying outside
SBAS service areas.

7.11.6.4 ANS providers should adopt conservative models compatible with avionics meeting basic
standards. This does not preclude providing a feature that allows users to input such things as mask angle
and barometric aiding capability to obtain predictions that are better matched to specific avionics
performance.

7.11.6.5 Table 7-1 provides an example of the service levels and related predictive integrity alert limits for
Basic GNSS (e.g. TSO C129) and SBAS (e.g. TSO C145/146) avionics.

Table 7-1 Service levels and Alert Limits

En Route Terminal LNAV LP LPV* CAT I*

LNAV/VNAV
Alert Limit HAL=2NM HAL=1NM HAL=0.3NM HAL=40m VAL=50m VAL=35m

GPS Avionics Provided Provided Provided N/A N/A N/A

SBAS Avionics Provided** Provided** Provided Provided Provided Provided

* SBAS LPV and CAT I both have an HAL of 40m, but the VAL may be assumed to be the dominant
component for service prediction.

** With a functioning SBAS, predictions for en route and terminal service are not required because
availability will be 100%. These predictions are required to serve aircraft with SBAS avionics outside
an SBAS service area or in the case where there is a widespread SBAS failure.

7.11.6.6 As additional service levels emerge they will have to be included in modelling and notifications
by adding appropriate alert limit calculations. This could include levels associated with ADS-B
implementation.

7.12 Anomaly Reporting

7.12.1 From the perspective of the aircrew, a GNSS anomaly occurs when navigation guidance is lost or
when it is not possible to trust GNSS guidance. In this respect an anomaly is similar to a service outage. An
anomaly may be associated with a receiver or antenna malfunction, insufficient satellites in view, poor
satellite geometry or masking of signals by the airframe. The perceived anomaly may also be due to signal
interference, but such a determination requires detailed analysis based on all available information.

7.12.2 Pilot action(s) may include:

a) reporting the situation to ATC as soon as practicable and requesting special handling as
required;

b) forwarding the aircraft call sign, location, altitude and time of occurrence to ATC; and

c) forwarding information to the designated authority as soon as possible, including a

description of the event (e.g. how the avionics failed/reacted during the anomaly).

50
7.12.3 Controller action(s) may include:

a) recording minimum information, including aircraft call sign, location, altitude and time of
occurrence;

b) attempting to identify other GNSS-equipped aircraft that may be experiencing the anomaly;

c) broadcasting the anomaly report to other aircraft, as necessary;

d) forwarding information to the designated authority; and

e) requesting the aircrew to file a complete report in accordance with State procedures.

7.12.4 States should designate a national or regional office to collect anomaly-related information and to
determine the course of action required to resolve reported anomalies that can be traced to signal
interference. This office should analyze and distribute information to the appropriate agencies within the
State and/or other international agencies. Some actions that the focal point unit may take are:

a) evaluating the anomaly reports;

b) advising ATS and providing situational updates;

c) notifying the agency responsible for frequency management;

d) ensuring the issuance of appropriate advisories and NOTAMs as necessary;

e) coordinating with States/Agencies that provide core satellite constellation(s) or other

GNSS element(s);

f) attempting to locate/determine the source of the interference;

g) implementing national policy to mitigate the anomaly; and

h) tracking and reporting all activities relating to the anomaly until it is resolved.

7.12.5 National and international coordination of actions to prevent and mitigate GNSS interference is
essential. To facilitate the reporting process, the use of a standard form allows for the tracking of reports of
anomalies and is helpful to the coordination efforts. States may require more detailed information for an
analysis of GNSS anomalies. Data collection and the subsequent evaluation of these data will provide
decision makers with the requisite support for implementation actions. Any form adopted by a State should
be included in the State’s AIP and enacted by AIC.

7.12.6 Should analysis of aircrew reports conclude that interference is present, ANS providers must
identify the area affected, issue an appropriate NOTAM, advise aircrew via direct communications, apply
mitigation as described below then locate the source and resolve the problem. ANS providers or other
responsible organizations may also use ground-based systems to detect interference.

51
 7.13 GNSS Vulnerability: Mitigating the Impact on Operations

7.13.1 Risk Assessment

7.13.1.1 As discussed in Chapter 5, States can take measures to reduce the likelihood of service outages
due to unintentional and intentional signal interference. ANS providers must still, however, complete a risk
assessment by determining the residual likelihood of service outages and the impact of an outage on aircraft
operations in specific airspace.

7.13.1.2 The likelihood of interference depends on such factors as population density and the motivation
of individuals or groups in an area to disrupt aviation and non-aviation services. The likelihood will be very
low to non-existent in oceanic and sparsely settled areas and will be highest near major population centres.
Impact assessment will consider the type of airspace, traffic levels and the availability of independent
surveillance and communications services, and will address safety and economic effects. The likelihood of
disruption due to scintillation will depend on the geographic area and will require scientific assessment.
Mitigation will be required when disruption is deemed to be possible and would have a significant impact.

7.13.1.3 In future the availability of multi-constellation/multi-frequency GNSS along with advanced

avionics will reduce the likelihood of service disruption.

7.13.2 Mitigation Strategies

7.13.2.1 The disruption of GNSS signals will require the application of realistic and effective mitigation
strategies to both ensure the safety and regularity of air services and to discourage those who would
consider disrupting aircraft operations. There are three principal methods, which can be applied in
combination:

a) taking advantage of on-board equipment such as IRS;

b) taking advantage of conventional navigation aids and radar; and

c) employing procedural (aircrew and/or ATC) methods.

7.13.2.2 Several States, in view of the remaining GNSS vulnerabilities, have identified the need for an
alternative position, navigation and timing (APNT) strategy with the goal of maintaining services to the
maximum extent possible in the event of a GNSS signal outage. To be effective, an APNT strategy must
have global application and must be affordable. It must also be possible to implement the strategy within a
relatively short time. This implies taking advantage of systems and avionics in use today, then defining a
realistic evolution path as necessary.

7.13.2.3 IRS provides a short-term area navigation capability after the loss of GNSS updating. Many air
transport aircraft are equipped with IRS and these systems are becoming more affordable and accessible to
operators with smaller, regional aircraft. Most of these systems are also updated by DME. An APNT strategy
should therefore consider architectures that include an IRS component and consider the availability of DME
updating.

7.13.2.4 Conventional aids can provide alternative sources of guidance. DME is the most appropriate
conventional aid available in the near to mid term to support PBN operations, since it currently provides an
input to multi-sensor navigation systems that allow area navigation in both en-route and terminal airspace.
VOR/DME currently provides a useful backup capability for en route flight. The most appropriate alternative
for precision approach service is Instrument Landing System (ILS). Depending on the threat assessment,
traffic levels and weather conditions, an ANS provider might find it appropriate to retain some or all of the
existing ILSs at an airport or within an area under consideration.

52
7.13.2.5 Procedural (aircrew or ATC) methods can provide effective mitigation in combination with those
described above, taking due consideration of:

a) the airspace classification and the availability of radar;

b) the avionics in aircraft using the airspace (e.g. most aircraft in high level airspace will have IRS
and/or DME/DME updating of navigation systems);

c) aircrew and air traffic controller workload implications and the availability of controller decision
support tools;

d) the impact that the loss of GNSS will have on other functions such as surveillance in an ADS-B or
ADS-C environment; and

e) the potential for providing the necessary increase in aircraft route spacing and/or separation in the
airspace under consideration.

7.13.2.6 By adopting an effective strategy using one or more methods identified in this section, an ANS
provider will not only ensure safe aircraft operations in case of GNSS outages, but will also discourage
intentional interference attempts by reducing the operational impact of interference.

7.14 Transition Planning

7.14.1 Conventional Navigation Infrastructure

7.14.1.1 The current infrastructure comprising VOR, DME and NDB aids was initially deployed to support
navigation along routes aligned between VOR and NDB facilities.

7.14.1.2 As traffic levels increased, additional aids were installed to support new routes. This produced a
non-uniform distribution of navigation aids. Some areas have a high density of aids while others have a low
to very low density. This does not imply, however, that new conventional aids are required in the latter areas
as States implement GNSS-based services.

7.14.1.3 As States implement PBN and more aircraft equip with GNSS avionics, regions with high traffic
levels will no longer need a high density of VORs and NDBs. This presents an opportunity to rationalize
conventional infrastructure.

7.14.1.4 Networks of DMEs enable aircraft equipped with suitable RNAV avionics to fly RNAV routes and
procedures. DME will likely be part of the long term mitigation strategy to allow continued RNAV operations
in the event of a temporary loss of GNSS signals.

7.14.2 Rationalization of Conventional Aids

7.14.2.1 The implementation of GNSS-based services offers an opportunity to rationalize conventional

navigation aids and radar. The pace of rationalization will depend on the level of GNSS avionics equipage,
on airspace and procedure development and on the vulnerability risk assessment.

7.14.2.2 Equipage depends to a great extent on demonstrating capacity, efficiency and environmental
benefits, and to a lesser extent ANS infrastructure cost savings, which will be greatest when aids reach the
end of their life cycle and require replacement.

7.14.2.3 Avionics equipage is complicated by the stage-by-stage approach to implementation, by the

advent of new features (e.g. multiple frequencies), and by the addition of new GNSS elements. States need
to work closely with operators to develop a coordinated strategy and a plan that is practical and achievable

53
from both ANS providers’ and aircraft operators’ perspectives. This process must identify all of the avionics
requirements to meet PBN, ADS-B and the requirements of any other operational systems.

7.14.2.4 In some States or regions, and at some point in the future, it may be necessary to mandate
equipage to ensure the efficient use of airspace. All such decisions require close coordination with aircraft
operators.

7.14.3 Future Conventional Infrastructure Planning

7.14.3.1 Initial rationalization plans in several States followed a “top-down” process based on the
expectation that the implementation of PBN would make conventional aids redundant. While PBN benefits
are acknowledged in principle, it is not always easy to justify full implementation of PBN unless PBN can
resolve airspace capacity and efficiency issues. Even when PBN is implemented, avionics equipage can
dictate the need to retain conventional aids and routes.

7.14.3.2 A “bottom-up” process may be more appropriate, considering that the greatest economic benefits
come from avoiding the replacement of aids at the end of their life cycle (typically 20 to 25 years).

7.14.3.3 This should be done by identifying rationalization opportunities, evaluating necessary route
changes and ascertaining whether a limited PBN implementation would be more cost effective than
replacing the aids. This strategy would provide a catalyst to start the airspace transition to a full PBN
environment.

7.14.3.4 Many airports have multiple instrument approach procedures based on conventional aids. These
all incur maintenance and training (aircrew and ATC) costs. The implementation of PBN approach
procedures provides an opportunity to decommission some of these procedures and the aids that support
them.

7.14.3.5 The primary source of precision approach guidance is currently ILS, and ILS will serve as the
main backup to GNSS-based approaches for the foreseeable future. Several States have recently initiated
ILS replacement projects, and some have installed MLS.

7.14.3.6 The ultimate goal of rationalization is to evolve to a minimum operational network of aids that will
make it possible to maintain a level of continuity and efficiency of operations that meet aircraft operators’
expectations to the extent possible.

7.14.3.7 As an example, one State with a high density of VOR facilities has developed a strategy with the
goal of maintaining an alternate means of navigation for VOR-equipped aircraft in case of a GNSS outage.
This would support non-GNSS guidance for aircraft operating at or above 5,000 feet to an airport within 100
nm that has an ILS or VOR approach procedure. This strategy will permit the State to decommission a very
significant number of VORs. At the same time, this State will enhance DME facilities to support RNAV
operations in Class A airspace and in the vicinity of major airports.

7.14.3.8 ADS-B is already providing significant benefits in non-radar airspace where radar would have
been much more costly. The implementation of ADS-B in busy terminal and en route airspace now served
by radar will not necessarily result in the elimination of radar. Some States have concluded that primary and
secondary radar coverage will be required for the foreseeable future in such areas to address: the threat of
interference with GNSS signals that would result in a loss of navigation and surveillance capability; the need
to detect aircraft without transponders or ADS-B; and the requirement to detect hazardous weather.
Nevertheless, ADS-B promises to provide operational benefits in such areas, and the implementation of
ADS-B could avoid the cost of redundant radar coverage.

7.14.3.9 States and regions need to tailor rationalization and mitigation strategies to existing and planned
traffic levels, aircraft capabilities, threat levels and aircraft operators’ expectations. Major air carriers will

54
likely require a near-normal service with minimal impact on capacity. General aviation and helicopter
operators who generally operate in accordance with VFR will be better able to tolerate outages.

7.15 Programmatic and Security Issues

7.15.1 The security of conventional aids is the responsibility of State authorities. GNSS coverage
extends over the territory of many States, so security should be addressed at a regional or global level. It is
important to protect the GNSS elements used by civil aviation are against terrorism or hostile acts.

7.15.2 States must anticipate the possibility of GNSS and conventional navigation aid service
interruption or degradation during a national emergency situation (Article 89 of the Convention on
International Civil Aviation refers). States must also have contingency plans in the event of an international
conflict or if a neighbouring State jams GNSS signals in such a way that service is disrupted beyond its
borders. GNSS security aspects are being addressed by some States and may result in new procedures to
protect the safety and efficiency of aircraft operations.

7.15.3 Programmatic issues, including a lack of resources, launch failures or unanticipated satellite
failures could result in insufficient satellites being available to support specific GNSS-based services.
Control segment failure or human error could also potentially cause service outages and common-mode
errors on several satellites of a single constellation. The provision of reliable services from core satellite
constellations requires robust system management and funding.

7.16 Realizing GNSS Potential

7.16.1 GPS has provided safety and efficiency benefits to civil aviation since 1993, leading to
widespread acceptance of GNSS-based services by aircraft operators, State regulators and ANS providers.
Many States have started reorganizing airspace for increased efficiency based on PBN, ADS-B and ADS-C,
and have designed approaches that enhance safety and improve airport accessibility.

7.16.2 The rate of equipage with GNSS avionics is one key to realizing maximum benefits. The full
benefits of PBN in en route and terminal airspace depend on virtually all aircraft being equipped. Aircraft
operators will invest in avionics only if proposed services promise significant operational benefits and cost
savings. ANS providers and regulators must work with aircraft operators to identify the technical solutions
and services that will satisfy their safety and business cases.

7.16.3 Ideally, GNSS would support the decommissioning of all conventional aids, allowing aircraft
operators to eliminate the capital and training costs associated with maintaining conventional and GNSS
avionics. It would also mean cost savings for ANS providers. GNSS signal vulnerability issues, however,
necessitate the retention of some conventional aids for the foreseeable future. In the meantime ANS
providers can reduce costs by rationalizing networks of these aids.

7.16.4 The availability of multiple constellations broadcasting on multiple frequencies will make GNSS
more robust and will allow service expansion with increased benefits after 2020 when systems and avionics
are available. In the meantime, ANS providers can work with aircraft operators to expand GNSS-based
services and benefits while planning next generation services. The ASBUs and the navigation and PBN
roadmaps in the GANP provide a planning framework that States can adapt to their operational environment
while ensuring global compatibility.

55
 Appendix A
ACRONYMS

AAIM Aircraft Autonomous Integrity Monitoring

ABAS Aircraft-Based Augmentation System
ACARS Aircraft Communications Addressing and Reporting System
ACAS Aircraft Collision Avoidance System
ADF Automatic Direction Finder
ADS-B Automatic Dependent Surveillance – Broadcast
ADS-C Automatic Dependent Surveillance – Contract
AIC Aeronautical Information Circular
AIP Aeronautical Information Publication
AIS Aeronautical Information Service
ANS Air Navigation Service
APV Approach Procedure with Vertical Guidance
ARAIM Advanced RAIM
ARNS Aeronautical Radionavigation Service
ASBU Aviation System Block Upgrade
ATC Air Traffic Control
ATM Air Traffic Management
ATS Air Traffic Services
Baro VNAV Barometric Vertical Navigation
BDT BeiDou Time
BeiDou BeiDou Navigation Satellite System
C/A Coarse Acquisition
CAT I Category I
CAT II Category II
CAT III Category III
CDMA Code Division Multiple Access
CFIT Controlled Flight Into Terrain
CGS2000 China Geodetic System 2000
C/N0 Carrier-To-Noise Density
CNS Communications, Navigation, and Surveillance
COSPAS Space system for search of vessels in distress
CPDLC Controller-Pilot Data Link Communications
CSA Channel of Standard Accuracy (GLONASS)
DA Decision Altitude
DH Decision Height
DME Distance Measuring Equipment
EASA European Aviation Safety Agency
EC European Commission
EDCN EGNOS Data Collection Network
EGNOS European Geostationary Navigation Overlay Service
ELT Emergency Locator Transmitter
ETSO Technical Standard Order (Europe)
EU European Union
EUROCAE European Organisation for Civil Aviation Equipment
FAA Federal Aviation Administration (of the United States)
FAS Final Approach Segment
FD Fault Detection
FDE Fault Detection And Exclusion
FDMA Frequency Division Multiple Access

56
FMS Flight Management System
ft feet
GAGAN GPS Aided GEO Augmented Navigation (System) (India)
GAST GBAS Approach Service Type
GBAS Ground-Based Augmentation System
GBAS/E GBAS VDB Elliptical Polarization
GBAS/H GBAS VDB Horizontal Polarization
GEO Geostationary Earth Orbit (satellite)
GIVE Grid Ionospheric Vertical Error
GLONASS GLObal NAvigation Satellite System (Russian Federation)
GLS GBAS Landing System
GNSS Global Navigation Satellite System
GPS Global Positioning System
GPWS Ground Proximity Warning System
GRAS Ground-Based Regional Augmentation System
HAL Horizontal Alert Limit
HEO Highly Elliptical Orbit
HMI Hazardously Misleading Information
HPL Horizontal Protection Level
Hz Hertz
ICAO International Civil Aviation Organization
ICD Interface Control Document
IFR Instrument Flight Rules
IGSO Inclined Geosynchronous Orbit
ILS Instrument Landing System
IRS Inertial Reference System
ITRF International Terrestrial Reference Frame
ITU International Telecommunication Union
LAL Lateral Alert Limit
LNAV/VNAV Lateral Navigation/Vertical Navigation
LP Localizer Performance
LPL Lateral Protection Level
LPV Localizer Performance with Vertical Guidance
m metres
MASPS Minimum Aviation System Performance Standards
MEA Minimum En Route Altitude
MEO Medium Earth Orbit
MLS Microwave Landing System
MMR Multi-Mode Receiver
MOPS Minimum Operational Performance Standards
MSAS MTSAT Satellite-based Augmentation System (Japan)
MTSAT Multi-Functional Transport Satellite (Japan)
NAGU Notice Advisory to GLONASS Users
NANU Notice Advisory to NAVSTAR Users
NDB Non-Directional Beacon
NOTAM Notice to Airmen
NPA Non-Precision Approach
NSP Navigation Systems Panel (ICAO)
P-code Precise Code (GPS)
PAN Performance Analysis Network (USA)
PANS-ATM Procedures for Air Navigation Services — Air Traffic Management
PANS-OPS Procedures for Air Navigation Services — Aircraft Operations (Doc 8168)
PBN Performance Based Navigation
PIRG Planning and Implementation Regional Group
PNT Positioning, Navigation and Timing
PPS Precise Positioning Service

57
PRN Pseudo Random Noise
PZ-90 Parameters of the Earth 1990 coordinate system used in GLONASS
RAIM Receiver Autonomous Integrity Monitoring
RF radio frequency
RNAV Area Navigation
RNP Required Navigation Performance
RNSS Radionavigation Satellite Service
RSOO Regional Safety Oversight Organization
RTCA RTCA Inc. (United States)
SA Selective Availability
SARPs Standards and Recommended Practices
SARSAT Search And Rescue Satellite-Aided Tracking
SBAS Satellite-Based Augmentation System
SDCM System for Differential Correction and Monitoring (Russian Federation)
SID Standard Instrument Departure
SPS Standard Positioning Service (GPS)
STAR Standard Instrument Arrival
TACAN UHF Tactical Air Navigation Aid
TAWS Terrain Awareness and Warning System
TSO Technical Standard Order (United States FAA)
UDRE User Differential Range Error
UTC Coordinated Universal Time
VAL Vertical Alert Limit
VDB VHF Data Broadcast
VFR Visual Flight Rules
VHF Very High Frequency
VOR VHF Omnidirectional Radio Range
VPL Vertical Protection Level
WAAS Wide Area Augmentation System (United States)
WGS-84 World Geodetic System — 1984

_________________

58
 Appendix B
REFERENCES

RELEVANT ICAO PUBLICATIONS

The following are ICAO publications related to GNSS implementation. Document summaries can
be found in the Catalogue of ICAO Publications and Audio-visual Training Aids.

Assembly Resolutions

A32-19: Charter on the Rights and Obligations of States Relating to GNSS Services

A32-20: Development and elaboration of an appropriate long-term legal framework to

govern the implementation of GNSS

A33-15: Consolidated statement of continuing ICAO policies and practices related to

communications, navigation, and surveillance/air traffic management
(CNS/ATM) systems

A37/11 States to complete a PBN implementation plan as a matter of urgency

Annexes to the Convention on International Civil Aviation

Annex 2 Rules of the Air

Annex 4 Aeronautical Charts

Annex 6 Operation of Aircraft

Annex 10 Aeronautical Telecommunications, Volume I (Radio Navigation Aids)

Annex 11 Air Traffic Services

Annex 14 Aerodromes

Annex 15 Aeronautical Information Services

Documents

Doc 4444 Procedures for Air Navigation Services — Air Traffic Management

Doc 7030 Regional Supplementary Procedures

Doc 7300 Convention on International Civil Aviation

Doc 8071 Manual on Testing of Radio Navigation Aids, Volume II — Testing of
Satellite-based Radio Navigation Systems

59
 Doc 8126 Aeronautical Information Services Manual

Doc 8168 Procedures for Air Navigation Services — Aircraft Operations

Volume I — Flight Procedures
Volume II — Construction of Visual and Instrument Flight Procedures

Doc 8400 Procedures for Air Navigation Services — ICAO Abbreviations and
Codes

Doc 8697 Aeronautical Chart Manual

Doc 9161 Manual on Air Navigation Services Economics

Doc 9426 Air Traffic Services Planning Manual

Doc 9613 Performance Based Navigation (PBN) Manual

Doc 9660 Report on Financial and Related Organizational and Managerial Aspects
of Global Navigation Satellite System (GNSS) Provision and Operation

Doc 9674 World Geodetic System — 1984 (WGS-84) Manual

Doc 9689 Manual on Airspace Planning Methodology for the Determination of

Separation Minima

Doc 9734 Safety Oversight Manual

Doc 9750 Global Air Navigation Plan for CNS/ATM Systems

Doc 9859 Safety Management Manual

Doc 9906 Quality Assurance Manual for Flight Procedure Design, Volume 5 –
Flight Validation of Instrument Flight Procedures

EB 2001/56 Interference to Global Navigation Satellite System (GNSS) Signals

Circulars

Cir 257 Economics of Satellite-based Air Navigation Services

Cir 278 National Plan for CNS/ATM Systems

OTHER PUBLICATIONS

ITU-R SM 1009-1 Compatibility Between the Sound-Broadcasting Service in the Band of

About 87 – 108 MHz and the Aeronautical Services in the Band 108 –
137 MHz

RTCA/DO-200A/EUROCAE ED-76 Standards for Processing Aeronautical Data

60
 RTCA/DO-201A/EUROCAE ED-77 Standards for Aeronautical Information

ECC Report 129 Technical and operational provisions required for the use of GNSS
repeaters

ECC Report 145 Regulatory framework for Global Navigation Satellite System (GNSS)
repeaters

ECC Recommendation (10)02 A framework for authorization regime of Global Navigation

Satellite System (GNSS) repeaters”

U.S: National Telecommunications and Information Administration (NTIA) “Manual of Regulations

and Procedures for Federal Radio Frequency Management”, a.k.a. “Red Book”. Note: Section
9.3.20 of the NTIA Redbook only applies to federal government users. Use of repeaters by non-
government users in the US is prohibited.

IS-GPS-200 GPS Interface Specification

Avionics Standards Documents

RTCA (EUROCAE) Minimum

Operational Performance
Standards/Minimum Aviation System
Augmentation United States FAA Technical Performance Standards
systems Standard Order (TSO) (MOPS/MASPS)

ABAS TSO-C129A Level 2 (en-route/terminal) RTCA/DO-208

TSO-C129A Levels 1 or 3 (NPA) EUEOCAE ED-72A
TSO-C196 RTCA/DO-316
EASA ETSO-C129c

SBAS* TSO-C145 RTCA/DO-229D

TSO-C146A EASA ETSO-C145c, -C146c
EASA ETSO-C145c, -C146c

GBAS TSO-C161A RTCA/DO-245A

TSO-C162A RTCA/DO-246D
RTCA/DO-253C
EUROCAE ED-95

* SBAS avionics meet all ABAS requirements.

61
 Appendix C

ROLES OF ANS PROVIDERS AND REGULATORS

Air Navigation Service Provider Regulator

Lead the development of a CONOPS aimed at Participate in CONOPS development to identify
meeting aircraft operators’ goals for a proposed requirements for new or modified regulations.
GNSS-based service that defines performance
requirements and that proposes system
architecture.

Develop and adhere to a Safety Management Conduct safety oversight of the service
Plan to cover its GNSS-based services. provider’s GNSS-based services.

Complete trials, simulations and studies to Consider the service provider’s

validate the CONOPS. recommendations for operational approvals
based on study conclusions.

Coordinate provision of GNSS-based service Develop aircrew training and certification

with aircraft operators and the regulator. standards for the use of GNSS avionics by
commercial and business aircraft operators.

Approve the operational use of GNSS by

commercial and business aircraft operators.

Develop guidance material and processes for

the operational approval of GNSS.

Establish requirements for specific operator

approvals, aircrew training and certification.

Assist aircraft operators to make informed Develop national standards and guidance
decisions on the acquisition of avionics for material for the certification and installation of
GNSS-based services. GNSS avionics in nationally registered aircraft.
Where necessary, the development of
standards and guidance may be accomplished
as a joint effort with other airworthiness
authorities to avoid duplication of effort and to
maximize harmonization

Certify or oversee the certification, as

applicable, of GNSS avionics equipment
designed and manufactured nationally as well
as the installation of GNSS equipment in
nationally registered aircraft.

Develop guidance material and approval

62
 Air Navigation Service Provider Regulator
processes covering the installation of GNSS
avionics

Identify equipment and installation standards,

including provisions in Aircraft Flight Manual
Supplements.

Coordinate the development of business cases

for GNSS-based services to support decision-
making by aircraft operators and service
providers.

Establish appropriate strategies for fielding Validate the safety aspects of mitigation
GNSS-based infrastructure, mitigating GNSS strategies.
outages and decommissioning ground aids, as
appropriate. This incudes safety oversight of
contractors.

Coordinate the development of survey

methodology and implement the WGS-84
standard

Develop and implement data handling

processes to meet the accuracy and integrity
requirements of GNSS-based operations.

Develop status monitoring, notification and

NOTAM systems to support GNSS-based
operations.

Publish instrument approach and other GNSS- Develop GNSS-based instrument procedure
based procedures. design standards, or approve the use of
existing PANS-OPS or other recognized
Provide aeronautical information on GNSS criteria.
procedures to database suppliers and chart
producers. Oversee the certification of GNSS-based
systems and related airspace procedures.

Establish flight check requirements and

procedures, acquire the needed equipment and
carry out necessary flight checks for GNSS-
based operations.

Monitor and record GNSS performance.

Develop and publish guidance and training Publish the terms and conditions associated
material related to the operational use of with the approval to use GNSS via the State
GNSS-based services to support the training of Aeronautical Information Publication,
aircrew and ATS personnel. Aeronautical Information Circulars and advisory

63
 Air Navigation Service Provider Regulator
circulars.

Develop flight instructor guidelines and flight

training standards for the use of GNSS-based
services.

Define ATS requirements, airspace and

procedures, including application of separation
standards.

Establish training and certification requirements Approve training and certification requirements.
for procedure designers and ATS personnel.

Train ATS staff to support GNSS-based

operations.

Develop technical specifications for GNSS-

related infrastructure.

Procure and field GNSS augmentations and Conduct safety oversight for the
validate system performance against SARPs. implementation of GNSS-based infrastructure.

Identify GNSS-related spectrum management Provide spectrum management to protect

issues GNSS frequencies.

64
 Appendix D
GNSS SPECTRUM
Figure D-1: Frequency Allocations in the 1559 to 1610 MHz Band

Figure D-2: Frequencies used by Core Constellations

65
 Appendix E
Navigation Roadmap

66
 Appendix F
PBN Roadmap

67