AN ACR B737-500 EVACED ITS PAX AFTER A TAILPIPE FIRE ON THE RAMP.

Date: 1996-06 · Aircraft: B737-500

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

AN ACR B737-500 EVACED ITS PAX AFTER A TAILPIPE FIRE ON THE RAMP.

Narrative

'NO START' #1 ENG START. ACCOMPLISHED 'NO START' CHKLIST. WHILE GND CREW WAS CONCERNED ABOUT A 'FIRE' AND CAPT OPENED HIS WINDOW TO VIEW 'FIRE;' I TALKED TO PAX ON PA. IN THE MIDDLE OF TELLING THEM ABOUT PROB; CAPT INITIATED EVAC. CABIN WAS EVACED THROUGH R SIDE OF ACFT (DOORS 1 AND 2 R) WITH NO INJURIES. I WAS LAST PERSON OFF ACFT. THE CAPT WAS NOT AROUND; SO MAINT PERSON AND MYSELF WENT UP SLIDE BACK INTO ACFT; REMOVED SLIDES; AND SAT IN FLT DECK WHILE B737-500 TOWED BACK INTO GATE. PEOPLE CAME BACK ON TO REMOVE BELONGINGS AND I LEFT ACFT. GOOD PROCS; BUT I DON'T BELIEVE CAPT SHOULD HAVE INITIATED EVAC FOR CONTAINED TAILPIPE FIRE. SUPPLEMENTAL INFO FROM ACN 340034: #1 ENG STABILIZED AT 28 PERCENT N2 WITH NO EGT INDICATIONS. WE BEGAN THE ABNORMAL START PROC; CONTINUING TO MOTOR THE ENG FOR 60 SECONDS. I INSTRUCTED THE FO TO SEND FIRE TRUCKS. NO COCKPIT INDICATIONS OF A FIRE. THE ABNORMAL START CHKLIST WAS NOT COMPLETED. THE CABIN EVAC WAS ACCOMPLISHED IN AN ORDERLY FASHION; WITHOUT INJURY TO PAX OR CREW.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.