Mitsubishi MU-2B-60 accident near Amarillo, Texas, February 4, 2010
On February 4, 2010 at about 8:15 am local time, a Mitsubishi MU-2B-60, registered N644EM, was substantially damaged in an accident during landing (landing roll) near Amarillo, Texas (Amarillo International airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 4 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's loss of directional control while landing on an ice/snow covered runway.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 4, 2010 · about 8:15 am local time · cases in 2010
- Place
- Amarillo, Texas · Amarillo International · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Mitsubishi MU-2B-60 · all MU-2B-60s on the register
- Registration
- N644EM · registry record · serial 1534 S.A.
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
While on approach to the snow and ice-covered runway, the pilot was correcting for a right crosswind. The airplane was flying approximately 20 knots faster than the recommended landing airspeed. The airplane's right main landing gear touched down first followed by the left main landing gear and the nose gear. The airplane made an abrupt left turn and the pilot attempted to correct by depressing the right rudder pedal. The pilot lost control of the airplane and the airplane departed the left side of the runway. The right main landing gear was torn from the airplane and the airplane came to rest in the upright position. Airfield operations reported that the runway's braking condition was estimated at "nil." An examination of the airplane and its systems revealed no anomalies.
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
- Other weather encounter during landing (landing roll)
- Loss of control on ground during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- factor Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Snow/slush/ice covered › Effect on operation
- Personnel issues › Physical › Alertness/Fatigue › (general) › Pilot
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 12,954 hours in all; 9,277 in this make and model; 90 in the last 90 days; 26 in the last 30 days; 12,822 as pilot in command
- Last flight review: October 23, 2009
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 10,019 hours
- Last inspection: 100-hour inspection, November 11, 2009
- Maximum gross weight: 11,575 lb
- Seats: 10
- Landing gear: retractable
- Engine 1: Honeywell TPE331-10-511 (turboprop); 0 hours total
- Engine 2: Honeywell TPE331-10-511 (turboprop); 0 hours total
- Operator: Mid-Coast Air Charter INC
The flight
- Departed from: KDFW Dallas/Fort Wor TX at 7:11 am
- Destination: KAMA Amarillo TX
- Flight plan: IFR
- Runway 04, 13,502 ft by 200 ft
Weather at the time
- Light: night
- Wind: from 120° at 6 knots
- Sky: vv at 110 ft
- Temperature: 28°F (-2°C), dew point 28°F (-2°C)
- Altimeter: 29.90 inHg
- Observation at 8:11 am from KAMA, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on April 20, 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 | Photo: Wreckage Overview | 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
- N644EM 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: Honeywell TPE331-10-511 27 aircraft carry this series today · as the NTSB recorded it
- Engine: Honeywell TPE331-10-511 27 aircraft carry this series today · as the NTSB recorded it
- Rick Husband Amarillo International · nearest airport
- Dallas-Fort Worth International · departed from
- Accidents and incidents in Texas 6,244 since 1982 · 1,064 in the last ten years
- Texas 29,966 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN10LA117.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.