Mooney M20J accident near Pacoima, California, February 22, 2016
On February 22, 2016 at about 9:34 pm local time, a 1978 Mooney M20J, registered N201KY, was substantially damaged in an accident during initial climb near Pacoima, California (Whiteman 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 total loss of engine power for reasons that could not be determined because postaccident examination did not reveal any evidence of preimpact mechanical failures or malfunctions that would have precluded normal operation.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 22, 2016 · about 9:34 pm local time · cases in 2016
- Place
- Pacoima, California · Whiteman · 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 M20J NO SERIES, built 1978 · all M20Js on the register
- Registration
- N201KY · no longer on the register · serial 24-0462
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
About 3 minutes after takeoff, the engine started to run roughly. The private pilot contacted the tower controller and advised that he was turning back to the runway. While on short final, he pulled back on the power, and the engine lost total power. The pilot was able to restart the engine, but it again lost total power. The airplane was unable to reach the runway, and the pilot subsequently initiated a forced landing to a street, during which, the airplane struck a moving car and numerous parked vehicles. A postaccident engine test run did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The reason for the 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 (total) during initial climb defining event
- 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
- Environmental issues › Physical environment › Object/animal/substance › (general) › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 952 hours in all; 176 in this make and model; 17 in the last 90 days; 14 in the last 30 days; 952 as pilot in command
- Last flight review: December 25, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,052 hours
- Last inspection: annual inspection, February 1, 2013
- Maximum gross weight: 2,899 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360 1A (piston); 2,058 hours total
The flight
- Departed from: WHP Pacoima CA at 9:00 pm
- Destination: WHP Pacoima CA
- Flight plan: none
- Runway 30, 4,120 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 330° at 14 knots, gusting 21
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 19°F (-7°C)
- Altimeter: 29.97 inHg
- Observation at 9:36 pm from KWHP
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on January 4, 2018. 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 | Pilot Written Statement | PDF, 2 pages | View Download |
| 3 | Witness Statements | PDF, 2 pages | View Download |
| 4 | Emailed Statement of Mechanic | PDF, 1 page | View Download |
| 5 | FAA Inspector Statement of Investigation | PDF, 4 pages | View Download |
| 6 | Airframe & Engine Examination Report | PDF, 6 pages | View Download |
| 7 | Aircraft Logbook | PDF, 7 pages | View Download |
| 8 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 2 pages | View Download |
| 9 | Video of Engine Run #1 (Shelf Item) | PDF, 1 page | 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
- N201KY: not on the register today · the record of its deregistration
- Mooney M-20 6,245 registered today · the model family and its accident history
- Mooney 5,394 aircraft on the register
- Engine: Lycoming IO-360 1A · as the NTSB recorded it
- Whiteman Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR16LA074.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.
