CHI00LA304 · Cessna 182S
Cessna 182S · Accident: hard landing
From Wichita Dwight D. Eisenhower National Airport (ICT) to an unrecorded destination
Event
- NTSB case
- CHI00LA304
- 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
- Instrument 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
- N97TD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wichita Dwight D. Eisenhower National Airport (ICT)To not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said he began his roundout approximately 20 feet above the runway. 'As the throttle was pulled to idle, the aircraft ballooned to about 5 feet and the stall warning horn sounded.' The pilot said he lowered the nose slightly, the airplane touched down on its main gear, and 'bounced again about 5 feet.' The pilot lowered the nose again to just above level flight. 'The aircraft sank rapidly and impacted firmly on the main gear.' The nose gear struck the runway and collapsed. 'The aircraft bounced again - about 5 feet, then landed on the mains first with the nose dropping. The final bounce was approximately 10 feet above the runway, and settled rapidly in a slight nose up attitude. The airplane landed on the main landing gear, then the nose. The aircraft was allowed to coast to [taxiway] A5, and was turned off the runway using brakes.' An examination of the airplane revealed no anomalies.
Probable cause
the pilot's failure to maintain aircraft control during the landing. Factors relating to this accident were the pilot's improper recovery from the bounced landing and his failure to go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA304
- Event ID
- 20001212X21936
- Case number
- CHI00LA304
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-09-22.
- API snapshot SHA-256: 83d86ddd6866f24836ac91228bcf478e2c8ea7f2387f596fe2acd9a730f9e22a; retrieved 2026-09-22T12:25:52.371Z.