37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1037077 |
Time | |
Date | 201209 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Rudder Control System |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
On climb up to cruise altitude; rudder system 1-2 inoperative EICAS message appeared. We ran the rudder system 1-2 inoperative QRH and rudder system 1 came back online; rudder system 2 did not. We notified dispatch via radio. [The dispatcher] could not get a hold of maintenance control; they tried a second time. We tried to relay the problem to our dispatcher; however at that point they had a difficult time hearing us. The [maintenance controller] who answered said he was 'busy' and told [dispatch] to tell us to air return. We confirmed with [our dispatcher] 3 times via ACARS if they really wanted us to return. At this point; they confirmed it and we were only 30 minutes away from the destination airport. We checked to see if we had enough fuel to return. We landed without incident; swapped aircraft and headed back out towards destination.
Original NASA ASRS Text
Title: EMB145 First Officer experiences a RUDDER SYS 1-2 INOP EICAS message during climb. QRH procedures are accomplished but only Rudder System 1 is returned to normal operation. Maintenance indicates that the crew should return to the departure airport; which is accomplished; although at the time they are closer to their destination.
Narrative: On climb up to cruise altitude; RUDDER SYS 1-2 INOP EICAS message appeared. We ran the RUDDER SYS 1-2 INOP QRH and Rudder System 1 came back online; Rudder System 2 did not. We notified Dispatch via radio. [The Dispatcher] could not get a hold of Maintenance Control; they tried a second time. We tried to relay the problem to our Dispatcher; however at that point they had a difficult time hearing us. The [Maintenance Controller] who answered said he was 'busy' and told [Dispatch] to tell us to air return. We confirmed with [our Dispatcher] 3 times via ACARS if they really wanted us to return. At this point; they confirmed it and we were only 30 minutes away from the destination airport. We checked to see if we had enough fuel to return. We landed without incident; swapped aircraft and headed back out towards destination.
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.