Air carrier flight crew reported receiving a low altitude alert issued by ATC during departure.

Date: 2024-10 · Aircraft: A320 · Phase: climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

Air carrier flight crew reported receiving a low altitude alert issued by ATC during departure.

Narrative

During pre-departure setup; it was noted on the ATIS that the airport was departing Runway XX. Runway XY was loaded into the FMCG as the departure runway by the FO. Takeoff data was sent for Runway XX and loaded into the FMGC. The oversight was not discovered during FMGC verification or the Before Takeoff Checklist and therefore went uncorrected. After an uneventful taxi to Runway XX; the aircraft was issued a takeoff clearance; departed Runway XX; and instructed to contact ZZZ departure. During this time; the flight director commanded a left turn which was followed by the pilot-flying. Referencing the SID chart for cleared procedure; it was confirmed that the correct procedure was a right turn to a heading of 210 after takeoff. Before correction could be initiated; ZZZ departure immediately announced a 'low altitude alert' and directed an 'immediate turn to a 180 heading' with further climbs and turns northbound. ATC instruction was complied with and the crew was later handed off to ZZZ center without further incident. The crew was also directed to contact ZZZ approach on a provided phone number and warned about a 'possible pilot deviation'.After reaching cruise altitude; the event was debriefed. It was at this time that the crew realized the cause for the incorrect flight director guidance was likely the improper runway loaded into the FMGC. This was not confirmed; however; as the FMGC had already removed that information from the flight plan.

Second reporter narrative

It was the FO's leg; so I asked him to build the FMGC. Active departure Runway XX; FO programmed Runway XY (which was our landing runway a few minutes earlier). I did not detect the error in my FMGC review (I checked the departure heading of 210°; but missed the incorrect runway). Also; in the Before Takeoff Checklist; both the FO and I missed the runway programming error. Note; the FO requested and programed the correct runway data for Runway XX. After takeoff; the FO made a left turn; in accordance with flight director guidance. I was confused about the left turn guidance did not say anything to fix the error. Almost immediately ZZZ [TRACON] commanded an immediate turn to heading 180°; then subsequent right turns to north.

More incidents for this aircraft family →

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