 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A widebody transport air carrier had a malfunction of its warning computer. It declared an emergency and landed en route.
| Attributes | |
| ACN | 226617 |
| Time | |
| Date | 199211 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : orf |
| State Reference | VA |
| Altitude | msl bound lower : 33000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny |
| Operator | common carrier : air carrier |
| Make Model Name | Widebody, Low Wing, 2 Turbojet Eng |
| Navigation In Use | Other Other |
| Flight Phase | cruise other |
| Route In Use | enroute : other oceanic enroute : atlantic |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 420 flight time total : 3600 flight time type : 600 |
| ASRS Report | 226617 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | aircraft equipment problem : critical other anomaly other |
| Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
| Resolutory Action | flight crew : declared emergency flight crew : overcame equipment problem other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
Narrative:
Nov/tue/92, approximately PM20Z, FL330, .79 mach over champ intersection. We had numerous ECAM warnings (alerts) of several different malfunctions with the airplane. System were crosschecked and it was determined to be a faulty alert system. The aircraft suddenly swayed and the autoplt was disconnected. Aircraft yawed again along with stick shaker. Ny was contacted for a return to norfolk, va, our nearest airfield. An emergency was declared due to possible flight control malfunctions and the continuing of the alert messages. Passing through FL250, the warnings ceased. 60 NM from orf at 10000 MSL, a ctlability check was performed. With landing flaps and gear extended, aircraft handled well. Cleaned up, followed by normal uneventful landing at orf. The flight warning computer had failed according to our maintenance people.
Original NASA ASRS Text
Title: A WDB ACR HAD A MALFUNCTION OF ITS WARNING COMPUTER. IT DECLARED AN EMER AND LANDED ENRTE.
Narrative: NOV/TUE/92, APPROX PM20Z, FL330, .79 MACH OVER CHAMP INTXN. WE HAD NUMEROUS ECAM WARNINGS (ALERTS) OF SEVERAL DIFFERENT MALFUNCTIONS WITH THE AIRPLANE. SYS WERE XCHKED AND IT WAS DETERMINED TO BE A FAULTY ALERT SYS. THE ACFT SUDDENLY SWAYED AND THE AUTOPLT WAS DISCONNECTED. ACFT YAWED AGAIN ALONG WITH STICK SHAKER. NY WAS CONTACTED FOR A RETURN TO NORFOLK, VA, OUR NEAREST AIRFIELD. AN EMER WAS DECLARED DUE TO POSSIBLE FLT CTL MALFUNCTIONS AND THE CONTINUING OF THE ALERT MESSAGES. PASSING THROUGH FL250, THE WARNINGS CEASED. 60 NM FROM ORF AT 10000 MSL, A CTLABILITY CHK WAS PERFORMED. WITH LNDG FLAPS AND GEAR EXTENDED, ACFT HANDLED WELL. CLEANED UP, FOLLOWED BY NORMAL UNEVENTFUL LNDG AT ORF. THE FLT WARNING COMPUTER HAD FAILED ACCORDING TO OUR MAINT PEOPLE.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.