Narrative:

I had to abort a takeoff from dtw when the #2 engine did not reach takeoff power. After clearing the runway, I realized that I had inadvertently turned on the fadec control for the #2 engine. I believe during our acceptance check, that I turned the fadec on when we went to check the autoplt disengage buttons. The reason I did this was, when I talked to the captain who brought the aircraft in, we talked about the deferred fadec system and then he mentioned everything else was fine except the autoplt did not test on the first attempt, but when he cycled the fadec switch, it worked fine. (Usually cycling the autoplt master switch corrects the autoplt problem.) during our acceptance check of the aircraft, the autoplt did not test and my first reaction was to turn on the fadec control on the #2 engine, since it worked for the previous crew. When it didn't test, I started thinking about the system and felt that the other captain must have meant he cycled the 'autoplt master' when he said to me 'fadec.' at that point, I cycled the autoplt master and the system tested fine. I also neglected to turn the fadec system for the #2 engine back off. The start of all the engines and taxi out were all normal and there were no indications of a problem until the takeoff roll. During the takeoff roll we received a caution light and the #2 engine did not come up to takeoff power, at which point I called for an abort. Once we cleared the runway, I realized that the fadec for the #2 engine was on and since it was deferred, should have been off. I cycled the fadec to off and ran the engine up to normal takeoff power. Since there was an abort and it was reported to the tower as an engine failing to make takeoff power, and after talking to our maintenance department, we returned to the gate to have our maintenance take a look at it to be sure. They checked it out and we flew the next 3 legs without incident. I believe it was my fault for not cycling the fadec switch back to off after realizing that the fadec system probably had nothing to do with the autoplt system not testing. I am not sure why I didn't get back to it. It was a simple yet consequential oversight on my part. The only other 'fix' I can come up with is if the maintenance department were required to pull and collar a circuit breaker for the system as they do with others, ie, the APU.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN AVRO RJ-85 ON TKOF ROLL ABORTED THE TKOF DUE TO LOW PWR ON #2 ENG CAUSED BY SWITCHING A DEFERRED INOP ELECTRONIC FUEL CTL ON.

Narrative: I HAD TO ABORT A TKOF FROM DTW WHEN THE #2 ENG DID NOT REACH TKOF PWR. AFTER CLRING THE RWY, I REALIZED THAT I HAD INADVERTENTLY TURNED ON THE FADEC CTL FOR THE #2 ENG. I BELIEVE DURING OUR ACCEPTANCE CHK, THAT I TURNED THE FADEC ON WHEN WE WENT TO CHK THE AUTOPLT DISENGAGE BUTTONS. THE REASON I DID THIS WAS, WHEN I TALKED TO THE CAPT WHO BROUGHT THE ACFT IN, WE TALKED ABOUT THE DEFERRED FADEC SYS AND THEN HE MENTIONED EVERYTHING ELSE WAS FINE EXCEPT THE AUTOPLT DID NOT TEST ON THE FIRST ATTEMPT, BUT WHEN HE CYCLED THE FADEC SWITCH, IT WORKED FINE. (USUALLY CYCLING THE AUTOPLT MASTER SWITCH CORRECTS THE AUTOPLT PROB.) DURING OUR ACCEPTANCE CHK OF THE ACFT, THE AUTOPLT DID NOT TEST AND MY FIRST REACTION WAS TO TURN ON THE FADEC CTL ON THE #2 ENG, SINCE IT WORKED FOR THE PREVIOUS CREW. WHEN IT DIDN'T TEST, I STARTED THINKING ABOUT THE SYS AND FELT THAT THE OTHER CAPT MUST HAVE MEANT HE CYCLED THE 'AUTOPLT MASTER' WHEN HE SAID TO ME 'FADEC.' AT THAT POINT, I CYCLED THE AUTOPLT MASTER AND THE SYS TESTED FINE. I ALSO NEGLECTED TO TURN THE FADEC SYS FOR THE #2 ENG BACK OFF. THE START OF ALL THE ENGS AND TAXI OUT WERE ALL NORMAL AND THERE WERE NO INDICATIONS OF A PROB UNTIL THE TKOF ROLL. DURING THE TKOF ROLL WE RECEIVED A CAUTION LIGHT AND THE #2 ENG DID NOT COME UP TO TKOF PWR, AT WHICH POINT I CALLED FOR AN ABORT. ONCE WE CLRED THE RWY, I REALIZED THAT THE FADEC FOR THE #2 ENG WAS ON AND SINCE IT WAS DEFERRED, SHOULD HAVE BEEN OFF. I CYCLED THE FADEC TO OFF AND RAN THE ENG UP TO NORMAL TKOF PWR. SINCE THERE WAS AN ABORT AND IT WAS RPTED TO THE TWR AS AN ENG FAILING TO MAKE TKOF PWR, AND AFTER TALKING TO OUR MAINT DEPT, WE RETURNED TO THE GATE TO HAVE OUR MAINT TAKE A LOOK AT IT TO BE SURE. THEY CHKED IT OUT AND WE FLEW THE NEXT 3 LEGS WITHOUT INCIDENT. I BELIEVE IT WAS MY FAULT FOR NOT CYCLING THE FADEC SWITCH BACK TO OFF AFTER REALIZING THAT THE FADEC SYS PROBABLY HAD NOTHING TO DO WITH THE AUTOPLT SYS NOT TESTING. I AM NOT SURE WHY I DIDN'T GET BACK TO IT. IT WAS A SIMPLE YET CONSEQUENTIAL OVERSIGHT ON MY PART. THE ONLY OTHER 'FIX' I CAN COME UP WITH IS IF THE MAINT DEPT WERE REQUIRED TO PULL AND COLLAR A CIRCUIT BREAKER FOR THE SYS AS THEY DO WITH OTHERS, IE, THE APU.

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.