Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Electrical Distribution Relay
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
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
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While climbing through FL210 approximately with the FO (First Officer) operating as the PF (Pilot Flying) and autopilot 2 engaged; the aircraft experienced an abrupt yaw to the left; and the Captain's PFD; ND; and the upper ECAM screen momentarily went blank. The aircraft quickly recovered; and the blank screens returned to normal. Both the First Officer and I scanned the overhead panel and circuit breaker panels; and found nothing amiss. We also cycled through the systems pages on the ECAM display; and all was normal. Approximately two minutes later; the same thing happened; only the yaw was more abrupt; and the Captain's screens and upper ECAM display remained blank for several seconds. We then experienced the following ECAM's: ENG 1 EPR MODE FAULTNAV GPWS FAULTAUTO FLT RUDDER TRIM 1 FAULTBRAKES SYS 1 FAULTELEC GEN 1 FAULTELEC BCL 2 FAULTI directed the First Officer to fly the aircraft and communicate with ATC; and to ask to level the aircraft at FL240. Given the multiple malfunctions and our proximity to ZZZ; I consulted with the First Officer and decided that a return to ZZZ was in order. While the First Officer coordinated with ATC for our return to ZZZ; I started working through the displayed ECAM procedures; which resulted in taking generator 1 off line; and placing both engines in the N1 mode. We started the APU; and I coordinated with the flight attendants; made a PA announcement to the passengers; sent dispatch a brief ACARS message telling them that we were experiencing multiple issues and were returning to ZZZ; and asked for landing performance data. We completed an uneventful overweight landing back at ZZZ; and taxied back to the gate.


Second narrative: During the climb out heading west passing through FL210; airspeed 315 KIAS; autopilot and auto-thrust on; the aircraft made an uncommanded yaw to the left while simultaneously the Captain's side PFD; ND; and the E/WD screens momentarily went blank. The aircraft returned to stable flight conditions almost immediately; no ECAMs or other warnings were present; and all systems appeared to be operating normally; therefore the climb was continued. Approximately two minutes later climbing through FL240 there was a second uncommanded yaw to the left that was of greater magnitude than the first; causing the aircraft to also roll to the left; while again the Captain's side PFD; ND; and the E/WD screens went blank and flickered for several seconds. At this time the first of multiple ECAMs began to appear; which included ENG 1 EPR Mode Fault; NAV GPWS Fault; Auto Flt Rud Trim 1 Fault; Elec Gen 1 Fault; BCL Fault; and Brake Sys 1 Fault; along with several others. As I was the PF (Pilot Flying); and after briefly confirming with the Captain; I disconnected the Autopilot and Auto-thrust systems and initiated a level off; and after another quick discussion with the Captain; he began working the ECAMs while I continued to fly the aircraft and assume control of radio communications with ATC. I coordinated with ATC for a slight descent back down to maintain FL240; while I reduced thrust to slow the aircraft to 280 KIAS. While I was descending and slowing the aircraft (with Autopilot and Auto-thrust off); the aircraft again made several large; uncommanded yawing/roll movements to the left. With the Captain's concurrence; I [notified] Center and requested an immediate left turn and a heading vector back to ZZZ while also initiating a descent. There were many what I describe as 'cascading' ECAMs the Captain was working through at the time as it seemed that multiple systems were being affected simultaneously. One notable failure was the loss of GEN 1; so we elected to immediately start the APU in order to have a second generator available. The Captain continued to work through the list of ECAMs; confirming with me before shutting off or resetting any systems as directed by the ECAM while I maintained aircraft control and initiated a continuous descent and return. I coordinated for a visual approach to runway XX; as it was the longest runway for the winds; and I also requested emergency vehicles to be dispatched to the runway. The Captain meanwhile coordinated with the flight attendants; made an announcement to the passengers about our return; and sent an ACARS message to dispatch informing them of we had multiple system failures and requesting landing data. The Captain went through the overweight landing checklist as we were at still approximately 148;000 lbs. Approach reference speed was approximately 149 KIAS with full flaps. I maintained control of the aircraft and performed a visual approach backed up by the ILS followed by an uneventful landing using Max reverse thrust and minimal braking. However during rollout; the E/WD screen indicated that the #1 engine thrust reverser was not deployed; however I did not perceive any directional control problems while using reverse thrust; and only minimal braking was required to clear the runway. The Captain performed an uneventful taxi to the gate and once the aircraft was secured; the passengers were deplaned using normal procedures.


Synopsis: A320 flight crew reported numerous system malfunctions during climb and returned to departure airport.