FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA237 · Piper PA 46-350P

16 Apr 2010 · Parkersburg, WV, United States

P & C Aviation Piper PA 46-350P · Accident: landing gear collapse

From Charlotte Douglas International Airport (CLT) to Mid Ohio Valley Regional Airport (PKB)

Report a problem

Event

NTSB case
ERA10LA237
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 46-350P

Aircraft type
Piper PA-46
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
N779MA
Onboard fatalities
Unknown
Route
From Charlotte Douglas International Airport (CLT), Charlotte, NCTo Mid Ohio Valley Regional Airport (PKB), Parkersburg, WV
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 · landing roll
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
Landing gear collapse
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 systems
  • Organizational issues › Development

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During landing, the airplane veered hard to the right when the nose gear was lowered to the runway after touchdown. The pilot attempted to maintain directional control with rudder input, but the airplane veered to the right and departed the runway. Initial examination of the airplane at the site revealed that the nose landing gear had collapsed and the attachment components between the nose landing gear actuator and the engine mount were fractured. Each of the right and left two-piece attachment feet were fractured at the nose landing gear actuator attach location. Detailed examination of the right foot showed evidence of fatigue, which covered a 0.75-inch arc and approximately 0.04 inches of the 0.06-inch wall thickness of the foot. The left foot also showed evidence of fatigue, which covered a 0.35-inch arc and was approximately 0.03 inches deep.

The manufacturer had issued a series of Service Bulletins (SB 1103, with subsequent revisions A, B, and C) for PA-46-350P models that required inspections for cracks in the engine mounts in the areas of the nose landing gear actuator attachment feet. Inspections were to take place at the next regularly scheduled maintenance event, and at each 100 hours time in service or annual inspection, whichever occurred first. Records showed that SB 1103B was accomplished on the accident airplane during an annual inspection in 2007, but records of subsequent annual inspections in 2008 and 2009 showed that SB1103 was not accomplished. Previous nose gear failures and runway excursions resulted in the redesign of the original engine mount due to compliance (flexibility) in the engine mount actuator attach feet structure. This compliance issue was sometimes exasperated at various speeds, resulting in a high speed shimmy effect and subsequent uncommanded left or right turn of the nose wheel during takeoff and/or landing. The new engine mount incorporates a one piece design at the actuator attach point, eliminating the two piece feet design. The one piece design provides a less compliant structure, which prevents relative motion between the two feet in the original engine mount design.

The Federal Aviation Administration did not mandate the actions outlined in SB 1103B, but compliance could have alerted the operator of any problems because the SB inspection criteria called for examinations of the engine mount in the areas where the fatigue cracks were located. Replacement of the engine mount with the new design that had one-piece nose landing gear actuator attachment feet would have relieved the operator of the manufacturer's repetitive inspection requirement, but because the accident airplane still had the welded two-piece attachment feet it was subject to the repetitive inspection per the service bulletin.

Probable cause

The inadequate design of the engine mount by the manufacturer, resulting in collapse of the nose landing gear. Contributing to the accident was the failure of the operator to adhere to the manufacturer's suggested engine mount inspection schedule.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA237
Event ID
20100420X00326
Case number
ERA10LA237
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: ff9fa48dff1c77cdaa8f74cdcd4d44ba2c56f8dec68665b8088c1132475e07cd; retrieved 2026-09-15T13:52:37.179Z.