FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07FA035 · Cessna 421B

14 Nov 2006 · Big Bear Lake, CA, United States

Cessna 421B · Accident: partial loss of engine power (mechanical failure) during initial climb

From Big Bear City Airport (L35) to Harry Reid International Airport (KLAS)

Report a problem

Event

NTSB case
LAX07FA035
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 421B

Aircraft type
Cessna 421
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
N642BD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Big Bear City Airport (L35), Big Bear Lake, CATo Harry Reid International Airport (KLAS), Las Vegas, NV
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
Initial climb
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
Partial loss of engine power (mechanical failure)
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

  • Exhaust system, turbocharger › Fractured
  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Airspeed(v2 min), not obtained/maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Witnesses said that it appeared that the left engine sustained a loss of power just after rotation and liftoff. The airplane initially had a positive rate of climb, but then immediately yawed to the left as it cleared 30-foot-high power lines that were perpendicular across the flight path. The airport is at the east end of a lake in a mountain valley; the airplane departed to the west and was flying over the lake. The airplane was about 2 miles from the runway when witnesses observed dark smoke coming from the left engine, and the smoke increased significantly as the flight continued. The airplane banked hard left with the wings perpendicular to the ground, and then nosed in vertically. The landing gear remained down throughout the accident sequence. On site examination revealed that the top spark plugs for the left engine were black and sooty. A detailed examination revealed that the left turbocharger turbine wheel shaft fractured and separated. Extreme oxidation of the fracture surfaces prevented identification of the failure mode; however, the oxidation was the result of high temperature exposure indicating that the fracture occurred while the turbocharger was at elevated temperature during operation. The multiple planes exhibited by the fracture also were not consistent with a ductile torsional failure as would be expected from a sudden stoppage of either rotor. No evidence of a mechanical malfunction was noted to the right engine. The Cessna Owners Manual for the airplane notes that the most critical time for an engine failure is a 2-3 second period late in the takeoff while the airplane is accelerating from the minimum single-engine control speed of 87 KIAS to a safe single-engine speed of 106 KIAS. Although the airplane is controllable at the minimum control speed, the airplane's performance is so far below optimum that continued flight near the ground is improbable. Once 106 KIAS is achieved, altitude can more easily be maintained while the pilot retracts the landing gear and feathers the propeller. The best single-engine rate-of-climb is 108 KIAS with flaps up below 18,000 feet msl. Section VI of the manual provides operational data for single-engine climb capability. The data was only valid for the following conditions: gear and flaps retracted, inoperative propeller feathered, wing banked 5 degrees toward the operating engine, 39.5 inches of manifold pressure if below 18,000 feet, and mixture at recommended fuel flow.

Probable cause

Failure of the turbine wheel shaft in the left turbocharger during the takeoff initial climb for undetermined reasons, and the pilot's failure to attain and maintain safe single engine airspeed that led to a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07FA035
Event ID
20061116X01682
Case number
LAX07FA035
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: d2102538eadfb66b5ca84c06fec761d40b8232d97d6ecd45c95367a8ed98afb9; retrieved 2026-09-20T16:59:20.379Z.