Narrative:

Ground cleared us to taxi to runway 18L; bridge. FMS was set up for the jaspa RNAV departure; runway 18L. Approaching taxiway Z; ground changed our clearance to; 'runway 17R; txwys west; eg; contact queue once your RNAV is set up.' changed the RNAV departure and runway in the FMS using company procedures. Contacted queue; read runway 17R from the route page; and trexx as the first waypoint on the legs page. Started right engine with associated electrical power change. Takeoff position; EFIS displayed correctly with runway 17R and trexx. At 400 ft preparing to engage navigation; EFIS displayed a magenta line from runway 18L to trexx; and the flight director was commanding a right turn to intercept this course. A quick check of the paper SID was made to confirm that trexx was the correct departure fix. When returning to view the departure on the EFIS; it now showed a magenta line from runway 18L to larnn; with a white dotted line from runway 17R to trexx. The first officer began a turn to the left to intercept the correct course while the captain pressed the illuminated 'execute' light. Departure then instructed us to make a 15 degree turn left turn. The rest of the departure was uneventful with radar vectors to jaspa.supplemental information from acn 639950: this airplane is one of those that with the #2 dfgc selected and push of navigation my side stays in heading select unless I go from rad to navigation; select navigation then go back to rad. When I selected navigation on dfgc; the information displayed on EFIS navigation display switched back to the west side departure which is runway 18L and larrn with a white dotted line off of runway 17R to trexx. The first officer noticed this and made a comment about navigation; I saw myself in heading select so I turned my head to switch from rad to navigation; re-engage navigation; and go back to rad. When I finished that's when I noticed the EFIS display being incorrect. The first officer was already working towards the proper ground track then ATC instructed us to turn left 15 degrees. Everything was displayed correctly before going down the runway. No exe light illuminated; proper runway and first fix. When we selected navigation it went bad. I don't know if the right engine generator coming online interrupted the actual execute.callback conversation with reporter acn 693949 revealed the following information: the first officer stated that on the initial part of the takeoff; his navigation display was showing trexx and the runway 17R departure track but the flight director was commanding a right turn vice the essentially straight ahead track indicated by the active route line. After he attempted to evaluate this contradiction with the departure plate he came back to the navigation display and saw that now the runway 18R track with larrn was the active route (shown in magenta) and the runway 17R track now was shown as dashed white line indicative of a secondary; un-executed route. It is likely that this switch was the result of some mcdu input from the PNF although they were unable to determine that with certitude. He expanded on the differences between this aircraft and the majority of the air carrier fleet in that a navigation/rad (FMS navigation/radio navigation) switch must be properly selected in order for RNAV functions to display although they can; apparently; be programmed in while in the rad mode. Reporter suggested that some combination of programming and inappropriate navigation/rad switch position might well have been the source of the problems. He advised that the air carrier training center suggested the use of the 5 mile range for RNAV takeoffs to ensure close tracking of the required track. His concern was that doing so removed the initial fix (in this case trexx) from the display and it was thus less obvious that the command bar indications were erroneous.

Google
 

Original NASA ASRS Text

Title: CLRED VIA THE JASPA RNAV SID FROM RWY 18L; MD80 RECEIVES A CHANGE TO RWY 17R WHICH IS PROGRAMMED INTO THE FMS BUT NOT EXECUTED ON BOTH PLTS' DISPLAYS. TRACK DEV RESULTS.

Narrative: GROUND CLRED US TO TAXI TO RWY 18L; BRIDGE. FMS WAS SET UP FOR THE JASPA RNAV DEP; RWY 18L. APCHING TXWY Z; GND CHANGED OUR CLRNC TO; 'RWY 17R; TXWYS W; EG; CONTACT QUEUE ONCE YOUR RNAV IS SET UP.' CHANGED THE RNAV DEP AND RWY IN THE FMS USING COMPANY PROCS. CONTACTED QUEUE; READ RWY 17R FROM THE RTE PAGE; AND TREXX AS THE FIRST WAYPOINT ON THE LEGS PAGE. STARTED R ENG WITH ASSOCIATED ELECTRICAL POWER CHANGE. TKOF POSITION; EFIS DISPLAYED CORRECTLY WITH RWY 17R AND TREXX. AT 400 FT PREPARING TO ENGAGE NAV; EFIS DISPLAYED A MAGENTA LINE FROM RWY 18L TO TREXX; AND THE FLT DIRECTOR WAS COMMANDING A R TURN TO INTERCEPT THIS COURSE. A QUICK CHK OF THE PAPER SID WAS MADE TO CONFIRM THAT TREXX WAS THE CORRECT DEP FIX. WHEN RETURNING TO VIEW THE DEP ON THE EFIS; IT NOW SHOWED A MAGENTA LINE FROM RWY 18L TO LARNN; WITH A WHITE DOTTED LINE FROM RWY 17R TO TREXX. THE FO BEGAN A TURN TO THE L TO INTERCEPT THE CORRECT COURSE WHILE THE CAPT PRESSED THE ILLUMINATED 'EXECUTE' LIGHT. DEP THEN INSTRUCTED US TO MAKE A 15 DEG TURN L TURN. THE REST OF THE DEP WAS UNEVENTFUL WITH RADAR VECTORS TO JASPA.SUPPLEMENTAL INFO FROM ACN 639950: THIS AIRPLANE IS ONE OF THOSE THAT WITH THE #2 DFGC SELECTED AND PUSH OF NAV MY SIDE STAYS IN HDG SELECT UNLESS I GO FROM RAD TO NAV; SELECT NAV THEN GO BACK TO RAD. WHEN I SELECTED NAV ON DFGC; THE INFO DISPLAYED ON EFIS NAV DISPLAY SWITCHED BACK TO THE W SIDE DEP WHICH IS RWY 18L AND LARRN WITH A WHITE DOTTED LINE OFF OF RWY 17R TO TREXX. THE FO NOTICED THIS AND MADE A COMMENT ABOUT NAV; I SAW MYSELF IN HDG SELECT SO I TURNED MY HEAD TO SWITCH FROM RAD TO NAV; RE-ENGAGE NAV; AND GO BACK TO RAD. WHEN I FINISHED THAT'S WHEN I NOTICED THE EFIS DISPLAY BEING INCORRECT. THE FO WAS ALREADY WORKING TOWARDS THE PROPER GND TRACK THEN ATC INSTRUCTED US TO TURN L 15 DEGS. EVERYTHING WAS DISPLAYED CORRECTLY BEFORE GOING DOWN THE RWY. NO EXE LIGHT ILLUMINATED; PROPER RWY AND FIRST FIX. WHEN WE SELECTED NAV IT WENT BAD. I DON'T KNOW IF THE R ENG GENERATOR COMING ONLINE INTERRUPTED THE ACTUAL EXECUTE.CALLBACK CONVERSATION WITH RPTR ACN 693949 REVEALED THE FOLLOWING INFO: THE FO STATED THAT ON THE INITIAL PART OF THE TKOF; HIS NAV DISPLAY WAS SHOWING TREXX AND THE RWY 17R DEP TRACK BUT THE FLT DIRECTOR WAS COMMANDING A R TURN VICE THE ESSENTIALLY STRAIGHT AHEAD TRACK INDICATED BY THE ACTIVE RTE LINE. AFTER HE ATTEMPTED TO EVALUATE THIS CONTRADICTION WITH THE DEP PLATE HE CAME BACK TO THE NAV DISPLAY AND SAW THAT NOW THE RWY 18R TRACK WITH LARRN WAS THE ACTIVE RTE (SHOWN IN MAGENTA) AND THE RWY 17R TRACK NOW WAS SHOWN AS DASHED WHITE LINE INDICATIVE OF A SECONDARY; UN-EXECUTED RTE. IT IS LIKELY THAT THIS SWITCH WAS THE RESULT OF SOME MCDU INPUT FROM THE PNF ALTHOUGH THEY WERE UNABLE TO DETERMINE THAT WITH CERTITUDE. HE EXPANDED ON THE DIFFERENCES BETWEEN THIS ACFT AND THE MAJORITY OF THE ACR FLEET IN THAT A NAV/RAD (FMS NAVIGATION/RADIO NAVIGATION) SWITCH MUST BE PROPERLY SELECTED IN ORDER FOR RNAV FUNCTIONS TO DISPLAY ALTHOUGH THEY CAN; APPARENTLY; BE PROGRAMMED IN WHILE IN THE RAD MODE. RPTR SUGGESTED THAT SOME COMBINATION OF PROGRAMMING AND INAPPROPRIATE NAV/RAD SWITCH POSITION MIGHT WELL HAVE BEEN THE SOURCE OF THE PROBLEMS. HE ADVISED THAT THE ACR TRAINING CTR SUGGESTED THE USE OF THE 5 MILE RANGE FOR RNAV TKOFS TO ENSURE CLOSE TRACKING OF THE REQUIRED TRACK. HIS CONCERN WAS THAT DOING SO REMOVED THE INITIAL FIX (IN THIS CASE TREXX) FROM THE DISPLAY AND IT WAS THUS LESS OBVIOUS THAT THE COMMAND BAR INDICATIONS WERE ERRONEOUS.

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