CEN12CA011 · Cirrus Design Corp SR20
Cirrus Design Corp SR20 · Accident: abnormal runway contact during landing
From Centennial Airport (APA) to Centennial Airport (APA)
Event
- NTSB case
- CEN12CA011
- 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
Cirrus Design Corp SR20
- Aircraft type
- Cirrus SR20
- 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
- N777XG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Centennial Airport (APA), Englewood, COTo Centennial Airport (APA), Englewood, CO
- Aircraft age
- About 7 years (built 2004)
- 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
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the student pilot, the airplane was high on final approach. He said that the airplane touched down on the main landing gear and that he added back pressure on the control yoke, but the airplane bounced and became airborne again. The airplane bounced several times before exiting the runway, sliding across the grass, traveling down a hill, and coming to rest next to a fence. A postaccident examination of the airplane revealed substantial damage to both composite wings. The examination did not disclose any mechanical malfunctions that would have precluded normal operation.
Probable cause
The student pilot's improper flare, which resulted in a bounced landing from which he was unable to recover.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA011
- Event ID
- 20111011X62233
- Case number
- CEN12CA011
- 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: a02f0e80cdd47669bd876f38e80ca38ffb9ea411822545f80ee6e38326ea5f47; retrieved 2026-09-15T16:49:44.049Z.