CHI07CA278 · Piper PA-28-180
Piper PA-28-180 · Accident: on ground/water collision with object during takeoff
From Hagerstown, IN to Indianapolis Regional Airport (MQJ)
Event
- NTSB case
- CHI07CA278
- 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
- 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-28-180
- 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
- N15425
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hagerstown, INTo Indianapolis Regional Airport (MQJ), Indianapolis, 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 · rejected takeoff
- 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
- On ground/water collision with object
- 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
- Pilot in command › Aborted takeoff, delayed
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, used
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted a fence and nosed over during an aborted takeoff from runway 20 (4,000 feet by 200 feet, wet grass). The pilot stated, "It was 8:00 AM the grass was a little tall and covered with heavy dew. I did not feel that the plane was accelerating like I thought that it should." The pilot reported that about halfway down the runway the airplane lifted "slightly off the turf, then settled back down" and headed left of the centerline. The pilot said that the airplane "slid on the wet grass, struck a steel farm fence, and nosed over ... in a soybean field." The pilot reported no mechanical malfunctions with the airplane in reference to the flight.
Probable cause
The pilot's use of an unsuitable runway for takeoff and delayed aborted takeoff. Factors were the wet grass and the fence the airplane impacted and subsequently nosed over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA278
- Event ID
- 20071018X01616
- Case number
- CHI07CA278
- 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: investigation status, coordinates. 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: 1afc955bf93ba1d4de5289bd6bb23116f096cf9a6c0b60909a528801cfd01f45; retrieved 2026-09-22T03:29:33.615Z.