CEN22LA378 · Cessna 210B
Acp Enterprises Cessna 210B · Accident: system/component malfunction/failure (non-power) during landing
From Charles W. Baker Airport (2M8) to an unrecorded destination
Event
- NTSB case
- CEN22LA378
- 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
- Event fatalities
- Unknown
- 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 210B
- 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
- N9637X
- Operator
- Acp Enterprises
- Onboard fatalities
- Unknown
- Route
- From Charles W. Baker Airport (2M8), Millington, TNTo not recorded
- Aircraft age
- About 60 years (built 1962)
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the landing gear retracted normally on takeoff; however, when he attempted to extend the landing gear in preparation for landing, the nosewheel extended and locked into place but the main landing gear did not fully extend. The pilot completed the checklist items for “landing gear emergency operation,” but the landing gear still did not fully extend and lock into place. Unable to extend the main landing gear, the pilot elected to accomplish the landing with the nosewheel extended and the main gear out of the wheel well, but not in the down-and-locked position. The pilot shut down the engine when the landing was assured to protect the engine. After the touchdown and during deceleration, the airplane rolled slightly to the left and the left elevator and horizontal stabilizer contacted the runway, which resulted in substantial damage.
Postaccident examination of the hydraulic actuator revealed a fatigue crack that initiated along the retaining ring groove of the actuator. The crack propagated in a circumferential direction outward and once the fatigue crack grew to its terminal size, the remainder of the cross-section fractured from mixed overstress and fatigue. This led to part of the housing barrel fracturing in overstress, allowing the release of the internal pressurized hydraulic fluid.
Probable cause
A fatigue crack in the hydraulic actuator, which resulted in the loss of hydraulic fluid and the pilot’s inability to fully extend the landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA378
- Event ID
- 20220810105706
- Case number
- CEN22LA378
- 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, 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: 5fd717d39fc59f43e823092201da14a5b9df8ba7aaa3b46878fbf79ca26756e7; retrieved 2026-09-16T15:37:55.799Z.