FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14FA094 · Beech B36TC

1 Dec 2013 · Yellow Pine, ID, United States

Beech B36TC · Accident: fuel related en route

From Baker City, OR to Butte, MT

Report a problem

Event

NTSB case
WPR14FA094
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
5 · 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 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
N36ML
Operator
Unknown
Onboard fatalities
Unknown
Route
From Baker City, ORTo Butte, MT
Aircraft age
About 30 years (built 1983)
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
Fuel related
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The instrument-rated pilot was on a 234-nm instrument flight rules (IFR) cross-country flight over mountainous terrain; instrument meteorological conditions prevailed at the time. During the flight, the pilot notified a controller at the Air Route Traffic Control Center (ARTCC) that the airplane was picking up too much ice and requested to divert to an airport located about 96 miles ahead of his position and to descend to 11,000 feet mean sea level (msl). The controller informed the pilot that he could descend to 12,000 feet msl for terrain clearance. Over the following few minutes, the ARTCC controller notified the pilot several times that he had to maintain an altitude of 12,000 feet or above due to terrain clearance, all of which the pilot acknowledged. Following a low-altitude alert issued by the controller, the pilot stated his altitude was 11,500 feet. Subsequently, the pilot advised the controller that he was having engine problems and needed to go to an airport immediately.

When the controller asked the pilot to verify his altitude, the pilot responded that he was at 10,000 feet. The controller then asked the pilot if he was able to climb, and the pilot responded "negative." The controller advised the pilot of an airport that was 24 miles behind his position and asked if he wanted to divert. The pilot responded affirmatively and asked for guidance to the airport. About 1 minute later, the pilot advised the controller that the airplane had "just lost its engine." The controller advised the pilot that the airport was at the pilot's six o'clock position and suggested a heading of 253 degrees, adding that another airport was right below their position. There were no further communications with the accident airplane.

Wreckage and impact signatures were found consistent with a wings-level, slightly nose-low descent into trees and terrain. Postaccident examination of the airframe and engine revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation.

Airmen's Meteorological Information (AIRMETs) for IFR and mountain obscuration conditions, low-level wind shear and turbulence, and moderate icing were issued for the flight track area and timeframe. In additional to the AIRMETs, multiple pilot reports included reports of light rime-type icing between 8,000 feet and 13,000 feet throughout the region and National Weather Service data was consistent with the pilot reports and AIRMET that were current at the time. The investigation was unable to determine whether the pilot obtained weather information regarding his planned flight. It is likely that the loss of engine power was due to a combination of structural and induction icing during the continued flight in icing conditions in an airplane that was not certified for flight in icing conditions.

Probable cause

The pilot’s continued flight into known light-to-moderate icing conditions over mountainous terrain. Contributing to the accident was the loss of engine power due to induction icing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14FA094
Event ID
20131216X13812
Case number
WPR14FA094
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. 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: b5b01cfe2278b78eaa234fdb68dfb2cb94df11ba98952db354b980957e51427d; retrieved 2026-09-14T16:08:48.095Z.