CHI04GA130 · Cessna T206H
Cessna T206H · Accident: loss of engine power en route
From Chicago Midway International Airport (MDW) to Spirit of St Louis Airport (SUS)
Narrative check · The NTSB narrative appears to contradict this record's operation. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI04GA130
- 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
- Government Narrative disagrees
- 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 T206H
- Aircraft type
- Cessna 206
- 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
- N9548D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chicago Midway International Airport (MDW), Chicago, ILTo Spirit of St Louis Airport (SUS), St. Louis, MO
- 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
- Public Aircraft
- 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
- Loss of engine power
- 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
- Destroyed
Cause areas
- Exhaust system, turbocharger › Seized
- Pilot in command › Altitude/clearance, not obtained/maintained
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, encountered
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 1999 Cessna T206H was operated as a public aircraft when the pilot reported a loss of engine power during cruise flight about 1,150 feet above ground level. Spectrum analysis of air traffic control transmissions indicate that a propeller speed of 1,669 revolutions per minute was present following the loss of engine power. Visual meteorological conditions prevailed with recorded surface winds from the northeast. Witnesses reported that they heard several attempted engine restarts while the airplane was being positioned for a forced landing on a 500-foot long fallow agricultural field north of a house. A witness reported that black smoke would emanate from the airplane during each start attempt. The airplane's wing and horizontal stabilizer contacted trees near the house resulting in a steep descent into the garage adjacent to the house. A post crash fire/explosion then ensued. The Airframe & Powerplant Mechanics Handbook states that a mixture "too rich" is indicated by black smoke. Examination of the airplane systems and related components revealed that the turbocharger could not be rotated and a hydraulic press was utilized to effect the removal of the turbocharger turbine wheel. The engine crankcase halves exhibited fretting, and the nut of one crankcase thru-bolt was not in place. Maintenance records indicate that the crankshaft was replaced in response to airworthiness directives and service bulletins. No other anomalies that would have precluded normal operation were found. In 1994, the National Transportation Safety Board issued recommendation A-94-081 relating to emergency procedures for turbocharger failures to be included in airplane pilot operating handbooks (POHs) and airplane flight manuals. The Cessna T206H POH does not list emergency procedures for turbocharger failures. The Cessna T206H POH states, under emergency procedures, to advance the mixture control to the rich position if restart does not occur. The manufacturer's airplane pilot safety supplement, which was reissued in 1998 to incorporate turbocharger failures, states that "If a turbocharger failure results in a loss of power, it may be further complicated by an overly rich mixture." A review of the emergency exit procedures in Cessna 206 models shows that with the flaps lowered, the forward portion of the cargo door can only be opened approximately 4 inches to allow the aft portion of the cargo door to be opened during emergency egress. The distance between the cabin roof and seat back was measured to be approximately 11 inches.
Probable cause
The seized turbocharger, the altitude/clearance not maintained/obtained during approach to a forced landing on an agricultural field, and the unsuitable landing area encountered by the pilot. Contributing factors were the inadequate emergency procedures by the manufacturer, the trees, and the residential area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04GA130
- Event ID
- 20040608X00756
- Case number
- CHI04GA130
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: b22e57b6c834d691aa304d3058478e434da5b134ba6fa8484c27c03d5010c761; retrieved 2026-09-20T18:28:06.821Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: operation. The narrative states "The 1999 Cessna T206H was operated as a public aircraft"; the flight was a public aircraft operation, not Part 91 general aviation.