37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1159486 |
Time | |
Date | 201403 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | Dash 8-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Turbine Engine |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Flying |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
The first officer was the pilot flying on this leg. On the takeoff roll the first officer called 'set power' at the appropriate time; and I verified that he had correctly set the power (no adjustment was necessary). I called '70 KTS;' 'V1;' 'rotate' and the first officer began rotating to the command bars. As the nose wheel lifted off the ground; we both noticed a slight hesitation in the #1 engine as the torque initially dropped 5-10%. We continued through lift-off; adjusting the torque to takeoff power. We put the gear up and coming through 400-500 feet; the torque dropped to appox 75%. The torque then shot back up 100%. At this point I advised tower we were having engine issues and would need to return. The surges continued to become increasingly sporadic and as we approached acceleration height the surge dropped the torque so far that it triggered the autofeather system. Our plan just prior to this was to do a precautionary shutdown above acceleration height; but the plane took care of that for us. I declared an emergency for the engine failure while we ran the eap for an engine failure below acceleration height. We completed the engine fire/failure checklist and engine clean-up items checklist. At this point I briefed the cabin on the situation and called the flight attendant; advising her of the situation; to prepare for an emergency landing with the anticipation of a completely normal landing in 5-10min. She indicated that the cabin was prepared and the passengers were all calm and cooperative. Being so close to the airport (at this point on a downwind vector from ATC) I elected not to call dispatch but rather to prepare for landing. We ran the single-engine landing checklist as we turned base. At this point all checklists were completed and we were cleared for the ILS. The approach and landing were normal in every way aside from the engine situation. Arff was awaiting us but we advised we would not need their assistance after we exited the runway. We taxied back to the gate and parked without further incident.since this is apparently the third time this plane has had a torque surge induced #1 engine shutdown; I suggest we either send the engine to pratt & whitney for complete overhaul or else scrap that engine before it gets someone killed. I'm trying pretty hard to be level headed here but; what are we doing? Whatever is being replaced each time this happens is not working. Stop putting band aids on this and fix it or get rid of it.
Original NASA ASRS Text
Title: DHC-300 flight crew experiences fluctuating torque on the number one engine at rotation that quickly increases in amplitude until auto feather is triggered. An emergency is declared and flight returns to the departure airport. This engine had a history of similar incidents.
Narrative: The First Officer was the pilot flying on this leg. On the takeoff roll the First Officer called 'set power' at the appropriate time; and I verified that he had correctly set the power (no adjustment was necessary). I called '70 KTS;' 'V1;' 'Rotate' and the First Officer began rotating to the command bars. As the nose wheel lifted off the ground; we both noticed a slight hesitation in the #1 engine as the torque initially dropped 5-10%. We continued through lift-off; adjusting the torque to takeoff power. We put the gear up and coming through 400-500 feet; the torque dropped to appox 75%. The torque then shot back up 100%. At this point I advised Tower we were having engine issues and would need to return. The surges continued to become increasingly sporadic and as we approached acceleration height the surge dropped the torque so far that it triggered the autofeather system. Our plan just prior to this was to do a precautionary shutdown above acceleration height; but the plane took care of that for us. I declared an emergency for the engine failure while we ran the EAP for an engine failure below acceleration height. We completed the engine fire/failure checklist and engine clean-up items checklist. At this point I briefed the cabin on the situation and called the Flight Attendant; advising her of the situation; to prepare for an emergency landing with the anticipation of a completely normal landing in 5-10min. She indicated that the cabin was prepared and the passengers were all calm and cooperative. Being so close to the airport (at this point on a downwind vector from ATC) I elected not to call dispatch but rather to prepare for landing. We ran the single-engine landing checklist as we turned base. At this point all checklists were completed and we were cleared for the ILS. The approach and landing were normal in every way aside from the engine situation. ARFF was awaiting us but we advised we would not need their assistance after we exited the runway. We taxied back to the gate and parked without further incident.Since this is apparently the third time this plane has had a torque surge induced #1 engine shutdown; I suggest we either send the engine to Pratt & Whitney for complete overhaul or else scrap that engine before it gets someone killed. I'm trying pretty hard to be level headed here but; what are we doing? Whatever is being replaced each time this happens IS NOT WORKING. Stop putting band aids on this and fix it or get rid of it.
Data retrieved from NASA's ASRS site 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.