Mooney Airplane CO INC M20TN accident near Fayetteville, North Carolina, February 17, 2012
On February 17, 2012 at about 10:32 pm local time, a Mooney Airplane CO INC M20TN, registered N118RZ, was substantially damaged in an accident during landing (flare/touchdown) near Fayetteville, North Carolina (Fayetteville Regional Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain adequate separation behind a large airplane during landing, which resulted in an encounter with wake turbulence and a loss of control.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 17, 2012 · about 10:32 pm local time
- Place
- Fayetteville, North Carolina · Fayetteville Regional Airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Mooney Airplane CO INC M20TN
- Registration
- N118RZ · no longer on the register · serial 31-0069
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was in the traffic pattern for landing and was informed by the tower air traffic controller that there was a large airplane (Gulfstream) at his one o'clock position on a 5-mile final approach. The accident pilot replied at 17:27:19, "I see the gulfstream ah gulfstream on the final." A 5.72-mile separation was noted on the controller’s radar screen at that time. At 17:27:24, the approach controller informed the accident airplane, which was at 2,500 feet, "caution wake turbulence" and instructed the pilot to contact the tower. The accident airplane was cleared to land on runway 4 by the controller at 17:27:54. The pilot acknowledged the transmission. The tower controller informed the accident pilot, “caution wake turbulence from the gulfstream" at 17:29:09. The response from the accident airplane was unintelligible. The pilot stated he encountered wake turbulence from the Gulfstream that landed ahead of him and lost airplane control. A witness observed the airplane about 8 feet over the runway when it stalled and landed hard. The pilot applied full engine power and attempted a go-around. The airplane drifted to the left toward an airplane parking ramp, struck a light pole, and spun around, coming to rest in a grass area past the parking ramp. The required separation in accordance with FAA regulations was 4 miles. It stated that a pilot landing a smaller airplane behind a larger airplane on the same runway should stay above the larger airplane’s final approach path and land beyond it to avoid an encounter with wake turbulence. The pilot had contacted the tower controller, after a handoff from the approach controller, and was cautioned again about wake turbulence. It is likely that the pilot did not land beyond the Gulfstream's touchdown point, and the airplane encountered wake turbulence, which led to the runway excursion and on-ground collision with a pole. The pilot stated he did not experience any mechanical problems with the airplane before the accident.
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
- Aircraft wake turb encounter during landing (flare/touchdown)
- Loss of control in flight during landing (flare/touchdown) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- Environmental issues › Conditions/weather/phenomena › Turbulence › Wake turbulence › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 356 hours in all; 49 in this make and model; 66 in the last 90 days; 19 in the last 30 days; 282 as pilot in command
- Last flight review: February 20, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 390 hours
- Last inspection: annual inspection, December 14, 2011; 33 hours since
- Maximum gross weight: 3,368 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor TSIO-550-G (piston); 0 hours total
The flight
- Departed from: RDU Raleigh NC at 10:07 pm
- Destination: FAY Fayetville NC
- Flight plan: none
- Runway 04, 7,709 ft by 150 ft
Weather at the time
- Light: dusk
- Wind: from 290° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 61°F (16°C), dew point 39°F (4°C)
- Altimeter: 30.04 inHg
- Observation at 10:53 pm from FAY
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
25 documents, released by the NTSB on June 27, 2013. 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.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.