Mooney Aircraft CORP. M20K accident near Urbana, Illinois, February 17, 2011
On February 17, 2011 at about 4:30 pm local time, a Mooney Aircraft CORP. M20K, registered N262CP, was substantially damaged in an accident during approach (VFR go-around) near Urbana, Illinois (Frasca Field Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain aircraft control during the go-around.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 17, 2011 · about 4:30 pm local time
- Place
- Urbana, Illinois · Frasca Field Airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Mooney Aircraft CORP. M20K
- Registration
- N262CP · registry record · serial 25-0092
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Prior to the flight, the pilot contacted the destination airport's fixed based operator to inquire about the local wind conditions. He planned on diverting to an alternate airport if the crosswind was too strong. During the final approach to the airport, the airplane encountered turbulent wind. The airplane ballooned during the landing flare, and the pilot executed a go-around. During the attempted go-around, the left wing contacted terrain, and came to rest upright adjacent to a residence. During the accident sequence, the airplane sustained damage to the firewall, fuselage, and both wings. Postaccident examination of the airplane showed no preimpact mechanical malfunctions or failures with the airplane.
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 control in flight during approach (VFR go-around) defining event
- Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,162 hours in all; 713 in this make and model; 33 in the last 90 days; 8 in the last 30 days; 2,100 as pilot in command
- Last flight review: September 7, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 3,919 hours
- Last inspection: annual inspection, October 22, 2010
- Maximum gross weight: 2,900 lb
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor TSIO-360 SER (piston); 0 hours total
The flight
- Departed from: 2K0 Monticello IL at 4:15 pm
- Destination: C16 Urbana IL
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 180° at 20 knots, gusting 26
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 37°F (3°C), dew point 0°F (-18°C)
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.