CHI07LA151 · Piper PA 46-350P
Piper PA 46-350P · Accident: airframe, component or system failure during landing
From Marion Municipal Airport (MZZ) to UMP
Event
- NTSB case
- CHI07LA151
- 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
- N411MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marion Municipal Airport (MZZ), Marion, INTo UMP
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Landing gear, nose gear › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he crossed the "fence" at 90 knots and the touch down was soft on the main landing gear in the center of the runway. The pilot indicated that he "lightly applied toe brake pressure to slowdown the aircraft. ... Upon light toe brake pressure, we felt snap, and collapse of nose gear resulting in swerve to [left] of centerline - power setting was at IDLE when this occurred." An on-scene examination of the engine mount revealed a separation of the "new" one-piece foot design right attachment foot. Examination of the nose landing gear tire and rim revealed no pre-impact anomalies or under inflation. Examination of the engine mount revealed that "the upper aft part of the right nose gear actuator attachment foot fractured away from the rest of the engine mount. ... The fracture at the forward edge of the [right] foot had relatively smooth features on flat planes and showed curved crack arrest markings consistent with fatigue cracking from multiple origins. The fatigue cracking was evident over an arc of approximately 90 degrees; at its deepest penetration, the fatigue crack had propagated through approximately 90 percent of the estimated 0.07-inch wall thickness of the foot."
Probable cause
The fatigue separation of the engine mount's nose gear actuator attachment foot during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07LA151
- Event ID
- 20070522X00614
- Case number
- CHI07LA151
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 9cbd7ba462c54e13d8d393c8060433ede31cfc563b98f9ec5072b8dbf5134205; retrieved 2026-09-22T03:48:47.876Z.