GBAS vs. SBAS: How Aviation GNSS Augmentation Systems Work

Understanding the Two Technologies Transforming Satellite Navigation in Aviation

Executive Summary

GBAS and SBAS solve the same fundamental problem in different ways: basic GNSS alone does not always provide the accuracy, integrity, continuity, and availability required for safety-critical aviation operations.

A Satellite-Based Augmentation System, or SBAS, monitors GNSS performance across a very large geographic region. Ground reference stations calculate corrections and integrity information, which are then broadcast to aircraft through satellite signals. Examples include the FAA’s Wide Area Augmentation System (WAAS) and Europe’s EGNOS.

A Ground-Based Augmentation System, or GBAS, performs a similar augmentation function locally around an airport. Precisely surveyed ground receivers detect GNSS errors, and a local GBAS facility transmits corrections, integrity information, and approach-path data directly to approaching aircraft through a VHF Data Broadcast. The aircraft can then conduct a GBAS Landing System, or GLS, approach.

The result is not a contest in which one technology simply replaces the other. SBAS is optimized for wide-area navigation and broadly distributed approach capability, while GBAS is optimized for high-performance terminal and landing operations at specifically equipped airports.

Understanding that distinction is the key to understanding the future of satellite-based precision navigation.

Table of Contents

1. Why GNSS Needs Augmentation
2. What Is SBAS?
3. What Is GBAS?
4. GBAS vs. SBAS Architecture
5. How SBAS Works
6. How GBAS Works
7. GLS vs. LPV Approaches
8. Operational Advantages and Limitations
9. Integrity, Redundancy, and Safety
10. Advanced Technology and Future Development
11. Pilot and Maintenance Perspectives
12. Common Misconceptions
13. Main Points
14. Frequently Asked Questions
15. Conclusion
16. Discussion Questions 

Introduction

Why Does GPS Need Help to Land an Aircraft?

an airliner descending through cloud toward a runway with the crew relying on satellite-derived position information.

The aircraft may be traveling at more than 130 knots. The runway is only tens of meters wide. At low altitude, even a navigation error that appears small on an en route chart can become operationally significant.

For aviation, therefore, knowing an approximate position is not enough.

The navigation system must also answer a much more important question:

Can the aircraft trust that position right now?

This is where augmentation becomes essential.

Global Navigation Satellite Systems such as GPS provide extraordinarily capable worldwide positioning, but safety-critical aviation applications require additional mechanisms for accuracy, integrity monitoring, availability, and timely warnings when navigation performance cannot be trusted.

Two of aviation’s most important augmentation technologies are SBAS—Satellite-Based Augmentation System—and GBAS—Ground-Based Augmentation System.

The FAA describes both as augmentation methods that enhance satellite positioning for aviation. SBAS operates across broad geographic areas, while GBAS provides local corrections around an airport and enables GLS precision approaches.

Although pilots may see surprisingly similar lateral and vertical guidance in the cockpit, the infrastructure generating that guidance is fundamentally different.

Understanding those differences matters to pilots, engineers, airport operators, flight procedure designers, regulators, avionics technicians, and anyone studying the transition from conventional ground-based navigation toward performance-based satellite navigation.

1. Overview: Why GNSS Augmentation Exists

Basic GNSS Is Only the Starting Point

An aircraft’s GNSS receiver determines position by measuring signals transmitted by navigation satellites.

Those measurements can contain errors resulting from factors such as:

• Satellite clock errors
• Satellite orbit or ephemeris errors
• Ionospheric propagation effects
• Tropospheric effects
• Receiver errors
• Multipath
• Radio-frequency interference

Many of these errors are small enough for ordinary navigation but cannot simply be ignored when navigation guidance is being used close to the ground.

Aviation therefore requires more than accuracy.

It requires integrity.

What Does Integrity Mean?

Integrity is fundamentally the ability of a navigation system to provide confidence that its information can safely be used—and to warn the user within the required time if it cannot.

That distinction is critical.

A navigation solution could appear extremely accurate most of the time but still be unsuitable for approach operations if it could occasionally produce an undetected hazardous error.

Both SBAS and GBAS therefore combine:

GNSS positioning + correction information + Integrity monitoring.

2. What Is SBAS

SBAS stands for Satellite-Based Augmentation System.

It is a wide-area augmentation architecture in which a network of surveyed ground monitoring stations observes GNSS signals across a large geographic region.

The observations are processed to determine GNSS errors and integrity information. The resulting augmentation messages are sent to satellite broadcast systems and transmitted back to appropriately equipped aircraft.

The FAA’s WAAS architecture, for example, uses numerous Wide Area Reference Stations that send observations to master stations. WAAS generates augmentation messages containing information that allows compatible receivers to improve the accuracy and integrity of their navigation solution.

Major SBAS Systems

Examples around the world include:

• WAAS — United States
• EGNOS — Europe
• GAGAN — India
• Other regional systems and interoperable developments

ICAO has established standards intended to enable internationally compatible SBAS services.

Historical Development

The FAA commissioned WAAS into the U.S. National Airspace System on July 10, 2003. 

Since then, SBAS has become a major enabler of Performance-Based Navigation and vertically guided RNAV approaches.

3. What Is GBAS

GBAS stands for Ground-Based Augmentation System.

Instead of monitoring satellite errors across an entire continent, GBAS concentrates its augmentation capability in the vicinity of an airport.

A typical GBAS ground installation contains:

• Multiple precisely surveyed GNSS reference receivers
• GNSS antennas
• Ground processing equipment
• Integrity-monitoring functions
• A VHF Data Broadcast transmitter
• Supporting monitoring and control systems

FAA descriptions of operational GBAS installations identify multiple ground reference antennas, a central processing function, and a VHF Data Broadcast system as key components. 

The reference antennas know their positions extremely accurately.

Because the GBAS processor knows where an antenna actually is, it can compare that position with what the GNSS measurements indicate.

The difference allows the system to estimate errors affecting the satellite measurements locally.

These corrections and associated integrity information are transmitted to participating aircraft.

From GBAS to GLS

The landing application is known as GLS—GBAS Landing System.

In the United States, the FAA now reserves the GLS designation for approaches using GBAS.

A GLS-equipped aircraft uses GNSS together with locally transmitted GBAS corrections and digital approach-path information to generate precise three-dimensional approach guidance.

Operationally, the presentation to pilots can look deliberately similar to an ILS.

Airbus, for example, describes its GLS architecture as an ILS-like implementation in which pilots receive familiar lateral and vertical deviation indications.

4. GBAS vs. SBAS: Architecture Compared

Feature	GBAS	SBAS
Full name	Ground-Based Augmentation System	Satellite-Based Augmentation System
Coverage philosophy	Local / airport-centered	Regional / wide-area
Main ground infrastructure	Airport reference receivers and processor	Distributed regional reference-station network
Correction delivery	VHF Data Broadcast	Satellite broadcast
Main approach application	GLS	LPV and other SBAS-supported operations
Approach-path data	Can be transmitted by GBAS	Normally obtained from onboard navigation database for the published procedure
Infrastructure location	At or near airport	Distributed across a large region
Multiple runways	One GBAS can support multiple runway ends	SBAS service can support procedures at many airports throughout its coverage area
Typical strength	High-performance airport landing operations	Broad navigation and approach availability
Dependence on GNSS	Yes	Yes
Independent of GNSS interference?	No	No

The difference can be summarized visually:

                         

                          Click The Image for Detail

GBAS:

GNSS Satellites

↓

Airport Reference Receivers

↓

GBAS Ground Processor

↓

Integrity Monitoring + Corrections + Approach Data

↓

VHF Data Broadcast

↓

Aircraft Multi-Mode Receiver

↓

GLS Guidance

SBAS: 

GNSS Satellites

↓

Wide-Area Reference Station Network

↓

Master Processing Stations

↓

Correction + Integrity Messages

↓

Satellite Uplink

↓

SBAS Broadcast Satellite

↓

Aircraft SBAS Receiver

↓

Improved GNSS Navigation / LPV Guidance

5. How SBAS Works Step by Step

Step 1 — Reference Stations Monitor GNSS

A network of precisely located ground stations receives signals from navigation satellites.

Because the reference station’s true position is known, discrepancies in the satellite-derived solution can be analyzed.

Step 2 — Measurements Are Sent to Processing Facilities

Information collected across the network is transmitted to master processing stations.

The architecture allows the system to evaluate errors over a broad geographic area rather than at one airport.

Step 3 — Corrections and Integrity Information Are Generated

Processing determines information related to satellite performance and other correctable error sources.

The system also determines whether a satellite or service condition should be considered unsuitable for safety-critical navigation.

This integrity function is at least as important as improved accuracy.

Step 4 — Augmentation Messages Are Sent to Satellites

The processed augmentation information is transmitted through uplink facilities to satellites providing the SBAS broadcast.

Step 5 — The Aircraft Receives GNSS and SBAS Signals

An SBAS-capable receiver receives both the original GNSS measurements and the augmentation message.

Step 6 — The Receiver Calculates an Improved Navigation Solution

The aircraft applies the available corrections and evaluates whether navigation performance satisfies the required service level.

If the required integrity or protection criteria cannot be satisfied, the approach capability may downgrade or become unavailable.

Step 7 — The Flight Guidance System Uses the Position

For an LPV approach, the aircraft uses the augmented GNSS position together with the coded procedure contained in its approved navigation database.

The resulting display can provide lateral and vertical guidance with angular characteristics that appear similar to an ILS.

FAA guidance notes that LPV minima can, where procedure design and airport infrastructure permit, reach decision altitudes as low as approximately 200 feet above touchdown. 

Importantly, under FAA terminology, LPV provides approach-with-vertical-guidance performance rather than being classified identically to a conventional precision approach such as ILS. 

6. How GBAS Works Step by Step

Step 1 — The Airport’s Reference Receivers Observe GNSS

Multiple GBAS antennas are positioned at accurately surveyed locations around the airport.

They simultaneously receive signals from available GNSS satellites.

Step 2 — Measured Ranges Are Compared With Known Geometry

Because the precise positions of the reference antennas are known, the GBAS system can estimate errors affecting the satellite measurements.

The important engineering principle is local correlation.

An approaching aircraft and a nearby reference station are observing many of the same satellite-related errors under similar conditions.

Step 3 — The Ground Facility Performs Integrity Monitoring

Before supplying navigation information to aircraft, the system performs extensive monitoring.

Potentially unsafe satellite measurements, reference-receiver failures, or other unacceptable conditions must be detected and managed.

Step 4 — Corrections Are Generated

The GBAS processor produces local differential corrections and integrity parameters.

Step 5 — Final Approach Information Is Added

GBAS can also transmit the digital information defining the final approach path.

This is an important difference from an ILS.

An ILS creates physical radio guidance patterns using separate localizer and glideslope transmitters.

A GLS approach instead generates guidance relative to a digitally defined reference path.

Step 6 — Data Are Broadcast Over VHF

The corrections, integrity information, and approach-related data are transmitted through the VHF Data Broadcast, or VDB.

FAA guidance specifically identifies this VHF link as the means through which the GBAS ground facility provides aircraft with correction, integrity, and approach-path information.

Step 7 — The Aircraft Computes the Corrected Position

The aircraft’s approved GBAS avionics—often integrated into a Multi-Mode Receiver—combine GNSS measurements with the GBAS information.

Step 8 — GLS Deviations Are Calculated

The aircraft determines its position relative to the published final approach path.

The resulting lateral and vertical deviations can then feed:

• Primary Flight Display
• Flight director
• Autoflight computers
• Autopilot
• Flight guidance functions
• Crew alerting and monitoring systems

The FAA describes GLS as providing precise three-dimensional angular lateral and vertical guidance similar in operational presentation to ILS.

7. GLS vs. LPV: The Operational Difference Pilots Need to Understand

One of the most common sources of confusion is treating GBAS vs. SBAS as exactly equivalent to GLS vs. LPV.

They are closely related, but those terms describe different levels of the system.

GBAS and SBAS describe augmentation architectures.

GLS and LPV describe operational approach applications enabled by those architectures.

SBAS → LPV

SBAS is commonly associated with:

RNAV (GNSS/GPS) approach → LPV minima

The airport itself generally does not require a dedicated SBAS ground transmitter.

That is one of SBAS’s greatest strengths.

Airbus describes SBAS-based landing functionality as permitting satellite-based approaches without dedicated ground infrastructure at the destination airport.

GBAS → GLS

GBAS is commonly associated with:

GLS approach

The airport must have an approved GBAS facility.

The aircraft must also have compatible and approved GBAS/GLS avionics.

Similar Cockpit — Different Infrastructure

From the flight deck, the difference can seem surprisingly small.

Modern aircraft manufacturers deliberately design some GLS and SBAS landing interfaces to resemble familiar ILS guidance.

Airbus’s xLS philosophy, for example, uses consistent lateral and vertical indications across ILS, GLS, SBAS-based SLS, and other approach functions to reduce differences in pilot technique.

Behind the display, however, the navigation architectures are very different.

8. Functions, Advantages, and Limitations

Advantages of SBAS

Wide Geographic Coverage

A single SBAS architecture can support users across very large regions.

FAA guidance describes WAAS as providing navigation service broadly throughout the U.S. National Airspace System rather than only near individual navigation aids. 

No Dedicated Landing Transmitter at Every Airport

Airports can gain vertically guided GNSS approach capability without installing an ILS or GBAS transmitter for each approach.

That can be especially valuable at regional and smaller airports.

Supports Performance-Based Navigation

SBAS is an important enabler of PBN because it improves both navigation accuracy and integrity across wide areas.

Geometric Vertical Guidance

LPV vertical guidance is satellite-derived rather than dependent on a barometric vertical path.

Limitations of SBAS

Availability depends on:

• SBAS coverage
• Satellite geometry
• GNSS health
• Ionospheric conditions
• Receiver capability
• Procedure design
• Airport lighting and infrastructure
• Operational approval

Not every airport within an SBAS service area automatically qualifies for LPV minima equivalent to the lowest CAT I values.

EASA similarly notes that actual LPV minima depend on service performance, aerodrome infrastructure, and procedure design. 

Advantages of GBAS

One Ground Facility Can Support Multiple Runway Ends

This is one of GBAS’s major infrastructure advantages.

The FAA notes that a single GBAS facility can support multiple runway ends rather than requiring individual ILS installations for each one.

Digitally Defined Approach Paths

Because GLS guidance is based on a digitally defined path rather than a physical localizer/glideslope beam, GBAS provides important procedure-design flexibility.

Potential applications can include:

• Different glide-path angles
• Different runway thresholds
• Multiple approaches
• Future advanced terminal procedures

Actual implementation always depends on procedure design, regulatory approval, aircraft capability, and operational authorization.

Reduced ILS-Specific Infrastructure

An ILS normally requires dedicated localizer and glideslope equipment for each equipped runway direction, along with protected critical and sensitive areas.

GBAS can consolidate some of those functions into a common airport system.

Strong Airline Integration

GLS capability is available on various modern transport aircraft configurations.

Boeing training material identifies GLS capability for aircraft including members of the 737 and 787 families, while Airbus supports GLS capabilities across multiple modern aircraft families depending on configuration.

Limitations of GBAS

GBAS requires significant airport-specific infrastructure.

The airport needs:

• Approved reference receivers
• Processing equipment
• VDB transmission capability
• Monitoring
• Power and backup systems
• Maintenance support
• Surveying
• Regulatory approval
• Flight procedure development

Aircraft must also have compatible approved equipment.

Consequently, GBAS cannot provide the geographic scalability of SBAS.

9. Integrity, Redundancy, and Safety

A major engineering lesson from both systems is that navigation performance cannot be measured only by accuracy.

Imagine two systems:

System A is normally accurate to one meter but occasionally produces a 100-meter undetected error.

System B is slightly less accurate but reliably detects unsafe conditions and stops providing approach guidance.

For aviation safety, System B may be far more useful.

That is why augmentation systems incorporate:

• Ground monitoring
• Integrity algorithms
• Fault detection
• Protection calculations
• Alerting
• Redundant infrastructure
• Receiver monitoring
• Service-level determination

GBAS installations use multiple reference receivers partly so that faulty measurements can be identified rather than accepted unquestioningly.

SBAS uses geographically distributed stations partly so that satellite and propagation errors can be evaluated across a large service region.

10. GAST C and GAST D: Understanding Advanced GBAS

GBAS capability is defined through standardized GBAS Approach Service Types, commonly abbreviated GAST.

GAST C

GAST C was designed primarily to support CAT I operations, with certain frameworks also addressing additional CAT II applications.

GAST D

GAST D introduces the performance and monitoring requirements necessary to support the more demanding environment associated with CAT III operations.

Current EASA material explains that GAST C supports the requirements associated with CAT I and certain CAT II applications, while GAST D was designed around CAT III requirements. 

An important qualification is necessary:

A standard being capable of supporting CAT III does not automatically mean every GAST D installation, aircraft, airline, runway, and crew is authorized for CAT III operations.

Operational capability depends on the complete certified and approved system.

That includes:

ground facility + aircraft + procedure + airport + operator + crew + regulatory approval.

11. Advanced Technology and Lesser-Known Facts

1. GBAS Does Not Create a Physical Glide Beam

This is one of the most important engineering differences between GLS and ILS.

ILS guides the aircraft relative to radio patterns transmitted from antennas beside the runway.

GBAS transmits data.

The aircraft uses that information to determine its position relative to a mathematically defined reference path.

2. SBAS Is More Than “Better GPS Accuracy”

The integrity function is central.

SBAS is designed not merely to move the calculated position closer to the aircraft’s true position but also to determine whether that navigation solution is sufficiently trustworthy for a particular operation.

3. GBAS and SBAS Can Coexist on the Same Aircraft

Modern avionics architectures do not necessarily force an operator to choose only one.

A sophisticated aircraft may support:

• ILS
• GLS
• SBAS/LPV
• Basic GNSS
• DME/DME
• IRS
• RNP operations

The aircraft’s navigation and guidance architecture can select or integrate the appropriate source according to the operation and installed capability.

Collins Aerospace, for example, markets modern Multi-Mode Receiver architecture incorporating SBAS capability alongside other landing-system functions.

4. A Single GBAS Can Replace Several Sets of Landing Infrastructure

A significant airport may have multiple runway ends requiring precision guidance.

Traditionally, each ILS-equipped approach direction requires dedicated equipment.

GBAS changes that infrastructure model because one approved system can support multiple published GLS approaches.

5. Neither System Eliminates GNSS Vulnerability

Augmentation improves navigation performance, but it does not make GNSS immune to:

• Jamming
• Spoofing
• Interference
• Satellite outages
• Spectrum problems

The FAA specifically identifies GNSS interference, jamming, and spoofing as issues being addressed in modern satellite-navigation work. 

This is one reason resilient navigation architectures continue to retain alternative sources and contingency strategies.

12. What About Artificial Intelligence?

AI receives significant attention in modern aerospace, but it is important not to exaggerate its role in GBAS or SBAS.

The core safety-critical augmentation functions rely on highly controlled, deterministic, validated algorithms and integrity-monitoring architectures.

AI is not the fundamental technology calculating today’s certified GBAS and SBAS safety-of-life guidance.

Machine learning may eventually contribute to surrounding functions such as:

• Spectrum anomaly detection
• Predictive maintenance
• Network monitoring
• Interference characterization
• Operational analytics

But any integration into safety-critical navigation functions would face stringent certification and assurance requirements.

13. The Future: DFMC, Authentication, and Resilient GNSS

Several developments are likely to shape the next generation of aviation satellite navigation.

Dual-Frequency Multi-Constellation GNSS

Future aviation receivers are moving toward increased use of:

• Multiple frequencies
• Multiple satellite constellations

This can improve resilience and reduce exposure to individual frequency or constellation problems.

ICAO’s current GNSS roadmap includes development of dual-frequency, multi-constellation—DFMC—GNSS, alongside continuing evolution of GBAS and SBAS.

The 2025 fifth edition of ICAO Doc 9849 also added material on DFMC GNSS, performance monitoring, and radio-frequency-interference mitigation.

Authentication

Another future direction is navigation-message authentication.

Authentication can help systems determine whether navigation data genuinely came from the expected source rather than being falsified.

ICAO is developing provisions addressing authentication of future SBAS services as part of broader GNSS-resilience efforts.

Brief Facts

Technology: GNSS augmentation

GBAS Full Name: Ground-Based Augmentation System

SBAS Full Name: Satellite-Based Augmentation System

Main Purpose: Improve GNSS accuracy, integrity, availability, and operational usability for aviation

GBAS Primary Landing Application: GLS

SBAS Primary Approach Application: LPV and other SBAS-supported GNSS operations

GBAS Coverage: Localized around an equipped airport

SBAS Coverage: Large regional service area

Typical GBAS Ground Components: Reference receivers, antennas, processor, integrity monitoring, VHF Data Broadcast transmitter

Typical SBAS Components: Wide-area reference stations, master processing stations, uplink facilities, satellite broadcast segment, compatible aircraft receiver

Manufacturers/Providers: Multiple government, infrastructure, and avionics organizations; Honeywell SmartPath is one operational GBAS example

Typical Aircraft: Commercial transports, business aircraft, and general aviation aircraft depending on installed and approved avionics

Important Dates: WAAS entered U.S. operational service in 2003; the first U.S. operational GBAS approval occurred at Newark in September 2012.

Terminology

GNSS — Global Navigation Satellite System
Satellite-based positioning and timing infrastructure including systems such as GPS and Galileo.

GPS — Global Positioning System
The U.S. GNSS constellation.

GBAS — Ground-Based Augmentation System
Local GNSS augmentation using ground reference receivers and a VHF data link.

SBAS — Satellite-Based Augmentation System
Wide-area GNSS augmentation delivered to users through satellite broadcasts.

GLS — GBAS Landing System
An instrument approach using GBAS-augmented GNSS guidance.

LPV — Localizer Performance with Vertical Guidance
An SBAS-enabled approach line of minima providing angular lateral guidance and geometric vertical guidance.

WAAS — Wide Area Augmentation System
The U.S. SBAS.

EGNOS — European Geostationary Navigation Overlay Service
Europe’s SBAS.

VDB — VHF Data Broadcast
The radio data link used by GBAS to transmit augmentation and approach information to aircraft.

MMR — Multi-Mode Receiver
Aircraft avionics combining several radio/satellite navigation functions in one receiver architecture.

GAST — GBAS Approach Service Type
A classification describing defined GBAS approach-service performance.

Integrity
The degree of trust that can be placed in navigation information, including the capability to provide timely warning when it should not be used.

PBN — Performance-Based Navigation
Navigation based on specified aircraft system performance rather than dependence on particular ground navigation aids.

Pilot’s Perspective

From the pilot’s seat, the most significant advantage of modern augmentation systems is often not that the technology looks revolutionary.

It is that it doesn’t have to.

Modern implementations are intentionally designed to present guidance in familiar ways.

A crew flying GLS may see lateral and vertical deviation indications resembling an ILS.

An SBAS-capable aircraft flying LPV may similarly provide an intuitive stabilized three-dimensional path.

But pilots still need to understand the underlying mode.

The crew must know:

• Which approach is actually loaded
• Which navigation source is providing guidance
• What annunciations confirm the intended mode
• What minima apply
• What downgrade conditions mean
• Whether the aircraft and operator are approved for the procedure
• What action is required after loss of approach capability

Similar-looking displays must never become an excuse for assuming all approach systems are operationally identical.

Maintenance Engineer’s Perspective

For avionics and CNS engineers, GBAS and SBAS highlight the shift from isolated navigation sensors toward interconnected systems.

A fault may involve much more than a single receiver.

Troubleshooting can require understanding:

• GNSS antenna performance
• Receiver configuration
• MMR software
• Navigation database status
• VHF data reception
• Aircraft data buses
• FMS integration
• Flight-guidance interfaces
• Maintenance messages
• Ground-facility status
• Software compatibility
• Regulatory configuration requirements

For GBAS, airport infrastructure adds another complete safety-critical subsystem.

Reference antenna surveying, RF environment, ground processing, integrity monitoring, VDB coverage, power, configuration control, and maintenance procedures all become part of the operational chain.

Common Misconceptions

Misconception 1: “SBAS and GBAS are competitors.”

Not necessarily.

They solve different operational problems and can complement one another.

SBAS provides broad geographic augmentation.

GBAS concentrates augmentation performance around specific airports.

Misconception 2: “LPV is simply satellite ILS.”

The pilot experience can be similar, but the technical architecture and regulatory classification are different.

ILS uses ground-generated radio beams.

LPV uses SBAS-enhanced GNSS positioning and a database-defined procedure.

Misconception 3: “GBAS is GPS transmitted from the airport.”

Incorrect.

The aircraft still receives satellite signals directly.

The GBAS station supplies corrections, integrity information, and approach data that improve the aircraft’s use of those signals.

Misconception 4: “If GNSS is jammed, GBAS fixes it.”

Generally no.

GBAS relies on the ability of both the ground facility and aircraft to receive usable GNSS signals.

Augmentation is not the same as an independent backup navigation system.

Misconception 5: “GAST D automatically means CAT III is available.”

No.

GAST D provides the technical service framework designed for CAT III requirements, but actual CAT III operations require the complete approved combination of infrastructure, aircraft, operator, runway, procedure, and crew qualification.

Operational Lessons Learned

Satellite navigation systems are extraordinarily capable, but their safety comes from layers, not from assuming satellite signals are infallible.

Operational experience with GNSS has reinforced several principles:

• Radio-frequency interference must be treated seriously.
• Integrity monitoring is as important as raw accuracy.
• Flight crews must respond correctly to navigation downgrades.
• Conventional or alternative navigation capability remains important for contingency planning.
• Ground and airborne configurations must be tightly controlled.
• Published procedures and approved databases are part of the safety architecture.

EASA’s European PBN transition policy, for example, still recognizes the importance of retaining conventional navigation capability for contingencies when GNSS or other PBN infrastructure becomes unavailable. 

The larger lesson is simple:

Modern navigation safety is achieved through monitored performance, redundancy, disciplined procedures, and graceful degradation—not through dependence on any single technology.

Main Points

• GBAS and SBAS both augment GNSS but use fundamentally different architectures.
• SBAS operates across large geographic regions; GBAS is localized around an airport.
• SBAS corrections and integrity information are delivered through satellite broadcasts.
• GBAS corrections and approach information are delivered through a local VHF Data Broadcast.
• SBAS commonly enables LPV approaches.
• GBAS enables GLS approaches.
• A single GBAS facility can support multiple approaches and runway ends.
• LPV can provide minima comparable with CAT I ILS in suitable circumstances, but classification and operational approval remain distinct.
• GAST D is designed to support the performance requirements associated with CAT III GBAS applications.
• Both systems depend on GNSS and remain vulnerable to radio-frequency interference.
• Future navigation development includes dual-frequency, multi-constellation GNSS, authentication, and improved interference resilience.
• GBAS and SBAS are complementary parts of the broader transition toward performance-based satellite navigation.

Frequently Asked Questions

1. What is the main difference between GBAS and SBAS?

GBAS provides local GNSS augmentation around an equipped airport, while SBAS provides wide-area augmentation across an extensive geographic region.

2. Which system is used for GLS?

GLS uses GBAS.

The GBAS ground facility sends local corrections, integrity information, and approach-path information to the aircraft.

3. Which system provides LPV approaches?

LPV is primarily enabled by SBAS, such as WAAS in the United States or EGNOS in Europe.

4. Can LPV go as low as an ILS CAT I approach?

At suitably equipped airports and where procedure design permits, LPV minima can reach approximately 200 feet above touchdown, comparable operationally with the lowest typical CAT I decision-altitude range.

Actual published minima must always be used.

5. Can GBAS support CAT III?

GAST D was developed to meet the technical performance requirements associated with CAT III GBAS operations. Actual CAT III capability still depends on the complete approved ground, aircraft, airport, operator, and procedure combination. (

6. Does every airport need its own SBAS station?

No.

That is a major advantage of SBAS.

A regional SBAS network can support appropriately designed procedures at numerous airports within its service area without installing a dedicated augmentation transmitter at every runway.

7. Does every GBAS airport require separate equipment for each runway?

Not in the same way as ILS.

A single GBAS ground facility can support multiple GLS approaches and runway ends. 

8. Is GBAS more accurate than GPS?

GBAS provides local differential corrections and integrity information that enable performance substantially beyond unaided basic GNSS for approved aviation applications.

But operational capability is defined by certified system performance rather than a single accuracy number.

9. Can pilots fly GLS exactly like ILS?

The presentation and basic flying technique may be intentionally similar, but pilots must follow the aircraft manufacturer’s procedures, operator SOPs, published approach, and applicable approvals.

GLS and ILS are technically different systems.

10. Will satellite navigation eventually eliminate ILS?

Satellite augmentation is taking on an increasingly important role, but aviation navigation infrastructure evolves slowly because resilience and contingency capability matter.

Different States, airports, operators, and fleets will maintain different combinations of ILS, GBAS, SBAS, DME, inertial navigation, and other navigation capabilities for many years.

Conclusion

GBAS and SBAS represent two different engineering solutions to one of aviation’s most important navigation challenges:

How can an aircraft turn satellite positioning into navigation information reliable enough for safety-critical operations?

SBAS answers that question on a regional scale.

A network of monitoring stations calculates augmentation information and delivers it through satellites, allowing compatible aircraft to obtain improved navigation performance across enormous areas and enabling applications such as LPV approaches.

GBAS solves the problem locally.

Precisely surveyed receivers at an airport measure GNSS performance, calculate local corrections, monitor integrity, and transmit those corrections together with approach information directly to aircraft. The result is GLS—a satellite-based precision-approach system designed to provide flight crews with familiar, highly accurate landing guidance.

Neither technology should be viewed as simply “better.”

Their architectures reflect different objectives.

SBAS brings high-integrity satellite navigation to entire regions. GBAS brings high-performance satellite landing guidance to individual airports.

Together, they illustrate a major shift in aviation navigation: from following radio beams fixed to the ground toward navigating precisely defined trajectories supported by digitally monitored satellite infrastructure.

The future of precision navigation is therefore not merely about knowing where the aircraft is.

It is about knowing—with certified confidence—where that position can safely be trusted.

Discussion Questions

1. Have you operated, maintained, studied, or trained with GBAS, GLS, SBAS, or LPV?
2. Which aircraft implementation of satellite-based landing guidance have you worked with?
3. What future improvement would you most like to see—DFMC GNSS, greater GBAS deployment, authentication, or stronger interference resilience?
4. Share your operational experience or technical questions below.