WPR20LA054 · Mitsubishi MU2B 60
Mitsubishi MU2B 60 · Accident: communication system malfunction/failure during landing
From North Platte Regional Airport Lee Bird Field (LBF) to Miley Memorial Field (BPI)
Event
- NTSB case
- WPR20LA054
- 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
- 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 MU2B 60
- Aircraft type
- Mitsubishi MU2
- 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
- N43866
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Platte Regional Airport Lee Bird Field (LBF), North Platte, NETo Miley Memorial Field (BPI), Big Piney, WY
- Aircraft age
- About 39 years (built 1980)
- 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
- Landing · landing roll
- Defining eventThe 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
- Communication system malfunction/failure
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the approach and landing flare were normal; however, as he moved both throttles to the beta position, it appeared that the left propeller went into the beta position while the right one did not. This resulted in a course deviation and runway excursion to the left, which led to the separation of the right main landing gear and substantial damage to the right wing. The National Transportation Safety Board was unable to conduct a follow-up examination, as the airplane has been sold and a chain of custody had been compromised. As a direct result of the airplane not being able to be examined, the cause of the right propeller failure to correspond to the throttle movement to the beta position is undetermined.
Probable cause
The failure of the right propeller position to correspond to the throttle change when moved to the beta position for reasons that could not be determined based on available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20LA054
- Event ID
- 20191230X20237
- Case number
- WPR20LA054
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b208a5bbc18e019ad9986dc9143ff477ef5fe762552e846e6cb89a20a468534b; retrieved 2026-09-16T10:50:18.189Z.