NYC93FA177 · Mitsubishi MU-2B-40
Mitsubishi MU-2B-40 · Accident: total loss of engine power (mechanical failure) en route
From Rochester International Airport (RST) to Roanoke–Blacksburg Regional Airport (ROA)
Event
- NTSB case
- NYC93FA177
- 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
- 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-40
- 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
- N965MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rochester International Airport (RST), Rochester, MNTo Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VA
- 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
- En route · cruise
- 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
- Total loss of engine power (mechanical failure)
- 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 › Emergency procedure, improper
- Pilot in command › Wrong engine shutdown, inadvertent
- Torquemeter system › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THE RIGHT ENGINE FAILED, FOLLOWED BY THE LEFT ENGINE APPROXIMATELY ONE MINUTE LATER WHILE HE WAS IN CRUISE AT 25000 FT. HE SAID HE INITIATED A STEEP DESCENT TO GET BELOW 18000 FT, AND ATTEMPTS AT RESTARTING THE LEFT ENGINE WERE UNSUCCESSFUL. THE PILOT LANDED 500 FT DOWN A 1900 FT LONG RUNWAY AND RAN OFF THE DEPARTURE END, 300 FT, INTO A WOODED AREA. POST ACCIDENT INVESTIGATION FOUND 130 GALLONS OF FUEL ONBOARD IN THE MAIN TANKS. THE FUEL WAS TESTED AND FOUND TO BE FREE OF WATER. THE FUEL LINES WERE FREE OF OBSTRUCTIONS AND THE FUEL PUMPS WORKED. A FAILED TORQUE SENSOR WAS FOUND ON THE LEFT ENGINE WHICH WOULD DISCONNECT THE LEFT ENGINE DRIVEN FUEL PUMP. THE RIGHT ENGINE WAS TEST RUN SATISFACTORILY.
Probable cause
was improper emergency procedures by the pilot which resulted in the shutdown of an operative engine, following a power loss due to a failed torque sensor in the other engine, which resulted in a total power loss approach, landing, and overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93FA177
- Event ID
- 20001211X13219
- Case number
- NYC93FA177
- 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: 882a3a87c8fc47d94154e2eef75e65823cf66a30feb20a5ce2022d96b200a07a; retrieved 2026-09-21T22:49:33.875Z.