ERA24LA186 · Cessna 210 L
Cessna 210 L · Accident: system/component malfunction/failure (non-power) on approach
From Chester Catawba Regional Airport (DCM) to an unrecorded destination
Event
- NTSB case
- ERA24LA186
- 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
- 0
- 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 L
- 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
- N777NT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chester Catawba Regional Airport (DCM), Chester, SCTo not recorded
- Aircraft age
- About 49 years (built 1975)
- 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
- 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
During approach, the pilot attempted to extend the landing gear, but it remained retracted. The pilot was unable to extend the landing gear via normal or emergency procedures, and subsequently observed that all the hydraulic fluid had leaked out of the reservoir. The pilot diverted to a larger airport and performed a gear-up landing. During the landing, the airplane skidded right, and came to rest upright partially off the right side of the runway. Examination of the wreckage revealed substantial damage to the right horizontal stabilizer and right elevator. The examination also revealed that a hydraulic hose (possibly the original hose) had deteriorated and separated from its fitting, allowing all the hydraulic fluid to leak out of the system.
Probable cause
Failure of a landing gear extension system hydraulic hose, which resulted in a landing with the landing gear retracted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA186
- Event ID
- 20240422194120
- Case number
- ERA24LA186
- 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, cause areas. 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: d6ba7cba1eab082de0e22c467202e92882914b589dd5941b11e34402f4d6e1a3; retrieved 2026-09-16T18:41:05.673Z.