# Incident 20050916025459I: Bac AVRO146RJ85A, Omaha, NE, September 16, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 16, 2005, 11:40 local time
- Place: Omaha, NE
- Airport: Eppley Airfield
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: Air carrier (Part 121)
- Operator: MALA
- Location: 41.3032° N, 95.8941° W: Placed by OpenAirDocs at EPPLEY AIRFIELD (OMA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.3032&lon=-95.8941&mi=10
- Aircraft: N513XJ, a cancelled registration (https://openairdocs.org/deregistered/N513XJ-2006-05-24) (OpenAirDocs)
- Registry model: British Aerospace AVRO 146-RJ85A (registry code 1500097, https://openairdocs.org/model/british-aerospace-avro-146-rj85a) (OpenAirDocs)
- Registry engine: Alliedsign LF507-1F (registry code 02503, https://openairdocs.org/engine/alliedsign-lf507-1f) (OpenAirDocs)
- Reported make and model: BAC AVRO146RJ85A
- Reported engine: LYC LF5071F
- People aboard: 60
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050916025459I

## Narrative

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

(-23) N513XJ OPERATING AS MESABA AIRLINES FLIGHT 3605, DEPARTED MINNEAPOLIS, MN ENROUTE TO OKLAHOMA CITY, OK. THE NUMBER FOUR ENGINE DEVELOPED A VIBRATION AT CRUISE ALTITUDE. THE CREW SHUT DOWN THE ENGINE, DECLARED AN EMERGENCY AND DIVERTED TO OMAHA, NE. COMPANY MECHANICS CHANGED THE ENGINE. THEY NOTICED THAT THE POWER TURBINE BUCKET HAD A MISSING BLADE.

## Other reports on N513XJ (1)

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

- [Incident 20001119028279I](https://openairdocs.org/incident/20001119028279I), Nov 19, 2000: Bac AVRO146RJ85A (N513XJ), Minneapolis, MN, Minor damage. (-23) Mesaba flight 3596, under the command of captain[privacy data omitted]taxied into a congested and snow-covered gate area at Minneapolis, MN. During…

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.