NTSB CAROL · Event
Event CEN10LA117
Registry · N644EM
FAA Aircraft Registry record.
Make / Model
MITSUBISHI MU-2B-60
Year of manufacture
1980 · 30 years old at event
Engine
AIRESEARCH TPE331 SERIES (904 hp)
Seats / Engines
10 seats · 2 engines
Last airworthiness date
19800423
ADS-B equipped
Yes — Mode-S A87487
Registrant of record
AGRILOGICS INDUSTRIES LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's loss of directional control while landing on an ice/snow covered runway.
Factual narrative
**This report was modified on April 23, 2010** On February 4, 2010, approximately 0215 central standard time, a Mitsubishi MU-2B-60, N644EM, was substantially damaged during a runway excursion at the Rick Husband Amarillo International Airport (KAMA), Amarillo, Texas. Night visual meteorological conditions prevailed at the time of the accident. The on-demand air taxi flight was being conducted under the provisions of Title 14 Code of Federal Regulations Part 135 on an instrument flight rules flight plan. The pilot and three passengers were not injured. The cross-country flight originated from the Dallas/Fort Worth International Airport (KDFW), Fort Worth, Texas at 0111 and was landing at its intended destination at the time of the accident. According to a statement provided by the airline transport pilot, while on approach to the airport, the pilot was informed by airport operations that the runway was covered with snow and ice. The pilot acknowledged and continued the instrument approach to the landing runway. While on approached the pilot was correcting for a right crosswind. The pilot kept a higher approach speed and landed 20 knots faster than the manufacturer's 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 on a heading that was approximately 30 degrees left of runway heading. The right main landing gear detached from the airplane and the airplane came to rest in the upright position. An inspector from the Federal Aviation Administration (FAA) responded to the accident scene and found no pre-impact anomalies with the airframe or engines. Denting, bending, and crushing damage was sustained to fuselage and the forward spar of the right wing. In an interview with the FAA inspector, a representative from airfield operations reported the runway's braking condition was estimated at "nil." This accident is part of the Safety Board's Human Fatigue Investigation Methodology Study. Forms completed by the pilot indicate that he awoke at approximately 0700 on February 3, 2010. The pilot had been awake for 19 hours and 15 minutes prior to the accident, but had only been on-duty for 4 hours and 15 minutes. At 0211, an aviation special weather report from KAMA's weather station reported winds from 120 degrees at 6 knots, 1/2 miles visibility with a runway 04 visual range of 4,000 to 5,000 feet, snow, freezing fog, an indefinite ceiling with a vertical visibility of 110 feet, temperature 28 degrees Fahrenheit (F), dew point 28 F, and a barometric pressure of 29.91 inches of Mercury. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- F Environmental issues-Physical environment-Runway/land/takeoff/taxi surfa-Snow/slush/ice covered-Effect on operation - F
- — Personnel issues-Physical-Alertness/Fatigue-(general)-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2010_CEN10LA117.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗