Corporate Flight Management Mitsubishi MU-300 accident
Mitsubishi MU-300 · Accident: overrun during landing
From Frederick W. Smith International Airport (MEM) to Anderson Municipal Darlington Field (AID)
Event
- NTSB case
- CHI02FA097
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Mitsubishi MU-300
- Aircraft type
- Mitsubishi MU-300
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N617BG
- Operator
- Corporate Flight Management
- Onboard fatalities
- Unknown
- Route
- From Frederick W. Smith International Airport (MEM), Memphis, TNTo Anderson Municipal Darlington Field (AID), Anderson, IN
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Flightcrew › Flight to destination alternate, not performed
- Flightcrew › Missed approach, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The MU-300 on-demand passenger charter flight sustained substantial damage during a landing overrun on a snow/ice contaminated runway. The captain, who was also the company chief pilot and check airman, was the flying pilot, and the first officer was the non flying pilot. Instrument meteorological conditions prevailed at the time of the accident. Area weather reporting stations reported the presence of freezing rain and snow for a time period beginning several hours before the accident. The captain did not obtain the destination airport weather observation until the flight was approximately 30 nautical miles from the airport. The flight received radar vectors for a instrument landing system approach to runway 30 (5,401 feet by 100 feet, grooved asphalt). The company's training manual states the MU-300's intermediate and final approach speeds as 140 knots indicated airspeed (KIAS) and Vref, respectively. Vref was reported by the flight crew as 106 KIAS. During the approach, the tower controller (LC) gave the option for the flight to circle to land or continue straight in to runway 30. LC advised that the winds were from 050-070 degrees at 10 knots gusting to 20 knots, and runway braking action was reported as fair to poor by a snow plow. Radar data indicates that the airplane had a ground speed in excess of 200 knots between the final approach fix and runway threshold and a full-scale localizer deviation 5.5 nm from the localizer antenna. The company did not have stabilized approach criteria establishing when a missed approach or go-around is to be executed. The captain stated that he was unaware that there was 0.7 percent downslope on runway 30. The company provided a page from their airport directory which did not indicate a slope present for runway 30. The publisher of the airport directory provided a page valid at the time of the accident showing a 0.7 percent runway slope. Runway slope is used in the determination of runway performance for transport category aircraft such as the MU-300. The airplane operating manual states that MU-300 landing performance on ice or snow covered runways has not been determined. The airplane was equipped with a cockpit voice recorder with a remote cockpit erasure control. Readout of the cockpit voice recorder indicated a repetitive thumping noise consistent with manual erasure. No notices to airman pertaining to runway conditions were issued by the airport prior to the accident.
Probable cause
Missed approach not executed and flight to a destination alternate not performed by the flight crew. The tail wind and snow/ice covered runway were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02FA097
- Event ID
- 20020401X00430
- Case number
- CHI02FA097
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 93ea2f6ef59b0849ade08acf195d17c1f0259fdd1cdde0dbae6ce7b2d0b372ca; retrieved 2026-09-18T16:04:20.144Z.