DEN06MA119 · Mitsubishi MU-2B-35
Berg Steel Pipe Mitsubishi MU-2B-35 · Accident: in flight encounter with weather en route
From Tulsa International Airport (TUL) to Argyle, FL
Event
- NTSB case
- DEN06MA119
- 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
- 1 · 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
- Instrument Meteorological Cond
Mitsubishi MU-2B-35
- 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
- N6569L
- Operator
- Berg Steel Pipe
- Onboard fatalities
- Unknown
- Route
- From Tulsa International Airport (TUL), Tulsa, OKTo Argyle, FL
- 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 · descent
- 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 › Aircraft control, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
- Pilot in command › Flight into adverse weather, inadvertent
- Wing, spar › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Prior to the accident flight, the pilot obtained a preflight weather briefing and filed an instrument flight rules flight plan. The briefer noted no adverse weather conditions along the route. The airplane departed the airport at 0853, and climbed to FL190. The first two hours of the flight was uneventful, and the aircraft was handed off to Jacksonville Air Route Traffic Control Center (ZJX ARTCC) at 1053. The pilot contacted ZJX Crestview sector at 1054:45 with the airplane level at FL190. At 1102, the Crestview controller broadcasted an alert for Significant Meteorological Information (SIGMET) 32E, which pertained to thunderstorms in portions of Florida southwest of the pilot's route. At 1103, the controller cleared to the airplane to descend to 11,000 feet and the pilot again acknowledged. At 1110:21, the pilot was instructed to contact Tyndall Approach. The pilot checked in with the Tyndall RAPCON North Approach controller at 1110:39. The pilot was told to expect a visual approach. Shortly thereafter, the pilot transmitted, "...we're at 11,000, like to get down lower so we can get underneath this stuff." The controller told the pilot to stand by and expect lower [altitude] in 3 miles. About 15 seconds later, the controller cleared to pilot to descend to 6,000 feet, and the pilot acknowledged. At 1112:27, the pilot was instructed to contact Tyndall Approach on another frequency. The airplane's position at that time was just northwest of REBBA intersection. The Panama sector controller cleared the pilot to descend to 3,000 feet at his discretion, and the pilot acknowledged. There was no further contact with the airplane. The controller attempted to advise the pilot that radar contact was lost, but repeated attempts to establish communications and locate the airplane were unsuccessful. A witness, located approximately 1 mile south of the accident site, reported he heard a "loud bang," looked up and observed the airplane in a nose down spiral. The witness reported there were parts separating from the airplane during the descent. The witness stated it was raining and there was lightning and thunder in the area. Local authorities reported that the weather "was raining real good with lightning and the thunderstorm materialized very quickly." The main wreckage came to rest near the edge of a swamp in tree covered and high grassy terrain. The left wing, left engine, and the left wing tip tank were located in a wooded area approximately 0.6 miles northwest of the main wreckage. The left wing separated from the airplane inboard of the left engine and nacelle. Examination of the fracture surfaces indicated that both the front and rear spars failed from "catastrophic static up-bending overstress..." The airplane flew through an intense to extreme weather radar echo containing a thunderstorm. Although the controllers denied that there was any weather displayed ahead of the airplane, recorded radar and display data indicated that moderate to extreme precipitation was depicted on and near the route of flight. During the flight, the pilot was given no real-time information on the weather ahead. The airplane was equipped with a weather radar system and the system provided continuous en route weather information relative to cloud formation, rainfall rate, thunderstorms, icing conditions, and storm detection up to a distance of 240 miles. No anomalies were noted with the airframe and engines.
Probable cause
the pilot's inadvertent flight into thunderstorm activity that resulted in the loss of control, design limits of the airplane being exceeded and subsequent in-flight breakup. A contributing factor was the failure of air traffic control to use available radar information to warn the pilot he was about to encounter moderate, heavy, and extreme precipitation along his route of flight,
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06MA119
- Event ID
- 20060906X01291
- Case number
- DEN06MA119
- 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: bc540d72e77219e1ea0b5472f5a72d3e80de71833ae5bca542e540816223f445; retrieved 2026-09-20T17:04:23.076Z.