Date: 201709
Local time of day: 0001-0600
Location: PHX.Airport, AZ
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B PHX
ATC / advisory: Tower PHX
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Distraction; Communication Breakdown; Confusion
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I; the Captain; was occupied with a small cabin issue in the forward galley when the First Officer received the PDC clearance. Upon my return; we conducted the predeparture route verification. I; as the PM; read the clearance to the FO as he was the PF and entered the routing to the FMS. He verified the routing that I read to him including the LALUZ5 departure. Immediately after takeoff; PHX tower asked us to confirm a left turn while we were in a right turn. I immediately queried ATC and they stated that we were cleared the FTHLS5 departure which entailed a left hand turn. I told them that we thought we were to fly the LALUZ5. He cleared us to continue flying the LALUZ5. I looked at the PDC and it had a revised segment that I failed to see and the FO did not see it during the route verification. I queried PHX tower and TRACON and they stated that it was not a problem.I believe that there were several factors that caused this event. First; I was involved in a minor cabin issue that diverted me away from my flight deck duties and I failed to review the PDC before the route verification. Second; the flight was departing very early and with several irregularities during the previous 2 days on the trip; a small amount of fatigue may have been a factor. Lastly; the FO obviously did not closely follow the PDC printout while we were conducting the route verification.As a relatively new Captain and flying with highly competent First Officers; I let my guard down by failing to verify the clearance and routing myself before conducting the route verification.


Second narrative: Upon departure from PHX runway 26 the LALUZ5 RNAV departure was flown; but ATC had assigned the FTHLS5 RNAV departure in a revised segment on the PDC.At the gate approximately 40 minutes before departure; I had completed most of my prefight duties that I could up until that point. Normally; I wait until I get the PDC at about 30 minutes before departure before loading the flight plan into the FMS. This way; I load it based on what I see on the PDC; instead of what is on the filed flight plan; since they may differ. But this night; I decided to go ahead and load the FMS completely from the filed release instead of waiting to get the PDC. The reason was; I wanted to get ahead of the game and be fully ready as early as possible; since it was such a late/early departure (middle of the night). I had the feeling of just wanting to get stuff done instead of sitting there for another 10-15 minutes letting fatigue set in.The CA and I both were slightly unfamiliar with PHX late night procedures; and weren't exactly sure which runway we would get for takeoff. Runway 26 and Runway 25R were in use. The filed clearance was the LALUZ5 departure; which is a right (north) turn; and we were told to taxi to runway 26 (north side runway) which all made sense. The problem was; the PDC had a revised segment of the FTHLS5 departure (left/south turn) which doesn't exactly make sense for a departure off the north side runway.Upon receiving the PDC; I remember reviewing it and all I can think of is that I must have seen under the ***filed route*** portion what I expected to see (LALUZ5 departure); and did not read/notice the ***revised segment*** of the PDC that indicated the FTHLS5 departure. The CA and I did a full route verification; and I specifically remember him reading from the MCDU 'LALUZ5'. At that point I was reading off of the PDC paper under the (what I expected/heard) ***filed route*** instead of the ***revised segment*** portion. After I hear the CA read the name of the departure; I immediately go to the iPad to verify the fixes/altitudes/airspeeds on the departure as the CA reads them from the MCDU. Again; the CA was reading out the fixes from the wrong departure procedure; but it all seemed correct; because that is what I was expecting to hear.Upon departure; PHX tower asked if we had begun our LEFT turn. We had actually just begun our right turn. We immediately looked to the PDC clearance and noticed the error. We quickly consulted with ATC; admitted our mistake; and asked them what they would like us to do. They advised that we should just remain on the LALUZ5 departure. They actually indicated that if anyone had a problem with it; it would be the TRACON; and not them (the tower/departure). Upon checking in with departure; they too advised that we should just remain on the LALUZ5 departure as they had consulted with the TRACON and that's what they wanted us to do.


Synopsis: A321 flight crew reported they missed a revised segment of their predeparture clearance resulting in a track heading deviation.