37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 424577 |
Time | |
Date | 199901 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : stl |
State Reference | MO |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Jetstream 32 |
Flight Phase | other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument |
Experience | flight time last 90 days : 210 flight time total : 3500 flight time type : 240 |
ASRS Report | 424577 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 210 flight time total : 1670 flight time type : 470 |
ASRS Report | 424573 |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : declared emergency other |
Consequence | Other |
Narrative:
We taxied from the gate, took 'position and hold' on runway 30L at stl. Our fire bell and cap light went on indicating a left engine fire. We feathered both engines and completed our emergency items which included firing both fire bottles. We evacuate/evacuationed our 5 passenger out the rear main exit. The fire trucks determined there was no fire and so I suspect the fire detection loop was faulty. We elected to evacuate/evacuation out of the main door on the left side after visually evaluating whether there was a legitimate fire risk to our passenger and balancing that against the risk of evacing over the wing onto an icy runway. Callback conversation with reporter revealed the following information: the reporter stated the false warning was caused by the faulty engine fire sensing loop but the exact component of the loop that failed is unknown. Callback conversation with reporter on acn 424573 revealed the following information: the reporter stated the false fire warning was caused by a defective engine fire warning sensing loop.
Original NASA ASRS Text
Title: A JETSTREAM 3201 IN POS AND HOLD FOR TKOF DECLARED AN EMER AND EVACED THE ACFT DUE TO A L ENG FIRE WARNING BELL AND LIGHT CAUSED BY A FAULTY ENG FIRE SENSING LOOP.
Narrative: WE TAXIED FROM THE GATE, TOOK 'POS AND HOLD' ON RWY 30L AT STL. OUR FIRE BELL AND CAP LIGHT WENT ON INDICATING A L ENG FIRE. WE FEATHERED BOTH ENGS AND COMPLETED OUR EMER ITEMS WHICH INCLUDED FIRING BOTH FIRE BOTTLES. WE EVACED OUR 5 PAX OUT THE REAR MAIN EXIT. THE FIRE TRUCKS DETERMINED THERE WAS NO FIRE AND SO I SUSPECT THE FIRE DETECTION LOOP WAS FAULTY. WE ELECTED TO EVAC OUT OF THE MAIN DOOR ON THE L SIDE AFTER VISUALLY EVALUATING WHETHER THERE WAS A LEGITIMATE FIRE RISK TO OUR PAX AND BALANCING THAT AGAINST THE RISK OF EVACING OVER THE WING ONTO AN ICY RWY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE FALSE WARNING WAS CAUSED BY THE FAULTY ENG FIRE SENSING LOOP BUT THE EXACT COMPONENT OF THE LOOP THAT FAILED IS UNKNOWN. CALLBACK CONVERSATION WITH RPTR ON ACN 424573 REVEALED THE FOLLOWING INFO: THE RPTR STATED THE FALSE FIRE WARNING WAS CAUSED BY A DEFECTIVE ENG FIRE WARNING SENSING LOOP.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.