# Incident 20060516006659I: Beech 200BEECH, Butte, MT, May 16, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 16, 2006, 13:48 local time
- Place: Butte, MT
- Airport: Bert Mooney
- Phase of flight: Normal Cruise
- Operating rules: Air taxi and commuter (Part 135)
- Operator: DDNA
- Location: 45.9548° N, 112.4975° W: Placed by OpenAirDocs at BERT MOONEY (BTM), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.9548&lon=-112.4975&mi=10
- Aircraft: N616GB, a cancelled registration (https://openairdocs.org/deregistered/N616GB-2019-05-14) (OpenAirDocs)
- Registry model: Beech 200 (registry code 1152920, https://openairdocs.org/model/beech-200) (OpenAirDocs)
- Reported make and model: BEECH 200BEECH
- Reported engine: PWA PT6A41
- People aboard: 7
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060516006659I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON MAY 16, 2006, WHILE ON A 14 CFR PART 135 ON-DEMAND FLIGHT LEAVING SEATTLE, WASHINGTON, AT APPROXIMATELY 1 HOUR AND 35 MINUTES INTO THE FLIGHT, ENROUTE TO SIOUX FALLS, SOUTH DAKOTA, WITH AN INTENDED FUEL STOP AT BOZEMAN, MONTANA, THE PILOT NOTICED A YAW IN THE AIRCRAFT. HE DID A QUICK SCAN OF THE INSTRUMENTS, AND NOTICED THAT HE HAD A DROP IN TORQUE AND AN INCREASE IN THE INLET TURBINE TEMPERATURE ON THE LEFT ENGINE. THE PILOT PROCEEDED WITH EMERGENCY PROCEDURES, AND FEATHERED THE LEFT PROP. THE PILOT THEN NOTIFIED AIR TRAFFIC CONTROL AND LANDED AT BUTTE, MONTANA, WITHOUT INCIDENT.

## Other reports on N616GB (1)

Matched to the same aircraft by N-number and date.

- [Incident 20001109022029I](https://openairdocs.org/incident/20001109022029I), Nov 9, 2000: Beech 200BEECH (N616GB), Denver, CO, Minor damage. (-23) While taxiing pilot attempted to copy IFR clearance, lost directional control and taxied off taxiway into taxiway direction signs, and came to rest in…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.