# NTSB FTW00LA084: Mitsubishi MU-300, N900WJ, Dallas, TX, January 27, 2000 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: January 27, 2000, 10:15 local (16:15 UTC) - Place: Dallas, TX - Coordinates: 32.850002, -96.830261 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.8500&lon=-96.8303&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 6 uninjured - Status: Completed, report April 6, 2001 - Report: Approved by Office Director - ADs cited in the narratives: [AD 94-25-10](https://openairdocs.org/ad/94-25-10) (OpenAirDocs) - NTSB case key (mKey): 48647 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW00LA084 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/48647/pdf - Page: https://openairdocs.org/ntsb/FTW00LA084 ## Probable cause The diminished effectiveness of the anti-skid brake system due to the slush contaminated runway. Factors were the freezing rain encountered during the approach, coupled with a failure of the horizontal stabilizer heat. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, approach - iaf to faf/outer marker (ifr) - weather condition - freezing rain (contributing factor) - anti-ice/deice system,empennage - failure (contributing factor) - checklist - not complied with, flightcrew - On ground/water encounter with weather, landing - roll - airport facilities,runway/landing area condition - slush covered (cause) - brakes,anti-skid - diminished (cause) - Overrun, landing - roll ## Analysis Freezing rain, mist, and ice pellets were forecast for the destination airport with temperatures 34 to 32 degrees F. During the daylight IMC descent and vectors for the approach, the airplane began to accumulate moderate clear ice, and a master warning light illumination in the cockpit indicated that the horizontal stabilizer heat had failed. The airplane was configured at 120 knots and 10 degrees flaps in accordance with the flight manual abnormal procedures checklist; however, the crew did not activate the horizontal stabilizer deice backup system. The aircraft touched down 1,500 ft down the runway, which was contaminated with slush, and did not have any braking action or antiskid for 3,000 ft on the 7,753-ft runway. Therefore, 3,253 ft of runway remained for stopping the aircraft, which was 192 feet short of the 3,445 ft required for a dry runway landing. Upon observing a down hill embankment and support poles beyond the runway, the captain forced the airplane to depart the right side of the runway to avoid the poles. After the airplane started down the embankment, the nose landing gear collapsed, and the airplane came to a stop. ## Factual narrative HISTORY OF FLIGHT: On January 27, 2000, at 1015 central standard time, a Mitsubishi MU-300, N900WJ, overran runway 31R during landing at the Dallas Love Field Airport, Dallas, Texas, and struck the terrain. The aircraft was owned and operated by Matrix Aviation, of Denver, Colorado, under 14 Code of Federal Regulations Part 91. The two commercial pilots and their 4 passengers were not injured. The airplane sustained substantial damage. Instrument meteorological conditions prevailed for the cross-country business flight, and an IFR flight plan was filed. The flight departed Austin, Texas, at 0940. During the descent and vectors for the approach to runway 31R, the airplane began to accumulate moderate clear ice, and a master warning light illumination in the cockpit indicated that the horizontal stabilizer heat had failed. The crew continued the approach to get the airplane out of the icing conditions and on the ground as soon as possible. Landing weight was 12,500 lbs. Considering the possibility of additional ice accumulation on the horizontal stabilizer, the crew, per the flight manual abnormal procedures checklist, configured the airplane for a touchdown speed of 120 knots in lieu of 108 knots, and a flap extension of 10 degrees in lieu of 30 degrees. The first officer made the approach call outs. The captain stated that "on the approach, we broke out as expected and had good visibility of the runway and noticed that the runway had slush on it." The aircraft touched down approximately 1,500 feet down the runway and the captain began applying the brakes. The captain reported that the aircraft did not have any braking action for approximately 3,000 feet and the anti-skid was not pulsing. With about 1,500 feet of runway remaining, it looked to the captain like there would not be enough available runway to stop the aircraft. Beyond the departure end of the runway, there was a steep down hill embankment and support poles for the approach lights for runway 13L. The captain forced the aircraft to depart the right side of the runway to avoid the poles. After the aircraft started down the embankment, the nose gear collapsed and the airplane came to rest. The crew and passengers exited the aircraft, and the captain and passengers walked to the fixed base operator (FBO) while the first officer remained with the aircraft. At the FBO, the captain called the control tower to advise them of the situation, since the captain had not observed any emergency vehicles responding to the site. The FAA inspector, who responded to the accident site, found the left main landing gear and the lower fuselage damaged. The aircraft was recovered to a hangar at the airport. During the post accident examination on February 22, 2000, the FAA inspector and a mechanic found structural damage to the right wing rear spar at the wing root. CREW INFORMATION: The captain held a commercial pilot certificate with a type rating in the MU-300 aircraft. He had accumulated 5,960 total flight hours, of which 770 hours were in the accident make/model aircraft. The first officer held a commercial pilot certificate and had accumulated 751.9 hours second-in-command time in the MU-300 aircraft. AIRCRAFT INFORMATION: The aircraft, serial number AO28SA, was manufactured in 1982. The last 100-hour inspection was performed on December 29, 1999, and the accumulated time since the inspection was 12.3 hours. The Raytheon Aircraft Company (formerly Beechcraft) acquired the type certificate for the MU-300 on June 30, 1998. Maintenance records were not available for review by the Safety Board. The airplane was not equipped with a cockpit voice recorder or a flight data recorder, and a thrust reverser system was not installed. Landing Performance According to the Raytheon Aircraft Company representative, the calculated field length requirement for the MU-300 aircraft, using a landing weight of 12,500 pounds (maximum gross weight is 15,500 pounds), using the Approved Flight Manual (AFM) Landing Field Length Chart would have been "2,650 feet of runway." According to the MU-300 AFM Abnormal Procedures section, under the paragraph Horizontal Stabilizer Ice Protections Systems Failure, the crew is directed to turn OFF the horizontal stabilizer anti-ice and/or de-ice switches in the cockpit. Further, activate the horizontal stabilizer deice back-up by opening the guard and selecting manual at the cockpit toggle switch to energize the back-up system for 30 seconds. Repeat the manual selection every 2 minutes. The procedures section also specifies a landing flap setting of 10 degrees and an approach speed of Vref plus 15 KIAS when the horizontal stabilizer anti-ice fail or horizontal stabilizer de-ice fail light illuminates. The AFM notes that the landing field length will increase approximately 30 percent. According to the representative, this would "add 795 feet to the landing for a total of 3,445 feet required (with a dry runway and speed brakes extended after touchdown)." The representative reported that "if you subtract the 1,500 feet of runway before touchdown and the 3,000 feet of sliding from the 7,753-foot runway length, you are left with 3,253 feet, 192 feet short of the 3,445 feet required for a dry runway. He also stated that the "MU-300 AFM does not have performance data for a contaminated runway" since the FAA has not defined what constitutes a "contaminated runway." The representative further stated that flying the airplane at 120 knots and with 10 degrees of flaps, on the 3 degree glideslope with a threshold crossing height of 49 feet, would require a descent rate of 637.5 feet per minute in order to maintain the glideslope. In this configuration, the airplane should make contact with the runway at 933.71 feet beyond the threshold. Service Bulletins A review of Service Bulletins and Airworthiness Directives, by the NTSB IIC, revealed the data in the following paragraphs. In September 1983, Mitsubishi issued Service Bulletin (SB) 30-001 for modification of the horizontal stabilizer system to install a horizontal stabilizer de-ice test switch and change the de-ice cycle sequence. Compliance with the SB was mandatory for operation in known icing conditions. In September 1985, Mitsubishi issued SB 30-005 for the installation of a safety cap over the horizontal stabilizer de-ice backup switch to prevent inadvertent flight crew activation of the switch while on the ground. In 1994, Beechcraft obtained data generated during icing tests on the Model 400A to satisfy the requirements of Canadian Icing Certification. These requirements were more stringent than the FAA Part 23 icing certification requirements. During the wind tunnel test, ice accumulated on the horizontal stabilizer. Beechcraft determined that, if the conditions experienced during the test occurred in flight in icing conditions with all ice protection systems operating, the accumulated ice could result in an uncommanded nose down pitch at flaps settings greater than 10 degrees. In July 1994, Beechcraft issued a Safety Communique to the MU-300-10, 400, 400A, and the 400T operators to extend no more than 10 degrees flaps for landing if icing conditions were encountered during flight. Beech Aircraft did not own the MU-300 type certificate in 1994; therefore, the MU-300 was not included in the Safety Communique. In December 1994, the FAA issued Airworthiness Directive (AD) 94-25-10 requiring that all Mitsubishi Model MU-300 airplanes; and all Beech Model 400, 400A, 400T, and MU-300-10 airplanes comply with the Safety Communique procedures to extend no more than 10 degrees of flaps for landing if icing conditions were encountered in flight. In January 1996, Mitsubishi issued SB 30-007 as an alternate means of compliance with AD 94-25-10 for the MU-300 airplanes (serial numbers A003SA through A091SA). The SB detailed the installation of t ## Aircraft - Registration: [N900WJ](https://openairdocs.org/deregistered/N900WJ-2012-09-27), registration cancelled 2012-09-27, S/N A028SA, built 1982 (OpenAirDocs) - Reported make and model: Mitsubishi MU-300 - Registry model: [Mitsubishi MU-300](https://openairdocs.org/model/mitsubishi-mu-300) (registry code 5780602) (OpenAirDocs) - Registry engine: [Pratt & Whitney Canada JT15D-4 series](https://openairdocs.org/engine/pratt-whitney-canada-jt15d-4-series) (registry code 52112, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: A028SA - Airframe hours: 5266 - Engines: P&W JT15D-4D 2500 lbs thrust turbo fan - Damage: Substantial damage - Flight: Business, Part 91 - Registered owner: Matrix Aviation - Airworthiness certificate: Standard, Transport - Last inspection: 100 hour, December 29, 1999, 12 hours before - Departed: AUS, AUSTIN, TX - Destination: DAL - Flight plan: IFR - Airport: DAL, Dallas Love Field Airport, runway 31R, 7,753 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 27; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 5,960 total, 770 in this make and model, 5,670 as pilot in command, 55 in the last 90 days, 11 in the last 30 days ## Weather - Conditions: Instrument (IMC), Day - Wind: calm - Visibility: 0.75 statute miles - Lowest ceiling: 600 ft broken - Temperature: 32 °F - Altimeter: 30.00 inHg ## 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 20000127043969A](https://openairdocs.org/incident/20000127043969A), Jan 27, 2000: Mtsbsi MU300, Dallas, TX, Substantial damage. (-23) During ILS approach to rwy 31R at dal, a warning light for ice accumulation on the horizontal stabilizer illuminated. The aircraft was landed at 120K in… 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.