Narrative:

Aircraft was dispatched with an MEL on loop B of r-hand engine fire detection system. On climb out I (I was PNF) noticed the master caution light flicker, but I was unable, at first, to determine the exact light. Happened again and 'fire detect loop' light stayed illuminated for a few seconds without t-handle illuminating. Flickered again and fire warning. T-handle sounded intermittently. Talked to company and agreed to return to sea. QRH was followed for loop failure. The MEL'ed loop tested fine and there was no fire warning with B side selected. Did we have a fire or bleed leak and run the wrong checklist? Possibly, but it seemed like a loop problem because there were no other indications of fire. There were several mins between 'flickers,' the 'a' side failed the test and the 'B' side tested ok, and this 'flicker' happened to other crews recently. But perhaps we should have followed the fire checklist, but again it was intermittent and do we shut down an engine in this situation? We chose not. On the ground, the mechanics found 1 loop to work and test fine but the other was faulty. They also said they had been troubleshooting the problem for 2 nights and maybe the wires were crossed. Callback conversation with reporter revealed the following information: the reporter stated maintenance reported the failed intermittent loop was 'B' loop but the connectors on the engine loop were swapped for troubleshooting and not returned to normal so the intermittent loop was connected to loop 'a' control panel. The reporter said the only operative loop which was 'a' loop was connected to the control panel 'B' loop and deferred as intermittent. The reporter said the loop 'a' tested ok but were actually checking the intermittent loop 'B' because of the connector swap.

Google
 

Original NASA ASRS Text

Title: AN MD80 ON INITIAL CLB AT 3000 FT HAD A R ENG INTERMITTENT FIRE WARNING CAUSED BY AN IMPROPERLY CONNECTED FIRE WARNING LOOP.

Narrative: ACFT WAS DISPATCHED WITH AN MEL ON LOOP B OF R-HAND ENG FIRE DETECTION SYS. ON CLBOUT I (I WAS PNF) NOTICED THE MASTER CAUTION LIGHT FLICKER, BUT I WAS UNABLE, AT FIRST, TO DETERMINE THE EXACT LIGHT. HAPPENED AGAIN AND 'FIRE DETECT LOOP' LIGHT STAYED ILLUMINATED FOR A FEW SECONDS WITHOUT T-HANDLE ILLUMINATING. FLICKERED AGAIN AND FIRE WARNING. T-HANDLE SOUNDED INTERMITTENTLY. TALKED TO COMPANY AND AGREED TO RETURN TO SEA. QRH WAS FOLLOWED FOR LOOP FAILURE. THE MEL'ED LOOP TESTED FINE AND THERE WAS NO FIRE WARNING WITH B SIDE SELECTED. DID WE HAVE A FIRE OR BLEED LEAK AND RUN THE WRONG CHKLIST? POSSIBLY, BUT IT SEEMED LIKE A LOOP PROB BECAUSE THERE WERE NO OTHER INDICATIONS OF FIRE. THERE WERE SEVERAL MINS BTWN 'FLICKERS,' THE 'A' SIDE FAILED THE TEST AND THE 'B' SIDE TESTED OK, AND THIS 'FLICKER' HAPPENED TO OTHER CREWS RECENTLY. BUT PERHAPS WE SHOULD HAVE FOLLOWED THE FIRE CHKLIST, BUT AGAIN IT WAS INTERMITTENT AND DO WE SHUT DOWN AN ENG IN THIS SIT? WE CHOSE NOT. ON THE GND, THE MECHS FOUND 1 LOOP TO WORK AND TEST FINE BUT THE OTHER WAS FAULTY. THEY ALSO SAID THEY HAD BEEN TROUBLESHOOTING THE PROB FOR 2 NIGHTS AND MAYBE THE WIRES WERE CROSSED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED MAINT RPTED THE FAILED INTERMITTENT LOOP WAS 'B' LOOP BUT THE CONNECTORS ON THE ENG LOOP WERE SWAPPED FOR TROUBLESHOOTING AND NOT RETURNED TO NORMAL SO THE INTERMITTENT LOOP WAS CONNECTED TO LOOP 'A' CTL PANEL. THE RPTR SAID THE ONLY OPERATIVE LOOP WHICH WAS 'A' LOOP WAS CONNECTED TO THE CTL PANEL 'B' LOOP AND DEFERRED AS INTERMITTENT. THE RPTR SAID THE LOOP 'A' TESTED OK BUT WERE ACTUALLY CHKING THE INTERMITTENT LOOP 'B' BECAUSE OF THE CONNECTOR SWAP.

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.