Narrative:

Takeoff began normally; with 'takeoff configuration ok' advisory message being displayed on EICAS 2. As takeoff power was applied; an immediate triple chime; master warning occurred; with 'configuration rudder' being displayed on EICAS 2. The rudder trim was centered and in the green. We exited the runway onto the next available taxiway; and contacted maintenance control on the phone. I was told to exercise the rudder trim full left and right; [and] then re-center it. It again showed green and the aircraft was released for service by maintenance control. Maintenance control requested I contact them in our destination to let them know if there was an issue again. The subsequent takeoff occurred without issue. I contacted maintenance control upon arrival; and was then requested to write up the discrepancy regarding the configuration rudder warning; with the corrective action of 'this discrepancy no longer exists'. Upon conversation with a supervisor the following day; it occurred to me that the initial corrective action which occurred with maintenance control while still in departure airport did not include advancing the engine thrust to a setting which would cause the 'configuration rudder' warning to occur again prior to the subsequent takeoff.although the rudder trim was centered and in the green; this warning still occurred. Threat would be the pressure to 'get the flight on time;' as well as again trusting maintenance as opposed to questioning every issue which occurs with them. My error was not questioning why the aircraft was being released without an initial writeup and corrective action immediately following the discrepancy as well as why the aircraft was not set back into a state which would cause the discrepancy to occur prior to the next takeoff attempt.again; ensure everything is done correctly even when dealing with a maintenance issue.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CRJ-200 Master Warning CONFIG RUDDER EICAS alerted as takeoff power was set even with the rudder trim centered and in the green; so the takeoff was rejected and during communications with Maintenance they were instructed cycle and re-center the trim. The following takeoff was uneventful; but the crew realized a maintenance log entry and sign-off had not been completed.

Narrative: Takeoff began normally; with 'TAKEOFF CONFIG OK' Advisory message being displayed on EICAS 2. As takeoff power was applied; an immediate Triple Chime; Master Warning occurred; with 'CONFIG RUDDER' being displayed on EICAS 2. The rudder trim was centered and in the green. We exited the runway onto the next available taxiway; and contacted Maintenance Control on the phone. I was told to exercise the Rudder Trim full left and right; [and] then re-center it. It again showed green and the aircraft was released for service by Maintenance Control. Maintenance Control requested I contact them in our destination to let them know if there was an issue again. The subsequent takeoff occurred without issue. I contacted Maintenance Control upon arrival; and was then requested to write up the discrepancy regarding the CONFIG RUDDER Warning; with the Corrective Action of 'This discrepancy no longer exists'. Upon conversation with a Supervisor the following day; it occurred to me that the initial corrective action which occurred with Maintenance Control while still in departure airport did NOT include advancing the engine thrust to a setting which would cause the 'CONFIG RUDDER' Warning to occur again prior to the subsequent takeoff.Although the Rudder Trim was centered and in the green; this Warning still occurred. Threat would be the pressure to 'get the flight on time;' as well as again trusting Maintenance as opposed to questioning every issue which occurs with them. My error was not questioning why the aircraft was being released without an initial writeup and corrective action immediately following the discrepancy as well as why the aircraft was not set back into a state which would cause the discrepancy to occur prior to the next takeoff attempt.Again; ensure everything is done correctly even when dealing with a maintenance issue.

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