CHI05LA225 · Cessna 210
Cessna 210 · Accident: airframe, component or system failure on approach
From Richard I Bong Memorial Airport (SUW) to Rapid City Regional Airport (RAP)
Event
- NTSB case
- CHI05LA225
- 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 210
- 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
- N9408T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richard I Bong Memorial Airport (SUW), Superior, WITo Rapid City Regional Airport (RAP), Rapid City, SD
- 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
- Approach
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Flt control syst, wing flap control › Inoperative
- Hydraulic system, line › Fatigue
- Pilot in command › Gear extension, not possible
- Unknown › Maintenance, rebuild/remanufacture, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted the landing runway in a gear-up and no flap configuration following a loss of hydraulic fluid. The pilot stated that he was unable to lower the flaps for the landing. The airplane slid off the runway, impacted a culvert, and came to rest on a grass area adjacent to the runway. The landing gear and flap system were operated by a common hydraulic system. The pilot was unable to extend the flaps after not being able to extend the landing gear. Inspection of the airplane revealed a fractured hydraulic tube in the nose section of the airplane. The hydraulic tube fracture exhibited a fatigue fracture that was located at one of several circumferential impressions on the tube. There was no record of repair of the hydraulic tube assembly in the airplane maintenance logbooks.
Probable cause
The landing gear extension not possible and inoperative flap system due to fatigue failure of a hydraulic system tube during approach. An additional cause was the improper rebuild/remanufacture of the hydraulic tube. Contributing factors were the dependency of the landing gear and flap systems on the common hydraulic system allowing a single-point failure to affect both systems.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05LA225
- Event ID
- 20050906X01382
- Case number
- CHI05LA225
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-08-10.
- API snapshot SHA-256: fbe8977bc48f81f1beceb8c44a62640d3296164735d47d95310a04b6c965269c; retrieved 2026-09-22T05:30:23.453Z.