A300 flight crew reported an airspeed indication and flap malfunction during initial climb out. Flight crew returned to departure airport; landed; and taxied to the gate.
Synopsis
A300 flight crew reported an airspeed indication and flap malfunction during initial climb out. Flight crew returned to departure airport; landed; and taxied to the gate.
Narrative
Flight XXXX from ZZZ-ZZZ1 departed with two MELS. The number 2 Flight Augmentation Computer (FAC) and the number 2 Slat/Flap Control Computer (SFCC) were both deferred. Appropriate MEL procedures were used and communicated prior to departure. The Captain was the pilot flying (PF) due to the MELS. After takeoff during the climb out the red spd lim" appeared on the Captain's Primary Flight Display (PFD) and the data for the speed tape disappeared. The IAS was indicating correctly on both Captain and First Officer's (FO's) side. We did not receive an ecam message for this indication. Takeoff configuration was 15/0. After slats retracted we received an ECAM FLAPS SYS 1 and 2 Fault/FLAPS STUCK. Since we didn't use the flaps on takeoff and they were already indicating 0 and the slats retracted normally; we decided to keep the aircraft in the clean configuration until the approach phase and proceeded to ZZZ. The Maintenance log revealed a history with this issue. The crew discussed this prior to departure. The FO took control of the Aircraft and radios while I ran the checklist items. En route to ZZZ we decided that we would have the possibility of landing flaps 15/0. We [requested priority handling] with ZZZ Center because the flight plan had us on the ZZZZZ arrival for Runway XX and we wanted XXC for a longer runway. ZZZ cleared us direct ZZZ for Runway XXC. On the approach to XXC we ran the ecam but the flaps were stuck at 0. Appropriate QRH procedures were followed. We Proceeded on a visual approach to XXC with the Captain as the PF with slats normal and flaps 0. There were no issues on landing and there were no indications from the crews that there were additional issues with the aircraft. We taxied to the gate. Cause: Maintenance issues after departure."
Second reporter narrative
Flight ABCD started out of ZZZ for ZZZ1 at XA:15 with two MEL's. MEL 27-XX-XX-XX: Slat/Flap Control Computer (SFCC) #2 inopMEL 22-XX-XX-XY: Flight Augmentation computer (FAC) #2 inopBoth MEL's were complied with on the operations side and discussed prior to the flight with the crew.The Captain was the pilot flying (PF) due to the MELS. After takeoff during the climb out the red spd lim" appeared on the Captain's Primary Flight Display (PFD) and the data for the speed tape disappeared. The IAS was indicating correctly on both Captain and First Officer's (FO's) side. We did not receive an ecam message for this indication. Takeoff configuration was 15/0. After slats retracted we received an ECAM FLAPS SYS 1 and 2 Fault/FLAPS STUCK. Since we didn't use the flaps on takeoff and they were already indicating 0 and the slats retracted normally; we decided to keep the aircraft in the clean configuration until the approach phase and proceeded to ZZZ.We had enough fuel to continue on considering a no flap landing using XXC to include provisions such as go arounds: we then [requested priority handling] to give the crew priority to XXC and any other assistance needed shall it arise. The crew then took the time enroute to study and comply with the QRH and go over all possible situations that could arise with a no flap or partial flap configuration. Landing was non-eventful and no damage was detected by fire and rescue. The crew was able to taxi on their own power to their gate.Cause: Flap failure"
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.