 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Douglas dc-3 pilot reported an engine problem shortly after takeoff; which resulted in an immediate return to the departure airport.
| Attributes | |
| ACN | 1554904 |
| Time | |
| Date | 201806 |
| 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 | DC-3/Dakota/Skytrain |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | None |
| Component | |
| Aircraft Component | Engine |
| Person 1 | |
| Function | Pilot Not Flying |
| Qualification | Flight Crew Rotorcraft Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Sea |
| Experience | Flight Crew Last 90 Days 28 Flight Crew Total 5175 Flight Crew Type 25 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
After a normal takeoff for a local scenic flight with two passengers; we made the customary two power reductions. A few seconds after the second reduction I noticed a small yaw to the left and the pilot flying (PF) called 'engine failure.' the PF subsequently identified the problem as the left engine and called for the engine failure checklist. For the next minute or so; I was absorbed with the checklist and notifying the control tower that we were returning to the field and [advised them of our situation]. The PF determined that the engine was still producing some power and elected not to feather. As most of the checklist concerns securing a failed engine; I abandoned the checklist and devoted some time to troubleshooting the engine. I observed that the left engine RPM was varying from about 2000 to 2600. I verified mixture was auto rich and boost pumps on. I tried running on left and right mag with no difference in either case. By this time we were downwind at pattern altitude and the PF reduced power and things seemed to settle down a bit. We landed uneventfully and taxied to parking. On the ground; the left engine seemed to run ok below about 1700 RPM but backfired at higher speeds.
Original NASA ASRS Text
Title: Douglas DC-3 pilot reported an engine problem shortly after takeoff; which resulted in an immediate return to the departure airport.
Narrative: After a normal takeoff for a local scenic flight with two passengers; we made the customary two power reductions. A few seconds after the second reduction I noticed a small yaw to the left and the pilot flying (PF) called 'Engine Failure.' The PF subsequently identified the problem as the left engine and called for the engine failure checklist. For the next minute or so; I was absorbed with the checklist and notifying the Control Tower that we were returning to the field and [advised them of our situation]. The PF determined that the engine was still producing some power and elected not to feather. As most of the checklist concerns securing a failed engine; I abandoned the checklist and devoted some time to troubleshooting the engine. I observed that the left engine RPM was varying from about 2000 to 2600. I verified mixture was auto rich and boost pumps on. I tried running on L and R mag with no difference in either case. By this time we were downwind at pattern altitude and the PF reduced power and things seemed to settle down a bit. We landed uneventfully and taxied to parking. On the ground; the left engine seemed to run OK below about 1700 RPM but backfired at higher speeds.
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.