Narrative:

Departing out of las to slc. On our flight plan we were cleared via the las 1 departure. We did not receive a pre departure clearance as we normally do. I called clearance delivery and they issued the aaces 1 departure. During this process, we had a thrust management malfunction (at gate). We looked at the route pages and we saw the aaces fix and we thought we had the correct departure in the FMS. We were distraction by the maintenance malfunction. On departure, we asked for a heading and the controller indicated that we were cleared on the RNAV aaces 1. We complied with radar vectors and called las upon arrival in slc. Supplemental information from acn 559769: as captain, I looked down on legs page and saw aaces and milford in box but didn't realize first officer had not changed departure in FMS from las 1 departure to aaces RNAV 1 departure. At the gate, we discussed aligning the IRU's to the gate position, and also we would align the IRU's to QA1 position at the end of runway 25R in order to fly a more precise RNAV departure. At the same time the weight and balance and takeoff data arrived at the flight deck and the crew became immersed in an FMS failure which rendered the autothrottles inoperative. Communicating with the maintenance coordinator and the dispatcher. The departure discrepancy was not discovered until vegas departure failed to call us for vectors on departure. They told us to follow the aaces 1 departure. I said we were still on las 1 departure. Vectors were given and normal departure ensued.

Google
 

Original NASA ASRS Text

Title: B757 FLC FOLLOWED THE WRONG SID AFTER TKOF DUE TO NOT PROGRAMMING THE FMC WITH THE ACTUALLY ASSIGNED SID.

Narrative: DEPARTING OUT OF LAS TO SLC. ON OUR FLT PLAN WE WERE CLRED VIA THE LAS 1 DEP. WE DID NOT RECEIVE A PDC AS WE NORMALLY DO. I CALLED CLRNC DELIVERY AND THEY ISSUED THE AACES 1 DEP. DURING THIS PROCESS, WE HAD A THRUST MGMNT MALFUNCTION (AT GATE). WE LOOKED AT THE RTE PAGES AND WE SAW THE AACES FIX AND WE THOUGHT WE HAD THE CORRECT DEP IN THE FMS. WE WERE DISTR BY THE MAINT MALFUNCTION. ON DEP, WE ASKED FOR A HDG AND THE CTLR INDICATED THAT WE WERE CLRED ON THE RNAV AACES 1. WE COMPLIED WITH RADAR VECTORS AND CALLED LAS UPON ARR IN SLC. SUPPLEMENTAL INFO FROM ACN 559769: AS CAPT, I LOOKED DOWN ON LEGS PAGE AND SAW AACES AND MILFORD IN BOX BUT DIDN'T REALIZE FO HAD NOT CHANGED DEP IN FMS FROM LAS 1 DEP TO AACES RNAV 1 DEP. AT THE GATE, WE DISCUSSED ALIGNING THE IRU'S TO THE GATE POS, AND ALSO WE WOULD ALIGN THE IRU'S TO QA1 POS AT THE END OF RWY 25R IN ORDER TO FLY A MORE PRECISE RNAV DEP. AT THE SAME TIME THE WT AND BAL AND TKOF DATA ARRIVED AT THE FLT DECK AND THE CREW BECAME IMMERSED IN AN FMS FAILURE WHICH RENDERED THE AUTOTHROTTLES INOP. COMMUNICATING WITH THE MAINT COORDINATOR AND THE DISPATCHER. THE DEP DISCREPANCY WAS NOT DISCOVERED UNTIL VEGAS DEP FAILED TO CALL US FOR VECTORS ON DEP. THEY TOLD US TO FOLLOW THE AACES 1 DEP. I SAID WE WERE STILL ON LAS 1 DEP. VECTORS WERE GIVEN AND NORMAL DEP ENSUED.

Data retrieved from NASA's ASRS site as of July 2007 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.