FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10FA029 · Beech A36TC

27 Oct 2009 · Kalamazoo, MI, United States

Beech A36TC · Accident: loss of engine power (total) during takeoff

From Kalamazoo/Battle Creek International Airport (AZO) to Muskoka Airport (CYQA)

Report a problem

Event

NTSB case
CEN10FA029
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
1 · 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 A36TC

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
C-FFIH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kalamazoo/Battle Creek International Airport (AZO), Kalamazoo, MITo Muskoka Airport (CYQA), Muskoka, ON
Aircraft age
Not recorded
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
Takeoff
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
Destroyed

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

Witnesses and global positioning system data indicated that after takeoff the airplane tracked the runway centerline and climbed approximately 150 feet above ground level before turning to the right and descending. The airplane subsequently impacted the ground, a fence, and a pole about 1,400 feet from the departure end of the runway. A postimpact fire ensued. After acknowledging the takeoff clearance, no further communications were received from the accident airplane. Examination of the airplane’s structure, flight controls, engine controls, and fuel system did not reveal any anomalies consistent with a preimpact failure. The engine manufacturer had issued a Mandatory Service Bulletin (MSB) that was applicable to the accident airplane’s engine. The airplane’s engine was disassembled in order to replace components damaged during the impact sequence. During the disassembly the valve lifters that were the subject of the MSB were examined and found to have pitting. However, the engine was reassembled with the original valve lifters for a functional test run and during the test run the engine produced full rated power and no anomalies were noted. Data retrieved from an engine monitoring system installed on the accident airplane recorded a significant reduction in engine power during the accident takeoff. The monitoring system did not record throttle, mixture, or propeller control positions and the data was consistent with normal power reductions recorded during the landing phase of previous flights. No mechanical reason for the loss of engine power was found.

Probable cause

The loss of engine power for an undetermined reason.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10FA029
Event ID
20091027X05010
Case number
CEN10FA029
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. 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: 0f2e50a5dab277efcc9fe47fdada0e500538d5200d2be1edcc385afd95f20e04; retrieved 2026-09-13T20:32:30.198Z.