Narrative:

While climbing through FL210 approximately with the first officer (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: engine 1 EPR mode faultnav GPWS faultauto flight rudder trim 1 faultbrakes system 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.

Related reports:

Google
 

Original NASA ASRS Text

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

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.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.