Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Flight Crew Type 259
Human-Machine Interface; Situational Awareness; Workload
ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Human Factors; Procedure
We had originally planned and briefed the KIPPR5 Arrival and the ILS approach to Runway 16L into Denver. Our arrival was later changed to the ANCHR4. We then set up and briefed this arrival and the ILS to 35R; which was the expected approach based on the latest ATIS. When contacting Denver Approach; we were assigned the RNAV (RNP) Z to 35R. In the course of flying this approach; we were assigned several non-standard speeds which further increased our workload. Because of this; we did not notice that there was an extraneous vector leg after MSIMS which was a remnant of the ANCHR4. The plan view on our displays showed MSIMS and the radius to FRONZ; which appeared to be the active course. When passing MSIMS we did not make the turn onto the radius and instead continued straight ahead briefly. We noticed the deviation immediately and were about to contact Approach when they called us with vectors to a visual approach; since they had also observed that we were off of the planned course. We were vectored onto final approach for a visual to Runway 35R and landed without further incident.
B737 First Officer reported a track deviation occurred on the RNAV (RNP) Z Approach to 35R in DEN when the FMC was programmed improperly following a late clearance change.