The U.S. aircraft register, updated daily
Accidents · NTSB CEN10FA119 · Final report

Piper PA-31T accident near Forest City, Iowa, February 12, 2010

On February 12, 2010 at about 7:55 pm local time, a Piper PA-31T, registered N250TT, was substantially damaged in an accident during approach (VFR pattern final) near Forest City, Iowa (Forest City Municipal Airport). It was a business flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain airplane control during final approach.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 12, 2010 · about 7:55 pm local time · cases in 2010
Place
Forest City, Iowa · Forest City Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-31T · all PA-31Ts on the register
Registration
N250TT · registry record · serial 31T-7820050
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

A witness reported that the multi-engine turboprop airplane was on final approach to land when it suddenly veered to the left and entered a rapid descent. The witness stated that he heard the "whine of the engines" before the airplane impacted terrain about 1/2 mile south of the runway threshold. In the days preceding the accident flight, the airplane had been at a maintenance facility to resolve a vibration in the rudder system while the autopilot system was engaged. There were no anomalies reported with the autopilot system during a test flight completed immediately before the accident flight. However, anomalies with the rate gyro were noted by a mechanic who recommended replacing it, but the pilot departed on the accident flight without the recommended repair having been completed. Further, examination of the autopilot annunciator panel indicated that the autopilot was likely not engaged at the time of impact, likely because the airplane was on a short final approach for landing. Accordingly, any existing autopilot faults would not have affected the flight as the autopilot system was likely not in use. There were no failures identified with the primary flight controls, engines, or propellers that would have prevented the pilot from maintaining control of the airplane manually. Toxicological testing revealed the presence of Zolpidem in the pilot's blood (Zolpidem, the trade name for Ambien, is used for short-term treatment of insomnia); however, the reported levels would likely not have resulted in any impairment.

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

  1. Loss of control in flight during approach (VFR pattern final) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained

Pilot

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 10,352 hours in all; 57 in the last 90 days; 34 in the last 30 days; 8,160 as pilot in command; 880 on instruments
  • Last flight review: February 1, 2008
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 9,048 hours
  • Last inspection: continuous airworthiness programme, February 3, 2010; 9 hours since
  • Maximum gross weight: 9,050 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: P&W PT6A-28 (turboprop); 0 hours total
  • Engine 2: P&W PT6A-28 (turboprop); 0 hours total
  • Operator: Mayes Aviation, LLC.

The flight

  • Departed from: SUS St. Louis MO at 6:23 pm
  • Destination: FXY Forest City IA
  • Flight plan: IFR
  • Runway 33, 5,796 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 110° at 3 knots
  • Visibility: 2 statute miles
  • Sky: overcast at 4,600 ft
  • Temperature: 21°F (-6°C), dew point 18°F (-8°C)
  • Altimeter: 30.01 inHg
  • Observation at 7:55 pm from FXY, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

37 documents, released by the NTSB on November 4, 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.

#DocumentWhat it is
1 Witness Statements PDF, 2 pages View Download
2 Accident Flight Summary, FAA Form 8020-6 PDF, 7 pages View Download
3 Transcript of Minneapolis Air Route Traffic Control Center Radio Communications with Accident Flight PDF, 6 pages View Download
4 radar Track Data Plots PDF, 2 pages View Download
5 FAA Inspector Statements PDF, 6 pages View Download
6 Aviation Mechanic Statement - John Wimpee, Gulf Coast Aircraft Inc. PDF, 1 page View Download
7 Memorandum of Conversation, Todd Bauer of Aero Charter Jet Center PDF, 1 page View Download
8 Aviation Mechanic Statement - Thomas Welge, Aero Charter Jet Center PDF, 1 page View Download
9 Aero Charter Jet Center Work Orders PDF, 4 pages View Download
10 Maintenance Logbook Information, Excerpts PDF, 20 pages View Download
11 Airplane Flight Logbook PDF, 6 pages View Download
12 Pilot Certificate Information PDF, 2 pages View Download
13 Pilot Logbook, Excerpts PDF, 16 pages View Download
14 Pilot Training Records PDF, 1 page View Download
15 Accident Site Diagram PDF, 1 page View Download
16 Summary of Engine Examinations PDF, 1 page View Download
17 Honeywell Autopilot Examination Report PDF, 28 pages View Download
18 Weather Information PDF, 1 page View Download
19 Toxicological Report PDF, 1 page View Download
20 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
21 Retention / Release of Wreckage Form PDF, 6 pages View Download
22 Photo 01 - Wreckage Debris Path PDF, 1 page View Download
23 Photo 02 - Main Wreckage, Left Side of Airplane PDF, 1 page View Download
24 Photo 03 - Main Wreckage PDF, 1 page View Download
25 Photo 04 - Main Wreckage, Right Wing and Engine PDF, 1 page View Download
26 Photo 05 - Main Wreckage, Right Side of Airplane PDF, 1 page View Download
27 Photo 06 - Wreckage Layout, Forward Fuselage and Cockpit PDF, 1 page View Download
28 Photo 07 - Wreckage Layout, Forward Fuselage and Cockpit PDF, 1 page View Download
29 Photo 08 - Wreckage Layout, Right Wing PDF, 1 page View Download
30 Photo 09 - Wreckage Layout, Right Wing PDF, 1 page View Download
31 Photo 10 - Wreckage Layout, Left Wing PDF, 1 page View Download
32 Photo 11 - Wreckage Layout, Left Wing PDF, 1 page View Download
33 Photo 12 - Wreckage Layout, Empennage and Aft Fuselage PDF, 1 page View Download
34 Photo 13 - Right Engine and Propeller PDF, 1 page View Download
35 Photo 14 - Left Engine and Propeller PDF, 1 page View Download
36 Photo 15 - Right Propeller PDF, 1 page View Download
37 Photo 16 - Left Propeller 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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN10FA119.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.