# Incident 20040112002199I: Beech 200BEECH, Charleston, WV, January 12, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 12, 2004, 10:02 local time
- Place: Charleston, WV
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 38.3498° N, 81.6326° W: Placed by OpenAirDocs: center of Charleston, WV, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.3498&lon=-81.6326&mi=10
- Aircraft: N5LE, a cancelled registration (https://openairdocs.org/deregistered/N5LE-2006-03-28) (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: 3
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040112002199I

## Narrative

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

(-23) ^PRIVACY DATA OMITTED^ AIRCRAFT ENROUTE FROM TAZWELL, VIRGINIA (6V3) TO FORT MEADE, MD (FME) IN CRUISE AT 19,000 FEET. PILOT NOTICED UNCOMMANDED RIGHT HAND ENGINE SETTING TO FULL POWER WITH NO THROTTLE RESPONSE. PILOT SHUT DOWN RIGHT HAND ENGINE AND LANDED UNEVENTFUL AT CHARLESTON, WEST VIRGINIA (CRW).

## Other reports on N5LE (2)

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

- [Incident 20051029033119I](https://openairdocs.org/incident/20051029033119I), Oct 29, 2005: Beech 200BEECH (N5LE), Nashville, TN, Minor damage. (-23) Aircraft N5LE departed maury co airport (mrc) on a VFR flight in VMC to Nashville, TN, landing at John Tune airport (jwn). Upon arrival at jwn a low…
- [Incident 20041110028609I](https://openairdocs.org/incident/20041110028609I), Nov 10, 2004: Beech 200BEECH (N5LE), Panama City, FL. (-23) The pilot stated that during the landing phase there was a gusty crosswind. During the flare the aircraft ballooned and a little power was added to…

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.