Mitsubishi MU-2B-36 N103RC
23 September 2005 · West Memphis, Arkansas, United States · Fatal
Summary
On 23 September 2005 at about 00:58 local time, a Mitsubishi MU-2B-36 registered N103RC, operated by McNeely Charter Service Inc, was involved in an accident near West Memphis, Arkansas, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:58
- Classification
- Accident
- Location
- West Memphis, Arkansas, United States
- Nearest airport
- West Memphis Municipal Airport (AWN)
- Coordinates
- 35.1917, -90.2597
- Aircraft
- Mitsubishi MU-2B-36
- Registration
- N103RC
- Category
- Airplane
- Engines
- 2
- Operator
- McNeely Charter Service Inc
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Positioning
- Phase of flight
- Not recorded
- Route
- West Memphis → Gainesville
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Night
- NTSB number
- CHI05FA272
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Mitsubishi MU-2B accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 25 May 2005 | Mitsubishi MU-2B-25 | Hillsboro, Oregon, United States | - | Fatal | 4 |
| 12 Mar 2005 | Mitsubishi MU-2B-26A | Blythe, California, United States | Jaax Flying Service, Inc. | No injuries | - |
| 21 Dec 2005 | Mitsubishi MU-2B-36 | Terrace, BC, Canada | Nav Air Charter Inc. | Fatal | 2 |
| 4 Aug 2005 | Mitsubishi MU-2B-60 | Parker, Colorado, United States | - | Fatal | 1 |
| 1 Sep 2006 | Mitsubishi MU-2B-35 | Argyle, Florida, United States | Berg Steel Pipe Corp. | Fatal | 1 |
| 11 Dec 2004 | Mitsubishi MU-2B-60 | Englewood, Colorado, United States | - | Fatal | 2 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Sep 2005 | Bell 47G | Swifton, Arkansas, United States | Sissom and Woods Farms, Inc | Serious injuries | - |
| 21 Feb 2005 | Bell 206-L1 | Gentry, Arkansas, United States | Air Evac Lifeteam | Fatal | 1 |
| 10 Jun 2005 | Cessna A188B | Truman, Arkansas, United States | - | No injuries | - |
| 1 Jul 2005 | Grumman-Schweizer G-164C | Gillett, Arkansas, United States | - | No injuries | - |
| 9 Aug 2005 | Grumman G-164 | Knobel, Arkansas, United States | Corning Farm Supply, Inc | No injuries | - |
| 10 Aug 2005 | Hiller UH-12E | Hampton, Arkansas, United States | Summit Helicopters Inc | Serious injuries | - |