FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA276 · Piper PA 30

21 Jul 2016 · Plainfield, IL, United States

Piper PA 30 · Accident: loss of control in flight en route

From Upper Cumberland Regional Airport (SRB) to Eagle River Union Airport (EGV)

Report a problem

Event

NTSB case
CEN16FA276
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
Unknown
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 PA 30

Aircraft type
Piper PA-30
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
N7409Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Upper Cumberland Regional Airport (SRB), Sparta, TNTo Eagle River Union Airport (EGV), Eagle River, WI
Aircraft age
About 52 years (built 1964)
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
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot departed on a cross-country flight in the multi-engine airplane and attempted to use visual flight rules flight following from air traffic control during the flight. The availability of this service is based on controller workload, and, as the flight neared an area of Class B airspace, the controller discontinued flight following services and instructed the pilot to remain clear of the Class B airspace. The airplane then climbed from its cruise altitude of 8,500 ft mean sea level (msl) to 10,300 ft msl while losing airspeed until reaching about 48 kts, well below its lowest published stall speed. The airplane subsequently entered a series of descending turns, reaching an airspeed of about 211 kts that exceeded the airplane's design maneuvering speed. The airplane experienced an in-flight breakup.

Weather radar imagery identified reflectivity values consistent with convective activity immediately adjacent to the airplane's position just before the time of the accident. It is likely that the pilot initiated the climb in order to remain clear of the developing convective activity, and it is also likely that the airplane entered instrument meteorological conditions sometime between the initiation of the climb and the loss of control. The convective conditions present at the time of the accident were conducive to the development of updrafts, downdrafts, and turbulence; however, there were no recorded pilot reports for this area and the exact conditions encountered by the accident airplane could not be determined.

Although maintenance records indicated that the airplane had undergone recent maintenance to the left wing and rivet holes in the left wing spar exhibited signs of anomalous installation, this likely did not contribute to the accident, since a performance study determined that the airplane exceeded its design maneuvering speed, which put the airplane at risk of exceeding its design load limitations and the subsequent structural failure.

Toxicology findings indicated that the pilot was using two antidepressants, one of which, trazodone, is potentially impairing. While symptoms of depression often include cognitive deficits, it is impossible to know what, if any, medication side effects or cognitive symptoms the pilot may have been experiencing at the time of the accident. Therefore, whether his depression or its treatment contributed to the circumstances of the accident could not be determined from the available information.

Probable cause

The pilot's failure to maintain airplane control during an en route climb near convective activity, which resulted in an aerodynamic stall, an uncontrolled descent, and a subsequent in-flight breakup due to an exceedance of the airplane's design load limitations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA276
Event ID
20160721X74604
Case number
CEN16FA276
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. 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: 7b78c9fa23ac4b79fa7b9eef3e5ed32461af7b37d7cc6d691a3ca41770933158; retrieved 2026-09-14T21:55:54.819Z.