FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA160 · Piper Aircraft Inc PA 46-350P

16 Apr 2024 · Hartsburg, MO, United States

Upward Aviation Piper Aircraft Inc PA 46-350P · Accident: loss of control in flight en route

From Dane County Regional Truax Field (MSN) to Smith Field (SLG)

Report a problem

Event

NTSB case
CEN24FA160
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
Visual Meteorological Cond

Piper Aircraft Inc PA 46-350P

Aircraft type
Piper PA-46
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
N451MA
Onboard fatalities
Unknown
Route
From Dane County Regional Truax Field (MSN), Madison, WITo Smith Field (SLG), Siloam Springs, AR
Aircraft age
About 12 years (built 2012)
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 · cruise
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
Loss of control in flight
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
  • Aircraft › Aircraft structures
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was on an instrument flight rules flight and air traffic control (ATC) provided the pilot with vector guidance to avoid an active military operations area (MOA). The controller informed the pilot that he would only be able to deviate to the left of his course due to the active MOA. At that time, the airplane was in an area of developing convective weather activity and likely in instrument meteorological conditions. The pilot reported to ATC that he encountered freezing rain. ATC communications revealed that the pilot requested to deviate to the left of his course due to weather, including mention of encountering freezing rain, which ATC approved. Flight track data showed the airplane entered a descending left turn. A performance study based on the aircraft track data showed that, during the turn, the airplane’s roll angle reached 70°, the pitch angle reached -17° and then -34°, and the calibrated airspeed exceeded both the airplane's published never exceed speed (VNE), and its maximum operating maneuvering speed (VO). During the turn, the airplane’s structure broke apart, and wreckage was distributed along a 3-mile path. The flight path depicted in the flight track data was consistent with a loss of airplane control. Postaccident examination of the airplane confirmed that the horizontal stabilizer and the wings failed in a downward direction. A failure of the airplane’s horizontal stabilizer would result in the airplane pitching forward and a high negative load to the wings. The examination noted that all identified failures in the airplane structure had signatures consistent with overload failure. Examination of the airplane’s flight control system did not reveal any preexisting anomalies. The cockpit avionics could not be tested due to impact damage. Based on the available data, the pilot encountered forecast adverse weather associated with convective activity. The pilot noted to ATC that he encountered freezing rain, however, the quantity of ice accumulation and its effect on the flight could not be determined. While attempting to deviate from his flight path to avoid this weather, airplane control was lost and it entered a steep descending turn. During the turn, the airplane’s speed exceeded its published never exceed speed, which resulted in overload failure of the horizontal stabilizer and subsequent failure of the airplane’s wings.

Probable cause

The pilot’s encounter with convective weather conditions, which resulted in a loss of airplane control, the exceedance of the airplane’s never exceed speed, and the resulting overload failure of the horizontal stabilizer and subsequent failure of the airplane’s wings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA160
Event ID
20240416194102
Case number
CEN24FA160
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, coordinates, 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: 86d02305dc9c9d7783e979f34847a660725bed49313e91dde6339116c052c82a; retrieved 2026-09-15T08:12:48.278Z.