ERA13CA208

NTSB accident investigation · Cessna 140 · Lancaster, SC · April 18, 2013

Accident · No injuriesData collectionFinal report
Date
April 18, 2013, 14:30 local (18:30 UTC)
Place
Lancaster, SC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N76688Cessna 140
Defining event
Approach-VFR go-around: Miscellaneous/other
Weather
Visual (VMC) · Day
Status
Completed · report August 13, 2013
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA FSDO
FAA report
20130418006599A
Case key
86675

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 pilot’s decision to land with a tailwind and his failure to turn off the carburetor heat during a go-around, which resulted in degraded engine performance and the airplane’s subsequent collision with trees at the end of the runway.

Findings · 4

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.

Engine controlsAircraft › Aircraft power plant · Incorrect use/operationCessna 140: 1 caseAll aircraft: 51 casesProbable cause
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomeCessna 140: 4 casesAll aircraft: 933 cases
Performance/control parameters: powerplant parametersAircraft › Aircraft oper/perf/capability · Attain/maintain not possibleCessna 140: 1 caseAll aircraft: 81 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 stated that before he departed for a local flight, the wind was “squirrelly and swapping around” and that at takeoff the wind favored runway 21. After flying for about 15 to 20 minutes, the pilot returned to the departure airport and flew over it to observe the windsock, which indicated the wind had shifted and now favored runway 3. He entered the airport traffic pattern for runway 3 and perceived that the ground speed was “a little fast” during the approach to land. He continued the approach and touched down about 1/3 down the runway and perceived that the groundspeed was now “real fast.” Because the airplane was tailwheel equipped, the pilot did not apply the brakes; instead, he added power to go around, reporting that the engine responded normally. The pilot said that the airplane barely cleared the power lines off the end of the runway with marginal airspeed, and then stalled/mushed into the trees beyond the power lines. The pilot also reported that he was not aware of any preimpact failure or malfunction that would have precluded normal operations of the airplane, engine, or engine systems. A postaccident examination of the airplane revealed that the carburetor heat was on, the fuel selector was off, and the throttle was full forward. A weather observation taken about 23 minutes after the accident at an airport located about 13 nautical miles north of the accident airport indicated that the wind was from 200 degrees at 5 knots.

Factual narrative

The pilot stated that before departure for a local flight the wind was “squirrelly and swapping around” and at takeoff the wind favored runway 21. After flying for about 15 to 20 minutes he elected to return to the departure airport and flew over it to observe the windsock which indicated the wind seemed to favor runway 03. He entered the traffic pattern for runway 03, and while on approach for a full-stop landing, he perceived the groundspeed was, “a little fast.” He continued the approach and touched down 1/3 down the runway, but at touchdown perceived the groundspeed was, “real fast.” Because the airplane was tailwheel equipped he did not apply the brakes, and he added power to go-around reporting that the engine responded OK. The flight barely cleared powerlines ahead with marginal airspeed, and with tall trees ahead, the airplane stall/mushed into trees. Although a bucket truck came to rescue him from the tree, it was too short to reach him. He donned a harness and shimmied out of the tree and also reported he was not aware of any preimpact failure or malfunction with the airplane, engine, or engine systems. A postaccident inspection of the airplane following recovery revealed the carburetor heat remained on, the fuel selector was off, and the throttle was full forward. An aviation surface analysis report from Charlotte-Monroe Executive Airport (EQY) at 1453, or about 23 minutes after the accident indicates in part that the wind was from 200 degrees at 5 knots. The EQY Airport is located about 13 nautical miles and 019 degrees from the accident airport.

Aircraft

Registration
N76688
Reported as
Cessna 140
Category
Airplane
Serial number
10861
Airframe hours
2,159
Engine
Cont Motor C85-12, 85 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Wiese Jerry W
Registered owner
Wiese Jerry W
Airworthiness certificate
Standard, Normal
Last inspection
Annual · December 4, 2012
Departed
SC76 · Lancaster, SC
Destination
SC76 · Lancaster, SC
Airport
SC76 · Unity Aerodrome, runway 03, 2,600 × 100 ft, grass/turf

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
79
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
October 31, 2011
Seat
Left
Flight hours
334 total · 70 in this make and model · 271 as pilot in command · 3 in the last 90 days · 1 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
200° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 59 °F
Altimeter
30.10 inHg
Observed at
EQY, 13 nm away

Docket · 3

The files NTSB released with the investigation on May 30, 2013, 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.

Other investigations on N76688 · 1

Matched to the same aircraft by N-number and date.