FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX01FA186 · Beech M35

19 May 2001 · North Las Vegas, NV, United States

Beech M35 · Accident: total loss of engine power (mechanical failure) en route

From North Las Vegas Airport (VGT) to North Las Vegas, NV

Report a problem

Event

NTSB case
LAX01FA186
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
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 M35

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
N9820R
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Las Vegas Airport (VGT), North Las Vegas, NVTo North 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
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
Total loss of engine power (mechanical failure)
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
Pole
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

  • Fluid, oil › Exhaustion
  • Lubricating system, oil filter/screen › Stripped thread
  • Owner/pilot mechanic › Maintenance, improper

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 obstructions during a forced landing precipitated by a loss of engine power. In a radio exchange with the control tower, the pilot reported a total loss of oil pressure. The airplane had accrued about 1 hour of flight time since a owner-assisted annual inspection was accomplished during which the owner changed the oil and filter element. Post accident examination of the underside of the forward fuselage/engine compartment area revealed an oil filter element hanging free from the oil filter base by the installation safety wire and fresh oil on the underside of the fuselage. The airplane had a STC'd remote mounted oil filter base that used a screw on filter element. The installation location was in the aft engine compartment on the forward side of the firewall, requiring a blind insertion of the element by feel only onto the threaded shaft. The only way to see the element pad and threaded shaft is by mirror or by looking up through the right cowl flap with a light. Examination of the filter base revealed evidence of thread damage to the first complete thread in the bore. The first 5 or 6 threads of the shaft were damaged, also with a cross the thread appearance to the first 2 or 3 threads. Other threads were damaged and had the appearance of attempted file repair. Both ends of the shaft revealed internal damage to the bore of the shaft. During manufacture, the shaft is permanently factory installed to a depth about 5 threads with red Locktite and torqued into the base. No evidence of Locktite was noted on the shaft or in the base bore. According to the Aircraft Maintenance Technician and IA who approved the annual inspection, the pilot/owner had recently commented to him that other filter elements could be used besides the one specified for the system. The pilot reportedly told the mechanic that you could either unscrew the 3/4-16 shaft from the other elements or the ones without a shaft could be screwed onto the shaft in the base unit.

Probable cause

The pilot/owner's failure to correctly install the oil filter, which resulted in oil exhaustion and a loss of engine power. Also causal was his attempt to modify the design of the oil filter element adapter by breaking the bond between the base and the threaded shaft, which resulted in a loss of torque during filter element installation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX01FA186
Event ID
20010523X01010
Case number
LAX01FA186
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: aed74f7a66f6a7c922667ddb20ca3d31239f080b848c440e669b2eeb323827a3; retrieved 2026-09-20T20:32:47.705Z.