CEN14CA355 · Cessna 182S
Cessna 182S · Accident: abnormal runway contact during landing
From Washington County Airport (KAFJ) to Put In Bay Airport (3W2)
Event
- NTSB case
- CEN14CA355
- 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
Cessna 182S
- Aircraft type
- Cessna 182
- 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
- N2366G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Washington County Airport (KAFJ), Washington, PATo Put In Bay Airport (3W2), Put in Bay, OH
- Aircraft age
- About 16 years (built 1998)
- 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
- Abnormal runway contact
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers were on a cross-country flight. Upon arrival to the destination airport, the pilot entered the traffic pattern for landing. He reported that the downwind leg was too close to the runway, so he departed the pattern and re-entered for a more stable approach. During the landing he looked for birds and the displaced threshold; he flared the airplane too high, landed hard and bounced. The airplane landed hard a second time, before the pilot executed a go-around. The pilot then conducted a normal landing. Examination of the airplane revealed substantial damage to the firewall and damage to the propeller tips.
Probable cause
The pilot's improper flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA355
- Event ID
- 20140711X04435
- Case number
- CEN14CA355
- 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: aecc0041f098de2160f4d27c427ee21167b369928329d19c0df458774a61949a; retrieved 2026-09-16T00:53:31.833Z.