Narrative:

Aircraft was parked at iab (gate). ATIS copied by first officer (in my absence) indicated departure on runway 14. Accuload (weight and balance) sheet, delivered to cockpit seconds before push, indicated runway 14 also. As we got our taxi clearance, I was expecting to hear '...to runway 14.' instead, controller gave us runway 26 (which I missed). I had briefed first officer to back me up on all taxi clrncs by writing them down and also having his taxi chart out, since while taxiing both of my hands, as well as feet, are busy. He complied, however, he had interrupted our routine by starting to run the taxi checklist before I called for it and before the taxi clearance was 100 percent understood. As the aircraft left the 'north ramp connector' at nk, I started a slight turn to the left (as if going towards runway 14) and asked if we were to taxi via 'nb' or 'na.' the first officer corrected my mistake regarding which runway before clarifying that I should taxi towards runway 26. However, by this time we had gotten so preoccupied with correcting the major mistake that we both forgot which taxiway to taxi on (nb or na) until ground called and asked 'who was that aircraft on nb -- is that XXX?' to which we answered yes. Ground said just continue and did not make a major issue of it. I have more to say about this problem than will fit on this 1 sheet. Please contact me at your earliest convenience for additional details and my input as to possible causes and corrections. Callback conversation with reporter revealed the following information: callback was accomplished at reporter's request. His comments were pertinent and valid regarding taxi instructions. The present lettering system on txwys, though no doubt is supposed to eliminate confusion, in fact, adds to confusion. As an example, if the controller said taxi via the inner taxiway, it is easily seen and understood, whereas taxi via nb to np requires head down map reading and the captain can't be searching out the route. Another complaint reporter vented -- when cleared to follow some other aircraft when the other aircraft is behind him. If controller terminology included a few more details or more positive instructions like, 'X hold short of the next taxiway, let Y pass by and then follow him' would be clearer and better procedure than instructions to just follow without any other details. Reporter believes the term 'follow' should not be used unless the other aircraft is in front already. Another item reporter believes needs improvement is more information from ATC for flight crew planning. Ie, an assigned airspeed for an intercept to an approach the controller should provide more information on his plan -- will he plan you to intercept, fly through the final and when can you slow down. All those are valid inputs for better communication between pilots and controllers.

Google
 

Original NASA ASRS Text

Title: ATIS AND FLT PAPERS SHOWED RWY IN USE AS RWY 14, SO FLC HAD A MINDSET THAT RWY 14 WAS WHERE THEY WERE GOING. BUT, THEN GND CTLR CLRED THEM TO RWY 26. RPTR WAS NOT CLR ON THE TAXI INSTRUCTIONS JUST AS THE FO STARTED THE TAXI CHKLIST. CONSEQUENTLY, RPTR TURNED THE WRONG WAY ON A TXWY, GND CTLR CALLED AND PROVIDED NEW DIRECTIONS.

Narrative: ACFT WAS PARKED AT IAB (GATE). ATIS COPIED BY FO (IN MY ABSENCE) INDICATED DEP ON RWY 14. ACCULOAD (WT AND BAL) SHEET, DELIVERED TO COCKPIT SECONDS BEFORE PUSH, INDICATED RWY 14 ALSO. AS WE GOT OUR TAXI CLRNC, I WAS EXPECTING TO HEAR '...TO RWY 14.' INSTEAD, CTLR GAVE US RWY 26 (WHICH I MISSED). I HAD BRIEFED FO TO BACK ME UP ON ALL TAXI CLRNCS BY WRITING THEM DOWN AND ALSO HAVING HIS TAXI CHART OUT, SINCE WHILE TAXIING BOTH OF MY HANDS, AS WELL AS FEET, ARE BUSY. HE COMPLIED, HOWEVER, HE HAD INTERRUPTED OUR ROUTINE BY STARTING TO RUN THE TAXI CHKLIST BEFORE I CALLED FOR IT AND BEFORE THE TAXI CLRNC WAS 100 PERCENT UNDERSTOOD. AS THE ACFT LEFT THE 'N RAMP CONNECTOR' AT NK, I STARTED A SLIGHT TURN TO THE L (AS IF GOING TOWARDS RWY 14) AND ASKED IF WE WERE TO TAXI VIA 'NB' OR 'NA.' THE FO CORRECTED MY MISTAKE REGARDING WHICH RWY BEFORE CLARIFYING THAT I SHOULD TAXI TOWARDS RWY 26. HOWEVER, BY THIS TIME WE HAD GOTTEN SO PREOCCUPIED WITH CORRECTING THE MAJOR MISTAKE THAT WE BOTH FORGOT WHICH TXWY TO TAXI ON (NB OR NA) UNTIL GND CALLED AND ASKED 'WHO WAS THAT ACFT ON NB -- IS THAT XXX?' TO WHICH WE ANSWERED YES. GND SAID JUST CONTINUE AND DID NOT MAKE A MAJOR ISSUE OF IT. I HAVE MORE TO SAY ABOUT THIS PROB THAN WILL FIT ON THIS 1 SHEET. PLEASE CONTACT ME AT YOUR EARLIEST CONVENIENCE FOR ADDITIONAL DETAILS AND MY INPUT AS TO POSSIBLE CAUSES AND CORRECTIONS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CALLBACK WAS ACCOMPLISHED AT RPTR'S REQUEST. HIS COMMENTS WERE PERTINENT AND VALID REGARDING TAXI INSTRUCTIONS. THE PRESENT LETTERING SYS ON TXWYS, THOUGH NO DOUBT IS SUPPOSED TO ELIMINATE CONFUSION, IN FACT, ADDS TO CONFUSION. AS AN EXAMPLE, IF THE CTLR SAID TAXI VIA THE INNER TXWY, IT IS EASILY SEEN AND UNDERSTOOD, WHEREAS TAXI VIA NB TO NP REQUIRES HEAD DOWN MAP READING AND THE CAPT CAN'T BE SEARCHING OUT THE RTE. ANOTHER COMPLAINT RPTR VENTED -- WHEN CLRED TO FOLLOW SOME OTHER ACFT WHEN THE OTHER ACFT IS BEHIND HIM. IF CTLR TERMINOLOGY INCLUDED A FEW MORE DETAILS OR MORE POSITIVE INSTRUCTIONS LIKE, 'X HOLD SHORT OF THE NEXT TXWY, LET Y PASS BY AND THEN FOLLOW HIM' WOULD BE CLEARER AND BETTER PROC THAN INSTRUCTIONS TO JUST FOLLOW WITHOUT ANY OTHER DETAILS. RPTR BELIEVES THE TERM 'FOLLOW' SHOULD NOT BE USED UNLESS THE OTHER ACFT IS IN FRONT ALREADY. ANOTHER ITEM RPTR BELIEVES NEEDS IMPROVEMENT IS MORE INFO FROM ATC FOR FLC PLANNING. IE, AN ASSIGNED AIRSPD FOR AN INTERCEPT TO AN APCH THE CTLR SHOULD PROVIDE MORE INFO ON HIS PLAN -- WILL HE PLAN YOU TO INTERCEPT, FLY THROUGH THE FINAL AND WHEN CAN YOU SLOW DOWN. ALL THOSE ARE VALID INPUTS FOR BETTER COM BTWN PLTS AND CTLRS.

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.