ERA13LA148 · Piper PA-32-300
Piper PA-32-300 · Accident: system/component malfunction/failure (non-power) on approach
From 5W8 · Siler City, NC to Raleigh Executive Jetport (TTA)
Event
- NTSB case
- ERA13LA148
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-32-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N1953H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 5W8 · Siler City, NCTo Raleigh Executive Jetport (TTA), Sanford, NC
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern downwind
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was in the traffic pattern at the intended destination airport when the airplane experienced a loss of engine throttle control. Unable to reach the runway, he elected to perform a forced landing in a nearby field. During the landing, the airplane struck a fence post, which resulted in substantial damage to the left wing of the airplane.
Postaccident examination revealed that the throttle lever clevis and throttle cable became separated from the throttle arm, which resulted in the engine being unresponsive to throttle input; thus, the pilot could not apply power to the engine from the idle position. No evidence of metal deformation existed on either the throttle lever clevis or on the throttle cable; however, examination of the cotter pin revealed that one prong was separated and unable to be located. Examination of the remaining portion of the cotter pin revealed that it was twice as long as manufacturer-approved guidance required. Examination of the clevis for the propeller cable linkage revealed that the cotter pin prongs exceeded Federal Aviation Administration Advisory Circular 43-13-1B guidance by allowing the prong to exceed the pin diameter and the cotter pin prongs were not seated firmly against the shank. A review of maintenance records did not reveal when the cotter pin was replaced. The hardware was likely installed using the incorrect safetying technique and the improper length of cotter pin. This allowed the prong to become caught and subsequently fracture on nearby hardware, which resulted in the cotter pin becoming unsecured and separating from the linkage pin. Subsequently, the linkage pin detached, which allowed the throttle lever clevis and cable to separate from each other. The last annual inspection occurred 2 weeks and less than 1 flight hour before the accident. It is likely that the mechanic did not detect the incorrect cotter pin and safetying technique due to its location; the location was such that it would have been difficult for the mechanic to see.
Probable cause
The installation of an incorrect length of cotter pin on the throttle linkage clevis pin by maintenance personnel at an undetermined time, which resulted in the pin coming loose and the loss of throttle control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA148
- Event ID
- 20130227X63724
- Case number
- ERA13LA148
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e7d5fe8a205519e2a1231f3688c2193c70262926676b77cd26d1e7e4c6ac3ff1; retrieved 2026-09-15T21:01:20.964Z.