FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA113 · Beech A36

19 Jan 2023 · North Castle, NY, United States

Beech A36 · Accident: loss of engine power (total) en route

From John F. Kennedy International Airport (JFK) to Cuyahoga County Airport (CGF)

Report a problem

Event

NTSB case
ERA23FA113
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
2 · 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
Instrument Meteorological Cond

Beech A36

Aircraft type
Beechcraft 36
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
N19MT
Operator
Unknown
Onboard fatalities
Unknown
Route
From John F. Kennedy International Airport (JFK), New York, NYTo Cuyahoga County Airport (CGF), Cleveland, OH
Aircraft age
About 47 years (built 1976)
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
Loss of engine power (total)
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
  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

About 18 minutes after takeoff, while on an instrument flight rules (IFR) flight, the pilot requested a lower altitude, advising the controller that the airplane’s climb performance was degraded. As the flight continued the pilot recognized a “dead cylinder” and requested a heading to a nearby airport. The controller vectored the flight to the airport, but the pilot delayed turning onto the vectored heading for over 2 minutes. When the flight was about 6 nautical miles from the airport the pilot declared an emergency and advised the controller that the oil pressure was dropping. After turning onto the vectored heading, the airplane began a right turn that was not directed by the controller or announced by the pilot. The controller informed the pilot to level the wings and maintain 5,000 ft msl. The change in the airplane’s heading resulted in the controller providing a new vector, which increased the distance and flight time to the intended runway. Recorded data showed the engine then lost all power. The airplane continued to descend and subsequently collided with trees and the ground less than 1 mile from the intended runway threshold. According to recorded data, shortly after takeoff, when the flight was about 1 nautical mile from the departure end of the runway, the No. 4 cylinder head temperature (CHT) value exceeded the highest allowed value. The flight continued while the No. 4 CHT continued to increase. The CHT for that cylinder then began to decrease, consistent with non-firing of the fuel air mixture, and the flight continued. Postaccident examination of the engine revealed damage to the top and sides of the No. 4 piston that were likely the result of pre-ignition/detonation that pressurized the crankcase, pushing oil out of the breather assembly and depleting the oil supply. This ultimately resulted in oil exhaustion and subsequent catastrophic internal engine failure. Both spark plugs of the No. 4 cylinder had extensive deposits and one had a separated section of core nose insulator while the other only had a cracked core nose insulator, though it could not be determined from the available evidence if those conditions existed before or were the result of pre-ignition/detonation. Causes for detonation include improper ignition timing, high inlet air temperature, engine overheating, carbon build-up or oil in the combustion chamber, an issue with the fuel octane, or a lean fuel-to-air mixture. Although the magneto-to-engine timing could not be determined postaccident, there were no postaccident anomalies noted with either the magneto or the ignition harness. High inlet air temperature, engine overheating, or carbon build-up/oil in the combustion chamber were not likely or not observed. There was no report of any fuel-related issue from the facility that last fueled the accident airplane. While the position of the mixture control during the flight and the pilot’s leaning procedures were unknown, it is unlikely that the pilot would have leaned the fuel-to-air ratio to CHT exceedance as that would have been contrary to the published limitations and takeoff procedures.

Probable cause

The pre-ignition/detonation damage to the No. 4 piston for reasons that could not be determined, which allowed the crankcase to become pressurized and resulted in oil exhaustion and subsequent catastrophic internal engine failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA113
Event ID
20230120106608
Case number
ERA23FA113
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: 7562b9037e09b563b2e77f0fa4ca785fa4aeef0e46950a7aeb4d0dfd70d6c7a8; retrieved 2026-09-15T07:56:19.592Z.