FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA85LA129 · Grumman AA-5

22 Mar 1985 · Okeechobee, FL, United States

Grumman AA-5 · Accident: airframe, component or system failure during an emergency descent

From Lakeland Linder International Airport (LAL) to Treasure Coast International Airport (FPR)

Report a problem

Event

NTSB case
MIA85LA129
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-5

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
N5867L
Operator
Roman A. Swiezy · private individual
Onboard fatalities
Unknown
Route
From Lakeland Linder International Airport (LAL), Lakeland, FLTo Treasure Coast International Airport (FPR), Fort Pierce, FL
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
Emergency descent
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
Airframe, component or system failure
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(vmo), exceeded
  • Pilot in command › Design stress limits of aircraft, exceeded

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE IN CRUISE FLT THE PLT PLACED THE ACFT IN A DIVE TO AVOID WHAT APPEARED TO BE THE LANDING LIGHT OF ANOTHER ACFT. THE LIGHT WAS ACTUALLY A SPACE VEHICLE WHICH HAD JUST BEEN LAUNCHED FROM CAPE CANAVERAL AIR FORCE STATION 60 MILES FROM THE ACFT'S POSITION. DURING THE DIVE THE PLT EXCEEDED THE LIMITATIONS OF THE ACFT CAUSING DAMAGE TO THE ACFT'S TAILSURFACES WHICH BEGAN TO FLUTTER AFTER LEVEL FLT WAS REGAINED. DURING THE FOLLOWING EMERGENCY LANDING IN A FLD, THE ACFT STRUCK A FENCE POST AND NOSED UP, COLLAPSING THE NOSE LANDING GEAR.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA85LA129
Event ID
20001214X35997
Case number
MIA85LA129
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: 7aeffcbd8f4ffd35859dde28cc45b6117d3cc0d22587f2a6082504a1baf8f065; retrieved 2026-09-23T18:17:18.183Z.