CEN17LA039 · Cessna P210N
Cessna P210N · Accident: system/component malfunction/failure (non-power) en route
From South Texas Regional Airport at Hondo (HDO) to Mustang Beach Airport (RAS)
Event
- NTSB case
- CEN17LA039
- 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 P210N
- 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
- N44C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Texas Regional Airport at Hondo (HDO), Hondo, TXTo Mustang Beach Airport (RAS), Port Aransas, TX
- Aircraft age
- About 37 years (built 1979)
- 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
- En route · cruise
- 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 power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, about 20 minutes into the cross-country flight, the engine suddenly experienced a partial loss of power. The pilot attempted to restore engine power but was not successful. During the subsequent forced landing to a road, the airplane struck a car, resulting in substantial damage to the fuselage and both wings. Examination of the airplane revealed that the hardware that attached the throttle linkage to the engine was not present. Given that the airplane had flown for only a few hours following recent maintenance, it is likely that maintenance personnel did not properly secure the throttle linkage hardware during that maintenance. No other anomalies were noted that would have precluded normal operations.
Probable cause
Maintenance personnel's improper installation of the throttle linkage attachment hardware, which resulted in a partial loss of engine power when the hardware separated in flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA039
- Event ID
- 20161116X04207
- Case number
- CEN17LA039
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-11-13.
- API snapshot SHA-256: 77d737a96e51e1802dd4158df97d57d471c511494d4cdc3feb8d34988df8b376; retrieved 2026-09-16T04:50:24.410Z.