A319 flight crew reported receiving ECAM messages for multiple aircraft system malfunctions after takeoff. Flight crew returned to departure airport and landed without incident.

Date: 2024-03 · Aircraft: A319 · Phase: climb

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-maintenance

Synopsis

A319 flight crew reported receiving ECAM messages for multiple aircraft system malfunctions after takeoff. Flight crew returned to departure airport and landed without incident.

Narrative

The event occurred on day four of a four day pairing. This was our second flight of three scheduled for the day. The fight originated in ZZZ and was to arrive in ZZZZ; then return back to ZZZ. The flight briefing and preflight were normal with the exception of a minor maintenance CIDS (cabin intercommunication data system) panel issue that was resolved by Maintenance before pushback from the gate. Engine start and taxi were normal. We departed on Runway XXL from [Taxiway] 1 into IFR conditions with the First Officer (FO) as Pilot Flying. Shortly after we got airborne; we got two ECAMs simultaneously ENG 2 REVERSER FAULT and ANTI ICE CAPT PITOT- (Icing conditions were not present). A few seconds later we got a FUEL INERTING SYS FAULT. The FO engaged Autopilot 2. I told the FO to continue to fly the airplane and to handle the radio communications with ATC and I would accomplish the ECAMs. I did all the steps of the ECAMs and then referred to the hard copy of the QRC to make sure nothing was missed. I briefed the FO and then stated ECAM Complete Screens normal. After completing the ECAMs; they continued to reappear on multiple occasions so I finally emergency cancelled them.We elected to continue with the flight. We leveled off at our cruise altitude of FL340 in clear conditions. After a few moments; the FO said that he was not getting correct indications for his airspeed. The aircraft was switching intermittently between Managed Speed and Selected Speed on its own. The FO did an excellent job flying the aircraft and prevented it from over speeding. In the meantime; I sent an ACARS to Dispatch requesting a radio call with Maintenance Control on the call as well. Dispatch; the FO and I; along with Maintenance Control decided the best course of action was to return to ZZZ vice continuing to ZZZZ.I took the radios back from the FO and told ZZZ Center we needed to return to ZZZ. I then briefed the Flight Attendants of our planned return and made an announcement to the passengers. ATC gave us vectors and a descent back to ZZZ. During the descent; the aircraft was not responding properly to heading inputs being made to FCU (flight control unit) by the FO with Autopilot 2 on. We switched to Autopilot 1 and the aircraft responded correctly. At this point; we [requested priority handling] with ZZZ Center. I gave the Flight Attendants a briefing; telling them not to prep the cabin.The FO briefed the approach and then flew a perfect ILS in actual IFR conditions to Runway X at ZZZ to a soft landing. We landed slightly overweight at 137.8 thousand pounds. As we taxiing clear of the runway; we got an additional ECAM of LG SYS DISAGREE. The taxi back to the gate was without further incident.

Second reporter narrative

Right after takeoff; 3 ECAMs; Captain pitot; #2 reverser fault; fuel inerting. Procedures accomplished for ECAMs. Strange symbols on FO (First Officer) attitude indicator. Aircraft accelerating past managed speed; opened selected airspeed to control-aircraft put itself back in managed speed- continued back and forth. Upon diverting back to ZZZ; aircraft would not take heading input- stayed in NAV until I turned the Autopilot off. Airspeed indications on final were fine but symbology was wrong. Landed uneventfully. After landing got a landing gear disagree ECAM.

More incidents for this aircraft family →

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