# NTSB WPR09CA002: Piper J3C-65, N2146M, Lynden, WA, October 3, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 2, 2008, 18:45 local (Oct 3, 2008, 01:45 UTC) - Place: Lynden, WA - Coordinates: 48.955833, -122.458053 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=48.9558&lon=-122.4581&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 5, 2008 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 69224 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09CA002 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/69224/pdf - Page: https://openairdocs.org/ntsb/WPR09CA002 ## Probable cause The separation of the tailwheel spring retaining clip for unknown reasons, which resulted in the loss of directional control during the landing roll. ## 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 · Attain/maintain not possible (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) - [Landing gear system: nose/tail landing gear](https://openairdocs.org/ntsb-findings/01023220): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Piper J3C-65, 2 cases](https://openairdocs.org/ntsb-findings/01023220/cases.md?model=7100510), [All aircraft, 185 cases](https://openairdocs.org/ntsb-findings/01023220/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: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330); cases with it: [Piper J3C-65, 2 cases](https://openairdocs.org/ntsb-events/330/sequence.md?model=7100510), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); 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: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper J3C-65, 14 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7100510), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper J3C-65, 54 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7100510), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that the tailwheel equipped airplane suddenly veered to the right during the landing roll. Despite his control inputs, the airplane continued to veer to the right, exited the runway, and impacted a hangar located adjacent to the runway. Examination of the airplane revealed that the fuselage and both wings were structurally damaged. The tailwheel spring retaining clip was found separated from the tailwheel assembly. No anomalies were noted with the flight control system. ## Factual narrative The pilot stated that during the landing roll in a tailwheel equipped airplane, it veered suddenly to the right. Despite his control inputs, the airplane continued to veer to the right, exited the runway, and impacted a hangar located adjacent to the runway. Examination of the airplane revealed that the fuselage and both wings were structurally damaged. The tailwheel spring retaining clip was found separated from the tailwheel assembly. No anomalies were noted with the flight control system. ## Aircraft - Registration: [N2146M](https://openairdocs.org/aircraft/N2146M), registered now, S/N 20931, built 1946 (OpenAirDocs) - Reported make and model: PIPER J3C-65 - Registry model: [Piper J3C-65](https://openairdocs.org/model/piper-j3c-65) (registry code 7100510) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 20931 - Engines: Continental C85 85 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: John William Vanderhage - Registered owner: Scott Peterson - Airworthiness certificate: Standard, Normal - Departed: 38W, Lynden, WA - Destination: 38W, Lynden, WA - Airport: 38W, Lynden Airport, runway 25, 2,425 × 40 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 34; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 12, 2008; seat: rear; flight hours: 233 total, 15 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 3,900 ft overcast - Temperature: 63 °F, dew point 54 °F - Altimeter: 29.73 inHg - Observed at: BLI, 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 (OpenAirDocs). - [Accident 20081002846449A](https://openairdocs.org/incident/20081002846449A), Oct 2, 2008: Piper J3C65, Lynden, WA, Substantial damage. (-23) On 10/02/2008 at approximately 18:30 PDT a Piper J3C-65 aircraft, serial number 20931, operated by [privacy data omitted] lost control momentarily after… 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.