ERA11LA383

NTSB accident investigation · Cessna 150L · Plymouth, MA · July 4, 2011

Accident · No injuriesLimited investigationFinal report
Date
July 4, 2011, 13:00 local (17:00 UTC)
Place
Plymouth, MA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N150ETCessna 150L
Defining event
Initial climb: Powerplant sys/comp malf/fail
Weather
Visual (VMC) · Day
Status
Completed · report January 17, 2012
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20110704011799A
Case key
81011

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

A partial loss of engine power during initial climb due to a stuck cylinder valve, which resulted from excessive corrosion and carbon deposits on the valve springs due to inadequate maintenance.

Findings · 3

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.

MaintenancePersonnel issues › Task performance · Not specifiedCessna 150L: 1 caseAll aircraft: 143 casesProbable cause
Engine (reciprocating): recip eng cyl sectionAircraft › Aircraft power plant · Fatigue/wear/corrosionCessna 150L: 6 casesAll aircraft: 373 casesProbable cause
Engine (reciprocating): recip eng cyl sectionAircraft › Aircraft power plant · MalfunctionCessna 150L: 6 casesAll aircraft: 373 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

During initial climb, the engine began to run rough and experienced a partial loss of power. The pilot elected to land straight ahead into a cranberry bog. The pilot believed the loss of engine power was due to a stuck cylinder valve. Postaccident examination of the engine revealed that the No. 2 cylinder intake and exhaust valve springs exhibited excessive corrosion and carbon deposits, consistent with lack of use, which made them more susceptible to sticking. The extent of the corrosion was such that it presented over a long period of time and should have been addressed during routine maintenance. No other defects were noted with the engine that would have resulted in a partial loss of power. The airplane had been operated for 17 hours since its most recent annual inspection, which was completed 11 months prior to the accident. The engine had been operated for 256 hours since its most recent overhaul, which was completed more than 10 years prior to the accident. The same airplane was involved in a forced landing to a cranberry bog 8 years earlier due to a stuck cylinder valve.

Factual narrative

On July 4, 2011, about 1300 eastern daylight time, a Cessna 150L, N150ET, operated by a private individual, was substantially damaged during a forced landing to a cranberry bog, following a partial loss of engine power during takeoff from Plymouth Municipal Airport (PYM), Plymouth, Massachusetts. The certificated commercial pilot was not injured. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the planned local flight. The pilot reported that during initial climb, the engine began to run rough and experienced a partial loss of power. The pilot elected to land straight ahead into a cranberry bog. During the landing, the landing gear, propeller, and engine firewall sustained substantial damage. The pilot further stated that the loss of engine power was due to a stuck cylinder valve. Examination of the engine by a Federal Aviation Administration (FAA) inspector revealed that the No. 2 cylinder intake and exhaust valve springs exhibited corrosion and carbon deposits. The other cylinder valve springs also exhibited corrosion, consistent with lack of operation; however, they did not exhibit the carbon build-up similar to the No. 2 cylinder valve springs. The inspector also checked the fuel system, cylinder compression, sparkplugs, the carburetor, and the exhaust system, and no other defects were noted. According to maintenance records, the airplane had been operated for 17 hours since its most recent annual inspection, which was performed on August 14, 2010. The engine had been operated for 256 hours since its most recent overhaul, which was completed more than 10 years prior to the accident. Review of FAA records revealed that the same airplane was involved in a forced landing to a cranberry bog in 2003, due to a stuck cylinder valve.

Aircraft

Registration
N150ET
Reported as
Cessna 150L
Category
Airplane
Serial number
15073072
Airframe hours
4,500
Engine
Cont Motor O-200, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Richard C Murphy
Registered owner
Richard C Murphy
Airworthiness certificate
Standard, Normal
Last inspection
Annual · August 14, 2010 · 17 hours before
Departed
PYM · Plymouth, MA
Destination
PYM · Plymouth, MA
Airport
PYM · Plymouth

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

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
70
Injuries
None
Certificates
Commercial, Flight instructor
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
February 17, 2011
Seat
Left
Flight hours
4,327 total · 3,001 in this make and model · 4,023 as pilot in command · 44 in the last 90 days · 20 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 11 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
84 °F, dew point 64 °F
Altimeter
29.79 inHg
Observed at
PYM

Docket · 4

The files NTSB released with the investigation on November 28, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 655 KB 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.