CEN13LA552 · Piper PA 28-180
Piper PA 28-180 · Accident: hard landing
From William Tiny Zehnder Field (66G) to William Tiny Zehnder Field (66G)
Event
- NTSB case
- CEN13LA552
- 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
- N4756L
- Operator
- Ferrier Mark A
- Onboard fatalities
- Unknown
- Route
- From William Tiny Zehnder Field (66G), Frankenmuth, MITo William Tiny Zehnder Field (66G), Frankenmuth, MI
- Aircraft age
- About 46 years (built 1967)
- 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
- Landing
- 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
- Hard landing
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that an intermittent engine power loss occurred during the initial takeoff climb. Despite troubleshooting efforts, the engine continued to run intermittently as the pilot initiated a turn back toward the airport. The pilot attempted to land on the runway but then chose to conduct a forced landing to a hayfield. The airplane subsequently rolled into a cornfield and was substantially damaged. Postaccident examinations of the airframe, engine, and fuel system revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The recorded temperature and dew point at the time of the accident was conducive for the accumulation of carburetor icing during glide power settings. However, the intermittent engine power loss occurred while the airplane was at a high-throttle setting during initial climb, which was not consistent with carburetor icing.
Probable cause
An intermittent loss of engine power for reasons that could not be determined because postaccident examinations revealed no anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA552
- Event ID
- 20130919X43425
- Case number
- CEN13LA552
- 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, 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: b2ed6589d9c815df66a95d23f06efc4e4bcf38df47df087373759fe3f9371909; retrieved 2026-09-15T22:53:02.446Z.