FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA053 · Cessna T210M

16 Dec 2017 · Oldenburg, IN, United States

Cessna T210M · Accident: powerplant system/component malfunction/failure en route

From Columbus Municipal Airport (BAK) to Frederick Municipal Airport (FDK)

Report a problem

Event

NTSB case
CEN18FA053
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
3 · 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 T210M

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
N761YZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Columbus Municipal Airport (BAK), Columbus, INTo Frederick Municipal Airport (FDK), Frederick, MD
Aircraft age
About 39 years (built 1978)
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 · climb to 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
Powerplant system/component malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airline transport pilot and two passengers, one of whom was pilot-rated, were conducting a cross-country flight in dark, night visual conditions. During an en route climb to the assigned cruise altitude, the airplane experienced a loss of engine power about 6,600 ft above ground level (agl). The pilot identified a diversionary airport located about 4 miles northeast of the airplane's position and subsequently established a course toward that airport. The air traffic controller immediately informed the pilot that the airport was closed. However, based on the pilot's stated intention to divert to the airport, the controller provided radar vectors to assist the pilot. The airplane subsequently overflew the airport about 3,000 ft agl. However, instead of circling the airport, the pilot continued about 1 1/2 miles north and entered a right gliding turn until the airplane impacted trees and terrain about 2 miles north of the airport.

A postaccident airframe examination did not reveal any anomalies consistent with an airframe structural failure or a malfunction of the flight control system. An engine examination revealed that the No. 4 piston had failed. Specifically, the perimeter of the No. 4 piston crown had separated, resulting in the separation of the upper compression ring and compression ring insert. Metallurgical examination determined that the piston failure was caused by the disbonding of the upper piston ring insert from the piston body. Lead deposits were present on parts of the piston body that formed an interface with the insert. The deposits were abraded in areas exposing the underlying piston material. The abraded areas where the deposits had been worn away could only have occurred if the upper piston ring insert had disbonded from the piston body before the piston failed. The disbonding of the insert was likely caused by a manufacturing anomaly; however, due to the extensive damage to the piston and the insert, it was not possible to determine with any more precision where the failure started or the nature of the defect that might have caused it.

An airplane performance study revealed that no airports other than the diversionary airport were within the power-off glide range of the airplane at the time of the loss of engine power. Thus, the location of the airplane at the time of the loss of engine power presented the pilot with limited options for a forced landing. Furthermore, the pilot's ability to discern a suitable off-airport landing area was hindered by the dark night lighting conditions. Although, an interstate highway was below the airplane, attempting to execute a forced landing on an unlighted roadway at night presented significant hazards. In contrast, approach paths to an airport are generally free of obstructions. Therefore, the pilot's decision to alter course toward the diversionary airport, even though it was closed and unlighted, was understandable. However, once the airplane was positioned over the airport, the pilot did not circle but continued to fly north into an area with more limited opportunities for a successful forced landing.

A review of the available medical information did not reveal the presence of any condition or medication that would have led to an incapacitation or impairment of the pilot. However, the pilot was likely fatigued at the time of the accident due to the length of time he had been awake, and the significant amount of flight time completed on the day of the accident. This may have narrowed the pilot's attention during the emergency. Additionally, situational stress imposed by the engine failure and the necessity to find a forced landing site in dark night conditions further reduced the pilot's ability to maintain situational awareness.

The pilot-rated passenger's medical history included conditions and medications that, while unlikely to cause any sudden incapacitation, could potentially be impairing. However, the investigation was unable to determine the extent of impairment, if any, that might have been present at the time of the accident.

Probable cause

A total loss of engine power due to the failure of the No. 4 piston, which resulted in an attempted forced landing in dark night conditions and a subsequent in-flight collision with trees and terrain. Contributing to the accident were the pilot's situational stress and fatigue, both of which degraded his performance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA053
Event ID
20171217X14131
Case number
CEN18FA053
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 2017-12-17.
  • API snapshot SHA-256: 6cfa8cde1f76545b29475c12c2dca7a23cdc1c3182e950bbac1c7a5ee1f8210d; retrieved 2026-09-15T06:27:36.162Z.