Guidance material. Performance assessment of pilot response to Enhanced Ground Proximity Warning System (EGPWS)

Similar documents
Advisory Circular. Regulations for Terrain Awareness Warning System

KGP 560. Enhanced Ground Proximity Warning System for General Aviation SEAMLESS SAFETY INTEGRATION THROUGH IHAS

Approach-and-Landing Briefing Note Response to GPWS Pull-Up Maneuver Training

ADVISORY CIRCULAR FOR AIR OPERATORS

COPYRIGHT NOTICE Copyright 2010 Honeywell International Inc. All rights reserved. All marks are owned by their respective companies.

Research on Controlled Flight Into Terrain Risk Analysis Based on Bow-tie Model and WQAR Data

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Technical Standard Order

Product Description. SmartRunway and SmartLanding. functions of the. Enhanced Ground Proximity Warning System

REPORT SERIOUS INCIDENT

Civil Aviation Department

March 2016 Safety Meeting

Runway Incursion Preventive measures at aircraft level

AIRBUS FlyByWire How it really works

Available Technologies. Session 4 Presentation 1

BUSINESS AND GENERAL AVIATION RELOADABLE CUSTOMER DEFINITIONS (RCD) WORKSHEET FOR SmartRunwayTM and SmartLandingTM

CHAPTER 7 AEROPLANE COMMUNICATION AND NAVIGATION EQUIPMENT

Available Technologies. Asia / Pacific Regional Runway Safety Seminar Session 4

ILS APPROACH WITH B737/A320

CFIT-Procedure Design Considerations. Use of VNAV on Conventional. Non-Precision Approach Procedures

The Board concluded its investigation and released report A11H0002 on 25 March 2014.

Minimum Safe. Federal Aviation Administration Altitude Warning. Presented to: Pan American Aviation Safety Summit; Sao Paulo, Brazil

Advisory Circular. Flight Deck Automation Policy and Manual Flying in Operations and Training

Implementation of Terrain Awareness and Warning System (TAWS) Final Report to CAST. Hop Potter, AFS-210,

Approach Specifications

Technical Standard Order

AREA NAVIGATION RNAV- MANAGEMENT

ICAO Air Navigation Commission (ANC) - Industry. Third Meeting on the Global Aviation Safety Plan. ICAO Headquarters, Montreal.

Instrument Proficiency Check Flight Record

Khartoum. Close Call in. causalfactors. Confusion reigned when an A321 was flown below minimums in a sandstorm.

Go-Around Procedure. Flight Instructor Seminar / Miami, May 24 th and 25 th, 2011

AVIATION INVESTIGATION REPORT A00Q0116 RISK OF COLLISION

Dive-and-Drive Dangers

ERRONEOUS SAFETY 28 AERO DAVID CARBAUGH CHIEF PILOT FLIGHT OPERATIONS SAFETY BOEING COMMERCIAL AIRPLANES. Third-Quarter 2003 July

Breaking the Accident Chain

FINAL REPORT BOEING B777, REGISTRATION 9V-SWH LOSS OF SEPARATION EVENT 3 JULY 2014

APRAST outputs for RASG consideration and approval PROGRESS UPDATE ON APRAST SAFETY ENHANCEMENT INITIATIVE CFIT/1. (Presented by CFIT Sub-Group)

OPERATIONS MANUAL PART A

OPERATIONS CIRCULAR 01/2012. Subject: HEAD-UP DISPLAYS (HUD) AND ENHANCED VISION SYSTEMS (EVS)

MetroAir Virtual Airlines

CASCADE OPERATIONAL FOCUS GROUP (OFG)

AC DATE: 5/22/00. Airworthiness Criteria for the Installation Approval of a Terrain Awareness and Warning System (TAWS) for Part 25 Airplanes

del Airbus en el mundo de la

Non Precision Approach (NPA) Status and Evolution

Flight Operations Briefing Notes

AVIATION INVESTIGATION REPORT A02P0290 GEAR-UP LANDING

TABLE OF CONTENTS 2 REVISIONS - ALL SHEETS ARE SAME REVISION STATUS SH REV DESCRIPTION DATE APPROVE

Flight Evaluation Schedule For GPS IFR Approval Primary Means Enroute, Terminal and Non-Precision Approach

Pilot RVSM Training Guidance Material

IATA Air Carrier Self Audit Checklist Analysis Questionnaire

Preventing Runway Excursions. Technical solutions From the Design and Manufacturing Sector

TAWS Terrain Awareness and Warning Systems

Glass Cockpits in General Aviation Aircraft. Consequences for training and simulators. Fred Abbink

Global Aviation Data Management (GADM) Jehad Faqir Head of Safety & Flight Operations IATA- MENA

Safety Enhancement SE ASA Design Virtual Day-VMC Displays

TCAS Pilot training issues

Office of Research and Engineering Safety Study Report: Introduction of Glass Cockpit Avionics into Light Aircraft Study Overview Joseph Kolly

TABLE OF CONTENTS 2 REVISIONS - ALL SHEETS ARE SAME REVISION STATUS SH REV DESCRIPTION DATE APPROVE

Navigation event 28 km north-west of Sydney Airport, NSW 11 January 2007

National Transportation Safety Board Aviation Incident Final Report

AUTOMATION MANAGEMENT STANDARD OPERATING PROCEDURES

Overview of ACAS II / TCAS II

AVIATION OCCURRENCE REPORT A98W0216 LOSS OF SEPARATION

FLIGHT OPERATIONS PANEL (FLTOPSP)

Garrecht TRX 1500 Traffic-Sensor

Air Navigation Bureau ICAO Headquarters, Montreal

IAGSA Survey Contract Annex

Advanced Transition Training

INVESTIGATION REPORT. Incident to ATR registered F-GVZG on 11 September 2011 at Marseille

GENERAL INFORMATION Aircraft #1 Aircraft #2

Flight Testing the Wake Encounter Avoidance and Advisory system: First results

Front Line Managers (FLMs) and Airline Pilots Training for Operational Evaluation! of enhanced Final Approach Runway Occupancy Signal (efaros) at DFW!

Sometimes a government

SUPPLEMENT S06. Transport Canada Approved Flight Manual Supplement For GARMIN 400W/500W SERIES GPS WASS NAVIGATION SYSTEM

AIRCRAFT INCIDENT REPORT

Challenges in Complex Procedure Design Validation

Navigation Systems. 1. The Chart Supplement provides a listing of available VOR receiver ground checkpoints and VOTs (VOR receiver test facilities).

Loss Of Control Inflight. An Approach to Enhance Safety

RNP 2 JOB AID REQUEST TO CONDUCT RNP 2 OPERATIONS

ACAS Training for Pilots

AIRCRAFT SERVICE CHANGE

GUERNSEY ADVISORY CIRCULARS. (GACs) UPSET PREVENTION AND RECOVERY TRAINING GAC 121/135-2

RNP AR and Air Traffic Management

Aircraft Accident Investigation Bureau of Myanmar

Newcastle Airport. 36 years

SECURITY OVERSIGHT AGENCY June 2017 ALL WEATHER (CAT II, CAT III AND LOW VISIBILITY) OPERATIONS

Safety Syllabus. VFR into IMC

STABLE APPROACHES. Captain Alan Stealey DSVP Flight Operations Emirates Airline

ATM 4 Airspace & Procedure Design

Flight Operations Briefing Notes

MINIMUM FLIGHT ALTITUDES

All-Weather Operations Training Programme

AIR LAW AND ATC PROCEDURES

RNP In Daily Operations

SERIOUS INCIDENT. Aircraft Type and Registration: Boeing 737-8F2, TC-JKF. No & Type of Engines: 2 CFM 56-7B22 turbofan engines

Flight Evaluation and Validation of RNP AR/SAAAR Instrument Flight Procedures

CAR Section II Series I Part VIII is proposed to be amended. The proposed amendments are shown in subsequent affect paragraphs.

Any queries about the content of the attached document should be addressed to: ICAO EUR/NAT Office:

National Transportation Safety Board Aviation Incident Final Report

ONE-ENGINE INOPERATIVE FLIGHT

Transcription:

Guidance material Performance assessment of pilot response to Enhanced Ground Proximity Warning System (EGPWS) 1 Edition 1-2019

Disclaimer DISCLAIMER. The information contained in this document is based on data collected, and the analysis performed by, Honeywell in respect to the performance of the EGPWS technology and has not been independently verified and assessed by the International Air Transport Association (IATA). The information contained in this document is subject to constant review in the light of changing government and industry requirements and regulations and also subject to change in view of evolving technological capabilities. No subscriber or other reader should act on the basis of any such information without referring to applicable laws and regulations and without taking appropriate professional advice. Although every effort has been made to ensure the relevance and accuracy of information, IATA, Honeywell, and any other contributors to this publication shall not be held responsible for any loss or damage caused by errors, omissions, misprints or misinterpretation of the contents hereof. Furthermore, IATA, Honeywell, and any other contributors to this publication expressly disclaim any and all liability to any person or entity in respect of anything done or omitted, and the consequences of anything done or omitted, by any such person or entity in reliance on the contents of this publication. The findings, recommendations and opinions expressed in this publication do not necessarily reflect the opinion of IATA. The mention of specific companies, products brands or services in this publication does not imply that they are endorsed or recommended by IATA and Honeywell in preference to others of a similar nature which are not mentioned. IATA expressly disclaims any suggestion that it endorses any particular product, brand or service. International Air Transport Association and Honeywell, 2019. All Rights Reserved. No part of this publication may be reproduced, recast, reformatted or transmitted in any form by any means, electronic or mechanical, including photocopying, recording or any information storage and retrieval system, without the prior written permission from: Senior Vice President Safety & Flight Operations International Air Transport Association 800 Place Victoria, P.O. Box 113 Montreal, Quebec CANADA H4Z 1M1 2 Edition 1-2019

CONTENTS Abbreviations and Acronyms... 4 Introduction... 5 EGPWS descriptions... 5 EGPWS evolvement... 6 Terrain / obstacle / runway database updates... 6 Response to an EGPWS alert activation... 7 Reporting... 7 Conclusions... 8 Recommendations... 8 Supporting information... 9 EGPWS statistics... 9 Mode 1 (Excessive Descent Rate)... 9 Mode 2 (Excessive Terrain Closure Rate)... 9 Mode 3 (Descent After Takeoff)... 9 Mode 4 (Insufficient Terrain Clearance)... 9 Mode 5 (Descent Below Glideslope)... 10 Terrain Awareness Alerting and Terrain Clearance Floor (TCF) Functions... 10 Terrain Awareness Display (TAD)... 11 Pilot s response... 11 Aircraft fitted with Honeywell EGPWS... 13 EGPWS algorithm enhancements in software version -218... 133 Appendix A... 15 3 Edition 1-2019

Abbreviations and Acronyms AGL AFM ASR ATC CFIT EFIS EGWPS FDM GA GPS GPWS HFOM HDOP IATA IMC MFD MOR ND OEM PLI PNF RFCF ROC SOPs TAWS TAD TCF TO VDOP VFOM VMC Above Ground Level Airplane Flight Manual Air Safety Report Air Traffic Control Controlled Flight into Terrain Electronic Flight Instrument System Enhanced Ground Proximity Warning System Flight Data Monitoring Go Around Global Positioning System Ground Proximity Warning System Horizontal Figures of Merit Horizontal Dilution of Precision International Air Transport Association Instrument Meteorological Conditions Multi-Function Display Mandatory Occurrence Reporting Navigation Display Original Equipment Manufacturer Pitch Limit Indicators Pilot Not Flying Runway Field Clearance Floor Required Obstacle Clearance Standard Operating Procedures Terrain Awareness and Warning System Terrain Awareness and Alerting Display Terrain Clearance Floor Take off Vertical Dilution of Precision Vertical Figures of Merit Visual Meteorological Conditions 4 Edition 1-2019

Introduction Historic accident data shows that CFIT has been a major cause of fatal accidents. In response to this hazard, the industry developed and implemented the Ground Proximity Warning System (GPWS) which provides warnings to pilots when the aircraft is in potentially hazardous proximity to terrain. This system was introduced in the 1970s to reduce the high number of Controlled Flight into Terrain (CFIT) accidents and incidents. The functionality of GPWS was limited. To overcome the limitations of GPWS, a new technology Enhanced Ground Proximity Warning System (EGWPS), also known as Terrain Awareness and Warning System (TAWS), was introduced; which combines a worldwide digital terrain database with an accurate navigation system, ideally using the Global Positioning System (GPS). EGPWS is not a solution for stopping CFIT accidents but it can help interrupt a flight path which is likely to lead to an accident. EGPWS or TAWS, provides a warning in advance of steeply rising ground and extends the warning area almost to the runway threshold, overcoming the limitations of GPWS. EGPWS descriptions The EGPWS is a Terrain Awareness and Alerting system providing terrain alerting and display functions with additional features. The EGPWS uses aircraft inputs including geographic position, attitude, altitude, ground speed, vertical speed and glideslope deviation. These are used with internal terrain, obstacles, and airport databases to predict a potential conflict between the aircraft flight path and terrain or an obstacle. A terrain or obstacle conflict results in the EGPWS providing a visual and audio caution or warning alert. The EGPWS contains the following databases: Terrain database o A worldwide terrain database of varying degrees of resolutions Obstacle database o Known obstacles 100 feet or greater in height Runway database o Runways 3500 feet or longer in length (2000 feet or longer in some EGPWS models) Additionally, the EGPWS provides alerts for excessive glideslope deviation, too low with flaps or gear not in landing configuration, and optionally provides bank angle and altitude callouts based on system configuration settings. Detection of severe windshear conditions is also provided for selected aircraft types when enabled. The EGPWS incorporates the functions of the basic GPWS. This includes the following alerting modes: Mode 1: Excessive Descent Rate Mode 2: Excessive Terrain Closure Rate Mode 3: Descent After Takeoff Mode 4: Unsafe Terrain Clearance Mode 5: Descent Below Glideslope Mode 6: Advisory Callouts (Optional) Mode 7: Reactive Windshear (Optional) 5 Edition 1-2019

The EGPWS includes several other enhanced features: Terrain Alerting algorithms continuously compute terrain clearance envelopes ahead of the aircraft. If the boundaries of these envelopes conflict with terrain/obstacle elevation data in the terrain/obstacle database, then alerts are issued. Two envelopes are computed, one corresponding to a caution alert level and the other to a warning alert level. Terrain Display provides a graphic display of the surrounding terrain and obstacles on a dedicated weather radar indicator or, on compatible Electronic Flight Instrument System (EFIS), electronic Navigation Display (ND) or Multi-Function Display (MFD). Based on the aircraft s position and the internal database, the terrain topography is presented on the system display for additional situational awareness. Terrain Clearance Floor (TCF) creates an increasing terrain clearance envelope around a runway. TCF alerts are based on current aircraft location, nearest runway position and radio altitude. TCF complements existing Mode 4 by providing an alert based on insufficient terrain clearance even when in landing configuration. Runway Field Clearance Floor (RFCF) is similar to the TCF feature except that RFCF is based on height above the runway elevation instead of radio altitude. Geometric Altitude is a computed aircraft altitude designed to help ensure optimal operation of the EGPWS functions through all phases of flight and atmospheric conditions. Geometric Altitude uses an improved pressure altitude calculation, GPS altitude, radio altitude, and terrain and runway elevation data to reduce errors potentially induced in corrected barometric altitude by temperature extremes, non-standard altitude conditions, and altimeter miss-sets. Geometric Altitude also allows continuous EGPWS operations in QFE environments without custom inputs or special operational procedures. EGPWS evolvement The unreliability and limitation of the first generation GPWS was cited where GPWS was plagued by false and nuisance warnings, causing pilots to distrust the equipment when actual hazardous conditions existed. Subsequently, generations of GPWS have become more reliable. A number of studies have examined pilot response times to GPWS alerts and indicate that alerts and warnings in the final 5 seconds of a flight would not give sufficient time for the flight crew and aircraft to respond effectively. This issue has been addressed with EGPWS, which provides the pilot with a greater time to respond to an alert and take avoiding action. Terrain / obstacle / runway database updates For the system to work as designed, aircraft operators must ensure the accuracy of terrain, runways, and surrounding obstacles. The Terrain/Obstacle/Runway database applicable to the Honeywell EGPWS is released every 56 days and the release schedule can be found at https://ads.honeywell.com. Appendix A to this report presents an example of the Terrain Database Schedule for 2018, 2019 and 2020. 6 Edition 1-2019

Response to an EGPWS alert activation Appropriate response procedures for flight crew are determined by the aircraft type performance capability. They must be clearly defined by operators and defined in an applicable airplane flight manual (AFM). In the case of a warning, flight crew should follow the warnings without hesitation as soon as triggered. During night or in instrument meteorological conditions (IMC), apply the procedures immediately in response to caution and warning level alerts. Do not delay reaction for diagnosis. During daylight or in visual meteorological conditions (VMC), take positive corrective action until the alert stops or a safe trajectory is ensured. Following an EGPWS alert, flight crew should control the aircraft flight path with immediate maximum Required Obstacle Clearance (ROC) and maximum thrust to clear the obstacles threatening the flight. For detailed Standard Operating Procedures (SOP s) consult the respective Original Equipment Manufacturer (OEM) flight operations documentation Warning level alert Aggressively position throttles for maximum rated thrust. Apply maximum available power as determined by emergency need. The pilot not flying (PNF) should set power and ensure that takeoff / go-around (TO/GA) power and modes are set. If engaged, disengage the autopilot and smoothly but aggressively increase pitch toward stick shaker or Pitch Limit Indicators (PLI) to obtain maximum climb performance. Continue climbing until the warning is eliminated and safe flight is assured. Advise ATC of situation. NOTE: Climbing is the only recommended response unless operating in visual conditions and/or pilot determines, based on all available information, that turning in addition to the climbing is the safest course of action. Follow established operating procedures. Navigation must not be based on the use of the Terrain Awareness and Alerting Display (TAD). Caution level alert Take immediate corrective action as necessary to recover safe terrain clearance. Advise ATC of situation as necessary. Reporting A written Air Safety Report (ASR) should be submitted to the appropriate Air Traffic Control Unit and the authority in accordance with the mandatory occurrence reporting (MOR) requirements, whenever the aircraft flight path has been modified in response to an EGPWS alert. This data together with the operational data downloaded from an aircraft s on-board computer at the end of every flight (FDM) can be collected, analyzed and used by the operator, to identify and discover underlying issues that have the potential to negatively affect aviation safety and to enable operators to take appropriate action to mitigate. Aircraft Operators with a flight data monitoring (FDM) process, should have an automatic alerting system for any recording which contains such an occurrence, and this should support an investigation 7 Edition 1-2019

already initiated by receipt of an ASR or prompt the commencement of a new investigation and/or should reinforce the lesson with dedicated simulator training sessions. Conclusions The introduction of terrain awareness technologies, such as the EGPWS / TAWS, have directly or indirectly, contributed to a reduction in the number of CFIT accidents. With such technology, the flight crew gets improved situational awareness and is able to counter act potential CFIT accidents sooner. For the system to work as designed, aircraft operators should keep the software and terrain/obstacle/runway database up to date. The proper and timely responses to EGPWS warnings can result in significantly reducing the risk of a CFIT accident. To achieve this objective, the pilot should demonstrate taking the correct action and perform appropriate recovery maneuvers needed in response to a caution and warning. Recommendations Operators are encouraged to o o o o o o Assess and consider equipping their aircraft with EGPWS equipment; Ensure the use of GPS that feeds direct to EGPWS; Put in place a training program to ensure flight crew can respond effectively to EGPWS cautions and warnings; are aware of factors that can reduce effectiveness of EGPWS and are trained to mitigate the effects of EGPWS degradation; Have procedures in place to ensure that EGPWS software and terrain, runway and obstacle databases are current and continually updated; Have procedures in place to ensure that EGPWS equipment remains activated and serviceable at all times; Include CFIT avoidance maneuvers in recurrent training. 8 Edition 1-2019

Supporting information EGPWS statistics This section presents analysis using Honeywell flight history data recorded in the EGPWS, covering over 18 million flights from 1997 till mid-2012 it is believed that the information to still be valid today. Below is a summary of findings and conclusions reached by Honeywell following its review of the data recorded. Please note that the data and resulting findings and conclusions have not been independently assessed and vetted by IATA. Mode 1 (Excessive Descent Rate) 89% of Mode 1 alerts occurred below 500 ft radio altitude, and 67% below 200 ft radio altitude. Mode 2 (Excessive Terrain Closure Rate) 98% of Mode 2 alerts occurred on airplanes with EGPWS software version older than -217 (or Boeing P/N 965-1690-050 or Airbus P/N 965-1676-001) or without GPS or without Geometric Altitude. In other words, GPS equipped airplanes with EGPWS a software version newer than -218 and Geometric Altitude have significantly less risk of activating unwanted Mode 2 alerts. 1.2 1 Chance of Receiving Mode 2 Alerts Likelihood 0.8 0.6 0.4 0.2 0-210 & older or w/o GPS or w/o Geometric Altitude -212 ~ -217 w/ GPS and Geometric Altitude -218 & newer w/ GPS and Geometric Altitude Mode 3 (Descent After Takeoff) The majority of Mode 3 alerts were occurring during a flight in a traffic pattern such as a training flight. However, some Mode 3 alerts were induced by departure procedures. Mode 4 (Insufficient Terrain Clearance) 57% of Mode 4 alerts were false alerts caused by external faults. The primary cause of the false alerts was faulty radio altimeter (false tracking). 9 Edition 1-2019

Mode 5 (Descent Below Glideslope) 34% of Mode 5 glideslope alerts occurred below 100 ft radio altitude. There were a large number of cases where pilots were ducking under the glideslope below 100 ft. Glideslope alerts occurring at higher altitude were often triggered while maneuvering to intercept the localizer below 1000 ft. Terrain Awareness Alerting and Terrain Clearance Floor (TCF) Functions Some causes of Terrain Awareness alerting and TCF/ Runway Field Clearance Floor (RFCF) functions are shown in the figure below. Causes of Terrain Awareness Alerts 2% 1% 1% 3% 3% 5% 7% 9% 12% 13% 44% Runway not in Database FMS Map Shift Maneuvering close to terrain in visual flight QFE w/o Geometric Altitude Insufficient Terrain Data Resolution Terrain Database Error GPS Anomaly Runway Database Error Premature descent / Flight toward terrain or obstacle Others Altimeter Error Majority of the alerts were caused by external signal faults (e.g., FMS map shift or altimeter error) and terrain/obstacle/runway databases. Nearly a half of Terrain Awareness and TCF/RFCF alerts were caused by not having a destination runway in the database. This often meant the latest terrain/runway database was not installed (the database was not kept up-to-date in the EGPWS). 10 Edition 1-2019

Terrain Awareness Display (TAD) A terrain awareness display had not been selected prior to terrain awareness alerts in 65% of the cases. 2.2% 32.6% 65.2% None Selected One Side Selected Both Sides Selected Pilot s response During EGPWS alert events that pilots responded to, their response time is shown in figures below. For this analysis, a pilot s response time was the time it took for the aircraft pitch to increase more than 1.4 after an alert due to limited availability of parameters that can be used to measure pilot s response in the EGPWS flight history database. Data collected suggests that pilot s response time is very similar regardless of EGPWS alert types or alert level (caution vs. warning). For that reason, statistics have been aggregated in the diagrams below. Frequency Mode 1 (Caution & Warning) 140 120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 9 10 More Response Time (sec) 11 Edition 1-2019

Mode 2 & Terrain Awareness (Caution & Warning) 400 350 300 Frequency 250 200 150 100 50 0 1 2 3 4 5 6 7 8 9 10 More Response Time (sec) Mode 4 & TCF (Caution) Frequency 100 90 80 70 60 50 40 30 20 10 0 1 2 3 4 5 6 7 8 9 10 More Response Time (sec) 12 Edition 1-2019

Aircraft fitted with Honeywell EGPWS The number of commercial jets and turboprop aircraft fitted with Honeywell EGPWS could not be reliably determined. Honeywell estimates that a majority of western built commercial jets and turbo prop airplanes are equipped with Honeywell EGPWS. EGPWS algorithm enhancements in software version -218 Major enhancements were introduced in EGPWS software version -218, which was released in 2003. The Federal Aviation Administration (FAA) issued a Special Airworthiness Information Bulletin (NM-15-11) advising operators of potential safety enhancements made available in -218 software. Honeywell followed up with a detailed Service Information Letter (SIL D201504000056), available at the MyAerospace portal under the Technical Services tab. For more details, please refer to Honeywell SIL D201504000056. The following enhancements are available in these software versions: MK V software version -218-218 and later MK V (Airbus) software version -002 and later MK V (Boeing) software version -051 and later MK VII software version -218-218 and later MK VI software version -022 and later MK VIII software version -022 and later Cessna Sovereign Primus Epic Phase 5.0 and later Dassault Primus Epic EASy II In previous software versions, the Terrain Clearance Floor (TCF) envelope begins between 0.5 and 1.0 nautical mile from the runway threshold, and increases at 100 feet per nautical mile. An enhancement was made to allow TCF envelope to begin 0.25 nautical mile from the runway threshold, and increase at 200 feet per nautical mile for the first mile, providing earlier alerting in landing short scenarios. One such scenario is discussed in FAA SAIB NM-15-11. In previous software versions, the Runway Field Clearance Floor (RFCF) envelope begins 1.0 nautical mile from the runway threshold. An enhancement was made to allow RFCF envelope to begin 0.5 nautical mile from the runway threshold, providing earlier alerting in landing short scenarios. Compared to previous software versions, the look-ahead distance for the terrain awareness algorithm was increased by 12.5%. In 25% of accidents studied, this would result in earlier terrain alerting. In previous software versions, terrain near the airport less than 400 feet above the runway was excluded from the alerting algorithm. An enhancement was made, if runway and terrain quality allow, reducing this limit to terrain 200 feet above the runway, providing improved terrain alerting on final approach. Improved the radio altitude reasonable algorithm to further reduce nuisance Mode 2 and Mode 4 alerts when radio altitude inputs are providing a falsely low indication. To make GPWS Mode 2 compatible with radar vectoring 1000 feet above terrain, the Mode 2 algorithm maximum height was limited to 950 feet AGL, and 789 feet AGL when within 10 nautical miles of a runway in the database. 13 Edition 1-2019

To reduce GPWS Mode 4 nuisance alerts during final approach, the Mode 4A algorithm maximum height was limited to 500 feet Above Ground Level (AGL), and the Mode 4B algorithm maximum height was limited to 245 feet AGL. Many of the algorithm enhancements mentioned above require the EGPWS to receive GPS input of various signals, including latitude, longitude, altitude, Vertical Figures of Merit (VFOM), Horizontal Figures of Merit (HFOM), Vertical Dilution of Precision (VDOP) and Horizontal Dilution of Precision (HDOP). To ensure optimal performance of the EGPWS, GPS input of these signals should be provided from GPS that meet or exceed TSO- C129a. For more information on GPS as an acceptable source for EGPWS, please refer to Honeywell EGPWS specifications. 14 Edition 1-2019

Appendix A An example of the Terrain Database Schedule for 2018 2020, the schedule is the following: 15 Edition 1-2019