FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI05FA272 · Mitsubishi MU-2B-36

22 Sept 2005 · West Memphis, AR, United States

McNeely Charter Service Mitsubishi MU-2B-36 · Accident: airframe, component or system failure en route

From West Memphis Municipal Airport (AWM) to Lee Gilmer Memorial Airport (GVL)

Report a problem

Event

NTSB case
CHI05FA272
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Mitsubishi MU-2B-36

Aircraft type
Mitsubishi MU-2
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N103RC
Onboard fatalities
Unknown
Route
From West Memphis Municipal Airport (AWM), West Memphis, ARTo Lee Gilmer Memorial Airport (GVL), Gainesville, GA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › In-flight planning/decision, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The twin-engine airplane was destroyed when it impacted an earthmoving scraper and terrain in a field about 2.5 miles north of the departure airport in night visual meteorological conditions. Witnesses reported that the pilot had aborted an earlier flight when he returned to the airport and told the mechanic that he had a right engine fire warning light. The discrepancy could not be duplicated during maintenance, and the airplane departed. About 23 minutes after departure, the pilot reported to air traffic control that he needed to return to the airport to have something checked out. The pilot did not report to anyone why he decided to return to the departure airport, and he flew over four airports when he returned to the departure airport. Radar track data indicated that the airplane flew over the departure end of runway 35 at an altitude of about 1,600 feet agl, and made a descending left turn. The airplane's altitude was about 800 feet agl when it crossed the final approach course for runway 35. The airplane continued the descending left turn, but instead of landing on runway 35, the airplane flew a course that paralleled the runway, about 0.8 nm to the right of runway 35. The airplane continued to fly a northerly heading and continued to descend. The radar track data indicated that the airplane's airspeed was decreasing from about 130 kts to about 110 kts during the last one minute and fifty seconds of flight. The last reinforced beacon return indicated that the airplane's altitude was about 200 feet agl, and the airspeed was about 107 kts. The airplane impacted terrain about 0.75 nm from the last radar contact on a 338-degree magnetic heading. A witness reported that the airplane was going slow and was "extremely low." He reported that the airplane disappeared, and then there was an explosion and a fireball that went up about 1,000 feet. Inspection of the airplane revealed that it impacted the earthmover in about a wings level attitude. The landing gear handle was found to be in the landing gear UP position. The inspection of the left engine and propeller revealed damage indicative of engine operation at the time of impact. Inspection of the right engine revealed damage indicative of the engine not operating at the time of impact, consistent with an engine shutdown and a feathered propeller. No pre-existing conditions were found in either engine that would have interfered with normal operation. The inspection of the right engine fire detection loop revealed that the connector had surface contamination. When tested, an intermittent signal was produced which could give a fire alarm indication to the pilot. After the surface contamination was removed, the fire warning detection loop operated normally.

Probable cause

The pilot's improper in-flight decision not to land at the departure runway or other available airports during the emergency descent, and his failure to maintain clearance from a vehicle and terrain. Contributing factors were a false engine fire warning light, inadequate maintenance by company personnel, a contaminated fire warning detection loop, and night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05FA272
Event ID
20050929X01550
Case number
CHI05FA272
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-09-23.
  • API snapshot SHA-256: 5ce5e4e669b14e501a0d1155561cd99ecd5cc9e4dc80a3cfab2dee894718a2ee; retrieved 2026-09-20T17:52:42.066Z.