LAX00FA123 · Boeing 369D
Boeing 369D · Accident: total loss of engine power (mechanical failure) en route
From Reno Tahoe International Airport (RNO) to Yuba County Airport (MYV)
Event
- NTSB case
- LAX00FA123
- 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
- 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
Boeing 369D
- Aircraft type
- Boeing 369
- Category
- Helicopter
- 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
- N8351F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reno Tahoe International Airport (RNO), Reno, NVTo Yuba County Airport (MYV), Marysville, 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
- 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
- Tree(s)
- 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
- Engine assembly, bearing › Disintegrated
- Fluid, oil › Starvation
- Lubricating system, oil pressure pump › Seized
- Lubricating system, oil pressure pump › Sheared
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter collided with trees in a mountainous area during an attempted forced landing on a ridge line following a total loss of engine power. The pilot stated that he had been airborne approximately 25 minutes when the engine began to run erratically, and a chip detector light illuminated. He was only a few feet above the trees as he maneuvered to land when the engine stopped producing power. A quick scan of the instruments revealed that there was no oil pressure or torque. The helicopter struck a tree, and fell to the ground. Examination of the engine revealed dark, cloudy oil in the gear case sump. The upper chip detector contained debris. The No. 8 bearing cavity was dry, the shaft end nut was split and off the shaft, and the bearing was destroyed. The rotor shaft exhibited scoring at the bearing race, and was dark brown in color. The No. 6/7 bearing exhibited a similar appearance. The No. 2 shaft separated forward of the No. 6/7 bearing and exhibited a dry, deep red appearance. The Nos. 6/7 and 8 bearing oil delivery tubes were clear and dry. The oil supply line to the oil delivery tubes contained no residual oil. The oil screen in the Nos. 6/7 - 8 bearing oil supply T-fitting was clear and dry. Oil analysis discovered dark oxides that were indicative of engine lubricant starvation, and friction polymers that indicated excessive internal engine stress loads. The 3-stage oil pump was disassembled. The first (pressure) and second (gear case and No. 1 scavenge) stages were intact, visibly undamaged, turned freely, and the pump drive shaft through the two stages was intact. The pump drive shaft to the third stage was sheared. An area between the second and the third (6/7 and 8 bearing scavenge) stage of the pump and the third stage gear cavity contained small chunks of metallic debris that was determined to be bearing material. The third stage gear assembly bound when turned by finger rotation. Oil supply distribution passages in the gear case casting were clear. The check valve in the Nos. 6/7 - 8 bearing oil supply line was properly assembled and pressurized air flowed through the valve in the direction of the flow arrow on the body, and the flow checked in the reverse direction. The oil pressure relief valve was also properly assembled. The relief valve spring and poppet were visibly undamaged, and the poppet seat was smooth to the fingertip. A metallurgical analysis of the oil pump gear shaft assembly found that it conformed to the requirements and specifications of the engineering drawing and that it failed in torsional overload.
Probable cause
a loss of engine power due to oil starvation. The oil starvation was due to the seizure and failure of the turbine element oil pump shaft, which was caused by debris from a failed bearing seizing the pump. A factor in the accident was the lack of a suitable place to land following the loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00FA123
- Event ID
- 20001212X20657
- Case number
- LAX00FA123
- 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: 2ae5be552445eb2109a97e77fabae8752e9ded4ac96b2cab2c876bf98ff74274; retrieved 2026-09-21T10:41:39.347Z.