37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 283017 |
Time | |
Date | 199409 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : cae |
State Reference | SC |
Altitude | msl bound lower : 37000 msl bound upper : 37000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zjx |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : atp |
Experience | flight time last 90 days : 225 flight time total : 6800 flight time type : 4200 |
ASRS Report | 283017 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 18500 flight time type : 3800 |
ASRS Report | 283086 |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : clearance other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : overcame equipment problem flight crew : declared emergency other |
Consequence | Other Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While en route from mia to cyyz, we experienced a flameout of the left engine at FL370. It was obvious that we would not be able to maintain that altitude, and I initiated a call to ZJX advising them that we had an engine failure and needed an immediate descent to a lower altitude. However, in the midst of the commotion, I used an incorrect call sign (don't ask me how I did it -- it was written on my notepad in front of me and dialed in on the ADF). Needless to say, this led ZJX to believe that he had an aircraft on the wrong frequency. As jax was confused, we had to begin our drift-down now, and began to do so. We initiated our descent while ZJX was attempting to give the incorrect aircraft the correct frequency for the correct sector. We also corrected our call sign with the callout of altitude and again stated that we were the aircraft with the engine failure and were descending to a lower altitude. ZJX then felt better about who had the problem and where he was. There were no traffic conflicts, but 1 aircraft had to be vectored out of our way for descent into a diversion airfield. At a lower altitude, we attempted a restart, which was successful, and changed our diversion field from cae to atl. The remainder of the flight was completed with an uneventful approach and landing with 2 engines. We changed aircraft and continued cyyz. The only weak link in the event was that my initial call to ZJX was with an incorrect call sign. This occurred most likely because I was holding a checklist in my hand and trying to pull up to drift-down altitude on the cruise page of the FMS. Otherwise, checklist performance/coordination, communication with the flight attendants communication and coordination with flight control and maintenance coordinators were textbook. Supplemental information from acn 283086: the flight attendants prepared the cabin for landing and briefed the passenger in a timely manner. Maintenance met the aircraft in atl and a substitute aircraft was provided.
Original NASA ASRS Text
Title: ACR HAS ENG FLAMEOUT AT ALT. USES WRONG CALL SIGN WHEN COM WITH ATC.
Narrative: WHILE ENRTE FROM MIA TO CYYZ, WE EXPERIENCED A FLAMEOUT OF THE L ENG AT FL370. IT WAS OBVIOUS THAT WE WOULD NOT BE ABLE TO MAINTAIN THAT ALT, AND I INITIATED A CALL TO ZJX ADVISING THEM THAT WE HAD AN ENG FAILURE AND NEEDED AN IMMEDIATE DSCNT TO A LOWER ALT. HOWEVER, IN THE MIDST OF THE COMMOTION, I USED AN INCORRECT CALL SIGN (DON'T ASK ME HOW I DID IT -- IT WAS WRITTEN ON MY NOTEPAD IN FRONT OF ME AND DIALED IN ON THE ADF). NEEDLESS TO SAY, THIS LED ZJX TO BELIEVE THAT HE HAD AN ACFT ON THE WRONG FREQ. AS JAX WAS CONFUSED, WE HAD TO BEGIN OUR DRIFT-DOWN NOW, AND BEGAN TO DO SO. WE INITIATED OUR DSCNT WHILE ZJX WAS ATTEMPTING TO GIVE THE INCORRECT ACFT THE CORRECT FREQ FOR THE CORRECT SECTOR. WE ALSO CORRECTED OUR CALL SIGN WITH THE CALLOUT OF ALT AND AGAIN STATED THAT WE WERE THE ACFT WITH THE ENG FAILURE AND WERE DSNDING TO A LOWER ALT. ZJX THEN FELT BETTER ABOUT WHO HAD THE PROB AND WHERE HE WAS. THERE WERE NO TFC CONFLICTS, BUT 1 ACFT HAD TO BE VECTORED OUT OF OUR WAY FOR DSCNT INTO A DIVERSION AIRFIELD. AT A LOWER ALT, WE ATTEMPTED A RESTART, WHICH WAS SUCCESSFUL, AND CHANGED OUR DIVERSION FIELD FROM CAE TO ATL. THE REMAINDER OF THE FLT WAS COMPLETED WITH AN UNEVENTFUL APCH AND LNDG WITH 2 ENGS. WE CHANGED ACFT AND CONTINUED CYYZ. THE ONLY WEAK LINK IN THE EVENT WAS THAT MY INITIAL CALL TO ZJX WAS WITH AN INCORRECT CALL SIGN. THIS OCCURRED MOST LIKELY BECAUSE I WAS HOLDING A CHKLIST IN MY HAND AND TRYING TO PULL UP TO DRIFT-DOWN ALT ON THE CRUISE PAGE OF THE FMS. OTHERWISE, CHKLIST PERFORMANCE/COORD, COM WITH THE FLT ATTENDANTS COM AND COORD WITH FLT CTL AND MAINT COORDINATORS WERE TEXTBOOK. SUPPLEMENTAL INFO FROM ACN 283086: THE FLT ATTENDANTS PREPARED THE CABIN FOR LNDG AND BRIEFED THE PAX IN A TIMELY MANNER. MAINT MET THE ACFT IN ATL AND A SUBSTITUTE ACFT WAS PROVIDED.
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.