Summary of the content on the page No. 1
Honeywell Honeywell Electronics Electronics
Enhanced Ground Proximity Warning
System (EGPWS):
Flight Flight History History Data Data
JJu im Mulkinss
EGPWS Sr. Systems Engineer
Honeywell Aerospace
August 27, 2012
Summary of the content on the page No. 2
EGPWS Flight History Data • EGPWS EGPWS F Flight light History History D Data ata w was as designed designed t to: o: - 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: - Help pp provide data to investig gate Incidents / Accidents Where FDRs do not exist on the aircraft or fail to function • EGPWS does not add much b
Summary of the content on the page No. 3
EGPWS Flight History Data - Limitations • EGPWS EGPWS F Flight light History History D Data: ata: - 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 t
Summary of the content on the page No. 4
EGPWS Units – Class A TAWS • MK MK V V & & MK MK VII VII - 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 Helicop pters File Number 4
Summary of the content on the page No. 5
EGPWS Units – Class B TAWS • KGP560 & KGP860 & MK XXI - (2”W x 4”H x 6”D) - Found Found in in Small business jets Turboprops VFR VFR Helicopters Helicopters • KMH820 KMH820 & & K KMH920 MH920 - 4 MCU (4”W x 7”H x 13”D) - Earlier units are black -Fd Found iin Small business jets Turboprops File Number 5
Summary of the content on the page No. 6
EGPWS Flight History Data (Warning/Caution) • EGPWS records data 20 seconds before and 10 seconds after every EGPWS alert/warning Used to determine a cause of the alert/warningp g and pilot reaction 20 Seconds 10 Seconds Caution Terrain File Number 6
Summary of the content on the page No. 7
EGPWS Flight History Parameters • List of parameters recorded in EGPWS Warning Flight History Data A Aller ert t T Ty yp pe e Te Ter rra raiin n D Da at ta aba bas se e E Elle evat vatiion on Engi Engine ne Tor Torque que D Da at ta a #1 #1 System Operating Time GPS Satellites Visible Engine Torque Data #2 Engine Torque Data #3 Corrected Altitude GPS Satellites Tracked Tactical (Low Altitude) Select Latitude Pitch Angle Longitude Roll Angle Helicopter EGPWS Only Pi Posittiion SSource Glid Glide
Summary of the content on the page No. 8
EGPWS Flight History Data • Does Does not not record record what what is is not not input 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) File Number 8
Summary of the content on the page No. 9
Flight History Retrieval Process • Flight History information is stored in the EGPWS in a specific area of the non-volatile memory • Data Data can can be be downloaded downloaded via via PCMCIA PCMCIA or or CF CF card card - 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 • Decoding Decoding of of encr encrypted pted information information is is
Summary of the content on the page No. 10
Hawker 800 crash at Owatonna MN • NTS SB AAR-11//01, 31 July 2008, – 8 Fatal - CVR, no FDR and none required - Crashed while attemppg ting late ggo-around on runway y 30 • EGPWS issued Bank Angle alert - Aircraft rolled 90 degrees after becoming airborne off rwy end • Flight Flight History History download download performed performed a at t H Honeywell oneywell - Unit functional post-accident - Memory contained 22 seconds of data 20 before Bank Angle alert 2 after Bank Angle alert (then lo
Summary of the content on the page No. 11
Cessna 560 crash at Pueblo, CO • NTS SB AAR-07//02, 16 February 2005 – 8 f fatal - CVR, no FDR and none required - Pueblo was a pp planned fuel stop on cross-countryyg flight - Crashed 4 mi short of airport in freezing rain • EGPWS issued Bank Angle alert - EGPWS EGPWS destroyed destroyed in in impact impact, fire fire - 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 p
Summary of the content on the page No. 12
Honeywell Electronics Non-Volatile Memory (NVM): An Increasinggg Aide in Investigations Jay Eller Air Safety Investigator Honeywell Aerospace August 27, 2012 File Number 12
Summary of the content on the page No. 13
Agenda What Data What is the manufacturer’s intended use of NVM data? is What What can can we we llearn earn ffrom rom data data obtained obtained from from NVM? NVM? Available Airframes What types of equipment What types of airframes and and have NVM data? have NVM data? Equipment Handling of Equipment What at co comp plic cat atio ons s a and d p pre ecaut cautio ons s e exis st t Containing when handling equipment with NVM? NVM File Number 13 13
Summary of the content on the page No. 14
Intended Uses of NVM in Electronics •Mi Mainttenance/T /Trackiking - Logging of failures which require maintenance at next interval. - Logging of exceedances or failures which may require iimmedi diat te att ttenti tion. - Tracking of fleet such as EMS and Fire Fighting. • Trend analy ysis - Engine performance over a period of time. - Aircraft performance over a period of time. - Could Could be be specific specific to to an an altitude, altitude, t temperature, emperature, o or r o other ther
Summary of the content on the page No. 15
Various Levels of Data Available • L Low Fid Fidelit lity D Dat ta: • 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 Medium Fidelity Fidelity Data: Data: • Medium sample rates from 1/sec to 1/minute • Moderate data precision. • W Would ld sh how medi dium range trendi ding wiith h miiniimall abili bility to show immedia
Summary of the content on the page No. 16
Example of Low Fidelity Data Data points are on 4 minute increments. File Number 16 16
Summary of the content on the page No. 17
Example of Medium Fidelity Data Turn made but unable to determine accuracy during the turn. (1 minute data pp) oints) File Number 17 17
Summary of the content on the page No. 18
Example of High Fidelity Data (1Hz Rate) File Number 18 18
Summary of the content on the page No. 19
Example of High Fidelity Data (1Hz Rate) Notice location precision as witnessed during taxi! taxi! File Number 19 19
Summary of the content on the page No. 20
Types of Equipment and Data Fidelity EVXP HUMS FDR Sky Sky Connect EGPWS EGPWS (Air () (Gen Av) Transport) Transport) EPIC APEX Engine Maintenance ACMS Controls System Smart Serv Servo o Radios Low Medium High Increasing Fidelity of Data ACMS = Aircraft Condition Monitoring System File Number 20 20 HUMS = Health and Usage Monitoring System Increasing Ea ase of Datta Retrieva al Somewhat Highly Stra aight Involved Involved Forw ward
