B757 flight crew reported a track deviation occurred on the RNAV (rnp) Z rwy 16R approach to den. Re...

Narrative:

We initially briefed and set up for the ILS 16R approach. We were later told to expect the RNAV (rnp) Z runway 16R approach. We quickly briefed the approach; to include a review of the RNAV (rnp) approach briefing guide in the QRH. However; the entire guide was not completed due to time constraints. We were cleared for the approach. We received an alt hold FMA prior to clfff; and reset the MCP altitude. We crossed clfff at 11000 [ft] and 210 knots. The autopilot remained engaged. The fmas showed LNAV and VNAV path; but the aircraft did not start to descend. While trying to figure out the problem; cepee intersection quickly followed and the airplane did not start a turn. Shortly thereafter ATC said he noticed we were not on the RNAV approach and gave us vectors to the visual approach. We both made another note of the FMA status-LNAV and VNAV path. Subsequent approach and landing were uneventful. A few items to point out: I am a new captain on this aircraft-just finished consolidation the day prior. This is the first RNAV approach I have conducted since training. Of course; I am still on high minimums. The first officer had just been involved with an emergency procedure 6 hours prior to this flight; on a different leg with a different captain. We believe if ATC would have given us more advanced notice of the anticipated RNAV approach expectation; we would not have been so rushed. In this case though; we're not sure that would have prevented the issue. The RNAV approach is conducted so rarely that all ATC facilities could help the pilot group greatly; as there is much more to accomplish and lengthy briefings which need to take place. We did notice; as we debriefed the flight; that the 'VOR/DME navigation-off' step in the briefing guide was missed. Again; we're not sure if this was the cause of the issue. Overall; safety was never in doubt; it was a clear night; and no traffic nearby. It was a good learning experience; and if we were to do it all over again; we would probably ask for vectors for the visual or ILS approach; and as a last resort; holding to have more time to review the entire RNAV briefing guide.

Original NASA ASRS Text

Title: B757 flight crew reported a track deviation occurred on the RNAV (RNP) Z Rwy 16R approach to DEN. Reporters cited a late change to the clearance as contributing.

Narrative: We initially briefed and set up for the ILS 16R Approach. We were later told to expect the RNAV (RNP) Z RWY 16R Approach. We quickly briefed the approach; to include a review of the RNAV (RNP) approach briefing guide in the QRH. However; the entire guide was not completed due to time constraints. We were cleared for the approach. We received an Alt Hold FMA prior to CLFFF; and reset the MCP altitude. We crossed CLFFF at 11000 [ft] and 210 knots. The autopilot remained engaged. The FMAs showed LNAV and VNAV PATH; but the aircraft did not start to descend. While trying to figure out the problem; CEPEE intersection quickly followed and the airplane did not start a turn. Shortly thereafter ATC said he noticed we were not on the RNAV approach and gave us vectors to the visual approach. We both made another note of the FMA status-LNAV and VNAV PATH. Subsequent approach and landing were uneventful. A few items to point out: I am a new captain on this aircraft-just finished consolidation the day prior. This is the first RNAV approach I have conducted since training. Of course; I am still on high minimums. The First Officer had just been involved with an emergency procedure 6 hours prior to this flight; on a different leg with a different Captain. We believe if ATC would have given us more advanced notice of the anticipated RNAV approach expectation; we would not have been so rushed. In this case though; we're not sure that would have prevented the issue. The RNAV approach is conducted so rarely that all ATC facilities could help the pilot group greatly; as there is much more to accomplish and lengthy briefings which need to take place. We did notice; as we debriefed the flight; that the 'VOR/DME NAV-OFF' step in the briefing guide was missed. Again; we're not sure if this was the cause of the issue. Overall; safety was never in doubt; it was a clear night; and no traffic nearby. It was a good learning experience; and if we were to do it all over again; we would probably ask for vectors for the visual or ILS approach; and as a last resort; holding to have more time to review the entire RNAV briefing guide.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1561556
Time
Date	201807
Local Time Of Day	1801-2400
Place
Locale Reference	DEN.Airport
State Reference	CO
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument
Experience	Flight Crew Total 3739.45 Flight Crew Type 112.10
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 180 Flight Crew Total 3789.12 Flight Crew Type 363.52
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

B757 flight crew reported a track deviation occurred on the RNAV (rnp) Z rwy 16R approach to den. Reporters cited a late change to the clearance as contributing.