 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An SF340 developed a number 2 engine vibration after takeoff so the engine was shutdown; an emergency declared; and the flight returned to the departure airport.
| Attributes | |
| ACN | 1016641 |
| Time | |
| Date | 201206 |
| 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 | SF 340B |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Turbine Engine |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Commercial |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
On climbout; once above low level turbulence we noticed unusual and severe vibrations that appeared to be coming from the engines. We ran the QRH for unusual engine vibrations which enabled us to isolate the problem to the #2 engine. The QRH then instructed us to proceed to the engine shutdown checklist which was completed as well. At this point we declared an emergency with ATC and were turned direct back to the departure airport for an emergency landing. We notified the flight attendant of the situation; that we would be making an emergency landing and the approximate time to landing. We then called operations; informed them that we were an emergency aircraft returning and asked them to let dispatch know. The passengers were then told about the situation; that the aircraft flies just fine on one engine and that we would be landing shortly. ATC brought us immediately back [landing]. We shot the visual approach and landed without further incident. After exiting the runway the emergency vehicles met us and inspected the aircraft for damage or fluid leaks before allowing us to taxi to the gate under our own power. We returned to the gate and deplaned the passengers. A brief inspection of the number #2 engine led to the discovery of a loose prop blade.
Original NASA ASRS Text
Title: An SF340 developed a number 2 engine vibration after takeoff so the engine was shutdown; an emergency declared; and the flight returned to the departure airport.
Narrative: On climbout; once above low level turbulence we noticed unusual and severe vibrations that appeared to be coming from the engines. We ran the QRH for Unusual Engine Vibrations which enabled us to isolate the problem to the #2 engine. The QRH then instructed us to proceed to the Engine Shutdown Checklist which was completed as well. At this point we declared an emergency with ATC and were turned direct back to the departure airport for an emergency landing. We notified the Flight Attendant of the situation; that we would be making an emergency landing and the approximate time to landing. We then called Operations; informed them that we were an emergency aircraft returning and asked them to let Dispatch know. The passengers were then told about the situation; that the aircraft flies just fine on one engine and that we would be landing shortly. ATC brought us immediately back [landing]. We shot the visual approach and landed without further incident. After exiting the runway the emergency vehicles met us and inspected the aircraft for damage or fluid leaks before allowing us to taxi to the gate under our own power. We returned to the gate and deplaned the passengers. A brief inspection of the number #2 engine led to the discovery of a loose prop blade.
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.