FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA258 · Piper PA 28-181

8 Jul 2017 · Waterford, OH, United States

Piper PA 28-181 · Accident: loss of control in flight on approach

From Logansport Cass County Airport (GGP) to Mid Ohio Valley Regional Airport (PKB)

Report a problem

Event

NTSB case
CEN17FA258
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
2 · 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 28-181

Aircraft type
Piper PA-28
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
N793MA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Logansport Cass County Airport (GGP), Logansport, INTo Mid Ohio Valley Regional Airport (PKB), Parkersburg, WV
Aircraft age
About 19 years (built 1998)
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
Approach · IFR initial approach
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot and the passenger were making an instrument flight rules personal cross-country flight in the airplane. Radar data showed that the airplane was in cruise flight about 7,000 ft mean sea level (msl) until the pilot began a descent toward the initial approach fix for the GPS approach to the destination airport. Cloud tops in the area were about 6,200 to 6,900 ft msl; thus, the airplane likely entered clouds (instrument meteorological conditions) as it descended. The final 2.5 minutes of the radar data revealed erratic turns left and right, which were consistent with the pilot becoming spatially disorientated while descending in instrument meteorological conditions. The last radar point recorded the airplane about 2,950 ft msl or about 2,100 ft above ground level (agl); the reported cloud base at the destination airport was 1,200 ft agl. A witness reported that low overcast clouds were present as he heard the airplane fly overhead. The witness saw the airplane exit the clouds in a steep angle of descent with the engine operating at high power. The airplane disappeared behind a tree line and a few seconds later impacted a reservoir. The deviation from the intended flight path, erratic maneuvering, and steep descent in instrument meteorological conditions are consistent with spatial disorientation. A postaccident examination of the airplane and engine did not reveal any mechanical malfunctions or failures that would have precluded normal operation. The engine and propeller exhibited signatures consistent with high engine power at impact. The vacuum pump remained intact and did not exhibit any preimpact anomalies.

Although the pilot held an instrument rating, his total instrument flight experience could not be determined. The pilot's autopsy revealed severe coronary artery disease that put him at risk of an acute coronary event; however, it is unlikely that symptoms of shortness of breath, chest pain, palpitations, or fainting would lead to the type of airplane performance findings present in this case. Therefore, it is unlikely the pilot's heart disease contributed to the accident. Although the coroner's toxicology testing identified ethanol, the fact that it was absent on two other tests of liver and brain tissue indicates it was from sources other than ingestion and did not contribute to the accident. There is no evidence of a medical condition or substance that contributed to this accident.

Probable cause

The pilot's loss of airplane control due to spatial disorientation in instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA258
Event ID
20170708X73501
Case number
CEN17FA258
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: fb69a1a0f420ffa88d11d194932a10e54d0ed46b42686c788c7f1f930be2f006; retrieved 2026-09-15T06:06:24.821Z.