# Incident 20111028025459I: Mitsubishi MU-2B-60, Richmond, VA, October 28, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 28, 2011, 01:32 local time
- Place: Richmond, VA
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: Air taxi and commuter (Part 135)
- Operator: BKAA
- Location: 37.5538° N, 77.4603° W: Placed by OpenAirDocs: center of Richmond, VA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.5538&lon=-77.4603&mi=10
- Aircraft: N8083A, registered now (https://openairdocs.org/aircraft/N8083A) (OpenAirDocs)
- Registry model: Mitsubishi MU-2B-60 (registry code 5780460, https://openairdocs.org/model/mitsubishi-mu-2b-60) (OpenAirDocs)
- Registry engine: AiResearch TPE331 series (registry code 01514, https://openairdocs.org/engine/airesearch-tpe331-series) (OpenAirDocs)
- Reported make and model: MITSUBISHI MU-2B-60
- Reported engine: AIRESEARCH TPE331
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111028025459I

## Narrative

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

AIRCRAFT FLYING IN ROUTE AT FL210 AT A DISTANCE OF ABOUT 35 NAUTICAL MILES WEST OF RICHMOND INTERNATIONAL AIRPORT. THE LEFT ENGINE FAILED. PILOT WAS IN RADAR CONTACT AND COMMUNICATIONS WITH WASHINGTON CENTER AND PROCEEDED TO DECLARE AN EMERGENCY AND ASKED FOR THE NEAREST FIELD.  FOLLOWING SUGGESTION BY ATC TO GO DIRECT RICHMOND, PILOT INITIATED DESCENT AS SOON AFTER SECURING THE LEFT ENGINE AND COMPLETING ALL THE PERTINENT EMERGENCY CHECKLISTS.  PERFORMED AN UNEVENTFUL LANDING TO A FULL STOP. INSPECTED THE AIRCRAFT VISUALLY AND NO STRUCTURAL OR ABNORMALITIES WHERE OBSERVED.MAINTENANCE PERSONNEL WERE DISPATCHED AND DETERMINED THE ENGINE FAILURE WAS A RESULT OF A FAILED SUN GEAR.

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.