LAX06FA126 · Cessna 414A
Cessna 414A · Accident: loss of engine power on approach
From KHNL · Honolulu, HI to KOGG · Kalului, HI
Event
- NTSB case
- LAX06FA126
- 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
- 3 · 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
Cessna 414A
- Aircraft type
- Cessna 414
- 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
- N5601C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From KHNL · Honolulu, HITo KOGG · Kalului, HI
- 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
- Approach · VFR pattern final
- 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
- Loss of engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vmc), not maintained
- Pilot in command › Procedures/directives, not followed
- Pilot in command › Stall/spin, encountered
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The twin-engine medical transport airplane was on a positioning flight when the pilot reported a loss of power affecting one engine before impacting terrain 0.6 miles west of the approach end of the runway. The airplane was at 2,600 feet and in a shallow descent approximately 8 miles northwest of the airport when the pilot checked in with the tower and requested landing. Three and a half minutes later, the pilot reported that he had lost an engine and was in a right-hand turn. Radar data indicated that the airplane was 2 miles southwest of the airport at 1,200 feet msl. The radar track continued to depict the airplane in a descent and in a right-hand turn, approximately 1.9 miles west of the approach end of the runway. The altitude fluctuated between 400 and 600 feet, the track turned right again, and stabilized on an approximate 100-degree magnetic heading, which put the airplane on a left base for the runway. The track entered a third right-hand turn at 500 feet. The pilot's last transmission indicated that one engine was not producing power. The last radar return was 6 seconds later at 200 feet, in the direct vicinity of where the wreckage was located. Using the radar track data, the average ground speed calculations showed a steady decrease from 134 knots at the time of the pilot's initial report of a problem, to 76 knots immediately before the airplane impacted terrain. The documented minimum controlable airspeed (Vmc) for this airplane is 68 knots. The zero bank angle stall speed varied from 78 knots at a cruise configuration to 70 knots with the gear and flaps down. A sound spectrum study using recorded air traffic control communications concluded that one engine was operating at 2,630 rpm, and one engine was operating at 1,320 rpm. Propeller damage was consistent with the right engine operating at much higher power than the left engine at the time of impact, and both propellers were at or near the low pitch stops (not feathered). Examination and teardown of both engines did not reveal any evidence of mechanical malfunction. Investigators found that the landing gear was down and the flaps were fully deployed at impact. In this configuration, performance calculations showed that level flight was not possible with one engine inoperative, and that once the airspeed had decreased below minimum controllable airspeed (Vmc), the airplane could stall, roll in the direction of the inoperative engine, and enter an uncontrolled descent. The pilot had been trained and had demonstrated a satisfactory ability to operate the airplane in slow flight and single engine landings. However, flight at minimum controllable airspeed with one engine inoperative was not practiced during training. The operator's training manual stated that during single engine training an objective was to ensure the pilot reduced drag; however, there was no procedure to accomplish this objective, and the ground training syllabus did not specifically address engine out airplane configuration performance as a dedicated topic of instruction. The operator's emergency procedures checklist and manufacturer's information manual clearly addressed the performance penalties of configuring the airplane with an inoperative engine, propeller unfeathered, the landing gear down, and/or the flaps deployed. The engine failure during flight procedure checklist and the engine inoperative go-around checklist, if followed, configure the airplane for level single engine flight by feathering the propeller, raising the flaps, and retracting the landing gear.
Probable cause
The failure of the pilot to execute the published emergency procedures pertaining to configuring the airplane for single engine flight, which would have allowed him to maintain minimum controllable airspeed (Vmc) and level flight. The pilot's failure to maintain minimum controllable airspeed (Vmc) led to a stall and subsequent Vmc roll at a low altitude. Contributing to the accident was the operator's inadequate pilot training in the single engine flight regime, and the loss of power from the left engine for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06FA126
- Event ID
- 20060313X00294
- Case number
- LAX06FA126
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-03-09.
- API snapshot SHA-256: b80040b35012dcc93046a535bc07e0be957a5ff110a7ca2cdeea1eb0d3bf4f9a; retrieved 2026-09-20T17:30:07.489Z.