CEN16LA322 · Piper J5C
Piper J5C · Accident: loss of control on ground during landing
From Dupont-Lapeer Airport (D95) to Sandusky City Airport (Y83)
Event
- NTSB case
- CEN16LA322
- 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 J5C
- Aircraft type
- Piper J5
- 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
- N30313
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dupont-Lapeer Airport (D95), Lapeer, MITo Sandusky City Airport (Y83), Sandusky, MI
- Aircraft age
- About 76 years (built 1940)
- 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 · landing roll
- 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 on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After completing one full-stop landing on the grass runway in calm wind conditions, the private pilot decided to complete another landing in the opposite direction. During the landing, the tailwheel-equipped airplane bounced multiple times and became airborne again. The airplane then veered to the right and impacted a ditch next to the runway. The pilot stated that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. It is likely that the pilot failed to control the airplane's descent rate and landing flare, which led to the bounced landing. He was then unable to recover and exited the side of the runway.
Probable cause
The pilot's improper landing flare, which resulted in a bounced landing, and a subsequent loss of control followed by a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA322
- Event ID
- 20160816X05940
- Case number
- CEN16LA322
- 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: 8cbc8223a886bb464ea801ca1e1ce5856d634d03e09d4739e56086c507c6879e; retrieved 2026-09-16T04:09:47.133Z.