MIA88LA098 · Grumman AA-5B
Grumman AA-5B · Accident: hard landing
Event
- NTSB case
- MIA88LA098
- 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
Grumman AA-5B
- Aircraft type
- Grumman AA-5
- 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
- N28571
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 › Airspeed, not maintained
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of Clearwater, FL, the place the record names. Not the accident site.
NTSB narrative
PLT STATED ACFT STALLED DURING LANDING FLARE RESULTING IN A HARD LANDING. AFTER THE HARD LANDING THE ACFT BOUNCED INTO THE AIR AND VEERED TO THE LEFT. BEFORE A GO-AROUND COULD BE COMPLETED THE ACFT COLLIDED WITH A DIRT MOUND BETWEEN THE RUNWAY AND TAXIWAY CAUSING SEPARATION OF THE RIGHT MAIN GEAR AND FURTHER LOSS OF CONTROL. THE ACFT THEN COLLIDED WITH BUSHES AND A FENCE COMING TO REST. ARPT AUTHORITIES STATED THE DIRT MOUND STRUCK BY THE AIRCRAFT WAS THERE FOR CONSTRUCTION REASONS AND WAS APPROXIMATELY 70 FEET TO THE LEFT OF THE RUNWAY AND WAS 5 FEET HIGH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88LA098
- Event ID
- 20001213X24953
- Case number
- MIA88LA098
- 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: ce681ccb901388de212768e3aa07d3ab632c7f0053231a958a32350b7de959a6; retrieved 2026-09-23T11:08:41.337Z.