CEN11CA640 · Cessna T210M
Cessna T210M · Accident: system/component malfunction/failure (non-power) during landing
From St Louis Downtown Airport (CPS) to St Louis Downtown Airport (CPS)
Event
- NTSB case
- CEN11CA640
- 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 T210M
- 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
- N44HR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St Louis Downtown Airport (CPS), Cahokia, ILTo St Louis Downtown Airport (CPS), Cahokia, IL
- 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
- 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
- System/component malfunction/failure (non-power)
- 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 systems
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 executed a wheel-up landing after normal and emergency extension procedures failed to properly lower the airplane's landing gear. The airplane sustained damage to the propeller, lower fuselage skins, and fuselage bulkheads. Postaccident retraction tests revealed that the landing gear extended and retracted abnormally. Examination of the landing gear system revealed a deformed spring on the uplock sequencing actuator. The spring was replaced and subsequent retraction tests were normal. Review of the hydraulic system for the airplane revealed that a failure of the uplock sequencing actuator could result in hydraulic pressure being directed to both sides of the main landing gear actuators, causing the landing gear to not fully extend. No other preexisting anomalies were found.
Probable cause
A failure of a spring in the main landing gear actuation system that prevented the landing gear from extending.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA640
- Event ID
- 20110913X63156
- Case number
- CEN11CA640
- 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: 490ff7128d6746588e01c2a19b03a42b084a04375af271d845596850b07c1998; retrieved 2026-09-15T16:44:05.006Z.