# NTSB CHI02LA044: Mitsubishi MU-2B-40, N9052Y, St Paul, MN, November 30, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: November 30, 2001, 09:28 local (15:28 UTC) - Place: St Paul, MN - Coordinates: 44.930728, -93.07933 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.9307&lon=-93.0793&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report May 13, 2003 - Report: Approved by Office Director - Parties: Federal Aviation Administration, Mitsubishi Heavy Industries America - NTSB case key (mKey): 53866 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI02LA044 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53866/pdf - Page: https://openairdocs.org/ntsb/CHI02LA044 ## Probable cause The autopilot's computer connections arcing and reported disconnection during the localizer approach and the pilot not performing a go around prior to the hard landing. A factor was the pilots lack of total experience in the accident airplane's make and model. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, approach - faf/outer marker to threshold (ifr) - autopilot/flight director,amplifier and computer - arcing (cause) - Hard landing, landing - lack of experience, pilot in command (contributing factor) - missed approach - not performed, pilot in command (cause) ## Analysis The airplane sustained substantial damage on impact with the runway during a hard landing following a coupled autopilot approach. The pilot and three passengers were uninjured. Instrument meteorological conditions prevailed. The pilot reported, "I was using the autopilot to fly the ILS localized timed approach. I was looking for the runway and watching the time. The autopilot inadvertently disengaged, turning the airplane to the left. I righted the airplane just before touchdown. It landed on the mains with the nose slightly high. It came down, and the front wheel and strut broke." During the next flight, a ferry flight for repairs, the accident pilot reported that he engaged the autopilot at 2,500 feet. The pilot reported that when the autopilot was engaged, the airplane pitched down and turned sharply to the right. The pilot reported using opposing control inputs and differential engine power to maintain airplane control. The pilot performed a no flap landing at an en route airport with a 2,497-foot long runway. An examination of the airplane revealed that when the autopilot computer was moved in its shock mount the yoke moved "violently right in roll axis and forward in pitch axis." The MU-2 airplane flight manual's emergency procedures stated, "In case of emergency, the autopilot can be overpowered manually to correct the attitude, but the autopilot must immediately be disengaged. If the autopilot remains engaged, the autopilot will trim the airplane to oppose the pilot's actions. This could result in a severely out of trim condition." The manual stated, "The autopilot can also be disengaged by any of the following methods, "1. Operate trim switch UP or DOWN, 2. Position inverter switch to OFF momentarily and then return, to original position, 3. Turn off the ELECTRIC MASTER SWITCH." The pilot reported 11 hour hours of pilot in command time in the accident airplane make and model. ## Factual narrative On November 30, 2001, about 0928 central standard time, a Mitsubishi MU-2B-40, N9052Y, piloted by a private pilot, sustained substantial damage during a hard landing on runway 14 at St Paul Downtown Holman Field Airport (STP), near St Paul, Minnesota. The 14 CFR Part 91 business flight was operating on an IFR flight plan. Instrument meteorological conditions prevailed at the time of the accident. The pilot and three passengers were uninjured. The flight originated from Southwest Michigan Regional Airport, near Benton Harbor, Michigan, at time unknown, and was landing at STP at the time of the accident. The pilot reported in a written statement: I departed Benton Harbor (B.E.H.) on 11/30/01 at 0800 using runway 14. It was an hour and half flight to S.T.P. It was an ILS approach. The glide slope and DME [distance measuring equipment] were in-op [inoperative]. I was using the autopilot to fly the ILS localized timed approach. I was looking for the runway and watching the time. The autopilot inadvertently disengaged, turning the airplane to the left. I righted the airplane just before touchdown. It landed on the mains with the nose slightly high. It came down, and the front wheel and strut broke. The airplane skidded on the nose down the runway. I kept it on the runway by using the brakes. The Federal Aviation Administration (FAA) issued a ferry permit to allow the airplane to be flown to Green Bay, Wisconsin, for repairs. The pilot reported in another statement: After receiving a ferry permit from the FAA, I departed St. Paul, MN the morning of December 17, 2001, to fly my MU-2, N-9052Y to Green Bay, Wisconsin for repairs of damage to the aircraft in a hard landing at St. Paul Minnesota, as stated above. This flight was to be flown VFR, day, single pilot only. About 10 miles east of St. Paul and level at 2,500 feet, I engaged the autopilot. A few minutes after the autopilot was engaged, the nose of the aircraft pitched down and turned sharply to the right. I immediately attempted to disengage the autopilot, which was futile, and told the traffic controller of my problem. He in turn reported that a small airport was to my left and behind my current position. I saw the airport ) Lake Elmo (21D)) and in order to fly the airplane to the airport, I had to use extreme backpressure, left rudder, plus differential power to maintain enough control to reach the airport and land on a 2,497 foot runway without using flaps or reverse prop and with no damage to the airplane. ... After I got the aircraft back to Green Bay, Wisconsin, I took it to [a repair station there] where [mechanics and the FAA] each inspected the autopilot system. They were able to duplicate the runway trim on the ground where it was determined that the problem of the autopilot trim runaway was a faulty connection in the autopilot computer. FAA inspectors, safety investigators from the airplane manufacturer, and representatives from the repair station examined the airplane. The repair station stated: The autopilot system was engaged and disengaged several times and all flight director modes engaged. Mode Annunciator test function, all lamps test and illuminated when mode selected and coupled to autopilot. Electric manual trim and automatic pith trim moved elevator trim tab in the correct direction and speed. The servos in pitch, roll, and yaw had adequate strength and speed to move the respective control surfaces. No mechanical binding or slack noted in rigging or capstans and servo mounts. The attitude gyro Sperry VG14A (primary attitude reference for M4D autopilot, FD112V flight director and weather radar) was removed from its mount for field troubleshooting. Voltage measurements were taken at the autopilot computer, of 200mv per degree for pitch and roll output from vertical gyro referenced on flight director. Readings corresponded with pilot's primary attitude reference with respect to pitch and roll. Autopilot system performed satisfactory until the autopilot computer model 5536F part number 400495-8501 was moved in its shock mount at which time the yoke was pulled violently right in roll axis and forward in pitch axis. This finding is consistent with [the pilot's] experience, as you reported to us, during landing on November 30, 2001 had the autopilot remained engaged. This malfunction was repeated five times ... However during closer examination of the autopilot computer connections pin 53 of jack 2 of autopilot computer was found to be oversized and discolored in a manor consistent with electrical arcing. Pin function described as servo motor power in the M4D maintenance manual. The MU-2 airplane flight manual's emergency procedures stated: In case of emergency, the autopilot can be overpowered manually to correct the attitude, but the autopilot must immediately be disengaged. If the autopilot remains engaged, the autopilot will trim the airplane to oppose the pilot's actions. This could result in a severely out of trim condition. The manual stated: The autopilot can also be disengaged by any of the following methods: 1. Operate trim switch UP or DOWN 2. Position inverter switch to OFF momentarily and then return to original position 3. Turn off the ELECTRIC MASTER SWITCH The pilot reported he accumulated 11 hours of pilot in command time in the accident airplane make and model. Parties to the investigation were the FAA and Mitsubishi Heavy Industries America, Inc. ## Aircraft - Registration: N9052Y (not matched to a registry record) - Reported make and model: Mitsubishi MU-2B-40 - Category: Airplane - Serial number: 39917 - Engines: Garrett TPE-331-10 665 horsepower turbo prop; Garrett TPE-331-10 665 horsepower turbo prop - Damage: Substantial damage - Flight: Business, Part 91 - Registered owner: Superior Builders - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, September 12, 2001 - Departed: BEH, BENTON HARBOR, MI - Destination: STP, Saint Paul, MN - Flight plan: IFR - Airport: STP, St Paul Downtown Holman Fld, runway 14, 6,711 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: none; private; airplane ratings: multi-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; last flight review December 4, 2000; seat: left; flight hours: 3,420 total, 3,370 as pilot in command, 25 in the last 90 days, 3 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: 60° at 3 knots - Visibility: 4 statute miles - Lowest ceiling: 700 ft overcast - Temperature: 34 °F, dew point 30 °F - Altimeter: 29.77 inHg - Observed at: STP ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20011130032409A](https://openairdocs.org/incident/20011130032409A), Nov 30, 2001: Mtsbsi MU2B40, St Paul, MN, No damage. (-23) After touchdown on runway 14 at kstp the nose landing gear collapsed causing the fuselage lower nose to contact the ground. The aircraft continued for… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.