FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA284 · Piper PA-46-310P

10 Jun 2010 · Ontario, CA, United States

Piper PA-46-310P · Accident: loss of engine power (total) en route

From Santa Monica Municipal Airport (SMO) to Lake Havasu City Airport (HII)

Report a problem

Event

NTSB case
WPR10LA284
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-310P

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
N121HJ
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Lake Havasu City Airport (HII), Lake Havasu, AZ
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
En route · climb to cruise
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
Loss of engine power (total)
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
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting a cross-country flight with a certified flight instructor (CFI). During the climb-to-cruise phase of the flight, as the airplane was ascending through 16,000 feet mean sea level (msl), the pilot noticed a reduction in manifold pressure. He advanced the throttle and observed an increase of one or two inches of manifold pressure. Shortly thereafter, the pilot heard a loud bang originate from the engine followed by an immediate loss of engine power.

The pilot and CFI attempted to troubleshoot the engine anomalies and noted that it seemed to respond with the low boost "on", however it began to run rough whenever the throttle was advanced more than half way. They diverted to a nearby airport and conducted an emergency descent. As the airplane approached the airport, the pilot descended through an overcast cloud layer and attempted to enter the airport traffic pattern. While on final approach to the airport, the pilot thought the airplane was high and extended the landing gear and applied flaps. Shortly thereafter, the airspeed and altitude decreased drastically and the pilot realized he was too low. The pilot applied throttle and noticed no change in engine performance. The airplane subsequently struck a fence and landed hard in an open field just short of the airport, which resulted in structural damage to the fuselage and wings.

A postaccident examination of the engine revealed that the induction elbow for cylinders 1-3-5 (right side) was displaced from the throttle and metering assembly where the elbow couples with the throttle and metering assembly by an induction hose and clamp. The clamp was secure to the induction hose, however, the portion of the clamp that should have been installed beyond the retention bead on the throttle and control assembly was observed on the inboard side of the bead on the induction elbow. Review of the aircraft maintenance logbooks revealed that cylinders 4 and 5 were recently replaced prior to the accident flight due to low compression. The replacement of these cylinders required removal of the induction system to allow for cylinder removal and installation. In addition, a manufacturer service bulletin stated that during the reinstallation of the induction system, one must slide the induction hose and clamp(s) onto one of the tubes to be joined and that the connection joint and both tube beads are to be positioned in the center of the induction hose. The clamps should be installed in a position centered between the tubing bead and end of the induction hose.

Probable cause

A loss of engine power due to the in-flight separation of the 1-3-5 cylinder induction tube elbow, which was caused by the improper installation of the induction tube elbow by maintenance personnel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA284
Event ID
20100611X54536
Case number
WPR10LA284
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: 72899b70377c4726b2d76a4d69611d9f4fa21d694f3eaeee375c2958d20c3859; retrieved 2026-09-15T14:26:19.971Z.