CEN13CA474 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of control in flight during landing
From Clare Municipal Airport (48D) to Clare Municipal Airport (48D)
Event
- NTSB case
- CEN13CA474
- 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
- N2195T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clare Municipal Airport (48D), Clare, MITo Clare Municipal Airport (48D), Clare, MI
- 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
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that during landing approach the airplane was low, slow and drifting to the left of the runway. He took control of the airplane and attempted a go-around maneuver but the airplane settled into tall grass to the left of the runway. The flight instructor reported no preimpact mechanical malfunctions or failures of the airplane. The student pilot reported that during the landing approach the flight instructor told him that the approach speed was too low. At that point, the flight instructor took control of the airplane and attempted a go-around but a gust of wind pushed the airplane to the left side of the runway where it touched down and bounced. The airplane subsequently impacted the side of a ditch bank and came to a stop. The airplane sustained substantial damage including a separated landing gear, firewall damage, and bending of the aft fuselage.
Probable cause
The flight instructor's failure to adequately monitor the landing approach, his delayed corrective action and his failure to maintain directional control that resulted in the airplane's collision with a ditch adjacent to the runway. The student pilot's failure to maintain a proper glidepath contributed to the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA474
- Event ID
- 20130809X95359
- Case number
- CEN13CA474
- 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: 67916be01333442f195b07f125236eedf6fd7447fc10f775f0877b708406bd40; retrieved 2026-09-15T22:28:34.794Z.