# NTSB CEN18TA330: Piper J3C, N42218, Friendswood, TX, August 13, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Final report - Date: August 13, 2018, 11:00 local (16:00 UTC) - Place: Friendswood, TX - Coordinates: 29.504722, -95.175277 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=29.5047&lon=-95.1753&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: 1 uninjured - Status: Completed, report September 27, 2019 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 98067 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN18TA330 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98067/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98067 - Page: https://openairdocs.org/ntsb/CEN18TA330 ## Probable cause The pilot's decision to conduct a flight in an airplane that had a tailwheel with degraded locking pins, which allowed the tailwheel to unlock and swivel out of alignment and precluded the pilot from regaining directional control on the ground during a crosswind landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper J3C-65, 11 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7100510), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Landing gear system: nose/tail landing gear](https://openairdocs.org/ntsb-findings/01023220): Aircraft › Aircraft systems · Damaged/degraded (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) - [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) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause); cases with it: [Piper J3C-65, 6 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=7100510), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/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. - [Prior to flight: Aircraft maintenance event](https://openairdocs.org/ntsb-events/040); cases with it: [Piper J3C-65, 2 cases](https://openairdocs.org/ntsb-events/040/sequence.md?model=7100510), [All aircraft, 484 cases](https://openairdocs.org/ntsb-events/040/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: Landing gear not configured](https://openairdocs.org/ntsb-events/095); cases with it: [Piper J3C-65, 1 case](https://openairdocs.org/ntsb-events/095/sequence.md?model=7100510), [All aircraft, 584 cases](https://openairdocs.org/ntsb-events/095/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 During the personal flight, the commercial pilot completed several uneventful touch-and-go landings at two nearby airports, then returned and landed on the runway with a right crosswind at 9 knots. As the airplane slowed on the runway, it weathervaned into the wind and veered to the right. The pilot was unable to steer with the tailwheel, and the airplane exited the right side of the runway and collided with a tree. A postaccident examination of the airplane revealed that the tailwheel locking mechanism pins were worn and degraded. The locking mechanism could not withstand even a small amount of side pressure; as pressure was applied to the tailwheel, the locking mechanism would unlock and the tailwheel would swivel out of alignment. It is likely that, due to the degraded locking pins, the tailwheel became unlocked before the final landing and was out of alignment during the landing roll, which precluded the pilot from regaining directional control. It is the pilot's responsibility to ensure that the airplane is in a safe condition for flight; in this case, the pilot did not ensure that the tailwheel locking mechanism was in good working condition before he decided to conduct the flight. ## Factual narrative On August 13, 2018, about 1100 central daylight time, a Piper J3C-65 airplane, N42218, experienced a runway excursion during landing at Polly Ranch Airport (7XS0), Friendswood, Texas. The commercial pilot was not injured and the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and no flight plan had been filed. The local flight departed at 1024. The responding Federal Aviation Administration (FAA) inspector spoke to the pilot who described the runway excursion. The pilot stated that the airplane touched down about 35 to 40 mph and as soon as the tail touched the runway the airplane veered to the right. The airplane continued off the runway into a tree. The pilot reported that he departed 7XS0 and completed several uneventful touch-and-go landings at two nearby airports. He returned to 7XS0 and landed on runway 11 with a right crosswind at 9 knots. As the airplane slowed on the runway it weathervaned into the wind and he was unable to steer with the tailwheel. The airplane exited the right side of the runway and collided with a tree. A postaccident examination of the airplane revealed that the Maule tailwheel locking mechanism pins were worn down and degraded. The locking mechanism could not withstand even a small amount of side pressure. As pressure was applied to the tailwheel, the locking mechanism would unlock and the tailwheel would swivel out of alignment (figure 1). Figure 1 – Unlocked Tailwheel ## Aircraft - Registration: [N42218](https://openairdocs.org/aircraft/N42218), registered now, S/N 14464, built 1945 (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: [Continental A&C65 series](https://openairdocs.org/engine/continental-a-c65-series) (registry code 17003, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 14464 - Year built: 1945 - Airframe hours: 1776 - Engines: Continental Motors A75-8F 75 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 19, 2018 - Departed: 7XS0, Friendswood, TX - Destination: 7XS0, Friendswood, TX - Airport: 7XS0, Polly Ranch, runway 11, 2,700 × 22 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review December 14, 2017; seat: rear; restraint: lap only; flight hours: 3,433 total, 365 in this make and model, 3,372 as pilot in command, 52 in the last 90 days, 22 in the last 30 days, 0.6 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 150° at 9 knots - Visibility: 9 statute miles - Lowest ceiling: 3,000 ft broken - Temperature: 88 °F, dew point 75 °F - Altimeter: 30.07 inHg - Observed at: KLVJ, 4 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 20180813024259A](https://openairdocs.org/incident/20180813024259A), Aug 13, 2018: Piper J3C-65, Friendswood, TX, Substantial damage. When landing on runway 11 at airport polyranch (7XSQ) about 1030 local central time on August 13, 2018. After landing, on roll out pilot unable to keep… ## Docket (2 files) The files NTSB released with the investigation on September 26, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98067. 3.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40466930&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos (item 2, .PDF, 382 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40466931&FileExtension=.PDF&FileName=Photos-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.