37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1503235 |
Time | |
Date | 201712 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Direct |
Flight Plan | None |
Component | |
Aircraft Component | Engine |
Person 1 | |
Function | Instructor Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 1440 Flight Crew Type 500 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
Almost immediately after liftoff; the engine experienced a partial loss of power. I declared control of the aircraft 'my airplane'; identified the potential to land on the remaining runway; immediately pulled the power; and lowered the flaps. Subsequently; recognized the aircraft was not descending or slowing sufficiently to make the runway landing; I added power; and raised flaps; expecting the next potential landing spot in the event of complete power loss would be the golf course adjacent the runway. The engine continued to provide just enough power to maintain an airspeed of approximately 75 knots; and very small positive rate of climb; estimated 50-100 fpm. The engine continued to sputter; but the aircraft continued to climb slowly; so landing on the golf course was no longer an option.the next phase of this short flight would be to nurse the aircraft far enough beyond the city to ditch the aircraft into the water close to the beach. While expecting to do just that; I maintained airspeed and climb rate while searching for places to land in case the ocean could not be reached. Fortunately I gained enough altitude to determine that I could make the turn back to the airport. I contacted the tower; [advised them of the situation]; and notified them I would be landing. The landing was uneventful; and there was no damage; no injuries. Cause of the partial loss of power is unknown at this time.
Original NASA ASRS Text
Title: Cessna 172 flight instructor reported a partial loss of power immediately after takeoff resulting in a return to the departure airport.
Narrative: Almost immediately after liftoff; the engine experienced a partial loss of power. I declared control of the aircraft 'My airplane'; identified the potential to land on the remaining runway; immediately pulled the power; and lowered the flaps. Subsequently; recognized the aircraft was not descending or slowing sufficiently to make the runway landing; I added power; and raised flaps; expecting the next potential landing spot in the event of complete power loss would be the golf course adjacent the runway. The engine continued to provide just enough power to maintain an airspeed of approximately 75 knots; and very small positive rate of climb; estimated 50-100 fpm. The engine continued to sputter; but the aircraft continued to climb slowly; so landing on the golf course was no longer an option.The next phase of this short flight would be to nurse the aircraft far enough beyond the city to ditch the aircraft into the water close to the beach. While expecting to do just that; I maintained airspeed and climb rate while searching for places to land in case the ocean could not be reached. Fortunately I gained enough altitude to determine that I could make the turn back to the airport. I contacted the tower; [advised them of the situation]; and notified them I would be landing. The landing was uneventful; and there was no damage; no injuries. Cause of the partial loss of power is unknown at this time.
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.