FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA059 · Cessna T210 M

6 Jan 2019 · Flint, MI, United States

Cessna T210 M · Accident: system/component malfunction/failure (non-power) on approach

From Clare Municipal Airport (48D) to Bishop International Airport (FNT)

Report a problem

Event

NTSB case
CEN19LA059
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 T210 M

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
N1237M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Clare Municipal Airport (48D), Clare, MITo Bishop International Airport (FNT), Flint, MI
Aircraft age
About 42 years (built 1977)
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot reported that, after takeoff for the cross-country, personal flight, he attempted to retract the landing gear and noticed that the gear motor continued to operate longer than normal and that the sound had become abnormal toward the end of the retraction sequence. The pilot subsequently saw that the right main landing gear (MLG) had not fully retracted and was hanging about 45° rearward. He could not see the left MLG. The pilot attempted to address the gear issue for more than 20 minutes by completing the emergency procedures checklist; however, although the nose landing gear (NLG) had extended, the MLG did not respond, so the pilot continued to the destination airport. Before landing, the pilot again attempted to extend the landing gear. During a flyby, an air traffic controller confirmed that both MLG were not extended. The pilot subsequently conducted an emergency landing with the NLG extended and both MLG partially extended. Upon landing, the airplane spun about 180° and then came to rest on the runway, sustaining substantial damage to the right horizontal stabilizer and elevator.

During postaccident examination of the airplane, the NLG well was found partially covered in red hydraulic fluid, no hydraulic fluid was found on the reservoir dipstick, and an NLG actuator hydraulic hose was found damaged. During a functional test of the hydraulic system, the emergency gear extension handle was actuated in an attempt to extend the MLG; however, after 10 to 12 pumps, hydraulic fluid sprayed from the damaged hose; the system could not build pressure, and the MLG would not extend. The damaged hose was replaced, the emergency gear extension handle was actuated, and the MLG extended and locked normally.

According to a service bulletin issued 17 years before the accident and based on the maintenance criteria for the hydraulic hose part number, the hose should have been replaced with an updated hose. However, about 13 years before the accident, the hydraulic hose was replaced with the original part number rather than with the updated part number. The hydraulic hose failed during the accident flight when the pilot attempted to retract the landing gear after takeoff. It is likely that, during annual inspections subsequent to the hose replacement, the hose was treated as an "on-condition" part since it had not been replaced with the new hose.

It is likely that most of the hydraulic fluid was pumped out of the damaged hose during the pilot's troubleshooting attempts, which led to a loss of hydraulic system pressure and prevented the MLG from fully extending or retracting and resulted in a gear-up landing.

Probable cause

The failure of the nose landing gear actuator hydraulic hose, which resulted in the loss of hydraulic fluid and hydraulic system pressure and a subsequent gear-up landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA059
Event ID
20190107X33741
Case number
CEN19LA059
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. 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: febf21ec5b1e1bd0f2151a7301971219e18742fadcdaa2fa701918843611dd17; retrieved 2026-09-16T08:31:56.505Z.