Honeywell EGPWS User Manual

Honeywell Electronics

Enhanced Ground Proximity Warning

Flight History Data

J

s

Jus

System (EGPWS):

im Mulkin

EGPWS Sr. Systems Engineer

Honeywell Aerospace

August 27, 2012

EGPWS Flight History Data

EGPWS Flight History Data was designed to:

p p

pp g

•

- Provide detailed data on EGPWS alerts

 to improve terrain database
 to evaluate the performance of EGPWS algorithms in real-world operation

• maximize CFIT protection

• minimize nuisance alarms

• EGPWS Flight History Data can:

- Hel

 Where FDRs do not exist on the aircraft or fail to function

 But, it wasn’t designed for accident investigation purposes

2

rovide data to investigate Incidents / Accidents

• EGPWS does not add much beyond what FDR provides

File Number

EGPWS Flight History Data - Limitations

EGPWS Flight History Data:

•

- Does NOT record Date & Time

 EGPWS system time (hours:minutes:seconds) powered
 Flight Leg (Leg 1 is most recent flight)

- Is NOT environmentally protected or crashworthy

 The EGPWS can be damaged beyond the ability to provide any data

- Does NOT provide a rapid data rate

 1 sample per second

- Does NOT record data from all sources

 Typically only records source being used
 This may not be the source being used by the pilot in command

3

File Number

EGPWS Units – Class A TAWS

MK V & MK VII

p

p

•

- 2 MCU (2.5”W x 8”H x 13”D)

- Found in

 All Boeing
 Most Airbus
 Large and Medium business jets

• MK VI & MK VIII & MK XXII

- (3”W x 6”H x 10”D)

- Found in

 Medium and Small business jets
 Turboprops
 IFR Helico

4

ters

File Number

EGPWS Units – Class B TAWS

Found in



VFR Helicopters

KMH820 & KMH920

F

• KGP560 & KGP860 & MK XXI

- (2”W x 4”H x 6”D)

-

 Small business jets
 Turboprops

•

- 4 MCU (4”W x 7”H x 13”D)

- Earlier units are black

-

ound in

 Small business jets
 Turboprops

5

File Number

EGPWS Flight History Data (Warning/Caution)

g

gp

• EGPWS records data 20 seconds before and 10

seconds after every EGPWS alert/warning

 Used to determine a cause of the alert/warnin

20 Seconds 10 Seconds

Caution Terrain

and pilot reaction

6

File Number

EGPWS Flight History Parameters

Alert Type

Terrain Database Elevation

Engine Torque Data #1

Positi

Glidesl

• List of parameters recorded in EGPWS Warning Flight

History Data

System Operating Time GPS Satellites Visible

Corrected A l t i t ude GPS Satellit es Tracked

Lati tude Pit ch Angle

Longit ude Roll Angle

on Source

Positi on Uncertai nt y( HFOM ) Localizer Deviati on

Ai r speed Display Range #1

True Air spe ed Displ a y Range #2

Gr ound Spee d Terr ain Display Enabl ed # 1

Mi ni m um O per at i ng Speed Terrai n Displ ay Enabl ed #2

Barome t r ic Altitude ( Uncor r e ct ed) Landing Gear Down

Geom e t r ic Altitude Landing Flaps Sel ec t ed

Geom e t r i c A lti tude VFOM Terr ai n Awareness & TCF Inhibit

GPS Alt itude Audio Inhibit

GPS VFOM Body AOA

Radio A ltitude Longit udinal Accel er a t i on

Alti tude Rate Normal A cce l er a t ion

Magneti c Track Inert i al Vert ical A ccel er at i on

True Tr ac k Filter ed She ar /Total Shear

True Heading Stati c A i r Temperat ure

ope Deviation

Engine Torque Dat a #2
Engine Torque Dat a #3

Tacti cal ( Low A l t i t ude) Sel ect

Helicopter EGPWS Only

7

File Number

EGPWS Flight History Data

Does not record what is not input

•

- For example, no radio altitude on KGP or KMH Class B units

• Data that is invalid is noted as such

- For example, glideslope deviation when not ILS tuned

• Data is recorded even when manually inhibited by pilot

• Data can be exported to Excel spreadsheet (.xls file)

- Excel format facilitates graphing of data

• Data can be superimposed over maps/chart (KML)

8

File Number

Flight History Retrieval Process

Data can be downloaded via PCMCIA or CF card

Decoding of encrypted information is done by Hone

ell

If unit is damaged:



Honeywell can accept data directly from chip reader

• Flight History information is stored in the EGPWS in a

specific area of the non-volatile memory

•

- Card must be programmed with special instruction file

- Process similar to terrain database upload, requires < 5 minutes

- Cards available upon request from Honeywell Engineering

- Data is encrypted

•

using proprietary tools, tools are not distributed

•

- Circuit boards can be placed in donor units or fixtures

- Memory chips can be removed and data retrieved via chip reader

 Occasionally memory chips are damaged and unreadable

9

yw

File Number

Hawker 800 crash at Owatonna MN

p

pg g

y

Flight History download performed at Honeywell

Speed increase on runway

• NTSB AAR-11/01, 31 July 2008, – 8 Fatal

- CVR, no FDR and none required

- Crashed while attem

ting late go-around on runway 30

• EGPWS issued Bank Angle alert

- Aircraft rolled 90 degrees after becoming airborne off rwy end

•

- Unit functional post-accident

- Memory contained 22 seconds of data

 20 before Bank Angle alert
 2 after Bank Angle alert (then loss of power)

• Data used to confirm:

- Flaps down before landing

- Flaps retracted after landing

-

- 8 knot tailwind

10

File Number

Cessna 560 crash at Pueblo, CO

p

pp

yg

EGPWS destroyed in impact, fire

• NTSB AAR-07/02, 16 February 2005 – 8 fatal

- CVR, no FDR and none required

- Pueblo was a

lanned fuel stop on cross-country flight

- Crashed 4 mi short of airport in freezing rain

• EGPWS issued Bank Angle alert

-

- Circuit cards returned to Honeywell for possible analysis

• 1 of 2 Flight History data chips broken, data irretrievable

- Manual process used on surviving chip

- 30 seconds of partial data set recovered

 Altitude, descent rate
 Pitch, roll
 Ground speed, ground track angle

- Data correlated to radar data

11

File Number

Honeywell Electronics

g

gg

Non-Volatile Memory (NVM):

An Increasin

Air Safety Investigator

Honeywell Aerospace

August 27, 2012

Aide in Investigations

Jay Eller

12

File Number

Agenda

What can we learn from data obtained from NVM?

and

cations and precautions exist

at co p cat o s a d p ecaut o s e st

What Data

What is the manufacturer’s intended use of NVM data?

is

Available

Airframes

What types of equipment What types of airframes

have NVM data? have NVM data?

Equipment

Handling

What compli

when handling equipment with NVM?

13

13

of
Equipment
Containing

NVM

File Number

Intended Uses of NVM in Electronics

Maint

/T

ki

i

y

Could be specific to an altitude, temperature, or other

-

Capturing detailed data when a particular event has occurred

•

enance

rac

ng

- Logging of failures which require maintenance at next interval.

- Logging of exceedances or failures which may require

mmediate attention.

- Tracking of fleet such as EMS and Fire Fighting.

• Trend analysis

- Engine performance over a period of time.

- Aircraft performance over a period of time.

-

operational condition.

• Trouble Shooting

- Event could be pilot initiated (press of a button) or a

predetermined scenario.

All Could be Beneficial in Accident Investigation

14

14

.

File Number

Various Levels of Data Available

Fidelity Dat

•

Medium Fidelity Data:

W

bili

•

High Fidelity Data:

•

Good indication of immediate behaviors and performance just

•Low

a:

• Slow sample rates (greater than 1 sample per minute)

• Minimal data precision (ie: Latitude, Longitude, altitude, etc)

• Would show long term trending with little inability to show

immediate behaviors/signatures.

• Medium sample rates from 1/sec to 1/minute

• Moderate data precision.

•

ould show medium range trending with minimal a

show immediate behaviors/signatures

ty to

• High frequency rate of data capture (1Hz or faster)

• High data precision.

prior to the accident.

15

15

File Number

Example of Low Fidelity Data

16

16

Data points are on 4
minute increments.

File Number