# Incident 20170126000089I: Bombardier Inc CL-600-2C10, Nashville, TN, January 26, 2017

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 26, 2017, 18:07 local time
- Place: Nashville, TN
- Airport: Nashville International
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: Air carrier (Part 121)
- Operator: MASA
- Location: 36.1245° N, 86.6782° W: Placed by OpenAirDocs at NASHVILLE INTL (BNA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1245&lon=-86.6782&mi=10
- Aircraft: N515MJ (not matched to a registry record)
- Reported make and model: BOMBARDIER INC CL-600-2C10
- Reported engine: GE CF34-8C5B1
- People aboard: 65
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 18,175 total, 1,336 in this make and model, 224 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170126000089I

## Narrative

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

AN EMERGENCY LANDING (CA LANDING) WAS COMPLETED AFTER VISUAL APPROACH TO RUNWAY 31 BNA, DUE TO RAPID FUEL LOSS FOLLOWED BY R ENG FIRE WARNING.  WHILE ON APPROACH TO BNA (40 MILES OUT) AT FL220, FO (PILOT FLYING) IDENTIFIED APPARENT EXCESSIVE FUEL FLOW, A SIGNIFICANT FUEL FLOW DIFFERENTIAL, AND CONTINUOUS R AUTO FUEL XFLOW STATUS MESSAGE SHORTLY BEFORE BEING CLEARED TO DESCEND VIA THE PASLY4 ARRIVAL.  CA THEN ALSO NOTED THE OIL AND FUEL TEMPS HAD SIGNIFICANT DIFFERENCES FROM SIDE TO SIDE.  THE CREW BRIEFLY MONITORED FUEL CONDITION AND ENGINE INDICATIONS, AND THE CA DETERMINED THEY DID INDEED HAVE A FUEL ISSUE, FUEL HAD RAPIDLY DECREASED TO BELOW PLANNED RESERVE FUEL.  THE CREW REQUESTED STRAIGHT-IN APPROACH TO RUNWAY 31 DUE TO POTENTIAL FUEL PROBLEM, AND SUBSEQUENTLY RECEIVED VECTORS AND DESCENT.  THEY COMPLETED THE IN-RANGE CHECKLIST, BY APPROXIMATELY 9000 MSL.  THEN RECEIVED R ENG FIRE WARNING APPROXIMATELY 7000 MSL, ALL ENGINE AND FUEL SYSTEM INDICATIONS HAD REMAINED GREEN UNTIL THIS POINT.  CA RAN THE EPC FOR ENG FIRE OR SEVERE ENGINE DAMAGE (INFLIGHT), DECLARED AN EMERGENCY, AND NOTIFIED FAS OF EMERGENCY, WHILE FO CONTINUED TO FLY AND TALK TO ATC AS NEEDED.  THE R ENG FIRE WARNING PERSISTED AFTER COMPLETING ALL STEPS OF THE ENG FIRE CHECKLIST, BOTH FIRE BOTTLES WERE DISCHARGED.  THEY RECEIVED CLEARANCE FOR VISUAL APPROACH TO RWY 31.  MAINTAINED 250 KNOTS UNTIL THEY HAD TO SLOW FOR LANDING CONFIGURATION, LANDED WITH FLAPS 20.  CA TOOK THE FLIGHT CONTROLS AT 2500 MSL AND APPROXIMATELY 6 MILES FROM THE RUNWAY.  CA SAFELY LANDED THE PLANE AND EVACUATED THE AIRCRAFT ON RUNWAY 31, THROUGH PASSENGER DOOR ON LEFT SIDE OF AIRCRAFT, COMPLETING PASSENGER EVACUATION CHECKLIST.  AIRPORT FIRE CREW CONFIRMED EVIDENCE OF RIGHT ENGINE FIRE AND EXTINGUISHED WITH FOAM FOLLOWED BY WATER.  AIRPORT FIRE CREW DID NOT SEE FIRE BUT, SMOKE WAS TRAILING FROM THE #2 ENGINE (ESN 965370, P/N CF34-8C5B1, TSN 32423:57, CSN 23296, TSO 20289:44, CSO 15048).  ALL PASSENGERS AND CREW EXITED THROUGH THE MAIN CABIN DOOR SAFELY WITH NO INJURIES REPORTED.

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.