Operational Need Analysis
When considering whether to implement a GBAS in a specific airport, it is important to consider how the GBAS will be used within the existing Air Traffic Management (ATM) environment and the benefits that it will deliver to the ATM/ANS provider and/or the airport operator. In order to define operational requirements, it is needed to perform a deep analysis of the current context and operational needs. The analysis should take into consideration of the planned GBAS CONOPS, as well as any potential amendment in CONOPS to be developed in the future.
The following keypoints and considerations might be taken into account during the analysis:
Current approach services, including:
- Objectives
- Measures of effectiveness
- Operational policies and constraints
- Current modes of operation
- Existing support environment
- Reasons to change or supplement current aproach services with GBAS
- Proposed or expected GBAS services, including:
- Objectives
- Measures of effectiveness
- Operational policies and constraints
- Proposed modes of operation
- Integration issues with the existing ATM infrastructure
- Operational use cases
- Potential operational, safety and organisational impacts associated with implementing a GBAS
- Expected improvements, disadvantages and limitations of implementing a GBAS, and alternative technologies
- Overlay of future GBAS procedures with existing ILS or partial overlay with RNP approach procedures
- Alignment with the Navigation Strategy for the State
- Airspace users fleet capabilities and demands
- Level of performance/service that GBAS should achieve
- Impact on existing ATS procedures
- Different modes of operation for the GBAS
- Effect on staff and new capabilities needed
- New training required for staff
- Local limitations, including:
- Aircraft equipment rates
- Technology evolution
- Ionospheric environment
- Site consideration
- Support capability
- Alternative technologies that can accomplish the desired capability
