CEN09CA305 · Flight Design Gmbh CT2K
Flight Design Gmbh CT2K · Accident: abnormal runway contact during landing
From Meeker County Memorial Hospital Heliport (MN65) to Mitchell Municipal Airport (MHE)
Event
- NTSB case
- CEN09CA305
- 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
Flight Design Gmbh CT2K
- Aircraft type
- Flight Design CT2
- 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
- N433CT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Meeker County Memorial Hospital Heliport (MN65), Maple Plain, MNTo Mitchell Municipal Airport (MHE), Mitchell, SD
- 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that as he approached the destination airport he listened to the automated weather conditions. The reported conditions included winds from 290 degrees at 25 knots gusting to 35 knots. The pilot stated that he flew an extended downwind to Runway 30 in order to ensure runway alignment. On final approach, he increased his speed and used less flap extension to allow for the gusting wind conditions. He stated that when the airplane was about to touch down, a gust of wind raised the airplane into the air and then the airplane dropped abruptly to the runway. When the airplane impacted the runway, the nose landing gear and right main landing gear collapsed. The impact resulted in substantial damage to the firewall. The pilot reported no preaccident malfunctions of the airplane.
Probable cause
The pilot's inadequate compensation for the gusting winds during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA305
- Event ID
- 20090519X93305
- Case number
- CEN09CA305
- 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: ccdbe6ff2472f8d14490efc7c9dfe83dc2267b15baed4e2769ffa61ec7affaab; retrieved 2026-09-15T11:06:41.896Z.