FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20LA201 · Piper PA28 235

31 May 2020 · Carlinville, IL, United States

Piper PA28 235 · Accident: aircraft structural failure while maneuvering

From Creve Coeur Airport (1H0) to Fitch H Beach Airport (FPK)

Report a problem

Event

NTSB case
CEN20LA201
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
4 · 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 PA28 235

Aircraft type
Piper PA28
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
N8991W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Creve Coeur Airport (1H0), Maryland Hgts, MOTo Fitch H Beach Airport (FPK), Charlotte, MI
Aircraft age
About 56 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
Maneuvering
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
Aircraft structural failure
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 structures
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Position data depicted the airplane in cruise flight on a northeast course toward the destination airport at 5,500 ft mean sea level (msl). Shortly before the accident, the airplane entered a left turn with a gradually steepening bank angle. After completing a 360º turn and returning to a northeast course, the airplane immediately transitioned into a right turn that continued until the airplane again returned to a northeast course. Airplane bank angles reached 50° and 60° in the left and right turns, respectively. As the right turn continued, the airplane entered a descent and the airspeed increased. The bank angle ultimately reached about 110° (right wing down), the pitch attitude reached 63° nose down, and the airspeed increased to over 200 kts during the descent. The maximum computed load factor based on the available data was 4.72 G. The position data ended when the airplane was between 2,000 ft and 2,500 ft msl (1,400 ft and 1,900 ft above ground level). At the end of the data, the airplane was in a steep, spiral dive and about 35 kts above the never-exceed airspeed (VNE). The airplane was established on a southwesterly course away from the accident site at that time.

The wreckage debris path was oriented on a northeasterly course and was about 400 ft long. The wreckage distribution was consistent with a low-altitude inflight break up. In addition, the presence of all airframe structural components and flight control surfaces within the debris path was consistent with the airplane being structurally intact as it approached the accident site. A postaccident examination revealed that the wing structure failed as a result of overstress. No preimpact anomalies with respect to the flight control system were identified. As a result, the steep descent was likely an intentional action by the pilot but for reasons that could not be determined.

The investigation did not have any data from which to determine the flightpath from the final data point to the accident site. However, because the final segment of the flightpath was toward the southwest and the debris path was oriented to the northeast, it is clear that the pilot attempted to pull out of the dive and, in doing so, reversed course. That maneuver, which was initiated from a steep, spiral dive and above VNE, resulted in the pilot inadvertently exceeding the ultimate load factor for the airframe. The excessive load factor caused the separation of the wings and stabilator, and a loss of control of the airplane.

Probable cause

The pilot’s attempted recovery from a steep descent which inadvertently exceeded the ultimate load factor of the airframe and resulted in a low-level inflight breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA201
Event ID
20200531X82140
Case number
CEN20LA201
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: f3e957942afa6f817515c6483ae9bd0fe6649e76e64a8afee3f9d8bbeada8d5a; retrieved 2026-09-15T07:15:24.405Z.