FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA087 · Cessna 172F

17 Dec 2009 · Corona, CA, United States

Cessna 172F · Accident: loss of engine power (total) on approach

From Corona Municipal Airport (AJO) to Corona Municipal Airport (AJO)

Report a problem

Event

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

Cessna 172F

Aircraft type
Cessna 172
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
N8520U
Operator
Fly Corona
Onboard fatalities
Unknown
Route
From Corona Municipal Airport (AJO), Corona, CATo Corona Municipal Airport (AJO), Corona, 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
Approach · VFR pattern base
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 after he was established on the downwind leg for landing the engine experienced a partial loss of power, followed by a total power loss after turning into the base leg. The pilot subsequently made an emergency descent and forced landing to an open field. The airplane hit a fence and nosed over, sustaining substantial damage to both wings. A Federal Aviation Administration inspector reported that an examination of the airframe and engine revealed no anomalies that would have precluded normal operation. Atmospheric conditions at the time of the accident were not conducive to the formation of carburetor ice. The reason for the reported loss of engine power could not be determined.

Probable cause

A loss of engine power for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA087
Event ID
20091217X01559
Case number
WPR10LA087
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: e43ae0b5d28a8d4d6c20635b366d3ef7d90aac9aa019993716ce994bf82f8c0e; retrieved 2026-09-15T13:34:40.489Z.