CHI06FA152 · Beech B36TC
Beech B36TC · Accident: partial loss of engine power (non-mechanical) en route
From Kalamazoo/Battle Creek International Airport (AZO) to Willow Run Airport (YIP)
Event
- NTSB case
- CHI06FA152
- 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
- Visual Meteorological Cond
Beech B36TC
- 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
- N65EL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kalamazoo/Battle Creek International Airport (AZO), Kalamazoo, MITo Willow Run Airport (YIP), Ypsilanti, MI
- 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
- En route · cruise
- First occurrenceThe 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
- Partial loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane struck trees and terrain during an emergency landing following a reported loss of engine power. The airplane was being flown on its first flight after an annual inspection. A cylinder was replaced, a turbocharger leak was fixed, and the right fuel bladder was removed, repaired, and reinstalled during the annual inspection. The fuel from the removed fuel bladder was recovered, stored, and was returned to the bladder when it was reinstalled. The airplane was also serviced with about 67 gallons of 100 low lead aviation gasoline. The fuel in the airplane's fuel tanks were reported to have been checked by observing samples collected from the fuel sumps prior to the flight. The airplane battery was low and external power was used to start the engine for the flight. A replay of radar data showed the airplane was at 5,000 feet above mean sea level (MSL) and was traveling eastward at about 170 knots groundspeed when it checked on with approach. About 1907, the radar data replay showed the airplane descending to 4,800 feet and its groundspeed slowing to 160 knots. The air traffic controller issued the flight a descent clearance to 3,000 feet MSL. The pilot responded back that he had an emergency, had lost engine power, had switched fuel tanks, and needed the closest airfield. The pilot was given a heading of 360 degrees to an airfield. While en route to the airfield, the pilot was asked if his engine was completely out and if he was gliding into the airport. The pilot reported that was correct. About 1910, the air traffic controller pointed out another closer airport. No further response was received from the airplane. The last recorded radar data was at 1910. The radar showed the airplane was about 2 miles from the closer airport at 2,000 feet MSL and traveling northbound at about 80 knots groundspeed. About 1918, the police department received notification of a downed aircraft. The cabin area of the fuselage, left and right inboard fuel tank sections, and upper forward section of the empennage were destroyed by a post impact fire. An on-scene investigation and follow up examinations revealed no-pre-impact anomalies. The airplane's track was reviewed in reference to satellite images of the area. The airplane had over flown open fields prior to impact.
Probable cause
The non-mechanical loss of engine power for undetermined reasons during cruise flight and the unsuitable terrain the pilot selected for the forced landing. A factor was the tree that was impacted during the forced landing. An additional factor was the inadequate planned approach during the forced landing when the pilot over flew open fields on the way to the intended airfield.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06FA152
- Event ID
- 20060614X00735
- Case number
- CHI06FA152
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: f8a15b7a9a0e18258aea90efcb7055b5f91d61b86e5def2e7d75bbbdb41df29a; retrieved 2026-09-20T17:18:32.471Z.