Small plane’s Wings Break Apart in Storm | ATC Audio & Exclusive Artcc, Sheriff, Jtoc Comms

Advertisement

The Gap Looked Safe on the Screen

On August 11, 2022, Piper PA-32 N720RP was returning from Indiana toward Pennsylvania when the pilot began discussing a line of precipitation with Cleveland Center. The pilot was not instrument-rated and was operating in conditions where the distinction between a visible opening and a safe route through a storm line was critical.

Accident Facts

Date
11 August 2022
Location
Near Metz, West Virginia
Operation
Part 91 personal flight
Outcome
3 fatalities; aircraft destroyed
Investigation
NTSB ERA22FA368
Timeline
07:35 EDT —
N720RP departed Deck Airport in Pennsylvania.
1.
15:43 EDT —
The aircraft departed Daviess County Airport in Indiana on the return flight.
2.
About 17:52 EDT —
The aircraft was cruising near 9,500 feet south of a line of precipitation.
3.
About 18:01 —
The pilot discussed a left deviation based on the cockpit weather display.
4.
18:01:31 —
The pilot's final transmission indicated he was proceeding toward the apparent gap.
5.
Shortly afterward —
The aircraft transitioned through increasingly intense precipitation.
6.
About 18:03 —
Track data showed a steep descending right turn.
7.
18:05 EDT —
The flight was lost near Metz, West Virginia.
8.

At about 9,500 feet, the pilot told the controller that he was looking at his cockpit NEXRAD display and considering a deviation through what appeared to be a gap. The controller cautioned that the line contained moderate to heavy precipitation with pockets of extreme echoes and warned that the apparent gaps might not be real from the airplane's position.

The pilot continued toward the area he believed was open.

The Controller Warned About the Difference Between a Gap and a Safe Gap

The pilot nevertheless chose to continue.

The NTSB later found that the pilot was likely using cockpit NEXRAD for tactical avoidance without accounting for the latency inherent in the creation and delivery of the imagery. That distinction is fundamental. Datalink weather is not a real-time radar picture. The display can represent conditions that existed earlier, while the storm itself has moved and changed.

The Weather Data Was Not the Same Weather the Pilot Was Flying Through

The investigation reconstructed the flight through radar and weather data. After the final transmission, the aircraft continued through echoes that progressed from light and moderate precipitation into heavy and extreme precipitation.

The wreckage distribution supported an in-flight breakup. The debris field extended roughly 0.8 miles, and fracture surfaces were consistent with overstress. Investigators found no pre-impact mechanical anomaly that would have prevented normal operation.

The aircraft therefore did not break apart because an unexplained structural failure suddenly occurred. The breakup followed the flight into severe precipitation and the subsequent loss of control.

The Pilot Knew the Storm Was There

The accident is not well described as a case in which the pilot was unaware of bad weather. The ATC communications show active discussion of the precipitation line. The pilot was trying to find a route around it.

The problem was the operational interpretation of the displayed information. The apparent opening was treated as a tactical corridor even though the data itself was delayed and the controller's display showed significant precipitation ahead.

The NTSB's finding also matters because the pilot did not hold an instrument rating. The decision to penetrate worsening precipitation therefore occurred in an environment that exceeded the pilot's demonstrated qualification and eventually removed visual and aerodynamic control margins.

What the Records Show

The NTSB determined: “The non-instrument-rated pilot’s intentional visual flight into instrument meteorological conditions based on latent weather information, which resulted in the airplane entering extreme precipitation, a loss of aircraft control, and in-flight break-up.”

The Board's wording ties together qualification, decision-making, weather information and the final loss of control. It does not say that NEXRAD itself caused the accident. The problem was using delayed information for tactical penetration of a severe weather line.

Why This Incident Matters

The phrase “gap in the radar” can sound reassuring, but a gap on a weather display is not a guarantee of a gap in the atmosphere. The weather system is moving, the data is delayed and the display is an aid to planning rather than a clearance to penetrate.

The accident also shows why avoidance must remain the primary strategy around severe convective weather. Once the aircraft entered the strongest precipitation, the pilot had few remaining options.

For the reconstruction, the ATC audio is particularly instructive because the warning is audible before the accident sequence. The controller's uncertainty about the gap was itself a safety signal. The safest interpretation was to remain clear of the line rather than test the opening.

Evidence and Findings

The weather reconstruction makes the latency problem concrete. The pilot's final communications occurred while the aircraft was still several miles from the strongest precipitation. After the last transmission, the track continued into progressively stronger radar returns until it reached extreme precipitation.

The pilot's qualification was another part of the safety chain. He held a private pilot certificate but did not hold an instrument rating. The accident flight therefore entered instrument meteorological conditions despite the pilot not being qualified for instrument flight. The investigation connected that operational decision with the use of delayed weather information and the eventual loss of control.

The Accident Was Not a Sudden Surprise

The final loss of control came quickly, but the decision chain had been developing for several minutes. The pilot was aware of the weather, was communicating with ATC and was actively trying to find a route through the precipitation. That makes the case more instructive than an unexplained encounter with a storm.

The danger was the gradual erosion of the safety margin. The displayed weather suggested an opening, the aircraft turned toward it, and the actual precipitation became progressively more severe. Once the airplane entered extreme precipitation, aerodynamic control and visibility margins were overwhelmed.

The investigation therefore points toward avoidance discipline rather than a last-second recovery technique. The safest gap was the gap around the storm line, not the gap that appeared on a delayed display.

The Weather Display Was a Planning Tool, Not a Tunnel Through the Storm

The NTSB's discussion of linked weather data is especially relevant to the ATC recording. The controller's display and the pilot's cockpit display were not identical representations of the same instant. Both were products of weather surveillance systems with processing and transmission delays.

That means the word “gap” should never be interpreted as a guarantee that the aircraft can safely fly through the opening. A storm cell can move into the corridor before the displayed image catches up, and precipitation intensity can change faster than the pilot expects. The safe operational response is to maintain generous separation from convective weather rather than attempt to thread a narrow opening based on delayed information.

The accident ultimately converted a weather-avoidance decision into an aerodynamic and structural emergency. Once the aircraft entered extreme precipitation, the remaining options were minimal.

  • Datalink NEXRAD is not a live tactical weather-avoidance radar.
  • A displayed gap may not be a safe gap at the aircraft's current position.
  • Severe convective weather should be avoided rather than penetrated.
  • Pilot qualification and recent experience matter when weather deteriorates beyond VFR capability.
  • ATC warnings about severe precipitation should be treated as operational information, not background commentary.

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident