Just prior to the sea olympia 7 arvad waypoint; ATC assigned ILS runway 16C so the pilot flying chan...

Narrative:

During descent on the olympia 7 just prior to the arvad waypoint; we were advised by approach to expect the 16C ILS approach. Up to this point; we had briefed the 16R ILS; since that was the runway in use in the most current ATIS. So; as pilot flying; at approximately three miles from arvad; I reprogrammed the approach in the FMC. I unexpectedly experienced a problem when selecting the 16C ILS. The FMC displayed not only the approach; but part of the arrival as well. Specifically; it displayed all the points on the OLY7 from arvad and beyond. I tried to select the next point beyond arvad; that being fourt; but I got an error message stating 'altitude restriction...'; and therefore; I could not execute the operation. So; thereafter; I line selected arvad from key L4 and used that to replace the current arvad at L1 (my fly to waypoint). As it turns out; I must have executed this operation very closely to actually passing over arvad; because thereafter; we continued on our northeasterly heading and flew right past the next turn point; fourt. Approach control noticed that we did not turn to heading 350 after fourt as directed and depicted on the chart. Approach control then gave us a vector to correct our ground track. The steering error did not cause any loss of separation with other aircraft. As well; the controller did not ask us to contact him afterward. Since we were close to the airfield and in a busy phase of flight; I should have asked the pilot not flying to reprogram the FMC with the newly assigned runway. As well; even if I was to reprogram the FMC myself; I should have followed the standard procedure and ensured that the pilot not flying agreed with the programming change prior to me executing the action. Including both pilots in the programming would increase the likelihood of noticing any programming errors.

Original NASA ASRS Text

Title: Just prior to the SEA OLYMPIA 7 ARVAD waypoint; ATC assigned ILS Runway 16C so the pilot flying changed the FMS runway from 16R and subsequently the track after ARVAD was dropped prompting ATC to issue a vector.

Narrative: During descent on the OLYMPIA 7 just prior to the ARVAD waypoint; we were advised by Approach to expect the 16C ILS approach. Up to this point; we had briefed the 16R ILS; since that was the runway in use in the most current ATIS. So; as pilot flying; at approximately three miles from ARVAD; I reprogrammed the approach in the FMC. I unexpectedly experienced a problem when selecting the 16C ILS. The FMC displayed not only the approach; but part of the arrival as well. Specifically; it displayed all the points on the OLY7 from ARVAD and beyond. I tried to select the next point beyond ARVAD; that being FOURT; but I got an error message stating 'Altitude Restriction...'; and therefore; I could not execute the operation. So; thereafter; I line selected ARVAD from key L4 and used that to replace the current ARVAD at L1 (my fly to waypoint). As it turns out; I must have executed this operation very closely to actually passing over ARVAD; because thereafter; we continued on our northeasterly heading and flew right past the next turn point; FOURT. Approach Control noticed that we did not turn to heading 350 after FOURT as directed and depicted on the chart. Approach Control then gave us a vector to correct our ground track. The steering error did not cause any loss of separation with other aircraft. As well; the Controller did not ask us to contact him afterward. Since we were close to the airfield and in a busy phase of flight; I should have asked the pilot not flying to reprogram the FMC with the newly assigned runway. As well; even if I was to reprogram the FMC myself; I should have followed the standard procedure and ensured that the pilot not flying agreed with the programming change prior to me executing the action. Including both pilots in the programming would increase the likelihood of noticing any programming errors.

Data retrieved from NASA's ASRS site as of July 2013 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	1047419
Time
Date	201211
Local Time Of Day	1801-2400
Place
Locale Reference	SEA.Airport
State Reference	WA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer
Experience	Flight Crew Last 90 Days 127
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Just prior to the sea olympia 7 arvad waypoint; ATC assigned ILS runway 16C so the pilot flying changed the FMS runway from 16R and subsequently the track after arvad was dropped prompting ATC to issue a vector.