Mitsubishi MU-2B-60 accident near Millington, Tennessee, December 9, 2008
On December 9, 2008 at about 4:58 pm local time, a Mitsubishi MU-2B-60, registered N452MA, was substantially damaged in an accident during enroute near Millington, Tennessee (Millington Regional Jetport airport). It was a positioning flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s improper configuration of the airplane following an engine shutdown, which resulted in a low-altitude, unstabilized approach. Contributing to the accident was a loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 9, 2008 · about 4:58 pm local time · cases in 2008
- Place
- Millington, Tennessee · Millington Regional Jetport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Mitsubishi MU-2B-60 · all MU-2B-60s on the register
- Registration
- N452MA · registry record · serial 1533 S.A.
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, after he took off for a nearby airport he raised the landing gear but did not raise the 20-degree flaps per the “after takeoff” checklist. Shortly thereafter, when the airplane was at an altitude of about 2,400 feet, and in "heavy rain," the pilot noticed that the right engine was losing power. He subsequently feathered the propeller as engine power reduced to 40 percent, but still did not raise the flaps. Weather, recorded shortly before the accident, included scattered clouds at 500 feet, and a broken cloud layer at 1,200 feet, and the pilot advised air traffic control (ATC) that he would fly an ILS (instrument landing system) approach if he could maintain altitude. After maneuvering, and advising ATC that he could not maintain altitude, the pilot descended the airplane to a right base leg where, about 1/4 nautical mile from the runway, it was approximately 300 feet above the terrain. The pilot completed the landing, with the airplane touching down about 6,200 feet down the 8,000-foot runway, heading about 20 degrees to the left. The airplane veered off the left side of the runway and subsequently went through an airport fence. The left engine was running at “high speed” when fire fighters responded to the scene. The right engine propeller was observed in the feathered position at the scene, and after subsequent examinations, the right engine was successfully run in a test cell with no noticeable loss of power. There was no determination as to why the right engine lost power in flight, although rain ingestion is a possibility. Airplane performance calculations indicated that with the landing gear up, a proper single-engine power setting and airspeed, and flaps raised, the airplane should have been able to climb about 650 feet per minute. Even with flaps at 20 degrees, it should have been able to climb at 350 feet per minute. In either case, unless the airplane was not properly configured, there was no reason why it should not have been able to maintain the altitudes needed to position it for a stabilized approach.
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 enroute defining event
- Engine shutdown during enroute
- Abnormal runway contact during landing
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Not attained/maintained
- factor Aircraft › Aircraft power plant › Engine (turbine/turboprop) › (general) › Inoperative other cases naming the engine
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 5,311 hours in all; 662 in this make and model; 63 in the last 90 days; 20 in the last 30 days
- Last flight review: July 17, 2008
- Medical certificate: Class 2
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 6,094 hours
- Last inspection: annual inspection, June 24, 2008; 56 hours since
- Maximum gross weight: 11,575 lb
- Seats: 8
- Landing gear: retractable
- Engine 1: Garrett Airesearch TPE331 SERIES (turboprop); 0 hours total
- Engine 2: Garrett Airesearch TPE331 SERIES (turboprop); 0 hours total
- Operator: Briggs Tobacco and Specialty Company INC
The flight
- Departed from: NQA Millington TN at 4:40 pm
- Destination: 2M8 Millington TN
- Flight plan: IFR
- Runway 22, 8,000 ft by 200 ft
Weather at the time
- Light: daylight
- Visibility: 3 statute miles
- Sky: broken clouds at 1,200 ft; scat at 500 ft
- Temperature: 54°F (12°C), dew point 54°F (12°C)
- Altimeter: 29.81 inHg
- Observation at 4:50 pm from NQA
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
13 documents, released by the NTSB on July 6, 2010. 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 | Memorandum of Record (Pilot Interview) | PDF, 2 pages | View Download |
| 3 | Pilot Email Responses | PDF, 1 page | View Download |
| 4 | Excerpts, FAA Air Traffic Partial Transcript | PDF, 31 pages | View Download |
| 5 | Excerpts, FAA Contract Tower Partial Transcript | PDF, 9 pages | View Download |
| 6 | FAA Inspector Observations | PDF, 2 pages | View Download |
| 7 | Fire Fighter Observations | PDF, 3 pages | View Download |
| 8 | Raw radar Data | PDF, 4 pages | View Download |
| 9 | radar Plots | PDF, 3 pages | View Download |
| 10 | Satellite View: Last radar Point in Relation to Runway | PDF, 1 page | View Download |
| 11 | Excerpts, Honeywell Right Engine Test Report | PDF, 6 pages | View Download |
| 12 | Performance Charts | PDF, 2 pages | View Download |
| 13 | Firefighter Photo: Airplane | 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
- N452MA on the register today · the tail number may have moved to another aircraft since
- Mitsubishi MU-2 176 registered today · the model family and its accident history
- Mitsubishi 198 aircraft on the register
- Engine: Garrett Airesearch TPE331 SERIES · as the NTSB recorded it
- Engine: Garrett Airesearch TPE331 SERIES · as the NTSB recorded it
- Millington/Memphis Airport · nearest airport
- Charles W Baker Airport · bound for
- Accidents and incidents in Tennessee 1,198 since 1982 · 229 in the last ten years
- Tennessee 6,542 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA09FA083.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.