Narrative:

On a flight from ewr to sav, during a step up climb near the coyle VOR, we received a low N1 warning on the #2 engine of an EMB145. After following company procedures and checklists, the low N1 warning would not go away if thrust lever was at maximum thrust. We elected to return to ewr and land. While receiving radar vectors from ATC, the #2 engine shut down. We declared an emergency and returned to ewr without further incident. Callback conversation with reporter revealed the following information: reporter states the engine, an allison AE3007A, is controled by a fadec and would not allow a power setting greater than 81.6 N1 then it just shut down. Reporter advised maintenance reported finding the control rods or push rods which move the variable guide vanes bent, which probably was cause for the low power and then shortly after the shutdown. The reporter related that these rods have been an ongoing problem. Supplemental information from acn 382560: while climbing out of new york terminal area, we received an EICAS warning for engine #2 low N1. We complied with the QRH, though the problem was not resolved, so we contacted maintenance control. They directed us to attempt various system resets (fadec). The engine was developing plenty of power and the message and abnormal N1 parameter only occurred in the autothrust mode. It was decided that we would be unable to rectify what we believed to be a software problem. We requested and received vectors back to ewr (point of departure). Shortly after turning back, all #2 engine parameters fell back to idle -- no thrust was available. We accomplished precautionary engine shutdown QRH, declared an emergency, accomplished all abnormal and normal checklists, and executed a single engine approach and landing at ewr. There was no further incident, no fire and no injuries.

Google
 

Original NASA ASRS Text

Title: AN EMBRAER 145 ON CLB DECLARED AN EMER AND DIVERTED DUE TO #2 ENG FAILURE.

Narrative: ON A FLT FROM EWR TO SAV, DURING A STEP UP CLB NEAR THE COYLE VOR, WE RECEIVED A LOW N1 WARNING ON THE #2 ENG OF AN EMB145. AFTER FOLLOWING COMPANY PROCS AND CHKLISTS, THE LOW N1 WARNING WOULD NOT GO AWAY IF THRUST LEVER WAS AT MAX THRUST. WE ELECTED TO RETURN TO EWR AND LAND. WHILE RECEIVING RADAR VECTORS FROM ATC, THE #2 ENG SHUT DOWN. WE DECLARED AN EMER AND RETURNED TO EWR WITHOUT FURTHER INCIDENT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE ENG, AN ALLISON AE3007A, IS CTLED BY A FADEC AND WOULD NOT ALLOW A PWR SETTING GREATER THAN 81.6 N1 THEN IT JUST SHUT DOWN. RPTR ADVISED MAINT RPTED FINDING THE CTL RODS OR PUSH RODS WHICH MOVE THE VARIABLE GUIDE VANES BENT, WHICH PROBABLY WAS CAUSE FOR THE LOW PWR AND THEN SHORTLY AFTER THE SHUTDOWN. THE RPTR RELATED THAT THESE RODS HAVE BEEN AN ONGOING PROB. SUPPLEMENTAL INFO FROM ACN 382560: WHILE CLBING OUT OF NEW YORK TERMINAL AREA, WE RECEIVED AN EICAS WARNING FOR ENG #2 LOW N1. WE COMPLIED WITH THE QRH, THOUGH THE PROB WAS NOT RESOLVED, SO WE CONTACTED MAINT CTL. THEY DIRECTED US TO ATTEMPT VARIOUS SYS RESETS (FADEC). THE ENG WAS DEVELOPING PLENTY OF PWR AND THE MESSAGE AND ABNORMAL N1 PARAMETER ONLY OCCURRED IN THE AUTOTHRUST MODE. IT WAS DECIDED THAT WE WOULD BE UNABLE TO RECTIFY WHAT WE BELIEVED TO BE A SOFTWARE PROB. WE REQUESTED AND RECEIVED VECTORS BACK TO EWR (POINT OF DEP). SHORTLY AFTER TURNING BACK, ALL #2 ENG PARAMETERS FELL BACK TO IDLE -- NO THRUST WAS AVAILABLE. WE ACCOMPLISHED PRECAUTIONARY ENG SHUTDOWN QRH, DECLARED AN EMER, ACCOMPLISHED ALL ABNORMAL AND NORMAL CHKLISTS, AND EXECUTED A SINGLE ENG APCH AND LNDG AT EWR. THERE WAS NO FURTHER INCIDENT, NO FIRE AND NO INJURIES.

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.