Plane Crash List

Mitsubishi MU 2B-40 N73MA

23 September 2017 · Ainsworth, Nebraska, United States · Fatal

Summary

On 23 September 2017 at about 15:28 local time, a Mitsubishi MU 2B-40 registered N73MA was involved in an accident near Ainsworth, Nebraska, 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 15:28
Classification
Accident
Location
Ainsworth, Nebraska, United States
Nearest airport
Ainsworth Regional (KANW)
Coordinates
42.5369, -99.9592
Aircraft
Mitsubishi MU 2B-40
Registration
N73MA
Category
Airplane
Year built
1979
Engines
2
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Ainsworth → Bottineau
Aircraft damage
Destroyed
Weather
IMC
Light
Day
NTSB number
CEN17FA362

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The pilot's loss of airplane control due to spatial disorientation.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The instrument-rated private pilot departed on a cross-country flight in instrument meteorological conditions (IMC) with an overcast cloud layer at 500 ft above ground level (agl) and visibility restricted to 1 ¾ miles in mist, without receiving an instrument clearance or opening his filed instrument flight rules flight plan. There was an outage of the ground communications system at the airport and there was no evidence that the pilot attempted to open his flight plan via his cellular telephone. In addition, there was a low-level outage of the radar services in the vicinity of the accident site and investigators were unable to determine the airplane's route of flight before impact. The airport manager observed the accident airplane depart from runway 35 and enter the clouds. Witnesses located to the north of the accident site did not see the airplane but reported hearing an airplane depart about the time of the accident. One witness reported hearing a low-flying airplane and commented that the engines sounded as if they were operating at full power. The witness heard a thud as he was walking into his home but attributed it to a thunderstorm in the area. The airplane impacted a field about 3.5 miles to the northeast of the departure end of the runway and off the track for the intended route of flight. The airplane was massively fragmented during the impact and debris was scattered for about 300 ft. The damage to the airplane and ground scars at the accident site were consistent with the airplane impacting in a left wing low, nose low attitude with relatively high energy. A postaccident examination of the engines and propeller assemblies did not reveal any preimpact anomalies that would have precluded normal operation. Signatures were consistent with both engines producing power and both propellers developing thrust at the time of impact. While the massive fragmentation precluded functional testing of the equipment, there was no damage or failure that suggested preimpact anomalies with the airframe or flight controls. Several days before the accident flight, the pilot encountered a "transient flag" on the air data attitude heading reference system. The pilot reported the flag to both the co-owner of the airplane and an avionics shop; however, exact details of the flag are not known. The unit was destroyed by impact forces and could not be functionally tested. If the flag affecting the display of attitude information had occurred with the unit after takeoff, the instrument panel had adequate stand-by instrumentation from which the pilot could have continued the flight. It is not known if this unit failed during the takeoff and investigators were unable to determine what role, if any, this transient issue may have played in the accident. Based upon the reported weather conditions, the location of the wreckage, and the attitude of the airplane at the time of impact with the ground, it is likely that the pilot experienced spatial disorientation shortly after takeoff which resulted in a loss of control and descent into terrain.

Quoted verbatim from the NTSB record.

Other Mitsubishi MU-2B accidents

Date Aircraft Location Operator Outcome Died
29 Mar 2016 Mitsubishi MU 2B
N246W
Iles-de-la-Madeleine, Canada - Fatal 7
22 Aug 2015 Mitsubishi MU 2B-25
N553T
Arvin, California, United States - No injuries -
29 Jan 2020 Mitsubishi MU 2B-40
N425GZ
Chilton, Wisconsin, United States - No injuries -
10 Nov 2013 Mitsubishi MU 2B-25
N856JT
Owasso, Oklahoma, United States - Fatal 1
16 Jan 2011 Mitsubishi MU-2B-20
N52CD
Walterboro, South Carolina, United States - No injuries -
29 Dec 2011 Mitsubishi MU-2B-20
N800BY
Picayune, Mississippi, United States Northshore Group LLC No injuries -

All 175 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
29 Jul 2017 Piper PA36
N132VA
McCook, Nebraska, United States Red Willow Aviation No injuries -
4 Mar 2017 Mooney M20F
N381LB
Hebron, Nebraska, United States - No injuries -
13 May 2017 As+ AC 4
N358R
Blair, Nebraska, United States - Fatal 1
2 Aug 2017 Cessna 172
N91966
Kearney, Nebraska, United States Beers Investment Group Inc No injuries -
6 Jul 2017 Luscombe 8
N45609
Grand Island, Nebraska, United States - No injuries -
22 Aug 2017 Cessna 182
N2465G
North Platte, Nebraska, United States - No injuries -

All 170,864 records in United States