ERA24FA176 · Piper PA-32R-301
Piper PA-32R-301 · Accident: structural icing en route
From McGhee Tyson Airport (TYS) to Gerald R. Ford International Airport (GRR)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA24FA176
- 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
- 0
- 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
Piper PA-32R-301
- Aircraft type
- Piper PA-32
- 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
- N9236J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From McGhee Tyson Airport (TYS), Knoxville, TNTo Gerald R. Ford International Airport (GRR), Grand Rapids, MI
- Aircraft age
- About 31 years (built 1993)
- 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 · change of cruise level
- Defining eventThe 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
- Structural icing
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on an instrument flight rules cross-country flight. About 15 minutes after departure, shortly after reaching a cruise altitude of 8,000 ft mean sea level (msl), the pilot reported to air traffic control that he was “picking up moisture in the clouds” and asked for a course deviation or a higher altitude. The controller approved course deviations and cleared the pilot to climb to 10,000 ft msl, which the pilot accepted. A performance study of the airplane’s ADS-B flight track data showed that the airplane’s airspeed decreased during the subsequent climb, and the airplane reached a maximum altitude about 8,500 ft msl and a minimum airspeed around 80 knots (kts) before it rapidly rolled left and lost altitude at a rate of about 1,300 ft per minute, consistent with an aerodynamic stall. The airplane briefly leveled off before entering a descending right turn, reaching a descent rate of 6,000 ft per minute. The descending turn continued until flight track data was lost at an altitude about 5,750 ft msl. At this time, the airplane’s calculated calibrated airspeed was about 210 kts; the airplane’s published never-exceed speed (Vne) was 197 kts indicated airspeed. A witness on the ground near the accident site observed the airplane “twirling” as it descended below the clouds and also observed debris falling from the sky. The wreckage was distributed over a distance of more than 10,000 ft, consistent with an in-flight breakup. Postaccident examination of the airplane and engine revealed no evidence of a mechanical failure that would have precluded normal operation. Control cable separations and airframe structural fractures all exhibited characteristics consistent with overload failure. The airplane was not equipped with anti- or de-icing equipment and was not certified for flight into known icing conditions. Review of weather information for the area indicated cloud bases around 4,500 to 5,000 ft with tops around 18,500 ft. The freezing level was around 5,500 ft, with supercooled large droplets (SLD) likely between 6,000 and 8,000 ft. The pilot filed his instrument flight plan for the accident flight with a flight planning application that generated a route briefing. The briefing contained weather information for the route of flight, including the forecast for moderate icing conditions; however, information regarding the potential SLD conditions would have been contained in supplemental icing information not provided in the standard briefing. Whether the pilot accessed supplemental icing information before the flight could not be determined. Flight track information indicated that the airplane likely entered instrument meteorological and icing conditions shortly after takeoff, and that the airframe and flight control surfaces began to accumulate ice rapidly, as the time between the pilot’s request for a higher altitude and the loss of flight track data was about 2 minutes. The airplane then likely encountered an aerodynamic stall while flying at an airspeed of 80 kts (15 kts faster than its maximum published stall speed). This was consistent with the effects of increased drag and stall speed due to ice accretion. It is likely that the pilot lost control of the airplane following the initial aerodynamic stall and was unable to recover. During the subsequent descending turn, the airplane exceeded its structural limitations, resulting in an in-flight breakup. The pilot held an instrument rating; however, review of available logbook information indicated limited recent instrument experience, with two instrument approaches and one holding procedure conducted during an instructional flight about 7 months before the accident. Whether the pilot’s loss of airplane control was the result of his inability to control the airplane due to ice accretion, a lack of proficiency in instrument flight, or a combination of those factors, could not be determined. Although the pilot’s awareness of the potential for SLD could not be determined, the route briefing generated at the time he filed the flight plan provided adequate information to alert him to the potential for icing conditions along his intended route of flight. Nevertheless, the pilot chose to depart and continue into an area with a known potential for icing conditions in the airplane that was not equipped to do so.
Probable cause
The pilot’s decision to depart into an area of instrument meteorological and icing conditions, which resulted in loss of airplane control and a subsequent in-flight breakup.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA176
- Event ID
- 20240412194081
- Case number
- ERA24FA176
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 209193010efae5f9ba8457225c9a7c9751eca591e2839a6eeb06ce6f3b73973f; retrieved 2026-09-15T08:12:33.892Z.