LAX08LA168 · Mkii Corporation Lancair Legacy 2000
Lancair International Mkii Corporation Lancair Legacy 2000 · Accident: powerplant system/component malfunction/failure en route
From Yuba County Airport (KMYV) to Roberts Field (KRDM)
Event
- NTSB case
- LAX08LA168
- 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
Mkii Corporation Lancair Legacy 2000
- Aircraft type
- Mkii LANCAIR LEGACY 2000
- 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
- N199L
- Operator
- Lancair International
- Onboard fatalities
- Unknown
- Route
- From Yuba County Airport (KMYV), Marysville, CATo Roberts Field (KRDM), Redmond, OR
- 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 · 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
- Powerplant system/component malfunction/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
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While at 9,000 feet, the engine lost oil pressure, suddenly oversped (3,560 rpm), and lost power. The pilot made a dead-stick approach to a nearby runway. During the landing flare the airplane's main landing gear impacted a trench and sheared off just short of the runway. The airplane slid down the runway on its nose gear, main mount struts, and tail. The airplane then veered off to the right and departed the runway. Examination of the engine revealed a 4- to 5-inch diameter hole in the top of the engine case above the No. 3 cylinder. Further examination revealed that the No. 3 connecting rod of the engine had failed due to fatigue just below the wrist pin. The loose end of the connecting rod produced metal shavings that obstructed the oil pickup tube as the crankshaft continued to rotate. The blocked tube led to oil starvation, propeller overspeed, and catastrophic engine failure. Material Laboratory testing revealed that the connecting rod fatigue fracture was located in a decarburized region of the rod. The engine manufacturer could not identify the connecting rod as a component supplied by them.
Probable cause
A total loss of engine power due to the fatigue failure of the Number 3 cylinder connecting rod.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08LA168
- Event ID
- 20080611X00835
- Case number
- LAX08LA168
- 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: 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 2008-06-09.
- API snapshot SHA-256: 33505e96a08cd69b07b951c8d68fb84e4a2548d4b4108168606e2da360424822; retrieved 2026-09-15T09:45:21.177Z.