Aviation Accident Summaries

Aviation Accident Summary ERA23FA024

Marietta, OH, USA

Aircraft #1

N515GK

BEECH E-90

Analysis

Shortly after departure to pick up a passenger at their destination airport about 75 nm away, the pilots climbed and turned onto a track of about 115° before leveling off about 11,000 ft mean sea level (msl), where the airplane remained for a majority of the flight. Pilot and controller communications during the flight were routine and there were no irregularities reported. As the airplane descended into the destination airport area, the airplane passed through areas of light to heavy icing where there was a 20 to 80% probability of encountering supercooled large droplets (SLD) during their initial descent and approach. While level at 4,000 ft msl, the flight remained in icing conditions, and then was cleared for the instrument approach to the runway. The flight emerged from the overcast layer as it crossed the final approach fix at 2,800 ft msl; the flight continued its descent and was cleared to land. The controller informed the flight that there was a vehicle on the runway but it would be cleared shortly, which was acknowledged; this was the final communication from the flight crew. Multiple eyewitnesses and security camera footage revealed that the airplane, while flying straight and level, suddenly began a steep, spinning, nearly vertical descent until it impacted a commercial business parking lot; the airplane subsequently collided with several unoccupied vehicles and caught fire. The airplane was certified for flight in known icing conditions and was equipped with pneumatic deice boots on each of the wings and tail surfaces. The pneumatic anti-icing system was consumed by the postimpact fire; the control switches were impact and thermally damaged and a reliable determination of their preimpact operation could not be made. Further examination of the airframe and engines revealed no indications of any preimpact mechanical anomalies that would have precluded normal engine operation or performance. During the approach it is likely that the airframe had been exposed to and had built-up ice on the control surfaces. It could not be determined if the pilots used the pneumatic anti-icing system, or if the system was inoperative, based on available evidence. Review of the weather conditions and the airplane’s calculated performance based on ADS-B data, given the speeds at which the airplane was flying, and the lack of any discernable deviations that might have been expected due to an extreme amount of ice accumulating on the airframe, it is also likely that the deice system, if operating at the time of the icing encounter, should have been able to sufficiently remove the ice from the surfaces. Although it is also uncertain when the pilots extended the landing gear and flaps, it is likely that the before-landing checklist would be conducted between the final approach fix and when the flight was on its 3-mile final approach to land. Given this information, the available evidence suggests that the sudden loss of control from a stable and established final approach was likely due to the accumulation of ice on the tailplane. It is likely that once the pilots changed the airplane’s configuration by extending the landing gear and flaps, the sudden aerodynamic shift resulted in the tailplane immediately entering an aerodynamic stall that maneuvered the airplane into an attitude from which there was no possibility to recover given the height above the ground. Postaccident toxicological testing detected the presence of delta-8 THC. Delta-8 THC has a potential to alter perception and cause impairment, but only the non-psychoactive metabolite carboxy-delta-8-THC was present in the pilot’s liver and lung tissue. Thus, it is unlikely that the pilot’s delta-8-THC use contributed to the accident.

Factual Information

HISTORY OF FLIGHTOn October 18, 2022, at 0709 eastern daylight time, a Beech E-90, N515GK, was substantially damaged when it was involved in an accident in Marietta, Ohio. The two commercial pilots were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 positioning flight. The flight originated at the John Glenn Columbus International Airport (CMH), Columbus, Ohio, about 0640 and was enroute to Mid-Ohio Valley Regional Airport (PKB), Parkersburg, West Virginia. Automatic dependent surveillance - broadcast (ADS-B) data revealed that after takeoff from CMH the airplane climbed and turned on a ground track of 115°, and then leveled off at 11,000 ft mean sea level (msl), where it remained for most of the enroute portion of the 75-nautical-mile (nm) flight. Air traffic control (ATC) communication information revealed that the flight crew was in communication with the Indianapolis Air Route Traffic Control Center during the enroute portion the flight and that all communications with the controllers were normal with no indication of any irregularities. After departing the cruise portion of the flight, in preparation for the approach into PKB, the airplane descended at a rate of about 1,200 ft per minute at a calculated airspeed of 122 knots. As the airplane approached PKB, the controllers cleared the flight to descend and maintain 4,000 ft msl. About 0706, the pilot contacted PKB requesting the RNAV approach to runway 21 and was instructed to report upon reaching MIDCO, the Final Approach Fix (FAF) for that instrument approach. MIDCO was 5.9 nm from the runway threshold and had a minimum crossing altitude of 2,800 ft msl. The pilots were subsequently cleared for the RNAV RWY 21 approach. The airplane leveled off at 2,800 ft msl and increased speed to 150 knots and turned on a long final approach to join the RNAV RWY 21 instrument approach procedure. Shortly after, the pilots were instructed to contact the PKB control tower. Subsequent communication exchanges with the controllers were normal. Figure 1 - Airplane flight path with selected times and altitudes annotated. A portion of the RNAV (GPS) RWY 21 instrument approach procedure has been superimposed onto aerial imagery. About 0709, as the airplane was on a 3-mile final approach, the controller notified the pilots that there was a vehicle on the runway checking for wildlife and that it would be cleared shortly; this was acknowledged by the pilots. About 1 minute later, the airplane was observed emerging from the overcast cloud layer while it simultaneously crossed MIDCO, after which the pilots were cleared to land on runway 21. It was traveling about 170 knots and aligned with the runway heading. The speed decreased to 126 knots in preparation for approach and landing. (The airplane’s published approach speed was about 90 knots and the stall speed was about 65 knots with full flaps [88 knots with no flaps at maximum gross weight]). There were no additional communications received from the flight crew. Multiple eyewitnesses located on the airport and area surrounding the accident site reported that the airplane, while flying straight and level, suddenly began a steep descent and spun near vertically to the ground. Security camera footage from multiple camera angles showed the airplane’s descent through impact, which was consistent with the eyewitness’s accounts (see figure 2). Figure 2 - Three sequential still images from the security camera video showing the airplane’s near vertical descent to impact. Note landing light and position light. AIRCRAFT INFORMATIONThe airplane was a high-performance, conventional-tail, pressurized, twin-engine turbo-propeller airplane and was designed and equipped for flight in instrument meteorological conditions, day or night, and into known or forecast icing conditions. The surface deice system would remove ice accumulation from the leading edges of the wings and stabilizers through the use of pneumatic boots. Ice would be removed by alternately inflating and deflating the deice boots. Pressure-regulated bleed air from the engines supplied pressure to inflate the boots. A venturi ejector, operated by bleed air, created a vacuum to deflate the boots and hold them down while not in use. To assure operation of the system in the event of failure of one engine, a check valve was incorporated in the bleed air line from each engine to prevent loss of pressure through the compressor of the inoperative engine. Inflation and deflation phases were controlled by a distributor valve. A three-position switch in the ICE PROTECTION group on the pilot's subpanel, placarded SURFACE DEICE - SINGLE - OFF MANUAL, controlled the deicing operation. The switch was spring-loaded to return to the OFF position from SINGLE or MANUAL. When the SINGLE position was selected, the distributor valve would inflate all of the airframe boots, both wings and tail. After an inflation period of approximately 7 seconds, an electronic timer switched the distributor to deflate the boots. After these boots have inflated and deflated, the cycle was complete. When the switch was held in the MANUAL position, all the boots would inflate simultaneously and remain inflated until the switch was released. The switch returned to the OFF position when released. After the cycle, the boots would remain in the vacuum hold-down condition until again actuated by the switch. According to the airplane’s Airplane Flight Manual (AFM) landing checklist: Figure 3 - Excerpt from AFM showing the landing checklist items. METEOROLOGICAL INFORMATIONWeather information at the time of the accident indicated that there were pilot reports throughout the area for trace to moderate icing conditions and AIRMETs for moderate icing. Weather satellite data showed supercooled liquid water clouds from 1,300 ft above ground level (agl) to about 8,000 ft agl. Mid-Ohio Valley Regional Airport (PKB), Parkersburg, West Virginia, had the closest official weather station to the accident site and was the intended destination airport. PKB had an Automated Surface Observing System (ASOS) and reports that were augmented by ATC. The PKB ASOS was located 4 miles south-southwest of the accident site at an elevation of 808 ft and issued the following observations surrounding the period of the accident. The PKB reported weather at 0653 included wind from 260° at 3 knots, visibility 10 miles or greater, overcast ceiling at 1,400 ft agl, temperature of 3° C, dew point temperature 1°C, and an altimeter setting of 29.80 inches of mercury. The sea level pressure was 1009.4 hPa, temperature 3.3°C, and dew point temperature 0.6°C. The reported weather at PKB at 0750 included wind from 260° at 6 knots, visibility 10 miles or greater, overcast ceiling at 1,300 ft agl, temperature of 3°C, dew point temperature 1°C, and an altimeter setting of 29.81 inches of mercury. The NWS Current Icing Product (CIP) and Forecast Icing Product (FIP) were intended to supplement other icing advisories such as AIRMETs and SIGMETs. The CIP icing probabilities and severity and 1-hour forecast was valid at 0700 and showed that at 3,000, 4,000, and 5,000 ft, there was a 60 to 85% probability of icing at 3,000 to 5,000 ft surrounding the accident area (see figure 4). Furthermore, the icing intensity near the accident site ranged from “light” to “heavy,” with a 20 to 80% probability of Supercooled Large Droplets (SLD). For additional weather information see the meteorology factual report in the public docket for this investigation. Figure 4 - Icing probability and severity charts with accident location annotated. A search of archived information indicated that the accident pilot(s) did not request weather information from Leidos Flight Service. The accident pilot(s) did use their ForeFlight account to gather and receive a weather briefing through ForeFlight about 2008 on October 17. The ForeFlight weather briefing from 2008 on October 17 contained all the standard weather forecast information valid then through the proposed departure and flight time, starting at 0630 on October 18. While the text AIRMETs (Sierra and Zulu) were highlighted for the accident flight route, the G-AIRMETs were not forecast for the region after 0500 due to it being beyond the G-AIRMET forecast issuance timeframe. No weather imagery was viewed in the ForeFlight application before the flight. AIRPORT INFORMATIONThe airplane was a high-performance, conventional-tail, pressurized, twin-engine turbo-propeller airplane and was designed and equipped for flight in instrument meteorological conditions, day or night, and into known or forecast icing conditions. The surface deice system would remove ice accumulation from the leading edges of the wings and stabilizers through the use of pneumatic boots. Ice would be removed by alternately inflating and deflating the deice boots. Pressure-regulated bleed air from the engines supplied pressure to inflate the boots. A venturi ejector, operated by bleed air, created a vacuum to deflate the boots and hold them down while not in use. To assure operation of the system in the event of failure of one engine, a check valve was incorporated in the bleed air line from each engine to prevent loss of pressure through the compressor of the inoperative engine. Inflation and deflation phases were controlled by a distributor valve. A three-position switch in the ICE PROTECTION group on the pilot's subpanel, placarded SURFACE DEICE - SINGLE - OFF MANUAL, controlled the deicing operation. The switch was spring-loaded to return to the OFF position from SINGLE or MANUAL. When the SINGLE position was selected, the distributor valve would inflate all of the airframe boots, both wings and tail. After an inflation period of approximately 7 seconds, an electronic timer switched the distributor to deflate the boots. After these boots have inflated and deflated, the cycle was complete. When the switch was held in the MANUAL position, all the boots would inflate simultaneously and remain inflated until the switch was released. The switch returned to the OFF position when released. After the cycle, the boots would remain in the vacuum hold-down condition until again actuated by the switch. According to the airplane’s Airplane Flight Manual (AFM) landing checklist: Figure 3 - Excerpt from AFM showing the landing checklist items. WRECKAGE AND IMPACT INFORMATIONThe airplane impacted an automobile dealership parking lot at an elevation of 614 ft msl about 3 miles northeast of the approach end of runway 21 at PKB. The airplane struck several vehicles before coming to rest on level pavement. The wreckage path was compact and oriented on a heading of 305° magnetic. All major components of the airplane were accounted for at the accident site. The cockpit and forward portions of the fuselage were crushed aft. A significant postimpact fire ensued consuming a majority of the fuselage and the cockpit area. The fuselage above the floorboards was totally consumed by fire. The instrument panel and all associated instrumentation, gauges, and switches were severely impact and thermally damaged. The left and right flaps, which were significantly damaged by impact and postimpact fire, remained attached to their respective mounts; the actuators indicated a flap position of 15°. Partial flight control continuity from the cockpit to the ailerons, elevator, and rudder was established through cables, bell cranks, and push/pull rods. All breaks in the cables consisted of a “broom straw” appearance indicative of overload and push/pull rod damage was consistent with overload and thermal damage. The pneumatic anti-icing system, including bleed lines, pneumatic boots, and their respective operating system on each of their respective wing leading edges and empennage, were consumed by postimpact fire; the switches were impact and thermally damaged. A reliable determination of their preimpact operation could not be made. Both engines were located in the wreckage in their respective attachment locations and both displayed significant impact and thermal damage. On-scene examination revealed that both engines displayed rotational contact signatures to their internal and external components, which is indicative of power generation at impact. There were no indications of any preimpact mechanical anomalies to any of the engine components that would have precluded normal engine operation. Both left and right propeller assemblies impact-separated from their respective engine propeller shaft flanges. All 4 blade shanks on each of the 2 assemblies remained attached to their respective hubs. There were no discrepancies noted in the components examined that would prevent or degrade normal operation before impact with terrain; all damage was consistent with high impact forces. Blade damage included chordwise/rotational scoring on both camber and face sides, bending forward/thrust direction, bending opposite rotation, and leading-edge gouging consistent with impact while rotating with power. There was no damage to indicate either propeller was feathered or at low pitch/idle power at the time of impact. Impact signatures indicated the blade angle for both propellers were approximately 30° while rotating with power and generating thrust. A Garmin GTN 750 was recovered from the wreckage and sent to the NTSB vehicle recorders laboratory for examination. The units exhibited severe impact and fire damage. The unit’s internal circuit boards were fire damaged and the extent of the damage precluded normal and advanced recovery procedures. No data pertinent to the accident were recovered. ADDITIONAL INFORMATIONA performance study revealed that the glide performance for the E90 model was not available, but the Beech B200 had a glide performance of 2 nm for every 1,000 ft of altitude. The final descent to the wreckage location was not consistent with a loss of power. Pilot reports throughout the area stated trace to moderate icing conditions and AIRMETs and upper air soundings reported moderate or greater icing potential (rime, clear, mixed) from 2,600 ft through 9,000. A simplified aerodynamic model of the airplane was constructed to estimate body attitudes and aerodynamic coefficients during the flight. Absolute values of each parameter were estimated, with the trends reflective of the airplane’s aerodynamic behavior. Lift and drag increased with pitch as the airplane climbed and then leveled during cruise flight. Drag also increased during descents when the airplane maintained or decreased speed. However, drag did not increase substantially enough during the flight to indicate a buildup of ice on the airframe. If icing was present, the calculations made from the ADS-B flight path data were not able to capture its effects. Additionally, icing effects localized to a control surface or similar would not be discernible from just flight path data alone. The FAA Advisory Circular AC_91-74B, the effect of icing section 3-7 Tailplane icing, stated the following: “a. Downward Lift. Most aircraft have a nose-down pitching moment from the wings because the center of gravity (CG) is ahead of the center of lift. It is the role of the tailplane to counteract this moment by providing downward lift. The result of this configuration is that actions that move the wing away from stall, such as deployment of flaps or increasing speed, may increase the negative AOA [angle of attack] of the tail. With ice on the tailplane, it may stall after deployment of flaps.” This could result in a sudden pitchover. Section b. states, “Tailplane Stall. Since the tailplane is ordinarily thinner than the wing, it is a more efficient collector of ice. On most aircraft, the tailplane is not visible to the pilot, who therefore cannot observe how well it has been cleared of ice by any deicing system. Thus, it is important that the pilot be alert to the possibility of tailplane stall, particularly after full flap deflection, on airplanes not evaluated for susceptibility. A no-flap landing should be considered to avoid a tailplane stall, consistent with AFM procedures.” MEDICAL AND PATHOLOGICAL INFORMATIONThe Montgomery County Coroner’s Office performed the autopsy of t

Probable Cause and Findings

Structural icing on the tailplane that resulted in a tailplane stall and subsequent loss of control.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports