NYC04LA186

NTSB accident investigation · Cessna 150E · Marlboro, MA · August 7, 2004

Accident · Minor injuriesLimited investigationFinal report
Date
August 7, 2004, 09:00 local (13:00 UTC)
Place
Marlboro, MA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N6159TCessna 150E
Weather
Visual (VMC) · Day
Status
Completed · report April 28, 2005
Report
Approved by Office Director
Parties
FAA FSDO-01
FAA report
20040807016859A
Case key
59852

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 loss of engine power due to a stuck cylinder exhaust valve. Factors were the tailwind and a jammed engine cylinder exhaust valve.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine power(partial) - mech failure/malfTakeoff - initial climb
Engine assembly,valve,exhaust - jammedFactor
Forced landingDescent - emergency
OverrunEmergency landing
Weather condition - tailwindFactor
In flight collision with objectLanding - aborted
Object - tree(s)
In flight collision with terrain/waterLanding - aborted
Terrain condition - ground

Analysis

The airplane engine began to run rough about 1,000 feet agl, during the initial climb from runway 32; a 1,659-foot-long, 45-foot-wide, asphalt runway. The pilot initiated a 180-degree left turn back toward runway 14, and reduced engine power to approximately 2,000 rpm, which reduced the engine vibration. The airplane approached runway 14 fast, and touched down within the first one-half of the runway. The airplane then bounced and floated past the midpoint of the runway. There was insufficient runway remaining to stop the airplane, and the pilot elected to abort the landing. However, during the initial climb from runway 14, the airplane struck trees and landed in a field off the departure end of the runway. Examination of the wreckage revealed that the number four cylinder exhaust valve was stuck in the closed position. The airplane had accumulated 8 hours of operation since the last annual inspection was performed; which was about 9 months prior to the accident. The reported wind at an airport about 10 miles east of the accident site, about the time of the accident, was from 340 degrees at 5 knots.

Factual narrative

On August 7, 2004, about 0900 eastern daylight time, a Cessna 150E, N6159T, was substantially damaged during a collision with trees, following an aborted landing at Marlboro Airport (9B1), Marlboro, Massachusetts. The certificated private pilot sustained minor injuries. Visual meteorological conditions prevailed for the flight that departed Marlboro Airport; destined for Fitchburg Municipal Airport, Fitchburg, Massachusetts. No flight plan was filed for the personal flight conducted under 14 CFR Part 91.

The pilot stated that he departed from runway 32 at 9B1; a 1,659-foot-long, 45-foot-wide, asphalt runway. During the initial climb, about 1,000 feet agl, the engine began to run rough. The pilot initiated a 180-degree left turn toward runway 14, and reduced engine power to approximately 2,000 rpm. The pilot further stated that the engine vibrated less at the lower rpm setting. The airplane approached runway 14 "fast," and touched down within the first one-half of the runway. The airplane then bounced and floated past the midpoint of the runway. There was insufficient runway remaining to stop the airplane, and the pilot elected to abort the landing. However, during the initial climb from runway 14, the airplane struck trees and landed in a field off the departure end of the runway. During the landing, the nose gear collapsed and the airplane came to rest upright.

Examination of the wreckage by a Federal Aviation Administration (FAA) inspector revealed that the number four cylinder exhaust valve was stuck in the closed position.

The pilot reported that the most recent annual inspection was performed on the airplane on November 20, 2003. The airplane had accumulated 8 hours of operation since that inspection.

The pilot reported 303 hours of total flight experience; of which, 170 hours were in the same make and model as the accident airplane. The pilot added that although he had practiced total loss of engine power procedures many times, he had never practiced partial loss of engine power procedures.

Review of the FAA Practical Test Standards for a private pilot applicant revealed that "partial or complete power loss," and "engine roughness or overheat," were two items in which an applicant could be tested to analyze the situation and take appropriate action. However, an applicant was not required to be tested for those two items.

The reported wind at an airport about 10 miles east of the accident site, at 0856, was from 340 degrees at 5 knots.

Aircraft

Registration
N6159T
Reported as
Cessna 150E
Category
Airplane
Serial number
15060859
Airframe hours
2,658
Engine
Lycoming O-200, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
David S. Reasner
Airworthiness certificate
Standard, Utility
Last inspection
Annual · November 20, 2003 · 8 hours before
Departed
9B1 · Marlboro, MA
Destination
FIT · Fitchburg, MA
Airport
9B1 · Marlboro Airport, runway 14, 1,659 × 45 ft, asphalt

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
43
Injuries
Minor
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Last flight review
February 14, 2003
Seat
Left
Flight hours
303 total · 170 in this make and model · 178 as pilot in command · 8 in the last 90 days · 4 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
340° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
63 °F, dew point 52 °F
Altimeter
29.84 inHg
Observed at
BED, 10 nm away

FAA reports on this event · 1

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