# Incident 20120112000069I: Bombardier Inc CL-600-2B19, Charleston, WV, January 12, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 12, 2012, 08:10 local time
- Place: Charleston, WV
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: Air carrier (Part 121)
- Operator: VNAA
- 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: N226JS, registered now (https://openairdocs.org/aircraft/N226JS) (OpenAirDocs)
- Registry model: Bombardier CL-600-2B19 (registry code 1390008, https://openairdocs.org/model/bombardier-cl-600-2b19) (OpenAirDocs)
- Registry engine: GE CF34 series (registry code 30015, https://openairdocs.org/engine/ge-cf34-series) (OpenAirDocs)
- Reported make and model: BOMBARDIER INC CL-600-2B19
- Reported engine: GE CF34 SERIES
- People aboard: 25
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120112000069I

## Narrative

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

AIRCRAFT WAS ENROUTE FROM NASHVILLE (BNA) TO REAGON/NATIONAL (DCA) AT FL310 WHEN THERE WAS A CARGO SMOKE WARNING LIGHT.THE PILOT IMMEDIATELY REFERRED TO THE QRH EMERGENCY PROCEDURE, ACTIVATED THE CARGO FIRE BOTTLE SYSTEM, BUT THE WARNING LIGHT REMAINED.THE PILOT THEN DIVERTED TO CHARLESTON YEAGER (CRW). THE PILOT LANDED AND STOPPED THE AIRCRAFT ON RUNWAY 23, AND ORDERED AN EMERGENCY EVACUATION OF THE PASSENGERS VIA THE AIRCRAFT STEPS. THEY WERE IMMEDIATELY PUT ON A BUS AND TAKEN TO THE TERMINAL. NO PASSENGER INJURIES WERE REPORTED DURING THE EVACUATION.  NO SMOKE WAS NOTED IN THE COCKPIT OR CABIN, BUT WHEN THE BAGGAGE DOOR WAS OPENED BY THE ARFF WHAT APPEARED TO BE SMOKE CAME OUT, BUT IT WAS LATER DETERMINED THAT IT WAS POSSIBLY THE HALON THAT WAS RELEASED.ALL PASSENGER BAGS WERE SCREENED BY CRW TSA TWICE AND PHYSICALLY SEARCHED ONCE FOR ANY EVIDENCE OF FIRE DAMAGE OR SMOKE. AN FAA INSPECTOR WAS PRESENT DURING THIS SCREENING. THE PASSENGER BAGS WERE THEN RELEASED. THE PMI FOR PSA WAS CONTACTED AN MEL FOR BOTH CARGO COMPARTMENT SMOKE DETECTORS AND AN MEL FOR THE CARGO FIRE EXTINGUISHING SYSTEM. THE AIRCRAFT THEN REPOSITIONED FROM CRW TO CLT WHERE CLT MX REPLACED BOTH CARGO SMOKE DETECTORS AND BOTH CARGO FIRE BOTTLES AND CLEARED BOTH MEL'S, RETURNING THE AIRCRAFT TO SERVICE.

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.