CHI01LA101 · Cessna P206
Sky Tours Cessna P206 · Accident: partial loss of engine power (mechanical failure) en route
From Cook Airfield (K50) to an unrecorded destination
Event
- NTSB case
- CHI01LA101
- 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
- 0 · 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 P206
- 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
- N2507X
- Operator
- Sky Tours
- Onboard fatalities
- Unknown
- Route
- From Cook Airfield (K50), Derby, KSTo not recorded
- 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 · descent
- 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 (mechanical failure)
- 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 › In-flight planning/decision, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage on impact with trees and terrain during a forced landing to a field following an in-flight loss of engine power. Skydivers had been dropped prior to the loss of engine power and the pilot reported no injuries. The pilot stated, "I climbed to 11000 [feet.] Was not getting usual climb rate[.] Before decent found I could not close cowl flaps. Decended to 6000 [feet.] Noticed eratic raise on manifold gage[.] Decided to shut down engine to stop further any possible damage. Flew down to pattern altitude where a plane flew in front of me and carried on across airport. I then carried on my landing, was about to turn base when I noticed the plane had turned 120 [degrees] and was flying toward me[.] I finally got hold of him on the radio and told him I had an engine out. He acknolaged and headed north out of the area. I then realized I was not able to get to runway because of high trees[.] Decided to turn into cleared area but hit tree with right wing[.]" Under mechanical malfunction failure, the pilot stated, "Air intake hose blown off after backfire[.]"
Probable cause
The misjudged in-flight planning the pilot had for the forced landing. Factors were the induction air ducting separation, the pilot not coordinating his emergency procedure with airfield traffic, and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA101
- Event ID
- 20010316X00591
- Case number
- CHI01LA101
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-03-10.
- API snapshot SHA-256: 1b3c8f9834448b0709f0896b7d462256bc5e53f320e933fa12ce9f02193c9f9e; retrieved 2026-09-22T12:06:20.074Z.