Narrative:

All pre-departure checks were completed with route verification and briefing of SPAZZ3 RNAV SID off runway 08 at den. Given that it was a first flight of day; short taxi with low sun angle glare the taxi checklist was completed to the line while on the ramp. After ramp clearance; received printer message of change to runway 17R. First officer's performance check confirmed V speeds the same as runway 08 with a change to toga thrust and entered runway 17R in FMS. Upon contact with ground runway was changed to runway 17L. First officer requested and received ACARS takeoff data for runway 17L and entered new V speeds into performance page. I had first officer check for and review the special engine out procedure while I taxied; but failed to call for a new route verification and re-accomplishment of the taxi checklist. Called for below the line portion of taxi check and noted that runway 17R was still in FMS; first officer made the correction. Unfortunately having not switched from the 10-9 taxi chart on my ipad to the 10-3T RNAV SID chart to check initial course; waypoint and altitude against the FMS; navigation display and flight computer I missed my last chance to trap the error that was about to occur. Shortly after takeoff with autopilot engaged the aircraft initiated a left turn to the gisst waypoint. Gisst is part of the BRYCC3 RNAV SID not the SPAZZ3. Somehow with two runway changes the SPAZZ3 had dropped out of the FMGC and the BRYCC3 was present. Departure control asked us to confirm destination and assigned a southerly heading. First officer made the necessary programming corrections and the remainder of the flight continued normally.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight crew reported being assigned Runway 17L with the SPAZZ3 departure after first entering 17R in the flight computer. The departure is not checked after the runway change and somehow the BRYCC3 is the active departure at takeoff; resulting in a track deviation.

Narrative: All pre-departure checks were completed with route verification and briefing of SPAZZ3 RNAV SID off Runway 08 at DEN. Given that it was a first flight of day; short taxi with low sun angle glare the taxi checklist was completed to the line while on the ramp. After ramp clearance; received printer message of change to Runway 17R. First Officer's performance check confirmed V speeds the same as Runway 08 with a change to TOGA thrust and entered Runway 17R in FMS. Upon contact with Ground runway was changed to Runway 17L. First Officer requested and received ACARS takeoff data for Runway 17L and entered new V speeds into performance page. I had First Officer check for and review the special engine out procedure while I taxied; but failed to call for a new route verification and re-accomplishment of the taxi checklist. Called for below the line portion of taxi check and noted that Runway 17R was still in FMS; First Officer made the correction. Unfortunately having not switched from the 10-9 taxi chart on my iPad to the 10-3T RNAV SID chart to check initial course; waypoint and altitude against the FMS; navigation display and flight computer I missed my last chance to trap the error that was about to occur. Shortly after takeoff with autopilot engaged the aircraft initiated a left turn to the GISST waypoint. GISST is part of the BRYCC3 RNAV SID not the SPAZZ3. Somehow with two runway changes the SPAZZ3 had dropped out of the FMGC and the BRYCC3 was present. Departure control asked us to confirm destination and assigned a southerly heading. First Officer made the necessary programming corrections and the remainder of the flight continued normally.

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.