FTW00FA070 · Mitsubishi MU-2B-26A
Mitsubishi MU-2B-26A · Accident: loss of engine power during takeoff
From San Antonio International Airport (SAT) to Tucson International Airport (TUS)
Event
- NTSB case
- FTW00FA070
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mitsubishi MU-2B-26A
- Aircraft type
- Mitsubishi MU-2
- 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
- N386TM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo Tucson International Airport (TUS), Tucson, AZ
- 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 91: General Aviation
- 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
- Takeoff
- 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vmc), not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Witnesses reported that during the airplane's takeoff roll they heard a heard a series of repeated sounds, which they described as similar to a "backfire" or "compressor stall." Several witnesses reported seeing the airplane's right propeller "stopped." One witness reported that as the airplane lifted off the ground, he heard "a loud cracking sound followed by an immediate prop wind down into feather." He continued to watch the airplane, as the gear was retracted and the airplane entered a climb and right turn. Subsequently, the airplane pitched up, entered a "Vmc roll-over," followed by a 360-degree turn, and then impacted the ground. Radar data indicated the airplane took off and climbed on runway heading to a maximum altitude of about 200 feet agl. The airplane than entered a right turn and began to lose altitude. A radar study revealed that the airplane's calibrated airspeed was 97 knots when the last radar return was recorded. According to the flight manual, minimum controllable airspeed (Vmc) was 93 knots. Examination of the accident site revealed that the airplane impacted the ground in a near vertical attitude. A post-crash fire erupted, which destroyed all cockpit instruments and switches. Examination of the propellers revealed that neither of the propellers were in the feathered position at the time of impact. Examination of the left engine revealed signatures consistent with operation at the time of impact. Examination of the right engine revealed that the second stage impeller shroud exhibited static witness marks indicating that the engine was not operating at the time of impact. However, rotational scoring was also observed through the entire circumference of the impeller shroud. The static witness marks were on top of the rotational marks. Examination of the right engine revealed no anomalies that would have precluded normal operation. The left seat pilot had accumulated a total flight time of about 950 hours of which 16.9 hours were in an MU-2 flight simulator and 4.5 hours were in the accident airplane. Although he had started an MU-2 Pilot-Initial training course, he did not complete the course. The right seat pilot had accumulated a total flight time of about 2,000 hours of which 20.0 hours were in an MU-2 flight simulator and 20.6 hours were in the accident airplane. He had successfully completed an MU-2 Pilot-Initial training course one month prior to the accident.
Probable cause
the pilot's failure to maintain the minimum controllable airspeed following a loss of engine power during the initial takeoff climb. Contributing factors to the accident were both pilot's lack of total experience in the make and model of the accident airplane and the loss of right engine power for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00FA070
- Event ID
- 20001212X20356
- Case number
- FTW00FA070
- 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, coordinates. 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: 4e62edc4acd282d1e84c8d77da672f336e1906b975d573ddca2aabcc1c8dd015; retrieved 2026-09-20T21:29:17.485Z.