# NTSB ATL05LA076: Piper PA-20, N7053K, Thomaston, GA, April 28, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 28, 2005, 09:35 local (13:35 UTC) - Place: Thomaston, GA - Coordinates: 32.954723, -84.263053 - Nearby events: https://openairdocs.org/map.md?lat=32.9547&lon=-84.2631&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 31, 2006 - Report: Approved by Office Director - Parties: FAA Atlanta FSDO - 11 - NTSB case key (mKey): 61378 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ATL05LA076 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61378/pdf - Page: https://openairdocs.org/ntsb/ATL05LA076 ## Probable cause The unapproved repair of the tailwheel rudder arm assembly, which resulted in an overload failure during touchdown and subsequent loss of control of the airplane and on-ground collision with an object. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, landing - flare/touchdown - landing gear,tailwheel assembly - fractured - maintenance - not approved, other maintenance personnel (cause) - landing gear,tailwheel assembly - overload - Loss of control - on ground/water, landing - roll - aircraft control - not possible, pilot in command - On ground/water collision with object, landing - roll - object - vasi light/system ## Analysis The pilot stated the main wheels touched down normally; when the tailwheel touched down, the airplane pulled hard to the left, and application of the rudder had no effect. The airplane continued left off the side of the runway and collided with a lighting system. The tailwheel rudder arm assembly was found fractured and separated on the right side, and evidence of a previous weld repair inboard of the fracture was observed. The weld repair was observed at the thickest area of the tapered rudder arm assembly, and the fracture was observed at a smaller-diameter area. Metallurgical examination of the rudder arm assembly revealed the aluminum component showed deformation near the fracture surfaces with no evidence of fatigue. ## Factual narrative On April 28, 2005, at 0935 eastern daylight time, a Piper PA-20, N7053K, registered to Matlad, Inc., and operated by the airline transport pilot, veered off the runway during landing roll at Thomaston - Upson County Airport, Thomaston, Georgia. The personal flight was operated under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual meteorological conditions prevailed. The airline transport pilot and the passenger were not injured, and the airplane sustained substantial damage. The flight departed Aiken Municipal Airport, Aiken, South Carolina, about 0815. The pilot stated the approach to runway 30 was normal, and the main wheels touched down normally. The pilot stated that, when the tailwheel touched down, the airplane pulled hard to the left, application of the rudder had no effect, and the airplane continued left off the side of the runway. The airplane continued through the grass, and the empennage collided with the runway's precision approach path indicator lights. Examination of the airplane revealed damage to the empennage and fuselage. The tailwheel rudder arm assembly was found fractured and separated on the right side, and evidence of a previous weld repair outboard of the fracture was observed. The weld repair was observed at the thickest area of the tapered rudder arm, and the fracture was observed at a smaller-diameter area. Metallurgical examination of the rudder arm revealed the aluminum component showed deformation near the fracture surfaces with no evidence of fatigue. The pilot stated he had purchased the airplane two days before the accident, and the airplane had accumulated approximately 1.9 hours since annual inspection. Review of maintenance records for the airplane revealed no record of the rudder arm assembly repair. ## Aircraft - Registration: [N7053K](https://openairdocs.org/aircraft/N7053K), registered now, S/N 20-160, built 1950 (OpenAirDocs) - Reported make and model: Piper PA-20 - Registry model: [Piper PA-20](https://openairdocs.org/model/piper-pa-20) (registry code 7102002) (OpenAirDocs) - Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 20-160 - Airframe hours: 1631.9 - Engines: Lycoming O-290-D2 135 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 1, 2005, 1.9 hours before - Departed: KAIK, Aiken, SC - Destination: KOPN, Thomaston, GA - Airport: KOPN, Thomaston - Upson County, runway 30, 5,701 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: none; commercial, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review March 1, 2005; seat: left; flight hours: 7,500 total, 50 in this make and model, 7,300 as pilot in command, 160 in the last 90 days, 69 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 60° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 63 °F, dew point 37 °F - Altimeter: 30.14 inHg - Observed at: KOPN ## 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 20050428009069A](https://openairdocs.org/incident/20050428009069A), Apr 28, 2005: Piper PA20, Thomaston, GA, Substantial damage. (-23) On landing at Thomaston-Upson County Airport (opn) runway 30, aircraft pulled hard left and departed runwya approximately 150 feet after landing.… 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.