ERA09CA121 · Lake LA-4-200
Lake LA-4-200 · Accident: hard landing
From Orlando Executive Airport (ORL) to Apopka, FL
Event
- NTSB case
- ERA09CA121
- 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
- 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
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
- N85213
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (ORL), Orlando, FLTo Apopka, 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
- 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 had completed two water landings to a lake and was climbing the airplane for a third when, about 200 feet above the water, he reduced power to simulate a "power out or reduced power landing." As the pilot "attempted to round out the glide for the landing," he could not arrest the descent and the airplane landed hard. The pilot took off again, then made a precautionary water landing to a full stop. The airplane and engine appeared to be undamaged, so the pilot took off again and made two touch-and-go landings to another lake, followed by a full stop landing. At that point the engine sounded "rough," so the pilot taxied to shore where he discovered that a propeller blade tip was missing, that a propeller strike had occurred to the turtle top, and that the hull was taking on water. Mechanics later changed the propeller, and the airplane was deemed airworthy to fly to another location for further inspection. A few days later, structural damage was found to cross-frames in the hull. Weather at a nearby airport, about the time of the hard landing, included clear skies and calm winds.
Probable cause
The pilot's improper flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA121
- Event ID
- 20090102X45707
- Case number
- ERA09CA121
- 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. 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: 9de89f622886450dac150a2d0e4acf153a06827a80a61bfd7bf1724252bf81b0; retrieved 2026-09-15T10:39:36.161Z.