CEN17FA297 · Piper PA30
Piper PA30 · Accident: loss of control in flight on approach
From Philip Billard Municipal Airport (TOP) to Philip Billard Municipal Airport (TOP)
Event
- NTSB case
- CEN17FA297
- 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
- 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 PA30
- Aircraft type
- Piper PA30
- 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
- N22HW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Philip Billard Municipal Airport (TOP), Topeka, KSTo Philip Billard Municipal Airport (TOP), Topeka, KS
- Aircraft age
- About 52 years (built 1965)
- 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 · VFR pattern base
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot had been receiving multiengine instruction from the flight instructor in order to obtain a multiengine rating. The accident flight was a practice checkride for the pilot's practical test that was scheduled for the following day. A witness stated that, during the accident takeoff from runway 18, the airplane passed the airport terminal building at a "very low" altitude and stated that it was not climbing very fast. The airplane then turned left and appeared to enter a normal traffic pattern. The witness did not see the accident occur. The airplane came to rest on airport property west of the threshold of runway 18. Data from an onboard engine monitor indicated that right engine power was reduced about 7 minutes before the end of the data, consistent with simulated single-engine operation. The left engine power was then reduced about 2.5 minutes before the data ended, consistent with simulated dual-engine loss of power; however, data was consistent with power being restored and both engines operating normally for about the final minute of the flight.
The damage to the airplane was consistent with a low-speed impact in a left-wing-low and shallow pitch attitude. The left and right propellers displayed S-shaped bending and leading edge polishing consistent with operation. Postaccident examination of the airplane revealed no mechanical anomalies that would have precluded normal airplane operation.
Autopsy of the pilot receiving instruction revealed evidence of severe coronary artery disease, which could cause sudden impairment or incapacitation; however, if that occurred, the flight instructor should have been able to successfully complete the flight. Therefore, it is unlikely the pilot's heart disease contributed to the accident. Toxicology of the pilot revealed the presence of an antidepressant, indicating some degree of underlying depression; however, the flight instructor should have been able to compensate if the pilot had slowed responses to checkride scenarios.
Probable cause
The failure of the pilot and flight instructor to maintain aircraft control while maneuvering in the traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA297
- Event ID
- 20170802X82400
- Case number
- CEN17FA297
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-08-01.
- API snapshot SHA-256: 1ccfc8db8e430a2ef4a313bc791ac08bb9701bcdb32c92b1483c16e2208da62b; retrieved 2026-09-15T06:11:40.375Z.