ASN Wikibase Occurrence # 199960
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 23 September 2017 |
| Time: | 10:28 |
| Type: |  Mitsubishi MU-2B-40 Solitaire |
| Owner/operator: | Private |
| Registration: | N73MA |
| MSN: | 414 SA |
| Year of manufacture: | 1979 |
| Total airframe hrs: | 5383 hours |
| Engine model: | Honeywell TPE331 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Brown County, 5 miles N of the Ainsworth Regional Airport, NE (KANW) -
 United States of America
|
| Phase: | Initial climb |
| Nature: | Private |
| Departure airport: | Ainsworth Airport, NE (ANW/KANW) |
| Bottineau, ND (D09) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: The pilot's loss of airplane control due to spatial disorientation.
Accident investigation:
 |
|
Sources:
NTSB
Location
Images:
Photo: NTSB
Media:
#NTSB on MU-2 N73MA LOC-I due to spatial disorientation shortly after takeoffhttps://t.co/u6nY6eq5Dj#flightsafety #avgeek #avgeeks #humanfactors pic.twitter.com/rkLDncXiQ8
— Aerossurance (@Aerossurance) March 1, 2019
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 26-Sep-2017 08:13 | plcedi | Added |
| 26-Sep-2017 14:28 | Geno | Updated [Cn, Operator, Location, Departure airport, Source, Narrative] |
| 26-Sep-2017 17:19 | Dmitriy | Updated [Aircraft type] |
| 30-Sep-2017 21:52 | wf | Updated [Location, Departure airport] |
| 11-Jan-2018 20:35 | rvargast17 | Updated [Time, Aircraft type] |
| 02-Mar-2019 14:46 | ASN Update Bot | Updated [Cn, Operator, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ] |
| 02-Mar-2019 15:47 | harro | Updated [Narrative, Photo] |
| 03-Mar-2019 11:51 | Aerossurance | Updated [Location, Embed code] |
| 08-Mar-2019 19:56 | ASN Update Bot | Updated [Embed code, Narrative, Accident report, ] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation