FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA337 · Engineering & Research 415C

11 Jul 2009 · Corona, CA, United States

Engineering & Research 415C · Accident: loss of engine power (total) en route

From Flabob Airport (RIR) to Oceanside Municipal Airport (OKB)

Report a problem

Event

NTSB case
WPR09LA337
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
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

Engineering & Research 415C

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
N87295
Onboard fatalities
Unknown
Route
From Flabob Airport (RIR), Rubidoux, CATo Oceanside Municipal Airport (OKB), Oceanside, 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
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
Substantial

Cause areas

  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that the airplane's engine began to experience a degradation of power about 15 minutes after takeoff and he maneuvered the throttle to full power in an effort to recover the power loss. The engine rpm increased temporarily and then decreased again, with an eventual total loss of power. During the forced landing, the airplane collided with a house and had come to rest in a field 30 feet from the initial impact. The post accident investigation revealed several anomalies with the engine and modifications that were not in accordance with engine manufacturer's recommended maintenance practices. The owner/pilot reported that the airplane had undergone an annual inspection about eight months prior to the accident and had only flown a couple of hours since. At the conclusion of the examination, the exact cause of the engine failure could not be definitively identified.

Probable cause

A total loss of engine power during cruise flight for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA337
Event ID
20090713X00747
Case number
WPR09LA337
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. 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: a539fe06f11d4b4849a23cd550d913a582f4bd95e1ede9b9c6bebe2e8b60bbae; retrieved 2026-09-15T11:49:13.401Z.