ERA14CA190 · Progressive Aerodyne Inc SEAREY LSA
Progressive Aerodyne Inc SEAREY LSA · Accident: abnormal runway contact during landing
From Apopka, FL to Tavares, FL
Event
- NTSB case
- ERA14CA190
- 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
Progressive Aerodyne Inc SEAREY LSA
- Aircraft type
- Progressive Aerodyne SEAREY
- 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
- N657G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Apopka, FLTo Tavares, FL
- Aircraft age
- Built the same year (2014)
- 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
- 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
- Abnormal runway contact
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he positioned his airplane to land in an area on a lake with light ripples. During the landing attempt, the airplane bounced and the pilot attempted to continue the landing instead of immediately initiating a go around. The pilot stated that he then elected to perform a go around; however, there was not enough room to clear the trees at the end of the lake. The airplane subsequently impacted the tree line and came to rest.
Post-accident examination of the airplane revealed that both wing leading edges and the empennage incurred substantial damage. The pilot did not report any pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's improper landing flare resulting in a bounced landing and his delay in performing a go around which resulted in a collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA190
- Event ID
- 20140410X34218
- Case number
- ERA14CA190
- 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: 2e0ac3717f8273c1adcb2a73f4894e1d814c145005bee0c800fa55bd0722efe0; retrieved 2026-09-15T23:29:55.581Z.