B737-700
Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Flight Crew Last 90 Days 444
Human-Machine Interface; Situational Awareness
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Human Factors
On descent into ABQ we briefed both the RNAV (RNP) Z Runway 3 with a backup of the ILS 3. We verified the points; RNP availability forecast (RAF) and loaded the appropriate RNP value. We began the approach at TNTOE on LNAV/VNAV PATH. We proceeded to the next fix PLNET on the approach. When we overflew PLNET on the approach the aircraft flew directly to BILDE instead of doing the 7.3 DME ARC. Approach Control informed us that we were off course and gave us a vector and altitude. We complied and asked for vectors to fly the ILS 3; which we had previously briefed. The approach and landing were uneventful. We debriefed after landing but could not come a conclusion on why the aircraft flew directly to the point and why the 7.3 NM ARC was not flown. Possibly confirming in more detail that the ARC is confirmed on both DU display as well as confirming that it is on the CDU while briefing the approach.
[Report narrative contained no additional information.]
B737-700 flight crew reported a track deviation occurred on the RNAV (RNP) Runway 3 Approach into ABQ.