Flight Validation Process of RNP APCH Procedures: Thailand Case Study ICAO Asia-Pacific GNSS Seminar Bangkok, Thailand 26 March 2012 Flight Validation Process of RNP APCH Procedures: Thailand Case Study ICAO Asia-Pacific GNSS Seminar Bangkok, Thailand 26 March

Background Objectives of Flight Validation for RNP APCH Requirements Step-by-step process –Pre-flight –In-flight –Post-flight –Reporting Presentation Outline

RNP APCH = RNAV (GNSS) Using GNSS for approach operation For aircraft with RNP 0.3 capability Utilize Aircraft-Based Augmentation System (ABAS) May include Baro-VNAV Background

4 Phuket PBN Implementation

Procedures for Phuket 09 5 Yellow – Current VOR Track Green - PBN Track

Proposes of Flight Validation of RNP APCH –Correctness of Procedure Correctness of Chart Correctness of Navigation Database – Reliability of Navigation System Signal interference –Important GNSS parameters will be automatically recorded Conformity with ground based Navaids (VOR, DME) as necessary – Environmental Conditions Obstacle Clearance thus FLC needs to be conducted during day-time – Flyability Objectives of Flight Validation

Standards –ICAO Doc 9906 Vol 5 and 6 (Flight Validation) –ICAO Doc 8071 (as necessary) Qualification –Pilots and FIS technicians trained on RNAV flight validation and GNSS (ICAO Doc 9906 Vol 6) Equipment –Flight Management System (FMS) Baro-VNAV capability for Baro-VNAV procedures –Flight Inspection System (FIS) –Navigation Database Requirements

FMS – HS-CNS equipped with Pro Line 21 avionics Certified GPS Receiver – TSO 129a is continuously checking the integrity of the GPS position solution through RAIM Fault Detection Capability Requirements: Flight Management System

Automatic Flight Inspection System (AFIS) Fully automated Record archives both as print-out and electronic database Requirements: Flight Inspection System

Activities Initial Validation ATC coordination Weather forecast GNSS service prediction –Number of GPS satellite –Dilution of Precision (DOPs) –RAIM Outage Satellite image of expected flight path (recommended) Assessment of GNSS interference as needed Pre-Flight

Pre-flight: Initial Validation Simulation of Procedure –Using FMS simulator and FIS software to validate the design Reduce risks of error If no error detected, upload to aircraft FMS and FIS

Pre-flight: GNSS Service Prediction

Pre-flight: Satellite Image 13 Yellow – Current VOR Track Green - PBN Track

In- Flight For each RNAV(GNSS) Approach - Fly all segments and holdings - At least one FLC for each LNAV and LNAV/VNAV profiles - At least one FLC for entire missed approach profile - Preferably fly using auto-pilot - Fly final approach segment as designed and at 100 ft below the designed altitude - Identify controlling obstacles - Check obstacle clearance - Assess fly-ability and workloads - Record GNSS data for all legs flown

In- Flight: GNSS Interference As necessary Under scope of flight inspection, not flight validation Look at impact on service interruption RAIM Alert Loss of GNSS Service Interference may not result in full loss of GNSS services

In- Flight: GNSS Interference Importance Parameters Number of Satellites Signal to Noise Ration Dilution of Precision

Activities Data Analysis and Interference Assessment Flight Validation Report Post-Flight

Post-flight: Automated Data Recording

Post-flight: GNSS Interference Assessment Record and analysis of satellite availability, signal-to-noise ratio, and Dilution of Precision (DOPs).

Post-flight: Flight Validation Report

To ensure safety of flight operation, proper flight validation needs to be conducted using: –Proper equipments –Qualified personal –Proven process Summary

Thank you for your attention.