Narrative:

First officer called for taxi with information. Ground replied taxi to runway 1. First officer read back taxi to runway 1 and I proceeded to taxi on 'a' taxiway across runway 14/32 to hold short of runway 1. Runway 14 was in use for departure and no conflict whatsoever occurred. I questioned the first officer on us using runway 1 and he called for the winds. Ground control's reply was 200 degrees at 13 KTS. We switch to tower and I (captain) said we can't use runway 1, because of the tailwind. He said that we were supposed to taxi to runway 19. I replied that we heard runway 1. We then received new instructions to taxi to runway 19 and departed without incident. Contributing factors were fatigue. We had been on duty since xa:00 local time and had not had time to eat any food all day due to maintenance delays at a previous outstation. Also related, the tower controller appeared to have been working all frequencys at the time and was distracted by clearance calls/readbacks and inbound traffic. Also, we were running behind being pushed by our ramp personnel to turn the aircraft quickly. I also thought that perhaps the wind had shifted and thus the runway in use switched. We did get the winds from ground and started our taxi to runway 1. We probably could have prevented the situation by questioning the use of runway 1 (our perception) earlier. There is also a possibility the controller let off on the microphone switch early or was blocked on the niner part of runway 19 (read as 'one niner'). This runway could be easily confused if the 'niner' part is blocked. Callback conversation with reporter revealed the following information: reporter stated that on reaching runway 01, they immediately realized they were at the incorrect runway. They were informed by the controller that a clearance to runway 19 had been issued.

Related reports:

Google
 

Original NASA ASRS Text

Title: SA340 CREW TAXIING FOR DEP AT CAK UNDERSTOOD AND READ BACK TAXI TO RWY 01 INSTEAD OF RWY 19.

Narrative: FO CALLED FOR TAXI WITH INFO. GND REPLIED TAXI TO RWY 1. FO READ BACK TAXI TO RWY 1 AND I PROCEEDED TO TAXI ON 'A' TXWY ACROSS RWY 14/32 TO HOLD SHORT OF RWY 1. RWY 14 WAS IN USE FOR DEP AND NO CONFLICT WHATSOEVER OCCURRED. I QUESTIONED THE FO ON US USING RWY 1 AND HE CALLED FOR THE WINDS. GND CTL'S REPLY WAS 200 DEGS AT 13 KTS. WE SWITCH TO TWR AND I (CAPT) SAID WE CAN'T USE RWY 1, BECAUSE OF THE TAILWIND. HE SAID THAT WE WERE SUPPOSED TO TAXI TO RWY 19. I REPLIED THAT WE HEARD RWY 1. WE THEN RECEIVED NEW INSTRUCTIONS TO TAXI TO RWY 19 AND DEPARTED WITHOUT INCIDENT. CONTRIBUTING FACTORS WERE FATIGUE. WE HAD BEEN ON DUTY SINCE XA:00 LOCAL TIME AND HAD NOT HAD TIME TO EAT ANY FOOD ALL DAY DUE TO MAINT DELAYS AT A PREVIOUS OUTSTATION. ALSO RELATED, THE TWR CTLR APPEARED TO HAVE BEEN WORKING ALL FREQS AT THE TIME AND WAS DISTRACTED BY CLRNC CALLS/READBACKS AND INBOUND TFC. ALSO, WE WERE RUNNING BEHIND BEING PUSHED BY OUR RAMP PERSONNEL TO TURN THE ACFT QUICKLY. I ALSO THOUGHT THAT PERHAPS THE WIND HAD SHIFTED AND THUS THE RWY IN USE SWITCHED. WE DID GET THE WINDS FROM GND AND STARTED OUR TAXI TO RWY 1. WE PROBABLY COULD HAVE PREVENTED THE SITUATION BY QUESTIONING THE USE OF RWY 1 (OUR PERCEPTION) EARLIER. THERE IS ALSO A POSSIBILITY THE CTLR LET OFF ON THE MIC SWITCH EARLY OR WAS BLOCKED ON THE NINER PART OF RWY 19 (READ AS 'ONE NINER'). THIS RWY COULD BE EASILY CONFUSED IF THE 'NINER' PART IS BLOCKED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT ON REACHING RWY 01, THEY IMMEDIATELY REALIZED THEY WERE AT THE INCORRECT RWY. THEY WERE INFORMED BY THE CTLR THAT A CLRNC TO RWY 19 HAD BEEN ISSUED.

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.