B737-700 flight crew reported a track deviation occurred on the RNAV rnp 16R approach to smf when th...

Narrative:

While on the suutr 2 arrival; we requested the RNAV 16R rnp at least twice and were told to request with next controller while we were in close proximity to the smf airport. Just prior to the ovome intersection; we were cleared the RNAV rnp 16 right approach while in visual conditions. I had in the scratch pad as a 'preselected' fix to connect the approach segment. The name was zolov. I was anticipating and trying to plan ahead. I brought up the zolov fix to underneath the fikan fix to indicate the correct LNAV path for the RNAV approach. All of this was occurring while we received a traffic call; confirming we had the airport in sight and received a frequency change to tower. Unknown to me; this made the path and map show a course of direct to fikan from ovome; then fixan direct to zolov; versus an arching right course track. This made us high on approach; and tight with traffic on final. We asked for a s-turn; which tower said we could go thru final and come back; which I did with autopilot off/autothrottle off and configured for landing. Final flaps were configured above 1000 feet; and for a moment my descent below 1000 feet was approximately 1200 feet which I stated I was correcting the rate of descent. It would be beneficial to have a different name on the star after the intersection ovome other than the name fixan. Fixan is also indicated on the RNAV approach and it seemed to make sense to bring up the next point on the RNAV rnp 16R which was zolov. Hindsight; I should have brought up the fix named fixan on the approach segment and placed underneath ovome once we were cleared for the RNAV approach. A bit confusing with two names of the same on the STAR and the approach.

Original NASA ASRS Text

Title: B737-700 flight crew reported a track deviation occurred on the RNAV RNP 16R approach to SMF when the FMC was improperly programmed following a late clearance.

Narrative: While on the SUUTR 2 Arrival; we requested the RNAV 16R RNP at least twice and were told to request with next Controller while we were in close proximity to the SMF airport. Just prior to the OVOME intersection; we were cleared the RNAV RNP 16 R Approach while in visual conditions. I had in the scratch pad as a 'preselected' fix to connect the approach segment. The name was ZOLOV. I was anticipating and trying to plan ahead. I brought up the ZOLOV fix to underneath the FIKAN fix to indicate the correct LNAV PATH for the RNAV Approach. All of this was occurring while we received a traffic call; confirming we had the airport in sight and received a frequency change to Tower. Unknown to me; this made the path and map show a course of direct to FIKAN from OVOME; then FIXAN direct to ZOLOV; versus an arching right course track. This made us high on approach; and tight with traffic on final. We asked for a S-turn; which Tower said we could go thru final and come back; which I did with autopilot off/autothrottle off and configured for landing. Final flaps were configured above 1000 feet; and for a moment my descent below 1000 feet was approximately 1200 feet which I stated I was correcting the rate of descent. It would be beneficial to have a different name on the star after the intersection OVOME other than the name FIXAN. FIXAN is also indicated on the RNAV Approach and it seemed to make sense to bring up the next point on the RNAV RNP 16R which was ZOLOV. Hindsight; I should have brought up the fix named FIXAN on the approach segment and placed underneath OVOME once we were cleared for the RNAV Approach. A bit confusing with two names of the same on the STAR and the approach.

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	1591313
Time
Date	201811
Place
Locale Reference	SMF
State Reference	CA
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	STAR SUUTR TWO
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 449
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach

B737-700 flight crew reported a track deviation occurred on the RNAV rnp 16R approach to smf when the FMC was improperly programmed following a late clearance.