# NTSB WPR14CA223: Piper J3C 65, N1205P, Bellingham, WA, June 3, 2014

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: June 3, 2014, 09:30 local (16:30 UTC)
- Place: Bellingham, WA
- Coordinates: 48.67908, -122.409774 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=48.6791&lon=-122.4098&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report July 30, 2014
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- NTSB case key (mKey): 89360
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14CA223
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89360/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89360
- Page: https://openairdocs.org/ntsb/WPR14CA223

## 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

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper J3C-65, 23 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7100510), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper J3C-65, 43 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7100510), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper J3C-65, 11 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7100510), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Piper J3C-65, 28 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7100510), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Piper J3C-65, 11 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7100510), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md)

## 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](https://openairdocs.org/aircraft/N1205P), registered now, S/N 17630, built 1946 (OpenAirDocs)
- Reported make and model: PIPER J3C 65 (65)
- Registry model: [Piper J3C-65](https://openairdocs.org/model/piper-j3c-65) (registry code 7100510) (OpenAirDocs)
- Registry engine: [Continental A&C65 series](https://openairdocs.org/engine/continental-a-c65-series) (registry code 17003, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17630
- Year built: 1946
- Engines: 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

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 81; injuries: none; 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

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20140603007419A](https://openairdocs.org/incident/20140603007419A), Jun 3, 2014: Piper J3C-65, Bellingham, WA, Substantial damage. The pilot stated weather was not a factor (no wind) and he touched down on the grass strip about 200 feet from threshold. On roll out up the Airstrip ( it goes…

## Docket (4 files)

The files NTSB released with the investigation on June 20, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89360. 635 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 208 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413498&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Photo 1 – Overview of Airplane (Photo Courtesy of FAA) (item 2, .PDF, 168 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413499&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20Overview%20of%20Airplane%20%20(Photo%20Courtesy%20of%20FAA)%0D%0A-Master.PDF
- Photo 2 – Left Wing Damage (Photo Courtesy of FAA) (item 3, .PDF, 113 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413500&FileExtension=.PDF&FileName=Photo%202%20%E2%80%93%20Left%20Wing%20Damage%20(Photo%20Courtesy%20of%20FAA)%0D%0A-Master.PDF
- Photo 3 – Right Wing Damage (Photo Courtesy of FAA) (item 4, .PDF, 146 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413501&FileExtension=.PDF&FileName=Photo%203%20%E2%80%93%20Right%20Wing%20Damage%20(Photo%20Courtesy%20of%20FAA)%0D%0A-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.