CEN12LA187 · Brice RON GLASTAR SPORTSMAN 2+
Brice RON GLASTAR SPORTSMAN 2+ · Accident: hard landing
From Kimberling Airport (MO64) to Kimberling Airport (MO64)
Event
- NTSB case
- CEN12LA187
- 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
- 1 · 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
Brice RON GLASTAR SPORTSMAN 2+
- Aircraft type
- Brice Ron GLASTAR SPORTSMAN 2
- 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
- N627RM
- Operator
- Signs of Life
- Onboard fatalities
- Unknown
- Route
- From Kimberling Airport (MO64), Kimberling, MOTo Kimberling Airport (MO64), Kimberling, MO
- 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
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The float-equipped airplane was observed flying low over the lake before it made an attempt to land on the water. Witnesses said the engine was operating normally but that the airplane never leveled off before it touched down. The airplane impacted the water, cart-wheeled, and came to rest inverted. Examination of the airplane revealed that the landing gear was in the fully retracted position, consistent with a water landing configuration. Examination of the airplane revealed there were no mechanical deficiencies that would have precluded normal operation of the airplane.
Probable cause
The pilot’s inadequate flare, which resulted in the airplane impacting into the water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA187
- Event ID
- 20120314X33326
- Case number
- CEN12LA187
- 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: e85200449be499442be4043746894d7711a58debca06fb34e8d50fcf067d83d4; retrieved 2026-09-13T22:14:17.621Z.