Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Central Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Revenue flight from ZZZ1 to ZZZ cruising at 33;000 ft. approaching the TOD (Top of Descent). Crew received multiple failure messages: AVNX MAU3A FAIL; SPOILER FAULT; ADS3 FAIL; FMS2 FAIL; SPDBK FAIL; and other associated messages populated EICAS during approach and landing. Crew performed QRH procedures for the annunciated EICAS messages. Crew found That QRH FLT CTRL (Flight Control) page 12 'Spoiler Fault' stated that the landing distance will be increased by 1.78 and QRH FMS page 6 AVNX MAU3A FAIL stated relevant inoperative items (ADS3; GPS2; APU; Multi-Function Spoiler L3; R3; L4 R4; Autopilot2; Right Aileron indication; Auto throttle; Speed brake; FMS2). Flight crew decided that the best course of action was to [request priority handling]. Captain briefed the flight attendants. Pax briefed by Captain; FA (Flight Attendants) and instructed to brace upon landing. Aircraft landed safely and has deplaned. It was a very good CRM from all crew. During the decent and approach phase Captain searched for unfactored landing distance in the TLR (Takeoff/Landing Report) for the temperature and specific runway for XXR at ZZZ and aircraft Gross Landing Weight of 70;000 lb was 5;000 ft. and added 78% on the landing distance according to QRH; came out of 8;900 ft. of runway required. ZZZ Runway XXR [had sufficient length]. His decision to [request priority handling] was based upon the landing distance required and the amount of usable runway. After Captain [requested priority handling]; ATC instructed to descend to 12;000 ft. Since speed brakes was inoperative flight crew requested a shallower descend into ZZZ area maintaining a rate of descent of 1;000 ft. per minute until 10;000 ft. Captain changed AP source to the left side; LNAV mode was still operative and maintained during the STAR. The aircraft was vectored by ATC until intercepting final approach course and once visual with the field ATC cleared for visual approach. On short final EICAS populated 'Brakes Fault' advisory message and the Autobrake failed upon landing. Captain performed the landing touching the runway at the 500 ft. mark and exited the runway XXR at XY intersection. Aircraft proceeded to the gate normally where the passengers deplaned.The recurrent training provided by the company to the whole crew came to be very effective for the compliance of the procedures. Training department should continue emphasizing emergency scenario for flight crew and flight attendants during their annual training.


Second narrative: We were cruising at FL330 and about 150 nm from our TOD (Top of Descent); when we received multiple failure messages stating AVNX MAU3 FAIL; SPOILER FAULT; ADS3 FAIL; FMS2 FAIL and SPDBRK FAIL. My Captain was the pilot monitoring and so I asked him to run the QRH for those messages stated. We follow the procedures from the QRH and during the reading of the checklist; it tells us that because of these faults; we need to increase our landing distance by 1.78. We did some performance calculations and our results puts us very close to just making it to land safely and not running out of runway. The Captain and I decided that the best course of action was to [request priority handling]. Captain briefed the flight attendants; and also briefed the passengers and instructed to brace upon landing. Since we [requested priority handling]; ATC allowed us to not follow the restrictions for the arrival that we had in our flight plan. The captain took the flight controls eventually and I became the pilot monitoring. Aircraft landed safely; and we were able to get to the gate and deplane. Passengers were very grateful to all of us crew and told us we did a great job in bringing them to the ground safe.It was very good CRM from all crewmembers; and our recent recurrent training for all flight crew and flight attendants was very effective for this situation.


Synopsis: ERJ175 flight crew reported multiple EICAS failure messages while in cruise.