MIA98LA078 · Lake LA-4-200
Lake LA-4-200 · Accident: airframe, component or system failure during initial climb
Event
- NTSB case
- MIA98LA078
- 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
Lake LA-4-200
- Aircraft type
- Lake LA-4
- 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
- N2994P
- 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
- Initial climb
- 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
- Horizontal stabilizer attachment › Fatigue
- Horizontal stabilizer attachment › Worn
- Manufacturer › Acft/equip, inadequate design
Approximate · Estimated position: the centre of Sarasota, FL, the place the record names. Not the accident site.
NTSB narrative
The pilot had just completed a touch-and-go landing on a lake. During the initial climb at an altitude of less than 500 feet, the airplane shuddered, then pitched nose down. The pilot reduced power and pulled the control column with negative results, then forcibly pushed and pulled the control column, which freed the elevator control. He maneuvered the airplane for an emergency water landing. Postaccident visual examination of the airplane revealed that the left horizontal stabilizer was displaced down about 12 degrees from the normally installed position. Further examination revealed that an attachment ear for the left horizontal stabilizer fitting beam had failed due to fatigue in an area of fretting wear. Fretting wear was also detected on the adjacent angle/top beam. For comparison, the right fitting/beam and angle/top beam were removed and examined. Fretting wear was detected on both components. A small crack was also detected on an attachment for the right fitting/beam, which had originated from fretting wear associated from the respective angle/top beam. An air worthiness directive (AD 98-10-12), effective 6/8/98, was issued to inspect the affected aircraft, to ensure proper clearance, and to correct if fretting, cracking, or corrosion were found.
Probable cause
inadequate clearance and fretting wear of the fitting/beam attachment to the angle/top beam, due to inadequate design, which resulted in fatigue and subsequent failure of the fitting/beam attachment ear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA078
- Event ID
- 20001211X09489
- Case number
- MIA98LA078
- 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: 6dc3d4253c2eee72b4a20d4debc8c4c01fdea8934b505886eb1243ab102474d5; retrieved 2026-09-22T18:05:20.665Z.