Narrative:

We taxied for takeoff at cleveland and tower told us it would be 4 more mins before our release time. Within 1 min, tower called back and told us to 'cross runway 28, cleared for takeoff runway 23R.' I taxied across runway 28 and commenced takeoff on runway 23L. About 60 KTS, tower cancelled our takeoff clearance and said we had been cleared for takeoff on 23R, not 23L. Even though tower had said 23R and was acknowledged by the first officer, I 'heard' 23L because I was mentally programmed for the 'usual' runway for takeoff at cleveland. Another case of not listening to what was actually said instead of what I expected. Thanks to the vigilance of the tower crew for catching my mistake before it became a serious problem. The situation would not have occurred if I had 'listened up.' the tower controller could have helped (because of the different-than-usual runway) by stating: 'cleared to cross 28 and 23L, cleared for takeoff 23R, that's 23R.' callback conversation with reporter revealed the following information: reporter explained reason ATC had changed runway to 23R was that a vehicle was operating on 23L at southwest end of runway. Air carrier X aborted and turned off approximately 6000 ft from the vehicle. Tower had cleared them for takeoff on 23R and first officer readback corrected (23R), but flight crew still were thinking 23L because of ATIS information and usual takeoff on the left runway. They taxied back after abort and were then cleared for takeoff on 23L.

Related reports:

Google
 

Original NASA ASRS Text

Title: WRONG RWY TKOF BY COMMUTER AT CLE.

Narrative: WE TAXIED FOR TKOF AT CLEVELAND AND TWR TOLD US IT WOULD BE 4 MORE MINS BEFORE OUR RELEASE TIME. WITHIN 1 MIN, TWR CALLED BACK AND TOLD US TO 'CROSS RWY 28, CLRED FOR TKOF RWY 23R.' I TAXIED ACROSS RWY 28 AND COMMENCED TKOF ON RWY 23L. ABOUT 60 KTS, TWR CANCELLED OUR TKOF CLRNC AND SAID WE HAD BEEN CLRED FOR TKOF ON 23R, NOT 23L. EVEN THOUGH TWR HAD SAID 23R AND WAS ACKNOWLEDGED BY THE FO, I 'HEARD' 23L BECAUSE I WAS MENTALLY PROGRAMMED FOR THE 'USUAL' RWY FOR TKOF AT CLEVELAND. ANOTHER CASE OF NOT LISTENING TO WHAT WAS ACTUALLY SAID INSTEAD OF WHAT I EXPECTED. THANKS TO THE VIGILANCE OF THE TWR CREW FOR CATCHING MY MISTAKE BEFORE IT BECAME A SERIOUS PROBLEM. THE SITUATION WOULD NOT HAVE OCCURRED IF I HAD 'LISTENED UP.' THE TWR CTLR COULD HAVE HELPED (BECAUSE OF THE DIFFERENT-THAN-USUAL RWY) BY STATING: 'CLRED TO CROSS 28 AND 23L, CLRED FOR TKOF 23R, THAT'S 23R.' CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR EXPLAINED REASON ATC HAD CHANGED RWY TO 23R WAS THAT A VEHICLE WAS OPERATING ON 23L AT SW END OF RWY. ACR X ABORTED AND TURNED OFF APPROX 6000 FT FROM THE VEHICLE. TWR HAD CLRED THEM FOR TKOF ON 23R AND FO READBACK CORRECTED (23R), BUT FLC STILL WERE THINKING 23L BECAUSE OF ATIS INFO AND USUAL TKOF ON THE L RWY. THEY TAXIED BACK AFTER ABORT AND WERE THEN CLRED FOR TKOF ON 23L.

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.