FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00FA300 · Beech K35

14 Aug 2000 · NEWBERRY SPRING, CA, United States

Beech K35 · Accident: airframe, component or system failure en route

From Eagle Airpark (A09) to Zamperini Field (TOA)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX00FA300
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
1 · all aircraft and ground
Ground fatalities
0
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 K35

Aircraft type
Beechcraft 35
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
N878R
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Eagle Airpark (A09), Needles, AZTo Zamperini Field (TOA), Torrance, 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
Airframe, component or system 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, crankshaft › Failure, total

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

NTSB narrative

At 1247, during cruise flight, the pilot advised the radar controller that he had a little oil leak on his windshield. The severity of the leak increased, and 5 minutes later oil had covered the front windshield thus precluding visibility. One minute later, the pilot announced that he had "totally lost oil pressure." Prior to the engine seizing, the pilot attempted to make a forced landing on an interstate freeway. During flare, the airplane impacted three automobiles, cartwheeled, and came to rest upside down. Three days before the accident, the pilot had flown his airplane from Torrance, California, to Bullhead City, Arizona. En route, an engine oil leak became evident, which inhibited the pilot's ability to see through the front windshield. The pilot believed that engine oil was leaking past the engine's crankcase nose seal, aft of the propeller, and that replacing the seal would resolve the leakage problem. (Seepage had been documented in this crankshaft area during the last annual inspection that was completed 21 engine operational hours earlier.) The pilot flew 16 miles to near Needles, California, where repair services were available. Upon arrival, oil was dripping off the engine, and the pilot was advised by an engine shop to have the engine removed and repaired. The pilot declined indicating that he had insufficient funds. Instead, the pilot purchased the nose seal parts from the engine shop, and he hired a local independent mechanic to install them in his airplane. Upon completion of the maintenance, the mechanic requested that the pilot perform a ground run-up to check for leaks. The pilot declined and took off. The accident occurred about 40 minutes later, 92 miles from Needles. In 1986, about 537 engine operational hours earlier, the airplane's landing gear collapsed and the propeller was damaged. The crankcase was found cracked on its front, right side, and the engine was overhauled. The case was repaired, according to the maintenance records. During the last annual inspection, oil seepage was noted on the front, right side of the case. During the accident investigation, a weld was noted on the front, right side of the case, and electrical arc marks were noted about 2.3 inches inside the crankshaft bore. The crankshaft was found to have fractured, and the fracture had originated at the site of the arc marks creating a stress riser in the crankshaft. As the fracture progressed, it provided an avenue for oil to escape from the crankshaft and propagate through the nose seal.

Probable cause

The crankshaft's fatigue failure at the site of an electrical arc mark stress riser, during cruise flight. Contributing factors were the pilot's inadequate preflight inspection, improper decision, and maintenance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00FA300
Event ID
20001212X21751
Case number
LAX00FA300
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: c184f68822655c594f2a50ed3fff5b98bb070124b63fe4deba0fd87b1f788005; retrieved 2026-09-20T20:56:34.727Z.