CHI01LA010 · Piper PA-32R-301T PA-32R-301
Piper PA-32R-301T PA-32R-301 · Accident: overrun during takeoff
From Al Meyers Airport (3TE) to Delaware County Johnson Field (MIE)
Event
- NTSB case
- CHI01LA010
- 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
- 0 · 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 PA-32R-301T PA-32R-301
- Aircraft type
- Piper PA-32
- 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
- N289JG
- Operator
- James A. Gecsei · private individual
- Onboard fatalities
- Unknown
- Route
- From Al Meyers Airport (3TE)To Delaware County Johnson Field (MIE), Muncie, IN
- Aircraft age
- Not recorded
- 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
- Takeoff · roll/run
- First occurrenceThe 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
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane overran the runway and collided with soft terrain during an aborted takeoff. The pilot reported the preflight, engine start, and engine run-up were normal. He reported, "At 85 knts, I pulled back on the yoke. It moved only slightly, but the plane would not rotate. I pulled again hard, but still no movement. I then cut the throttle and applied full brakes." The airplane traveled off the end of the runway, across a road, and into a plowed field where the nose gear collapsed and both main gears were separated from the airplane. Inspection of the airplane failed to reveal any failure/malfunction with the flight control systems. Inspection of the engine revealed the three screws that hold the magneto harness cover on the right magneto were missing and the harness was backed away from the magneto. In addition, the turbine in the turbocharger was dragging when he attempted to spin it by hand. Teardown of the turbocharger revealed a build-up of carbon in the heat shield.
Probable cause
The pilot was unable to rotate the aircraft during takeoff for undetermined reasons. A factor associated with the accident was the soft terrain, which the airplane encountered during the aborted takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA010
- Event ID
- 20001212X22122
- Case number
- CHI01LA010
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-10-15.
- API snapshot SHA-256: 9a3f88693d6a4e0f4743efe8b87154f68b803c2e4ad8731dc2952bcf1d16d359; retrieved 2026-09-22T12:22:38.769Z.