CEN11LA352 · Aero Commander 100-180
Aero Commander 100-180 · Accident: hard landing
From Perry County Airport (I86) to Ohio University Airport (UNI)
Event
- NTSB case
- CEN11LA352
- 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
Aero Commander 100-180
- Aircraft type
- Aero Commander 100
- 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
- N4016X
- Operator
- Alder William D III · private individual
- Onboard fatalities
- Unknown
- Route
- From Perry County Airport (I86), New Lexington, OHTo Ohio University Airport (UNI), Athens, OH
- 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 · flare/touchdown
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he flew a stable approach and as he flared the airplane, a wind gust raised the nose and slowed the airplane. He added engine power, but the airplane descended and impacted the runway. The right main landing gear collapsed and the airplane skidded off the right side of the runway resulting in a collapsed nose gear and a propeller strike. A postaccident examination of the airplane revealed no preimpact mechanical anomalies, and substantial damage was noted to the firewall and fuselage. Witnesses reported that the airplane was on a high, steep, and fast approach before the landing flare and touchdown occurred near mid-field. The airplane appeared to "balloon" during the flare and stall prior to impact with the runway.
Probable cause
The pilot's failure to maintain adequate airspeed in the flare which resulted in a stall and a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA352
- Event ID
- 20110523X23900
- Case number
- CEN11LA352
- 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: 6c269d56f9d03a594be3a4f483c0a2f9a47bfd48f381a75ccbd82f40e4746bb0; retrieved 2026-09-15T16:11:48.708Z.