Date: 201510
Local time of day: 0601-1200
Location: ZZZ.Airport, CA
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: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon acceptance of aircraft the Captain noticed that the aircraft was undergoing maintenance for couple of weeks and it had just been released for our flight. A few maintenance uncertainties happened at power up at the gate; Captain called up MX Control about them and with the Maintenance person already being present and onboard (the one who signed and released the aircraft) they were all resolved.From the very beginning of flight down to Final Approach fix; the aircraft had no problem at all. We were cleared for visual approach to Runway XXL; with the request from tower controller to switch [to] visual Runway XXR. Since we already had our performance numbers for Runway XXR; and the ceiling and visibility was more than good; we accepted [clearance] to land on Runway XXR. Just [as] we put the gear down and I was asking for flap 5; a bunch of EICAS messages appeared and we lost Display Unit 1 & 4 together with MCDU 1 and Autothrottle. We checked the landing configuration; gear was down; flap was on 5; and aircraft was on speed and stable before 1000 feet AGL. We were on final approach segment; and had passed the FAF of Runway XXL. Therefore with all those malfunctions we decided to continue the approach and landed safely on Runway XXR. We vacated runway through high speed taxiway; and at that time Captain informed me that we lost the steering as well. We continued to vacate the runway by high speed taxiway using differential braking. Upon first contact with ground control I informed them that we need to hold there to run some checklists. We followed every required checklist; and upon completion Captain informed tower that we need to be towed to the gate. I talked to Ops and asked for tow truck. Captain informed flight attendants and passengers about the situation. We hold for about 15 minutes for tow truck and ground crews to perform the tow-in procedure. Before that; according to procedure we started the APU and shutdown both engines. We towed in to the gate and all passengers disembarked the aircraft safe and sound without ever feeling anything. We completed all of our checklists and the Captain wrote up the indexed EICAS message; (which appeared to be the root-cause of problem). Fail message has been written in Logbook; and aircraft handed over to maintenance which was present at the gate. We gave them verbal detail of problems in addition to what has been written in the logbook.To my own judgment; we; as flight crew; did whatever was necessary to start and complete a safe flight; and whatever was required to be handled according to procedures. All other colleagues; including the flight attendants; ground crews during the tow-in; Ops Controller in ZZZ; and maintenance personnel who accepted the aircraft after completion of flight did their job as best as they could; and would like to thank them all; that without their help a seamless passenger experience was impossible.  Mechanical Irregularities happen in any aircraft or any airline. I don't know if our experience was related to post heavy maintenance job or not; but if it was; it would be better to improve the Post Maintenance Quality Control procedures.




Synopsis: EMB-175 First Officer reported multiple system issues on short final that resulted in the flight being towed to the gate after landing.