OpenAirDocs.org

20120112000069I

Incident · No damage
Open the Markdown

FAA incident report · Bombardier CL-600-2B19 · Charleston, WV · January 12, 2012

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
January 12, 2012 · 08:10 local
Place
Charleston, WV
Phase of flight
Cruise/Level Flight
Operating rules
Air carrier (Part 121)
Operator
VNAA
Damage
No damage
Aircraft
N226JS
Reported as
Bombardier CL-600-2B19
Reported engine
GE CF34 series
People aboard
25
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
N226JSRegistered now · Bombardier CL-600-2B19S/N 7895 · Built 2004Airframe modelBombardier CL-600-2B19Engine modelGE CF34 seriesTurbo-fan

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.