CEN14CA153 · Diamond Aircraft IND Inc DA 20
Premier Fligth Academy Diamond Aircraft IND Inc DA 20 · Accident: abnormal runway contact during landing
From Burke Lakefront Airport (BKL) to Burke Lakefront Airport (BKL)
Narrative check · The NTSB narrative appears to contradict this record's operator. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN14CA153
- 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 Aircraft IND Inc DA 20
- Aircraft type
- Diamond DA-20
- 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
- N108WA
- Operator
- Premier Fligth Academy Narrative disagrees
- Onboard fatalities
- Unknown
- Route
- From Burke Lakefront Airport (BKL), Cleveland, OHTo Burke Lakefront Airport (BKL), Cleveland, OH
- Aircraft age
- About 14 years (built 2000)
- 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
- 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 solo student pilot reported that he was attempting to make a full stop landing. He attempted to land twice before, but bounced both landing attempts, and ultimately executed go-arounds each time. He reported that during the third attempted landing, he bounced the landing and attempted another go-around, but "could not recover." The airplane veered off the left side of the runway and impacted a distance marker, a stop sign, and a pile of rocks, which resulted in substantial damage to the wings.
Probable cause
The pilot's improper flare and recovery from a bounced landing, which resulted in a loss of control and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA153
- Event ID
- 20140310X43403
- Case number
- CEN14CA153
- 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: 61dad3ed405978e0e1faac179e5b352d188371abc64e11c6c8130a7fb3a57b65; retrieved 2026-09-15T23:23:03.353Z.