ERA12IA237 · Piper PA-32R-300
Piper PA-32R-300 · Incident: flight control system malfunction/failure during landing
From Washington Manassas Harry P. Davis Field (HEF) to Warrenton Fauquier Airport (HWY)
Event
- NTSB case
- ERA12IA237
- 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
- Incident
- 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-32R-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
- N1358H
- Operator
- Landers Morris John JR
- Onboard fatalities
- Unknown
- Route
- From Washington Manassas Harry P. Davis Field (HEF), Manassas, VATo Warrenton Fauquier Airport (HWY), Warrenton, VA
- 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
- Landing · flare/touchdown
- 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
- Flight control system malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the landing flare, the pilot heard a "boom," the airplane's nose dropped, and the airplane contacted the runway. Examination of the airplane revealed that the lower stabilator control cable turnbuckle had fractured as a result of stress corrosion cracking. An annual inspection was completed on the airplane the day before the accident. According to the airframe logbook entry, the inspection was performed in accordance with the PA32R-300 inspection checklist, which required, in part, inspection of the stabilator cable terminals and turnbuckles. The NTSB issued recommendations in 2001 to the FAA regarding the failure of control cable turnbuckles and recommending issuance of an airworthiness directive to require inspections of affected aircraft. On August 2, 2012, the FAA issued a notice of proposed rulemaking indicating the intention to adopt a new airworthiness directive (AD) that would require inspections of the stabilator control system and replacement of parts as necessary. The AD would be applicable for PA-28, PA-32, PA-34, and PA-44 airplanes.
Probable cause
Maintenance personnel's failure to identify stress corrosion cracking in the stabilator control cable during the most recent inspection, and the subsequent failure of the cable on the flight after the inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12IA237
- Event ID
- 20120320X55912
- Case number
- ERA12IA237
- 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, damage. 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: abcd205f846e04694dbc856f9e97c7c65d3b36279c1c906f1806582012e98e19; retrieved 2026-09-15T17:29:48.724Z.