CEN16FA037 · Cessna 182Q
Cessna 182Q · Accident: loss of engine power (partial) en route
From Oakland County International Airport (PTK) to Charles B. Wheeler Downtown Airport (MKC)
Event
- NTSB case
- CEN16FA037
- 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
Cessna 182Q
- Aircraft type
- Cessna 182
- 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
- N96381
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oakland County International Airport (PTK), Pontiac, MITo Charles B. Wheeler Downtown Airport (MKC), Kansas City, MO
- Aircraft age
- About 37 years (built 1978)
- 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 (partial)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As the airplane neared the destination airport in dark night visual meteorological conditions at the conclusion of a cross-country flight, the private pilot reported a partial loss of engine power. The air traffic controller provided the pilot with a vector and information for the nearest airport, which, according to his display, was equipped with a lighted, grass runway. Although the airport was equipped with a rotating beacon and runway lighting, these lights could not be pilot-operated and required manual activation by the airport owner. This information was not available to the controller. In attempting to assist the pilot in restoring engine power, the pilot-rated controller suggested that the pilot turn off the carburetor heat. Eventually, radar contact with the airplane was lost, and the controller continued to provide vectors to the pilot while also attempting to obtain more information about the airport, including a common traffic advisory frequency to activate the lighting system. Radio contact was lost with the airplane about 7 minutes after the loss of radar contact.
The airplane impacted trees and terrain about 1 nautical mile from the diversionary airport. All of the engine's spark plugs displayed carbon fouling, consistent with an overly rich fuel-air mixture. No other anomalies were detected with the airframe or engine that would have precluded normal operation. Although the airplane was operating in an area conducive to the formation of carburetor icing at glide power, it could not be determined if the engine experienced carburetor icing at the time the pilot reported that she had engine problems because she had the carburetor heat on and was likely operating at cruise power. Additionally, the effect of the controller's suggestion to turn off the carburetor heat could not be determined.
Probable cause
The airplane's impact with trees and terrain during an off-airport forced landing in dark night conditions following a partial loss of engine power. The reason for the partial loss of engine power could not be determined because postaccident examination did not reveal any mechanical anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA037
- Event ID
- 20151111X02115
- Case number
- CEN16FA037
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-11-11.
- API snapshot SHA-256: d675bfcd62e3a0c1af9f51afaf7497a1ef803c452ab36964e0f313ef5d2ceae3; retrieved 2026-09-14T21:34:05.740Z.