Cessna 172F accident near Corona, California, December 17, 2009
On December 17, 2009 at about 10:35 pm local time, a Cessna 172F, registered N8520U, was substantially damaged in an accident during approach (VFR pattern base) near Corona, California (Corona Municipal airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 17, 2009 · about 10:35 pm local time
- Place
- Corona, California · Corona Municipal · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172F · all 172Fs on the register
- Registration
- N8520U · no longer on the register · serial 17252420
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during approach (VFR pattern downwind)
- Loss of engine power (total) during approach (VFR pattern base) defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 90 hours in all; 3 in this make and model; 2 in the last 90 days; 90 as pilot in command
- Last flight review: October 30, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 8,700 hours
- Last inspection: 100-hour inspection, October 23, 2009; 100 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-300-D (piston); 0 hours total
The flight
- Departed from: AJO Corona CA at 10:20 pm
- Destination: AJO Corona CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 150° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 30°F (-1°C)
- Altimeter: 29.98 inHg
- Observation at 10:55 pm from AJO, 4 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.