37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1631678 |
Time | |
Date | 201903 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | EMB ERJ 190/195 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Rudder |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 10000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
While at FL300 we experienced multiple uncommanded rudder deflections. The first occurred over a waypoint and was very subtle. We were fortunate because due to the first event I maintained positive contact with the flight controls. The second event was more violent and resulted in an undesired aircraft state. By referencing the turn and slip coordinator and our own senses; we knew the aircraft was 'cross controlled'. I pressed and held the quick disconnect button and took control of the aircraft. We immediately [requested priority handling] and requested a diversion to ZZZ. Unfortunately there was no EICAS [engine indicating and crew alerting system] messages to provide an appropriate course of action. We realized it was a rudder issue so I felt it was wise to slow the aircraft to 250 knots and minimize bank angles to 10 degrees or less while turning the aircraft. There was no apparent incorrect rudder trim and realized that the problem was due to uncommanded rudder deflections. While being vectored for the approach; I transferred controls to the first officer and referenced the qrc and QRH for any guidance. We found that there was no action to be taken and we elected to land with flaps full. A successful approach and landing was made resulting in no damage to the aircraft or injuries. Upon landing we received a flight control no dispatch EICAS message.
Original NASA ASRS Text
Title: EMB190 Captain reported uncommanded rudder deflection in cruise flight resulting in a diversion.
Narrative: While at FL300 we experienced multiple uncommanded rudder deflections. The first occurred over a waypoint and was very subtle. We were fortunate because due to the first event I maintained positive contact with the flight controls. The second event was more violent and resulted in an undesired aircraft state. By referencing the turn and slip coordinator and our own senses; we knew the aircraft was 'cross controlled'. I pressed and held the quick disconnect button and took control of the aircraft. We immediately [requested priority handling] and requested a diversion to ZZZ. Unfortunately there was no EICAS [Engine Indicating and Crew Alerting System] messages to provide an appropriate course of action. We realized it was a rudder issue so I felt it was wise to slow the aircraft to 250 knots and minimize bank angles to 10 degrees or less while turning the aircraft. There was no apparent incorrect rudder trim and realized that the problem was due to uncommanded rudder deflections. While being vectored for the approach; I transferred controls to the First Officer and referenced the QRC and QRH for any guidance. We found that there was no action to be taken and we elected to land with flaps full. A successful approach and landing was made resulting in no damage to the aircraft or injuries. Upon landing we received a Flight Control No Dispatch EICAS message.
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.