After programming their las departure via the shead RNAV SID from runway 25R; the A320 flight crew i...

Attributes
ACN	915727
Time
Date	201010
Local Time Of Day	1201-1800
Place
Locale Reference	LAS.Airport
State Reference	NV
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying
Experience	Flight Crew Last 90 Days 210 Flight Crew Total 10000 Flight Crew Type 1548
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 240 Flight Crew Total 15000 Flight Crew Type 5000
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

During preflight while programming the box; we originally set 25R. Later; with an updated ATIS; we changed the runway to 1R. We verified the departure for the before start checklist; then again during the before to checklist. As first officer and pilot not flying; I verified during the FMGC check by double clutching 1L on the FMGC and read 'runway 1R; shead; oal transition'. During the takeoff roll; I visually verified 1R on the navigation dispaly. Shortly after takeoff the lateral command bar turned left; instead of waiting until the 2;681 ft bubble; which was displayed; which would have taken us into the strip. The captain ignored the command bars until 2;681; then started his left turn. Then; the next fix was rbell; instead of bessy. The box thought we were taking off from 25R. We told ATC that we were having navigation problems and flew an assigned heading of 210. A few moments later; after I manually inserted the correct fixes; we were given a turn direct shead. At no time were we more than 3 miles off course and passed between the two fixes; rbell and bessy.

Original NASA ASRS Text

Title: After programming their LAS departure via the SHEAD RNAV SID from Runway 25R; the A320 flight crew instead departed via Runway 1R. When 1R was entered into the FMGC the departure procedure failed to transition to the revised track.

Narrative: During preflight while programming the box; we originally set 25R. Later; with an updated ATIS; we changed the runway to 1R. We verified the departure for the Before Start checklist; then again during the Before TO checklist. As First Officer and pilot not flying; I verified during the FMGC check by double clutching 1L on the FMGC and read 'Runway 1R; Shead; OAL transition'. During the takeoff roll; I visually verified 1R on the Navigation Dispaly. Shortly after takeoff the lateral command bar turned left; instead of waiting until the 2;681 FT bubble; which was displayed; which would have taken us into the strip. The Captain ignored the command bars until 2;681; then started his left turn. Then; the next fix was RBELL; instead of BESSY. The box thought we were taking off from 25R. We told ATC that we were having navigation problems and flew an assigned heading of 210. A few moments later; after I manually inserted the correct fixes; we were given a turn direct SHEAD. At no time were we more than 3 miles off course and passed between the two fixes; RBELL and BESSY.

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.

After programming their las departure via the shead RNAV SID from runway 25R; the A320 flight crew instead departed via runway 1R. When 1R was entered into the FMGC the departure procedure failed to transition to the revised track.