Plane Crash in Colorado

Advertisement

Flight context

N150WR departed Centennial Airport on the morning of 7 June 2024. Shortly after takeoff the pilot noticed a slight drop in engine manifold pressure. He chose to divert toward a nearby airport rather than continue toward the planned destination. Almost immediately, an oil-pressure caution illuminated and the oil pressure rapidly decreased.

The emergency became a forced-landing problem when the engine lost all power. The pilot attempted to land on a residential street in Arvada. The aircraft struck a tree and a parked pickup truck before a post-impact fire developed. The NTSB's final investigation found that the engine failure was caused by oil starvation associated with loose turbocharger oil-line fittings.

Timeline
09:15 MDT —
N150WR departed Centennial Airport for Northern Colorado Regional Airport.
1.
About 09:27 MDT —
The pilot reported reduced manifold pressure and diverted toward Rocky Mountain Metropolitan Airport.
2.
About 09:28 MDT —
The pilot reported an oil-pressure warning and rapidly decreasing oil pressure.
3.
Minutes later —
The engine lost total power and the pilot searched for a forced-landing site.
4.
Final approach to roadway —
The pilot selected a residential street and kept the landing gear retracted to avoid obstacles.
5.
Impact —
The aircraft struck a tree, contacted the roadway and collided with a parked pickup truck.
6.
Post-impact —
A fire consumed most of the aircraft; one passenger was fatally injured, two passengers seriously injured and the pilot was uninjured.
7.

The critical sequence

The first warning was not a complete engine failure. The pilot saw a slight reduction in manifold pressure and still had an operating engine. That gave the flight a window in which to move toward a suitable landing area.

The oil-pressure indication changed the nature of the problem. Once oil pressure began falling rapidly, the aircraft was no longer dealing with a minor performance issue. An engine operating without adequate lubrication can suffer rapid internal damage, and the pilot had to assume that complete power loss was possible.

The engine examination found a missing bolt and three loose bolts associated with oil-line adapter fittings. Investigators found evidence of oil starvation, including connecting-rod and bearing damage. The engine oil and filter had been replaced in the days before the accident, but the maintenance work did not require loosening the fittings that later became loose.

The forced landing occurred in a residential area. The pilot attempted to use a roadway, but the road environment contained obstacles. The aircraft struck a tree before contacting the road and a parked vehicle. The accident illustrates the importance of selecting a landing area early, while altitude and airspeed still provide choice.

ATC decisions during the event

The NTSB released a partial ATC transcript as part of the investigation. ATC and another aircraft provided information during the emergency, but the critical problem was ultimately physical: the engine had lost its ability to produce power. Once the aircraft was descending toward an urban area, the controller could provide information but could not create a safe landing surface. The cockpit's available altitude and the pilot's selection of a landing area were therefore decisive.

Investigation and aftermath

The NTSB determined that the probable cause was a total loss of engine power due to oil starvation as a result of loose turbocharger oil-line fittings. The investigation could not conclusively determine how and when the fittings became loose. The engine examination, however, established the lubrication failure and the resulting internal damage.

The maintenance history is important but does not establish that the recent maintenance directly caused the loose fittings. The technician had changed the engine oil and filter and worked on exhaust hardware in the same general area, but the documented exhaust work did not require the turbocharger oil-line fittings to be loosened. The NTSB therefore identified the mechanical failure mechanism without claiming that it could determine exactly when or how the fittings became loose.

What the record establishes

The NTSB's final evidence identifies an oil-starvation sequence. N150WR initially showed a slight drop in manifold pressure, then the oil-pressure caution light illuminated and pressure fell rapidly. Examination found one missing bolt and three loose bolts at turbocharger oil-line adapter fittings. Witnesses saw smoke consistent with oil contacting hot exhaust components, and engine examination found lubrication distress and a separated No. 5 connecting rod. The pilot survived, two passengers were seriously injured and a third passenger was fatally injured. The NTSB concluded that total engine-power loss resulted from oil starvation caused by the loose turbocharger oil-line fittings.

What the sequence shows

CEN24FA212 is valuable because the mechanical chain is unusually clear while the maintenance history remains nuanced. The aircraft had recent maintenance near the engine, but investigators did not conclude that the maintenance directly caused the loose fittings. The correct lesson is not to assign unsupported blame; it is to understand that an oil-pressure warning must be treated as a potentially imminent total-power emergency.

  • Treat rapidly falling oil pressure as a possible imminent engine failure.
  • Move toward the best landing option while altitude remains available.
  • Select forced-landing areas with obstacle clearance in mind.
  • Do not assume recent maintenance explains a failure without supporting evidence.
  • Emergency planning should anticipate total power loss after an oil-system warning.

Accident facts

Date
7 June 2024
Aircraft
Beech V35A Bonanza
Registration
N150WR
Location
Arvada, Colorado
Operation
Part 91 personal flight
Defining event
Total loss of engine power
Outcome
1 passenger fatality; 2 passengers seriously injured; pilot uninjured
Investigation
NTSB CEN24FA212

Sources

Sources
Primary investigation: NTSB CEN24FA212. Supporting sources: Aviation Safety Network or equivalent accident database for cross-reference; ATC/radar or docket material where released; contemporary newspaper/aviation reporting for context only. Primary-source facts and official probable-cause wording take precedence over secondary reporting.
Advertisement

Primary investigation record

Primary Investigation Reference

NTSB accident number: CEN24FA212

The weekly incident