FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA431 · Piper PA-28-180

4 Sept 2009 · Oroville, CA, United States

Piper PA-28-180 · Accident: loss of engine power (total) during initial climb

From Oroville Municipal Airport (OVE) to Rogers Field (O05)

Report a problem

Event

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

Piper PA-28-180

Aircraft type
Piper PA-28
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
N2482R
Operator
Phillip P Beck · private individual
Onboard fatalities
Unknown
Route
From Oroville Municipal Airport (OVE), Oroville, CATo Rogers Field (O05), Chester, 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
Initial climb
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

  • Not determined › Not determined

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

NTSB narrative

The pilot reported that during initial climb he felt three "bumps" in the airframe. The pilot then initiated a left 180-degree turn towards the departure runway. He stated that the engine was running, but not producing power. As the descent continued, the engine began to "sputter" and lose power. Subsequently, the airplane struck two fences and landed hard. During the landing roll the airplane impacted a large ditch and came to rest upright, where a postcrash fire consumed the fuselage and right wing. Examination of the recovered airframe and engine revealed no anomalies that would have precluded normal operation.

Probable cause

A total loss of engine power for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA431
Event ID
20090904X30010
Case number
WPR09LA431
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: 77dc8ee9b86faf17616315aa5981b1a3824e62bc900ae8e08915537cb9683730; retrieved 2026-09-15T12:53:23.145Z.