NYC06MA208 · Mitsubishi MU-2B-40
Mitsubishi MU-2B-40 · Accident: in flight encounter with weather en route
From Monroe County Airport (KBMG) to Governor's Harbour Airport (MYEM)
Event
- NTSB case
- NYC06MA208
- 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
- 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
- N171MA
- Operator
- Ward T. Walter · private individual
- Onboard fatalities
- Unknown
- Route
- From Monroe County Airport (KBMG), Bloomington, INTo Governor's Harbour Airport (MYEM), Governors Harbo
- 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
- In flight encounter with weather
- 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 › Flight into adverse weather, inadvertent
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 had received an outlook briefing during the morning hours before the accident. The briefing included information regarding widely scattered thunderstorms and rain showers along portions of the pilot's planned route of flight. At the time of the accident, a convective weather significant to the safety of all aircraft (convective SIGMET) was in effect for the pilot's route of flight, and the information about the convective SIGMET was broadcast to the pilot by air traffic control (ATC). Several airplanes in the vicinity of the accident airplane were deviating around weather. Conversations between the accident pilot and the ATC controller were consistent with the accident airplane's weather radar functioning, and the possibility that the accident airplane's weather radar was providing more information than the ATC weather radar. Although the pilot initially declined a deviation query by ATC, he later accepted one. Shortly after, the pilot was unable to maintain his assigned altitude of 28,000 feet msl (FL 280), and the airplane impacted terrain consistent with a vertical descent. At the time of the accident, at FL 280, weak to moderate weather radar echoes existed. Very strong to intense weather radar echoes were seen about FL 200. The ATC facility was equipped with NEXRAD-derived weather displays. The weather displays had four settings: below FL 240, between FL 240 and FL 330, above FL 330, and from sea level to FL 600. At the time of the accident, the ATC controller's weather display indicated weak to moderate echoes above FL240. Very strong to intense weather radar echoes existed about FL200; however, the ATC controller did not have his weather display set to that altitude as he was not controlling traffic at that altitude. The investigation could not determine if the pilot was aware of the stronger intensity echoes below his altitude, or if the airplane's weather radar was depicting the stronger echoes. Examination of the wreckage did not reveal any preimpact mechanical malfunctions.
Probable cause
The pilot's inadvertent encounter with thunderstorms.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06MA208
- Event ID
- 20060906X01296
- Case number
- NYC06MA208
- 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: 31393133bce0b70e25e5e1b50e9afcd68d6613d05991d74036a8b0b543264496; retrieved 2026-09-20T17:04:50.841Z.