 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
DHC8-200 captain experiences an over torque just after takeoff and elects to shut the engine down and return to the departure airport.
| Attributes | |
| ACN | 1091195 |
| Time | |
| Date | 201305 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Dash 8-200 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Component | |
| Aircraft Component | Turbine Engine |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 85 Flight Crew Total 2925 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
I was operating a ferry flight and just after departure around 400 ft; the #1 engine torque immediately shot up to 116% with a noticeable change in yaw (and sound). My first officer called out 'engine failure;' and while correcting for the yaw; I asked him to identify that the #1 engine had failed and feathered. He said the engine had failed but did not feather; and I elected to immediately shut down the #1 engine and feather it. We notified ATC of our engine failure and emergency condition. We ran the engine failure checklist and circled back to land for a visual. With the emergency checklist not fully completed and clouds beginning to hide the airport; I requested additional vectors for the ILS in order to assure proper landing and to complete the emergency checklist in full. We then landed single-engine without incident.
Original NASA ASRS Text
Title: DHC8-200 Captain experiences an over torque just after takeoff and elects to shut the engine down and return to the departure airport.
Narrative: I was operating a ferry flight and just after departure around 400 FT; the #1 Engine torque immediately shot up to 116% with a noticeable change in yaw (and sound). My First Officer called out 'engine failure;' and while correcting for the yaw; I asked him to identify that the #1 Engine had failed and feathered. He said the engine had failed but did not feather; and I elected to immediately shut down the #1 Engine and feather it. We notified ATC of our engine failure and emergency condition. We ran the Engine Failure Checklist and circled back to land for a visual. With the Emergency Checklist not fully completed and clouds beginning to hide the airport; I requested additional vectors for the ILS in order to assure proper landing and to complete the Emergency Checklist in full. We then landed single-engine without incident.
Data retrieved from NASA's ASRS site as of July 2013 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.