CEN09CA300 · Diamond DA20 C1
Kansas City Aviation Center Diamond DA20 C1 · Accident: abnormal runway contact during landing
From Johnson County Executive Airport (KOJC) to Johnson County Executive Airport (KOJC)
Event
- NTSB case
- CEN09CA300
- 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
Diamond DA20 C1
- Aircraft type
- Diamond DA20
- 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
- N926AF
- Operator
- Kansas City Aviation Center
- Onboard fatalities
- Unknown
- Route
- From Johnson County Executive Airport (KOJC), Olathe, KSTo Johnson County Executive Airport (KOJC), Olathe, KS
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a planned touch-and-go landing, the student pilot flared too high and the airplane landed hard, bounced, and the propeller struck the runway. The student pilot executed a go-around. During the climbout, at approximately 250 feet above ground level, the engine lost power. The student pilot executed a straight-ahead forced landing, during which the airplane's right wing and horizontal stabilizer were separated. The airplane subsequently nosed over, coming to rest inverted in a tree line. The student pilot, who was trapped in the inverted airplane, was extracted 30 minutes later by emergency response crews; he sustained minor injuries. A serviceable propeller was later installed and the airplane's engine was successfully tested for over 20 minutes, including several minutes at full power.
Probable cause
The student pilot's improper landing flare and recovery from a bounced landing, as well as his improper decision to continue the takeoff after striking the propeller on the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA300
- Event ID
- 20090518X93855
- Case number
- CEN09CA300
- 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: 7f8c97264fb3f7f78c1dca0b5e4d3a17b2f800643692225dcdd09bcc6a84c92e; retrieved 2026-09-15T11:05:32.968Z.