ERA11LA224 · Piper PA 46-350P
Piper PA 46-350P · Accident: landing area undershoot
From Frederick W. Smith International Airport (MEM) to Lakefront Airport (NEW)
Event
- NTSB case
- ERA11LA224
- 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
- N146DG
- Operator
- Allan R. Garner · private individual
- Onboard fatalities
- Unknown
- Route
- From Frederick W. Smith International Airport (MEM), Memphis, TNTo Lakefront Airport (NEW), New Orleans, LA
- 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
- 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 area undershoot
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was climbing through 13,000 feet when the pilot heard a loud "pop" and observed a large reduction in manifold pressure. He declared an emergency to an air traffic controller and initiated a slow descent to the nearest airport recommended by the controller. The pilot asked the controller if there was a mechanic at that airport and the controller stated that there was not but that a mechanic was available at another airport. The pilot elected to go to the other airport, which was farther away.
The pilot acquired the airport visually but was initially a little high and planned to enter the traffic pattern on a downwind leg for the opposite runway; the pilot lowered the landing gear to assist in losing altitude. However, the airplane was then low and the airspeed was decreasing. The pilot subsequently decided to abandon the downwind approach and land straight-in to the runway. The oil pressure gauge indicated zero and the oil warning light illuminated. The pilot continued to run the engine until he thought he could reach the runway, and then he shut down the engine. He subsequently raised the landing gear as the airplane became low, but the airspeed also decreased. He realized that he was not going to reach the runway and lined up with a grassy area short of the runway to avoid colliding with the instrument landing system. He extended the landing gear and flaps and the airplane touched down and collided with a ditch.
A postaccident examination of the engine assembly revealed that the right turbocharger would not rotate when actuated by hand. The turbocharger was removed and oil was noted in the compressor outlet tubing. Several of the blades were broken and some were bent near the tip in the direction opposite of rotation. Metallurgical examination of the right turbocharger revealed that the turbine wheel assembly failed due to a fatigue fracture of one of the turbine wheel blades, which led to an imbalance of the turbine wheel.
Probable cause
The pilot did not obtain the proper touchdown point as a result of his decision to shut down the engine and to deploy the landing gear and flaps before the landing was assured. Contributing to the accident was his decision to overfly a closer suitable airport and the fatigue fracture of a turbine blade in the right turbocharger, which led to an imbalance of the turbine wheel and the subsequent failure of the turbocharger.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA224
- Event ID
- 20110403X25733
- Case number
- ERA11LA224
- 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, 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: a6765345c4df9eefe432f455a97f9b0e646147503a3ae6263ab54c14be6c7bdb; retrieved 2026-09-15T15:59:57.411Z.