LAX02FA148 · Beech C23
Beech C23 · Accident: partial loss of engine power (mechanical failure) en route
From Oceano County Airport (L52) to Harris Ranch Airport (3O8)
Event
- NTSB case
- LAX02FA148
- 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
Beech C23
- Aircraft type
- Beechcraft 23
- 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
- N9180S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oceano County Airport (L52), San Luis Obispo, CATo Harris Ranch Airport (3O8), HARRIS RANCH, CA
- 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
- 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
- Engine assembly, valve, exhaust › Fractured
- Engine assembly, valve, exhaust › Separation
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 collided with trees following a loss of engine power. A passenger heard a "roar" through the four-way intercom. The certified flight instructor (CFI) and the student pilot checked the oil pressure and fuel pressure; both were "good." The CFI pointed to the left and directed the student toward a private strip. During or immediately following the left turn, the CFI said, "I've got it." The student looked back at the two passengers, and motioned with his right hand that they were going to land at the strip. The last thing that the passenger remembered was contact with the trees and coming to rest. The airplane cleared a ridge top, but collided with trees about 1/4 mile from the landing strip. The spark plug for cylinder no. 1 sustained mechanical damage and contained metallic debris. The head of the cylinder no. 1 exhaust valve was missing, and the top of the piston exhibited mechanical damage across its entire surface. Metallurgists examined the valve and cylinder. The valve stem was broken and remained in the valve guide. The stem fractured and there were numerous secondary cracks below the fracture surface. The areas around the valve seats were severely damaged. The fracture surface condition was such that the fracture mechanism could not be determined. The secondary cracks were only in a local area where the material was severely battered and deformed. Many of the cracks were slightly curved and/or did not appear to be perpendicular to the outer or inner surface. These types of cracks are most likely to occur where surfaces have overlapped, or are the result of the excessive local strains in the area. There were no material or dimensional abnormalities that would suggest fatigue. The manufacturer issued maintenance instructions describing methods for determining exhaust valve and guide condition. This maintenance function was optional for the operator, and maintenance records indicated that this had not been done. Although the diameter of the exhaust valve stem was slightly below the specified diameter, this would have a small affect on overall stresses. However, a small change in diameter of the valve stem significantly changes the amount of clearance between the exhaust valve stem and the exhaust valve guide. Excessive clearance can lead to exhaust valve sticking, which can lead to overstress fracture. The engine total time was 2,079 hours, and it had not been overhauled since it was new in 1975. The manufacturer recommended overhaul at 2,000 hours or after 12 years of service life. Given the high hours on this engine and the number of years since overhaul, it was likely that the failure was due to exhaust valve sticking.
Probable cause
the number 1 cylinder exhaust valve fractured and separated resulting in a loss of engine power and an off airport forced landing. A finding in the accident was the owner's failure to maintain the engine in accordance with the manufacturer's recommendations.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA148
- Event ID
- 20020507X00640
- Case number
- LAX02FA148
- 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 2002-04-28.
- API snapshot SHA-256: 3e64837ea615333304e61866643426b10ec695d7231f58197470f75ef4c3690a; retrieved 2026-09-20T20:02:09.426Z.