Narrative:

After the pushback; just after starting engine number two; we got the message rudder system 2 inoperative on the EICAS. We ran the QRH and then contacted maintenance control for direction and made a logbook entry recording the discrepancy. Maintenance control directed us to complete a procedure that cleared the indication and then directed us to enter 'system self-reset per mcc no further action required' in the corrective action.we taxed to runway xxl with no further irregularities. We began the takeoff roll and before the 80 knot call-out; we got the message rudder system 2 inoperative on the EICAS. I called for the abort; the first officer; who was the pilot not flying; informed the tower and told the passengers to remain seated. After aborting the takeoff; we taxied down the runway exited and then ran the aborted takeoff and after landing checklist. After coordinating with dispatch; maintenance; and operations; we returned to the gate; where we deplaned the passengers and returned their luggage. I wrote a new logbook entry indicating the discrepancy and coordinated this with maintenance control. A mechanic was flown up from [another station] and after he repaired the aircraft we ferried the aircraft back to [that station] that afternoon without further event. Aborting the takeoff was an unusual event and a potential threat. In this case; given that the message rudder system 2 inoperative had occurred before at the gate; it was clearly an abnormal situation; since we were still below 80 knots; an abort was the safest course of action to mitigate any potential risk.I am not sure if the mechanical cause that triggered the message rudder system 2 inoperative is something that could have been caught earlier. Since we did have this issue at the gate; I am wondering if we could have trapped this mechanical issue earlier and avoided the aborted takeoff completely.

Related reports:

Google
 

Original NASA ASRS Text

Title: An EMB-145 EICAS alerted RUDDER SYS 2 INOP after engine start but Maintenance Control had the crew reset and log the event. During takeoff the same EICAS alert resulted in a rejected takeoff and return to the gate.

Narrative: After the pushback; just after starting engine number two; we got the message RUDDER SYS 2 INOP on the EICAS. We ran the QRH and then contacted Maintenance Control for direction and made a logbook entry recording the discrepancy. Maintenance Control directed us to complete a procedure that cleared the indication and then directed us to enter 'system self-reset per MCC no further action required' in the corrective action.We taxed to Runway XXL with no further irregularities. We began the takeoff roll and before the 80 knot call-out; we got the message RUDDER SYS 2 INOP on the EICAS. I called for the abort; the First Officer; who was the pilot not flying; informed the Tower and told the passengers to remain seated. After aborting the takeoff; we taxied down the runway exited and then ran the Aborted Takeoff and After Landing checklist. After coordinating with Dispatch; Maintenance; and Operations; we returned to the gate; where we deplaned the passengers and returned their luggage. I wrote a new logbook entry indicating the discrepancy and coordinated this with Maintenance Control. A Mechanic was flown up from [another station] and after he repaired the aircraft we ferried the aircraft back to [that station] that afternoon without further event. Aborting the takeoff was an unusual event and a potential threat. In this case; given that the message RUDDER SYS 2 INOP had occurred before at the gate; it was clearly an abnormal situation; since we were still below 80 knots; an abort was the safest course of action to mitigate any potential risk.I am not sure if the mechanical cause that triggered the message RUDDER SYS 2 INOP is something that could have been caught earlier. Since we did have this issue at the gate; I am wondering if we could have trapped this mechanical issue earlier and avoided the aborted takeoff completely.

Data retrieved from NASA's ASRS site as of July 2013 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.