Narrative:

The 'a' loop of the right engine fire detection system was mco'ed (maintenance carry over) inoperative. When we performed the fire test during preflight (with the 'B' loop selected per the MEL), the test failed. We called contract maintenance. He got a good test when he selected the 'a' loop (which was previously mco'ed). So the contract maintenance man wrote ''a' loop checks good,' and mco'ed the 'B' loop on the right engine. After we started the right engine, we got another 'a' loop failure. We shut down, called contract maintenance and this time he selected the 'B' loop and the test was normal, so he mco'ed the 'a' loop again. (So we were back where we started from -- 'a' loop inoperative and 'B' loop selected.) extensive troubleshooting could not reveal why the 'a' loop was bad or why the 'B' loop tested bad then tested good. This airplane (MD90) is equipped with a fire detection system that continually checks the loops for problems, and will automatically select the good loop if the other develops a problem. This airplane had a previous history of the 'B' loop being inoperative. Although we tested the 'B' loop several times, and it worked again, I was uncomfortable taking a plane that had the 'a' loop on mco and the 'B' loop operating but with a recent history of problems. It was also disconcerting that we did not know why the 'B' loop failed at the gate, and then 'fixed itself.' this airplane (MD90) does have the reputation of having spurious electrical faults that go away on their own. I am used to this, but not with the fire detection system. My ultimate concern was that if we had a 'B' loop failure we didn't know about, then we would lose fire detection on the right engine.

Google
 

Original NASA ASRS Text

Title: FO RPTS ON PROBS WITH THE MD90 LOOP FIRE DETECTION SYS.

Narrative: THE 'A' LOOP OF THE R ENG FIRE DETECTION SYS WAS MCO'ED (MAINT CARRY OVER) INOP. WHEN WE PERFORMED THE FIRE TEST DURING PREFLT (WITH THE 'B' LOOP SELECTED PER THE MEL), THE TEST FAILED. WE CALLED CONTRACT MAINT. HE GOT A GOOD TEST WHEN HE SELECTED THE 'A' LOOP (WHICH WAS PREVIOUSLY MCO'ED). SO THE CONTRACT MAINT MAN WROTE ''A' LOOP CHKS GOOD,' AND MCO'ED THE 'B' LOOP ON THE R ENG. AFTER WE STARTED THE R ENG, WE GOT ANOTHER 'A' LOOP FAILURE. WE SHUT DOWN, CALLED CONTRACT MAINT AND THIS TIME HE SELECTED THE 'B' LOOP AND THE TEST WAS NORMAL, SO HE MCO'ED THE 'A' LOOP AGAIN. (SO WE WERE BACK WHERE WE STARTED FROM -- 'A' LOOP INOP AND 'B' LOOP SELECTED.) EXTENSIVE TROUBLESHOOTING COULD NOT REVEAL WHY THE 'A' LOOP WAS BAD OR WHY THE 'B' LOOP TESTED BAD THEN TESTED GOOD. THIS AIRPLANE (MD90) IS EQUIPPED WITH A FIRE DETECTION SYS THAT CONTINUALLY CHKS THE LOOPS FOR PROBS, AND WILL AUTOMATICALLY SELECT THE GOOD LOOP IF THE OTHER DEVELOPS A PROB. THIS AIRPLANE HAD A PREVIOUS HISTORY OF THE 'B' LOOP BEING INOP. ALTHOUGH WE TESTED THE 'B' LOOP SEVERAL TIMES, AND IT WORKED AGAIN, I WAS UNCOMFORTABLE TAKING A PLANE THAT HAD THE 'A' LOOP ON MCO AND THE 'B' LOOP OPERATING BUT WITH A RECENT HISTORY OF PROBS. IT WAS ALSO DISCONCERTING THAT WE DID NOT KNOW WHY THE 'B' LOOP FAILED AT THE GATE, AND THEN 'FIXED ITSELF.' THIS AIRPLANE (MD90) DOES HAVE THE REPUTATION OF HAVING SPURIOUS ELECTRICAL FAULTS THAT GO AWAY ON THEIR OWN. I AM USED TO THIS, BUT NOT WITH THE FIRE DETECTION SYS. MY ULTIMATE CONCERN WAS THAT IF WE HAD A 'B' LOOP FAILURE WE DIDN'T KNOW ABOUT, THEN WE WOULD LOSE FIRE DETECTION ON THE R ENG.

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.