A B767 crew failed to update a non-pegasus equipped FMC before takeoff with the newly assigned runwa...

Narrative:

After a 3-hour delay at the gate we were given a clearance to taxi to the runway. After leaving the ramp; ground control offered us runway 18L. We accepted the new runway and I started to make the required changes in the FMS so that we would have the proper runway and departure loaded. We stopped at the hold short line 'set the brakes' and reviewed the changes to the departure and verified the proper runway was on the takeoff performance page and route pages. Back at the gate I had put in the position page the coordinates for our expected runway; to be ready for a quick align that I figured would be required due to our delay at the gate. When we did our quick align we failed to notice that I did not change the position page to the newly assigned runway. After departure I requested LNAV at 400 ft the command bars directed a right turn that I thought was excessive but the navigation display did show as correct. As soon as I made the turn to intercept the course; departure control gave us a left turn to 090 degree thus removing us from the departure; ie; we are now receiving vectors. Due to the late hour traffic was at a minimum. I do not believe we caused any traffic conflicts. It was later in the flight that I remembered not changing the quick-align coordinates.

Original NASA ASRS Text

Title: A B767 crew failed to update a non-Pegasus equipped FMC before takeoff with the newly assigned runway. After takeoff they deviated from the assigned SID's track.

Narrative: After a 3-hour delay at the gate we were given a clearance to taxi to the runway. After leaving the ramp; Ground Control offered us Runway 18L. We accepted the new runway and I started to make the required changes in the FMS so that we would have the proper runway and departure loaded. We stopped at the hold short line 'set the brakes' and reviewed the changes to the departure and verified the proper runway was on the Takeoff Performance page and RTE pages. Back at the gate I had put in the POS page the coordinates for our expected Runway; to be ready for a quick align that I figured would be required due to our delay at the gate. When we did our quick align we failed to notice that I did not change the POS page to the newly assigned runway. After departure I requested LNAV at 400 FT the command bars directed a right turn that I thought was excessive but the NAV display did show as correct. As soon as I made the turn to intercept the course; Departure Control gave us a left turn to 090 degree thus removing us from the departure; ie; we are now receiving vectors. Due to the late hour traffic was at a minimum. I do not believe we caused any traffic conflicts. It was later in the flight that I remembered not changing the quick-align coordinates.

Data retrieved from NASA's ASRS site as of April 2012 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	840168
Time
Date	200906
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Vectors SID ZZZ
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Flying First Officer
Person 2
Function	Captain Pilot Not Flying
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A B767 crew failed to update a non-pegasus equipped FMC before takeoff with the newly assigned runway. After takeoff they deviated from the assigned SID's track.