CEN20LA125 · Mitsubishi MU 2B-40
Mitsubishi MU 2B-40 · Accident: loss of control on ground during landing
From New Holstein Municipal Airport (8D1) to Flying Feathers Airport (11Y)
Event
- NTSB case
- CEN20LA125
- 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 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
- N425GZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Holstein Municipal Airport (8D1), New Holstein, WITo Flying Feathers Airport (11Y), Chilton, WI
- Aircraft age
- About 40 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
- 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
- Loss of control on ground
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
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 was landing the turbine-powered airplane on a 2,500-ft-long frozen, turf runway. The pilot reported to the manufacturer that, during the landing roll, the airplane yawed left and the right wing contacted the ground, resulting in substantial damage. Examination of the airplane did not reveal any anomalies that would have resulted in a directional control issue. According to the pilot operating handbook, the airplane’s landing distance over a 50-ft for a dry, hard surface runway was about 2,500 ft. The manufacturer estimated that this distance for a wet or turf runway were about 4,250 ft. The pilot did not respond to requests for information regarding his flight planning or estimated landing distance. The pilot's decision to land on a runway that provided an inadequate distance likely resulted in an inability to maintain control of the airplane during the landing roll.
Probable cause
The pilot's decision to land on the turf runway with insufficient landing performance and his subsequent loss of control during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA125
- Event ID
- 20200318X52128
- Case number
- CEN20LA125
- 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: 5fa6b815a6270e909ff547732d8b056f66b9ae856c8e6fbae8b3e4352f1cbd55; retrieved 2026-09-16T11:19:46.624Z.