Twin Cessna inflight break up due to severe turbulence — Fatality-5

Twin Cessna In-Flight Breakup in Severe Turbulence — 5 Fatalities

The pilot had already told air traffic control that the airplane was in serious turbulence.

The Cessna 421C was flying through a deteriorating weather system over the Gulf of Mexico when the pilot reported significant turbulence and then a startling descent rate of about 2,000 feet per minute. He wanted out of the weather and asked ATC for assistance.

The controller offered a way forward and then asked whether the pilot wanted to reverse course.

The pilot chose to turn around.

Seconds later, he declared an emergency and transmitted a final, chilling message: the airplane was upside down.

There were no further radio calls.

Radar contact disappeared as the aircraft descended out of coverage. Later, search crews found a debris field stretching across the Gulf of Mexico. The Cessna 421C, registration N4467D, had broken apart after penetrating the core of a severe thunderstorm.

All five people aboard—the commercial pilot and four passengers—were killed.

The accident occurred on July 8, 2009, about 25 nautical miles northwest of Port Richey, Florida, while the airplane was flying from McKinney, Texas, to Tampa. The NTSB investigation, ERA09FA389, determined that the accident resulted from the pilot's decision to continue into a known area of adverse weather, leading to inadvertent penetration of a severe thunderstorm, loss of control and in-flight breakup. (NTSB Data)

A Flight Into a Growing Weather Threat

N4467D was a Cessna 421C Golden Eagle III, a pressurized twin-engine aircraft manufactured in 1979. It was configured for seven occupants and equipped with two Continental GTSIO-520-L engines, each producing 375 horsepower.

The aircraft was also equipped with several systems intended to help the pilot manage weather, including airborne weather radar, a Stormscope lightning-detection system and an XM satellite weather receiver. The aircraft had been modified with winglets, spoilers and vortex generators. At the time of the accident, the airplane had accumulated approximately 4,326 hours. (NTSB Data)

The flight originated at Collin County Regional Airport near McKinney, Texas, and was destined for Tampa International Airport in Florida. It was an IFR flight conducted under Part 91 as a corporate flight.

Before departure, the pilot had obtained weather information from the Houston Automated Flight Service Station. According to the NTSB, he was aware that thunderstorms were present along the route and anticipated deviating around them if necessary. (NTSB Data)

That detail became important later.

The accident was not caused by a storm that suddenly appeared without warning. Convective weather was already known to be present along the route.

The pilot had also been receiving additional information during the flight. While communicating with Jacksonville Air Route Traffic Control Center, he requested weather information and reports from other aircraft regarding the ride conditions. (NTSB Data)

The situation was therefore one in which the pilot knew weather was a factor, had access to weather information and had the ability to request deviations.

But thunderstorms were developing across the route faster than the situation could be managed safely.

The First Signs of Trouble

At approximately 2:46 p.m. local time, the Cessna entered an area of significant turbulence.

The pilot contacted Jacksonville Center and asked for directions to get out of it.

The controller advised him that if he continued straight ahead for roughly two minutes, he should clear the weather.

A 2,000-fpm descent in this situation was not simply an uncomfortable ride.

It was evidence that the aircraft was encountering powerful vertical air movement associated with the convective system.

The Final Seconds

The sequence was remarkably short.

The Cessna had gone from reporting significant turbulence to reporting a 2,000-foot-per-minute descent, then requesting a course reversal, and finally reporting an extreme loss of control.

The phrase "upside down" provides an indication of how rapidly the aircraft's attitude had deteriorated.

In severe convective turbulence, the atmosphere can impose rapid changes in vertical velocity and attitude. Strong updrafts and downdrafts can cause large altitude excursions, while turbulence can generate rapid roll and pitch changes.

Once the airplane entered the most intense part of the storm, the pilot was no longer simply navigating around bad weather. He was dealing with a rapidly changing aerodynamic environment.

The NTSB's reconstruction showed that the airplane deviated south and then southwest into a much stronger area of weather. The aircraft subsequently entered an echo with a radar reflectivity of approximately 50 dBZ, classified in the investigation as extreme intensity. (NTSB Data)

That area was associated with a rapidly developing cumulonimbus cloud.

Investigators found evidence that the airplane penetrated the storm's main core.

The Radar Picture Was Getting Worse

One of the most important aspects of this accident is that the weather was not simply "rain."

The NTSB's meteorological investigation reconstructed the storm environment using NEXRAD radar data and satellite imagery.

Initially, the airplane was operating through radar echoes of approximately 20 to 30 dBZ, consistent with moderate rain.

About four minutes before the accident, the aircraft entered an area with echoes of 35 to 40 dBZ, associated with heavy rain and convective activity.

The distinction between those values matters.

Increasing radar reflectivity generally indicates increasing precipitation intensity, but the radar display is not a direct measurement of turbulence. It also does not tell a pilot exactly what the aircraft will experience inside a storm.

A thunderstorm is a three-dimensional atmospheric system containing rapidly moving air, heavy precipitation, hail, lightning and potentially extreme vertical currents.

The most dangerous part can be hidden inside the precipitation.

Airborne Weather Radar Was Not a Guarantee

N4467D was equipped with airborne weather radar, but the presence of radar did not make penetrating the storm safe.

The NTSB specifically examined the limitations of airborne weather radar in its investigation.

Weather radar detects precipitation. It does not directly detect turbulence.

A radar screen can show an area of heavy precipitation, but the system does not display the actual vertical acceleration or wind forces that the aircraft will experience.

The other major limitation is attenuation.

As radar energy travels through heavy precipitation, part of the signal is absorbed or scattered. In sufficiently intense precipitation, the radar beam can lose so much energy that it cannot properly display what lies beyond the strongest portion of the storm.

This can create what is commonly called a radar shadow.

A pilot may therefore see what appears to be a weaker area beyond a strong cell when the radar beam is actually being blocked by precipitation.

The NTSB emphasized that pilots should not assume that the complete extent of heavy precipitation is visible on the radar display. (NTSB Data)

For N4467D, investigators concluded that near the heavier echoes, the aircraft's weather radar may not have accurately represented the echoes along the flight path. Consequently, the final penetration into the intense part of the storm was considered likely to have been unintentional. (NTSB Data)

That finding is important.

The investigation did not conclude that the pilot deliberately pointed the airplane into the strongest part of the storm knowing exactly what was ahead.

Instead, the available evidence indicated that the airplane's final penetration into the storm's most intense region was likely the result of the limitations of the weather information available in that environment.

A Storm With an Overshooting Top

Satellite imagery provided another critical piece of evidence.

The intense radar echo was associated with a rapidly developing cumulonimbus cloud that had a defined overshooting top.

An overshooting top occurs when powerful updrafts push a portion of a thunderstorm above the surrounding anvil. It is a visual indication of strong vertical development and can be associated with a particularly intense convective cell.

Investigators determined that the storm was in its mature stage or near maximum intensity when the aircraft entered the area. (NTSB Data)

This explains why the conditions encountered by the Cessna could change so rapidly.

It was interacting with a developing convective system capable of producing powerful vertical air currents.

Why Severe Turbulence Can Break an Airplane Apart

Turbulence by itself does not automatically mean an aircraft will break apart.

Aircraft are designed and certified to withstand substantial loads, and pilots routinely encounter turbulence without structural damage.

The problem arises when the combination of aircraft speed, maneuvering and atmospheric vertical motion produces loads beyond the structure's capability.

An aircraft entering a strong updraft can experience a rapid increase in aerodynamic loading. A downdraft can then produce the opposite effect. If the airplane is simultaneously rolling or pitching, the resulting aerodynamic forces can become even more complex.

The pilot may also be forced to make rapid control inputs.

This is why standard thunderstorm-avoidance guidance emphasizes avoiding the storm rather than attempting to fight through its strongest regions.

The NTSB's investigation noted that FAA guidance described airborne weather radar primarily as an avoidance tool, not as equipment intended to make penetration of severe thunderstorms safe. (NTSB Data)

Once N4467D entered the extreme echo, the available margin disappeared rapidly.

The Debris Field

Search and rescue operations began after radar and radio contact were lost.

The U.S. Coast Guard searched the Gulf of Mexico using surface vessels and aircraft.

At approximately 8:00 p.m. on July 8, a debris field was located on the water. It stretched approximately two miles in length and was about 100 yards wide.

The following day, investigators located another, larger debris field approximately four miles northeast of the first. (NTSB Data)

The distribution of debris was consistent with the aircraft breaking apart before reaching the water.

No survivors were found.

The search was eventually suspended, and later side-scan sonar operations identified several underwater targets. However, the wreckage was never recovered for a complete physical examination. (NTSB Data)

The absence of a recovered wreckage site could have made the investigation substantially more difficult. Instead, investigators were able to reconstruct much of the accident using radar data, satellite imagery, communications and the location of the debris fields.

What Happened to the Five People Aboard?

The Cessna carried five people: the 33-year-old commercial pilot and four passengers.

All five were fatally injured.

The flight was a corporate trip, and contemporary reporting described the occupants as people associated with the company operating the aircraft. Initial news reports focused on the Coast Guard search and the discovery of the debris field approximately 20 miles west of Port Richey. (desastresaereosnews.blogspot.com)

The accident drew attention because the pilot had been communicating with ATC only moments before the aircraft disappeared.

For those listening to the radio communications, the final exchange makes the event particularly difficult to comprehend: a pilot asks for help escaping turbulence, reports a severe descent, agrees to reverse course and then, seconds later, reports that the airplane is inverted.

There was no extended distress call.

There was almost no time.

The airplane had been manufactured in 1979 and had accumulated approximately 4,326 hours. Its most recent annual inspection had been completed in August 2008, and maintenance had been performed two days before the accident. (NTSB Data)

However, the NTSB's probable cause did not identify a pre-existing structural or mechanical failure.

The absence of recovered wreckage meant investigators could not conduct the same level of structural examination that would have been possible had the airplane remained accessible. Nevertheless, the combination of radar evidence, weather analysis, flight sequence and debris distribution provided a coherent picture of thunderstorm penetration and breakup.

The NTSB's Probable Cause

After reviewing the flight history, weather data, radar information, communications and wreckage distribution, the NTSB identified the central causal sequence.

The agency's official probable-cause statement reads:

— National Transportation Safety Board, ERA09FA389. (NTSB Data)

That sentence is important because it does not simply say "severe turbulence caused the crash."

First, the pilot continued operating in an area where significant adverse weather was known to exist.

Third, the aircraft lost control.

Finally, the aircraft broke apart in flight.

The weather was the immediate physical environment, but the investigation focused on the decision to continue operating into known adverse conditions.

Accident Facts

The official NTSB docket contains the investigation's chronological flight summary, ATC information, meteorological report, weather overlays, radar data, satellite imagery and debris-field documentation. (NTSB Data)

The ATC Lesson

The ATC recordings associated with N4467D are particularly valuable because they show the accident developing in real time.

The controller did not simply ignore the aircraft.

When the pilot reported turbulence, the controller attempted to provide a route out of the weather. When the pilot reported a 2,000-fpm descent, the controller offered a course reversal.

The problem was that the aircraft was already in a rapidly changing convective environment.

ATC can provide weather information, vectors and traffic services, but controllers cannot see the exact turbulence forces being experienced by an individual aircraft. The pilot remains responsible for deciding whether the aircraft can safely continue the flight.

This distinction is important when listening to the radio exchange.

The controller's suggestion to reverse course was not itself identified by the NTSB as the cause of the accident. The final report placed the causal decision on the pilot's operation into known adverse weather. (NTSB Data)

But once the aircraft was inside the most intense part of the storm, there was little time left for any solution.

What Pilots Can Learn From N4467D

The accident provides several enduring lessons for pilots operating in convective weather.

First, avoid severe thunderstorms rather than attempting to penetrate them.

Second, understand radar limitations.

Weather radar displays precipitation, not turbulence. Heavy precipitation can also attenuate the radar beam and hide additional cells behind the strongest returns. (NTSB Data)

Third, treat rapidly worsening turbulence as a warning to reassess the entire flight.

The pilot had already reported significant turbulence and a 2,000-fpm descent before the final loss of control. At that point, the weather was no longer a minor deviation problem.

Fourth, do not allow the planned destination to dictate the decision.

Tampa was still the intended destination, but reaching it was no longer the important objective. The safest outcome would have been to create maximum distance from the convective system.

FAA thunderstorm guidance cited in the NTSB investigation emphasized avoiding severe or intense echoes by substantial margins and warned pilots not to underestimate thunderstorms based on visual appearance or apparently weaker radar areas. (NTSB Data)

The Broader Aviation Safety Lesson

The Cessna 421C did not disappear because of one dramatic mechanical failure.

It was the final link in a chain that developed over several minutes.

The pilot knew thunderstorms were along the route. He had received weather information and pilot reports. The aircraft had sophisticated weather equipment. ATC was available. Yet the aircraft eventually entered an extreme convective cell and was destroyed.

That is what makes this accident so instructive.

Technology can improve a pilot's understanding of weather, but it cannot remove the hazard. Airborne radar can show precipitation, but it cannot display every turbulent current. Satellite weather can provide valuable strategic information, but it is not a substitute for real-time conditions. ATC can help pilots navigate around storms, but the pilot remains responsible for deciding when the safest choice is to stop pressing toward the destination.

On July 8, 2009, N4467D entered an environment where the aircraft's available margins disappeared in seconds. The final radio transmission—an indication that the airplane was inverted—came only moments before radar contact was lost.

Five people never reached Tampa.

The lasting lesson is not that a Cessna 421 was incapable of handling turbulence. It is that no light aircraft should be expected to defeat a severe thunderstorm.

The safest encounter with a thunderstorm is the one that never happens. When the weather ahead is deteriorating, turning away early is not a failure of a flight plan. It is the fundamental purpose of sound aeronautical decision-making.

Sources

• https://data.ntsb.gov/Docket?NTSBNumber=ERA09FA389