2 Feb 2021: PIPER PA46 350P — Forza Management Co

2 Feb 2021: PIPER PA46 350P (N221ST) — Forza Management Co

No fatalities • Leicester, MA, United States

Probable cause

The pilot’s failure to maintain the minimum airspeed for flight in icing conditions, which resulted in a loss of elevator control during approach due to ice accumulation.

— NTSB Determination

Accident narrative

On February 2, 2021, about 1655 eastern standard time, a Piper PA-46-350P, N221ST, was substantially damaged when it was involved in an accident near Leicester, Massachusetts. The commercial pilot sustained minor injuries and the two passengers were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot stated that he received weather briefings via flight service and ForeFlight. The flight service specialist advised the pilot that there would be some icing in clouds, with cloud tops near 6,000 ft mean sea level msl (msl). Additionally, an AIRMET was in effect for moderate icing from the freezing level up to 18,000 ft msl. The pilot further stated that his previous flight that day, from Worcester, Massachusetts, to Martha’s Vineyard, Massachusetts, was uneventful. He added that the actual conditions were better than forecast with no ice observed during that flight and the accident flight, until descent for the RNAV (GPS) RWY11 approach to Worcester.

Light freezing rain was reported in the area of the accident site around the time of the accident, and the forecast icing potential indicated a 60% probability of supercooled liquid droplets (SLD) over the accident site, at the time of the accident, at 4,000 ft msl. The current icing potential indicated a 90% to 100% probability of SLD at 1,000 to 4,000 ft msl at the accident site, at 1700.

The pilot reported that, while descending through clouds and beginning the approach, a little ice built up on the wings and he actuated the deice boots twice. The pilot observed the deice boots functioning normally on the wings and could not see the tail. He reported that the elevator “began to shake and became ineffective” and that he “felt like the airplane was approaching a stall.” The pilot applied forward pressure on the yoke and had to trim elevator nose down to get the airplane to descend and avoid a stall, and he reported that any effort to pull back on the yoke exacerbated the situation. He further stated that no caution annunciators illuminated, and that he had disengaged the autopilot before descent. The airplane descended through the clouds and the pilot flew toward trees to avoid a house. The airplane subsequently contacted a tree and came to rest upright in the front yard of a residence about 3 miles from the runway threshold.

Examination of the wreckage did not reveal evidence of any preimpact mechanical malfunctions. Flight control continuity was confirmed from the cockpit to all control surfaces. The flap lever was observed at the 10° flap extension position. Examination of the flap jackscrew revealed about five exposed threads, which corresponded to a flap position between 0° and 10°. Component testing of the deice system did not reveal any anomalies.

Review of air traffic control audio and radar data revealed that the pilot contacted the tower controller at 1653 and reported a position of 1 mile from the RILOC intersection (about 6.5-mile final approach). The controller acknowledged the report and cleared the pilot to land. From that time until the flight upset about 2 minutes later, the airplane’s groundspeed averaged about 82 knots, or an airspeed of 94 knots based on a winds aloft forecast of 060° at 17 knots, at 3,000 ft msl.

Review of a pilot operating handbook (POH) for the airplane make and model revealed a minimum speed for flight in icing conditions as 130 knots indicated airspeed. The POH further stated, “The ice protection system was not designed or tested for flight in freezing rain, freezing drizzle or supercooled liquid water and ice crystals, or conditions defined as severe. Flight in these conditions is prohibited and must be avoided.”

Contributing factors

  • Pilot
  • Compliance w/ procedure
  • Airspeed — Not attained/maintained

Conditions

Weather
VMC, wind 020/13kt, vis 5sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.