Narrative:

On takeoff, the FMS dumped the SID and sequenced to the first waypoint beyond the SID. First officer was PF and selected 'navigation' mode. The command bars indicated a turn to waypoint. This happened right at acceleration altitude (1500 ft AGL) and departure control. I checked in with departure, and we both were realizing something didn't look right. I looked at my departure SID to verify and then looked for any conflicting traffic. By the time we were attempting to correct the flight path, departure control started to query us, then proceeded to give us altitude and a vector to fly. Eventually gave a heading to join the departure SID and gave us a phone number to call. Looking back, I remember loading the flight plan with runway 8 for departure. We instead got runway 7R. My first officer changed the runway per the checklist. When he did so, he selected the arrival page and grabbed the ILS approach. This wasn't right, and then selected runway 7R on the departure page. Corrected runway and upon takeoff, the FMS sequenced past SID to a waypoint. This all took place in the first 3000 ft on initial departure. I called phx ATC and explained what had happened. They (supervisor) said 'no harm, no foul' and 'they weren't going to file any paperwork.' prevention in the future will be to reconfirm FMS prior to takeoff roll. It was the last round trip of a 5 day trip. Early morning show time. I will redouble my efforts to not let this ever happen again. Supplemental information from acn 572780: the controller noticed our heading, questioned it, and called traffic climbing off the north runway (behind and below our position). As I continued the right turn to the heading depicted on the departure procedure, the traffic came into view below and behind our position. So as not to cross in front of the traffic, I stopped the turn, still short of the desired heading. Our speculation as to the incorrect flight path depicted from the FMS was that inadvertently the sequence of fixes had skipped to the northerly hg of the departure procedure. Our guess is this occurred during the input of the actual departure runway (runway 7L) from the originally programmed runway (runway 8) during taxi. I will try to select or remain in heading mode until further past this critical point until I can verify the path depicted from the FMS is indeed the desired route for this segment of flight.

Related reports:

Google
 

Original NASA ASRS Text

Title: ON INITIAL CLBOUT ON CHEZZ SID FROM PHX, CL65 FLT CREW'S INCORRECT FMS INPUT AND RWY CHANGE CAUSES A HDG DEV, CAUGHT AND CORRECTED BY P50 DEP CTLR.

Narrative: ON TKOF, THE FMS DUMPED THE SID AND SEQUENCED TO THE FIRST WAYPOINT BEYOND THE SID. FO WAS PF AND SELECTED 'NAV' MODE. THE COMMAND BARS INDICATED A TURN TO WAYPOINT. THIS HAPPENED RIGHT AT ACCELERATION ALT (1500 FT AGL) AND DEP CTL. I CHKED IN WITH DEP, AND WE BOTH WERE REALIZING SOMETHING DIDN'T LOOK RIGHT. I LOOKED AT MY DEP SID TO VERIFY AND THEN LOOKED FOR ANY CONFLICTING TFC. BY THE TIME WE WERE ATTEMPTING TO CORRECT THE FLT PATH, DEP CTL STARTED TO QUERY US, THEN PROCEEDED TO GIVE US ALT AND A VECTOR TO FLY. EVENTUALLY GAVE A HDG TO JOIN THE DEP SID AND GAVE US A PHONE NUMBER TO CALL. LOOKING BACK, I REMEMBER LOADING THE FLT PLAN WITH RWY 8 FOR DEP. WE INSTEAD GOT RWY 7R. MY FO CHANGED THE RWY PER THE CHKLIST. WHEN HE DID SO, HE SELECTED THE ARR PAGE AND GRABBED THE ILS APCH. THIS WASN'T RIGHT, AND THEN SELECTED RWY 7R ON THE DEP PAGE. CORRECTED RWY AND UPON TKOF, THE FMS SEQUENCED PAST SID TO A WAYPOINT. THIS ALL TOOK PLACE IN THE FIRST 3000 FT ON INITIAL DEP. I CALLED PHX ATC AND EXPLAINED WHAT HAD HAPPENED. THEY (SUPVR) SAID 'NO HARM, NO FOUL' AND 'THEY WEREN'T GOING TO FILE ANY PAPERWORK.' PREVENTION IN THE FUTURE WILL BE TO RECONFIRM FMS PRIOR TO TKOF ROLL. IT WAS THE LAST ROUND TRIP OF A 5 DAY TRIP. EARLY MORNING SHOW TIME. I WILL REDOUBLE MY EFFORTS TO NOT LET THIS EVER HAPPEN AGAIN. SUPPLEMENTAL INFO FROM ACN 572780: THE CTLR NOTICED OUR HDG, QUESTIONED IT, AND CALLED TFC CLBING OFF THE N RWY (BEHIND AND BELOW OUR POS). AS I CONTINUED THE R TURN TO THE HDG DEPICTED ON THE DEP PROC, THE TFC CAME INTO VIEW BELOW AND BEHIND OUR POS. SO AS NOT TO CROSS IN FRONT OF THE TFC, I STOPPED THE TURN, STILL SHORT OF THE DESIRED HDG. OUR SPECULATION AS TO THE INCORRECT FLT PATH DEPICTED FROM THE FMS WAS THAT INADVERTENTLY THE SEQUENCE OF FIXES HAD SKIPPED TO THE NORTHERLY HG OF THE DEP PROC. OUR GUESS IS THIS OCCURRED DURING THE INPUT OF THE ACTUAL DEP RWY (RWY 7L) FROM THE ORIGINALLY PROGRAMMED RWY (RWY 8) DURING TAXI. I WILL TRY TO SELECT OR REMAIN IN HDG MODE UNTIL FURTHER PAST THIS CRITICAL POINT UNTIL I CAN VERIFY THE PATH DEPICTED FROM THE FMS IS INDEED THE DESIRED RTE FOR THIS SEGMENT OF FLT.

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.