ERA09CA091 · Kimball Enterprises Inc Pitts Model-12
Kimball Enterprises Inc Pitts Model-12 · Accident: loss of control on ground during landing
From Tampa Executive Airport (VDF) to Hobby Hill STOLport (2FD1)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA09CA091
- 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
Kimball Enterprises Inc Pitts Model-12
- Aircraft type
- Kimball Enterprises PITTS MODEL-12
- 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
- N212DK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tampa Executive Airport (VDF), Tampa, FLTo Hobby Hill STOLport (2FD1), Weirdales, 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 · 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
- Loss of control on ground
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the homebuilt airplane stated that he overflew the airport from the east and observed that the windsock was indicating a 90-degree crosswind of 15-20 knots for the airport's runway, designated 36/18. The pilot elected to land on runway 36 and entered the downwind leg of the traffic pattern. The pilot reported inputting a "significant" amount of slip to maintain centerline during final approach and flare. The airplane touched down on the right main landing gear first and then bounced off the grass strip. During the bounce, the crosswind forced the airplane toward the left, off the runway, and into a fence where the left wingtip struck a fence post. The airplane yawed, the wing hit the ground, and the airplane cart-wheeled, coming to rest inverted.
Probable cause
The pilot's inadequate compensation for the wind conditions. Contributing to the accident was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA091
- Event ID
- 20081216X20341
- Case number
- ERA09CA091
- 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, coordinates. 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: ac436a78c80516d686a8e6443ddbadda0a881640e962e0411d5e7e6302b493f6; retrieved 2026-09-15T10:36:23.652Z.