ERA17CA013 · Mickler Larry J RV6 A
Mickler Larry J RV6 A · Accident: abnormal runway contact during landing
From Flying Harness Farms Airport (37FL) to Flying Harness Farms Airport (37FL)
Event
- NTSB case
- ERA17CA013
- 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
Mickler Larry J RV6 A
- Aircraft type
- Mickler Larry RV6
- 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
- N686RM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flying Harness Farms Airport (37FL), Bell, FLTo Flying Harness Farms Airport (37FL), Bell, FL
- Aircraft age
- About 10 years (built 2006)
- 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
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot/owner was landing at his home airport with a 60°, 10-knot crosswind that was gusting to 14 knots. The pilot stated the wind was "a little gusty" at the time and that the airplane was "right at stall speed" at touchdown. The airplane touched down on the right main landing gear (MLG) and then the left MLG before the pilot lowered the nose landing gear (NLG). He said that, when the NLG touched down, the airplane bounced into a very nose-high attitude, so he "pushed the nose over," and the propeller struck the ground, the airplane nosed over, and it then came to rest inverted. The pilot was seriously injured, and the airframe sustained substantial damage to the fuselage and vertical stabilizer. According to the pilot/owner, the performance and handling of the airplane on the day of the accident was "fine; you couldn't ask for a better airplane."
Probable cause
The pilot's inadequate compensation for gusting crosswinds, which resulted in a bounced landing and nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17CA013
- Event ID
- 20161012X61628
- Case number
- ERA17CA013
- 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: 08d6029ffea9864ae14fb0bc424de8b5bbcae5f8cc68f6633b4a229fb150fc83; retrieved 2026-09-16T04:23:25.510Z.