Narrative:

While taxiing out for takeoff at kpit we were told to taxi D, V, B runway 28R. My first officer read back the clearance, but I did not hear the clearance after D, V. I incorrectly started to taxi D and right on V, because kpit always has us taxi the same way for departure. This night however, the controller decided to have us use runway 28R, a runway I have never used for departure leaving kpit in the 2 1/2 yrs I have been flying to kpit. I didn't realize we were taxiing the wrong direction on V until we reached the end, but had already crossed runway 28C. Fortunately, runway 28C was not in use and ground allowed us to use runway 28L for departure without any further problems. I now know how easy it is to fall into a trap when you've done it one way every time before, and will be more diligent about looking at the whole taxi route before proceeding. Callback conversation with reporter revealed the following information: the first officer was just out of his initial operating experience training. He had difficulty copying and understanding the taxi clearance. The first two legs of the route were the same as the routine routing to another runway that was the usual and expected runway for departure. No effort was made to study the route using the airport chart since the reporter was familiar with the airport. The reporter was aware he was crossing a runway, but with a 'taxi to' clearance, he assumed it was okay, not realizing he was going the wrong direction. When advised, the ground controller was not concerned because of low traffic volume and no conflict was caused. Clearance was then revised to take off on the usual runway since that was the most practical after the error was made. The crew was eight hours into their duty day, but the reporter said that fatigue was not a major factor.

Related reports:

Google
 

Original NASA ASRS Text

Title: A DIFFERENT THAN USUAL RWY ASSIGNMENT WITH THE FIRST PART OF THE TAXI ROUTING THE SAME LEADS TO A WRONG TURN AND AN INADVERTENT RWY CROSSING WITHOUT CLRNC ON THE WAY TO THE USUAL RWY INSTEAD OF THE ASSIGNED ONE.

Narrative: WHILE TAXIING OUT FOR TAKEOFF AT KPIT WE WERE TOLD TO TAXI D, V, B RWY 28R. MY FO READ BACK THE CLRNC, BUT I DID NOT HEAR THE CLRNC AFTER D, V. I INCORRECTLY STARTED TO TAXI D AND R ON V, BECAUSE KPIT ALWAYS HAS US TAXI THE SAME WAY FOR DEP. THIS NIGHT HOWEVER, THE CTLR DECIDED TO HAVE US USE RWY 28R, A RWY I HAVE NEVER USED FOR DEP LEAVING KPIT IN THE 2 1/2 YRS I HAVE BEEN FLYING TO KPIT. I DIDN'T REALIZE WE WERE TAXIING THE WRONG DIRECTION ON V UNTIL WE REACHED THE END, BUT HAD ALREADY CROSSED RWY 28C. FORTUNATELY, RWY 28C WAS NOT IN USE AND GND ALLOWED US TO USE RWY 28L FOR DEP WITHOUT ANY FURTHER PROBS. I NOW KNOW HOW EASY IT IS TO FALL INTO A TRAP WHEN YOU'VE DONE IT ONE WAY EVERY TIME BEFORE, AND WILL BE MORE DILIGENT ABOUT LOOKING AT THE WHOLE TAXI ROUTE BEFORE PROCEEDING. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE FO WAS JUST OUT OF HIS INITIAL OPERATING EXPERIENCE TRAINING. HE HAD DIFFICULTY COPYING AND UNDERSTANDING THE TAXI CLRNC. THE FIRST TWO LEGS OF THE ROUTE WERE THE SAME AS THE ROUTINE ROUTING TO ANOTHER RWY THAT WAS THE USUAL AND EXPECTED RWY FOR DEP. NO EFFORT WAS MADE TO STUDY THE ROUTE USING THE ARPT CHART SINCE THE RPTR WAS FAMILIAR WITH THE ARPT. THE RPTR WAS AWARE HE WAS CROSSING A RWY, BUT WITH A 'TAXI TO' CLRNC, HE ASSUMED IT WAS OKAY, NOT REALIZING HE WAS GOING THE WRONG DIRECTION. WHEN ADVISED, THE GND CTLR WAS NOT CONCERNED BECAUSE OF LOW TFC VOLUME AND NO CONFLICT WAS CAUSED. CLRNC WAS THEN REVISED TO TAKE OFF ON THE USUAL RWY SINCE THAT WAS THE MOST PRACTICAL AFTER THE ERROR WAS MADE. THE CREW WAS EIGHT HOURS INTO THEIR DUTY DAY, BUT THE RPTR SAID THAT FATIGUE WAS NOT A MAJOR FACTOR.

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.