Mooney M20E accident near Corona, California, December 14, 2015
On December 14, 2015 at about 9:41 pm local time, a 1965 Mooney M20E, registered N5863Q, was substantially damaged in an accident during initial climb near Corona, California (Corona Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A partial loss of engine power during initial climb for reasons that could not be determined based on available information. Contributing to the accident was the pilot’s decision to conduct the takeoff with observed engine deficiencies.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 14, 2015 · about 9:41 pm local time · cases in 2015
- Place
- Corona, California · Corona Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Mooney M20E, built 1965 · all M20Es on the register
- Registration
- N5863Q · no longer on the register · serial 796
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot reported that the accident flight was the airplane's first flight after being painted. After completing a preflight inspection, the pilot started the engine and observed a decrease in power. He leaned the mixture slightly, and the engine rpm returned to normal idle speed. The pilot reported that during the engine run-up, he noticed that the engine had a delayed response when he increased the throttle, but that the run-up otherwise revealed no anomalies. The pilot stated that the takeoff roll took longer than expected, and after lifting off near the end of the runway, the airplane climbed more slowly than normal. The pilot stated that during the initial climb, engine power had decreased to 2,000 rpm. As the airplane reached about 100 ft above ground level, the engine was producing about 1,800 rpm and could not maintain a climb. The pilot elected to continue straight ahead rather than return to the runway, and the airplane subsequently descended into trees. A postaccident examination revealed no anomalies with the airframe or engine that would have precluded normal operation. The reason for the partial loss of engine power was not 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 initial climb defining event
- Off-field or emergency landing during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 707 hours in all; 300 in this make and model; 2 in the last 90 days; 550 as pilot in command
- Last flight review: July 19, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 4,480 hours
- Last inspection: annual inspection, August 18, 2015; 10 hours since
- Maximum gross weight: 2,575 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360 SER (piston); 140 hours total
The flight
- Departed from: AJO Corona CA at 9:41 pm
- Destination: CNO Chino Airport CA
- Flight plan: none
- Runway 25, 3,200 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 12 knots, gusting 16
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 57°F (14°C), dew point 28°F (-2°C)
- Altimeter: 29.98 inHg
- Observation at 9:56 pm from AJO, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on March 14, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Record of Email - FAA Inspector Regarding Postaccident Engine Examination | PDF, 2 pages | View Download |
| 3 | Photos from Postaccident Examination - Courtesy of the Federal Aviation Administration | PDF, 11 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N5863Q: not on the register today · the record of its deregistration
- Mooney M-20 6,246 registered today · the model family and its accident history
- Mooney 5,395 aircraft on the register
- Engine: Lycoming IO-360 SER 8,562 aircraft carry this series today · as the NTSB recorded it
- Corona Municipal · nearest airport
- Chino Airport · bound for
- Accidents and incidents in California 9,080 since 1982 · 1,093 in the last ten years
- California 28,512 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR16LA039.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
