Air carrier crew reported an EICAS message which affected several systems. Crew ran QRH and landed normally.

Date: 2025-10 · Aircraft: Any Unknown or Unlisted Aircraft Manufacturer · Phase: cruise

Anomalies: aircraft-equipment-problem-critical

Synopsis

Air carrier crew reported an EICAS message which affected several systems. Crew ran QRH and landed normally.

Narrative

We were level at FL350; the first officer was the pilot flying. About 40 minutes outside of ZZZ; the auto-throttles; autopilot; and yaw damp shut off; and we got the message 'AVNX MAU (Modular Avionics Unit) 1A FAIL.' We ran the QRH; which told us the relevant inoperative items; the big ones being half the brakes and the nose wheel steering. We chose to request priority handling as a precaution. The best option was to continue to ZZZ; which at this point was 30 minutes away; as it gave us time to get set up and burn off a little more fuel to be as light as we could be for landing. We felt there was no immediate danger to the aircraft. We called the flight attendant using the emergency call button. We advised them of the situation. No special instructions were given and we told them no need to brace. We were planning on landing on runway XXR until we talked to ZZZ; and they asked if we could accept XYL instead. Initially; we didn't accept the change; but after learning the wind had shifted to more favor XYL; plus giving us a few more feet of runway. We landed and rolled out to stop short of Taxiway 1. On landing; we experienced poor braking; which was expected but still had plenty of room to get the aircraft stopped. We stopped on the runway; and the emergency services inspected the aircraft but did not find any indication of damage or overheating. We made the decision to get towed to the gate as I didn't want to maneuver the aircraft around other aircraft and buildings with less brakes than I was use to and no nose wheel steering.

Second reporter narrative

During the cruise phase of flight; approximately 45 minutes from ZZZ; the autopilot and autothrottles disengaged unexpectedly. A loud thumping sound was heard from the aft section of the aircraft. Several EICAS messages were displayed; including AVNX MAU (Modular Avionics Unit) 1A FAIL; ADS 1 FAIL; SPOILER FAULT; FDR (Flight Data Recorder) FWD FAIL; BRK RH FAULT; BRK LH FAULT; and SPDBRK (Speed Brake) FAIL.I was the Pilot Flying (PF) and the Captain was the Pilot Monitoring (PM). The Captain's flight director failed; and the Captain's MCDU (Multipurpose Control Display Unit) was inoperative except for circuit breaker monitoring. The dispatcher was contacted via ARINC; and communication was maintained for the remainder of the flight.We discussed the possibility of a diversion. However; after considering maintenance availability; runway length; weather conditions; emergency response capability; and overall operational factors; we determined that continuing to ZZZ was the safest and most practical option. The autopilot and autothrottles were subsequently re-engaged and operated normally for the remainder of the flight.Initially; we planned for Runway XXL at ZZZ. After coordination with ATC; Runway XYL was selected due to more favorable winds and to allow us to stop on the runway for inspection and towing with minimal impact to airport operations.We reviewed the possibility of degraded braking performance. We agreed that; if additional braking was required; I would call for assistance and the Captain would use the parking brake due to its position on the flight deck. We also discussed whether to request priority handling and jointly decided that if we were within approximately 30 minutes of the destination; we would do so as a precaution in case of braking issues. Priority handling was declared accordingly.The Captain briefed the flight attendants; passengers; and dispatcher on the situation and our plan. We computed the landing distance and braking coefficient; and completed both the Flight Control Malfunction Descent and Flight Control Malfunction Landing checklists. ATC provided a long final and a straight-out missed approach as requested. A flaps full approach and landing were accomplished normally.Landing and rollout proceeded according to plan; and the aircraft was brought to a safe stop at the end of Runway XYL. Upon stopping; additional EICAS messages appeared and were addressed in accordance with SOP. Airport emergency crews inspected the aircraft. After completing the After Landing Checklist; Operations arranged for a tug; and the aircraft was towed to the gate under escort by airport operations and fire crews.Once parked; the Parking Checklist was completed. On and in times were relayed to dispatch; maintenance write-ups were entered; and passengers deplaned normally. The post-flight inspection was completed; and maintenance personnel met the aircraft and began troubleshooting.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.