Narrative:

Missed RNAV departure. Clearance was for CHEZZ2 RNAV departure, which neither crew member had flown before. Initially the departure for runway 8 was loaded which would have had the aircraft proceed to primy and then chezz. However, the assigned runway was runway 7L which incorporates a departure to zilla and then chezz. Both departures have a turn to close (I think that's the name) although no heading is depicted for this turn. The crew realized while taxiing into position that runway 8 was still loaded into the gfms. We changed this in position and were shortly after cleared for takeoff. Navigation was selected at 400 ft and the autoplt was engaged at 500 ft. The aircraft tracked navigation but after chezz apparently started heading for bayta instead of making the right turn first to close. All of this occurred during acceleration and cleanup and also very quickly. I believe it's only 2.2 mi from zilla to chezz. As I said, neither one of us had flown this departure before so, even though we had reviewed the departure at the gate, the post takeoff environment was too busy for us to catch the tracking error. Our indication that there was a navigation problem was a query from ATC asking us if we had been cleared directly to bayta. It took a min or so of reexamining the chart to figure out why he was asking and see that we had missed the right turn after chezz. He said that there was no real problem (there was no conflicting departure traffic from the north runway) and cleared us directly to bayta. To my memory, the correct departure was displayed on the navigation display and I'm still not sure why the correct departure path wasn't flown, although it seems obvious that there was a programming error that I didn't catch. A few things might have prevented all this from happening. First off, entering the runway 7L departure over zilla first would have helped. The tps gave runway 8 as the first runway expected and that was loaded even though I knew that we usually depart from runway 7L. Second, it would have been better to catch the change before being cleared into position. Even though the departure was reprogrammed to runway 7L, we made a data entry error somewhere. I suppose we could have taxied clear of the runway to reprogram and not been somewhat rushed, but we thought we had made the correct change in the FMS. Also, for a non RNAV SID, headings from all of the fixes are depicted. On the CHEZZ2 departure there is no advisory heading listed on the chart after chezz, only a direction arrow to close and then a continuation of the route to bayta. I think that if a heading had been depicted, it would have been an additional aid in the pre-takeoff brief to remind us to look for the right turn after chezz. As I stated earlier, neither one of us had flown this departure before (it was actually only my second ever RNAV departure) and things occur quite rapidly in the immediate after takeoff flow. ATC indicated that there was no problem (I explained the probable programming error with the runway change) and happily wished us on our way.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD80 CREW HAD A TRACK DEV DEPARTING PHX ON AN RNAV DEP. THE ACFT TURNED TOWARD A FIX NOT INTENDED BY THE CREW. THE ACFT IS EQUIPPED WITH AN AFTER MARKET FMS, AND HAS NO NAV DISPLAY.

Narrative: MISSED RNAV DEP. CLRNC WAS FOR CHEZZ2 RNAV DEP, WHICH NEITHER CREW MEMBER HAD FLOWN BEFORE. INITIALLY THE DEP FOR RWY 8 WAS LOADED WHICH WOULD HAVE HAD THE ACFT PROCEED TO PRIMY AND THEN CHEZZ. HOWEVER, THE ASSIGNED RWY WAS RWY 7L WHICH INCORPORATES A DEP TO ZILLA AND THEN CHEZZ. BOTH DEPS HAVE A TURN TO CLOSE (I THINK THAT'S THE NAME) ALTHOUGH NO HEADING IS DEPICTED FOR THIS TURN. THE CREW REALIZED WHILE TAXIING INTO POS THAT RWY 8 WAS STILL LOADED INTO THE GFMS. WE CHANGED THIS IN POS AND WERE SHORTLY AFTER CLRED FOR TKOF. NAV WAS SELECTED AT 400 FT AND THE AUTOPLT WAS ENGAGED AT 500 FT. THE ACFT TRACKED NAV BUT AFTER CHEZZ APPARENTLY STARTED HEADING FOR BAYTA INSTEAD OF MAKING THE R TURN FIRST TO CLOSE. ALL OF THIS OCCURRED DURING ACCELERATION AND CLEANUP AND ALSO VERY QUICKLY. I BELIEVE IT'S ONLY 2.2 MI FROM ZILLA TO CHEZZ. AS I SAID, NEITHER ONE OF US HAD FLOWN THIS DEP BEFORE SO, EVEN THOUGH WE HAD REVIEWED THE DEP AT THE GATE, THE POST TKOF ENVIRONMENT WAS TOO BUSY FOR US TO CATCH THE TRACKING ERROR. OUR INDICATION THAT THERE WAS A NAV PROB WAS A QUERY FROM ATC ASKING US IF WE HAD BEEN CLRED DIRECTLY TO BAYTA. IT TOOK A MIN OR SO OF REEXAMINING THE CHART TO FIGURE OUT WHY HE WAS ASKING AND SEE THAT WE HAD MISSED THE R TURN AFTER CHEZZ. HE SAID THAT THERE WAS NO REAL PROB (THERE WAS NO CONFLICTING DEP TFC FROM THE N RWY) AND CLRED US DIRECTLY TO BAYTA. TO MY MEMORY, THE CORRECT DEP WAS DISPLAYED ON THE NAV DISPLAY AND I'M STILL NOT SURE WHY THE CORRECT DEP PATH WASN'T FLOWN, ALTHOUGH IT SEEMS OBVIOUS THAT THERE WAS A PROGRAMMING ERROR THAT I DIDN'T CATCH. A FEW THINGS MIGHT HAVE PREVENTED ALL THIS FROM HAPPENING. FIRST OFF, ENTERING THE RWY 7L DEP OVER ZILLA FIRST WOULD HAVE HELPED. THE TPS GAVE RWY 8 AS THE FIRST RWY EXPECTED AND THAT WAS LOADED EVEN THOUGH I KNEW THAT WE USUALLY DEPART FROM RWY 7L. SECOND, IT WOULD HAVE BEEN BETTER TO CATCH THE CHANGE BEFORE BEING CLRED INTO POS. EVEN THOUGH THE DEP WAS REPROGRAMMED TO RWY 7L, WE MADE A DATA ENTRY ERROR SOMEWHERE. I SUPPOSE WE COULD HAVE TAXIED CLR OF THE RWY TO REPROGRAM AND NOT BEEN SOMEWHAT RUSHED, BUT WE THOUGHT WE HAD MADE THE CORRECT CHANGE IN THE FMS. ALSO, FOR A NON RNAV SID, HEADINGS FROM ALL OF THE FIXES ARE DEPICTED. ON THE CHEZZ2 DEP THERE IS NO ADVISORY HEADING LISTED ON THE CHART AFTER CHEZZ, ONLY A DIRECTION ARROW TO CLOSE AND THEN A CONTINUATION OF THE RTE TO BAYTA. I THINK THAT IF A HEADING HAD BEEN DEPICTED, IT WOULD HAVE BEEN AN ADDITIONAL AID IN THE PRE-TKOF BRIEF TO REMIND US TO LOOK FOR THE R TURN AFTER CHEZZ. AS I STATED EARLIER, NEITHER ONE OF US HAD FLOWN THIS DEP BEFORE (IT WAS ACTUALLY ONLY MY SECOND EVER RNAV DEP) AND THINGS OCCUR QUITE RAPIDLY IN THE IMMEDIATE AFTER TKOF FLOW. ATC INDICATED THAT THERE WAS NO PROB (I EXPLAINED THE PROBABLE PROGRAMMING ERROR WITH THE RWY CHANGE) AND HAPPILY WISHED US ON OUR WAY.

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.