CEN12CA564 · Cessna T210N
Cessna T210N · Accident: runway excursion during landing
From Boulder Municipal Airport (KBDU) to Boulder Municipal Airport (KBDU)
Event
- NTSB case
- CEN12CA564
- 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
Cessna T210N
- Aircraft type
- Cessna 210
- 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
- N85S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boulder Municipal Airport (KBDU), Boulder, COTo Boulder Municipal Airport (KBDU), Boulder, CO
- 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 · landing roll
- 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
- Runway excursion
- 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
- 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 pilot stated that he overshot the final approach to the runway and had to maneuver the airplane back to the final approach course. Because the airplane was high on the approach, he extended 30 degrees of flaps and descended at an airspeed of between 80 and 85 knots. The pilot stated that he thought that the approach was not stabilized; however, he continued the approach and landed. The pilot further stated that, during the landing roll, he thought that the airplane was being pushed by a strong tailwind and that he was unable to stop the airplane before the end of the runway. The airplane departed the runway, went down an embankment, and came to rest inverted, resulting in substantial damage to the airframe and both wings. The pilot stated that there were no preaccident mechanical malfunctions or anomalies that would have precluded normal operation.
Probable cause
The pilot’s decision to continue the unstable approach, which resulted in a loss of control during landing and a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA564
- Event ID
- 20120822X51704
- Case number
- CEN12CA564
- 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: 323b1c7b8ad411da65ce30a68f05839492f0f2daa4a08cc0de4a681f907d7b53; retrieved 2026-09-15T19:28:20.218Z.