WPR14CA223

NTSB accident investigation · Piper J3C 65 · Bellingham, WA · June 3, 2014

Accident · No injuriesData collectionFinal report
Date
June 3, 2014, 09:30 local (16:30 UTC)
Place
Bellingham, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1205PPiper J3C 65
Defining event
Landing-landing roll: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed · report July 30, 2014
Report
Approved by Office Director
NTSB office
Western Pacific Region
FAA report
20140603007419A
Case key
89360

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 failure to maintain directional control during the landing on a narrow airstrip, which resulted in a collision with trees.

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.

Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper J3C-65: 23 casesAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotPiper J3C-65: 43 casesAll aircraft: 9,295 casesProbable cause
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomePiper J3C-65: 11 casesAll aircraft: 933 cases

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 owner-pilot departed his home airport for a personal flight to another airstrip where he had previously operated many times. Since the turf runway had a significant slope and was bordered by trees on three sides, landings were conducted in the uphill direction, which was to the southeast. The narrowness of the runway, coupled with the proximity of trees to the runway edges, necessitated that pilots taxi uphill to the southeast end, in order to turn around and exit the runway at the northwest end. The pilot overflew the runway to check for deer and other obstacles, and made a left-hand circling approach for the landing to the southeast. There was a slight left crosswind during the approach, but no wind at all on the runway because of the tall trees. Touchdown at the intended landing point, which was about 150 feet beyond the approach end was normal. After landing, the pilot added power to taxi uphill to turn around. However, about 400 feet beyond the touchdown point, the airplane began to drift to the right. The pilot was unable to correct that drift before the right wingtip struck a small tree, which resulted in a sharp right turn. The airplane veered off the right side of the runway, which was a downsloped, wooded area. The airplane was stopped by a large tree, and came to rest approximately perpendicular to the runway, with the tail approximately at the runway edge. The airplane sustained substantial damage to its wings. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Factual narrative

The owner-pilot departed his home airport for a personal flight to another airstrip where he had previously operated many times. Since the turf runway had a significant slope and was bordered by trees on three sides, landings were conducted in the uphill direction, which was to the southeast. The narrowness of the runway, coupled with the proximity of trees to the runway edges, necessitated that pilots taxi uphill to the southeast end, in order to turn around and exit the runway at the northwest end. The pilot overflew the runway to check for deer and other obstacles, and made a left-hand circling approach for the landing to the southeast. There was a slight left crosswind during the approach, but no wind at all on the runway because of the tall trees. Touchdown at the intended landing point, which was about 150 feet beyond the approach end was normal. After landing, the pilot added power to taxi uphill to turn around. However, about 400 feet beyond the touchdown point, the airplane began to drift to the right. The pilot was unable to correct that drift before the right wingtip struck a small tree, which resulted in a sharp right turn. The airplane veered off the right side of the runway, which was a downsloped, wooded area. The airplane was stopped by a large tree, and came to rest approximately perpendicular to the runway, with the tail approximately at the runway edge. The airplane sustained substantial damage to its wings. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Aircraft

Registration
N1205P
Reported as
Piper J3C 65 (65)
Category
Airplane
Serial number
17630
Built
1946
Engine
Cont Motor A&C65 SERIES, 65 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Departed
BVS · Burlington, WA
Destination
WA90 · Bellingham, WA
Airport
WA90 · Floathaven, runway 00, 1,200 × 50 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
81
Injuries
None
Certificate
Commercial
Airplane ratings
Multi-engine land, Single-engine sea, Single-engine land
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Last flight review
August 19, 2013
Seat
Front
Restraint
3-point
Flight hours
7,349 total · 273 in this make and model · 6,545 as pilot in command · 27 in the last 90 days · 10 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
130° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
57 °F, dew point 52 °F
Altimeter
30.10 inHg

Docket · 4

The files NTSB released with the investigation on June 20, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 635 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.