EMB145 flight crew reported multiple control system anomalies in flight requiring a precautionary landing.
Synopsis
EMB145 flight crew reported multiple control system anomalies in flight requiring a precautionary landing.
Narrative
Departure from runway XX; claiming on ZZZZZ SID. At 1;300 ft; On right turn per SID. We experienced Trim runway and bunch of other messages displayed on EICAS.- Rudder System 1-2 Inop- Yam dumper fail- Autopilot fail- Pitch trip main InopI immediately executed memory item for Pitch trim runaway followed by QRH. FO run QRH and i was flying. We were able to trouble shot all issue at time. Few minutes later and during the cruise it happened again except this time there's no trim runway but message was displayed is Rudder system 1-2 Inop; No yaw dumper and no auto pilot; I transfer controls to the FO and I run QRH myself. Then I was able to trouble shot the issues. Again few minutes later while FO Still pilot flying and was still monitoring for other complications. Suddenly autopilot fail; yaw dumper fail and rudder system 1-2 inop came back again. I Run QRH again; and this time the message of rudder system 1-2 Inop precisest. We slow down 250 knots on speed and cruising at FL270; no Autopilot and no Yaw dumper. I made an announcement to the passengers and also brief flight attendant; that we are planing on precautionary landing and fire truck will be present in the field etc.Around 13;000 feet. I took controls back from the first officer; and been vectored for long and shallow turn for LNAV runway XX; which was visual anyway. Landing was executed according to the QRH; flaps 45. Landing was perfect. No Embrace; and No Injuries and NO medcs. Weather condtion was good; wind was very much down the runway.
Second reporter narrative
Captain was flying; Departing from runway XX passing 1000' Autopilot failed on us hand flying to around 1300' RUDDER system 1&2 INOP message was displayed on the EICAS. As he was flying the departure called for QRH; I ran the QRH procedure and troubleshooted the issue reengaged the autopilot and continued on. Few minutes later the same issue repeated with the same EICAS messages. This time Captain handed over the controls to me and he ran the QRH second time; the messages went away and problem was fixed. We were doing fine until almost half way in to the cruise at FL 270 malfunction messages reappeared on the EICAS (along with malfunctions). Captain once again ran the QRH procedure; messages didn't go away the 3rd time as well as we couldn't troubleshoot the issue. As a precaution we slowed down the aircraft to 250kts. I flew it down to 13000 from there captain took over. He made announcement to the passengers and informed the FA our decision. Made it clear it's a precautionary measure.We were given long vector for final app in to Runway XX RNAV approach. Landed safely.EICAS MESSAGESAUTOPILOT FAILRUDDER SYSTEM INOPPITH TRIM INOPYAW DAMP FAIL
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.