FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA212 · Beech V35A

7 Jun 2024 · Arvada, CO, United States

Whiskey Romeo Beech V35A · Accident: loss of engine power (total) en route

From Centennial Airport (APA) to Northern Colorado Regional Airport (FNL)

Report a problem

Event

NTSB case
CEN24FA212
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 V35A

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
N150WR
Onboard fatalities
Unknown
Route
From Centennial Airport (APA), Centennial, COTo Northern Colorado Regional Airport (FNL), Fort Collins / Loveland, CO
Aircraft age
About 55 years (built 1969)
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 · climb to 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
Loss of engine power (total)
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

  • Aircraft › Aircraft power plant
  • Aircraft › Fluids/miscellaneous hardware

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

NTSB narrative

The pilot reported that shortly after takeoff he noticed a slight drop in engine manifold pressure, but the airplane was still able to climb. He chose to divert to a nearby airport, and shortly thereafter, noticed that the oil pressure caution light had illuminated and oil pressure was rapidly decreasing. The engine subsequently lost total power. The pilot performed a forced landing on a residential street, during which the airplane impacted a tree and a parked pickup truck. The airplane was consumed by a postimpact fire. Examination of the airplane after it was recovered from the accident site revealed one missing bolt and three loose bolts associated with the oil line adapter fittings on the engine turbocharger. Police photos confirmed that the missing bolt was missing from the top oil line fitting at the accident site before the wreckage was moved. Three witnesses along the route of flight saw smoke emanating from the airplane, consistent with leaking oil contacting hot exhaust components during the flight. An engine examination revealed signatures consistent with an oil starvation event. The No. 5 connecting rod separated from the crankshaft, and the No. 5 connecting rod journal exhibited lubrication distress and smeared bearing material. The other connecting rod journals and main bearing journals showed varying degrees of discoloration from heat and lubrication distress. The engine oil and filter were replaced in the days before the accident. Additionally, the maintenance technician also replaced exhaust/muffler hardware in the vicinity of the missing and loose oil line fitting bolts; however, this would not have required loosening the oil line fitting bolts. The technician stated that there were no fluid leaks identified during a post-maintenance engine run and leak check. The pilot reported that when he retrieved the airplane after maintenance, he checked the oil and performed a thorough preflight inspection before takeoff and did not observe any discrepancies during a 50-mile flight the day before the accident. Based on the available evidence, the engine lost total power due to an oil starvation event as a result of the loose turbocharger oil line fittings, which allowed for an oil leak. Although the engine had undergone recent maintenance in the vicinity of the loose oil line fittings, the associated maintenance tasks did not require the those fittings to be loosened or removed. As such, the investigation could not conclusively determine how and when the oil line fittings became loose.

Probable cause

A total loss of engine power due to oil starvation as a result of loose turbocharger oil line fittings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA212
Event ID
20240607194416
Case number
CEN24FA212
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: investigation status, coordinates, cause areas. 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: b02d98663e123faf7e8f5421a0825750a8834e4b293f9c263ef1e50508f33464; retrieved 2026-09-15T08:16:24.879Z.