CEN11LA388

NTSB accident investigation · Cessna 172 · Ironton, OH · May 28, 2011

Accident · Minor injuriesLimited investigationFinal report
Date
May 28, 2011, 19:15 local (23:15 UTC)
Place
Ironton, OH
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N5663RCessna 172
Defining event
Enroute-cruise: Loss of engine power (total)
Weather
Visual (VMC) · Day
Status
Completed · report November 7, 2012
Report
Approved by Office Director
NTSB office
Central Region
Parties
Federal Aviation Adminstration
FAA report
20110528009609A
Case key
80760

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The total loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

Findings · 1

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Not determinedNot determined › Not determined · Unknown/Not determinedCessna 172F: 5 casesAll aircraft: 2,247 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot said that the airplane experienced a gradual loss of engine power during cruise flight followed by a total loss of engine power and a loss of electrical power. The pilot performed a forced landing to a field. Examination of the airplane and engine did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. According to carburetor icing charts, a probability of serious icing at glide power existed based upon the temperature and dew point at the time of the accident; however, the airplane was operating at a higher power setting, for which the probability of carburetor icing was minimal.

Factual narrative

On May 28, 2011, about 1915 eastern daylight time, a Cessna 172F, N5663R, experienced a total loss of engine and electrical power during cruise flight near Ironton, Ohio. The pilot subsequently made a forced landing to a field. The private pilot and the certified flight instructor sustained minor injuries. The airplane sustained substantial damage to the fuselage, engine firewall, and empennage. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as an instructional flight. Visual meteorological conditions prevailed and no flight plan had been filed for the local flight destined for Ashland Regional Airport (DWU), Ashland, Kentucky. The flight originated from DWU at 1815. The pilot stated that prior to May 26, 2011, the airplane had not been flown and had not been fueled for a "very long time." On May 26, 2011, the pilot flew the airplane for a flight review, which was given to him by his flight instructor. After landing, the left toe brake pedal was very soft, and the airplane was not flown for the remainder of the day. On May 27, 2011, a mechanic at DWU fixed the brake and also removed some bird nest material that was found around the engine. On May 28, 2011, the pilot and his flight instructor flew around the DWU traffic pattern eight times and performed four landings. They then flew 7-8 miles northwest of DWU, where the pilot performed "normal" flight maneuvers. At 2,500 feet mean sea level (MSL), the airplane experienced decreasing engine power. While beginning to fly towards DWU, the engine power continued to decrease, and the airplane began to lose altitude. At 1,500 feet mean sea level, the engine lost all power along with a loss of electrical power. The pilot then landed the airplane on a field. Examination of the airplane by a Federal Aviation Administration (FAA) inspector from the Nashville Flight Standards District Office, revealed that the outside of the engine was rusted with many corroded parts. The engine was rotated and engine compression was noted. The magnetos were operational. There was fuel in the airplane fuel tanks. According to the probability icing chart contained in FAA Special Airworthiness Information Bulletin, CE-09-35, there was a probability of serious icing at glide power with a temperature of 79 degrees Fahrenheit and a dew point of 64 degrees Fahrenheit.

Aircraft

Registration
N5663R
Reported as
Cessna 172 (F)
Category
Airplane
Serial number
17253296
Airframe hours
3,653
Engine
Continental O300, 145 hp, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Pilot
Registered owner
Pilot
Airworthiness certificate
Standard, Normal
Last inspection
Annual · September 27, 2010
Departed
DWU · Worthington, KY
Destination
DWU · Worthington, KY

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
56
Injuries
Minor
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
May 26, 2011
Seat
Left
Flight hours
106 total · 5 in this make and model · 77 as pilot in command · 3 in the last 90 days · 3 in the last 30 days · 2 in the last 24 hours
Role
Pilot
Age
45
Injuries
Minor
Certificates
Commercial, Flight instructor
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 2, Without waivers/limitations
Last flight review
January 30, 2010
Seat
Right
Flight hours
1,520 total · 640 in this make and model · 1,500 as pilot in command · 45 in the last 90 days · 13 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 64 °F
Altimeter
29.90 inHg
Observed at
HTS, 14 nm away

Docket · 4

The files NTSB released with the investigation on September 12, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.