ERA21LA185 · Cessna 182Q
Gud Luk Cruzin Cessna 182Q · Accident: hard landing
From Cincinnati Municipal Airport Lunken Field (LUK) to an unrecorded destination
Event
- NTSB case
- ERA21LA185
- 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
- Event fatalities
- Unknown
- 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 182Q
- 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
- N735LC
- Operator
- Gud Luk Cruzin
- Onboard fatalities
- Unknown
- Route
- From Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OHTo not recorded
- Aircraft age
- About 44 years (built 1977)
- 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
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he planned to practice landings at a nearby airport. During the first approach, the crosswind was higher than he expected, so he completed a go-around, but remained in the traffic pattern and completed a normal landing. Subsequently, he departed from the other end of the runway and remained in the traffic pattern to complete a touch-and go. During the landing the airplane bounced three times, which became progressively harder, and after the third bounce the pilot performed a go-around. The pilot completed a normal landing following the bounced landing, taxied to the ramp, and secured the airplane noting damage to the propeller. Further examination of the airframe after the accident revealed that the lower forward portion of the fuselage had been substantially damaged during the accident sequence.
Probable cause
The pilot’s improper recovery from a bounced landing, which resulted in a subsequent hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA185
- Event ID
- 20210415102914
- Case number
- ERA21LA185
- 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, cause areas. 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: 8a5762e35dc6ab83109fc2a3bf3d7789d836d12325c024b5bce164496afa9990; retrieved 2026-09-16T13:56:59.949Z.