37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 132625 |
Time | |
Date | 198912 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mia |
State Reference | FL |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : dec |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | ground other : taxi landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 90 flight time total : 10000 flight time type : 580 |
ASRS Report | 132625 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : atp pilot : instrument |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : overcame equipment problem |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
During the following occurrence, I was acting as captain (PNF) on an medium large transport for a large scheduled airline. During the landing rollout on runway 30 in mia, we experienced a dual engine flameout at an airspeed somewhere between 120 KTS and taxi speed. While on the parallel taxiway we restarted the left engine, and with all engine indications normal, we taxied to gate. At no time did I consider my passenger in any sort of danger. I did not advise mia ground of our problem, only that we would need a few mins to resume our taxi to the gate. I then made a log book entry describing the dual engine flameout. After extensive conversations with maintenance personnel describing all details of the occurrence. A complete inspection of the aircraft and engines was conducted. They were unable to discover anything which could have caused the flameouts. The log book was signed off as all systems relating to the inspections checked out normal and the aircraft was released to passenger service the following morning.
Original NASA ASRS Text
Title: MLG JET ACFT HAD DUAL ENGINE FLAMEOUT AFTER LNDG.
Narrative: DURING THE FOLLOWING OCCURRENCE, I WAS ACTING AS CAPT (PNF) ON AN MLG FOR A LARGE SCHEDULED AIRLINE. DURING THE LNDG ROLLOUT ON RWY 30 IN MIA, WE EXPERIENCED A DUAL ENG FLAMEOUT AT AN AIRSPD SOMEWHERE BTWN 120 KTS AND TAXI SPD. WHILE ON THE PARALLEL TXWY WE RESTARTED THE LEFT ENG, AND WITH ALL ENG INDICATIONS NORMAL, WE TAXIED TO GATE. AT NO TIME DID I CONSIDER MY PAX IN ANY SORT OF DANGER. I DID NOT ADVISE MIA GND OF OUR PROB, ONLY THAT WE WOULD NEED A FEW MINS TO RESUME OUR TAXI TO THE GATE. I THEN MADE A LOG BOOK ENTRY DESCRIBING THE DUAL ENG FLAMEOUT. AFTER EXTENSIVE CONVERSATIONS WITH MAINT PERSONNEL DESCRIBING ALL DETAILS OF THE OCCURRENCE. A COMPLETE INSPECTION OF THE ACFT AND ENGS WAS CONDUCTED. THEY WERE UNABLE TO DISCOVER ANYTHING WHICH COULD HAVE CAUSED THE FLAMEOUTS. THE LOG BOOK WAS SIGNED OFF AS ALL SYSTEMS RELATING TO THE INSPECTIONS CHKED OUT NORMAL AND THE ACFT WAS RELEASED TO PAX SVC THE FOLLOWING MORNING.
Data retrieved from NASA's ASRS site as of August 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.