MIA82DA107 · Cessna 152
Cessna 152 · Accident: hard landing
From St. Petersburg, FL to Osceola, IA
Event
- NTSB case
- MIA82DA107
- 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
- Visual Meteorological Cond
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N67966
- Operator
- Donald F. Kaltenbach · private individual
- Onboard fatalities
- Unknown
- Route
- From St. Petersburg, FLTo Osceola, IA
- 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 › Go-around, delayed
- Pilot in command › Level off, improper
- Pilot in command › Raising of flaps, premature
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of New Port Richey, FL, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED THAT SHE LANDED WITH 30 DEGREES OF FLAPS ON RUNWAY 23. SHE REPORTED THAT THE WIND WAS GUSTING FROM 15 TO 20 KNOTS AND THE WIND SOCK SEEMED TO FLUCTUATE FROM WESTERLY TO NORTHWESTERLY. THE PILOT RELATED THAT THE AIRCRAFTBOUNCED TWICE UPON LANDING BEFORE SHE APPLIED POWER FOR A GO-AROUND. HOWEVER, THE WING FLAPS HAD BEEN RETRACTED AND THE AIRCRAFT CAME BACK DOWN ON THE RUNWAY AND THE PILOT WAS UNABLE TO MAINTAIN CONTROL AND THE PLANE VEERED OFF THE LEFTSIDE OF THE RUNWAY AND FLIPPED INVERTED INTO A CANAL BESIDE THE RUNWAY. THE PILOT REPORTED THAT THE NOSE GEAR STEERING ROD APPEARED TO HAVE BROKEN DURING A HARD LANDING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA82DA107
- Event ID
- 20020917X02390
- Case number
- MIA82DA107
- 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: 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: d369dcb02dd79f40643b4e43b1e388cf34f72ba4a0b05149ae87d2daa91754e7; retrieved 2026-09-24T03:22:41.100Z.